Bug #48398 for Email-Valid: Incorrect return value when domain is Address Literal

Mon Aug 03 12:02:56 2009 david.koconis [...] icsalabs.com - Ticket created

Subject:	Incorrect return value when domain is Address Literal
Date:	Mon, 03 Aug 2009 16:02:19 +0000
To:	bug-Email-Valid [...] rt.cpan.org
From:	"Koconis, David" <david.koconis [...] icsalabs.com>

Distribution: Email-Valid-0.181 Perl version: v5.8.8 Operating System: CentOS 5.2 (kernel is 2.6.18-92.1.22.el5.centos.plus x86_64 SMP) Problem: The address method gives an incorrect return value for an address that uses the address literal format described in section 4.1.3 of RFC 2821. For example, the address 'david@[129.170.247.10]' returns undefined and the address 'david@129.170.247.10' returns a value. According to the RFC, the first form is valid and the second one is not. FYI, my inelegant solution to this issue is to check if the domain portion of the address is an IPv4 without brackets in the _valid_domain_parts() subroutine just after checking if $string matches ".." and before splitting it. If it is an IP and no brackets are present, then the subroutine returns. David Koconis Technical Lead, Network IPS & Anti-Spam Lab ICSA Labs, An Independent Division of Verizon Business david.koconis@icsalabs.com 717-790-8138 - Office

Fri Jan 27 10:57:44 2012 rjbs [...] cpan.org - Correspondence added

According to RFC 822, a domain can be 123.123.123.123, even though we both know this won't be deliverable. I agree that the domain-literal behavior is wrong and will give it a look. -- rjbs

Fri Jan 27 10:57:44 2012 The RT System itself - Status changed from 'new' to 'open'

Fri Jan 27 11:23:58 2012 rjbs [...] cpan.org - Correspondence added

This is addressed in 0.187 -- rjbs

Fri Jan 27 11:23:59 2012 rjbs [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #48398 for Email-Valid: Incorrect return value when domain is Address Literal

Preferred bug tracker