> Oops the paste didn't work as expected -
> looked good but disappeared when sending -
> but here it goes:
>
> Mats Carlid wrote:
>
> To check the domain I use:
>
> EXECUTE \SH -c "nslookup -q=MB \:DOMAIN:\"\ CAPTURING RESULT
nslookup is 'going away' and is only maintained for compatibility.
Oops the paste didn't work as expected -
looked good but disappeared when sending -
but here it goes:
Mats Carlid wrote:
To check the domain I use:
EXECUTE \SH -c "nslookup -q=MB \:DOMAIN:\"\ CAPTURING RESULT
To check the domain I use
this for unix only and You may have to add the path to nslookup.
If someone does not understand the swedish message - if any -:)
it translates to "Nonexistent mail adress domain"
-- mats
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe
Claus Derlien wrote:
>...i need a neat way to validate an email adress, so i
> can return an error if it contains any illegal chars...
Can U2 use Regular Expressions (RegExp)?
As mentioned, there are many RFC rules that must be met in order for an
e-mail address to be considered valid. I found a
Claus,
When matching, you can match multiple patterns if you separate them with
@VM. Eg: "1N0N":@VM:"'N/A'" matches one or more numerics or N/A.
try this (the logic from my email address validation subroutine):
The string must contain @ (unless you allow sending to users in your
local domain wit
>From: [EMAIL PROTECTED]
>
>In a message dated 5/3/2005 4:43:20 AM Pacific Daylight Time,
>[EMAIL PROTECTED] writes:
>
>> GoodEmail = ( Convert("_.1234567890","",Email) Matches
>> "1A0A'@'1A0A")
>
>Change that patter to 1X0X'@'1X0X'.'1X0X
>
>1A0A Would mean you're disallowing emails ad
Wouldn't you also have to check for email addresses with this pattern
1X0X'@'1X0X'.'1X0X'.'1X0X
and other variants?
Note the TO: for this email list, for one example.
Karl
> In a message dated 5/3/2005 4:43:20 AM Pacific Daylight Time,
> [EMAIL PROTECTED] writes:
>
>
>> GoodEmail = ( Convert
In a message dated 5/3/2005 4:43:20 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> GoodEmail = ( Convert("_.1234567890","",Email) Matches
> "1A0A'@'1A0A")
Change that patter to 1X0X'@'1X0X'.'1X0X
1A0A Would mean you're disallowing emails addresses with numbers in them or
st
D] Behalf Of Brian Leach
> Sent: Tuesday, May 03, 2005 1:34 PM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2] Validating an email adress
>
>
> Claus,
>
> Since the MATCH operator handles alphas OR numerics and not
> both, this is
> the closest I can
rfc 2822 contains the entire syntax of what's alowed and whats not
(http://www.faqs.org/rfcs/rfc822.html) allowed in an email.
Overkill, but interesting. And there's a perl module (Email:Address) to do
2822 validating as well, if you need be able to validate any possible allowed
email.
Howeve
t; To: u2-users@listserver.u2ug.org
> Subject: RE: [U2] Validating an email adress
>
>
> Claus,
>
> Since the MATCH operator handles alphas OR numerics and not
> both, this is
> the closest I can get using a pattern match:
>
> GoodEmail = ( Convert("_.123456
How about this:
GOOD.CHARS = "abcdefghijklmnopqrstuvwxyz"
GOOD.CHARS := "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
GOOD.CHARS := "0123456789.-_@"
INPUT EMAIL.ADDR
TEST.ADDR = EMAIL.ADDR
CONVERT GOOD.CHARS TO "" IN TEST.ADDR
IF TEST.ADDR # "" THEN
No, No, Bad User
Do It Over
END
Hope this help
Claus,
Since the MATCH operator handles alphas OR numerics and not both, this is
the closest I can get using a pattern match:
GoodEmail = ( Convert("_.1234567890","",Email) Matches
"1A0A'@'1A0A")
Brian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On B
Just create a loop in basic and convert each character to its ascii value
and then just check your range of allowed values.
INPUT EMAIL.ADDRESS
BAD.EMAIL = @FALSE
FOR LETTER=1 TO LEN(EMAIL.ADDRESS)
TEST=SEQ(EMAIL.ADDRESS[LETTER,1])
IF TEST<32 OR TEST>126 THEN;*just chec
14 matches
Mail list logo
