Mailman should honor X-Approve and X-Approved

Bug #557750 reported by Barry Warsaw on 2010-04-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Status tracked in 3.0
2.1
Undecided
Mark Sapiro
3.0
Undecided
Barry Warsaw

Bug Description

From mailman-users:

It appears that while the Approved: header is standard in Usenet for
posting to moderated groups, it's use for email and email lists has
never been standardized (RFC 2076, Sec 3.4). Thus, your point is well
taken.

dag (dag-wieers) wrote :

Original thread:

    http://mail.python.org/pipermail/mailman-users/2010-April/069232.html

For backward compatibility I would support both Approved: and X-Approved: headers. Just in case so that after an upgrade the Approved: header is not shared with the whole mailing-list (exposing your password). The documentation could indicate X-Approved: as being supported and deprecate the usage of Approved: ?

Barry Warsaw (barry) wrote :

Sorry, I was time constrained when I submitted the bug. Yes, absolutely we should continue to support the old headers. I don't think we need to deprecate them though.

Barry Warsaw (barry) wrote :

r6592 in Mailman 3

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers