[issue5146] threading via uid method doesn't work in imaplib

Georg Brandl added the comment: Some research into IMAP commands confirms that this change is correct. Done so in r83374. -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5146] threading via uid method doesn't work in imaplib

R. David Murray added the comment: A test suite skeleton was recently contributed; it's in the standard location (Lib/test/test_imaplib). -- nosy: +r.david.murray stage: needs patch -> unit test needed ___ Python tracker

[issue5146] threading via uid method doesn't work in imaplib

Terry J. Reedy added the comment: I confirmed that 3.1.2 has same 'old' text that the OP proposes to change. I cannot comment on the substance. Stage 'needs patch' means it needs a diff file. I do not know whether or how the imaplib is unit tested. -- keywords: +easy nosy: +tjreedy st

[issue5146] threading via uid method doesn't work in imaplib

Piers Lauder added the comment: I agree with this change. It should be propagated to all versions. ___ Python tracker ___ ___ Python-bugs-list

[issue5146] threading via uid method doesn't work in imaplib

New submission from abhishek : Hi, IMAP commands in general can be either called directly or via the UID command which basically returns the UIDs instead of message IDs. Consider this example: 02:23.02 > GDJB3 UID THREAD references UTF-8 (SEEN) 02:23.02 < * THREAD (3)(2)(4)(1) 02:23.02