2
Anyone using SM v14 and EWS with eM Client?
Question asked by Joe Burkhead - 1/14/2016 at 11:00 AM
Unanswered
Does anyone here run SmarterMail 14 with EWS and use eM Client for their user interface? Interested in pursuing this, but don't really want to buy the EWS add-on from SmarterTools only to find that there are things not working right. Would appreciate any insight.
 
Thanks!

12 Replies

Reply to Thread
0
Employee Replied
Employee Post
Hey Joe! I don't personally use eM Client, but I wanted to let you know that you can test a trial of EWS before purchasing! In your SmarterMail install, go to Settings > Activations > Licensing. You can select the EWS add-on an click Start Trial to get 30 days free. Then follow these steps to configure:
 
 
Hope this helps!
0
Joe Burkhead Replied
Thank you, Andrea. I have enabled the trial, and have followed the article that you linked. It connected, pulled in my email, but is not pulling in my calendar or my contacts. I read the info on the eM Client site as well, it just states what is in your link. So...still not able to get my calendar or contacts. Confused as to why or what else I can do.
 
Joe
0
Nathan Replied
emClient works with the smartermail EWS implementation for mail, calendar and contacts. There was nothing special to setup, it just worked. Perhaps you are connecting via IMAP rather than EWS ?
0
Joe Burkhead Replied
Thanks for your answer, Nathan. When I setup eM Client I used the automatic setup, just gave it my email address and it found my server settings. Then entered my account credentials and it auto configured everything. I didn't specify IMAP, is there a way to find out what it is actually using?
0
Nathan Replied
Hi Joe, It does not specifically state the account type within the settings. However, try going to Tools > Accounts. This should list the accounts configured. For the EWS account I see the name then on the next line 'Mail, Calendar, Contact'. I have not got an IMAP account configured but presume it would say 'Mail' only.
0
Joe Burkhead Replied
Thanks again, Nathan for trying to help.
 
Mine does not show Calendar and Contact within the Accounts section of eM Client. Only shows Mail. And there is an IMAP tab and an SMTP tab as well. So, I guess it is obvious that it is not picking up the EWS. I show EWS as active within the Licensing area of SmarterMail. I have used the auto method of eM Client to set it up...not sure why it is not finding EWS. And no one from SmarterTools seems to be too interested in giving me some pointers. :-(
0
Nathan Replied
That's a separate issue. The annual smartermail tax for a 'new' version which for the most part seems the same as previous does irritate slightly too. And do not mention that SmarterTools do not allow you to downgrade your ActiveSync license without it first expiring. They designed it this way but are not interested in helping paying customers. Given the 'exchange replacement' tag I do wonder sometimes...

Anyway, back to the point. We have implemented the correct A/SRV records so that is why it autodetects. See the following for more info:

https://portal.smartertools.com/kb/a2752/set-up-autodiscover-for-smartermail.aspx

If you add new account but choose 'Mail' rather than 'Automatic Setup', then choose 'Exchange' it will add the account as EWS. In doing so you will see Mail, Calendar and Contacts.
0
Joe Burkhead Replied
Nathan,

I already had those exact settings configured. I have tested using nslookup and the autodiscover settings (both A and SRV records) do point to my SmarterMail server's external IP address. Really strange...this morning I disabled IMAP totally in the server admin pages. Even so, SM still connects to eM Client using IMAP!!! I am beginning to think this is a bug!
0
Nathan Replied
Have you configured the hostnames for auto detection in the protocol settings in SmarterMail ?
0
Joe Burkhead Replied
Are you referring to the EWS tab under protocol settings? If so, I have configured "mail.mydomain.org" for autodiscover. Is that where you refer to?
0
Joe Burkhead Replied
Well, I totally uninstalled eM Client, removed all leftover folders on my hard drive, cleaned the registry of any references to eM Client, then reinstalled and attempted to reconnect. It threw connection errors at me, so I am including the log file. Anyone make any sense out of this?
 
10:10:15 AM Online state: changed to online due to NetworkAvailability
10:10:19 AM user@somewhere.org [Exchange Web Services]  Synchronizing folder list
10:10:20 AM   MailExceptions.OperationException: Synchronizing folder list failed due to the following error: The expected XML node type was Element, but the actual type is EndElement. ---> Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializationException: The expected XML node type was Element, but the actual type is EndElement.
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read(XmlNodeType nodeType)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.EwsXmlReader.InternalReadElement(XmlNamespace xmlNamespace, String localName, XmlNodeType nodeType)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadResponse(EwsServiceXmlReader ewsXmlReader)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponseXml(Stream responseStream)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponse(IEwsHttpWebResponse response)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder(FolderId folderId, PropertySet propertySet)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeFolderSynchronizer.GetFolderList(Folder homeFolder, CancellationToken cancellationToken)
10:10:20 AM    at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass5.<EnqueueGetFolderList>b__0(WorkerStatus status, CancellationToken cancellationToken)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    --- End of inner exception stack trace ---
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    at MailClient.Commands.Command.Process(WorkerStatus status)
10:10:20 AM   MailExceptions.OperationException ---> Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializationException: The XML document ended unexpectedly.
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SoapFaultDetails.ParseDetailNode(EwsXmlReader reader)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SoapFaultDetails.Parse(EwsXmlReader reader, XmlNamespace soapNamespace)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadSoapFault(EwsServiceXmlReader reader)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ProcessWebException(WebException webException)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ExchangeService.SubscribeToPullNotifications(IEnumerable`1 folderIds, Int32 timeout, String watermark, EventType[] eventTypes)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeInboxWatcher.<GoOnline>b__0(WorkerStatus s, CancellationToken c)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    --- End of inner exception stack trace ---
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    at MailClient.Commands.Command.Process(WorkerStatus status)
10:10:20 AM user@somewhere.org [Exchange Web Services]  Synchronizing folder list
10:10:20 AM   MailExceptions.OperationException: Synchronizing folder list failed due to the following error: The expected XML node type was Element, but the actual type is EndElement. ---> Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializationException: The expected XML node type was Element, but the actual type is EndElement.
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read(XmlNodeType nodeType)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.EwsXmlReader.InternalReadElement(XmlNamespace xmlNamespace, String localName, XmlNodeType nodeType)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadResponse(EwsServiceXmlReader ewsXmlReader)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponseXml(Stream responseStream)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.ReadResponse(IEwsHttpWebResponse response)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder(FolderId folderId, PropertySet propertySet)
10:10:20 AM    at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeFolderSynchronizer.GetFolderList(Folder homeFolder, CancellationToken cancellationToken)
10:10:20 AM    at MailClient.Protocols.Common.FolderSynchronizer.<>c__DisplayClass5.<EnqueueGetFolderList>b__0(WorkerStatus status, CancellationToken cancellationToken)
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    --- End of inner exception stack trace ---
10:10:20 AM    at MailClient.Protocols.Exchange.ExchangeGenericCommand.Execute(WorkerStatus status)
10:10:20 AM    at MailClient.Commands.Command.Process(WorkerStatus status)
 
0
Nathan Replied
Yes - it sounds like it is configured correctly.

Reply to Thread