935439 - SeaMonkey-2.21: message lost upon sending with IMAP "server busy" errors

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[sphakka]

I have two IMAP accounts with the same server, so I guess this generates a fairly amount of "stress" on the server. Indeed, I sometimes experience a "Server busy" error when sending messages. Not too annoying, but the problem is that the message being sent is *lost*: I can see old copies in the "Draft" folder, but the last version is not there!
Of course, being the server busy it might be really impossible to save it over there, so I tried to look in any of the "Local Folders", but... nada :-(

Thus, I suggest, on such kind of connection problems, to save the message in a local folder and pop an appropriate message.

(I use SeaMonkey-2.21, build 20131105182914)

Comment 1

[WADA:World Anti-bad-Duping Agency]

> I sometimes experience a "Server busy" error when sending messages.

When(at what timing) does the "Server busy" error happen when you try to send a message?
Is the "sent mail" actually delivered to recipint(s) of the mail after the "Server busy" error?
Same problem as bug 780124?

Anyway, get SMTP log and check log file content using Text Editor by yourself, after reading that bug well, please.

Comment 2

[sphakka]

(In reply to WADA from comment #1)
> When(at what timing) does the "Server busy" error happen when you try to
> send a message?

Mmh, not sure: possibly as soon as SM try to connect after it gets a 'Ctrl+Enter'. I'll take note next time I see it.

> Is the "sent mail" actually delivered to recipint(s) of the mail after the
> "Server busy" error?

Apparently not, but I'll check explicitly when it happens again.

> Same problem as bug 780124?

Similar, with the difference that I don't get the latest version of the (unsent?) mail saved in "Draft", though older auto-saved copies are there... better than nothing ;-) But actually nothing is saved in "Sent" -- those are all IMAP folders on gmail.

> Anyway, get SMTP log and check log file content using Text Editor by
> yourself, after reading that bug well, please.

Thanks for the tip. I instrumented SM-2.22 (upgraded in the meanwhile) and let you know as soon as I get something useful.

Comment 3

[Wayne Mery (:wsmwk)]

sphakka

Do you still see this issue?

Comment 4

[sphakka]

Never seen again. I guess this can be closed.

Comment 5

[Wayne Mery (:wsmwk)]

Thanks for the update