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 cred
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 a
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.
rega
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
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: s
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 a
So I did generate an activity log, which is sadly not too rich in
information. The empty oauth window appears at the point where the log says
"XOAUTH2 auth". I then close the window (since I can't interact with it
anyways) and close icedove, leading to the rest of the log.
I would assume that the
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 a
Hello Nikola,
hello Cedric,
On Mon, Aug 29, 2016 at 07:13:35AM +0200, Cedric Brandenbourger wrote:
> 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
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 prefer
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,
11 matches
Mail list logo