183449 - the resolver in Mail uses the browser proxy settings

Status: RESOLVED DUPLICATE of bug 156535

(MailNews Core :: Networking, defect)

Description

[Simon Crute]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

The name resolver in the mail component of mozilla seems to use browser proxy
settings. 
i.e. If I put the name of my email server in my local hosts file (the site DNS
won't resolve it) and turn the proxy settings on in the browser, then the mail
client can't connect to the mail server. 

Reproducible: Always

Steps to Reproduce:
1. add a spurious name for your mail server to your local
\winnt\system32\drivers\etc\hosts file
2. disable the proxy setttings in the browser.
3. Configure mozilla mail to use this mail server
4. downlaod email etc. 
5. enable the proxy settings in the browser. 
6. try to access your email again. 

Actual Results:  
When the browser proxy settings are enabled, the mailer can't resolve the host
name, even though it's in the local hosts file

Expected Results:  
it should have resolved the name useing the hosts file.

You may well close this as "Working as designed".
so be it. 

------

FYI, I'm using it this way so I can tulle IMAP over putty to my mail server on
my home network so it doesn't have a locatable host name. 
The DNS on the current site I'm working at only has local machines in it. Only
the resolvers on the web proxy servers are able to resolve internet host names. 

So I normally just add and remove the mail servers name to my hosts file maped
to 127.0.0.1

Comment 1

[R.K.Aa.]

did you read bug 156535?

Comment 2

[Simon Crute]

Oops. Nope. 
It didn't turn up on my searches cos it didn't have DNS or resolver in the info.
(guess that teaches me I should search on the symptom, not what I think the
problem is :-) )

I still think the resolver is a bit broken, though, but I suspect the work
around in that bug will work. I'll test on Monday when I'm next in the environment. 

Comment 3

[Simon Crute]

Yep. Adding the imap server under "no proxies" in the broser configuration is a
good workaround. 

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

While it's a workaround, that's actually how it's intended to be, until we
re-architect those settings.  (I can't find them right now, but there are bugs
in Bugzilla about adding per-server proxy settings in Mail.)

Comment 5

[OstGote!]

This bug is IMHO INVALID, see bug 156535 comment 5.

>it should have resolved the name useing the hosts file.
If you have a socks proxy the proxy will do the DNS.

Comment 6

[Simon Crute]

I'm nolonger in the same environment to check if that was the problem or not. 

However, I still think the resolver should look at the hosts file first, before
resorting to a name server query, either via the socks proxy or directl. 

I could be wrong though :-) 

Comment 7

[OstGote!]

(In reply to comment #6)
> However, I still think the resolver should look at the hosts file first, before
> resorting to a name server query, either via the socks proxy or directl. 
Resolving does the OS (including the hosts file) or the proxy not Mozilla.



*** This bug has been marked as a duplicate of 156535 ***