Comment 6 for bug 164301

I'm having similar problems (Gutsy, Pidgin 2.2.1) but possibly different root cause (devs - please advise if you'd prefer a new bug).

Basically, both Yahoo buddy icon gets and file transfers file behind a proxy server because: I have to set "No proxy" for the basic port 5050 connection, and Pidgin isn't honouring the global (Gnome) HTTP proxy connections for its separate port 80 connections for file transfers and buddy icon uploads/downloads.

It's strange because the debug window shows that it *is* honouring the Gnome HTTP proxy settings for the address.yahoo.com connection, but not the filetransfer.msg.yahoo.com (which it appears to use for both buddy icon and other file transfers). Extracts of debug log below confirming this (ist:3128 is the Squid proxy I'm using).

OK main connection with no proxy:

(10:46:01) proxy: Attempting connection to 66.163.181.187
(10:46:01) proxy: Connecting to scs.msg.yahoo.com:5050 with no proxy
(10:46:01) proxy: Connection in progress
(10:46:01) proxy: Connected to scs.msg.yahoo.com:5050.

No Gnome proxy settings used for filetransfer connections (hence they fail - first one for buddy icons, second for actual file transfer):

(10:46:01) dns: Got response for 'filetransfer.msg.yahoo.com'
(10:46:01) dnsquery: IP resolved for filetransfer.msg.yahoo.com
(10:46:01) proxy: Attempting connection to 209.191.110.214
(10:46:01) proxy: Connecting to filetransfer.msg.yahoo.com:80 with no proxy
(10:46:01) proxy: Connection in progress
(10:46:04) proxy: Connected to filetransfer.msg.yahoo.com:80.
(10:46:04) proxy: Error connecting to filetransfer.msg.yahoo.com:80 (No route to host).
(10:46:04) proxy: Connection attempt failed: No route to host
(10:46:04) yahoo: Buddy icon upload failed: No route to host

(10:55:59) proxy: Attempting connection to 209.191.110.214
(10:55:59) proxy: Connecting to filetransfer.msg.yahoo.com:80 with no proxy
(10:55:59) proxy: Connection in progress
[never completes]

Note separate bug #52801 advocating *not* using the global proxy settings:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/52801

If this is an issue as well then presumably the best fix is to add an option to the Yahoo settings to be able to set separate proxy settings for the main (port 5050) connection and the HTTP connections. Otherwise, it should honour the global Gnome HTTP proxy settings I guess.

Apologies if this pollutes what looks a slightly different bug for others (as mentioned earlier, can put in another bug if advised), but this seems a prime root cause problem for all Yahoo proxy related problems.