On Saturday, September 24, 2016 07:25:13 PM Mick wrote: > On Saturday 24 Sep 2016 07:13:15 Daniel Frey wrote: > > On 09/24/2016 03:53 AM, Mick wrote: > > > On Saturday 24 Sep 2016 13:46:04 Stanislav Ch. Nikolov wrote: > > >> On 09/24/2016 01:21 PM, Mick wrote: > > >>> Has something changed on T'bird and this is why it stopped sending > > >>> messages? Clicking on send just sits there with no sign that the > > >>> client > > >>> is trying to connect to the server. > > >>> > > >>> Have you noticed the same? > > >> > > >> If you see this message, then the answer is no :P > > >> > > >> Stanislav > > > > > > Thanks, this means something may have changed on Gmail and my T'bird > > > settings are not working anymore. > > > > I was having problems a while back until I switched to OAuth2 for the > > GMail servers. The thing is you have to set OAuth2 separately for > > incoming *and* outgoing mail. > > > > Dan > > Thanks Dan, the user assured me they had enabled 'unsafe client > applications' or some such setting on the web interface of their > Google/Gmail account security settings, which means that it should also be > able to do vanilla IMAP4/SMTP with 'Normal Password'. I'll ask them to > check again in case Google has changed this. However, T'bird can still > received messages in the Inbox, it is the SMTP which is not working. :-/ > > Either way, I also tried SSL/TLS with OAuth2 and it is still not working.
You can still do SMTP and IMAP without OAuth2. Use application passwords, and create an application password for your Thunderbird use. This is how I'm using GMail+IMAP+SMTP with Akonadi. https://support.google.com/accounts/answer/185833?hl=en -- :wq
signature.asc
Description: This is a digitally signed message part.
