➜

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 spaetz
Recipients lavajoe, spaetz
Date 2011-01-27.15:43:51
SpamBayes Score 9.148044e-10
Marked as misclassified No
Message-id <1296143032.31.0.170546466388.issue11024@psf.upfronthosting.co.za>
In-reply-to
Content 
I think I found the issue he mentioned, however it was about the functions taking the local time (rather than UTC), which is fine.

The problem is that Time2Internaldate is used for every .append() operation internally, producing invalid dates which are handed to the IMAP server. So in most cases, the IMAP server will silently ignore the time and use the current time (as per IMAP RFC) or it will complain and barf out (as the MS Exchange server rightly does.

So this is more than just an inconvenience, it outright prevents intenational users from APPENDing new messages to a server (or silently bodges the message date) as there is no way around using that function...

Sorry if this sounds like whining :-) I don't even have a patch handy...
History
Date User Action Args
2011-01-27 15:43:52spaetzsetrecipients: + spaetz, lavajoe
2011-01-27 15:43:52spaetzsetmessageid: <1296143032.31.0.170546466388.issue11024@psf.upfronthosting.co.za>
2011-01-27 15:43:51spaetzlinkissue11024 messages
2011-01-27 15:43:51spaetzcreate