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, r.david.murray
Date 2013-01-16.21:13:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358370824.34.0.785969797245.issue16983@psf.upfronthosting.co.za>
In-reply-to
Content
It has come to my attention that at least some mail agents apply postel's law to addresses like the following:

   From: "=?utf-8?Q?not_really_valid?=" <foo@example.com>

Since encountering something that looks like an encoded word but that is not is a very unlikely occurrence, we could go ahead and decode such strings, resulting in

   "not really valid" <foo@example.com>

a defect would be registered, and some sort of 'strict' policy mode could refuse to do the decode (as well as several other non-compliant patterns, such as encoded words not separated by whitespace).  I think the decoding should be the default, though.

This applies also to other headers where words or phrases can be quoted, such as in filenames.  I have also encountered the quoted-encoded-word-as-filename in the wild.
History
Date User Action Args
2013-01-16 21:13:44r.david.murraysetrecipients: + r.david.murray, barry
2013-01-16 21:13:44r.david.murraysetmessageid: <1358370824.34.0.785969797245.issue16983@psf.upfronthosting.co.za>
2013-01-16 21:13:44r.david.murraylinkissue16983 messages
2013-01-16 21:13:43r.david.murraycreate