Bug 386010

Summary:	KMail2 fails to archive folder
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Thorsten Otto <admin>
Component:	Archive Mail Agent	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	grave
Priority:	NOR
Version:	5.6.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thorsten Otto 2017-10-21 06:10:49 UTC

While trying to archive a folder within KMail2, i get an error message:

Failed to archive the folder 'xxx'. Downloading a message in folder 'xxx' failed.

i'm not complaining about why that happens, but i'm complaining about the behaviour of KMail2 here. Firstly, aborting the whole operation only because a single message could not be accessed is absolutely catastrophic for a feature that  is primarly used to backup mails, or to transfer them to a different location. Aborting that renders the whole folder unusable. Secondly, it does not give *any* hint about which message could not be accessed. Maybe the problem could be solved by just deleting that single message, but i get no clue which one.

It would be nice it that error behaviour could be improved.

Comment 1 Thorsten Otto 2020-01-25 15:39:18 UTC

Reported more than 2 years ago, the bug still persists, and no comment at all?

Comment 2 Christophe Marin 2020-01-26 09:38:25 UTC

Did you identify the message?

Comment 3 Thorsten Otto 2020-01-26 12:00:21 UTC

As already noted, in the GUI i don't get any hint about which message was involved. IIRC it had something to do with duplicate mails, and one of them being rejected. All i can see in the journal log is:

ItemRetrievalJob for request 0x7f20c007f210 finished with error: "Unable to retrieve item from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify item 13106 () (in collection 17) with dirty payload, aborting STORE.

But that is not the main problem. I could live with the fact that single mails would be skipped during archiving, especially if they are really duplicates. But i cannot live with the fact that the whole archiving process is aborted, leaving a truncated & damaged archive behind.

Comment 4 Christophe Marin 2020-01-27 09:11:20 UTC

So, you had 2 years to try moving messages in other folders and test in order to provide useful information that would help identify the issue but didn't do anything, and only 2 years later you mention the error you're seeing when trying to reproduce.

That's like calling your doctor to tell you're ill without mentioning any symptom.

Comment 5 Thorsten Otto 2020-01-27 12:30:55 UTC

And why did nobody ask for missing information 2 years ago?

And you still don't get the point. Its not about why some mail cannot be retrieved. Its about that the archiving process is completely aborted. That makes it impossible to get at least some kind of backup.