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 gkuenning, r.david.murray
Date 2017-12-13.02:32:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513132324.48.0.213398074469.issue32298@psf.upfronthosting.co.za>
In-reply-to
Content
From RFC 2047:

(3) As a replacement for a 'word' entity within a 'phrase', for example,
    one that precedes an address in a From, To, or Cc header.  The ABNF
    definition for 'phrase' from RFC 822 thus becomes:

    phrase = 1*( encoded-word / word )

    In this case the set of characters that may be used in a "Q"-encoded
    'encoded-word' is restricted to: <upper and lower case ASCII
    letters, decimal digits, "!", "*", "+", "-", "/", "=", and "_"
    (underscore, ASCII 95.)>.  An 'encoded-word' that appears within a
    'phrase' MUST be separated from any adjacent 'word', 'text' or
    'special' by 'linear-white-space'.

The reason for this is that things like '@' are syntactically significant in headers and so must be encoded.
History
Date User Action Args
2017-12-13 02:32:04r.david.murraysetrecipients: + r.david.murray, gkuenning
2017-12-13 02:32:04r.david.murraysetmessageid: <1513132324.48.0.213398074469.issue32298@psf.upfronthosting.co.za>
2017-12-13 02:32:04r.david.murraylinkissue32298 messages
2017-12-13 02:32:03r.david.murraycreate