Version: 2.0.96 (using KDE 4.6.3) OS: Linux I have set-up "i" as shortcut for marking a group as "ignore". Often if I click on the first message in a group and "i" immediately afterward I get an akonadi conflict regarding the status of the message, i.e. whether it should have no status, or $IGNORED. Another variant is the conflict of $IGNORED and $SEEN. I think this is because kmail does not sync quick enough and thus confuses akonadi. If this is not a kmail2 but akonadi issue, please re-assign. Reproducible: Sometimes
Same happens if one deletes an email (to a local folder) while kmail is still retrieving its content.
Another way to trigger this is to filter imap messages to a local folder where the thread they belong to is marked as "ignored". One opens the local folder with the ignored thread. Tells kontact to go offline/online. It starts to pull new messages for the imap account It filters the messages to the local folder and puts the email that belongs to the ignored thread into it and marks it as ignored (this fails sometimes, then the conflict does not occur) The email is added to the thread and marked as ignored and a pop-up comes up which compares an empty version with the actual email on the right-hand side. No other clients accessing the imap account.
Can you reproduce with KDEPIM 4.7.2 or even better, with master?
akonadi-4.7.2-298.1.x86_64 akonadi-runtime-1.6.2-103.1.x86_64 libakonadi4-4.7.2-247.1.x86_64 libakonadiprotocolinternals1-1.6.2-103.1.x86_64 libakonadi4-debuginfo-4.7.2-247.1.x86_64 libakonadiprotocolinternals-devel-1.6.2-103.1.x86_64 and KDE 4.7.2 and it still happens, i.e. if one presses the shorcut for "ignore group" before kmail2 finishes to retrieve and display an emails content the conflict happens.
Still valid for kdepim 4.8. If one marks an email as ignored/spam while it is downloaded it will cause a conflict. See attached screenshot.
Created attachment 68533 [details] conflict after clicking on "mark as spam" button in the toolbar while email was not loaded yet
*** This bug has been marked as a duplicate of bug 259574 ***