Pages: 1
RSS
I can no longer connect to The Bat with POP3 due to Googles OAUTH issues of using insecure apps., I have scoured the internet trying to find a solution to this OAUTH issue.
 
I don't understand why the programmers at Ritlabs are not addressing this problem, as it will affect everyone's ability to connect to Gmail using TB. I've looked everywhere for a solution, but nothing has surfaced concerning the fact that the Ritlabs team isn't offering any solutions to this issue. Everyone will be cut off very soon in 2025. Could this be the end of TB? It certainly feels that way. It feels like the days of Eudora, Pocomail, and Pegasus Mail. Will 2025 mark the end of TB? At this point, it seems likely. It's obvious the developers don't care anymore. I don't know what to do. I have searched the internet for a solution to this OAUTH issue, but have been unsuccessful. I don't understand why the programmers at Ritlabs are not addressing this problem, especially since it will affect everyone's ability to connect to receive Gmail. Everyone will be cut off very soon in 2025. The developers don't care anymore. And, besides, with every update they rush to the table, you can expect a slew of bugs for 60 months or more. Below is the error message I received when trying to log into Gmail from TB.

This site can’t be reached
localhost refused to connect.

Try:

ERR_CONNECTION_REFUSED
 
I'm using an antique version of The Bat and it works just fine with Gmail POP3. The OAUTH issues that existed a few years ago have all been addressed, too.

In other words, I don't know what you're speaking of.

See my messages in this topic for the Gmail/POP3 settings that I use:

https://www.ritlabs.com/en/auth-forums/forum4/topic16544/
I volunteer as a moderator to help keep the forum tidy. I do not work for Ritlabs SRL.
 
Quote
Tim Hamm wrote:
Everyone will be cut off very soon in 2025. Could this be the end of TB? It certainly feels that way. It feels like the days of Eudora, Pocomail, and Pegasus Mail. Will 2025 mark the end of TB? At this point, it seems likely.

And please stop with the doom and gloom, for the vast majority of users TB is working just fine.

EDIT: Including yourself, now I see in the other thread that you found a workaround :D
Anyway, I don't understand how/why Google would flag TB as insecure for you. I went through browser-driven OAUTH authentication once more than a year ago, and never needed to again. Upgraded / rolled-back multiple v11 subversions in the meantime... Maybe there is some confusion with tokens/cookies in your browser from multiple authentication attempts. If you ever need to go through this again maybe try using another browser never used for this purpose.
Edited: Miloš Radovanović - 09 May 2025 14:24:00
Pages: 1