[Mailman-Users] bouce processing problem

[Mark Sapiro]

Dimitrios Karapiperis 

>verp enabled lsit -> test
>maximum member bounce score 2.0
>The number of days after which a member's bounce information is 
>discarded, if no new bounces have been received in the interim  7
>How many /Your Membership Is Disabled/ warnings disabled member should 
>get before their address is removed from the mailing list. 0
>The number of days between sending the /Your Membership Is Disabled/ 
>warnings  0
>
>
>non-verp list -> test12
>maximum member bounce score 2.0
>The number of days after which a member's bounce information is 
>discarded, if no new bounces have been received in the interim  7
>How many /Your Membership Is Disabled/ warnings a disabled member should 
>get before their address is removed from the mailing list. 1
>The number of days between sending the /Your Membership Is Disabled/ 
>warnings  0


This is inconsistent. This says you are going to disable delivery to
the member and send the member one warning notice, but then you are
going to remove the member from the list after 0 days, effectively
giving the member no time to respond to the warning if it is received.

>Logs
>Do you mean /var/log/mailman/bounce?

Yes.


>It catches the bounce but it doesn't increase the bounce score for the 
>e-mail address in question.
>
>Sep 25 18:43:54 2009 (5993) test: lala1 at domain.gr already scored a 
>bounce     for date 25-Sep-2009
>Sep 25 18:43:55 2009 (5775) <BounceRunner at 47833231358288> processing 
>1 queued   bounces
>Sep 25 18:43:55 2009 (5775) test: city at domain.gr current bounce 
>score:    2.0
>Sep 25 18:43:55 2009 (5775) <BounceRunner at 47833231358288> processing 
>1 queued  bounces
>Sep 25 18:43:55 2009 (5775) test: city at domain.gr already scored a bounce 
>for date 25-Sep-2009
>Sep 25 18:58:55 2009 (22975) <OutgoingRunner at 47783975251768> 
>processing 1 queued bounces
>Sep 25 18:58:55 2009 (22975) test12: lala1 at domain.gr current bounce 
>score:      2.0
>Sep 25 18:58:55 2009 (22975) <OutgoingRunner at 47783975251768> 
>processing 1 queued bounces
>Sep 25 18:58:55 2009 (22975) test12: lala1 at domain.gr already scored a 
>bounce for date 25-Sep-2009


Are these all the messages in that portion of the log? There should be
a "disabling" entry after the 

Sep 25 18:58:55 2009 (22975) test12: lala1 at domain.gr current bounce
score:      2.0

since the threshold for that list is 2.0.

What is in Mailman's error log (/var/log/mailman/error)?

If no exception occurred in bounce processing, there should at a
minimum be a "sending probe" log message or a "disabling" log message
following the message where the score reaches the threshold. If an
exception occurred, it should be logged in the error log.

The only other possibility I see is that somehow the
bounce_score_threshold for these lists is set to the string "2.0"
rather than the floating point value 2.0. Then bounce processing will
not see that 2.0 is >= "2.0".
	
-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan