Personally I would rather reject the data from the program and have the
program tell the client that the format is invalid and please re-enter it
properly. This is the way to do it because you don't know why the customer
entered it that way and trying to clean the input up and make it valid data
may/probably will cause problem later since the program never corrected the
client's assumption about the validity of that type of format for the data
that was requested. It is always better to throw out bad data, and notify
the client/program-user that it is bad data and ask for a re-input in the
proper format, so they better understand what exactly it is the program is
asking for.
Tim Jung
System Admin
Internet Gateway Inc.
tjung@igateway.net
----- Original Message -----
From: "Justin S." <kidjustino@chesco.com>
To: <discuss-list@opensrs.org>
Sent: Friday, June 16, 2000 8:06 AM
Subject: Re: "." before the "@"
> I think overall that those types of e-mail addresses should be allowed. It
> doesn't matter if it doesn't go with RFC822 or whatever, because some
people
> are different. It comes down to: do you want the business, or do you want
to
> bitch and moan at the client for having a '.' before the '@'? I'd rather
> have the business any day!
>
> Justin S...
>
>
> ----- Original Message -----
> From: "Bill Gerrard" <bill@daze.net>
> To: "Merchant Solutions" <merchant-solution@merchant-solution.com>;
> <discuss-list@opensrs.org>
> Sent: Friday, June 16, 2000 1:45 AM
> Subject: RE: "." before the "@"
>
>
> > > The . before the @ needs to be allowed. Many email addy's are set
> > > that way.
> > > Example, my own admin email address is aba.admin@merchant-solution.com
> >
> > In your example address, there are five characters between the '.' and
> '@'.
> > Your e-mail address is perfectly valid. Now if your e-mail address was
> > aba.@merchant-solution.com or admin.@merchant-solution.com, then you
would
> > have an invalid e-mail address, per RFC822.
> >
> > > If I understand correctly, OpenSRS won't accept that addy. NSI does
> accept
> > > that addy, if that makes any difference in the decision here.
> > >
> > >
> > > Sincerely,
> > > Todd Sumrall
> > > Authorize.net & Miva Partner
> > > http://www.merchant-solution.com
> > > Merchant Accounts, Web Hosting,
> > > Free Miva Merchant Shopping Cart
> > >
> > > ----- Original Message -----
> > > From: Bill Warner <lww@ictech.net>
> > > To: Joe McDonald <joe@vpop.net>
> > > Cc: <discuss-list@opensrs.org>
> > > Sent: Thursday, June 15, 2000 9:05 PM
> > > Subject: RE: "." before the "@"
> > >
> > >
> > > > Hi Joe,
> > > >
> > > > At 03:44 PM 6/15/00 -0700, Joe McDonald wrote:
> > > > >I think when Robert answered, he meant to say "right before the @"
> > > > >instead of "before the @". He was replying to the message below
> > > > >which shows a bad address (according to my interpretation of
> > > rfc 822...)
> > > >
> > > > Ahh, yes. I see now. In that case he's quite right. Sorry Robert!
> > > >
> > > >
> > > > >The OpenSRS check_email_syntax() is doing the right thing as
> > > > >far as I can tell, but it will be loosened up to allow some
> > > > >bad addresses through because it appears that MTA's out there
> > > > >are letting them through and people are using them. :-(
> > > >
> > > > I'm with you on that one. ugh. The problem with letting the bad
ones
> > > > through is that the syntax checker may no longer catch addresses
that
> > > > really were typed in wrong and don't work.
> > > >
> > > >
> > > > > > We have a customer with an e-mail address like mark.o.@foo.net.
> > > > > Unfortunately
> > > > > > OpenSRS' system does NOT accept this address ...
> > > >
> > > > Good. ;-)
> > > >
> > > > [PS - Joe, I'm going to CC this reply back to the list so that
> > > my apology
> > > > to Robert goes public. Only fair, since my flame was public...]
> > > >
> > > > --Bill
> > > >
> > >
> > >
> >
> >
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:38 EDT