Re^4: Email::Valid rejecting emails @example.com today

See RFC2606. :)

Which part of "RFC2606" dictates how ICANN should manage example.com? It also makes no mention of mail exchanger record (MX record)

When I'm guessing I says I'm guessing. Otherwise I check my answers before posting so I'm not posting bad memories/fantasy.

Comment on Re^4: Email::Valid rejecting emails @example.com today Download Code

Replies are listed 'Best First'.
Re^5: Email::Valid rejecting emails @example.com today by jcb (Parson) on Sep 06, 2019 at 04:17 UTC
Read section 2 of RFC2606, which describes the purpose of reserving domain names and reserves a few TLDs. Section 3 describes "example.com" and others as "also" reserved to be "used as examples". That means that they should be treated like the top-level domain ".example." and are intended for use in documentation. There is no reason that a documentation placeholder domain should even resolve. In fact, I recall some controversy when the .COM registrar put up a page on example.com, complete with ads, during one of the Internet bubbles.	[reply]
Re^6: Email::Valid rejecting emails @example.com today by Anonymous Monk on Sep 06, 2019 at 04:40 UTC
How does that RFC section trump ICANN? ICANN is the boss. A purpose is not a limitation :)	[reply]
Re^7: Email::Valid rejecting emails @example.com today by jcb (Parson) on Sep 06, 2019 at 04:48 UTC
Did you read your own link? That example domains resolve at all is only a means to provide an explanation to unknowing users. And ICANN does not get to do whatever it wants: ICANN is constrained by protocol rules, which RFC6761 takes pains to explicitly reiterate.	[reply]
Re^8: Email::Valid rejecting emails @example.com today by Anonymous Monk on Sep 06, 2019 at 04:59 UTC