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.
Bug 1941114 - Packaged translatesieve is non-functional
Summary: Packaged translatesieve is non-functional
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cyrus-imapd
Version: 8.3
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Martin Osvald 🛹
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-20 02:57 UTC by Simon Wilson
Modified: 2023-03-20 07:27 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-20 07:27:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Simon Wilson 2021-03-20 02:57:00 UTC
Description of problem:
Running translatesieve on sieve scripts migrated from cyrus-imapd 2.4 as advised in upgrade documentation (due to change in default altnamespace) fails as it tries to run on the wrong directory. Running with translatesieve from a configured and made but not installed 3.0.15 works fine, although I have not been able to find a corresponding bugfix at Cyrus.

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

How reproducible:
On my system I replicated cyrus mailstores from the Cyrus 2.4 server (on CentOS 7) to the Cyrus 3.0 server (on RHEL8) which copies over the sieve scripts to /var/lib/imap/sieve. Replication should not be needed though, as long as the original scripts are there. The old server had fileinto commands working under a 'altnamespace: 0' system, so used INBOX/ formats for folders. As I already had unixhierarchysep: 1, so the correct command is "translatesieve -n -u" for a dry run. Leaving off the -n produces a FATAL error as expected.

Steps to Reproduce:
1. have some sieve scripts in /var/lib/imap/sieve, and a functional RHEL-package installed cyrus-imapd 3.0.7
2. run the translatesieve script with -n for dry run (has to be run as cyrus user)
3. observe error...

Actual results:
bash-4.4$  /usr/libexec/cyrus-imapd/translatesieve -u -n
you are using /var/lib/imap/sieve as your sieve directory.
translating sievedir /var/lib/imap/sieve... not converting separator.
converting name space from traditional to alternative.
error: couldn't chdir to portables
error: couldn't chdir to private
error: couldn't chdir to tpm
error: couldn't chdir to polkit-1
error: couldn't chdir to rsyslog
error: couldn't chdir to NetworkManager
error: couldn't chdir to setroubleshoot
error: couldn't chdir to udisks2
error: couldn't chdir to rhsm
error: couldn't chdir to mlocate
error: couldn't chdir to postfix

Expected results:
...would be what I get when running with the translatesieve from 3.0.15: (ignore the described changes, as I have already converted these scripts it would mess it up if I actually ran it again).
bash-4.4$ /opt/cyrus-imapd-3.0.15/tools/translatesieve -u -n
you are using /var/lib/imap/sieve as your sieve directory.
translating sievedir /var/lib/imap/sieve... not converting separator.
converting name space from traditional to alternative.
translating ingo.script...
translating ingo.script...
<     fileinto "Spam";
>     fileinto "Shared Folders/Spam";
translating ingo.script...
<     fileinto "Spam";
>     fileinto "Shared Folders/Spam";
...etc...

Additional info:

Comment 1 Simon Wilson 2021-03-20 03:01:41 UTC
One thing I should have put in additional info...

When it tries to run it *says* it is running on the correct directory:

 you are using /var/lib/imap/sieve as your sieve directory.
 translating sievedir /var/lib/imap/sieve... not converting separator.

...but then iterates through directories two levels higher (/var/lib):

 error: couldn't chdir to portables
 error: couldn't chdir to private
 error: couldn't chdir to tpm
 error: couldn't chdir to polkit-1
 error: couldn't chdir to rsyslog
 error: couldn't chdir to NetworkManager
 error: couldn't chdir to setroubleshoot
 error: couldn't chdir to udisks2
 error: couldn't chdir to rhsm
 error: couldn't chdir to mlocate
 error: couldn't chdir to postfix

Comment 4 RHEL Program Management 2022-09-20 07:27:46 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 7 RHEL Program Management 2023-03-20 07:27:48 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.