I've been trying to assimilate the way the bounce handling is done by
Mailman so as to set up ways to handle the odd ball bounces that clog my
in-box. I see that BouncerAPI runs through the "BOUNCE_PIPELINE". I
assume that adding an entry there and putting the appropriate py file in
pref
> "SP" == Skye Poier <[EMAIL PROTECTED]> writes:
SP> Another followup.
SP> I added the following to SimpleMatch.py
Thanks Skye, and thanks JC for forwarding this to me. Although I'm
going to implement this slightly differently to accommodate another
MSExchange format I've got on fil
I'm actually enjoying the conversation (though it is one sided). I've
modified most of the other parts of Mailman at one time or another and
always wanted to look at the bounce sections - just never had a good
reason to.
Looks like it's as easy to modify as the other modules.
If you take it to
Another followup.
I added the following to SimpleMatch.py
# MSEXCH
(_c('did not reach the following recipient'),
_c('MSEXCH:'),
_c('(?P[^ ]*) on ')),
to catch bounces like this:
Your message
To: [EMAIL PROTECTED]
Subject: [Test] test8
Sent:Tue, 15 Oct 2002 19:5
Well, since nobody helped, I went ahead and started debugging the stuff
in Bouncers/*.py
First I took a look at why Hotmail bounces weren't being caught in
DSN.py. Here's an example with my debugging:
Oct 16 12:46:01 2002 (11207) DSN parsing header {'action': 'failed',
'final-recipient': 'rfc82
Hello,
I just upgraded from mailman 2.0beta4 to 2.0.13 (python 2.2.1) and
everything is going pretty smoothly, except certain kinds of bounces
aren't being picked up by the bounce detector.
I've verified that the Bouncers/*.py process() functions are being
called, and it picks up some bounces, b
