Subject: | |
From: | |
Reply To: | |
Date: | Fri, 29 Sep 2017 11:29:27 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 09/28/2017 02:10 PM, Yasha Karant wrote:
> Supposedly, I am using office365 that you indicate is IETF IMAP compliant.
Arguable, laughable, but yes, it usually works well enough.
> The diagnostic on failure states "authenticated but not connected".
They are having world-wide issues with IMAP over the last week or so. Your mailbox may be affected while your co-worker is not.
To verify if you are affected:
openssl s_client -connect outlook.office365.com:993 -crlf
...
* OK The Microsoft Exchange IMAP4 service is ready. [TQBXAEg...AbwBrAC4AYwBvAG0A]
. login username@yourdomain [password]
. OK LOGIN completed.
. LIST "" *
. BAD User is authenticated but not connected.
. LIST INBOX *
. BAD User is authenticated but not connected.
* BYE Connection closed. 14
read:errno=0
|
|
|