[
https://issues.apache.org/jira/browse/VALIDATOR-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved VALIDATOR-315.
----------------------------
Resolution: Fixed
Fix Version/s: 1.4.1
This has been fixed by the addition of DomainValidation.
URL: http://svn.apache.org/r1649170
Log:
VALIDATOR-315 - Email validator does not properly validate symbolic domain names
Add test to show it has been fixed
Modified:
commons/proper/validator/trunk/src/test/java/org/apache/commons/validator/routines/EmailValidatorTest.java
> Email validator does not properly validate symbolic domain names
> ----------------------------------------------------------------
>
> Key: VALIDATOR-315
> URL: https://issues.apache.org/jira/browse/VALIDATOR-315
> Project: Commons Validator
> Issue Type: Bug
> Affects Versions: 1.4.0 Release
> Reporter: Christopher Schultz
> Fix For: 1.4.1
>
>
> This returns true:
> EmailValidator.getInstance().isValid("me@at&t.net")
> ...when IMO it should not. If the portion of the address after the @ is
> symbolic, then it should be validated like a host name which may only contain
> [A-Za-z0-9-\.] and has a few other requirements as well (no leading or
> trailing hyphen or empty 'label', max 63 characters per label, max 255
> characters total length).
> I'm less interested in the limits, etc. but an '&' is not valid in a hostname
> and it would be nice to fail under those conditions. Use of IDN should pretty
> much allow any letter or number (\p{Alnum}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
