Closed Bug 500234 Opened 15 years ago Closed 15 years ago

Thunderbird crashes every time when sending email with attachment, no report given nor is the email saved anywhere.

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: susan, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, stackwanted, Whiteboard: closeme 2009-12-01)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11 Build Identifier: version 2.0.0.22 (20090605) This is becoming very tiresome. Since I've updated to the latest version I have not been able to send email with attachments. This is unacceptable because I need to send my clients a proof of their designs. The pdfs that I send are .5 - 2MB. Anything larger I try to send in multiple emails. I've tried uninstalling and reinstalling... Disabling add-ons (they are still disabled)... Sending when it asks for a password... Sending without a password... No matter what I do, Thunderbird quits while sending email with attachment(s) without warning and without producing an error. Also the email I am trying to send disappears. Sending email with no attachment works fine. Reproducible: Always Steps to Reproduce: 1. new email 2. add address 3. subject line 4. brief message 5. add pdf 6. send Actual Results: It crashes/quits (usually around 30% complete) No warnings Expected Results: It should have sent the email.
Perchance, could you get us an SMTP log (see <https://wiki.mozilla.org/MailNews:Logging>) of when you send the attachment? Also, what server installation (e.g., Exchange) are you using? xref bug 497985 for why I'm interested.
Bug 497985 does look similar. Microsoft Windows Server 2003 R2 SE SP2 Here's the log of a test I tried to send today: 0[353b0]: SMTP Connecting to: mail.yournewgcp.com 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 220-alpha.whbdns.com ESMTP Exim 4.69 #1 Thu, 25 Jun 2009 22:29:51 +0000 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 220-We do not authorize the use of this system to transport unsolicited, 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 220 and/or bulk e-mail. 0[353b0]: SMTP entering state: 15 0[353b0]: SMTP Send: EHLO [192.168.1.142] 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250-alpha.whbdns.com Hello [192.168.1.142] [69.89.210.229] 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250-SIZE 52428800 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250-PIPELINING 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250-AUTH PLAIN LOGIN 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250-STARTTLS 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250 HELP 0[353b0]: SMTP entering state: 4 0[353b0]: SMTP entering state: 22 0[353b0]: SMTP entering state: 17 0[353b0]: Logging suppressed for this command (it probably contained authentication information) 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 235 Authentication succeeded 0[353b0]: SMTP entering state: 19 0[353b0]: SMTP entering state: 3 0[353b0]: SMTP Send: MAIL FROM:<susan@yournewgcp.com> SIZE=2881976 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250 OK 0[353b0]: SMTP entering state: 6 0[353b0]: SMTP Send: RCPT TO:<susan@tchoup.com> 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 250 Accepted 0[353b0]: SMTP entering state: 7 0[353b0]: SMTP Send: DATA 0[353b0]: SMTP entering state: 0 0[353b0]: SMTP Response: 354 Enter message, ending with "." on a line by itself 0[353b0]: SMTP entering state: 8 0[353b0]: SMTP entering state: 9
We need the talkback crash ids for the crash, so make sure that's installed/enabled. (See http://kb.mozillazine.org/Talkback)
Keywords: regression
Version: unspecified → 2.0
susan can you answer to comment #3, please?
still need susan's stack ... we don't like to close crashes without good resolution, but stack is needed.
Keywords: crash, stackwanted
Whiteboard: closeme 2009-12-01
RESO INCO due to lack of response to last question. If you feel this change was in error, please respond to this bug with your reasosn why.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.