#584 Authentication fails after davmail tries to locate autodiscovery at wrong domain

[Lectrode]

I've been at this issue for quite about a week now; I am unable to successfully authenticate through davmail.

The company I work for set up their exchange server as follows:

user@company.com
companywebmail.com - exchange server
Exchange Server 2013
Microsoft IIS 7.5
IMAP disabled
SMTP disabled

(All occurances of the company name, user name, password, etc in the attached log have been replaced with generic or removed)

I have taken the workarounds mentioned at the following discussion into account with no success:
https://sourceforge.net/p/davmail/discussion/644057/thread/3540b14f/?limit=25

Created as bug because it doesn't seem like it should be trying to resolve "autodiscovery.company.com", but I don't know enough about the inner workings of this software to say for sure.

[Mickael Guessant]

According to your log file you didn't set path to https://www.companywebmail.com/ews/exchange.asmx

The autodiscover is a failover that will only work if your company DNS is configured correctly

[Lectrode]

Thank you for the quick response. I had tried using /ews/exchange.asmx instead of /owa in my previous attempts. Here is the log (removed) using that instead of /owa. I've also tried adding a forward slash (/) to the end of the url even though that particular bug was marked as fixed. Authentication still fails.

Just to be clear on what I've tried as far as credentials go: I am including the exchange user domain with the login username (domain\username). I have also tried just username and username@company.com.

[Lectrode]

Thank you for your continued effort in this matter. Unfortunately, even
with the latest patches it does not successfully authenticate. I believe
EWS is disabled server-side; I can't even use Outlook to connect to the
exchange. If you try to specifically browse to
http://www.[companymail].com/ews/exchange.asmx you are redirected to
http://www.[companymail].com/owa . I'm not sure if any changes to
davmail would provide a workaround to use a desktop client with the
server-side limitations that are in place.

Regards,

Steven Hoff

On 02/17/2015 06:27 PM, Mickael Guessant wrote:

• status: open --> pending
• Comment:

Please try again with 4.6.1, the recent Office365 patch may help

---

[bugs:#584] http://sourceforge.net/p/davmail/bugs/584
Authentication fails after davmail tries to locate autodiscovery at
wrong domain

Status: pending
Group: v4.5.1
Labels: authentication audodiscover ntlm
Created: Thu Oct 30, 2014 02:01 AM UTC by Lectrode
Last Updated: Fri Dec 12, 2014 02:52 AM UTC
Owner: nobody

I've been at this issue for quite about a week now; I am unable to
successfully authenticate through davmail.

The company I work for set up their exchange server as follows:

user@company.com
companywebmail.com - exchange server
Exchange Server 2013
Microsoft IIS 7.5
IMAP disabled
SMTP disabled

(All occurances of the company name, user name, password, etc in the
attached log have been replaced with generic or removed)

I have taken the workarounds mentioned at the following discussion
into account with no success:
https://sourceforge.net/p/davmail/discussion/644057/thread/3540b14f/?limit=25

Created as bug because it doesn't seem like it should be trying to
resolve "autodiscovery.company.com", but I don't know enough about the
inner workings of this software to say for sure.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/davmail/bugs/584/
https://sourceforge.net/p/davmail/bugs/584

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/
https://sourceforge.net/auth/subscriptions

[Mickael Guessant]

Please try again with 4.6.1, the recent Office365 patch may help

[Mickael Guessant]

Should work fine with latest version