Bug 334740 - kmail doesn't handle failed archiving attempts well.
Summary: kmail doesn't handle failed archiving attempts well.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: misc (show other bugs)
Version: 4.13.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-05-14 09:08 UTC by qqqqqqqqq9
Modified: 2018-10-27 04:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description qqqqqqqqq9 2014-05-14 09:08:48 UTC
Be the archiving interval 7 days.
When archiving fails the following happens:

1. A corrupted archive is produced.
2. The archiving status is set do done
3. The next archiving will be started in 7 days.
4. What will happen if the maximum number of kept archives is 1? Will kmail discard the good one and keep the corrupted?

A better handling would be:

1. Delete the corrupted archive
2. Retry after sometime (e.g. 3 h)
 

Reproducible: Didn't try
Comment 1 Laurent Montel 2014-05-14 17:26:11 UTC
"When archiving fails the following happens:" why ? How do you produce it ?
Comment 2 Laurent Montel 2014-05-16 09:40:38 UTC
wait for infos
Comment 3 qqqqqqqqq9 2014-06-12 15:29:37 UTC
I don't know why the archiving failed, i have not been able to reproduce it.
All I do know is that kontact kept a corrupt archive and went on as if archiving has been successful (Besides a small error message).
Comment 4 Andrew Crouthamel 2018-09-25 03:31:45 UTC
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 set the bug status 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!
Comment 5 Andrew Crouthamel 2018-10-27 04:10:21 UTC
Dear Bug Submitter,

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!