On Wed, 8 Dec 2021 19:27:08 -0600
Post by Rinaldi Post by Chris Vine
On Wed, 8 Dec 2021 16:49:01 +0100
Post by Ralph Spitzner
I'm currently using fetchmail to draw from various POP accounts and distribute on my server using fetchmail, procmail, and dovecot. It has worked flawlessly for several years going back to when imapd was the serving daemon.
I received notification that Gmail will be going to 2FA (two factor authentication) as of December 14.
Switching to 2FA at gmail results in a fetchmail authentication error. Obviously the challenge/response required to log in is missing in fetchmail, just the POP password is submitted.
Does this signal the end of my current mail service and force us to use webmail? If not, how can I satisfy gmail's need for 2FA via fetchmail? Is there an alternative to fetchmail that will provide this authentication requirement?
all good just generate an "application-specific" password an use that instead of "your" password
Would you care to elaborate?
Got app specific passwords for fetchmail and t-bird. This stanza is
working for gmail in ~/.fetchmailrc.
poll pop.gmail.com with proto POP3 service 995
user '$USER' there with password '$2FAPWD' is '$USER' here ssl
Thanks. I use fetchmail for receiving from pop.gmail.com and for
sending I generally use postfix as a local server on localhost with
smtp.gmail.com as relay, or sometimes mailx and sylpheed directly
forwarding to smtp.gmail.com as relay. I also have two or three
different laptops which I use with my gmail account.
Do all these different applications require their own application
specific password? If so, given that each laptop would also seem to
require its own set of passwords, this all sounds somewhat tedious.