Godaddy claims MS 365 no longer supports Thunderbird. Apparently MS365 has been systematically blocking such accounts. I just got off the phone with godaddy and they claim there is no fix and of course its Thunderbirds fault. I have been planning to switch away from Godaddy/MS365 anyway, so I guess the time is now

I've called GoDaddy a couple of different times for this problem. In July the person I spoke to said that Microsoft 365 no longer supports Thunderbird, but changing configuration values to what a friend suggested, I got POP to work until a couple of weeks ago.

I called GoDaddy for this recent problem and the person I spoke to, who sounded like a salesperson instead of a technical person, said virtually the same thing and he could sell me a full Microsoft Office package. I thanked him for his "help" and said I didn't want to do that.

I called GoDaddy again yesterday and asked to speak to someone who could walk me through email configuration. The person transferred me to a real honest-to-goodness technician. She patiently walked me through the configuration values and we tried numerous times, but could not get it to work.

My final configuration error was the following. Since it seemed like a Thunderbird or Microsoft error, I sincerely thanked her for her help. I don't know what to do now. I was using Eudora when Thunderbird appeared on the scene and easily transitioned to that. I've got decades, I believe, of email history. Sure, I can just keep that in the Thunderbird client and even though I can no longer send or receive email from that client, I can use it as a historical record for searching old mails. I just don't know which client to change to. Outlook 365 is totally useless for me because I can't import or export mail lists or emails.

Here's the configuration error I got:

Message: AADSTS165000: Invalid Request: The user session context is missing. Do not copy the user context values (cookies; form fields; headers) between different requests or user sessions; always maintain the ALL of the supplied values across a complete single user flow. Failure Reasons:[Missing session context cookie;Token values do not match;]