Loading Profile...
EAUT lookups
Regarding EAUT lookups - it would be nice if there were a DNS lookup stage first, rather than hardcoding @company.com addresses to http://company.com or http://www.company.com. A SRV or TXT record would allow any server to be specified similar to how MX records work for mail.
Many organisations will have their TLD hogged by legacy services and all manner of odd restrictions. Checking the TLD for a web based record first may not incur instant failure but timeouts that could take some minutes which would be a major usability issue.
Many organisations will have their TLD hogged by legacy services and all manner of odd restrictions. Checking the TLD for a web based record first may not incur instant failure but timeouts that could take some minutes which would be a major usability issue.
Follow this discussion to get notifications on your dashboard.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?We certainly considered this, as we share the concern that this could be a pretty steep barrier to entry for large email providers. The problem is that we use XRDS-Simple for discovery which does not allow for that. It even goes so far as to explicitly forbid changing the discovery flow in such a manner.
The least invasive way of adding XRDS to a domain is simply to add an X-XRDS-Location header which specifies where the document can be found. The document itself need not be hosted at the top domain, only a pointer to where it is. This is how Yahoo! currently advertises their XRDS document.
Even still, this may be too much of a barrier for some providers. We are aware of that, but don't have any immediate plans to accommodate that use case. If it proves to be insurmountable, I'm sure we'll revisit it. These types of discussions surrounding the EAUT spec happen at the EAUT Google Group
