After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607788 - Unable to authenticate through MS ISA Server proxy
Unable to authenticate through MS ISA Server proxy
Status: RESOLVED DUPLICATE of bug 585638
Product: evolution-mapi
Classification: Applications
Component: Mail
0.29.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2010-01-22 16:48 UTC by John Crossno
Modified: 2011-12-22 09:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Crossno 2010-01-22 16:48:43 UTC
Environment:
Evolution 2.29.20100112-1.2 (x86_64) (reports itself as 2.29.6 in the Help -> About box.
Evolution-MAPI 0.29.5-1.3 (x86_64)

I am unable to get Evolution to authenticate correctly through our ISA server. I've configured it through the network settings in Evolution with authentication. It seems that Evolution is not passing my credentials to the proxy according to the ISA logs, even though I check the box and tell it that authentication is needed and hardcoded my information. I would also have thought that my leaving it blank, I would get asked to authenticate the first time to avoid having to hardcode the information.

I'm having similar issues with the system level proxy set up, which uses curl under the covers to test with. When I run curl manually, I have to specify --proxy-anyauth before it will work, if that is of any help.
Comment 1 Akhil Laddha 2010-02-11 04:29:50 UTC
Could you please try evolution-mapi with libmapi 0.9 as it solves some authentication issues. 

See http://mailman.openchange.org/pipermail/devel/2009-December/001431.html
Comment 2 Milan Crha 2011-12-22 09:37:11 UTC
Thanks fgor a bug report. evolution-mapi is using samba4 for all the connections, and it is also connection with RPC. If I understand your proxy issue correctly, then you request RPC over HTTP, which OpenChange cannot do at the moment, it does only RPC over TCP. There is opened a bug report for this already, thus I'm moving this there. Note the fix requires changes also in OpenChange.

*** This bug has been marked as a duplicate of bug 585638 ***