Description of problem: The CYRUSV2_MAILER_ARGS used to have the value `FILE /var/imap/socket/lmtp' but this changed in cyrus-imapd-3.0.2 (release 2) with commit #3a725240446, specifically the introduction of the file patch-cyrus-default-settings. Version-Release number of selected component (if applicable): sendmail-8.15.2-19 cyrus-imapd-3.0.4-1 How reproducible: Install both packages above. Steps to Reproduce: 1. Install both packages. 2. Modify your sendmail.mc file to have: define(`confLOCAL_MAILER', `cyrusv2')dnl MAILER(cyrusv2)dnl then "make sendmail.cf" and "systemctl restart sendmail.service" 3. Send yourself an email. Actual results: Oct 20 18:55:40 mail sendmail[3244]: v9L0tYLt003240: SYSERR(root): Could not connect to socket /var/lib/imap/socket/lmtp: Connection refused by localhost Oct 20 18:55:40 mail sendmail[3244]: v9L0tYLt003240: to=philipp, delay=00:00:00, xdelay=00:00:00, mailer=cyrusv2, pri=140297, relay=localhost, dsn=4.4.1, stat=Deferred: Connection refused by localhost Expected results: Oct 20 22:06:39 localhost cyrus/lmtpunix[2277]: Delivered: <4ADC6710-49B7-42BD-B248-1E5103092E56> to mailbox: user.philipp.Lists.Darwin-kernel Oct 20 22:06:39 localhost cyrus/lmtpunix[2277]: USAGE philipp user: 0.028834 sys: 0.009641 Oct 20 22:06:39 localhost sendmail[2281]: v9L46Wn3002278: to=philipp, delay=00:00:01, xdelay=00:00:00, mailer=cyrusv2, pri=96757, relay=localhost, dsn=2.0.0, stat=Sent Additional info: You'll also need to modify SElinux policy as: #============= sendmail_t ============== allow sendmail_t cyrus_var_run_t:sock_file { getattr write };
Created attachment 1341490 [details] Correct CYRUSV2_MAILER_ARGS to point to path for lmtp socket
I upgraded from F25 to F26 and my production mail server broke right away. After a couple of hours of digging, I got delivery working again. Jason: please note that I *also* had to extensively edit the cyrus-imapd.conf files to restore functionality, in particular: % cat >> /etc/imapd.conf sasl_mech_list: CRAM-MD5 DIGEST-MD5 unixhierarchysep: off altnamespace: off ^D % sed -i -e 's/^httpdmodules/# &/' /etc/imapd.conf % sed -r -i -e 's/^#\( idled\)/\1/' /etc/cyrus.conf Note that imapd.conf(5) says "see sasl_mech_list" but it's not documented anywhere (seems to be an upstream bug). Could we fix the *new* config files to be more compatible with prior installs, even if the defaults have changed? i.e. add back the "unixhierarchysep" and "altnamespace" values (which now default to "on")?
The answer to the last question is "definitely not". Upstream has justified their changing of those default values and I made sure that mention of the changes made it into the release notes along with a link to the upstream documentation which is very clear about the change in those values. https://docs.fedoraproject.org/f26/release-notes/sysadmin/Mail_Servers.html If you read those and somehow didn't know about the change in the default calues then, well, I just don't know what to say. If you didn't read the release notes then, uh.... As to the other stuff, I would not expect that the new configuration file would work with your existing system. RPM doesn't overwrite your existing files for a reason. I'm sorry you had a difficult time of it, but you appear to have brought the bulk of that upon yourself.
(In reply to Jason Tibbitts from comment #3) > The answer to the last question is "definitely not". [snip] > https://docs.fedoraproject.org/f26/release-notes/sysadmin/Mail_Servers.html > > If you read those and somehow didn't know about the change in the default > calues then, well, I just don't know what to say. If you didn't read the > release notes then, uh.... I read it, but I hadn't noticed what the previous defaults were. > As to the other stuff, I would not expect that the new configuration file > would work with your existing system. RPM doesn't overwrite your existing > files for a reason. I'm sorry you had a difficult time of it, but you > appear to have brought the bulk of that upon yourself. What about adding a commented out section like: # if you're upgrading from cyrus-imapd 2.4 or 2.6, uncomment these: #unixhiearchy: off #altnamespace: off Usually the configs on Fedora are pretty good about helping people maintain continuity even with the frequent pace of updates.
By the way, the release notes don't talk about cyrus-imapd having a built-in httpd service or how that might interfere with existing Apache on a machine already hosting a website.
Also, is this a known issue? Oct 24 11:48:52 mail master[24698]: invalid value 'isschedule' for httpmodules in line 55 The package is 'ischedule' not 'isschedule'. The typo is creeping in from patch-cyrus-default-configs
(In reply to Philip Prindeville from comment #6) > Also, is this a known issue? > > Oct 24 11:48:52 mail master[24698]: invalid value 'isschedule' for > httpmodules in line 55 > > The package is 'ischedule' not 'isschedule'. The typo is creeping in from > patch-cyrus-default-configs This seems to be a more urgent issue, since it stops the service from starting up so I'll open a separate bug.
See bug #1506000
Adding Lukas and Miroslav because of the SElinux policy changes implied by the fix.
Looking at /etc/postfix/main.cf on F26, it looks like that's broken too. Opening a bug for that as well.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Can we please fix this? It's a one line change: dnl define(`CYRUSV2_MAILER_ARGS', `FILE /var/lib/imap/socket/lmtp')dnl should be: define(`CYRUSV2_MAILER_ARGS', `FILE /run/cyrus/socket/lmtp')dnl in /etc/mail/sendmail.mc (sendmail) and in /usr/share/sendmail-cf/mailer/cyrusv2.m4 (sendmail-cf). Thanks
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.