Outlook | Windows | Classic Outlook for Windows | For business
Using classic Outlook for Windows in business environments
email sent with 4 impacted accounts.
Outlook 2016 doesn't accept password or app password
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
862 answers
Sort by: Newest
-
Anonymous
2024-01-30T22:37:11+00:00 -
Anonymous
2024-01-30T22:36:46+00:00 Well here's the thing, 9Folders claim they know what the issue is, but they actually don't.
They claim sending authentication data in plain text (over tls port 993, of course) fixes the issue, but it doesn't.
Below are 10 identical IMAP connection attempts, all over tls port 993, all plain text auth with identical credentials.
As you can see only 2 of the 10 plain text auth attempts succeeded.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADQAUAAyADYANQBDAEEAMAAwADIANAAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADIAUAAyADYANQBDAEEAMAAxADkAOAAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 OK LOGIN completed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADYAUAAyADYANQBDAEEAMAAwADAAMwAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADIAUAAyADYANQBDAEEAMAAxADIAOQAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADYAUAAxADIAMwBDAEEAMAAwADIAMwAuAEcAQgBSAFAAMQAyADMALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADQAUAAzADAAMgBDAEEAMAAwADEANgAuAEcAQgBSAFAAMwAwADIALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 OK LOGIN completed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADQAUAAyADYANQBDAEEAMAAxADkANQAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADQAUAAxADIAMwBDAEEAMAAxADAANQAuAEcAQgBSAFAAMQAyADMALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADQAUAAxADIAMwBDAEEAMAAxADIANgAuAEcAQgBSAFAAMQAyADMALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
* OK The Microsoft Exchange IMAP4 service is ready. [TABPADIAUAAyADYANQBDAEEAMAAwADUAMQAuAEcAQgBSAFAAMgA2ADUALgBQAFIATwBEAC4ATwBVAFQATABPAE8ASwAuAEMATwBNAA==]
a1 NO LOGIN failed.
* BYE Microsoft Exchange Server IMAP4 server signing off.
-
Anonymous
2024-01-30T22:19:49+00:00 Thanks for catching that. I edited my post so it would show up correctly.
-
Anonymous
2024-01-30T22:11:56+00:00 Hi all,
I apologize for the delay getting back to you. I am working with the service teams investigating the issue. It is being worked as a priority incident.
The service teams asked me to get some email accounts for users that were affected when the issue started. If you are willing to share your outlook.com email address and what client you were connected with, and when the issue started for you, please send me an email with that info to *** Email address is removed for privacy ***. I'll come back and edit the post after I get a few replies.
The service team is already working on a solution, but they want to confirm against the service logging with repro accounts that it matches up with the issue.
So, supposedly, you're a Microsoft Agent/Moderator and you didn't know that if you type an email address here, it will be removed? Funny.
Did you saw the link I sent? The developers of OfficeMail Pro app already found what's the issue. Maybe it would be good for you and "service teams" to read it.
It started 2 or 3 days ago. The app I use is the OfficeMail Pro.
-
Anonymous
2024-01-30T22:00:45+00:00 Hi all,
I apologize for the delay getting back to you. I am working with the service teams investigating the issue. It is being worked as a priority incident.
The service teams asked me to get some email accounts for users that were affected when the issue started. [Edit] Thank you to those that responded and provided your repro account specifics. I have shared that to the service teams working on the incident.
The service team is working on a solution, and we should have an update shortly. I'll post back with an update tomorrow 1/31/24.