Description of problem:

On host1, within a user's mail directory, after activating an Out of Office message in Roundcube, the .dovecot.sieve symbolic link is correctly created:

imap1:/VOLUMES/imapstore/rgiles# ls -la
total 8
drwxr-xr-x. 4 vmail vmail 102 Jan 10 13:50 .
drwxr-x---. 4 vmail vmail  33 Dec 21 13:56 ..
-rw-------. 1 vmail vmail  38 Jan 10 11:13 .dovecot.lda-dupes
lrwxrwxrwx. 1 vmail vmail  23 Jan 10 10:47 .dovecot.sieve -> sieve/managesieve.sieve

-rw-------. 1 vmail vmail 138 Jan 10 13:50 .dovecot.svbin
drwx------. 4 vmail vmail 149 Dec 21 14:14 mdbox
drwx------. 3 vmail vmail  42 Jan 10 11:14 sieve

On the other host, the symlink is *not* created properly (but the Sieve scripts *are* correctly propagated, as well as e-mail, etc.).

imap2:/VOLUMES/imapstore/rgiles# ls -la
total 0
drwxr-xr-x. 4 vmail vmail 32 Jan 13 13:32 .
drwxr-x---. 4 vmail vmail 33 Dec 21 13:58 ..
drwx------. 4 vmail vmail 86 Dec 21 14:14 mdbox
drwx------. 3 vmail vmail 42 Jan 10 11:14 sieve

This is a bug that is fixed in later versions of Dovecot-Pigeonhole (0.4.4 onward).

RHEL7 ships with dovecot-pigeonhole-2.2.10-7.el7.x86_64, which contains Pigeonhole 0.4.2.

This particular thread on the Dovecot list also describes the issue (and detailing that the problem was identified and fixed in a later version):

https://dovecot.org/list/dovecot/2015-February/099661.html

Version-Release number of selected component (if applicable):

dovecot-pigeonhole-2.2.10-7.el7.x86_64
dovecot-2.2.10-7.el7.x86_64

How reproducible:

Always

Steps to Reproduce:

Setup Dovecot dsync replication service on two hosts

Actual results:

The symlink is *not* created 

Expected results:

Create symlink