FW: [Mailman-Users] No Bounce Notification

[Tony]

Thank you very much for your input Mark.  

Stephen, will you please verify the MTA settings and correct if necessary.

Regards,
Tony

-----Original Message-----
From: Mark Sapiro [mailto:msapiro at value.net]
Sent: Monday, September 20, 2004 1:08 PM
To: Tony; mailman-users at python.org; public at webhearth.com
Subject: Re: FW: [Mailman-Users] No Bounce Notification

Tony wrote:

>Attached is most of the log file.  Please let me know if anyone finds
>anything out of the ordinary.
>

<big snip>


>bounce:Sep 15 00:10:26 2004 (3629) testlist_thetrick.us: tony at tony.tony =
>bounce score: 1.0
>bounce:Sep 15 00:25:27 2004 (3629) testlist_thetrick.us: web at thetrick.su =
>bounce score: 1.0
>bounce:Sep 15 00:25:27 2004 (3629) sending testlist_thetrick.us list =
>probe to: web at thetrick.su (score 1.0 >=3D 0.5)
>bounce:Sep 15 00:25:27 2004 (3629) testlist_thetrick.us: =
>noaddess at yahoo.com bounce score: 1.0
>bounce:Sep 15 00:25:27 2004 (3629) sending testlist_thetrick.us list =
>probe to: noaddess at yahoo.com (score 1.0 >=3D 0.5)

<more snips>

A new feature in 2.1.5 is that before disabling or unsubscribing,
bounce processing sends a VERP-like probe message to the bouncing
address to confirm bouncing. If this probe doesn't bounce, the bounce
processing is not continued. Apparently, there is a problem with your
MTA receiving the bounced VERP-like probes and they are getting lost.

>From the Mailman 2.1.5 NEWS file:

- The bounce processor has been redesigned so that now when an
address's bounce score reaches the threshold, that address will be
sent a probe message.  Only if the probe bounces will the address be
disabled. The score is reset to zero when the probe is sent.  Also,
bounce events are now kept in an event file instead of in memory.
This should help contain the bloat of the BounceRunner.

   New supporting variables in Defaults.py: VERP_PROBE_FORMAT,
   VERP_PROBE_REGEXP

   REGISTER_BOUNCES_EVERY is promoted to a Defaults.py variable.


Basically, the probe is sent with envelope from
     <listname>-bounces+<token string>@<domain>

The outgoing MTA needs to preserve this envelope from address. When the
delivery of the probe bounces, it is returned to the probe's envelope
from address. The incoming MTA needs to be aware of the "+" delimiter
so that it will deliver the bounce to the <listname>-bounces address
with the <token string> intact. This would be in your MTA
configuration somewhere.

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