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 feel like there's essential information missing for people who are less experienced with mail autodiscover. Fortunately, this repo seems much more complete than other repositories available. However, this also brings the complexity of slight differences between each supported client. For this reason I think a sort of setup guide is missing.
I think it would be nice to get an overview of each exported page and to which client it belongs. You also have utility pages such as the Apple mobileconfig and the dns-zone.
I found the following routes and my interpretation of it's use.
method
path
client/usage
GET
/
UI welcome page
GET
/apple
UI page to get the Apple mobileconfig
GET
/email.mobileconfig?<email>
Route that uses the email query and host header to generate the mobileconfig
autodiscover Android MyMail, Android Spike Email, Outlook Android, Office Pro Plus 2013 & 2021 (multiple routes for different letter casing)
POST
/autodiscover/autodiscover.xml
autodiscover Outlook Android, Office Pro Plus 2013 & 2021 (multiple routes for different letter casing)
GET
/robots.txt
Search engine indexing page
GET
/version
Report of the app version and description
GET
/ping
Pong response message
Most or all autodiscover routes also seem to use the host header to set the DomainName fields in the response.
I am expecting this project should be published on autodiscover.domain.tld to function properly, as suggested by the DNS records generated by dns-zone and the fact that a index path is used for the Apple mobileconfig page.
The text was updated successfully, but these errors were encountered:
I feel like there's essential information missing for people who are less experienced with mail autodiscover. Fortunately, this repo seems much more complete than other repositories available. However, this also brings the complexity of slight differences between each supported client. For this reason I think a sort of setup guide is missing.
I think it would be nice to get an overview of each exported page and to which client it belongs. You also have utility pages such as the Apple mobileconfig and the dns-zone.
I found the following routes and my interpretation of it's use.
/
/apple
/email.mobileconfig?<email>
/mail/config-v1.1.xml?<emailaddress>
/v1.1/mail/config-v1.1.xml?<emailaddress>
/.well-known/autoconfig/mail/config-v1.1.xml?<emailaddress>
/autodiscover/autodiscover.json?<Email>&<Protocol>&<RedirectCount>
/autodiscover/autodiscover.json/v1.0/infos?<Email>&<Protocol>&<RedirectCount>
/autodiscover/autodiscover.xml
/autodiscover/autodiscover.xml
/robots.txt
/version
/ping
Most or all autodiscover routes also seem to use the host header to set the
DomainName
fields in the response.I am expecting this project should be published on
autodiscover.domain.tld
to function properly, as suggested by the DNS records generated bydns-zone
and the fact that a index path is used for the Apple mobileconfig page.The text was updated successfully, but these errors were encountered: