[
https://issues.apache.org/jira/browse/VALIDATOR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936468#comment-14936468
]
Bernd Eckenfels commented on VALIDATOR-376:
-------------------------------------------
Have to correct myself, EmailValidator is using DomainValidator and that one
already checks for a hardcoded list of TLD and gmail is on it. It will be
useable for emails in the future and the validator is allowed to accept it - it
might even be used by millions .... so the case C) is there and the application
should do D).
I am not sure if it is a good idea to provide actual network accessing code, as
you typically need retries, different policies and proxy support.
> 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)
