'approved' rule should not modify the message
Bug #973790 reported by
Barry Warsaw
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Confirmed
|
Low
|
Unassigned |
Bug Description
In Mailman 3, technically rules should not have side effects. The 'approved' rule breaks this because it removes the Approved header (and other supported headers) from the message. There should instead be a handler that does the header cleaning, and the rule should not do this.
From an implementation standpoint, the same code can be used in both the handler and in the rule. You can use a slightly different API wrapper and use a flag to indicate whether the header should be removed or not. OTOH, some clever refactoring might make better sense.
Changed in mailman: | |
status: | New → Confirmed |
importance: | Undecided → Low |
milestone: | none → postponed |
To post a comment you must log in.
As far as I see, the cleanse handler removes the approved headers, too. I.e. whenever the message goes through the posting pipeline, the headers are removed.
Should they get removed when the message goes through other pipelines, too? If not, I guess the removal code from the approved rule could just be deleted?