Bug 4206 - Unreliable mbox export, frequently fails to export messages
Summary: Unreliable mbox export, frequently fails to export messages
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (Windows)
Classification: Unclassified
Component: default (show other bugs)
Version: 3.17.3
Hardware: PC Windows 7
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2019-05-04 02:25 UTC by Mike
Modified: 2019-05-17 12:57 UTC (History)
0 users

See Also:


Attachments

Description Mike 2019-05-04 02:25:38 UTC
The mbox export often fails. It sometimes exports nothing at all, even after the export has appeared to succeed (no error messages).
Comment 1 Andrej Kacian 2019-05-04 02:56:25 UTC
Is there any text output shown if you run Claws Mail from a terminal and do the export that fails?

Does the export always fail when exporting certain message(s) and/or folder, or does it seem random? It would help if we had a way to reliably reproduce this failure. I tried exporting several full folders, as well as randomly chosen individual messages, and it always seems to work for me.
Comment 2 Mike 2019-05-04 14:18:12 UTC
Thank you for the reply. I am on Windows and so have never run Claws Mail from a terminal-- not even sure how that works with Claws Mail, whether there is a command line to export mailboxes, etc.

So far, the problem seems random but frequent, except to say that I can never seem to export more than about 500 messages, but the exact number might be 504, 507, etc. at times. In some cases, it is zero. Error messages never appear. During the export process, my computer's drive indicator light is active, and several seconds do pass. My mailbox has about 7,000 messages.

Sorry I do not have more details. Based on some frustrations with a few things, I have switched clients to Sylpheed for now-- has limitations of its own!-- but perhaps I will eventually switch back.
Comment 3 Ricardo Mones 2019-05-17 12:57:01 UTC
Closing as there's no enough information to reproduce this.

When you have more info feel free to reopen this bug with the steps o conditions required to trigger it reliably.

Note You need to log in before you can comment on or make changes to this bug.