User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/20060508 Firefox/126.96.36.199 Build Identifier: Thunderbird/188.8.131.52 On a machine provided by my company and through the company network... I have ports 143 and 25 tunneled via cygwin ssh from my local machine to my server. Thunderbird 184.108.40.206 and below have no problem with this configuration when the "mail server" is set to "localhost". When T-bird upgraded to 220.127.116.11 automatically I now get the message "Could not connect to mail server localhost; the connection was refused." I get the same message when I use "127.0.0.1" as server name. I verified the same behavior with a new profile and on the latest nightly build "version 3 alpha 1 (20060604)" with both old and new profiles. On a machine within my home network the same tunneling appears to work without a problem in 18.104.22.168 Reproducible: Always Steps to Reproduce: 1. set up local ssh tunnel redirecting imap and smtp. (here is the excerpt from my ~/.ssh/config file) Host hometunnel hostname gateway.example.com User me Compression yes TCPKeepAlive yes LocalForward 25 mail:25 LocalForward 143 mail:143 2. (probably optional) Install Thunderbird 22.214.171.124. Create a profile with mail server "localhost" for both incoming and outgoing and server type imap. Observe that a connection is made and mail is retrieved. 3. Install Thunderbird 126.96.36.199 or version 3 alpha (20060604). Start Thunderbird on the same profile or create a new profile. Observe that the connection is reportedly refused. 4. Downgrade to Thundebird 188.8.131.52. Verify that the mail is still retrieved. 2. 3. Actual Results: see above Expected Results: see above If you have any suggestions about the possible differences in environment I'd be happy to investigate from this end.
Are you sure there isn't another app binding to those ports on localhost? Are the ports available?
Version: unspecified → 1.5
>Are you sure there isn't another app binding to those ports on localhost? Are the ports available? Yes. I don't change the tunneling configuration between runs of T-bird. Also, even while T-bird 184.108.40.206 refuses to connect I can telnet to the appropriate port and see the mail server greeting messages.
Dewey, could you please check to see if the issue still occurs in the latest supported version 220.127.116.11 or trunk nightlies?
Whiteboard: CLOSEME 2008-04-16
No information for ~3 weeks since last comment, resolving incomplete. Please comment if the issue still occurs in the latest supported 2.0.0.x or trunk nightlies.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.