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 Lita.Cho, barry, ezio.melotti, jesstess, r.david.murray, rafales
Date 2014-07-16.19:22:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Postel's Law says: be conservative in what you do, be liberal in what you accept from others.  So the client should not violate the RFC when sending data to the server.  The server, on the other hand, by that law could accept "dirty" data if it can do something reasonable with it...except that in general the IMAP RFC in particular says "don't do that".  IMAP servers are supposed to be IMAP RFC sticklers, even when accepting input.  So gmail is broken for some definition of broken, and so is imaplib.

Since the code has been this way for a long time, and gmail does in fact accept it, I think a doc warning about []s violating the RFC should be sufficient; a warning would probably just be annoying to little real benefit.
Date User Action Args
2014-07-16 19:22:37r.david.murraysetrecipients: + r.david.murray, barry, ezio.melotti, jesstess, Lita.Cho, rafales
2014-07-16 19:22:37r.david.murraysetmessageid: <>
2014-07-16 19:22:37r.david.murraylinkissue21815 messages
2014-07-16 19:22:37r.david.murraycreate