| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
list from a non-member who is a member of a regular_include_list, the
bounce will be processed as a bounce for the included list.
|
| |
|
|
| |
for a member just deleted if bounce_you_are_disabled_warnings is zero.
|
| |
|
|
|
|
| |
to accommodate MemberAdaptors that store bounce info outside the
list instance.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Split GetConfirmSubject into Leave/Join.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Closing [ 1003070 ] Decode original subject in post acknowledgement
by Soji IKEDA
Modified Files:
Tag: Release_2_1-maint
Mailman/Bouncer.py
Mailman/Handlers/Acknowledge.py
|
| |
|
|
|
|
|
|
|
|
|
| |
registerBounce(): When the bounce score is higher than the threshold, instead
of disabling the address right way, we send a probe message, then we reset the
bounce score to zero.
disableBouncingMember(): Use the new pending db interface and update the log
messages.
sendNextNotification(): Use the new pending db interface.
|
| |
|
|
|
|
|
|
| |
fix for SF bug # 846681, where the confirmation cookie emailed in a
bounce disabled notification was always out of date. The problem was
that we created the cookie at the time of the first bounce. This is
very likely more than three days before the time of the last bounce,
which is when we should have (and now do) create the cookie.
|
| | |
|
|
|
'Release_2_1-maint'.
|
