Bug 1506336 - postfix mailbox_transport definition no longer works with cyrus-imapd-3.0.2-3
Summary: postfix mailbox_transport definition no longer works with cyrus-imapd-3.0.2-3
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix
Version: 27
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-25 18:13 UTC by Philip Prindeville
Modified: 2018-11-30 21:27 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:27:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1505015 0 unspecified CLOSED sendmail cyrusv2 mailer definition no longer works with cyrus-imapd-3.0.2-3 2021-02-22 00:41:40 UTC

Internal Links: 1505015

Description Philip Prindeville 2017-10-25 18:13:08 UTC
Description of problem:

The stock /etc/postfix/main.cf as shipped in F26 today (postfix-2:3.2.3-1) includes the following section:

#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
# Cyrus IMAP over LMTP. Specify ``lmtpunix      cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

Problem is that as of cyrus-imapd-3.0.2-3, the correct path per the above
referenced imapd.conf file is:

/run/cyrus/socket/lmtp

so the file postfix-3.2.0-config.patch needs to be refreshed.

The "fallback_transport" probably also needs to be changed.

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

postfix-2:3.2.3-1

How reproducible:

Install postfix and cyrus-imapd.  Uncomment #mailbox_transport line and
do "postfix reload".  Watch your mail queue file up because the messages
are undeliverable.


Steps to Reproduce:
1. As above
2.
3.

Actual results:

Postfix fails to pass message along to IMAPd for final delivery.

Expected results:

Normal and timely delivery of messages.

Additional info:

You'll also need to modify SElinux policy as:

#============= postfix_smtpd_exec_t ==============
allow postfix_smtpd_exec_t cyrus_var_run_t:sock_file { getattr write };

or something similar.  Not sure what context LMTP delivery happens in.

Comment 1 Fedora End Of Life 2018-05-03 09:00:07 UTC
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.

Comment 2 Philip Prindeville 2018-05-03 19:04:32 UTC
This is a 3 line fix to postfix-3.2.0-config.patch:

+#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

+# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

+#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp

should all point to /run/cyrus/socket/lmtp as the path instead.

Comment 3 Ben Cotton 2018-11-27 15:49:46 UTC
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.

Comment 4 Ben Cotton 2018-11-30 21:27:36 UTC
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.


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