IMAP cannot connect to mailserver as of mozilla 0.9.9 (Build ID: 2002031103)

VERIFIED WORKSFORME

Status

MailNews Core
Networking: IMAP
--
major
VERIFIED WORKSFORME
17 years ago
10 years ago

People

(Reporter: Bruno Essmann, Assigned: Scott MacGregor)

Tracking

Trunk
Sun
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
When trying to read any mail message (or get new messages) from an IMAP account
I get an error stating "cannot connect to mailserver <servername>; the
connection was refused". Running a mozilla 0.9.8 (Build ID: 2002020516) with the
same settings works as expected.
Reporter: 
Do you use a Proxy and your Imap server is internal ? 
Have you added your imap server to the "no-Proxy" list ?
(This changed between 0.9.8 and 0.9.9)
Severity: blocker → major
(Reporter)

Comment 2

17 years ago
Yes indeed! Thanks!

My proxy configuration is valid except for ".ergon.ch" in the exclude list.
Specifying "mailhost" as my mailhost doesn't work (even though this is
implicitly "mailhost.ergon.ch").

After I fully qualifying the mailhost (i.e. specifying "mailhost.ergon.ch" as my
mailhost instead of just "mailhost") it works again. 

It would be great if you could add a note in the IMAP server settings that the
mailhost should be qualified. I understand that there's a problem with simply
deciding that non-fully-qualified always bypass the proxy settings. One solution
might be to let the user specify a default domain for non-fully-qualified
servers so that mozilla can decide wether it's on the no-proxy list or not.
marking worksform (the reported bug itself works)

Feel free to file a RFE (but search before)..
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME

Updated

16 years ago
QA Contact: huang → stephend

Comment 4

16 years ago
MailNews issues related to Proxy -> Stephen.
Stephen, can you verify this bug? Thanks.
verified worksforme, per reporter.
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.