I personally wrote the patch that caused example.com to be invalid in accordance with the RFCs (in version 1.199, released on 2016-03-27, based on the Email::Valid Changes file).
Something changed at your end, whether it be an update to the distribution, or your DNS/naming infrastructure. Given that it happened across two separate environments separately, I suspect the latter (as you've stated within this thread).
jcb suggested to add a sub-domain to your domain for testing. If you go this route, ensure you create an MX record so your MX tests pass. You could also create a dummy example.com domain (with an MX) within your local infrastructure, or simply bypass the MX checks (unadvised).
Regardless... the reason this is failing is due to the fact that example.com is not a valid domain (technically it's a reserved domain; I say "invalid" for the purposes of the distribution).
In reply to Re: Email::Valid rejecting emails @example.com today
by stevieb
in thread Email::Valid rejecting emails @example.com today
by grantm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |