Bug 290311 - Archiving folders is not robust
Summary: Archiving folders is not robust
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-01 12:01 UTC by Christoph Bartoschek
Modified: 2017-01-07 22:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Bartoschek 2012-01-01 12:01:46 UTC
Version:           4.8 (using Devel) 
OS:                Linux

If there is a network glitch during archiving folders from an IMAP server the operation is aborted. This makes it nearly impossible to archive large folder structures. Even the connection to google mail is sometimes disconnected. In such a situation archiving should resume the operation or give the user the time to fix the network connection and then allow resuming of the operation.

There are other reasons to be more robust:
- DSL connections are often disconnected by the providers once a day
- Mobile connections are extremely unreliable and often have to be resetted.

Reproducible: Always

Steps to Reproduce:
Try to archive 8 GiB of mails from an IMAP-Server and then simulate a network connection failure.

Actual Results:  
Archiving is aborted.

Expected Results:  
An option to resume the operation after the network has been restored.
Comment 1 Denis Kurz 2016-09-24 18:08:06 UTC
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.
Comment 2 Denis Kurz 2017-01-07 22:28:45 UTC
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.