Re: [Validator] E-Mail Verification
On Mon, Sep 08, 2003 at 02:32:01PM -0700, David Graham wrote: } --- Paananen, Tero [EMAIL PROTECTED] wrote: } +1 on the new option but I think the allowed characters should be } } a-zA-Z0-9_.- } } -999 } } That's missing several perfectly valid characters } in Email addresses, like a space, +, single quote, } etc. } } The RFC defines the valid characters for a reason. } } This would be a new option for people who want to limit email addresses to } more reasonable characters than the RFC defines. It would not be enabled } by default. Even so, it should at least include +. I can't tell you how many times I've been annoyed by stupid web forms that wouldn't tolerate the +extension trick in an email address (see the email address I am using for this list). I see no reason to make it easy to break such things. } David } -TPP --Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Validator] E-Mail Verification
Is there a published specification on e-mail addresses? The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes Comments? Jerry Jalenak Team Lead, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Validator] E-Mail Verification
--- Jerry Jalenak [EMAIL PROTECTED] wrote: Is there a published specification on e-mail addresses? I believe it's RFC 822. The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes Unfortunately, I think that's a valid email address as defined in the RFC. David Comments? Jerry Jalenak Team Lead, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Validator] E-Mail Verification
Is there a published specification on e-mail addresses? The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes Comments? There was discussion about this earlier on the mailing list. Search the archives for email validation RFC or some such. There's an RFC that covers what're valid email addresses. Your example looks perfectly valid to me... -TPP - This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Validator] E-Mail Verification
David / Tero - Thanks for the guidance. The RFC822 spec is what I was looking for Jerry Jalenak Team Lead, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] -Original Message- From: Paananen, Tero [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 10:34 AM To: 'Struts Users Mailing List' Subject: RE: [Validator] E-Mail Verification Is there a published specification on e-mail addresses? The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes Comments? There was discussion about this earlier on the mailing list. Search the archives for email validation RFC or some such. There's an RFC that covers what're valid email addresses. Your example looks perfectly valid to me... -TPP - This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Validator] E-Mail Verification
David Graham [EMAIL PROTECTED] wrote:
--- Jerry Jalenak [EMAIL PROTECTED] wrote:
Is there a published specification on e-mail addresses?
I believe it's RFC 822.
Unfortunately, I think that's a valid email address as defined in the RFC.
You're better off writing your own. RFC 822 is very generous because it
doesn't just deal with remote internet addresses, but email from all sorts
of networks.
Here's an example of something that's a bit more restrictive.
This first runs it through javax.mail.internet.InternetAddress(). You'll
need to have the javax.mail package installed to use it.
Then it performs additional restrictions (we want to disallow local
addresses).
private boolean isRemoteAddressSyntax(String emailAddress)
{
int firstAtPos = emailAddress.indexOf('@');
int lastAtIndexOf = emailAddress.lastIndexOf('@');
int lastDotIndexOf = emailAddress.lastIndexOf('.');
// Must be one @
if (-1 == firstAtPos) return false;
// Must be at least one character before @
if (1 firstAtPos) return false;
// Must be at least one '.'
if (-1 == lastDotIndexOf) return false;
// Only one @ allowed.
if (firstAtPos != lastAtIndexOf) return false;
// '.' must be at least one character after '@'
if (lastDotIndexOf (firstAtPos + 2)) return false;
// Must be at least one character after '.'
if (lastDotIndexOf == (emailAddress.length() - 1)) return false;
return true;
}
public boolean isValidBasicEmailSyntax(String emailAddress)
{
try
{
javax.mail.internet.InternetAddress anAddress = new
javax.mail.internet.InternetAddress(emailAddress);
return isRemoteAddressSyntax(emailAddress);
}
catch(javax.mail.internet.AddressException anAddressException)
{
return false;
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Validator] E-Mail Verification
David Graham wrote: --- Jerry Jalenak [EMAIL PROTECTED] wrote: Is there a published specification on e-mail addresses? I believe it's RFC 822. The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes I believe that the name part needs to be quoted. However, I believe currently validator will still count this as a valid email. I haven't gotten around to tweaking the regexp. To handle these cases the user name pattern/expression will need to increase in complexity by a factor of 3 or so. How about an option that would allow only struct user names checking, ie [a-z][A-Z] and '.'. The clunky part is both the client and server versions of the regexp need to change. I believe I would actually like to make the client side checking more course, ie allow any email in the form of [EMAIL PROTECTED], then let the java take care of full validation, what do you think ? Unfortunately, I think that's a valid email address as defined in the RFC. David Comments? Jerry Jalenak Team Lead, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Validator] E-Mail Verification
--- Robert Leland [EMAIL PROTECTED] wrote: David Graham wrote: --- Jerry Jalenak [EMAIL PROTECTED] wrote: Is there a published specification on e-mail addresses? I believe it's RFC 822. The reason I ask is that we are using the 'email' validator, and it's accepting as valid e-mail addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think Validator would accept these, but apparently is it. If there's not an established spec for e-mail addresses, then I would assume that anything goes I believe that the name part needs to be quoted. However, I believe currently validator will still count this as a valid email. I haven't gotten around to tweaking the regexp. To handle these cases the user name pattern/expression will need to increase in complexity by a factor of 3 or so. How about an option that would allow only struct user names checking, ie [a-z][A-Z] and '.'. +1 on the new option but I think the allowed characters should be a-zA-Z0-9_.- The clunky part is both the client and server versions of the regexp need to change. I believe I would actually like to make the client side checking more course, ie allow any email in the form of [EMAIL PROTECTED], then let the java take care of full validation, what do you think ? +1. Javascript is merely a convenience for the user and it's a pain to maintain this complex logic in 2 places. David Unfortunately, I think that's a valid email address as defined in the RFC. David Comments? Jerry Jalenak Team Lead, Web Publishing LabOne, Inc. 10101 Renner Blvd. Lenexa, KS 66219 (913) 577-1496 [EMAIL PROTECTED] This transmission (and any information attached to it) may be confidential and is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient or the person responsible for delivering the transmission to the intended recipient, be advised that you have received this transmission in error and that any use, dissemination, forwarding, printing, or copying of this information is strictly prohibited. If you have received this transmission in error, please immediately notify LabOne at the following email address: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Validator] E-Mail Verification
+1 on the new option but I think the allowed characters should be a-zA-Z0-9_.- -999 That's missing several perfectly valid characters in Email addresses, like a space, +, single quote, etc. The RFC defines the valid characters for a reason. -TPP - This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Validator] E-Mail Verification
just-remembered-this
Some time ago I needed an e-mail regular expression, and found this in a
book on JavaScript. Seemed to work OK at the time.
/^\w(\.?[\w-])[EMAIL
PROTECTED](\.?[-\w])*\.([a-z]{3}(\.[a-z]{2})?|[a-z]{2}(\.[a-z]{2})?)
$/i
/just-remembered-this
Jerry Jalenak
Team Lead, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS 66219
(913) 577-1496
[EMAIL PROTECTED]
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Monday, September 08, 2003 3:45 PM
To: Struts Users Mailing List
Subject: Re: [Validator] E-Mail Verification
--- Robert Leland [EMAIL PROTECTED] wrote:
David Graham wrote:
--- Jerry Jalenak [EMAIL PROTECTED] wrote:
Is there a published specification on e-mail addresses?
I believe it's RFC 822.
The reason I
ask is
that we are using the 'email' validator, and it's
accepting as valid
e-mail
addresses such as 'u-+-+%^_/[EMAIL PROTECTED]'. I didn't think
Validator
would accept these, but apparently is it. If there's not an
established
spec for e-mail addresses, then I would assume that
anything goes
I believe that the name part needs to be quoted. However, I believe
currently validator will still
count this as a valid email. I haven't gotten around to
tweaking the
regexp. To handle these cases
the user name pattern/expression will need to increase in
complexity by
a factor of 3 or so.
How about an option that would allow only struct user names
checking,
ie [a-z][A-Z] and '.'.
+1 on the new option but I think the allowed characters should be
a-zA-Z0-9_.-
The clunky part is both the client and server
versions of the regexp
need to change. I believe I would actually like to make the
client side
checking more course,
ie allow any email in the form of [EMAIL PROTECTED], then let the
java take care
of full validation,
what do you think ?
+1. Javascript is merely a convenience for the user and it's
a pain to
maintain this complex logic in 2 places.
David
Unfortunately, I think that's a valid email address as
defined in the
RFC.
David
Comments?
Jerry Jalenak
Team Lead, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS 66219
(913) 577-1496
[EMAIL PROTECTED]
This transmission (and any information attached to it) may be
confidential and is intended solely for the use of the
individual or
entity to which it is addressed. If you are not the
intended recipient
or the person responsible for delivering the transmission to the
intended recipient, be advised that you have received this
transmission
in error and that any use, dissemination, forwarding, printing, or
copying of this information is strictly prohibited. If you have
received
this transmission in error, please immediately notify
LabOne at the
following email address: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This transmission (and any information attached to it) may be confidential and is
intended solely for the use of the individual or entity to which it is addressed. If
you are not the intended recipient or the person responsible for delivering the
transmission to the intended recipient, be advised that you have received this
transmission in error and that any use, dissemination, forwarding, printing, or
copying of this information is strictly prohibited. If you have received this
transmission in error, please immediately notify LabOne at the following email
address: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Validator] E-Mail Verification
--- Paananen, Tero [EMAIL PROTECTED] wrote: +1 on the new option but I think the allowed characters should be a-zA-Z0-9_.- -999 That's missing several perfectly valid characters in Email addresses, like a space, +, single quote, etc. The RFC defines the valid characters for a reason. This would be a new option for people who want to limit email addresses to more reasonable characters than the RFC defines. It would not be enabled by default. David -TPP - This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. Also, email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
