Closed
Bug 79448
Opened 24 years ago
Closed 23 years ago
IMAP with SSL enabled server doesn't work.
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 133434
People
(Reporter: blais, Assigned: mscott)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9) Gecko/20010505
BuildID: 2001050521
When using IMAP with SSL enabled, I get error message:
"Could not connect to the mail server; the connection was refused."
This works with netscape-4.7.
A telnet to my mail server port 993 shows it's up.
buenos-aires:[]/d$ telnet mail.iro.umontreal.ca imaps
Trying 132.204.24.67...
Connected to mercure.IRO.UMontreal.CA.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
When 0.8 came out, I tried this, had the same problem.
It was already submitted, I added a comment. Been trying multiple nightly
builds since, now trying in 0.9, not working.
Reproducible: Always
Steps to Reproduce:
1.create a new imap mail server
2.enable ssl
3.try to connect to an imaps port of a running imaps server
Actual Results: connection refused error message
Expected Results: for mozilla to start fetching summaries for inbox
Comment 1•24 years ago
|
||
worksforme. you _have_ checked the "use secure connection" checkbox for the
server in question, right?
Reporter | ||
Comment 2•24 years ago
|
||
Yes I have. "Use secure connection", to port 993 (default).
And for that server (I have two imap servers, one with SSL, and one without).
Comment 3•24 years ago
|
||
Works For Me - Linux 2.4.4 - Build 2001050808
I'm using Cyrus IMAPd 1.5.19 with stunnel 3.14.
Reporter | ||
Comment 4•24 years ago
|
||
I have the same problem using the windows build (for 0.9, same imaps server).
Comment 5•23 years ago
|
||
Does not work for me and hasn't worked for a while.... build 2001051813 under
2.2.19. Same error message. I've tried 2 different IMAP, both of which I can
telnet to on port 993. IMAP/SSL worked fine under NS4.76.
Comment 6•23 years ago
|
||
Fails to work on win32-installer-sea.exe (build 2001052304).
It does not connect (but has a busy progress bar).
I checked maillog stats and no activity.
IMAP without SSL works correctly.
It last worked correctly for me using win32-installer.exe (Build 2001051804) I
haven't checked the builds in between.
Comment 7•23 years ago
|
||
FYI, it last worked in Win32 for win32-installer-sea.exe Build 2001052204 from
what I've gathered...
It may not be just a Linux build problem.
But, then again,these failures could be unrelated...
Comment 9•23 years ago
|
||
I also get the message "cannot connect to server" when trying to use an imap
server using SSL. This is true for two different imap servers who are supposed
to support imap with ssl.
I used the installer of the 0.9 Windows Release.
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9) Gecko/20010505
Johannes
Comment 10•23 years ago
|
||
Hi,
I just tested it again with
Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.1) Gecko/20010607
and it seems to work fine - at least after I deleted the existing Imap account
and redefined it!
Thanks for fixing it!
Johannes
Assignee | ||
Comment 11•23 years ago
|
||
great!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 12•23 years ago
|
||
huh... not so fast.
running rh-7.1, downloaded and installed 0.9.1 rpms (main, mail, psm), deleted
~/.mozilla, created new profile, recreated imap server, press cancel on
[non-ssl] access, configure server to use ssl (port 993, default), try to access:
you get the certificate window, then accept, then you get a core dump.
another time i got the previous error (can't connect), but now i get mostly core
dumps.
i had the same problem with build 2001060511.
(i'll test it under windows tomorrow)
(imho this is a serious showstopper and should perhaps be raised priority,
because this prevents those unwilling to use non-encrypted imap mail over the
internet from testing the mail module, and it has been broken for quite a while)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 13•23 years ago
|
||
verified, i've got the same problem under win2k using 0.9.1.
dumps core.
Comment 14•23 years ago
|
||
It works for me using Cyrus 2.0.13 with 0.9.1 (2001061114) built from the rednat
7.x source rpms on a mandrake 8.0 system, however it didn't work for me under
0.9 or any previous builds. Would be nice if the little secure lock icon showed
up next to the mail server without closing mail and reopening it, but thats
being kinda picky.
Comment 15•23 years ago
|
||
Nope, I lied. Seems to be a problem with it not asking for a password when SSL
is used. It was working, I closed and reopened mozilla, and now it connection
refused when I open mail WITHOUT asking me for a password even though I have it
set to ask and not save it (which it does properly with unsecure imap)
Comment 16•23 years ago
|
||
Not sure if this is related, but...
- Using Mozilla v0.9.1 as shipped with Ximian Gnome.
- Configured an SSL IMAP server (Courier-IMAP+SSL) using a self-signed cert,
successfully connected to it and browsed IMAP folder.
- Changed SSL certificate on Courier-IMAP+SSL server to a different self signed
cert.
- From this point on Mozilla complained "could not connect to server".
- Solution: Delete old self signed cert from the cert manager. The next SSL-IMAP
connection worked fine after asking the "do you want to trust this cert" question.
Comment 17•23 years ago
|
||
I'm not sure if this is *directly* related to this bug, but its the closest I
could find - if you folks think it should filed separately, just let me know.
Two things: 1) from reading the last few comments, it appears that IMAP/SSL has
some issues w/ Mozilla - I'm running Moz 0.9.4 / FizillaCFM and connecting to a
Courier-IMAP + stunnel server using a Thawte signed cert and all works fine. 2)
However, I can't seem to (a) view any of the information for the secure
connection (b) nor is the lock 'locked' in the lower right hand corner of the
screen. I have Mozilla's preferences set to use a secure connection (port 993)
and it *seems* to be doing just that ... hard to verify, though. The reason (2)
occurred to me is that I just renewed the SSL cert via Thawte and updated the
PEM file on the server - I thought I'd be able to view the updated expiration
date via Mozilla, but I haven't been able to find any means of doing this.
Comment 18•23 years ago
|
||
I have this bug with 0.9.5 under Solaris 8 sparc. With SSL enabled for imap, it
does nothing. A tcpdump of the network shows no packets going out on port 993.
If I flip back to insecure mode, it works. However, when I go back to secure
mode again, it continues to use the insecure connection, port 143, until I
restart mozilla.
Reporter | ||
Comment 19•23 years ago
|
||
About laetst 0.9.5 IMAP over SSL:
It works for me with 0.9.5 under windows, "sometimes". When it fails, if I
click on a different folder, then it connects, then I can switch back to my
inbox folder and sometimes it works.
Most of the time I think it times out, it is insanely slow for IMAP over SSL. I
mostly still use ns-4.x, which is quite fast with the very same server.
Comment 20•23 years ago
|
||
Ssl (https) doesn't work at all on my Solaris workstation (Mozilla 0.9.5)!
Did anybody else notice this?
Comment 21•23 years ago
|
||
I too have this bug, but it seems even more severe for me, I'm totally unable to
get my mail with 0.9.5 since as soon as I try to open the mail window, it
attempts to connect to the secure IMAP server and promptly coredumps. The
message it gives is:
/usr/local/mozilla/run-mozilla.sh: line 72: 28910 Segmentation Fault (core dumped)
$prog ${1+"$@"}
Seems prety serious to me.this is on a linux intel box.
-Ryan
Comment 22•23 years ago
|
||
IMAP over SSL is broken in Mac OS X as well. Everytime I try to access an
IMAP server over SSL with version of Mozilla greater than 0.9.5, nothing
seems to happen, I click stop, try getting new mail and I get a message
saying "An unknown SSL error occurred (-122227)." Then I get the "Could
not connect to the mail server; the connection was refused." error
message.
Comment 23•23 years ago
|
||
This is still broken, at least for certain servers, it appears.
I told mozilla to log, using:
D:\WINDOWS>Set NSPR_LOG_MODULES=IMAP:5
D:\WINDOWS>Set NSPR_LOG_FILE=c:\tmp\log.txt
.96 only gives me two lines-
1668[2656f58]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: (null)
1472[278ec98]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: (null)
Where .95, with the same settings, gives me-
180[26f04f0]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: * OK
mail-1.oit.umass.edu Cyrus IMAP4 v1.5.24 server ready
180[26f04f0]: mail-c.oit.umass.edu:NA:SendData: 1 capability
180[26f04f0]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: * CAPABILITY
IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME
NO_ATOMIC_RENAME UNSELECT
180[26f04f0]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: 1 OK Completed
180[26f04f0]: mail-c.oit.umass.edu:NA:SendData: Logging suppressed for this
command (it probably contained authentication information)
180[26f04f0]: mail-c.oit.umass.edu:NA:CreateNewLineFromSocket: 2 OK User logged in
At the time I try to connect with .96 or higher, my school's server logs record a
I'm just guessing : "PEM routines:PEM_read_bio:no start line
"
Comment 24•23 years ago
|
||
I continue to have this problem in 0.9.8+ (Build ID: 2002012623) under RedHat
7.2. In 0.9.4, I could work around the problem: If I stopped Mail from trying
to connect, then clicked the "Get Messages" button, it would ask for my password
correctly, and proceed to connect. In my 0.9.8+, this workaround no longer
works: IMAP without SSL connects fine, IMAP with SSL appears to be trying to
connect without success or error message interminably.
Comment 25•23 years ago
|
||
*** Bug 117070 has been marked as a duplicate of this bug. ***
Comment 26•23 years ago
|
||
*** Bug 106850 has been marked as a duplicate of this bug. ***
Comment 27•23 years ago
|
||
Any ideas on where to start hunting this one?
It's a showstopper for me. imap/ssl works on one of my RH7.2 boxes, but not the
other.
Comment 28•23 years ago
|
||
Might this be SOCKS related?
FAILS:
0.9.9+ => socks5 proxy => imap/ssl server
WORKS:
0.9.9+ => ssh tunnel => socks5 proxy => imap/ssl server
Same browser version, same imap server, same source/destination machines.
(I also did some poking around with SSLTRACE and SSLDEBUG, it looks like the
socket is getting closed prematurely in the failure case.)
Updated•23 years ago
|
QA Contact: esther → junruh
Comment 29•23 years ago
|
||
*** This bug has been marked as a duplicate of 133434 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•