https://bugs.kde.org/show_bug.cgi?id=383131
Jan Kundrát <j...@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |NEEDSINFO --- Comment #3 from Jan Kundrát <j...@kde.org> --- Hi Matthieu, thanks for going through the trouble of debugging this paroblem and providing a patch. Sorry for a late response, I've been on a month-long holiday recently. I won't merge this patch as-is for a bunch of reasons. First of all, I believe that this issue was reported to the Dovecot upstream and fixed in 2010 [1] in all of their by-then maintained branches. Is there any chance of asking your IMAP service provider to upgrade their Dovecot? I find it a little bit worrying that this fix has not made it through whatever distribution/upgrading channels that they are using. I realize that there's only a small chance of success here, but it never hurts to ask. We do not generally carry fixes for stuff like this which has been fixed upstream for ages. Also, as the rest of the thread at [1] suggests, this might need a range of 1 to (2^32)-1 in order to also catch all UIDs that we haven't seen before (please check the RFC7162 if it's correct). That's one more special case which needs to be unit-tested properly. Right now, I do not think that this is something worth the extra effort, but please do comment if you disagree. As a quick fix, you can add "QRESYNC" to the list of blacklisted IMAP capabilities. This effectively reverts to a CONDSTORE-level functionality which is still better than plain RFC3501-like SELECT. Perhaps we need to add some extra-careful infrastructure which automatically enables quirks like this one in case of buggy servers... [1] https://dovecot.org/list/dovecot/2010-August/052025.html -- You are receiving this mail because: You are watching all bug changes.