Bug 3054 - Mail was not saved because imap server had problems
Summary: Mail was not saved because imap server had problems
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Folders (show other bugs)
Version: 3.9.3
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2014-01-09 01:39 UTC by nin
Modified: 2014-01-09 22:17 UTC (History)
0 users

See Also:


Attachments

Description nin 2014-01-09 01:39:51 UTC
I set the "Save copy of outgoing messages to this folder instead of Sent" option on a folder residing on the imap server. When I sent a reply to a mail in that folder the imap server had problems and claws-mail tried to move the mail a few times but then gave up but did not save the email locally. Losing mails is an inconvenience that I'd like to avoid, so please fix this. Thanks in advance.
Comment 1 Ricardo Mones 2014-01-09 12:50:43 UTC
This is unavoidable if your folders are remote and the server stops working. 

Currently only one "sent" folder per account is supported, so what you're asking is a new feature currently not available, which could be sumarised as "allow a fallback local sent folder when remote sent folder is not available" or "allow a secondary sent folder per account" (could also be useful for local accounts if partition where primary sent folder lives becomes full).

Marking as feature request.
Comment 2 nin 2014-01-09 22:17:10 UTC
I'd like to see at least a big warning window that the server had problems and emails got lost (the window should contain a list which mails were affected). Call it a "feature request" or "bug report", but I consider this to be critical.

Given that the mail was saved locally at first, I think the loss was avoidable by simply keeping the mail were it was (in the queue/draft folder). But this might be discussing semantics. So in any case, please avoid losing mails whenever possible. Even if it is by simply dumping the mail into the log file or something like that.

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