in reply to Re^2: Email::Valid rejecting emails @example.com today
in thread Email::Valid rejecting emails @example.com today

See RFC2606. :)

  • Comment on Re^3: Email::Valid rejecting emails @example.com today

Replies are listed 'Best First'.
Re^4: Email::Valid rejecting emails @example.com today
by Anonymous Monk on Sep 06, 2019 at 04:07 UTC

    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.

[reply]
[d/l]

      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]
        How does that RFC section trump ICANN? ICANN is the boss. A purpose is not a limitation :)
[reply]

In Section Seekers of Perl Wisdom