Google calendar fails when behind proxy

looks similar to bug http://bugzilla.gnome.org/show_bug.cgi?id=555888

is that similar to what you're facing? could you have a look to the bug previously mentioned? thanks.

That is basically what I'm seeing, except it only seems to affect google calendars (although I'll admit I haven't tried it with other things). The proxy settings seem like they're completely ignored.

I just tried with my gmail account on IMAP. I was able to configure it and get it to find the authentication types, suggesting it was using the proxy, but it wouldn't download folders or mail. No error, just continuously trying to connect. I'm not sure if that's the proxy being ignored or if the connection is being blocked by the proxy (as it does filter traffic like personal email).

I then disabled the proxy and attempted to get authentication information. It failed on the "Sending Email" tab when I clicked the "Check for Supported Types", with a message to the console:

    Host lookup failed: smtp.gmail.com: Name or service not known

so it seems like everything else is using the proxy settings. Only Google Calendar for me is affected.

Ok those patches are applied on evolution since 2.25.91-0ubuntu1 so it should work that way, could you get a tcpdump to see where the traffic is going? if it goes trough the proxy or taking another direction, you might also want to open an upstream bug about it after getting that information, please read http://wiki.ubuntu.com/Bugs/Upstream/GNOME to know how to do it, thanks again Cory.

Using Wireshark, I made a capture of what goes in/out of my network device as I try to add a google calendar. What I expect to see is traffic going out over the proxy to resolve the host and communicate with it. What I see instead is queries to my work DNS server for www.google.com, which return no such host:

48 7.022322 132.224.148.132 192.65.102.200 DNS Standard query A www.google.com
49 7.023570 192.65.102.200 132.224.148.132 DNS Standard query response, No such name

(192.65.102.200 = local DNS server (internal), 132.224.148.132 = my IP address)

This clearly shows the proxy isn't being used for this communication.

I also took a capture when I added the calendar and attempted to activate it. Evolution gives me a password prompt, which I answer. When I click OK, I get the following packets from Wireshark:

7 3.626634 132.224.148.132 192.65.102.200 DNS Standard query A www.google.com
8 3.628374 192.65.102.200 132.224.148.132 DNS Standard query response, No such name

Again, this shows the proxy isn't being used.

I'll submit this information upstream as well and attach the bug number when I get it.

Thanks for sent it upstream Cory.

Same problem here

I think it's an evolution problem. Same than the published by Pedro Villavicencio on gnome, but related to google calendar. If you watch the gnome issue, they haven't spoken about google calendar, then I think it's still broken.

Upstream comment:
>>>
Created commit cd230e5 in evo master (2.29.1+)
Created commit 2956f9d in evo gnome-2-28 (2.27.93+)
<<<
So this should be fixed in karmic. Thanks for reporting.

Its not fixed, im using 9.10. Same ol same ol: Cannot read data from Google server.
Cannot resolve proxy hostname. .

I am not behind any proxy... And the settings seems to be hidden in the new evolution so even if i wanted to give you info... Cant

Kristoffer, could you comment that on the upstream bug tracker : https://bugzilla.gnome.org/show_bug.cgi?id=582780 ? Thanks.

I'm having issues on 9.10 as well, but only when I set Evolution to use the system defaults for the proxy. When I configure the proxy manually within Evolution, I don't have any issues. Might this be an Ubuntu specific issue? It's a little annoying to have to switch the proxy settings in two places when I switch between work and home.

I'm seeing this exact same problem, Pedro. If I use my system's default proxy settings -- which are:

  http_proxy=http://cache.async.com.br:3128
  no_proxy=localhost,127.0.0.0/8,*.local

Then evolution fails to contact google calendar and just tells me "no response from server". If I change Evolution's proxy settings to say "direct connection" then it works fine. I'm not sure if this is a port issue -- perhaps my outbound proxy server doesn't allow connections to the default ICS port.

Oh good. It's not just me then... Does anyone have a clue as to whether this is an Ubuntu-specific or an upstream issue?

As Pedro already said, could you please comment on the upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=582780 that you are still suffering from the bug? They can then decide what to do. Thanks.

This bug was fixed in the package evolution - 2.30.1.2-1ubuntu1

---------------
evolution (2.30.1.2-1ubuntu1) maverick; urgency=low

  * Merge from debian experimental:
    + debian/control:
      - add Vcs-Bzr tag
      - don't build depends on pilot-link it's not required
      - don't use po-debconf there either
      - build-depends on libpst, python and shared-mime-info
      - set gnome-pilot-conduits as suggests
      - don't split documentation since it goes to langpacks
      - evolution replaces evolution-plugins (<< 2.22.2-1)
        since the bogofilter plugin has been moved there
      - evolution-plugins-experimental replaces evolution-plugins (<< 2.27)
      - updated descriptions to reflect binary installs
      - remove libgtkimageview-dev build-dep: not in main, seems crashy right
        now
    + debian/docs:
      - renamed evolution-common.docs
    + debian/evolution-2.2.desktop:
      - compatibility .desktop for users upgrading
    + debian/evolution.gconf-defaults:
      - don't display unstable warning on startup (Ubuntu: #91799)
    + debian/evolution.install:
      - install the autostart and compatibility desktop entries
      - install webdav and python but not hula and print-message there
    + debian/evolution-mail.desktop:
      - don't reapply this ubuntu change and use only one menu entry
    + debian/evolution-alarm-notify.desktop,
      debian/evolution-alarm-notify.desktop.in,
      #debian/patches/64_translate_autostart_strings.patch: #
      - autostart desktop file to start evolution-alarm-notify with the session,
        translate the entry
    + debian/evolution-dev.install:
      - detail the .so to install
    + debian/evolution-plugins.install,
      debian/evolution-plugins-experimental.install:
      - install the .so in binaries corresponding to the upstream options
    + debian/patches/01_dont-ship-evo-mail-notifier.png.patch:
      - don't ship that change that debian added without reason
    + debian/evolution.preinst, debian/evolution.templates:
      - don't display debconf template on upgrade
    + debian/patches/03_lpi.patch:
      - launchpad-integration patch
    + debian/patches/62_no_upstream_email_notification_by_default.patch:
      - don't enable the notification icon by default since the message indicator
        is running
    + debian/patches/10_desktop_shortcuts.patch
      - Adds desktop shortcuts for the messaging menu.
    + debian/rules:
      - don't use -Bsymbolic-functions to workaround memos crashing
      - don't use debconf translation there
      - use --disable-scrollkeeper --enable-python configure option
      - use --disable-inline-plugin: dep not in main, seems crashy right now
    + debian/patches/90_autoconf.patch:
      - refresh autotool

evolution (2.30.1.2-1) experimental; urgency=low

  * New upstream bugfix release.
  * debian/patches:
    - 03_fix-face-plugin-linking dropped, included upstream.

evolution (2.30.1.1-1) experimental; urgency=low

  * New upstream bugfix release. (LP: #154752)
  * debian/patches:
    - 03_fix-face-plugin-linking, fix ftbfs with face plugin.
  * debian/control:
    - bump (build-)deps to gtkhtml/eds 2.30.1.

evolution (2....