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

How does that RFC section trump ICANN? ICANN is the boss. A purpose is not a limitation :)
  • Comment on Re^6: Email::Valid rejecting emails @example.com today

Replies are listed 'Best First'.
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.

      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.

      jcb: Which part of that link says that example.com cannot resolve? That example.com cannot have a MX record? Quote the line