1390442 - After "The mail server responded: Resources temporarily unavailable" error on Yahoo with IMAP message is still copied to sent folder despite not sending

Status: RESOLVED DUPLICATE of bug 780124

(Thunderbird :: Untriaged, defect)

Description

[David Walker]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170810180547

Steps to reproduce:

Composed and send a message with Yahoo IMAP whilst the Yahoo SMTP server is faulty. Reproduced on two systems and accounts on both 55 and 56. 


Actual results:

Recieved message "The mail server responded: Resources temporarily unavailable" but clicking OK copies the message to the sent folder despite not actually being sent. This is extremelly misleading, as cannot tell it has not been sent, except for the error. 


Expected results:

Should return to the compose window and not copy the message to the sent folder like, for example, if you had an incorrect password.

Comment 1

[David Walker]

(In reply to David Walker from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0)
> Gecko/20100101 Firefox/56.0
> Build ID: 20170810180547
> 
> Steps to reproduce:
> 
> Composed and send a message with Yahoo IMAP whilst the Yahoo SMTP server is
> faulty. Reproduced on two systems and accounts on both 55 and 56. 
> 
> 
> Actual results:
> 
> Recieved message "The mail server responded: Resources temporarily
> unavailable" but clicking OK copies the message to the sent folder despite
> not actually being sent. This is extremelly misleading, as cannot tell it
> has not been sent, except for the error. 
> 
> 
> Expected results:
> 
> Should return to the compose window and not copy the message to the sent
> folder like, for example, if you had an incorrect password.

Yahoo SMTP server is now behaving again, so it is not currently possible to reproduce the error message.

Comment 2

[gene smith]

I did put in a bad smtp password while sending. Retried several times by intentionally entering a bad password. Then instead of trying again I clicked cancel. The message goes to Sent folder even though it was never sent. So the example of having an incorrect password doesn't seem to do the right thing either. Just an observation while also looking at bug 1409678. Maybe caused by the same thing as what the reporter of this bug observed.

Comment 3

[gene smith]

I have submitted a patch in Bug 780124 to fix this bug and Bug 1409678. I think these are essentially duplicates of Bug 780124.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to gene smith from comment #3)
> I have submitted a patch in Bug 780124 to fix this bug and Bug 1409678. I
> think these are essentially duplicates of Bug 780124.

In such cases I tend to close the potential dup to the likely root bug, but make it dependent so that if it doesn't actually get fixed then it is then easy for the reporter or someone else to recognize that we should reopen the blocked bug. (That could probably be said more artfully) Purists might not like seeing the dependency, but it works for me.

p.s. it will be fantastic to be fixing some of these longstanding bugs - thanks for your efforts