Author r.david.murray
Recipients barry, groner, r.david.murray
Date 2016-09-09.23:24:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473463499.14.0.786969378992.issue25235@psf.upfronthosting.co.za>
In-reply-to
Content
It turns out that solving this header problem via MIMEPart isn't really a good idea, given the rest of the API.  I don't want to not use 'type', or rather I do want to use the new policy.message_factory, and I don't really want to have to have two message_factory attributes.  I'm considering the possibility of only adding a MIME header in the Generator at the top level if and only if there are no parser derived headers.  (This will do the right think only if you stick to the new API, since the old API adds the header indiscriminately in several places).
History
Date User Action Args
2016-09-09 23:24:59r.david.murraysetrecipients: + r.david.murray, barry, groner
2016-09-09 23:24:59r.david.murraysetmessageid: <1473463499.14.0.786969378992.issue25235@psf.upfronthosting.co.za>
2016-09-09 23:24:59r.david.murraylinkissue25235 messages
2016-09-09 23:24:59r.david.murraycreate