Closed Bug 1263295 Opened 9 years ago Closed 6 years ago

Thunderbird network preferences > No proxy for: settings are ignored.

Categories

(MailNews Core :: Networking, defect)

x86_64
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1230823

People

(Reporter: MeSat, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160321091500 Steps to reproduce: Set up Thunderbird on a machine running TB 35 (I think) it works great. Moved user home directory to a new machine with TB 38, and TB refuses to connect to Davmail. Davmail is the same one that is working with TB35. If I use any proxy settings, I cannot connect to Davmail running on localhost. Same account, different versions of Thunderbird. Configure proxy settings as required for getting through corporate firewall for any web data. During testing I found that local host or 127.0.0.1 were being blacklisted. Even though localhost and 127.0.0.1 were in the preferences for "Manual Proxy", "No proxy for:", localhost or 127.0.0.1 were being blacklisted. If I turn off proxy, then mail works as expected. There never was any issue sending mail. Actual results: Thunderbird wouldn't connect to the davmail host running on localhost or 127.0.0.1 or any other host I set up. Same davmail and TB user data directories for both versions of TB. From debugging attempts I have these log bits. [localhost], host record [7fc9de6c25e0]. -296753408[7fca09654da0]: Successfully adding address [127.0.0.1] to blacklist for host [localhost]. From a different debugging attempt 1483392832[7fcc572b0380]: add word: localhost 1483392832[7fcc572b0380]: adding word to corpus store: localhost (Trait=2) (deltaCount=253) 1483392832[7fcc572b0380]: nsSocketTransport::Init [this=7fcc2e80f180 host=localhost:1110 proxy=webproxy.XXX.XXX:8080] 1006626560[7fcc572b0c80]: nsSocketTransport::ResolveHost [this=7fcc2e80f180 localhost:1110] 1006626560[7fcc572b0c80]: Resolving host [localhost]. 1006626560[7fcc572b0c80]: No usable address in cache for host [localhost]. 1006626560[7fcc572b0c80]: DNS lookup for host [localhost] blocking pending 'getaddrinfo' query: callback [7fcc2b81d200] 721413888[7fcc2cf9c580]: DNS lookup thread - Calling getaddrinfo for host [localhost]. 721413888[7fcc2cf9c580]: DNS lookup thread - lookup completed for host [localhost]: success. 721413888[7fcc2cf9c580]: Caching host [localhost] record for 60 seconds (grace 60). 1006626560[7fcc572b0c80]: Checking blacklist for host [localhost], host record [7fcc2b83e3d0]. Turning proxy settings off allows Thunderbird to connect to Davmail on localhost. Expected results: Thunderbird can connect to localhost or 127.0.0.1 if they are listed in the "No proxy for:" box. May be related to this bug. https://bugzilla.mozilla.org/show_bug.cgi?id=1230823
I mark this as major as it most likely will prevent TB from working properly with no proxy enabled when required.
Severity: normal → major
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Component: Untriaged → Security
Today I was trying to check for add-ons, lightning in particular and it was impossible. TB cannot do any network checks through the firewall as webproxy is turned off. I normally use text email (old preference) but there are times when I need to see remote content. This is impossible.
I confirm I have the same issue on TB 38 / ubuntu.
Component: Security → Networking
Product: Thunderbird → MailNews Core
Version: 38 Branch → 38
I would have to install it on the machine which is at work. I will test, hopefully tomorrow or Thursday.
Finally had time to test 31.8. It worked as expected. 31.7 was what I was testing with before I upgraded. 45.1.1 doesn't work. Same symptoms as I reported 2016-04-14.
I tested 31.8.0/linux-x86_64, and indeed the proxy setting "No proxy for:" works as expected.
Flags: needinfo?(fuujuhi)
Flags: needinfo?(MeSat)

Should be the same as bug 1230823

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.