You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am provided with [email protected] as my address. I can access the mailbox associated with that address as provided by my university at https://mail.university-name.edu.country-tld. It prompts me to log in with the credentials of the form:
firstname.lastname
password
like so:
then I am greeted with
this is what I see when I log out
I have been told that I can connect to it with Davmail. I launch Davmail with the following configuration:
I then start Thunderbird and configure it as follows:
I get the following messages in the logs:
Furthermore, after decrypting traffic between Davmail and the exchange, I find this:
I can do GET /EWS/Exchange.asmx from my browser but it prompts me with a basic HTTP auth, which after I feed my credentials, redirects me to this thing that looks like an XML
Davmail instead receives 401 Unauthorized because it doesn't authenticate with the credentials I typed in Thunderbird.
How can I make Davmail use my username and password in the HTTP requests to the exchange? Is there something wrong with the way I'm using it?
Thank you in advance
The text was updated successfully, but these errors were encountered:
@halvabner : In your Thunderbird configuration, have you tried specifying [email protected] for the username instead of firstname.lastname? I know firstname.lastname doesn't work with my DavMail/O365 setup and IMAP client.
Also, I'm not sure about davmail.mode=EWS, but I don't think the currently released version of DavMail supports a davmail.url property setting that looks like *.country-tld for davmail.mode=O365Manual or O365Interactive. The next version should though as changes for this have already been committed to the code repository.
I am provided with
[email protected]
as my address. I can access the mailbox associated with that address as provided by my university athttps://mail.university-name.edu.country-tld
. It prompts me to log in with the credentials of the form:like so:



then I am greeted with
this is what I see when I log out
I have been told that I can connect to it with Davmail. I launch Davmail with the following configuration:
I then start Thunderbird and configure it as follows:






I get the following messages in the logs:
Furthermore, after decrypting traffic between Davmail and the exchange, I find this:
I can do
GET /EWS/Exchange.asmx
from my browser but it prompts me with a basic HTTP auth, which after I feed my credentials, redirects me to this thing that looks like an XMLDavmail instead receives
401 Unauthorized
because it doesn't authenticate with the credentials I typed in Thunderbird.How can I make Davmail use my username and password in the HTTP requests to the exchange? Is there something wrong with the way I'm using it?
Thank you in advance
The text was updated successfully, but these errors were encountered: