On 06/28/2013 10:03 AM, Alessandro Vesely wrote:
On Thu 27/Jun/2013 06:56:51 +0200 Keith Moore wrote:
I've seen a lot of code (including but not just in email software) that
assumed that if a domain name contained a dot, it was an FQDN (and
therefore should be taken as correct as-is), and if it didn't contain a
dot, it was potentially an alias (and therefore subject to having a
default domain suffix appended to it).
I'm not sure appending a domain is the right thing to do. If you have
RCPT TO:<postmaster>, or something like that, you also append the "@".
RFC 5321 just says "mechanisms for inferring FQDNs from partial names or
local aliases are outside of this specification."
How about RCPT TO:<user@local>? According to RFC 6762, "operators
SHOULD NOT attempt to configure authoritative DNS servers to act as
authoritative for any of these names." So any address or MX should be
defined using mDNS.
Please, no. mDNS was, and is, a complete botch. Let's not pollute the
mail system with it.
All I'm saying is that there's a lot of existing and useful practice
which expects to be able to distinguish an alias (presumably without a
dot) from a FQDN. People shouldn't expect email to a domain name that
consists entirely of a TLD (any TLD) to work reliably. This is one of
a long list of reasons why vanity TLDs were a Really Bad Idea.
Keith
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp