Sometimes, kmail does not store or update messages on the IMAP server. Namely, often when I compose and submit a message, it is saved to sent-mail folder in the local akonadi database, but does not actually appear on the server (verified using other clients such as webmail). In the akonadi database, the message then has no ‘Remote ID’ (which I guess corresponds with its IMAP UID). The workaround I use is to move it to another account and back. Also, flag updates such as marking \SEEN is not propagated to the server. The workaround I use is to unmark \SEEN and mark \SEEN again. This does not happen with all accounts, but specifically with accounts on a Dovecot server. So it may be a server bug (unlikely, as other clients do not have this problem) or a bug triggered in the interaction with this server's specific set of capabilities: IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE QUOTA In any case, whatever the reason, for the case that the message is not actually submitted to the server, kmail (or the responsible backend) has enough information to just resubmit, because it needs to fill in the ‘Remote ID’/IMAP UID. For the flag change, modseqs could be used to check. Reproducible: Always
Related: Bug 360834
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!