1343858 - sent mail disappears when it can't be saved to IMAP-sent-folder

Status: RESOLVED DUPLICATE of bug 28211

(SeaMonkey :: MailNews: General, defect)

Description

[Flex]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 SeaMonkey/2.44a2
Build ID: 20160405015332

Steps to reproduce:

1. I composed and sent a mail.

2. It seems that the mail was sent, however I got the error message "Failed so save mail into sent folder. Try again? (Yes/Cancel)"
(I was using an IMAP-account. I don't know why the IMAP-connection failed, but for reproducing this error it works if you change your IMAP-username to some invalid data, so that the connection fails while you still have your valid data for the SMTP-connection.)

3. Click on cancel.

Switched Seamonkey to Offline Mode and composed a mail. (Mail was in local sendbox).
2. Switched back to 


Actual results:

They mail will be sent, but the sent mail will be gone. It won't be either in your IMAP sent box nor in your local sent box. It's gone.


Expected results:

I think the mail should at least be in your local sent box in that case.

(I like to use the offline-,ode sometimes, in that case your mail will be in your local outgoing-box before you go online - however the bug is not related to the offline-mode, i also tried without offline mode).

Comment 1

[Rainer Bielefeld]

This one might be related to or DUP of "Bug 1263863 - Thunderbird loses email when IMAP save after send fails"

@reporter:
your opinion? Please see Bug 1263863 comment #24 and Bug 1263863 comment #24

Comment 2

[Frank-Rainer Grahl (:frg)]

Iappened to me too once and I would set it to new but SeaMonkey/2.44a2 Build ID: 20160405015332 is clearly an old unsupported version so until someone confirms it with 2.46+ I would treat it as unconfirmed. Also 2.49 fixes some threading problems in imap and it might no longer be reproducable there.

The other bugs ar for Thunderbird but I believe they might have a root cause in shared mailnews code.

FRG

Comment 3

[Flex]

I can confirm it with 2.46 which is the latest version offered on the official Seamonkey websites.

Comment 4

[Rainer Bielefeld]

NEW due FRG's confirmatin an Bug 1263863 comment #24, but probably DUP

Version = Trunk because due to Bug 28211 the problem has been existing forever (more or less).

Comment 5

[Jorg K (CEST = GMT+2)]

Should be fixed by bug 28211/bug 1366591. If not, please reopen.

Comment 6

[Flex]

I still have this in 2.49.1.

Comment 7

[Jorg K (CEST = GMT+2)]

Yes, the fix landed today, so it will be in SM 2.53.