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 Johannes Löthberg, barry, maciej.szulik, msapiro, r.david.murray
Date 2017-06-03.18:10:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496513412.77.0.60899842333.issue27321@psf.upfronthosting.co.za>
In-reply-to
Content
replace_header has a different semantic than del-and-set (replace_header leaves the header in the same location in the list, rather than appending it to the end...that's it's purpose).  If replace_header is throwing a key error, then I guess we need a look-before-you-leap if statement.

And a test :)

Note that a correct fix would preserve the broken input email, but since we're obviously already doing munging I'm fine with just making this work for now.
History
Date User Action Args
2017-06-03 18:10:12r.david.murraysetrecipients: + r.david.murray, barry, msapiro, maciej.szulik, Johannes Löthberg
2017-06-03 18:10:12r.david.murraysetmessageid: <1496513412.77.0.60899842333.issue27321@psf.upfronthosting.co.za>
2017-06-03 18:10:12r.david.murraylinkissue27321 messages
2017-06-03 18:10:12r.david.murraycreate