Bug#525966: Proxy issue maybe?

2009-07-14 Thread Cedric Blancher
Le mercredi 06 mai 2009 à 12:44 +0200, Josselin Mouette a écrit : Evo does not support remote PAC scripts yet, it needs to be converted to using libsoup-gnome so that they actually work. Basically, I feel that evo-exchange proxy handling is not working very well. I got rid of my PAC script and

Bug#525966: Proxy issue maybe?

2009-05-26 Thread Cedric Blancher
Hi! Le mercredi 06 mai 2009 à 12:44 +0200, Josselin Mouette a écrit : Evo does not support remote PAC scripts yet, it needs to be converted to using libsoup-gnome so that they actually work. Any end-user proof way to do that ? PAC scripts only work for gecko applications currently, so that’s

Bug#525966: Proxy issue maybe?

2009-05-06 Thread Josselin Mouette
Hi all, I’ve been experiencing similar issues while upgrading to evo-exchange 2.26, and it turned out to be caused by the proxy configuration. If I configure a proxy manually in the evolution configuration, the exchange connector fails and asks indefinitely for authentication. If I configure the

Bug#525966: Proxy issue maybe?

2009-05-06 Thread Eamonn Hamilton
On Wed, 2009-05-06 at 10:39 +0200, Josselin Mouette wrote: Hi all, I’ve been experiencing similar issues while upgrading to evo-exchange 2.26, and it turned out to be caused by the proxy configuration. If I configure a proxy manually in the evolution configuration, the exchange connector

Bug#525966: Proxy issue maybe?

2009-05-06 Thread Cedric Blancher
Le mercredi 06 mai 2009 à 10:39 +0200, Josselin Mouette a écrit : I’ve been experiencing similar issues while upgrading to evo-exchange 2.26, and it turned out to be caused by the proxy configuration. That's right, but it turns out to be more complicated than that.. If I configure the proxy