On 02/20/2014 10:07 AM, Lindsay Haisley wrote: > I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA, > running Python 2.7.3. I track security updates and install them > promptly when they're issued by Ubuntu. Yesterday I updated the Linux > kernel from 3.2.0-58-generic (x86_64) to 3.2.0-59-generic and Mailman > quit working. List posts made it through to the archives, and were > apparently queued within Mailman, but wouldn't go out. The mail server > was working OK for non-list email. Today I backed out the kernel update > and posts to lists sent yesterday and today are going out without > problems.
What's in Mailman's 'post' and 'smtp' logs for these messages. Are they timestamped before or after you backed out the update. If before, they were queued in the MTA. If after, they were in Mailman's 'out' queue. If the latter, what's in Mailman's 'qrunner' log related to OutgoingRunner. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
