> (always with MysqlMemberships.py)
> I noticed that my bounce info stays in the database at level 1, even
> when the logs say "current bounce score: 2.0"
>
> In Mailman/Bouncer.py I think that two self.setBounceInfo(member,
> info) are missing:
>
> --- Mailman/Bouncer.save.py 2008-06-16 10:00:17.000000000 +0200
> +++ Mailman/Bouncer.py 2008-06-16 10:00:43.000000000 +0200
> @@ -137,6 +137,7 @@ class Bouncer:
> if lastbounce + self.bounce_info_stale_after < now:
> # Information is stale, so simply reset it
> info.reset(weight, day, self.bounce_you_are_disabled_warnings)
> + self.setBounceInfo(member, info)
> syslog('bounce', '%s: %s has stale bounce info, resetting',
> self.internal_name(), member)
> else:
> @@ -144,6 +145,7 @@ class Bouncer:
> # score and take any necessary action.
> info.score += weight
> info.date = day
> + self.setBounceInfo(member, info)
> syslog('bounce', '%s: %s current bounce score: %s',
> self.internal_name(), member, info.score)
> # Continue to the check phase below
Hello,
After another day has passed, I can confirm that this patch allows
MysqlMemberships.py to be notified of the bounce scores.
-- Fil
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
