[issue18921] In imaplib, cached capabilities may be out of date after login

2018-07-19 Thread STINNER Victor
STINNER Victor added the comment: See also bpo-33327: Add a method to move messages to IMAPlib. -- nosy: +vstinner ___ Python tracker ___

[issue18921] In imaplib, cached capabilities may be out of date after login

2018-04-21 Thread Matej Cepl
Matej Cepl added the comment: Well, and would it be too much to refresh capabilities attribute in the end of login method? -- nosy: +mcepl ___ Python tracker

[issue18921] In imaplib, cached capabilities may be out of date after login

2014-12-30 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- versions: +Python 3.5 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18921 ___ ___

[issue18921] In imaplib, cached capabilities may be out of date after login

2013-09-04 Thread Steven Murdoch
New submission from Steven Murdoch: When an IMAP server is behind a proxy, the proxy's capabilities may differ from that of the actual IMAP server. However, in Python imaplib, the client will ignore any updates to available capabilities in the response to the LOGIN command (see rfc3501,

[issue18921] In imaplib, cached capabilities may be out of date after login

2013-09-04 Thread R. David Murray
R. David Murray added the comment: I agree that this would be a good idea, but it is not a bug in the current implementation. The only place imaplib itself uses the cached capabilities is *before* login, in the starttls method, and there it refreshes it after starttls succeeds. Although it