This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Nicolas.Estibals, jcea, r.david.murray
Date 2011-06-18.19:57:58
SpamBayes Score 6.7861106e-07
Marked as misclassified No
Message-id <1308427080.04.0.318923681623.issue12147@psf.upfronthosting.co.za>
In-reply-to
Content
I think we can treat this as a bug.  However...

What if there is more than one set of Resent- headers?  I think that it is not possible to guarantee we only look at the most recent set, since the RFC provides no way to identify a "set".  Heuristically we could probably guess right 99% of the time, but we'd still be guessing.  Further, the RFC actually prohibits using the Resent- headers for "automated processing", though, granted, it is talking about the receiving end, not the sending end.

My inclination at this point is to fix the Sender bug, and to refuse to guess when there are any Resent- headers (throw a ValueError).  I've queried the email-sig to see what they think.
History
Date User Action Args
2011-06-18 19:58:00r.david.murraysetrecipients: + r.david.murray, jcea, Nicolas.Estibals
2011-06-18 19:58:00r.david.murraysetmessageid: <1308427080.04.0.318923681623.issue12147@psf.upfronthosting.co.za>
2011-06-18 19:57:59r.david.murraylinkissue12147 messages
2011-06-18 19:57:58r.david.murraycreate