2
autodiscover.xml erro response
Problem reported by Sérgio Rocha - 2/23/2024 at 3:29 AM
Submitted
Hi,

After the upgrade to version 87xx we receive complains about spark mail and I think that is because of autodiscover process.

I read the KB about autodiscover and at the end the article says that we should test de URL https://server/autodiscover/autodiscover.xml. When I try to test I get an authentication request and after login I get this error:

Invalid XML Request - Error: Domain does not exist.
   at MailService.Remoting.Mail.GetDBFoldersDomainStatic(String domainName)
   at SmarterMail.Protocols.AutoDiscover.AutoDiscoverProcessor.ProcessAsync(), 

Its some think wrong it this reposnse, right?

Regards,

SR

6 Replies

Reply to Thread
1
J. LaDow Replied
Autodiscover is only for mailbox holders on your server to configure their client application to connect to your server and retrieve/send their email.

Autodiscover should have NO effect on outside mail servers and interaction such as exchanging mail with your server.

Things that affect communications between your server and others can include SPF, DKIM, DMARC, TLS connectivity, and your server's reputation on outside block lists or reputation regarding spam and abuse.
MailEnable survivor / convert --
1
Sérgio Rocha Replied
Hi J. laDow,

Thanks for your response, I know what is Autodiscover. The point is: after the upgrade to last version (from 8667) Spark Mail clients (mail client like outlook) start to get an error on login and I think that is because the SM autodiscover its not working well.

Regards,
SR
0
J. LaDow Replied
That would mean you're most likely having issues with how the new version handles SSL certificates and whether or not you have SM manage your certificates. There were MAJOR changes to how SM operates in this fashion. It's one of the reasons we've held back upgrading yet.

Autodiscover relies a lot on the certificates for determining legitimacy of the endpoint offering the autodiscover response.
MailEnable survivor / convert --
0
Juan Lai Replied
Do you fix this issue fianlly? I've found we have the same message.

Invalid XML Request - Error: Domain does not exist.

Server stack trace: 
   於 MailService.Remoting.Mail.GetDBFoldersDomainStatic(String domainName)
   於 System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   於 System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   於 System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   於 System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   於 SmarterMail.RemoteInterface.IMail.GetDBFoldersDomain(String sessionStr, String domainName)
   於 SmarterMail.Logic.Remoting.RemoteWrapper.SessionCallWithConnection[T](UserData usr, Func`2 f)
   於 SmarterMail.Web.SyncProtocols.AutoDiscover.AutoDiscoverProcessor.DoWork(Object workItemState), 

0
Kyle Kerst Replied
Employee Post
I am going to do some client testing to see if I can replicate these behaviors on our latest release. In the meantime, it is expected to see responses like this when probing the autodiscover system manually as it is expecting an autodiscover-style response. I should know more once I complete my testing though so I will keep you updated!
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com
0
Kyle Kerst Replied
Employee Post
I was able to complete some initial testing on this for you and found autodiscover isn't handled well by the Spark email client, though we are providing an expected autodiscover response. This was previously investigated by our development team and they determined the Spark autodiscover process is likely problematic, and a ticket should be opened with their team for more information. With that being said, I did find EWS/IMAP/etc function as expected under manual account setup in the meantime. 
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Reply to Thread