Closed Bug 619809 Opened 15 years ago Closed 14 years ago

Large File Attachment mail will not send

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: curtis.egan, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2; .NET4.0C; .NET4.0E) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 OracleBeehiveExtension/1.0.0.2-OracleInternal ObetStats/CAT_1291216107962-554698530 Thunderbird/3.1.7 Mozilla Thunderbird 3.1.7 (just upgraded and still occures) Sending a mail with larger Attachment has much difficulties. Any attachement larger then 500k to 3 Meg will have difficulties sending. I definatly cannot send any email larger then 2 Meg and 1 Meg file will send about 1 in 5 tries. If mail is sent then it likely will not save to the SENT directory after delivery. Reproducible: Always Steps to Reproduce: 1.Email, attach file, increase the attached files size until occures 2.Send email......repeat until it works 3. then wait...Delivering mail... (does not go away) Actual Results: Email never completes and likely hangs the program. Need to restart Expected Results: Two things should occure 1) Email delivers 2) The sent email is placed into the sent folder help
(In reply to comment #0) > Actual Results: > Email never completes and likely hangs the program. Need to restart Do you call phenomenon like "wait of Tb" by "hang"? (CPU 0% by Tb) Do you call phenomenon like "loop of Tb" by "hang"? (CPU 100% by Tb) With SSL? Non SSL? Both SMTP server of SSL and Non SSL? > Mozilla Thunderbird 3.1.7 (just upgraded and still occures) When did your problem start to occur? From prevous Tb 3.1.5 or former Tb 3.1.x? From Tb 3.0.x? From Tb 2.x? Similar phenomenon to bugs listed in Dependency tree for Bug 538283 and Bug 538283 itsel?
If similar phenomenon, is you problem reproduced with network.tcp.sendbuffer=4096 and network.tcp.sendbuffer=65536?
insufficient information
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.