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 Henning.von.Bargen
Recipients Eric Lafontaine, Henning.von.Bargen, maciej.szulik, r.david.murray
Date 2016-12-16.16:00:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481904008.38.0.224404099573.issue28879@psf.upfronthosting.co.za>
In-reply-to
Content
OK, I understand the arguments. 
If I understand correctly, this will be fixed in one way or another in Python 3.6 or 3.7.
For Python 2.7, this will not be fixed (so I have to work around this somehow, should be quite easy).
I think that at least the documentation and the examples for smtplib should be updated.

The doc should make it clear that the message is passed "as-is" and it's the caller's reponsibility to create a valid message string.

The examples at https://docs.python.org/2/library/email-examples.html should note which header fields are required by RFC 5322 and provide an example.
History
Date User Action Args
2016-12-16 16:00:08Henning.von.Bargensetrecipients: + Henning.von.Bargen, r.david.murray, maciej.szulik, Eric Lafontaine
2016-12-16 16:00:08Henning.von.Bargensetmessageid: <1481904008.38.0.224404099573.issue28879@psf.upfronthosting.co.za>
2016-12-16 16:00:08Henning.von.Bargenlinkissue28879 messages
2016-12-16 16:00:08Henning.von.Bargencreate