Outlook 2016 doesn't accept password or app password

Anonymous
2024-01-25T09:40:42+00:00

I have this problem - Outlook 2016 doesn't accept password or app password - and i think it is a growing World wide Microsoft problem :-(

See also here: https://www.reddit.com/r/Outlook/comments/19dx64p/outlook_2013_windows_10_suddenly_not_accepting/Outlook gives me this: (startede yesterday)

I have 2 PC's with HOTMAIL accounts in Outlook 2016 ...

They both have this error.

I do get mails ... but I can´t send mails. Yesterday it did work for 1-2 hours ... but right now the error is there all the time :-(

Please help me.

Thanks in advance

Pierre

Outlook | Windows | Classic Outlook for Windows | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

862 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-09T12:56:05+00:00

    Another authentication error. EAS server. Email client: 9Folders. Outlook.com accounts.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-03-09T10:26:28+00:00

    A million words have been shared on this encompassing theories and fixes. What seems to be certain is that the intermittent nature of the issue proves that most of us are wasting our time changing settings most of the time - something's broke at MS, deliberately or not.

    How else do you explain, as in my case, Outlook 2013 successfully processing mail (apart from the prompts) all through this epic issue until two days ago when mail stopped getting through and started up again? Up yesterday, down today

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-03-08T21:59:57+00:00

    Hi guys, I think I found a solution (at least for mobile users).

    1. download app outlook mobile (even if you have no intention of using it actively), add the accounts of interest and give it all background permissions, excluding it from any battery optimizations. Go to the app settings and for each account in which you are interested in also synchronizing contacts and/or calendar, select the relevant options "synchronize contacts" and/or "synchronize calendars". In this way, the "Outlook" category will be added within the Android system accounts, which will allow system-wide synchronization and should be viewable/usable by any third-party app (in theory).

    I've already tried this method weeks ago. It has multitude of issues. You are essentially using Outlook for Android to handle the contact/calendar sync only. Outlook for Android would store data within the scope of the app itself, i.e., app-local databases. You then enable its sync to the device-global contact and calendar database, so then you can access those data via the stock calendar and contact apps and even email client when looking up contacts. The issue is, the moment you enable this, Outlook for Android would then have access to your device-global contact and calendar databases, which is a 2-way access, including reading data from other accounts you may have added, but wanted to shield Microsoft from accessing. This method is just another way to do proxying. This is the exact method how apps like Facebook scrape your contacts and so on...

    I was talking to some security/privacy experts and they see a strong indication Microsoft is messing with the EWS/EAS on purpose. By forcing us to use Outlook mobile client, they then could scrape data on our devices from other platforms. This is certainly how I would design it if I want to backdoor access user's 3rd party platform data.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-03-08T21:39:26+00:00

    Yet another authentication error on EAS 9Folders, outlook.com account.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-03-08T19:39:44+00:00

    P.S. From what I understand (but I could be wrong), OAuth also now makes the "app password" useless and outdated, since I believe it only makes sense in combination with basic authentication.

    That's the intention. But for apps which don't support OAuth2, app passwords are a compromise.

    Was this answer helpful?

    0 comments No comments