GNOME Bugzilla – Bug 738417
Evolution-ews cannot connect on Fedora 20
Last modified: 2014-10-24 12:20:12 UTC
Hi, On a fresh and updated Fedora 20 install, evolution cannot connect to the exchange server. The same setup works for me with a fresh install of Fedora 21. This is in a VirtualBox guest OS on a Windows host. [jfstepha@jfstepha-mobl4 ~]$ EWS_DEBUG=2 evolution Got 'YR' from squid (length: 2). got NTLMSSP packet: NTLMSSP challenge < HTTP/1.1 4 Cannot connect to destination (fmsmsx103.amr.corp.intel.com) < Soup-Debug-Timestamp: 1413147680 < Soup-Debug: ESoapMessage 0 (0x7fa004008130) (evolution:2322): evolution-mail-WARNING **: (mail-send-recv.c:1145):receive_update_got_folderinfo: runtime check failed: (info != NULL) (evolution:2322): evolution-mail-WARNING **: receive_update_got_folderinfo: No response: Cannot connect to destination (fmsmsx103.amr.corp.intel.com) [jfstepha@jfstepha-mobl4 ~]$ -Jon
Thanks for a bug report. Can you ping the server from that machine? The > < HTTP/1.1 4 Cannot connect to destination (fmsmsx103.amr.corp.intel.com) suggests that you cannot. Maybe an issue with proxy? There was a bug in libsoup where the https proxy was not properly used, thus maybe you face that? Can this be a duplicate of bug #738547?
Yes! It is a proxy bug. It looks like evolution is ignoring the no_proxy/"Ignore Hosts" setting. Turning the proxy off inside of Evolution fixed it. (Damn Linux and handling of proxies). I think the "correct" proxy settings have "Ignore Hosts" and no_proxy including ".intel.com". I'm inside the proxy, and the destination is inside the proxy, so any case with the proxy off works. Here’s the truth table (where the manual settings are correct): env_variables gnome_settings evolution_settings fedora_20 fedora_21 set manual system defaults error OK unset manual system defaults error OK set off system defaults OK OK unset off system defaults OK OK x x off OK OK x x manual error OK -Jon
Thanks for the update. In that case it's the libsoup bug about proxy settings for https:, which had been fixed in more recent version, as your table with Fedora 21 proves. *** This bug has been marked as a duplicate of bug 724316 ***