312207 - Hangs when sending new email with 3 attachments causing message size to exceed server limit

Status: RESOLVED INVALID

(Thunderbird :: Message Compose Window, defect)

Description

[Cecil Carpenter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

TB 1.5b2 hangs when sending attachments.  Problem is intermittent when sending
only one attachment.  Can recreate the problem every time with 3 attachments. 
The attachments are AVI files.

Reproducible: Always

Steps to Reproduce:
1. New Message
2. Some Subject, some text
3. Attach 3 AVI files
4. Send (hangs)

Actual Results:  
TB hangs.  Progress dialog never appears.

Expected Results:  
Progress dialog appears.  Message sent.

Comment 1

[Ray Booysen]

Could you please try creating an SMTP protocol log and substituting SMTP for
"protocol"?

The instructions are here:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp

Comment 2

[Cecil Carpenter]

I get no entries in the log.  Here is my batch file:

SET NSPR_LOG_MODULES=SMTP:5
SET NSPR_LOG_FILE=c:\Temp\thunderbird_log.txt
START "C:\Program Files\Mozilla Thunderbird\thunderbird.exe" "C:\Program
Files\Mozilla Thunderbird\thunderbird.exe"

This is a recap of the session:

1> Execute batch file;
2> Program is opened;
3> New messsage with attachments created;
4> Choose SEND;
5> TB hangs;
6> Check log file;
7> Log file created but empty.

I have tried several levels of reporting (3, 4, and 5) and the results are the
same; empty log file.

Comment 3

[Ray Booysen]

Is it only AVI files or any attachments?

Comment 4

[Cecil Carpenter]

I tried several types of attachments (photos, docs, presentations, etc), and
they all seem to work.  I also tried different file sizes, some small, some
large, mixed, and they all worked.  However, the avi files still hang TB.

Comment 5

[Ray Booysen]

WFM 20051025

It would be really great if we could get a hold of the protocol log. :)

Comment 6

[Cecil Carpenter]

I have a theory as to what happened here.  It seems as if the 3rd attachment pushed the message size over the limit (just barely) of what the ISP allows.  Since the ISP did not know the size until it received the message, TB was attaching the files to the message and sending it.  At some point, the ISP detected the size issue.  When that happened, something was returned to TB to indicate the problem, TB was still processing the message (i.e., had not finished the task), and ...?

To test this, I created a very large file (20 GB).  When I attached it and clicked SEND, TB began processing the message.  After 5 minutes, I cancelled TB.

So, I got TB to hang with 1 very large file attachment.  Still got no entries in the log.  Sorry about the delay, but I am new at this.

Comment 7

[Wayne Mery (:wsmwk)]

closing INVALID