Closed
Bug 271594
Opened 20 years ago
Closed 19 years ago
IMAP + SSL sometimes cannot connect
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: bugzilla, Assigned: mscott)
Details
User-Agent: Firefox/1.0 (Windows NT 5.1) Build Identifier: Thunderbird 0.9 My Thunderbird sometimes cannot connect to the SSL IMAP server. It just says it cannot connect, with some kind of error message saying nothing at all. Right now, it worked for one account, but not for the other two. All accounts are on the same server and configured to auto-check on startup. Turning off SSL, browsing a folder and turning SSL back on helps. It then works with SSL again. I have tried out any possible setting of maximum connections (currently set to 1) and root folder stuff (currently set to INBOX.*). I'm using a Courier-IMAP server. Reproducible: Sometimes Steps to Reproduce: Not reproduceable. Actual Results: Cannot connect, see above. Expected Results: Connects.
| Reporter | ||
Updated•20 years ago
|
Flags: blocking-aviary1.0?
Comment 1•20 years ago
|
||
I see this exact same issue with Thunderbird 0.9 on Windows XP SP2 connecting to my server with courier-imap-3.0.7-1 over SSL. I have no problems using Evolution on Fedora Core 2 to connect to the same server over SSL. Regular non-SSL imap works fine in Thunderbird.
Comment 2•20 years ago
|
||
We would need a lot more detail to be able to diagnose what is going on and probably a patch for the trunk with lots of testing before this could get in. Minusing for 1.0.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Comment 3•20 years ago
|
||
Also, suggestion would be to get a NSPR log.
Comment 4•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 5•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•