[sylpheed:36833] Re: Sylpheed no longer connects to my Gmail account

[Gene Goldenfeld]

Rich,

Guessing one possibility is that Google changed the way Gmail works,
although the scheduled date was May 15. I found out about it via
Mailwasher which sent out the following email (excerpted). Perhaps it
also applies to Sylpheed.

"From 15 May 2019, GMail has decided that all security and anti-spam
apps can no longer use their existing system for adding email accounts
in to applications (where the window pops up and asks you to sign in to
Gmail). Any Gmail users who already had email accounts setup in
MailWasher will find their email account no longer works (Sorry, it's
beyond our control!), but it's an easy fix to get it working again. 

These 2 [fix] options are below...

2: Turn on 'Less secure apps'
Go to your Google Account Security page and enable 'Allow less secure
apps'. https://myaccount.google.com/lesssecureapps

It's not really less secure - it's just the way people have always
added their passwords to email programs."

Gene



On Thu, 6 Jun 2019 10:54:46 -0500
Rich Coe <rcoe at wi.rr.com> wrote:

> On Sun, 2 Jun 2019 22:33:22 +0200
> Andreas Ronnquist <mailinglists at gusnan.se> wrote:
> > On Sun, 2 Jun 2019 23:23:47 +0300,
> > Anton Shepelev<anton.txt at gmail.com> wrote:
> > 
> > >Hello, all
> > >
> > >Sylpheed has suddenly stopped working today with my Gmail
> > >account, although I did not change any settings either in
> > >Sylheed or in Gmail.  Sylpheed now reports the following
> > >error:
> > >
> > >[23:15:43] IMAP4> 1 CAPABILITY
> > >[23:15:43] IMAP4< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE
> > >QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2
> > >AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
> > >[23:15:43] IMAP4< 1 OK Thats all she wrote! x18mb5033387lfa
> > >[23:15:43] IMAP4> 2 AUTHENTICATE PLAIN [23:15:43] IMAP4< +
> > >[23:15:43] IMAP4> **************** ** LibSylph-WARNING: Socket IO
> > >timeout ** LibSylph-WARNING: [23:15:59] IMAP4 authentication
> > >failed.
> 
> 
> I was getting errors too.  
> When gmail came back, I'm still getting this error:
> 
> * Connecting to POP3 server: pop.gmail.com...
> [10:50:08] POP3< +OK Gpop ready for requests from x.yy.zzz.ww
> g140mb209302117jac [10:50:08] POP3> USER richcoexxxxxxxxxx
> [10:50:08] POP3< +OK send PASS
> [10:50:08] POP3> PASS ********
> [10:50:10] POP3< +OK Welcome.
> [10:50:10] POP3> STAT
> [10:50:10] POP3< -ERR Command not understood
> [10:50:10] POP3> QUIT
> [10:50:10] POP3< +OK 475 7725813
> 
> When it works it looks like this:
> 
>  Connecting to POP3 server: pop.gmail.com...
> [10:46:54] POP3< +OK Gpop ready for requests from x.yy.zzz.ww
> y9mb188646814ioy [10:46:54] POP3> USER coxxxxxxxxxxxx
> [10:46:54] POP3< +OK send PASS
> [10:46:54] POP3> PASS ********
> [10:46:54] POP3< +OK Welcome.
> [10:46:54] POP3> STAT
> [10:46:54] POP3< +OK 0 0
> [10:46:54] POP3> QUIT
> [10:46:54] POP3< +OK Farewell.
> 
> So it cannot understand STAT, but it obviously can, otherwise.
> And the reply to 'QUIT' is OK with the number of messages and the
> size.
> 
> Anybody else seeing this?
> -- 
> Rich Coe     rcoe at wi.rr.com