i am trying the automatic archiving features of kmail, which most of the time work great. but since a few days, kmail is not able to archive my local folders any more -- it crashes at 1,4 GB, leaving an unfinished archive. over the past months, it always successfully created archive files of about 2,2 GB. there's no issue with disk space -- archiving two IMAP accounts to the same file system keeps working. Reproducible: Always Steps to Reproduce: 1. set up automatic mail archives of your local mail folders (here: every two months) 2. wait for it to crash Actual Results: the agent crashes at 1,4 GB. sometimes it tries again after a few minutes, crashing again. a vicious circle. Expected Results: the archiving should finish successfully. i ran fsck on the file system and found no problems, maybe there's something wrong with akonadis bookkeeping of the local folders. some hints on how to gether more information on this (e.g., find out whether there's a certain message causing this) would be great!
i narrowed it down, by manually archiving one subfolder after the other (archiving all local folders at once crashed kmail completely): as it turns out, a "phantom mail" in the local outbox seems to be the problem. when i try to archive the outbox, kmail crashes immediately. i could successfully archive all other subfolders. in kmail, the outbox looks empty, but the mouseover context menu lists 1 message with 5,5KB size. i noticed for some time now, that messages in the outbox are not automatically removed after they were sent, kmail then shows one unread mail, until i choose the outbox folder -- it is empty, the unread notice disappears. how can i fix my outbox? btw, i also noticed several greyed out messages in one local folder -- how can these messages be retrieved?
i've now upgraded to KF5 (5.23, plasma 5.6), and the bug is still present. it's impossible for me to backup local folders because the backup agend crashes.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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!