I am assuming that you are trying to setup an account in Outlook 2019, or Office365 (that is the only version that seems to work at the moment)  If so, then check these items:

1) Have you setup Autodiscover in DNS for the domain? 

2) Do you have an SSL certificate bound to your ports?

Exchange mode requires SSL/TLS and autodiscover to enable MAPI mode.

Hope this helps.

In my initial testing, you *might* also need to enable EAS for the mailbox so that the correct combination of jibberish is returned in the autodiscover.xml file that Outlook grants your wishes to connect using MAPI.  It is really, really frustrating to see just how inconsistent Outlook is behaving.

In the test domain I use, I have EAS turned off and it connects to MAPI fine.

I might have turned it off AFTER the account was setup but I dont think EAS is needed.

I was able to use MAPI without EAS, however, my Outlook client would never download new mail, it only sync the mailbox as is and then it never downloaded new email. I did find quite a few registry tweaks though when messing around with it in relation to telling Outlook to ignore O365.

So... with the new MAPI, is EAS and EWS/MAPI still add-on products that must be purchased separately from SmarterMail?  Or is this all included now in the MAPI builds?  And if so will it be in the future as well or just during the BETA period?

Rod,

It is included in the MAPI public beta.  In the future, it will need to be purchased as an add-on to SmarterMail Enterprise.

So... you are creating a SmarterMail MAPI … but we must then purchase the MAPI.

Am I the only once that sees this as counter-productive?

I dont see no  problem with it.

What is it you see as counter-productive?

Only thing thats really upsetting is that we paid for MAPI in August and its still not in production.