Just because it worked for you, it doesn't mean it will work for everyone.
Working or not depends on the clients search list and hostnames that resolve
using that search list.
This is not a fixable problem. It can NEVER be made to work reliable as people
want to be able to use short names and just because you have several thousand
dollars to buy a TLD it doesn't give you the right to steal the short name from
others.
Mark
On 09/07/2013, at 8:31, Steve Atkins <steve(_at_)blighty(_dot_)com> wrote:
On Jul 8, 2013, at 1:05 PM, John Levine <johnl(_at_)taugh(_dot_)com> wrote:
ICANN being ICANN, and clearly aware that Google has an unlimited
supply of lawyers, has been going around asking people are you *SURE*
that it's a bad idea to put A and AAAA records at the TLD? An
entirely reasonable response is, yes, nothing has changed, we're still
sure it's a bad idea.
Seems to work fine for http://ac/ and http://dk/ amongst others.
But, of course, actual data would be nice, too.
Of 317 current TLDs, 19 have MX records[1].
Of those 19, only 5 accept email to postmaster@tld. (ai, ax, km, tt, ua).
The remaining 14 either aren't listening on port 25, aren't configured to
handle that domain or, in one case, "Recipient address
rejected: need fully-qualified address".
I didn't bother checking for fallback to A.
Cheers,
Steve
[1] http://privatepaste.com/8e191ef714
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp