On Fri 05/Jul/2013 19:03:57 +0200 Keith Moore wrote:
On 06/28/2013 10:03 AM, Alessandro Vesely wrote:
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.
Fully agreed :-)
Let's not pollute the mail system with it.
Yet, there seem to be quite some users who happen to download and
install MTA software on their laptops, unwittingly. It is not at all
obvious how to provide an even barely working default configuration for
that kind of thing, which leads to frustration. OTOH, it might
sometimes be handy to be able to exchange email messages across an
ad-hoc LAN, possibly disconnected from the rest of the Internet.
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.
I'm neutral on this. I see no technical reason to ban dotless domains,
and no traction to make them work. Any chance we can catch some wind by
rocking the boat with mDNS?
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp