in reply to Email::Valid rejecting emails @example.com today

These tests are not trying to send email, the part of the code that's failing is the input validation which uses Email::Valid with the MX check enabled.

I found your problem: the example.com domain is not really even supposed to resolve, much less have ever had valid MX records. The validation is working correctly: email addresses on example.com are not valid and you should not be using those in test data that is supposed to pass validation.

I offer a solution: establish a ci-test subdomain on your own domain and use it for your sample customer records.

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

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

    I found your problem: the example.com domain is not really even supposed to resolve, much less have ever had valid MX records. The validation is working correctly: email addresses on example.com are not valid and you should not be using those in test data that is supposed to pass validation.

    Prove it :)

[reply]
[reply]

        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]

In Section Seekers of Perl Wisdom