➜

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 david.caro
Recipients david.caro, r.david.murray
Date 2011-03-14.20:01:51
SpamBayes Score 3.688724e-05
Marked as misclassified No
Message-id <1300132911.78.0.292482848893.issue11021@psf.upfronthosting.co.za>
In-reply-to
Content 
Of course, the RFC that discusses the MIME-Version Header is  RFC-2045
http://www.ietf.org/rfc/rfc2045.txt

Extract of the page 8:
   "Note that the MIME-Version header field is required at the top level
   of a message.  It is not required for each body part of a multipart
   entity."

Strictly all the implementations should support the MIME-Version on each field, because the RFC does not explicitly say that it should not be included, but all the best practice documents that mention it say that it should not be included in all the parts, my main concern is that maybe it raises the spam level of the sent e-mails.

Maybe it's not critical enough to be backported, but at least, it should be changed for future versions.

Thanks
History
Date User Action Args
2011-03-14 20:01:51david.carosetrecipients: + david.caro, r.david.murray
2011-03-14 20:01:51david.carosetmessageid: <1300132911.78.0.292482848893.issue11021@psf.upfronthosting.co.za>
2011-03-14 20:01:51david.carolinkissue11021 messages
2011-03-14 20:01:51david.carocreate