Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
Created attachment 1333943[details]
Rebase against 2.2.32 and pigeonhole 0.4.20
Figured we'd rebase a new RPM against 2.2.32. It certainly fixes this bug, among others.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3182