I have a setup where two computers update the maildir asynchronously and merge the changes via DVCS. For a few weeks now kmail (or akonadi) has been creating thousands of empty messages per day and created error messages saying that some emails could not be deleted. The new messages are named something like lists-and-forums/new/1393578315.R355.fluss (fluss is my hostname, but not the hostname of the computer which actually fetches the mails. the number after R has gone up to 997, but can also be 5. Many of the messages only differ in the number after the R - and they are empty) I guess that it can happen that some mail gets moved by one computer from <maildir>/new to <maildir>/cur while the other computer still sees it in <maildir>/new, giving me a clash in <maildir>/new. Reproducible: Always
I’m currently killing all those empty messages with cd .local/share/mail for i in */*/*; do if ! grep -q @ $i; then echo XXX $i ; rm $i; fi; done
Empty of 1-byte sized? If the latter, could this be the same as https://bugs.kde.org/show_bug.cgi?id=331486 or https://bugs.kde.org/show_bug.cgi?id=319226 ?
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.