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