Message 101039 - Python tracker

➜

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.

In-reply-to
Author	r.david.murray
Recipients	grmtz, r.david.murray
Date	2010年03月14日.02:49:14
SpamBayes Score	0.0061246944
Marked as misclassified	No
Message-id	<1268534957.09.0.999696045543.issue8132@psf.upfronthosting.co.za>

Content
Per the RFC, this is the correct behavior. An encoded word must begin and end either at the field boundary or with whitespace. So ...?=Arobase, with no whitespace between the = and Arobase, makes your first example into an invalid encoded word, and thus it is returned as if it were plain ASCII. One could argue that email could be smarter and interpret this string as an encoded word anyway, following the Postel principle (be generous in what you accept), but it currently does not do so, and not doing so is not a bug. email6 will handle such non-RFC compliant examples better, if all goes well.

Content

Per the RFC, this is the correct behavior. An encoded word *must* begin and end either at the field boundary or with whitespace. So ...?=Arobase, with no whitespace between the = and Arobase, makes your first example into an invalid encoded word, and thus it is returned as if it were plain ASCII.
One could argue that email could be smarter and interpret this string as an encoded word anyway, following the Postel principle (be generous in what you accept), but it currently does not do so, and not doing so is not a bug.
email6 will handle such non-RFC compliant examples better, if all goes well.

History
Date	User	Action	Args
2010年03月14日 02:49:17	r.david.murray	set	recipients: + r.david.murray, grmtz
2010年03月14日 02:49:17	r.david.murray	set	messageid: <1268534957.09.0.999696045543.issue8132@psf.upfronthosting.co.za>
2010年03月14日 02:49:15	r.david.murray	link	issue8132 messages
2010年03月14日 02:49:14	r.david.murray	create

homepage