Re: Error message I don't understand

________________________________________=0A=
From: Pieter van Oostrum <[email protected]>=0A=
Sent: Friday, December 30, 2022 8:08 AM=0A=
#############################################=0A=
I have seen this message when my getmail access to an office365/outlook ema=
il account stopped working a couple of months ago. It had to do with Micros=
oft policies about the use of plain passwords being changed. It has been re=
ported before on this mailing list. I haven't found a solution to this. I w=
ould be happy if we could find a solution.=0A=
#############################################=0A=
=0A=
Thank you Pieter for this tip and thank you Charles for your suggestions al=
so.  Our university is a ghost town between Christmas and New Years day.  E=
ven network operations has only a skeleton crew on duty so any communicatio=
n with them has to wait.  So, I've been trying to puzzle it out on my own.=
=0A=
=0A=
Since it's been several days I thought I'd report back to the list what I'v=
e tried to this point even though I haven't yet solved the problem.=0A=
=0A=
I still have access to email using webmail and Outlook, both on my phone an=
d windows, both, however, being very inconvenient.=0A=
=0A=
I tried accessing it using Thunderbird which gave me the exact same error m=
essage as getmail did.  Since the method of getting xoauth2 access suggeste=
d by Pieter Jacques in January, which I followed involved using Thunderbird=
's client ID and client secret, which are both publicly available and not a=
t all secret, I figured that getting the same error from both may be a hint=
 that the two problems are related.=0A=
=0A=
In March Gary Schmidt reported a similar problem  with access to a gmail ac=
count and Charles suggested running the password program from the getmailrc=
 file in a shell to see if it gave better diagnostic data.=0A=
=0A=
I tried that and found that it generated a new token without any error mess=
ages, but then running getmail still gives the same error message.=0A=
=0A=
So I think maybe the next thing I might try is going back to the beginning =
and getting the Thunderbird client ID and client secret from the source cod=
e again to see if they may have changed.  I'm not sure if this makes sense =
since it still generates a new token using the old ones, but it's all I can=
 think of at the moment.  If anybody gets any further inspiration, I'll be =
listening.=0A=
=0A=
So, for now that's the news from Lake Wobegon.  I'll report back any furthe=
r success or failure.=0A=
=0A=
Regards,=0A=
Donald=0A=