[Mailman-Developers] Debugging lost messages?

[Brad Knowles]

At 5:08 PM -0700 2005-10-04, Mark Sapiro wrote:

>  Is archiving on?

	Yes.  There's nothing in the archives for this list since the 
15th of September, and so far as I can tell nothing has been sent out 
to any of the list members since then.

>                   Are there members with delivery not disabled? If these
>  are digest members is digestable 'yes'? Likewise, if there are regular
>  members is nondigestable 'yes'?

	There are ten members of the list, none of which are in digest 
mode, and none are disabled.

>  Since there are presumably other, working lists, much of the FAQ isn't
>  relevant, but check for list locks in locks/

	Nope, no locks.  Of course, I had stopped and restarted Mailman, 
and sent a test message through (which worked), before I checked to 
see if there were any locks.

>  Also, if other lists are working, the wrapper and the scripts/post
>  script are presumably working, at least assuming that the wrapper in
>  the aliases pipe is the same one for this list as for the others that
>  work.

	The other lists are working fine, so far as I can tell.

>  You could put a 'debug' in scripts/post to be sure, but all it does is
>  put the message in qfiles/in. Check the queue or maybe all the queues,
>  but when you say there's no evidence of the messages in Mailman, maybe
>  you've already checked.

	I had checked all the queues before stopping and restarting 
Mailman, and they were all empty.

>  Once the message gets to qfiles/in, processing continues with
>  Mailman/Queue/IncomingRunner.py which basically directs the message
>  through the handlers in Mailman/Handlers/ which are listed in the
>  list's 'pipeline' attribute or the GLOBAL_PIPELINE. Does the list have
>  a 'pipeline' attribute? If so, are certain critical delivery handlers
>  such as  'ToDigest', 'ToArchive' and 'ToOutgoing' all there?

	I did not set up any list-specific pipeline, no.

>  Is there a lists/<listname>/extend.py file? If so, what is it intended
>  to do and does it work?

	No, there is no extend.py file for any of these lists.  The 
installation is pretty plain-jane.  About the only thing we modified 
was some of the templates for auto responses, telling the sender that 
their message was being held, etc....

>  It may be none of these things, but that's about all I can think of at
>  the moment.

	I certainly couldn't think of anything else.

>  If I couldn't find anything obvious in the above ideas, I'd try putting
>  a debug logging statement conditional on mlist.internal_name() ==
>  listname in Mailman/Queue/IncomingRunner.py in the while loop in
>  _dopipeline to see how far it gets.

	I'll give that a shot.  Thanks!

-- 
Brad Knowles, <brad at stop.mail-abuse.org>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
     Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See <http://www.sage.org/> for more info.