replicating (manage)sieve - no symlink on replica?

[Stephan Bosch]

On 9/11/2014 3:36 PM, Philipp wrote:
> 2.2.13/0.4.2, both from source-tarball, no fancy options.
>
> tcp-replication between two nodes and following plugin parameters
> (same on both sides, except the ip-addr)
> plugin {
>  sieve_before = /home/ssfn/etc/dovecot/sieve.default
>  sieve_global_dir = /home/ssfn/etc/dovecot
>  sieve = ~/.dovecot.sieve
>  sieve_dir = ~/.sieve
>  sieve_extensions = +vnd.dovecot.duplicate
>  sieve_duplicate_period = 6h
>  mail_replica = tcp:10.66.50.15:9993
> }
>
> mail_location = sdbox:/home/ssfn/var/mail/boxes/%n
> mail_home = /home/ssfn/var/mail/boxes/%n
>
> Testbed: user getting first email delivered, the subdir %n/.sieve/tmp
> is automatically created as expected.
> User logs into managesieve on node1 and uploads a script.
> The %n/.sieve/managesieve.sieve and the symlink .dovecot.sieve ->
> .sieve/managesieve.sieve
> is created as expected.
>
> One node2 (via replica) happens:
> automatically create %n/.sieve/tmp
> automatically create/sync %n/.sieve/managesieve.sieve
> just NOT the symlink .dovecot.sieve -> .sieve/managesieve.sieve
>
> Logfiles for lmtp,doveadm,dsync-local dont indicate an error why it
> could not create the link or such,
> to me it looks like it wouldnt even try.
>
> mail-syncing works flawlessly (for delivery, just read about the
> expunge .. hum.)
>
> I tried to force a full-resync via doveadm replicator afterwards, to
> no change on the matter.
>
> Any input?

Sorry, I haven't had time to look at this one. I believe a similar issue
was reported earlier. It is on my list, but testing this is a bit
cumbersome for me at the moment.

Regards,

Stephan.