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