# # Versions for all modules listed in MYMETA.json (including optional ones): # # === Configure Requires === # # Module Want Have # ------------------- ---- ---- # ExtUtils::MakeMaker any 7.34 # # === Build Requires === # # Module Want Have # ------------------- ---- ---- # ExtUtils::MakeMaker any 7.34 # # === Test Requires === # # Module Want Have # ------------------- ---- -------- # ExtUtils::MakeMaker any 7.34 # File::Spec any 3.75 # Test::More 0.96 1.302166 # # === Test Recommends === # # Module Want Have # ---------- -------- -------- # CPAN::Meta 2.120900 2.150010 # # === Runtime Requires === # # Module Want Have # ----------------- ---- -------- # Carp any 1.50 # File::Spec any 3.75 # IO::CaptureOutput any 1.1105 # IO::File any 1.41 # Mail::Address any 2.21 # Net::DNS any 1.28 # Net::Domain::TLD 1.65 1.75 # Scalar::Util any 1.55 # Test::More any 1.302166 # strict any 1.11 # warnings any 1.44 # t/00-report-prereqs.t .. 1..1 ok 1 ok t/resolver.t ........... 1..4 ok 1 - resolver is undef ok 2 - use Email::Valid; ok 3 - resover initialized ok 4 - An object of class 'Net::DNS::Resolver' isa 'Net::DNS::Resolver' ok t/utf-8.t .............. 1..2 ok 1 - do not accept addr with \xE9 ok 2 - do not accept addr with \x{11F} ok t/valid.t .............. 1..39 ok 1 - use Email::Valid; ok 2 - Alfred Neuman ok 3 - 123@example.com ok 4 - Alfred Neuman ok 5 - 123@example.com ok 6 - Alfred Neuman { -fqdn => 0 } ok 7 - spaces fudged out of an address local-part ok 8 - spaces in localpart is not valid when not fudging ok 9 - details are rfc822 ok 10 - spaced out address is squished ok 11 - comments nicely dropped from an address ok 12 - address with > 254 chars fails ok 13 - details say address is too long ok 14 - localpart with 64 chars or less is valid ok 15 - localpart with 64 chars or more fails ok 16 - details are localpart ok 17 - space between @ and domain is valid ok 18 - localpart in true context succeeds ok 19 - localpart in false context is defined (bug 75736) ok 20 - an email can start with a dash ok 21 - an email can start with a dash (alternate calling method) ok 22 - but a domain cannot ok 23 - a domain cannot end with a dash either ok 24 - but a domain may contain two dashes in a row in the middle ok 25 - and of course two-character labels are valid! ok 26 - onesies, too ok 27 - blort@aol.com, with mxcheck, is ok ok 28 - blort@will-never-exist.pobox.com, with mxcheck, is invalid ok 29 - no-mx-exists.manxome.org has a null mx record ok 30 - a domain literal address is okay ok 31 - a domain literal address is not okay if we say -allow_ip=>0 ok 32 - blort@notarealdomainfoo.com is ok with tldcheck ok 33 - blort@notarealdomainfoo.bla is not ok with tldcheck ok 34 - it was the tldcheck that broke this email ok 35 - allow_ip + domain literal = no tldcheck ok 36 - 123@example.invalid is wrong as per IETF spec (invalid TLD) ok 37 - 123@example.test is wrong as per IETF spec (invalid TLD) ok 38 - 123@example.example is wrong as per IETF spec (invalid TLD) ok 39 - 123@example.localhost is wrong as per IETF spec (invalid TLD) ok All tests successful. Files=4, Tests=46, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.47 cusr 0.08 csys = 0.58 CPU) Result: PASS