I did some test on our beta testing environnement. First thing, Outlook Android using exchange mode (ActiveSync) still works on latest beta. That's at least a good thing.
Then I did a test configuring the account in Outlook Android as IMAP/SMTP and yes I can confirm it doesnt work.
The result is a popup screen saying I need to check the login/pass of my account.
I've looked through the IMAP logs and discovered something interresting:
[2020.02.10] 06:29:24.370 [220.127.116.11] connected at 10.02.2020 06:29:24
[2020.02.10] 06:29:24.464 [18.104.22.168] command: LCX0 CAPABILITY
[2020.02.10] 06:29:24.464 [22.214.171.124] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=NTLM AUTH=PLAIN UIDPLUS QUOTA XLIST CHILDREN ENABLE CONDSTORE IDLE
[2020.02.10] 06:29:24.464 [126.96.36.199] response: LCX0 OK CAPABILITY completed
[2020.02.10] 06:29:24.558 [188.8.131.52] command: LCX1 AUTHENTICATE NTLM
[2020.02.10] 06:29:24.730 [184.108.40.206] response: LCX1 BAD authentication failed NTLM Failure
[2020.02.10] 06:29:24.761 [220.127.116.11] disconnected at 10.02.2020 06:29:24
[2020.02.10] 06:29:54.823 [IP Unknown] Authentication failed because the remote party has closed the transport stream.
Everytime I try to add the account, there is a connexion from a microsoft owned IP addres that tries to login using NTLM but fails.
My guess here is that Outlook on Android to validate the account verifies it first through some tool on their infrastructure (why the f***?).
The verification is made with NTLM as it is announced by SmarterMail recent builds but it fails. (I triple checked the login/pass).
For SMTP I have nothing in the logs. Here I think that it first checks IMAP but as it fails it aborts and doesn't check SMTP at all.
- There is maybe a global problem with NTLM on IMAP
- Or maybe only when negociating with microsoft client that wants to verify the account.