Closed Bug 98372 Opened 24 years ago Closed 24 years ago

SSL (host:port) fails without error

Categories

(MailNews Core :: Networking: SMTP, defect)

Product:
MailNews Core
Component:
Networking: SMTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 106631

People

(Reporter: ajs, Assigned: mscott)

References

Details

I just downloaded 2001090408 for Linux, and installed. I immediately found that I could not send mail. I can if I go back to non-SSL SMTP. The odd thing that I do is I set SMTP server to smtp-host:465 (e.g. the smtps port) because we run non-SSL SMTP on 25 (see bug 86648). I then had set use SSL to "Always". I discovered this workaround via bug 86648, and it was most distressing to have even the workaround for that bug evaporate in this nightly.... Going back to previous version for now. I'm also adding a comment to 86648, but since that bug is a "nice if we could" and this is a "used to work", I figure it's worthy of a seperate bug.
QA Contact: nbaca → junruh
Status: UNCONFIRMED → NEW
Ever confirmed: true
My bad. Our SMTPS server had a cert problem that cropped up right around when I installed the nightly. Please be aware that Mozilla did not report the cert failure to me, even though an entry showed up in stunnel's log when I tried to send the mail.
So.... does host:port work? If so, please resolve this invalid and file a separate bug on PSM on the cert thing.
*** Bug 99878 has been marked as a duplicate of this bug. ***
No, it does not work. I'm not using SSL, just a plain SMTP connection defined as "hostname:9025" (it's forwarded by ssh). That's from a build of today's tree on SunOS 5.9 and every other build I've made over the past few days. I can confirm that a build I made on Sep 13 works. 99878 may very well not be a duplicate of the problem that Aaron reported.
This is a follow up to Greg Onifer's comment: about whether 99878 is a dup or not. 99878 was about smtphost:port no longer working. Ignoring the SSL part of the description this bug sounds like the same problem.
My reasoning was that Aaron claimed "my bad" and the timeframes don't match. My builds from long after his problem report still work properly with host:port (non-SSL). His last update was 9/6, my 9/13 build works fine. It's only in the last few days that host:port stopped working for me (I build at least once a day).
*** Bug 101583 has been marked as a duplicate of this bug. ***
0.9.5 on Linux has the same problem.0.9.4 did not have. regardless of SSL.
Debugged it via tcpdump: Mozilla is not even trying to do a connection. Probably there is a bad check for validness: In the setup-wizard you are not allowed to enter the ":port" part - it responds with "please enter a valid hostname".
Looks like a dupe of bug 106631.
I agree, it is a duplicate of bug 106631.
*** This bug has been marked as a duplicate of 106631 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified.
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.