Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^4: Email::Valid rejecting emails today

by Anonymous Monk
on Sep 06, 2019 at 04:07 UTC ( #11105703=note: print w/replies, xml ) Need Help??

in reply to Re^3: Email::Valid rejecting emails today
in thread Email::Valid rejecting emails today

See RFC2606. :)

Which part of "RFC2606" dictates how ICANN should manage 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.

Replies are listed 'Best First'.
Re^5: Email::Valid rejecting emails today
by jcb (Chaplain) 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 "" 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, complete with ads, during one of the Internet bubbles.

      How does that RFC section trump ICANN? ICANN is the boss. A purpose is not a limitation :)

        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.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://11105703]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (7)
As of 2019-10-16 21:44 GMT
Find Nodes?
    Voting Booth?