Re: [Mailman-Developers] Debugging lost messages?

2005-10-10 Thread Brad Knowles
At 5:29 AM +0200 2005-10-07, Brad Knowles wrote: This is what I find so frustrating about debugging this particular process. As far as Mailman is concerned, you really can't get too much more plain-jane than what we're running. And yet, stuff has clearly been broken for about a

Re: [Mailman-Developers] Debugging lost messages?

2005-10-10 Thread Brad Knowles
At 11:18 AM +0200 2005-10-10, Brad Knowles wrote: What I'd like to do is add the name of the handler somewhere in that line, but I'm not sure how to do that. I'm going to read up on programming in Python, but any advice or assistance that anyone can provide would be appreciated.

Re: [Mailman-Developers] Debugging lost messages?

2005-10-10 Thread Brad Knowles
At 11:51 AM +0200 2005-10-10, Brad Knowles wrote: Anyway, I should now have the modname being printed in the vette log, so that I should be able to figure out which handler is causing the inappropriate bounces. I'll let you know when I find out more. Okay, I think I found

Re: [Mailman-Developers] Debugging lost messages?

2005-10-10 Thread Mark Sapiro
Brad Knowles wrote: Okay, I think I found the offending module. Hold.py will syslog to vette, if the message is being held. But Moderate.py will not syslog anything -- it passes a held message to Hold.py, but handles rejections and discards itself. Moreover, Moderate.py uses

Re: [Mailman-Developers] Debugging lost messages?

2005-10-10 Thread Brad Knowles
At 12:32 PM -0700 2005-10-10, Mark Sapiro wrote: In a prior post, you indicate that IncomingRunner was detecting a RejectMessage exception. Correct. and presumably you were seeing that log message. Thus, we know it is a 'reject' and not a 'discard'. I am seeing some

Re: [Mailman-Developers] Debugging lost messages?

2005-10-06 Thread Brad Knowles
At 5:08 PM -0700 2005-10-04, Mark Sapiro wrote: 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.

Re: [Mailman-Developers] Debugging lost messages?

2005-10-06 Thread Barry Warsaw
On Thu, 2005-10-06 at 12:39, Brad Knowles wrote: But I'm not seeing any details as to why a message is being discarded or bouncing. I see two more messages that came in today to the list in question, and by matching message-ids and listnames between the Mailman vette log and the

Re: [Mailman-Developers] Debugging lost messages?

2005-10-06 Thread Brad Knowles
At 10:31 PM -0400 2005-10-06, Barry Warsaw wrote: Maybe they're triggering one of your content (or other) filters? Have you got this list set up to discard non-members or something else of that nature? I thought of those. All non-member postings are supposed to be held for

Re: [Mailman-Developers] Debugging lost messages?

2005-10-05 Thread 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

[Mailman-Developers] Debugging lost messages?

2005-10-04 Thread Brad Knowles
Folks, I've got another mailing list server installation (Mailman 2.1.5 and postfix 2.2-20040504), and I've just discovered that one of the lists has been broken for about a month and I'm having some problems figuring out how messages are being lost. The postfix logs are

Re: [Mailman-Developers] Debugging lost messages?

2005-10-04 Thread Mark Sapiro
Brad Knowles wrote: I've got another mailing list server installation (Mailman 2.1.5 and postfix 2.2-20040504), and I've just discovered that one of the lists has been broken for about a month and I'm having some problems figuring out how messages are being lost. The postfix