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 barry, nitishch, r.david.murray, thedoctorsoup
Date 2018-01-28.03:56:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1517111799.66.0.467229070634.issue32606@psf.upfronthosting.co.za>
In-reply-to
Content
Yes.

There's this thing called Postel's Law that says you should be generous in what you accept and careful in what you emit.  So most MTAs and MUAs try very hard to guess what a non-RFC-compliant email is trying to say, which includes allowing spaces between the label and the colon (which I believe was legal at least in RFC 822, though I haven't checked).  If there's a space in the label, the handling for that is less predictable.  The email library's default is to treat that as a non-header line and therefor the start of the body (even if not followed by a blank line).
History
Date User Action Args
2018-01-28 03:56:39r.david.murraysetrecipients: + r.david.murray, barry, nitishch, thedoctorsoup
2018-01-28 03:56:39r.david.murraysetmessageid: <1517111799.66.0.467229070634.issue32606@psf.upfronthosting.co.za>
2018-01-28 03:56:39r.david.murraylinkissue32606 messages
2018-01-28 03:56:39r.david.murraycreate