7430 Beta - Can't get MAPI to work

Problem reported by David Fisher - 5/6/2020 at 12:55 PM

Resolved

Hi,

I have not been able to get MAPI working with the SmarterMail Beta's.

The latest issue is, if I try to enable MAPI/EWS or EAS, it says I have exceeded my license, even though I am using the public Beta key and I am well below the unlimited mailboxes for EWS/MAPI and well below the 25 limit of EAS.

For the accounts that shows enabled, but grayed out, so I cannot disable them, Outlook 2016 says It cannot connect, and tries to use insecure but that fails

Thanks!

-dave

8 Replies

Reply to Thread

David Fisher Replied

5/6/2020 at 2:11 PM

Update: I figured out the enable/disable issue, and this seems like a bug, if I am at the specified domain limit, I cannot enable more EAS, EWS/MAPI, which makes complete sense, but I also CANNOT disable the services, it grays the toggle completely for the people that are turned off and also turned on. *NOTE* I can right click on the user account and Enable/Disable just fine there, it is when I edit the user and go into the toggles.

I still CANNOT connect my Outlook 2016 to my MAPI server. It gives an error and nothing shows in the logs. It just keeps asking for my email and password over and over.

Thanks,

-dave

Employee Replied

5/6/2020 at 2:14 PM

Employee Post

David, thank you for reporting the issue about licensing and the EAS/EWS/MAPI toggles. I have added it to our bugs list. I'll update you when the fix is in place.

David Fisher Replied

5/6/2020 at 2:30 PM

Hi Robert,

Thank You

Another possible bug - I went into settings of Autodiscover MAPI, and it shows SSL on, there is no way to turn it off.. I noticed under EAS and EWS a message up top "SSL encryption is always enabled for EWS." So I am guessing this is also for MAPI and the message needs to be added.

Still trying to get MAPI working -- Update 2:

I get the following error manual setting up Office 365 account in Outlook 2016.

An encrypted connection to your mail server is not available. Click Next to attempt using an unencrypted connection.

I hit next and it goes back to the manual config screen for Office 365.

For testing purposes I disabled POP, IMAP and SMTP In Autodiscover, as sometimes it sets my account up as IMAP.

I have an SSL cert installed for HTTPS:// Port 443, through IIS, using Free Let's Encrypt, do I need a working Certificate on any of the Protocols, POP3, IMAP, SMTP, etc?

Thanks!

-dave

Employee Replied

5/6/2020 at 2:35 PM

Employee Post

David, I can get that banner added for the MAPI autodiscover modal.

Employee Replied

5/6/2020 at 4:18 PM

Employee Post

David, the banner has been added and the issue when a domain exceeds the EAS or MAPI/EWS limits the admin cannot disable the Service Access for that protocol has been fixed.

Regarding setting up SSL on POP3, IMAP, or SMTP is not necessary since those protocols don't use HTTP/HTTPS connections.

Sébastien Riccio Replied

5/6/2020 at 6:27 PM

It's not needed, but not using SSL or STARTTLS on those protocols would allow clear text authentication. In 2020 this shouldn't be allowed at all.

Authentification should only be allowed if the client is using SSL port of these protocols and/or STARTTLS !

Anyone could easily sniff passwords if you're accessing your mailboxes with these protocols on a compromisd public network ....

Sébastien Riccio

System & Network Admin

https://swisscenter.com

David Fisher Replied

5/12/2020 at 11:38 AM

Hi Robert,

Looks like the latest builds fixed those minor issues.. But I guess I am the only one that CANNOT even get MAPI setup in my Outlook. The MAPI log file is blank. It just seems it WILL NOT accept my email and password, other logs show authentication failure.

Only thing I have not done, is delete my install of SmarterMail and setup as brand new. I have deleted all configuration from Outlook and followed the KB articles on removing and setting up MAPI, but no go.

Thank You,

-dave

Christopher Shirley Replied

5/13/2020 at 8:07 AM

Hi Dave,

Just speaking from my own experience here I had some issues but i figured out it was mostly with my Auto discover configuration in DNS, etc.

I have attached a tool that will allow you test your Auto Discover configuration to see if its accurate. If its not you will get an error or wrong response.

If you do get an error, I could tell you what I did to solve it and maybe that will help.

Thanks,

Chris

AutoDiscoverXMLTool.zip

Back to Community Threads

Reply to Thread

Enter the verification text