Probe messages should not sent Precedence header
Bug #808821 reported by
Barry Warsaw
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| GNU Mailman | Status tracked in 3.0 | |||||
| 3.0 |
Fix Released
|
Medium
|
Barry Warsaw | |||
Bug Description
Probe messages (sent after an address has been disabled due to bounces) should not set Precedence. This is because they actually are not bulk or list traffic. It's possible that where list traffic might be bouncing, a non-Precedence containing probe message could have a better chance of getting through. One thing to think about though is vacation programs, which (if well-behaved) will not respond to Precedence messages. Thus, if a person's address were bouncing, and they had a vacation program on, these would respond to probe messages. This might be significant if we were to score probe bounces higher (i.e. as signs to permanently disable or delete the address).
Related branches
lp:~msapiro/mailman/precedence-fix
- Barry Warsaw: Approve
-
Diff: 94 lines (+45/-3)4 files modifiedsrc/mailman/app/bounces.py (+3/-1)
src/mailman/app/docs/message.rst (+38/-0)
src/mailman/docs/NEWS.rst (+2/-0)
src/mailman/email/message.py (+2/-2)
Revision history for this message
| Mark Sapiro (msapiro) wrote | #1 |
To post a comment you must log in.
Fix committed for Mailman 2.1.15. See <http://
Still open for Mailman 3.