[Mailman-Users] urgent: no mail shows up as pending...

[Mark Sapiro]

Maulwurf wrote:

>Sep 12 13:24:28 2007 (25625) 
><mailman.1462.1189596252.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.114 seconds

Above is from smtp log and is successful delivery of a mailman
generated notice (the message ID is a mailman generated one).



>__post
>Sep 12 09:56:15 2007 (25625) post to esel-mehl from 
>esel-mehl-bounces at esel.at, size=8726, 
>message-id=<mailman.1403.1189583762.11060.esel-mehl at esel.at>, 1 failures
>Sep 12 10:01:38 2007 (25625) post to safari from rain2 at gmx.at, 
>size=242776, message-id=<20070912063227.10690 at gmx.net>, success
>Sep 12 10:24:20 2007 (25625) post to esel-mehl from 
>esel-mehl-bounces at esel.at, size=8991, 
>message-id=<mailman.1417.1189585444.11060.esel-mehl at esel.at>, 1 failures
>Sep 12 11:54:27 2007 (25625) post to esel-mehl from 
>esel-mehl-bounces at esel.at, size=10681, 
>message-id=<mailman.1440.1189590851.11060.esel-mehl at esel.at>, 1 failures
>Sep 12 12:08:23 2007 (25625) post to beatboxing from 
>beatboxing-bounces at esel.at, size=7727, 
>message-id=<mailman.1446.1189591683.11060.beatboxing at esel.at>, 1 failures
>
>does not seem related (time earlier...)


The failures correspond with messages in the smtp_failure log.


>smtp could be related - but here everything seems alright, doesn't it?
>
>__smtp
>Sep 12 13:08:20 2007 (25625) 
><mailman.1461.1189595283.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.100 seconds
>Sep 12 13:24:28 2007 (25625) 
><mailman.1462.1189596252.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.114 seconds
>Sep 12 13:29:20 2007 (25625) 
><mailman.1463.1189596542.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.120 seconds
>Sep 12 13:32:35 2007 (25625) 
><mailman.1464.1189596734.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.497 seconds
>Sep 12 13:32:36 2007 (25625) 
><mailman.1465.1189596735.11060.esel-mehl at esel.at> smtp to esel-mehl for 
>1 recips, completed in 0.065 seconds


These too are all normal delivery of Mailman generated notices.



>__smtp-failure
>Sep 12 13:38:27 2007 (25625) All recipients refused: {'gateway at esel.at': 
>(550, '5.1.1 <gateway at esel.at>: Recipient address rejected: User unknown 
>in local recipient table')}, msgid: <mailman.6561.1189597105
>Sep 12 13:38:27 2007 (25625) delivery to gateway at esel.at failed with 
>code 550: 5.1.1 <gateway at esel.at>: Recipient address rejected: User 
>unknown in local recipient table


This is a Mailman generated notice to <gateway at esel.at> which the
outgoing MTA can't deliver.


>don't know if one of them is the messages that i have been sending...?!


Probably not, but they might be notices of the held message.


>____these are my latest entries in error
>they don't seem to be related with my sending (at 13:00)
>
>Sep 12 11:50:49 2007 (1557) Traceback (most recent call last):
>File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
>self._onefile(msg, msgdata)
>File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in 
>_dispose
>more = self._dopipeline(mlist, msg, msgdata, pipeline)
>File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in 
>_dopipeline
>sys.modules[modname].process(mlist, msg, msgdata)
>File "/usr/lib/mailman/Mailman/Handlers/Moderate.py", line 109, in process
>Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
>File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 224, in 
>hold_for_approval
>id = mlist.HoldMessage(msg, reason, msgdata)
>File "/usr/lib/mailman/Mailman/ListAdmin.py", line 189, in HoldMessage
>self.__opendb()
>File "/usr/lib/mailman/Mailman/ListAdmin.py", line 86, in __opendb
>self.__db = cPickle.load(fp)
>UnpicklingError: invalid load key, 'U'.
>
>Sep 12 11:50:49 2007 (1557) SHUNTING: 
>1189586196.3920839+935d0b4da5eaa35f51fe0714411d6b1d85fd8d38

<snip>

>Sep 12 12:45:00 2007 (1557) Uncaught runner exception:
>Sep 12 12:45:00 2007 (1557) Traceback (most recent call last):
>File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop
>self._onefile(msg, msgdata)
>File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in 
>_dispose
>more = self._dopipeline(mlist, msg, msgdata, pipeline)
>File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in 
>_dopipeline
>sys.modules[modname].process(mlist, msg, msgdata)
>File "/usr/lib/mailman/Mailman/Handlers/Moderate.py", line 109, in process
>Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost)
>File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 224, in 
>hold_for_approval
>id = mlist.HoldMessage(msg, reason, msgdata)
>File "/usr/lib/mailman/Mailman/ListAdmin.py", line 189, in HoldMessage
>self.__opendb()
>File "/usr/lib/mailman/Mailman/ListAdmin.py", line 86, in __opendb
>self.__db = cPickle.load(fp)
>MemoryError
>
>Sep 12 12:45:00 2007 (1557) SHUNTING: 
>1189589342.6301639+c26ce6b7163c2cc5dfeacc835d0cda2c53095ae9

<snip>

It appears that at least one list has a corrupt request.pck file
causing the UnpicklingError. The MemoryError might also be due to a
corrupt request.pck file.

Run bin/show_qfiles on qfiles/shunt/* to see the shunted messages which
will tell you what they are and what lists they're for.

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