commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Schultz (JIRA)" <>
Subject [jira] [Commented] (VALIDATOR-315) Email validator does not properly validate symbolic domain names
Date Mon, 05 Jan 2015 15:14:35 GMT


Christopher Schultz commented on VALIDATOR-315:

I checked this against the 1.4.1 candidate build and it seems to be working correctly. I then
checked against 1.4.0 since very few significant changes have been made to the email validator
in a looong time, and the 1.4.0 seems to work as expected. I'm interested in the earliest
release in which this has been fixed, so I'll do a bit of archeology.

> Email validator does not properly validate symbolic domain names
> ----------------------------------------------------------------
>                 Key: VALIDATOR-315
>                 URL:
>             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&")
> ...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

View raw message