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.14:07:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405519645.76.0.742545975205.issue21815@psf.upfronthosting.co.za>
In-reply-to
Content
Just to make sure I understand: the issue is that gmail may produce flags with [] in them, and imaplib currently fails to process such flags when it receives them from gmail?  

In principle I think we would not want to allow imaplib to be used to create such flags unless the user specifies some sort of "I want to violate the RFC" flag (which they might want to do, for example, to run tests against gmail :)  But currently it looks like it can?  (I haven't looked at this in enough detail to be sure.)  If that's true we probably have to continue to allow it for backward compatibility reasons, but we should document the RFC violation and possible consequences (an IMAP server rejecting such flags).
History
Date User Action Args
2014-07-16 14:07:25r.david.murraysetrecipients: + r.david.murray, barry, ezio.melotti, jesstess, Lita.Cho, rafales
2014-07-16 14:07:25r.david.murraysetmessageid: <1405519645.76.0.742545975205.issue21815@psf.upfronthosting.co.za>
2014-07-16 14:07:25r.david.murraylinkissue21815 messages
2014-07-16 14:07:25r.david.murraycreate