[
https://issues.apache.org/jira/browse/VALIDATOR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936643#comment-14936643
]
Sebb commented on VALIDATOR-376:
--------------------------------
Note that version 1.4.1 has already been released.
So reverting to previous behaviour would be a functional change, and needs to
be very well documented if it is considered OK to do.
I am generally against adding network code to Validator runtime; that seems
completely out of scope.
However it might be possible to add support for a user-provided callback to
handle such cases.
There's also the question of what the RFCs really say.
The example in VALIDATOR-273 used a country code, however the patch allowed all
TLDs, including country-codes.
Was that correct? I had a brief look at RFC 5321 but the answer is not obvious.
Also, just because one or more mail apps do not work with addresses such as
x.y@gmail does not mean that such addresses are invalid.
It's not unknown for mail apps to make unwarranted assumptions about the format
of mail addresses.
> 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)
