https://bugs.kde.org/show_bug.cgi?id=364506
--- Comment #3 from Jan Kundrát <j...@kde.org> --- > Well, this is not my server, I just have an account there. So a definite no > from my end, and an assumed no for the other side. OK, let's assume that they would have informed you if they, e.g., recovered from a little bit outdated backup. Do you know what Dovecot version they run? IMAP -> Debugging -> IMAP Server Information... might help in case they modified the default settings of not specifying the version info. > Ok, I'll do that in a private mail. This is what Trojita has cached for its UID map: (781, 1163, 1254, 1255, 1256, 1257, 1258, 1259, 1260, 1386, 1387, 1520, 1572, 1598, 1601, 1602, 1605, 1606) And SyncState has the following: UIDVALIDITY 1370200160 UIDNEXT 1607 EXISTS 18 HIGHESTMODSEQ 8340 The IMAP log says that: > y4 SELECT INBOX (QRESYNC (1370200160 8340 (10,15,18 1386,1601,1606))) < ... < * 11 EXISTS < * 0 RECENT < * OK [UIDVALIDITY 1370200160] UIDs valid < * OK [UIDNEXT 1645] Predicted next UID < * OK [HIGHESTMODSEQ 8517] Highest < * VANISHED (EARLIER) 1520,1629:1634,1636:1638,1640:1644 < * 10 FETCH (MODSEQ (8474) UID 1635 ...) < * 11 FETCH (MODSEQ (8509) UID 1639 ...) > ... Trojita is telling the IMAP server that message #10 (counting starts from 1, not 0) has UID 1386. Dovecot says that the oldest removed message had UID 1520, but that's > 1386, which means that first 10 messages must have remained unchanged. Trojita detects this error and disconnects. There are two possibilities: a) There's a grave bug in Trojita which caused UID mapping and HIGHESTMODSEQ to come out-of-sync. b) There's a bug in (your version of) Dovecot doing essentially the same. It also looks as if Dovecot was not looking at the client-provided list of known seq-UIDs and taking a shortcut through HIGHESTMODSEQ in this case. -- You are receiving this mail because: You are watching all bug changes.
