User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 Build Identifier: Mozilla Thunderbird 0.1 (20030723) While attempting to send an email via smtpgate.email.arizona.edu, mail crashed. The option "Use secure connection(SSL) When Available" was selected. When I attempted to send the e-mail, a pop-up box informed me that encryption was available for use on this particular message, and please see help for more information about using encryption. I hit ok, and the pop-up went away, and mail crashed. This happened several times. Upon changing "When Available" to "Never", the e-mail was sent without problems. Reproducible: Always Steps to Reproduce: 1.set up imap mail account (rdzeigle AT u.arizona.edu) with smtp server of smtpgate.arizona.edu (Unfortunately, this smtp server requires a valid login... try using another smtp server that supports ssl??) 2.set the option "use ssl" to When Available 3.compose mail as normal and attempt to send Actual Results: Thunderbird "stopped responding". Expected Results: Sent the e-mail. I was using the default theme. No other special configs. (The e-mail account was imap, and I do have 2 imap accounts set up. Both use the same outgoing server).
I'm am also experiencing this problem on Win98 Second Eddition with both the 20030723 build and the 0.1 Milestone. It has worked in earlier versions of Thunderbird but sudenly stopped working after I updated to the 0.1 Milestone. Sadly I can't remember wich build that worked but it was before the Password Manager was introduced.
Reporter (ongakugainochi), Brian Olsen: is this bug still an issue? If so, do you get the talkback dialog when the crash occurs? What's the Talkback ID for this crash?
Severity: normal → critical
Summary: maril crashes if I attempt to connect to smtp server which has support for ssl, when the "When available" option is checked → mail crashes if I attempt to connect to smtp server which has support for ssl, when the "When available" option is checked
No response from reporters; =>WFM
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.