Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#835866: icedove fails to connect to existing google apps accounts

118 views
Skip to first unread message

Никола Јелић

unread,
Aug 28, 2016, 5:30:02 PM8/28/16
to
Package: icedove
Version: 1:45.2.0-4

When I upgraded from 38.8.0-1~deb8u1 to 1:45.2.0-4, two existing email
accounts which are Google Apps business accounts, failed to connect to
server. The interesting thing is that other google mail accounts are
working just fine (those who use google directly, x...@gmail.com).

I tried:
1. Erasing passwords for those accounts, which made icedove to show me
an empty window, which should normally contain a dialog for entering
email address and password, followed by allowing icedove/thunderbird to
read and send emails from this account.
2. Downgrading to 38.8.0-1~deb8u1, which restored the expected behaviour.

I can only assume that a recent patch introduced some weird handling of
these types of email accounts and that the application fails to properly
acquire and/or use the token for Google Apps.

Best regards,
Nikola Jelic

Cedric Brandenbourger

unread,
Aug 29, 2016, 1:20:03 AM8/29/16
to
Package: icedove
Version: 1:45.2.0-4
Followup-For: Bug #835866

Same problem for me.
I tested the version of debian stable, every is working fine there.
I also tested the official thunderbird version. Everything is also working fine



-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages icedove depends on:
ii debianutils 4.8
ii fontconfig 2.11.0-6.5
ii libasound2 1.1.2-1
ii libatk1.0-0 2.20.0-1
ii libc6 2.23-4
ii libcairo2 1.14.6-1+b1
ii libdbus-1-3 1.10.10-1
ii libdbus-glib-1-2 0.106-1
ii libevent-2.0-5 2.0.21-stable-2+b1
ii libffi6 3.2.1-4
ii libfontconfig1 2.11.0-6.5
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.1.1-11
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-2
ii libgtk2.0-0 2.24.30-4
ii libhunspell-1.4-0 1.4.1-2
ii libicu57 57.1-2
ii libnspr4 2:4.12-2
ii libnss3 2:3.25-1
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libpangoft2-1.0-0 1.40.1-1
ii libpixman-1-0 0.33.6-1
ii libsqlite3-0 3.14.1-1
ii libstartup-notification0 0.12-4
ii libstdc++6 6.1.1-11
ii libvpx3 1.5.0-4
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.2-1
ii libxrender1 1:0.9.9-2
ii libxt6 1:1.1.5-1
ii psmisc 22.21-2.1+b1
ii zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii hunspell-en-us [hunspell-dictionary] 20070829-6
ii iceowl-extension 1:45.2.0-4
ii myspell-de-de [myspell-dictionary] 20160407-1
ii myspell-fr [myspell-dictionary] 1.4-27

Versions of packages icedove suggests:
pn apparmor <none>
pn fonts-lyx <none>
ii libgssapi-krb5-2 1.14.3+dfsg-1

-- no debconf information

Carsten Schoenert

unread,
Aug 29, 2016, 2:10:03 AM8/29/16
to
Hello Nikola,
hello Cedric,
from our side there was no special patch in this direction. The patches
that are currently used are visible in the VCS.

https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/tree/debian/patches

> Same problem for me.
> I tested the version of debian stable, every is working fine there.
> I also tested the official thunderbird version. Everything is also
> working fine

I don't know until now that there are "business" email accounts
available in GMail. So currently I can't readjust this situation.
You booth don't explain what the different steps are against the normal
email accpunt in Google and there it exactely breaks.

You can do some logging to see probbaly what's going on under hood like
cescribed in the wiki.

https://wiki.debian.org/Icedove#Debugging_Icedove_Activity

Please do at least some logging and try investigate the situation better.
Note that the logs may contain some private data before sending!

Regrads
Carsten

Stephan Burkhardt

unread,
Aug 29, 2016, 3:40:02 AM8/29/16
to
I have a "normal" google mail account which I am using with icedove (using oauth2, current version from testing). A couple of days ago, icedove stopped being able to fetch or send mail (with some version of "can't connect to server" or so). I then deleted the oauth2 credentials, which I suspected as likely culprit.

Now, when I try to connect, icedove opens an empty popup window with the title "Enter credentials for [my email address] on imap.googlemail.com. However, this window is blank except for a visible (but not selectable) address bar. Usually, this window should serve a website that handles the oauth2 login, I assume.

This sadly leaves me unable to connect to my gmail account for the time being (a workaround would be to use password login, I guess).

Eloi

unread,
Aug 29, 2016, 4:30:03 AM8/29/16
to
I had a long mail written using reportbug but somehow it appears to have
been lost :-(

I said that I have two Google Mail accounts setup with Icedove, one
configured with 2FA and so using a single purpose password for login,
and the other using OAuth2.

Also, the first one is a proper @gmail.com account (actually, this)
while the other was created at first with a third party domain for
Google+/Google Hangouts usage but after time Google Mail services were
attached to it, so it now has two logins, one with a third party domain
and another with the configured @gmail new mailbox.

The first account logs in flawlessly. The second one fails to login
using both the no...@gmail.com login as the @gmail.com one.

As other people suggested, I'm more inclined to believe that the issue
relies on OAuth2.

Cedric Brandenbourger

unread,
Aug 29, 2016, 5:10:03 AM8/29/16
to
Package: icedove
Version: 1:45.2.0-4
Followup-For: Bug #835866

I also tested version 4.5.2.0-1~deb8u1 from debian stable. This version is
working under debian testing. So i think there is a change which was made in
the package and not on the google side.



-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages icedove depends on:
ii debianutils 4.8
ii fontconfig 2.11.0-6.5
ii libasound2 1.1.2-1
ii libatk1.0-0 2.20.0-1
ii libc6 2.23-5
ii libcairo2 1.14.6-1+b1
ii libdbus-1-3 1.10.10-1
ii libdbus-glib-1-2 0.106-1
ii libevent-2.0-5 2.0.21-stable-2+b1
ii libffi6 3.2.1-4
ii libfontconfig1 2.11.0-6.5
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.1.1-11
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-2
ii libgtk2.0-0 2.24.30-4
ii libhunspell-1.4-0 1.4.1-2
ii libicu57 57.1-3

Cedric Brandenbourger

unread,
Aug 29, 2016, 5:50:02 PM8/29/16
to
Package: icedove
Version: 1:45.2.0-4
Followup-For: Bug #835866

I found a workaround for my case. When Creating a new email account, instead of
OAuth2, i checked "Normal password" and the emails are syncing again.

Hope that helps someone



-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)

Herbert Fortes

unread,
Aug 30, 2016, 2:00:03 PM8/30/16
to
Hi,

I am also had problems when creating a gmail
account.

> I also tested version 4.5.2.0-1~deb8u1 from debian stable. This version is
> working under debian testing. So i think there is a change which was
made in
> the package and not on the google side.

I am using 4.5.2.0-1~deb8u1 now.



regards,
Herbert

Michael Zimmermann

unread,
Sep 5, 2016, 4:10:03 AM9/5/16
to
I think that the Oauth2 Login dialog does not render properly. This
affects my email (by switching to normal password instead of Oauth this
works, but Oauth would require the login dialog as well), gContactSync
and Google Provider for iceowl. The latter give no chance to switch to a
different authentication method, so I have no chance to get this working
as this relies on Oauth and Oauth requires a web based login dialog
which does not show up at all.

Regards,

Michael

Andrey Skvortsov

unread,
Sep 9, 2016, 5:50:03 PM9/9/16
to
Same here.
I'm using icedove only for calendar management with iceowl. To access
google calendar I'm using calendar-google-provider.

After upgrade to 45.2.0-4+b1 calendar stopped working.
I got authentication error messages in console. To update OAuth2
authentication credentials I removed old credentials.
Now icedove shows empty window there it asked in the past e-mail and password to
access google calendar.

I get activity log for all modules, but it's 30M.
NSPR_LOG_MODULES=all:5 NSPR_LOG_FILE=~/icedove-activity.log icedove


--
Best regards,
Andrey Skvortsov


signature.asc
0 new messages