Closed Bug 84731 Opened 24 years ago Closed 23 years ago

Mail send fails to complete when SSL set to "When Available"

Categories

(MailNews Core :: Backend, defect, P1)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.2

People

(Reporter: tracy, Assigned: mscott)

References

Details

(Whiteboard: [nsbeta1+][PDT+])

Attachments

(3 files)

seen on commercial builds: windows 2001-06-08-06-trink mac 2001-06-08-01-trunk note: linux 2001-06-08-09-trunk is okay -Compose a mail message (in pop or imap, plain text or html) -Send the messaage the status bar spins perpetually "sending message" the message is never sent
Keywords: smoketest
Tracy, do you see this only on today's builds or do you see this on yesterday's build or a 4.7 build? I'm asking because I've been seeing this on a branch build from a couple of days ago when it didn't used to happen. I'm wondering if there's some kind of server problem or bad interaction between our client and the smtp server. reassigning to ducarroz and cc'ing varada.
Assignee: mscott → ducarroz
I am able to send messages from 4.x on the same machines taht the smoketests for the commercial builds were performed on. There seems to be alot of network problems today. I am sure it's possible that's allthis is...but I wonder why linux commercial works and not this. granrose believes that perhaps the cvs problem this morning prevented linux builds from getting ther changes from last night. Loan is respinning linux builds now.
I logged similar bug yesterday (see bug 84534) but after I remove profiles, mozregistry.dat & mozver.dat files and reboot my system - it's working again. don't know it matter or not!!
I don't have problem sending mail! Does anybody else have the problem? Tracy, can you delete your registry and try again.
Status: NEW → ASSIGNED
FYI, this is happening using the 6/6 0.9.1 build too. Multiple times I haven't been able to send an email the very first time but then when it comes back with Send Failed, I try again and it works. Though the last 4 or so mails I've sent have worked without a problem.
I am seeing this on MSW2000 Build 2001060804. Sendmail Sez: Jun 8 14:24:32 sdcorp sendmail[13229]: NOQUEUE: sdcorp.net [66.47.89.226] (may be forged) did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA.
Mai Mai Tsai has been having this problem with the beta1 cantidate bits. I'm adding her to the CC: list for her to comment.
Fails on Mac Commerical build 2001060808 also. Mozilla tree still building...
VARADA -"After several moments of stupidity I have found the problem - SSL When available strikes again. I forget the existing bug on this and will leave it to someone else."
I thought the SSL problem was fixed!
verified on the mac build too that ssl not set to never is the problem
This might be the dup of #74387 assigned to jgmyers. Reassigning bug to mscott as requested and removing smoketest blocker since there is a workaround.
Assignee: ducarroz → mscott
Status: ASSIGNED → NEW
Keywords: smoketest
Summary: Mail send fails to complete → Mail send fails to complete: SSL problem?
Okay, I'm tired of this pref setting repeatedly biting us in the butt. I don't agree with the default setting of "try SSL when available". I'm going to invoke the wrath of John and attempt to change our behavior to the 4.x behavior which is to default to "never use SSL" and allow the user to choose to try ssl. Of course we still need to find the cause of the regression that broke "try ssl" again.
I agree we should change the setting. Those who care about SSL will change it.
This patch reverses the change to default all SMTP servers to "Try SSL when available" back to the original behavior of "Never try SSL". Note: this only works for new profiles. It won't change the setting on existing profiles.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
*** Bug 84875 has been marked as a duplicate of this bug. ***
I also got this problem on Linux w/ build 2001060721. The weird thing is that it seems to block all the networking part of mozilla : when moz tries to send the mail, I go on an opened browser window, and try to load a page : there is absolutely no network activity (as I can see using tcpdump). See attachment for what I get on the console output of Mozilla. Setting SSL to never and de-selecting "Use name and password" seems to correct the problem (the mail is sent correctly). Note that this bug seems to be related to bug 79391.
In addition to making the pref Never by default, we need to fix the actual bug, so I'm changing the summary.
Keywords: nsbeta1
Priority: -- → P1
Summary: Mail send fails to complete: SSL problem? → Mail send fails to complete when SSL set to "When Available"
Whiteboard: [nsbeta1+]
*** Bug 85098 has been marked as a duplicate of this bug. ***
Win2000 build 20010610xx also has this problem. I didn't try if it is "SSL when available" or not. Same situation as ------- Additional Comments From Thibault G. 2001-06-09 08:56 ------- The weird thing is that it seems to block all the networking part of mozilla
adding PDT+
Whiteboard: [nsbeta1+] → [nsbeta1+][PDT+]
*** Bug 85262 has been marked as a duplicate of this bug. ***
I've spun off Bug #85304 to track down the regression with the TLS socket used by SMTP. Looks like the problem is in PSM who creates the TLS socket. I'm not sure how they are able to block our networking threads though but that's definetly what I'm seeing. I'll leave this bug alone as a tracking bug for making the default for new profiles be "Never use SSL" instead of "use when available".
Blocks: 83989
*** Bug 85338 has been marked as a duplicate of this bug. ***
*** Bug 85332 has been marked as a duplicate of this bug. ***
*** Bug 85497 has been marked as a duplicate of this bug. ***
a= asa@mozilla.org for checkin to the trunk. (on behalf of drivers)
The default for new profiles should be "When Available." Users shouldn't have to take extraordinary action in order to get the benefit of server features such as security or certificate authentication.
Please mark future dups of this bug on 83989 which is the real problem here (psm was no longer creating TLS connections properly).
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Do you mean trunk approval is the problem here? ;-)
There are currently no members of the crypto team on this cc list. I'm adding some.
Start having this problem on Windows and Linux since 6-12 trunk build. With 6-12 & 6-13 trunk builds on Windows and Linux, cann't send out mail at all. Did clean installation and use default settings to start messenger. It fail always. But as soon as switching back to Beta build or Communicator, sending mail works without any problem.
yulian, you are running into Bug #85304.
Works for 20010614 trunk builds now. Thank you for the FIX !!
Verifying it.
Status: RESOLVED → VERIFIED
*** Bug 86675 has been marked as a duplicate of this bug. ***
I use build 2001080303, I think this has regressed, but the problem is with big messages My setup is: -IMAP server with SSL encryption -Sent messages are copied to "sent" folder in the mailbox To reproduce, I need to: -Create a message -Add some attachments to it (I added 3 images ~350 kb each) -Fill in To: and Subject: lines -Click send Mozilla shows a modal send progress window. The bar goes to 99%, then stops. The spinner in the composition window keeps spinning even if I close the send progress window with its 'X' button. Should the bug be reopened?
BTW, when I change SMTP option "Use secure connection" from "When available" to "never", messages are sent successfully.
*** Bug 88303 has been marked as a duplicate of this bug. ***
Build: 2001 08 11 08 Win2K I run into this problem on a daily basis, normally when forwarding emails to other people. Reopening.
Status: VERIFIED → REOPENED
Keywords: nsenterprise
Resolution: FIXED → ---
Attached image snapshot of a frozen mail send (deleted) —
Bob, your problem is a dup of 88303 which is a psm bug. Someone incorrectly marked it a dup of this bug.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
Verifying as nothing really changed since the bug was earlier verified for the frst time.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: