If SOCKS server is down, Thunderbird shows no error message



14 years ago
13 years ago


(Reporter: tk-mozilla2, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: version 0.9 (20041103)

I use a SOCKS proxy to connect to *some* of my accounts while others use a 
direct connection (via exceptions in the proxy settings).

The SOCKS proxy always runs on localhost:1080, but sometimes I forget to start 

If the SOCKS server is not up and running Thunderbird shows no error message 
when I try to connect to the email accounts that make use of the SOCKS proxy. 
It looks as if there are no new messages on the server which is very very 

It should show a message to the effect "Cannot connect to the configured SOCKS 
proxy" or "Cannot connect to the mail server"

I haven't checked on the HTTP proxy but I suspect it suffers of the same issue.

I am not sure if it has anything to do with the fact that I am using the 
loopback interface, maybe it shows an error message when using another IP 
address but for localhost it shows no error.

Thanks for a future fix.

Reproducible: Always
Steps to Reproduce:
1. Configure a SOCKS server on localhost:1080 (usually you can simply use ssh -
D to forward localhost:1080 or putty and enable dynamic port forwarding)

2. Verify that you can access a mail server via the configured SOCKS proxy

3. Kill the SOCKS proxy

4. Try and connect to the email server again

5. No error message is shown in Thunderbird, it looks as if the connection 
worked fine and there's no new mail on the server (which is not the case).

Actual Results:  
No error message is shown in Thunderbird, it looks as if the connection worked 
fine and there's no new mail on the server (which is not the case).

Expected Results:  
Show an error message "Cannot connect to the email or proxy server"
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/
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.