626898 - Email from IMAP through HTTP-proxy fails

Status: RESOLVED DUPLICATE of bug 264981

(MailNews Core :: Networking: IMAP, defect)

Description

[gima]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7

Network configuration: IP set manually. Default gateway and nameserver left blank.

Attachments for case1.log, case2.log and case2_gw_ns_set.log are gathered by:
Environment variable NSPR_LOG_MODULES=imap:5,imapoffline:5,negotiateauth:5,nsHttp:5,nsSocketTransport:5,nsHostResolver:5,timestamp

What happens:
Cannot read emails from IMAP server if HTTP proxy is set (Squid).
Thunderbird making HTTP requests through the same HTTP proxy doesn't seem to be affected.
Accounts' connection security is "SSL/TLS".
As a side-note: The proxy dialog is antique.

Expected result:
To be able to read the emails normally.

Additional information:
The email reading works fine if I set default gateway and nameserver, while keeping Case 2 (two) Thunderbird proxy settings in effect.


----- Case 1 Thunderbird settings -----
Proxy: HTTP Proxy: [IP-address] 8080
[v] Use this proxy server for all protocols

----- Case 1 Results -----
Connecting to mail.kapsi.fi... [10 second pause] Connection to server [e-mail] timed out.
Connecting to imap.wippies.com... [10 second pause] Connection to server [e-mail] timed out.
Search for Add-on in Tools -> Addons -> Get Add-ons: Success, displays a list of Recommended Add-ons

----- Case 2 Thunderbird settings -----
Proxy: HTTP Proxy: [IP-address] 8080
[ ] Use this proxy server for all protocols
SSL Proxy and it's port & SOCKS Host and it's port set blank.

----- Case 2 Results -----
Looking up imap.wippies.com... Failed to connect to server [e-mail], Failed to connect to server [e-mail]
Search for Add-on in Tools -> Addons -> Get Add-ons: Thunderbird could not retrieve add-ons


Reproducible: Always

Steps to Reproduce:
1. Set network connection's gateway and nameserver blank
2. Set Thunderbird to use HTTP-proxy which resides in your intranet and is reachable by IP
3. Try to get mail
Actual Results:  
The email reading fails.

Expected Results:  
The emails should be delivered to Thunderbird normally.

Comment 1

[gima]

Attachment: Log files for Case 2, Case 2 and Case 2 with gw&ns set.

Comment 2

[Matthias Versen [:Matti]]

you can only use a socks proxy for imap/pop3/nntp at the moment.