November 1 – basic auth is really being shut off

Topic

New Reply

PK reminded me of this the other day: New minimum Outlook for Windows version requirements for Microsoft 365 – Microsoft Tech Community What is it? Mi
[See the full post at: November 1 – basic auth is really being shut off]

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

abbodi86

Reply | Quote

Replies

Glad I never used Microsoft Office.

Reply | Quote

11 years finally retiring Outlook 2010 isn’t unreasonable at all. And like I said, basic authentication should be killed off.  These older email clients weren’t built for newer authentication.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I have just contacted 1 and 1 in the UK and they will not be affected. (I use Outlook 2010)

Chris
Win 10 Pro x64 Group A

Reply | Quote

I have two desktop PCs for home use, neither uses Outlook although one has Outlook 2010 installed as I use Office 2010 (protected by 0patch) on that machine. Both access a hotmail email account through the Chrome browser, and clicking on the top left icon on the email account page shows Office 365.  My ISP is Virgin Media in the UK and I haven’t found any relevant forum announcements or posts on the subject there.

Am I right in assuming this change won’t affect browser-based email access in my circumstances?

Reply | Quote

My way or the Highway. Thus it has always been, thus it will always be.

Alas.

Reply | Quote

Susan Bradley wrote:

These older email clients weren’t built for newer authentication.

By newer authentication you mean the new passwordless authentication ?

Reply | Quote

No. “Modern authentication”:

Modern Authentication vs. Basic Authentication

How modern authentication works for Office 2013, Office 2016, and Office 2019 client apps

5 users thanked author for this post.

Tom-R, Perq, windbg, Noel Carboni, Alex5723

Reply | Quote

I had to use Outlook + Exchange Server at work, and learned to hate it:
1.   PST files get corrupted.
2.  PST files have a practical size upper limit, but it’s not documented.
3.  PST files have to be periodically scanned to uncorrupt them (scanpst.exe).
4.  The search function is un-intuitive, undocumented e.g., what, exactly, are “well-known fields”?), and disfunctional.
5.  Addresses in X.400 format cannot be replied to if you’re outside the Microsoft universe.
6.  The Outlook calendar is incompatible with other calendering systems.

If my ISP compelled me to use Outlook I would take my email hosting somewhere else.

Reply | Quote

Just out of curiosity, what email client are you using now?

Reply | Quote

Thunderbird.

Reply | Quote

I wonder is secure pop3 staying around in Office 2010?

Reply | Quote

I’m gettin’ old, but I’m not at all allergic to learning new things or working with technical details. So why can’t I just tell easily whether the Outlook 365 client I have will continue to be able to read my eMail from the iPage eMail service I have had handling my domain eMail for years? I have not re-entered or re-configured my account settings in a long time, though it IS and has been set up all along to use SSL. Today I can still get eMail from all my accounts. From what I’m reading SSL will be no longer “enough”.

Reading here, I think I should assume I will one day soon just stop receiving my domain eMail, and there may be some way to recover functionality that will only become apparent after more research. Or maybe time will pass before someone makes that available.

Not acceptable!

That would be arguably the worst possible way to find out I have been led down a blind alley to an unworkable combo of software and services.

A search online doesn’t show any evidence my ISP has any kind of advanced authorization setup. It still just shows pop or imap settings for clients, including Outlook 365:

https://www.ipage.com/help/article/email-client-setup-outlook-2016-and-microsoft-365

So, seriously, how can one even tell what’s doing what level of auth to avert an emergency outage? Am I okay if I have the Outlook 365 client?

-Noel

1 user thanked author for this post.

Cybertooth

Reply | Quote

At work, we use Outlook 2003 on Windows Xp for email. It seems will not have access to email soon…Great. Thanks for the info.

Reply | Quote

OK – you’re all going to laugh.

I am still using Outlook 2003 on my XP machine for my personal emails with verizon.net (run by aol) and on my wife’s domain (run by Network Solutions).

Yes, I should move everything to my Win 10 Pro 64-bit machine with MS 365, but I am really lazy.  (And I am not sure how to do that and maintain a unified Inbox with all my old emails on Outlook in MS 365.)

But … will my antique setup stop working on November 1?  Or is it so old it’s BEFORE this auth?

Thanks.

 

Reply | Quote

I forgot to say that both email accounts coming into my Outlook 2003 are POP3 with “leave a copy of email on server”.

So – will my Outlook 2003 on my XP stop working on Nov. 1   ????

Thanks.

Reply | Quote

Your question about November 1st is hitting very close to an issue I’m having right now! HELP!!

I have a client using Outlook 2010 on a protected Windows 7 system with a pop3 verizon.net address that completely stopped sending or receiving emails overnight at the beginning of September. Logging in through AOL’s web interface verifies the username & passwords are correct but Outlook continually fails to authenticate either sending or receiving any emails.

Is this issue related to the “basic-auth” thing or something else? Would setting his account up as  an IMAP account instead fix his problem or not?

Reply | Quote

I say it’s about time. I support a small department at a University, and Gmail forced a switch to OAuth2 authentication (Google’s version of “Modern” authentication) in July 2020, over a year ago. We use the Thunderbird 64bit email client with Google’s IMAP server, and there were no issues switching over.

Reply | Quote