[ 
https://issues.apache.org/jira/browse/VALIDATOR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934457#comment-14934457
 ] 

Bernd Eckenfels edited comment on VALIDATOR-376 at 9/29/15 1:28 AM:
--------------------------------------------------------------------

I guess there are two options. When doing a  purely lexicographic validity 
check of email addresses the Validator needs a list of valid TLDs and a 
mechanism to update them. (either all TLDs or specifically the dotlessones: 
https://tools.ietf.org/html/rfc7085#section-2.3)

When doing network based validation it needs a way to deal with 127.0.53.53 
(and similiar?) blacklist answers. In case of @gmail. the MX records are caused 
by  https://icann.org/namecollision


was (Author: b.eckenfels):
I guess there are two options. When doing apurely lexicographic validty check 
of email addresses the Validator needs a list of valid TLDs and a mechanism to 
update them. When doing network based validation it needs a way to deal with 
127.0.53.53 (and similiar?) blacklist answers. In case of @gmail. the MX 
records are caused by  https://icann.org/namecollision

> EmailValidator says addresses such as x.y@gmail are valid although most mail 
> apps will fail to send it
> ------------------------------------------------------------------------------------------------------
>
>                 Key: VALIDATOR-376
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-376
>             Project: Commons Validator
>          Issue Type: Bug
>          Components: Routines
>    Affects Versions: 1.4.1 Release
>            Reporter: Ralph Goers
>
> The VALIDATOR-273 patch causes EmailValidator to allow addresses such as 
> x.y@gmail. Unfortunately, this is causing us problems as none of the email 
> apps we have tried will actually allow that email address to be sent. 
> Although the RFCs may state it is valid, in practice it apparently isn't. 
> Some sort of option is needed to allow providing just the domain to fail. As 
> a consequence we have had to revert to a prior release of commons-validator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to