Hit ENTER after each Tag to add it to your post; Numbers in parentheses represent the Tag's usage.
Looking for an update on the status of autodiscover correctly configuring Outlook 2013.
Von Ausin, it appears our ticket (2C1-1B994A76-0A78) has been removed from our account as it it no longer in our ticket history. To recap:
Sorry for the delay.
I had discussed this issue with our developers, and right now Autodiscovery with EAS and EWS appear to configure Outlook 2013 and Outlook 2011 for Mac as an Exchange connection utilizing MAPI and not through EAS (Outlook 2013) or EWS (Outlook2011 for Mac).
This is based on the XML data returned to these clients when the Auto discovery process has been ran. We were able to replicate the same behavior within our test environment.
Changing this process will need to be a core change to SmarterMail. Each change to the EAS\EWS protocol must be tested against a wide range of clients to ensure the process does not get broken for more devices and clients. Please also note that the clients themselves control what protocols and methods they prefer based on the data returned, some clients will prefer IMAP\SMTP over EAS or EWS, this is something we do not have control over.
With that being said, the behavior has been reported and will be improved on in the next major release of SmarterMail.
In the mean time EAS and EWS accounts must be setup manually. I do apologize for the inconvenience in caused by this. I've refunded this ticket back to your account for future use as well since this will be improved on.
Please let me know if you have any questions or concerns.
We've no been through 5 minor releases and a major release and are still unable to use Outlook as if it was actually connected to an Exchange server. This update was from September of last year and this has still not been fixed. We also did not get the ticket refunded to us as was mentioned in this ticket.