I have had my Gmail setup in TB! for some time now. I have been receiving/sending messages with no problem. All of a sudden today when I came to retrieve new messages the attached pop up window appeared. Can you tell why it happened all of a sudden after some time of using this account smoothly? Shall I grant TB! the access requested in this window? I can't find a way to attached the screenshot, how do I do that?
If the popup window is about Less Secure Apps: you can configure Gmail to allow access from these so-called less secure apps. See
(in my case though, the setting is off, but I can still access my gmail using The Bat. So, I don't think it is required. I am using The Bat v8.8.2 and in the account properties, under transport, I have set Receive Mail | Authentication to 'OAUTH'.)
I volunteer as a moderator to help keep the forum tidy. I do not work for Ritlabs SRL.
Daniel van Rooijen wrote: I am using The Bat v8.8.2 and in the account properties, under transport, I have set Receive Mail | Authentication to 'OAUTH'.)
This is off topic fr om this thread, but I am running The Bat v8.8.9 and wh ere you are describing, OAUTH has been greyed out. I am asking as AT&T is requiring this.
Ron, I don't know what it is that makes The Bat offer OAUTH as an available option, or not. Maybe you should ask Ritlabs' technical support (see menu above).
In my case, with Gmail, I have set 'Connection type' in the Transport screen to 'Secure to dedicated port (TLS)'. I am not sure if that is what enables OAUTH, but I don't see what else it could be..
You may also want to check older threads about settings for AT&T: . I hope you'll get it to work soon!
I volunteer as a moderator to help keep the forum tidy. I do not work for Ritlabs SRL.
13.10.2019, 10:32:34: FETCH - receiving mail messages 13.10.2019, 10:32:34: FETCH - Connecting to POP3 server pop.gmail.com on port 995 13.10.2019, 10:32:34: FETCH - Initiating TLS handshake >13.10.2019, 10:32:34: FETCH - Certificate S/N: 8311742E893D489D0200000000448281, algorithm: RSA (2048 bits), issued from 9/17/2019 1:40:23 PM to 12/10/2019 1:40:23 PM, for 1 host(s): pop.gmail.com. >13.10.2019, 10:32:34: FETCH - Owner: "US", "California", "Mountain View", "Google LLC", "pop.gmail.com". >13.10.2019, 10:32:34: FETCH - Issuer: "US", "Google Trust Services", "GTS CA 1O1". Valid from 6/15/2017 12:00:42 AM to 12/15/2021 12:00:42 AM. >13.10.2019, 10:32:34: FETCH - Root: "GlobalSign Root CA - R2", "GlobalSign", "GlobalSign". Valid from 12/15/2006 8:00:00 AM to 12/15/2021 8:00:00 AM. 13.10.2019, 10:32:34: FETCH - TLS handshake complete 13.10.2019, 10:32:34: FETCH - connected to POP3 server 13.10.2019, 10:32:34: FETCH - authenticated (OAUTH2) 13.10.2019, 10:32:35: FETCH - 0 messages in the mailbox, 0 new 13.10.2019, 10:32:35: FETCH - connection finished - 0 messages received
sending:
Quote
13.10.2019, 10:47:42: SEND - sending mail message(s) - 1 message(s) in queue 13.10.2019, 10:47:42: SEND - Connecting to SMTP server smtp.gmail.com on port 465 13.10.2019, 10:47:42: SEND - Initiating TLS handshake >13.10.2019, 10:47:42: SEND - Certificate S/N: B1B2ED3884A6C7B6080000000014FB5C, algorithm: RSA (2048 bits), issued from 9/17/2019 1:25:41 PM to 12/10/2019 1:25:41 PM, for 1 host(s): smtp.gmail.com. >13.10.2019, 10:47:42: SEND - Owner: "US", "California", "Mountain View", "Google LLC", "smtp.gmail.com". >13.10.2019, 10:47:42: SEND - Issuer: "US", "Google Trust Services", "GTS CA 1O1". Valid from 6/15/2017 12:00:42 AM to 12/15/2021 12:00:42 AM. >13.10.2019, 10:47:42: SEND - Root: "GlobalSign Root CA - R2", "GlobalSign", "GlobalSign". Valid from 12/15/2006 8:00:00 AM to 12/15/2021 8:00:00 AM. 13.10.2019, 10:47:42: SEND - TLS handshake complete 13.10.2019, 10:47:42: SEND - connected to SMTP server 13.10.2019, 10:47:43: SEND - sending message to [some test address] <13.10.2019, 10:47:44: SEND - message to [some test address] sent (458 bytes) 13.10.2019, 10:47:44: SEND - connection finished - 1 message(s) sent
And when enabling the authentication debugging, I find this in the pop.log:
Quote
[10:37:48] C: Connected to pop.gmail.com, port 995 [10:37:48] S: +OK Gpop ready for requests from [my ip address] [some code here] [10:37:48] C: CAPA [10:37:48] S: +OK Capability list follows [10:37:48] S: USER [10:37:48] S: RESP-CODES [10:37:48] S: EXPIRE 0 [10:37:48] S: LOGIN-DELAY 300 [10:37:48] S: TOP [10:37:48] S: UIDL [10:37:48] S: X-GOOGLE-RICO [10:37:48] S: SASL PLAIN XOAUTH2 OAUTHBEARER [10:37:48] S: . [10:37:48] C: AUTH XOAUTH2 [some long token here] [10:37:49] S: +OK Welcome. [10:37:49] C: STAT [10:37:49] S: +OK 0 0 [10:37:49] C: QUIT [10:37:49] S: +OK Farewell.
Configuration looks like this:
Behind the SEND "Authentication..." button I have enabled "OAUTH (uses web browser)"
I do not know exactly what "uses web browser" means here, if it simply does 'web requests' or if it actually uses your browser to handle those requests... if the latter one: I have installed Firefox and Chrome, and Chrome is running right now.
Behind the RECEIVE "Authentication..." button I have set: [x] perform SMTP Authentication (RFC 2554) (x) Same user/password as for Mail Retriecal [x] Require secure authentication
Daniel van Rooijen wrote: Ron, I don't know what it is that makes The Bat offer OAUTH as an available option, or not. Maybe you should ask Ritlabs' technical support (see menu above).
In my case, with Gmail, I have set 'Connection type' in the Transport screen to 'Secure to dedicated port (TLS)'. I am not sure if that is what enables OAUTH, but I don't see what else it could be..
You may also want to check older threads about settings for AT&T: . I hope you'll get it to work soon!
Sorry for being away and not thanking y'all sooner. From what I can see, Gmail works - AT&T does not. It is something I am going to have to live with until I can get away from them.