[Mailman-Users] mailman has just stopped sending out mail toallmailing lists

Mark Sapiro msapiro at value.net
Tue Nov 28 00:02:33 CET 2006


Dirk Koopman wrote:

>The make install has a large number of "pointers differ in signedness
>warnings"


I think the only things that would produce this are the compilations of
the wrappers, and I don't see that wrapper issues could cause the
problem you're having.

Did you do any kind of Python update just before things stopped working?


>I did an 'unshunt' and here are some results
>
>Some extracts from the logs:
>
> == smtp-failure
>
>Nov 27 21:53:25 2006 (12035) delivery to seankerry at btinternet.com failed with code -1: please run connect() first
>Nov 27 21:53:25 2006 (12035) delivery to jane_major at msn.com failed with code -1: please run connect() first
>Nov 27 21:53:25 2006 (12035) delivery to mark at charnley7145.freeserve.co.uk failed with code -1: (-2, 'Name or service not known')
>Nov 27 21:53:25 2006 (12035) delivery to tom.pollendine at middlelevel.co.uk failed with code -1: (-2, 'Name or service not known')
>Nov 27 21:53:25 2006 (12035) delivery to Addmitch at aol.com failed with code -1: please run connect() first
>Nov 27 21:53:25 2006 (12035) delivery to pmitzs at yahoo.com failed with code -1: please run connect() first
>Nov 27 21:53:25 2006 (12035) delivery to sweenmarie at aol.com failed with code -1: please run connect() first
>Nov 27 21:53:25 2006 (12035) delivery to leserve at tinyworld.co.uk failed with code -1: (-2, 'Name or service not known')
>Nov 27 21:53:25 2006 (12035) delivery to djk at tobit.co.uk failed with code -1: (-2, 'Name or service not known')
>Nov 27 21:53:25 2006 (12035) delivery to janzyuk at yahoo.co.uk failed with code -1: (-2, 'Name or service not known')
>
>this is a snapshot of the last few lines. Each recipient has one of a
>similar set of messages for every .pck.


Strange, as the shunting occurs well before delivery, but in any case,
the above are not related to the shunting errors. These errors occur
between Mailman and the outgoing MTA. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.073.htp>
and
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.014.htp>


> == error
>
>Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.583493+aa39005732b51ab067ad1e5ac45d4cf8cb1bf3f1
>Nov 27 21:53:24 2006 (12031) Uncaught runner exception: 'str' object has no attribute 'get_sender'
>Nov 27 21:53:24 2006 (12031) Traceback (most recent call last):
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
>    self._onefile(msg, msgdata)
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 162, in _onefile
>    sender = msg.get_sender()
>AttributeError: 'str' object has no attribute 'get_sender'
>
>Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.5915849+536fe1680b23dc5e1d4773156e3c0e98b6e64ed0
>
>this is one of these for every pck


Expected as the shunted queue entries are defective (the question is
how did they get that way).

You need to apply the workaround discussed at
<http://mail.python.org/pipermail/mailman-users/2006-September/053556.html>
and then try to unshunt. The workaround will also allow new messages
to process OK.


> == smtp
>
>Nov 27 21:53:23 2006 (12035) <mailman.1.1164655871.6021.dxspider-support at dxcluster.org> smtp to dxspider-support for 1 recips, completed in 0.007 seconds
>Nov 27 21:53:23 2006 (12035) <mailman.5.1164657531.6019.pelicans at tobit.co.uk> smtp to pelicans for 2 recips, completed in 0.009 seconds
>Nov 27 21:53:24 2006 (12035) <20061127203222.31969.qmail at web86010.mail.ird.yahoo.com> smtp to pelicans for 204 recips, completed in 0.024 seconds
>Nov 27 21:53:25 2006 (12035) <2F78F48E8F45F2468D09D7768EEEA9230585C3 at ryburgh4> smtp to pelicans for 204 recips, completed in 0.053 seconds
>
>entirely normal


Except all the deliveries failed.


> == post
>
>Nov 27 21:53:23 2006 (12035) post to pelicans from mailman-bounces at tobit.co.uk, size=4440, message-id=<mailman.5.1164657531.6019.pelicans at tobit.co.uk>, 2 failures
>Nov 27 21:53:24 2006 (12035) post to pelicans from collin.picton at btinternet.com, size=18105, message-id=<20061127203222.31969.qmail at web86010.mail.ird.yahoo.com>, 204 failures
>Nov 27 21:53:25 2006 (12035) post to pelicans from bob.king at crispmalt.com, size=153840, message-id=<2F78F48E8F45F2468D09D7768EEEA9230585C3 at ryburgh4>, 204 failures


These again relate to the sending issue, not the shunting issue, but
these two issues could be related at the Python level. Again, have
there been any Python changes?

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan



More information about the Mailman-Users mailing list