bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Email fails to send due to invalid email address formerly valid. Alert states message size exceeds temporary size limit of server

RESOLVED INCOMPLETE

Status

Thunderbird
Untriaged
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: gaalrayn, Unassigned)

Tracking

38 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [dupeme])

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8648545 [details]
Screen shot of Alert message

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150806001005

Steps to reproduce:

Sent an email with an email address that was previously valid but is no longer valid. Always reproducible regardless whether sent alone, with others, in list, as To, as cc, or as bcc. It did NOT occur with a known spurious address, which sent but which bounced back later.

As to my list (with only 29 names), the 213 character email without attachments sent as soon as the offending email was removed.

I changed smtp's, and obtained the same results using both smtp.integra.net and smtpout.secureserver.net (goDaddy).


Actual results:

Immediately upon clicking send, the following popup "Alert" appeared: "The size of the message you are trying to send exceeds a temporary size limit of the server. The message was not sent; try to reduce the message size or wait some time and try again. The server responded:  ... temporary failure."


Expected results:

The email should have sent.

There is some similar discussion of similar error messages that seem to be caused by the same problem in Bug 197134 (See Comment 8 for excellent suggestions) and Bug 300937. But the problem remains.

Comment 1

2 years ago
(In reply to gaalrayn from comment #0)
> ... 
> There is some similar discussion of similar error messages that seem to be
> caused by the same problem in Bug 197134 (See Comment 8 for excellent
> suggestions) and Bug 300937. But the problem remains.

how is your situation different not a match of one of those?
Flags: needinfo?(gaalrayn)
Whiteboard: [closeme 2016-10-15][dupeme]

Comment 2

2 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(gaalrayn)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-10-15][dupeme] → [dupeme]
You need to log in before you can comment on or make changes to this bug.