1230823 - Thunderbird 38.4.0 does not load mails via POP3 when manual proxy configuration is used.

Status: UNCONFIRMED

(MailNews Core :: Networking, defect)

Description

[bugzilla]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20151027170520

Steps to reproduce:

After creating a new profile and configuring one POP3 account (from my server running on Linux and using dovecot), I was able to use this new account and load and send  new mails successfully. Thunderbird is running in Win7, 64Bit.


Actual results:

After some time (less than 3 hours), Thunderbird failed to load mails. The error console gives the following error message:

Zeitstempel: 06.12.2015 15:21:07
Fehler: An error occurred executing the cmd_getNewMessages command: [Exception... "Component returned failure code: 0x8055000a [nsIMsgIncomingServer.getNewMessages]"  nsresult: "0x8055000a (<unknown>)"  location: "JS frame :: chrome://messenger/content/mailWindowOverlay.js :: GetNewMsgs :: line 2719"  data: no]
Quelldatei: chrome://global/content/globalOverlay.js
Zeile: 99

The logfile from dovecot does not show any attempts for connection. A telnet from my windows machine to my home server shows me the message that dovecot is ready for connection.

Restarting Thunderbird and/or my Windows machine did not solve the issue. Thunderbird refues to download mails.


Expected results:

Mails should have been downloaded successfully.

Comment 1

[bugzilla]

More details regarding the "source" of the problem and the solution in case it happens (I just found out):

The problem can be triggered by editing the parameters for the network connection, i.e. if I use the proxy settings of the system, then Thunderbirds works perfectly fine, however when I manually enter proxy parameters, then the described failure occurs.

I my case, I entered: http proxy fqdn of my proxy and port 4711 and I am using this setting for all services (these paramter work perfectly fine in Firefox).

Comment 2

[Jorg K (CEST = GMT+2)]

FQDN = fully qualified domain name.

Comment 3

[Jorg K (CEST = GMT+2)]

Proxy? Let's ask Kent.

Comment 4

[Kent James (:rkent)]

There were changes to the proxy code in mozilla-central that we had to adopt in Thunderbird 38. My understanding is that broke some of our proxy code, and is still not fixed. I do not know the extent of what works and does not work. The guy who does the proxy addon was trying to fix this, but I think he has not made any progress for the last few months. There are bugs on this somewhere.

Comment 5

[Robin]

As I am having an issue with "No proxy for:" with manual proxy configured, I don't know if this bug is related to my bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=1263295

Comment 6

[Fuujuhi]

I confirm I have the same issue on TB 38 on Linux.

I have a proxy running on localhost, and none of the following is working:
* Using system proxy
* Using manual proxy
* Installing Foxy Proxy (this crashes TB).

I also tried to setup a ssh port forward on localhost. This works fine when no proxy is selected in TB. But this stops working when using the proxy (system or manual). Also, the following does not work as well:
* Using manual proxy with "No proxy for:" set for localhost.

However, the proxy DOES work (at least when set to system proxy) with add-on. At least, it worked with the Remote Address Book. I noticed that the book was not sync'ing at work, and noticed that TB was configured w/o proxy. So I enabled the system proxy (which is basically a local privoxy that then connects to the company proxy), and the book sync'ed fined.

What is also very frustrating is that when the proxy does not work, TB simply says nothing. There is no line in the activity manager. Only the mouse pointer and the tab icon that are spinning forever. It was very difficult to narrow down the problem to the proxy.

In any case, there seems to be serious flaws in the current proxy implementation.

Comment 7

[Wayne Mery (:wsmwk)]

ref bug 1159448, bug 1263295

Comment 8

[Wayne Mery (:wsmwk)]

Reporter does this still reproduce for you?

Comment 10

[bugzilla]

Problem still exists with TB 60.5.0.

Setup was changed since entering the bug: Access to the mail server is done using imap/smtp.

Changing the proxy to the proxy settings used by Firefox (60.5.0esr), then TB is not able to access any mailbox folder and seems to loop forever.

Comment 11

[Fuujuhi]

I confirm I still have the issue on TB 52.4.

I can't test with latest TB because of some add-ons I'm using that stop working with latest TB.
Sorry for that.

TBH I don't care much of this bug anymore because I'm using a VPN now.
In fact I started using a VPN because of this bug.

Comment 12

[opera wang]

Confirm for TB 68.7, I'm using davmail for IMAP on 127.0.0.1, but my SMTP need socks proxy.
I set proxy to ignore 127.0.0.1 but TB still use proxy for IMAP and fails.

Comment 13

[lazcho]

Second that, TB 68.7
The connection for the hosts excluded from proxy list fails!

Comment 14

[lazcho]

Is there any progress? The bug is there in TB 68.8.0

No proxy for: 64.0.0.0/8,.gmail.com,.google.com

Still imap.gmail.com goes through the proxy and fails.

Comment 15

[Wayne Mery (:wsmwk)]

(I misfiled this in imap component)

Magnus, can you assess a priority for proxy issues? https://mzl.la/3d2cPDy are from the same time frame. But there are more reports than that - one more more might be marked blocking the enterprise meta bug

Comment 16

[Magnus Melin [:mkmelin]]

Could be good to investigate, but in general I think proxying mail is a very uncommon setup. If companies don't have direct access on they will will use a VPN.