Closed Bug 795529 Opened 12 years ago Closed 12 years ago

When an error occurs sending an email, it closes the composer and adds the email to the Sent folder even though it was not actually sent

Categories

(Thunderbird :: General, defect)

15 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 780124

People

(Reporter: anthony.ciaravalo, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 Build ID: 20120826083223 Steps to reproduce: I have SMTP and IMAP configured for an Exchange Server. The SMTP configuration is STARTTLS, normal password and port 465. The IMAP configuration is SSL/TLS, normal password and port 993. Sometimes I get the following error when I send an email "An error occurred while sending mail. The mail server responded: 4.4.2 Message submission rate for this client has exceeded the configured limit. Please verify that your email address is correct in your Mail preferences and try again." Actual results: When I get the error, the composer window is closed and the email is added to the Sent folder on the Exchange Server, even though it is never delivered. When it happens I have to go into the Sent folder to copy it and either create another new email or reply again to the incoming email and paste my message. Expected results: The email should not have been placed into the Sent folder and the composer window probably should remain open to try sending again and not be forced to create another new email or reply again to the incoming email and copy/paste my message from the previous attempt.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
I frequently receive this error in my laptop at work when I send an email. However, at home: the same Exchange account (through IMAP), same operating system (Windows 7 x64) and same Seamonkey version 2.13, but this error doesn't happen here at home. I don't understand the reason, what's happening it in my laptop at work and not in my pc at home, maybe the intranet environment?
You need to log in before you can comment on or make changes to this bug.