I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
On 07/17/2014 08:43 AM, Jimmy wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
...
2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description
I'm really guessing here, but it looks like postfix is attempting to deliver this message via a 'mailman' transport and is piping the message to the transport (postfix_to_mailman.py ?) and there is some issue because there is no user 'list' in the system.
If this doesn't help, please provide more detail as to your postfix configuration. E.g. things like the output from 'postconf -n' the non-comment contents of /etc/postfix/transport and the definition of the 'mailman' transport from /etc/postfix/master.cf.
Also, see the FAQ at <http://wiki.list.org/x/EYDt>
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
Based on this error and the following link I think I'm missing something from my /etc/postfix/transport.
"unknown mail transport error" http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+...
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
On Mon, Jul 21, 2014 at 11:01 AM, Jimmy <g17jimmy@gmail.com> wrote:
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
On Mon, Jul 21, 2014 at 11:01 AM, Jimmy <g17jimmy@gmail.com> wrote:
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
On 7/21/2014 11:05 AM, Jimmy wrote:> Based on this error and the following link I think I'm missing something
from my /etc/postfix/transport.
"unknown mail transport error"
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+...
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
Why do you use postfix-to-mailman.py ? That piece is not recommended by the Mailman developers. See
http://wiki.list.org/pages/viewpage.action?pageId=15564817--Barry Finkel
I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not exist on my system, postfix-to-mailman.py isn't anywhere on my system at all, so that obviously presents a problem. Is that not normally in the RPM installation?
Thanks
On Mon, Jul 21, 2014 at 12:05 PM, Jimmy <g17jimmy@gmail.com> wrote:
Based on this error and the following link I think I'm missing something from my /etc/postfix/transport.
"unknown mail transport error"
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+...
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
On Mon, Jul 21, 2014 at 11:01 AM, Jimmy <g17jimmy@gmail.com> wrote:
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
I just found where the postfix-to-mailman line came from:
http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix
And see that Mark specifically recommends not using this doc. I'm backing that config out.
On Mon, Jul 21, 2014 at 1:04 PM, Jimmy <g17jimmy@gmail.com> wrote:
I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not exist on my system, postfix-to-mailman.py isn't anywhere on my system at all, so that obviously presents a problem. Is that not normally in the RPM installation?
Thanks
On Mon, Jul 21, 2014 at 12:05 PM, Jimmy <g17jimmy@gmail.com> wrote:
Based on this error and the following link I think I'm missing something from my /etc/postfix/transport.
"unknown mail transport error"
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+...
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
On Mon, Jul 21, 2014 at 11:01 AM, Jimmy <g17jimmy@gmail.com> wrote:
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=<systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
Backed out the 3rd party mailman module config, corrected the permissions on the aliases* files, restarted mailman and postfix and all is functional now. Thanks!
On Mon, Jul 21, 2014 at 1:43 PM, Jimmy <g17jimmy@gmail.com> wrote:
I just found where the postfix-to-mailman line came from:
http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix
And see that Mark specifically recommends not using this doc. I'm backing that config out.
On Mon, Jul 21, 2014 at 1:04 PM, Jimmy <g17jimmy@gmail.com> wrote:
I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not exist on my system, postfix-to-mailman.py isn't anywhere on my system at all, so that obviously presents a problem. Is that not normally in the RPM installation?
Thanks
On Mon, Jul 21, 2014 at 12:05 PM, Jimmy <g17jimmy@gmail.com> wrote:
Based on this error and the following link I think I'm missing something from my /etc/postfix/transport.
"unknown mail transport error"
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+...
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
On Mon, Jul 21, 2014 at 11:01 AM, Jimmy <g17jimmy@gmail.com> wrote:
I'm not sure why it's trying to use a username 'list', if that is the problem. Here are the things you mentioned. Thanks.
======master.cf====== mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
======/etc/postfix/transport====== lists.listdomain.com mailman:
======postconf -n====== alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix default_privs = nobody html_directory = no inet_interfaces = all inet_protocols = ipv4 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix mydestination = $myhostname localhost.$mydomain localhost lists.listdomain.com mydomain = lists.listdomain.com mynetworks = 10.0.0.0/8 mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix recipient_delimiter = + relay_domains = listdomain.com relayhost = mailserver.prod.listdomain.com sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop soft_bounce = no transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550
On Thu, Jul 17, 2014 at 11:43 AM, Jimmy <g17jimmy@gmail.com> wrote:
I am still working on this new mailman system and seeing these errors when an email is sent to the system. I've googled the errors and haven't yet found anything that helps. Any ideas? Thanks
2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]: connect from unknown[10.0.0.1] 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1] 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]: 790A84583: message-id=< 7e1decc87c4844c18882f3a27eefa406@CORPEXCHMBX10.listdomain.com> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]: 790A84583: from=<username@listdomain.com>, size=5925, nrcpt=1 (queue active) 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]: fatal: get_service_attr: unknown username: list 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]: disconnect from unknown[10.0.0.1] 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]: warning: private/mailman socket: malformed response 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]: warning: transport mailman failure -- see a previous warning/fatal/panic logfile record for the problem description 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command startup -- throttling 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]: 790A84583: to=< systems-changelog@lists.listdomain.com>, relay=none, delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport error) 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]: 740AF107: from=<username@listdomain.com>, size=5114, nrcpt=1 (queue active) 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]: 740AF107: to=< systems-changelog@lists.listdomain.com>, relay=none, delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
On 07/21/2014 10:43 AM, Jimmy wrote:
I just found where the postfix-to-mailman line came from:
http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix
And see that Mark specifically recommends not using this doc. I'm backing that config out.
Thanks for bringing that FAQ up. It is terribly misleading despite the Warning I added in sec 4. I didn't write it, and I have now added a stronger warning against following it at the top.
I see from other posts that you have things working now. I'm glad you got it straightened out.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Jimmy writes:
I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not exist on my system, postfix-to-mailman.py isn't anywhere on my system at all, so that obviously presents a problem. Is that not normally in the RPM installation?
That's right. IIRC, postfix-to-mailman.py was developed by Bruce Perens and adopted by Debian because it fits their configuration management philosophy better. AFAIK you'll find it on Debian and derivatives but not elsewhere.
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
With open source software, 3rd party guides need to be treated with care.
With open source software, 3rd party guides need to be treated with care.
Very true, I stumbled upon the other instructions and got that mixed up with what I was working on. I backed it all out and got it working now. Thanks!
On Mon, Jul 21, 2014 at 8:51 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
Jimmy writes:
I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not exist on my system, postfix-to-mailman.py isn't anywhere on my system at all, so that obviously presents a problem. Is that not normally in the RPM installation?
That's right. IIRC, postfix-to-mailman.py was developed by Bruce Perens and adopted by Debian because it fits their configuration management philosophy better. AFAIK you'll find it on Debian and derivatives but not elsewhere.
I used the 'integrating mailman and postfix' guide but don't see what I need to do to fix it. Thanks
With open source software, 3rd party guides need to be treated with care.
participants (4)
-
Barry S. Finkel -
Jimmy -
Mark Sapiro -
Stephen J. Turnbull