Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks.
On 03/15/11 09:57, Dennis Putnam wrote:
Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks.
The bounce score begins at 0.0. Each bounce (only one per day is counted) increases the score by 1.0 or 0.5 depending upon if the -bounces processing detects a soft error or hard error. Once the bounce score reaches 5.0, the subscription is set to NOMAIL, and for three successive weeks, once per week, a test mail is sent to the address asking the subscriber to re-confirm. If there is no response to these three mailings, then the address is unsubscribed. All of these parameters are configurable. The bounced mail that triggers the 5.0 score is sent to the list owners, the previous bounce messages are discarded. The unsubscribe notice is sent to the list owners.
I run a report daily
http://veenet.value.net/~msapiro/scripts/get_bounce_info.pythat tells me for each Mailman list, each subscriber that has a bounce score greater than zero. I review the report daily to spot bad addresses.
Look at the Mailman logs
/var/log/mailman/bounceand maybe other logs in that directory.
--
Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 240, Room 5.B.8 Internet: BSFinkel@anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994
On Tue, 15 Mar 2011 11:24:25 -0500, Barry Finkel <bsfinkel@anl.gov> wrote:
On 03/15/11 09:57, Dennis Putnam wrote:
Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks.
The bounce score begins at 0.0. Each bounce (only one per day is counted) increases the score by 1.0 or 0.5 depending upon if the -bounces processing detects a soft error or hard error. Once the bounce score reaches 5.0, the subscription is set to NOMAIL, and for three successive weeks, once per week, a test mail is sent to the address asking the subscriber to re-confirm. If there is no response to these three mailings, then the address is unsubscribed. All of these parameters are configurable. The bounced mail that triggers the 5.0 score is sent to the list owners, the previous bounce messages are discarded. The unsubscribe notice is sent to the list owners.
I run a report daily
http://veenet.value.net/~msapiro/scripts/get_bounce_info.pythat tells me for each Mailman list, each subscriber that has a bounce score greater than zero. I review the report daily to spot bad addresses.
Look at the Mailman logs
/var/log/mailman/bounceand maybe other logs in that directory.
Are you sure about the 1.0 and 0.5 score based on soft and hard failure? I think Mark has said previously that a soft and hard bounce both get scored as 1.0.
Jeff
Jeff Grossman wrote:
Are you sure about the 1.0 and 0.5 score based on soft and hard failure? I think Mark has said previously that a soft and hard bounce both get scored as 1.0.
The documentation on the Bounce processing page talks about the 0.5 and 1.0 score for a soft or hard bounce, but that's wrong (I really should change it, but doing so breaks every i18n translation rendering the entire documentation section of the page in English regardless of the list's language, so I don't).
A "soft" bounce is scored as either 0 or 1 depending on what you consider a soft bounce. E.g., a 'delay' DSN is ignored (scored as 0), but a message which is undeliverable due to a full mailbox is probably scored as 1. It actually depends on the format of the DSN returned, but any RFC 3464 compliant DSN with a 'failed' action is scored as 1.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Mark Sapiro <mark@msapiro.net>:
Jeff Grossman wrote:
Are you sure about the 1.0 and 0.5 score based on soft and hard failure? I think Mark has said previously that a soft and hard bounce both get scored as 1.0.
The documentation on the Bounce processing page talks about the 0.5 and 1.0 score for a soft or hard bounce, but that's wrong (I really should change it, but doing so breaks every i18n translation rendering the entire documentation section of the page in English regardless of the list's language, so I don't).
Well, shit happens :) Just do it!
-- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt@charite.de | http://www.charite.de
I am really trying to reply to Barry but, as a note to the admins, Barry's message did not make it to me for some reason. If it weren't for the replies I would not have seen this.
Thanks Barry.
P.S. I tried to go to the veenet link but it keeps timing out.
On 3/15/2011 4:41 PM, Jeff Grossman wrote:
On Tue, 15 Mar 2011 11:24:25 -0500, Barry Finkel <bsfinkel@anl.gov> wrote:
On 03/15/11 09:57, Dennis Putnam wrote:
Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks.
The bounce score begins at 0.0. Each bounce (only one per day is counted) increases the score by 1.0 or 0.5 depending upon if the -bounces processing detects a soft error or hard error. Once the bounce score reaches 5.0, the subscription is set to NOMAIL, and for three successive weeks, once per week, a test mail is sent to the address asking the subscriber to re-confirm. If there is no response to these three mailings, then the address is unsubscribed. All of these parameters are configurable. The bounced mail that triggers the 5.0 score is sent to the list owners, the previous bounce messages are discarded. The unsubscribe notice is sent to the list owners.
I run a report daily
http://veenet.value.net/~msapiro/scripts/get_bounce_info.pythat tells me for each Mailman list, each subscriber that has a bounce score greater than zero. I review the report daily to spot bad addresses.
Look at the Mailman logs
/var/log/mailman/bounceand maybe other logs in that directory. Are you sure about the 1.0 and 0.5 score based on soft and hard failure? I think Mark has said previously that a soft and hard bounce both get scored as 1.0.
Jeff
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net
On 3/15/2011 3:15 PM, Dennis Putnam wrote:
P.S. I tried to go to the veenet link but it keeps timing out.
On Tue, 15 Mar 2011 11:24:25 -0500, Barry Finkel <bsfinkel@anl.gov> wrote:
I run a report daily
http://veenet.value.net/~msapiro/scripts/get_bounce_info.py
That server died some time ago and the ISP that provided it never replaced it, but never removed the DNS record for it.
You can find that script at <http://www.msapiro.net/scripts/get_bounce_info.py> and <http://fog.ccsf.edu/~msapiro/scripts/get_bounce_info.py>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
Barry Finkel -
Dennis Putnam -
Jeff Grossman -
Mark Sapiro -
Ralf Hildebrandt