Does Smartermail autodiscover work's fine with Outlook 2016 and Outlook 365 without MAPI?
Problem reported by CLEBER SAAD - 9/13/2025 at 9:13 AM
Submitted
Hello Everybody,

Here we are trying to configure the Outlook 2016 and 365 to use only IMAP/SMTP. The autodiscover are corrected configured but Outlook can't use the SMTP port 587 or 465/w/SSL. Always try to use port 25 (in the XML are 587 correctly) and next screen need to edit and change to 587 and enable authentication.

Another problem it's if we Enable the Everride Desktop XML and click Generate, Outlook always trying to connect to MAPI (the account does not have this procotol enabled), because the XML it's not fieltered by smartermail (only filter with don't use the custom desktop xml).

So, anybody working without any problems with autodiscover in Outlook 2016+ or 365 with SMTP/IMAP only?

Using the latest version of SM.

Regards, Cleber
Derek Curtis Replied
Employee Post
You may want to take a look at this KB article: https://portal.smartertools.com/kb/a3747/autodiscover-dns-records.aspx

We've seen issues where Outlook attempts to autodiscover from Microsoft Cloud IPs, since that's what it connects to first, and it looks for specific connections. We've found that the autodiscover records listed for Outlook 2024+ seem to resolve this issue. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
Douglas Foster Replied
Autodiscover works much better if you use registry keys on the client to limit the process to less than all 7 of tits available techniques.   This presumes that you can deploy registry keys to most users via group policy.   Here is a post that I wrote on the subject several years ago.   It is unfortunate that the substance of it was not added to the KB article mentioned by Derek.

Reply to Thread

Enter the verification text