https://bugs.kde.org/show_bug.cgi?id=392440
--- Comment #1 from Erik Quaeghebeur <k...@equaeghe.nospammail.net> --- It happened again today: 15:23:11.1691 ThreadingMsgListModel for INBOX ThreadingMsgListModel::wantThreading: THREAD contains info about UID 30512 (or higher), mailbox has 30512 15:23:11.1711 [task] Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_WAIT_FOR_CONN INBOX Activated 15:23:11.1721 [task] conn Opening mailbox... 15:23:11.1781 [sync] Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX Synchronizing mailbox 15:23:11.1861 >>> y11 SELECT INBOX (QRESYNC (1164751602 953107 (3,5 30494,30512))) 15:23:11.2811 <<< * 5 EXISTS 15:23:11.2811 <<< * 0 RECENT 15:23:11.2811 <<< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen […]) 15:23:11.2811 <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen […] \*)] Ok 15:23:11.2811 <<< * OK [UNSEEN 4] Ok 15:23:11.2821 <<< * OK [UIDVALIDITY 1164751602] Ok 15:23:11.2821 <<< * OK [UIDNEXT 30515] Ok 15:23:11.2821 <<< * OK [HIGHESTMODSEQ 953323] Ok 15:23:11.2821 <<< * OK [URLMECH INTERNAL] Ok 15:23:11.2821 <<< * OK [ANNOTATIONS 65536] Ok 15:23:11.2821 <<< * 4 FETCH (FLAGS ($X-ME-Annot-2 $IsMailingList) UID 30513 MODSEQ (953162)) 15:23:11.2821 <<< * 5 FETCH (FLAGS ($X-ME-Annot-2) UID 30514 MODSEQ (953322)) 15:23:11.2821 <<< y11 OK [READ-WRITE] Completed 15:23:11.2831 Warning: unhandled untagged OK with a response code 15:23:11.2831 Warning: unhandled untagged OK with a response code 15:23:11.2831 [task] Imap::Mailbox::KeepMailboxOpenTask attached to INBOX Failed: The connection is being killed for unspecified reason 15:23:11.2831 [task] Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX Failed: The connection is being killed for unspecified reason 15:23:11.2831 >>> *** Connection killed. 15:23:11.2831 [err] MailboxException FETCH response: UID consistency error for message #4 -- expected UID 30511, got UID 30513␍␊FETCH 4 ( FLAGS "$X-ME-Annot-2 $IsMailingList" MODSEQ "953162" UID "30513") I guess this is an upstream (FastMail) issue. I'll point them to this bug report. -- You are receiving this mail because: You are watching all bug changes.
