Re: [Mailman-Users] problem with mailman not working...
Thanks again. Observations: Somehow the stale lock was stopping all emails from going out and secondly, /var/lock/mailman is where the lock was. I'm not sure how I happened to figure that lock location out as it isn't ~mailman/locks. Perhaps my config is non-standard. Troy This email was created using 100% recycled organic free range electrons. On 1/13/2012 4:11 PM, Mark Sapiro wrote: Troy Campbell wrote: It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! I'm glad things are again working well for you, but deleting and recreating the list was probably overkill. The FAQ at http://wiki.list.org/x/noA9 gives information about clearing stale/orphaned locks. I have now added a pointer to this FAQ from section 7 of the FAQ athttp://wiki.list.org/x/A4E9. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problem with mailman not working...
Troy Campbell wrote: Thanks again. Observations: Somehow the stale lock was stopping all emails from going out and secondly, /var/lock/mailman is where the lock was. I'm not sure how I happened to figure that lock location out as it isn't ~mailman/locks. Perhaps my config is non-standard. Is this a RedHat RPM installation? See http://wiki.list.org/x/KYCB. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problem with mailman not working...
It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 8:05 PM, Mark Sapiro wrote: On 1/12/2012 6:09 PM, Troy Campbell wrote: It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878: to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23, delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post troytest) No email is coming out though? It should be expanding to my email address? OK. The mail was piped to the wrapper to be posted to the list, so now it's getting to Mailman. See the FAQ athttp://wiki.list.org/x/A4E9, particularly sections 2b, 6b, 7, 8, 9 and 13. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problem with mailman not working...
Troy Campbell wrote: It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! I'm glad things are again working well for you, but deleting and recreating the list was probably overkill. The FAQ at http://wiki.list.org/x/noA9 gives information about clearing stale/orphaned locks. I have now added a pointer to this FAQ from section 7 of the FAQ at http://wiki.list.org/x/A4E9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] problem with mailman not working...
For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? Regards, -- Troy 719-484-2300 This email was created using 100% recycled organic free range electrons. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problem with mailman not working...
Troy Campbell wrote: For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Yes, it sounds like a Postfix issue, but in order to say anything, we'd need to see postconf -n and some relevant Postfix log messages. Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. Which one? (ps -fw) I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? The command is postalias, not postmap, and it's unlikely to help unless perhaps you previously ran 'postmap /etc/mailman/aliases', but it couldn't hurt to run 'postalias /etc/mailman/aliases'. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] problem with mailman not working...
Thanks so much Mark...see inline replies below Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 5:48 PM, Mark Sapiro wrote: Troy Campbell wrote: For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Yes, it sounds like a Postfix issue, but in order to say anything, we'd need to see postconf -n and some relevant Postfix log messages. # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliaseshash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = no inet_interfaces = all local_recipient_maps = mail_owner = postfix mailbox_size_limit = 0 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname localhost.$mydomainlocalhost localhost.localdomainrequest1.localdomain request2.localdomain request1.rmtc.fedex.com request2.rmtc.fedex.com mailman.rmtc.fedex.commailman2.rmtc.fedex.com mynetworks = 127.0.0.1/32146.18.0.0/16 155.161.0.0/16161.135.0.0/16 165.150.0.0/16170.5.0.0/16 170.86.0.0/16172.18.64.0/18 192.189.184.0/22198.140.0.0/22 199.81.0.0/16199.82.0.0/16 204.135.100.0/23204.135.106.0/23 204.135.108.0/23204.135.92.0/23 204.135.94.0/23204.135.96.0/23 204.135.97.0/23172.31.248.0/23 172.31.252.0/23 newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no permit_mx_backup_networks = $mynetworks queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES recipient_delimiter = + relay_domains = cosd.fedex.comrmtc.fedex.com relayhost = mapper.mail.fedex.com sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_authorized_verp_clients = localhost smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/accesspermit_mynetworks reject_unauth_destination transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. Which one? (ps -fw) mailman 21869 21862 92 16:16 ?02:24:52 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? The command is postalias, not postmap, and it's unlikely to help unless perhaps you previously ran 'postmap /etc/mailman/aliases', but it couldn't hurt to run 'postalias /etc/mailman/aliases'. It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1
Re: [Mailman-Users] problem with mailman not working...
On 1/12/2012 6:09 PM, Troy Campbell wrote: It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878: to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23, delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post troytest) No email is coming out though? It should be expanding to my email address? OK. The mail was piped to the wrapper to be posted to the list, so now it's getting to Mailman. See the FAQ at http://wiki.list.org/x/A4E9, particularly sections 2b, 6b, 7, 8, 9 and 13. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org