update version
bug fix for imaplib3 from Mathias Ball
On Sun, Mar 05, 2017 at 01:09:52AM +0000, Piers Lauder wrote: Ok, I agree imaplib...
Thank you!
binascii.Error: Incorrect padding
Fixed in versions 2.57 / 3.05
Fix for bug #11 binascii.Error: Incorrect padding
binascii.Error: Incorrect padding
Ok, I agree imaplib should be kind to bad implementations of the RFC in this case,...
I have also encountered this same problem with a major UK isp. Experience shows that...
Add "enable" command, and fix typo in imaplib3 ...
binascii.Error: Incorrect padding
Hi, While the response "go ahead" is normal for "continuation" responses, in the...
binascii.Error: Incorrect padding
Added ENABLE command for UTF8=ACCEPT capability...
new version with ENABLE command.
Update version
Remove irrelevant py3 comment
Remove irrelevant py3 comment
Add "InternalDate" to __all__
added Mon2num, MonthNames to __all__
new version of imaplib2.py
Removed unnecessary ".encode" from Mon2num setu...
Back out BINARY changes - not implemented corre...
Back out BINARY changes - not implemented corre...
Suggested fix accepted and installed. Thanks!
Use BINARY if capability available
New versions.
Added test for BINARY mode on server, and use i...
Added test for BINARY mode on send, and use if ...
Thanks for the fix. Will incoporate shortly...
Use BINARY if capability available
Fix for shutown exception by Sebastien Gross
Fix version number.
Minor improvement to an error message.
BETA release of version of imaplib2 converted f...
Various minor fixes.
Fix tabs to spaces, allow for "ssl3" not being ...
Fixed placement of new tls_level arg description.
Add support for TLS levels by Ben Boeckel <math...
Can't interrupt IDLE with Control-C
Thanks. Works. New version uploaded.
Fix to allow interruptible IDLE command
(oops... sorry... that patch was backwards. I hope you get the idea)
Here ya go! :D diff --git a/imaplib2.py b/imaplib2.py index 6641741..4fd04e6 100755...
Can't interrupt IDLE with Control-C
I have duplicated your result, so yes, please submit your two line patch! (just lines...
It appears that this is still an issue when using Python-2.x (at least with the python...
Make that "-i" instead of "-t"... but, you get the idea. :D
It appears that this is still an issue when using Python-2.x (at least with the python...
except .. as <var> clauses cause UnboundLocalError if <var> is global
Fixed in version 2.47
New version.
Fix for correct Python 3 exception handling by ...
except .. as <var> clauses cause UnboundLocalError if <var> is global
better minimal example
setup for PyPi
new version
Further improve example code.
Amend python 3 compatibility changes.
Improve example.
Fix example to match description for 'fetch'.
Change example to one that displays messages co...
Update version
Truncate data parts of debug output to avoid ve...
remove query comment (resolved)
Make example at end python3 compatible, and add...
Update to 2.44
Fix for correct byte encoding for _CRAM_MD5_AUT...
Fix for null appends to untagged responses afte...
Excellent! Glad that worked, and thanks for another bug fix!
untagged responses: an empty string is added when a literal is received
The updated patch is attached, it fixes my test case.
Thanks for yet another bug detection! However, that change breaks other responses...
untagged responses: an empty string is added when a literal is received
untagged responses: an empty string is added when a literal is received
Fix for untagged responses handling when using ...
new version
examine and select commands don't flush untagged responses
That's good to know! And thanks for your very helpful discussion. And you are right...
Your patch fixes the problem, thanks ! In the previous commit, should not we use:...
Ah, serious bug. I was processing the append_untagged for the command completion...
log.imaplib2: logs of imaplib2 using debug=5 (see lines 2063/2082) dump.imap: stream...
Can you generate a log showing the error? call IMAP4() with debug=5, and upload the...
The readonly error still occurs with 2.41. It seems that an untagged response is...
Ignore the above. The callbacks in your code mean that the flush of the untagged...
Just to clarify, the code before EXAMINE/SELECT commands should be: for typ,dat in...
new version
Change code to replect documented behaviour for...
Hmmm. Instead of changing the doc to match the code, I'm now in favour of changing...
These modifications fix the problem encountered with attached test.py but the read-only...
New version.
Fix for READ-ONLY error after multiple EXAMINE/...
examine and select commands don't flush untagged responses
and thanks for the bug report and the other patches!
The code at the top of the select method is clearly wrong in the case where the same...