Maybe the best option would be to have 2 different email validation
methods in UtilValidate (don't want to add an argument, because some
stuff depends on taking a single String argument and returning a
boolean).
Then the ContactList or something could have a indicator on it
specifying whether or not to require a dot after the @.
-David
On Nov 3, 2006, at 4:51 AM, Yoav Shapira wrote:
Hi,
On 11/3/06, David Welton <[EMAIL PROTECTED]> wrote:
> There was some discussion a long long time ago about this and how
> some valid email addresses don't have a dot in them. I don't
know how
> that could be except perhaps on an internal network or something.
[EMAIL PROTECTED]
Yup, that's an example. The general issue is in RFC2821, section
2.3.10. Only the destination host should attempt to parse, verify, or
manipulate the string after the @. Most of the time this would only
be useful on an internal network where you create aliases and/or run
your own mailing lists inside the network...
Yoav
