From: NoEMail@home.org
root wrote:
> Chris Vine wrote:
>> On Thu, 2 Jun 2022 22:24:29 -0000 (UTC)
>> root wrote:
>>> Rinaldi wrote:
>>> > On 6/2/22 16:16, Chris Vine wrote:
>>> >
>>> > poll pop.gmail.com with proto POP3 service 995
>>> > user '$USER' there with password '$PASSWD' is 'me' here ssl
>>> >
>>> > rinaldi
>>>
>>> Rinaldi please note:
>>> the oauth2 was supposed to start a few days ago. My name is
>>> early in the alphabet and I was hit this morning. It may be
>>> that your account, while now active, may be shut down soon.
>>>
>>> To be on the safe side, try to enable oauth2 now while
>>> you still have working account.
>>
>> Nonsense. Instead of encouraging others to go down your dead end
>> which you say you have spent 7.5 hours on, accept that what people have
>> told you is right and get yourself an app password. You will not get
>> fetchmail to work any more with gmail without it. If you want true 2
>> factor authentication then you need to use a client like evolution or
>> thunderbird, which support it.
>
> I was not saying that anything I did was right. I am saying that
> yesterday Rinaldi's pop entry worked for me. Today it did not.
> If you follow Google's instructions, you get to a point where
> you can't access your account.
>
> I only urged Rinaldi to get the oauth2 work done now.
>
> I say here that your instructions for oauth2 DO WORK for
> fetchmail.
>
> Maybe you can show me your line in .mailrc which includes
> the new 16 character password?
>
OK, all is well. Whereas the password with four strings
of four characters each separated by spaces works for
fetchmail, the spaces must be eliminated in .mailrc.
Just another google POS.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
