Validate EMail with RegExp...

[Dag Sunde]

My understanding of regular expressions is rudimentary,
at best.

I have this RegExp to to a very simple validation of an
email-address, but it turns out that it refuses to
accept mail-addresses with hypens in them.

Can anybody please help me adjust it so it will accept
addresses like da*******@test-domain.net too?

Here's what got:

function validateEmail(e Mail) {
return /^(\w+\.)*(\w+)@ (\w+\.)+([a-zA-Z]{2,4})$/.test(eMail);
}

TIA...

--
Dag.

Work is the curse of the drinking classes
-- Oscar Wilde

[Thomas 'PointedEars' Lahn]

Dag Sunde wrote:

"David Dorward" <do*****@yahoo. com> [...]

Dag Sunde wrote:

I have this RegExp to to a very simple validation of an
email-address, but it turns out that it refuses to
accept mail-addresses with hypens in them.

http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html

You're kidding me, right?

That is the longest monster of a regular expression I've ever seen!

And probably the most useless one (in this newsgroup), taking into account
that it is based on an obsolete RFC, is highly unlikely to be needed in
forms, and uses features no JS/ECMAScript engine supports.

Nice try, though.
PointedEars

[Dr John Stockton]

JRS: In article <lV************ *******@juliett .dax.net>, dated Thu, 3
Nov 2005 09:39:29, seen in news:comp.lang. javascript, Dag Sunde
<[e-mail] m> posted :

I have this RegExp to to a very simple validation of an
email-address, but it turns out that it refuses to
accept mail-addresses with hypens in them.

Can anybody please help me adjust it so it will accept
addresses like da*******@test-domain.net too?

Here's what got:

function validateEmail(e Mail) {
return /^(\w+\.)*(\w+)@ (\w+\.)+([a-zA-Z]{2,4})$/.test(eMail);
}

It is pointless to attempt to validate an E-mail address format in
detail, unless you are writing an E-mail system, or unless the task is
purely pedagogical. A RegExp that will accept [e-mail] will also
accept [e-mail], and for any given message at least one of those
is wrong. There's no way round it; someone typing an E-address just has
to be careful to get it right.

If a test does not accept any RFC-permitted E-address, there will be
complaints; if an allegedly-full test fails to reject any non-permitted
address, there will be complaints. And if the RFCs change the format
range, full-check code will have to be changed too.

Testing with /.+@.+\..+/ or /^.+@.+\..+$/, to ensure at least x@y.z,
does make sense as a check that something like an E-address has been put
in the field, rather than say a price or an arbitrary vulgarity.

See <URL:http://www.merlyn.demo n.co.uk/js-valid.htm#VEmA> .

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 IE 4 ©
<URL:http://www.jibbering.c om/faq/> JL/RC: FAQ of news:comp.lang. javascript
<URL:http://www.merlyn.demo n.co.uk/js-index.htm> jscr maths, dates, sources.
<URL:http://www.merlyn.demo n.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.

[Dag Sunde]

"Dr John Stockton" <jr*@merlyn.dem on.co.uk> wrote in message
news:DQ******** ******@merlyn.d emon.co.uk...

JRS: In article <lV************ *******@juliett .dax.net>, dated Thu, 3
Nov 2005 09:39:29, seen in news:comp.lang. javascript, Dag Sunde
<[e-mail] m> posted :

I have this RegExp to to a very simple validation of an
email-address, but it turns out that it refuses to
accept mail-addresses with hypens in them.

Can anybody please help me adjust it so it will accept
addresses like da*******@test-domain.net too?

Here's what got:

function validateEmail(e Mail) {
return /^(\w+\.)*(\w+)@ (\w+\.)+([a-zA-Z]{2,4})$/.test(eMail);
}
It is pointless to attempt to validate an E-mail address format in
detail, unless you are writing an E-mail system, or unless the task is
purely pedagogical. A RegExp that will accept [e-mail] will also
accept [e-mail], and for any given message at least one of those
is wrong. There's no way round it; someone typing an E-address just has
to be careful to get it right.

Of course.
If a test does not accept any RFC-permitted E-address, there will be
complaints; if an allegedly-full test fails to reject any non-permitted
address, there will be complaints. And if the RFCs change the format
range, full-check code will have to be changed too.

Testing with /.+@.+\..+/ or /^.+@.+\..+$/, to ensure at least x@y.z,
does make sense as a check that something like an E-address has been put
in the field, rather than say a price or an arbitrary vulgarity.

See <URL:http://www.merlyn.demo n.co.uk/js-valid.htm#VEmA> .

That is the only thing i want, to verify that the input at least can
be interpreted as an email-address. My problem was that my former regexp.
balked at 'x' or 'z' with hypens in them.

--
Dag.