Shay Rojansky added the comment:
Thanks and no problem for me, the workaround (deleting the header) works just
fine.
I'm not sure if/when the more general discussion on the package will take place
(low-level vs. high-level), I would be interested in foll
New submission from Shay Rojansky :
IMAP IDLE support is not implemented in the current imaplib. A "drop-in"
replacement called imaplib2 exists (), but uses internally managed threads - a
heavy solution that is not always appropriate (e.g. when handling many IMAP
accounts an as
Shay Rojansky added the comment:
Sorry for disappearing, will be following this closer from now on.
Thanks for the responses (and the acknowledgement of a problem), David and
Steffen.
I understand the API design philosophy and the need to allow the production of
invalid messages. The main
Shay Rojansky added the comment:
Sorry, the "print part" below doesn't work on Python3 (I'm back in 2.6), but I
see the same trouble by using part.__str__()
--
___
Python tracker
<http://bug
New submission from Shay Rojansky :
This may be my misunderstanding of the correct behavior, thanks in advance for
your patience...
The issue happens when calling set_charset (or set_payload charset) after a
Message has already been created and contains a Content-Transfer-Encoding
header
