Pidgin - MSN - Proxy

Tiago.Francisco.Abreu at Tiago.Francisco.Abreu at
Thu Mar 19 05:16:50 EDT 2009

Hi again.

I was responsible for the proxy. Now, I'm not but it's a person that works
with me. So I have some knowledge.
My company only allows connections for HTTP (80) and HTTPS (443). So 1863
is blocked, and we can't change that (we could but we won’t).
The proxy is configured manually.
The MSN servers are not blocked.
Can someone give me more information regarding the patch that Sascha was

Thanks everyone, especially Sascha.

             Sascha Vogt                                                   
             <FunkyFish at                                             
             t>                                                         To 
                                       Tiago.Francisco.Abreu at  
             18-03-2009 17:37                                           cc 
                                       support at                   
                                       Re: Pidgin - MSN - Proxy            


Tiago.Francisco.Abreu at schrieb:
> At my work I installed Pidgin in Windows v.2.5.5. My company use a proxy.
> I successfully configured gmail following same information on the web.
> But I can't make MSN work. However I can make Windows Live Messenger v8.1
> work.
> Can someone help me?
That depends on the actual problem, maybe only your network admin can
help you.

In case you're company uses a (manually configured) proxy for HTTP(S)
traffic over ports 80 and 443 (and blocks directly connecting without
using the proxy within the firewall), but does not require a proxy for
the rest of outgoing connections, then the problem is the following:
MSN uses two connections, one over port 80 and one over 1863 iirc.

So if you configure a proxy server within Pidgin, access over 1863
fails, due to the Proxy not being accepting connections for that port
and if you don't, connections to port 80 are blocked by the firewall.

At my company this issue has been solved as the proxy is now a
transparent proxy, no need to configure it manually anymore. So I do not
know of a solution, apart changing the network infrastructure.


PS: I remember there was a patch floating around somewhere, but I never
bothered to try it and compile Pidgin myself.

 AVISO DE CONFIDENCIALIDADE: Esta mensagem, assim como os ficheiros
eventualmente anexos, é confidencial e reservada apenas ao conhecimento
da(s) pessoa(s) nela indicada(s) como destinatária(s). Se não é o seu
destinatário, solicitamos que não faça qualquer uso do respectivo conteúdo
e proceda à sua destruição, notificando o remetente.
 LIMITAÇÃO DE RESPONSABILIDADE: A segurança da transmissão de informação
por via electrónica não pode ser garantida pelo remetente, o qual, em
consequência, não se responsabiliza por qualquer facto susceptível de
afectar a sua integridade.

 CONFIDENTIALITY NOTICE: This message, as well as existing attached files,
is confidential and intended exclusively for the individual(s) named as
addressees. If you are not the intended recipient, you are kindly requested
not to make any use whatsoever of its contents and to proceed to the
destruction of the message, thereby notifying the sender.
 DISCLAIMER: The sender of this message can not ensure the security of its
electronical transmission and consequently does not accept liability for
any fact which may interfere with the integrity of its content.

More information about the Support mailing list