[
https://issues.apache.org/jira/browse/VALIDATOR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936470#comment-14936470
]
Ralph Goers commented on VALIDATOR-376:
---------------------------------------
Obviously there is a reason that VALIDATOR-273 was requested to be implemented.
What I would prefer is that the default behavior of the isValid(String email)
method be reverted back to the behavior prior to VALIDATOR-273 so that
applications can easily migrate to the latest version. I would then suggest
that the getInstance() method accept an additional boolean to enable the
behavior that is currently implemented.
> 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)