Terry J. Reedy added the comment:
Since I wrote this, a new method has been added to the IMAP4 class
(starttls(ssl_context=None), 3.2) and a new parameter to the IMAP_SSL subclass
initialization (3.3). So the module is not dead.
Thomas is correct that a new method or, more likely, module util
Thomas Fenzl added the comment:
that change would require a new interface.
Since there is a drop-in threaded implementation of imaplib (imaplib2) and a
higher-level wrapper (imapclient) which uses imaplib2 if available and falls
back to imaplib if not, I think it is better to fully revise the
Terry J. Reedy added the comment:
While IMAP is very much a live protocol, I do not know that any of the
currently active core developers know much about it. Imaplib is based on the
obsolete RFC2060 of Dev 1996, superseded by 3501 in March 2003, with 6 later
updates. (I just found all this ou
New submission from Branden Moore :
IMAP Literals are a tricky subject. Currently, if IMAP returns:
* text text text {5}\r\n
12345more text
imaplib will return 2 data items:
[("text text text {5}", '12345'), "more text"]
This forces users of imaplib to then parse out and remove the '{5}' from
