|
|
Posted by Jim Moseby on 09/21/05 22:49
> -----Original Message-----
> From: Jim Moseby [mailto:JMoseby@nrbindustries.com]
> Sent: Wednesday, September 21, 2005 12:21 PM
> To: php-general@lists.php.net
> Subject: RE: [PHP] Re: email validation (no regex)
>
>
> >
> > btw simply checking for a single '@' with a domain doesn't do
> > it... what if
> > the user has 'foo@1.2.3.4' or 'r+foo@1.2.3.4'. will your
> > regex accept/deny
> > this???
>
> My function will quickly deny those because the DNS lookup
> for them will
> immediately fail. Will your regex deny
> 'bogususer@bogusdomain.com'? Should
> it?
>
> > welcome to the world of email validation
>
> That's your world. Mine is much simpler. :o) Seriously, I
> think Ben and
> Manuel have it right. A combination approach is probably
> most effective
> (and complex). I was hoping for a simple solution for the
> regex challenged.
> Of course the old tried and true validation email that
> requires the user to
> validate himself is the most fool-proof method, but thats not
> an on-the-fly
> solution.
>
> jim...
>
> these are valid emails... as defined by the rfc..
>
> so your function would be in error..
This is where I think you and I are not connecting. I don't care if they
are valid according to the RFC. I want to know if they are likely to be
*WORKING* email addresses. And so, from that perspective, my function would
not necessarily be in error, but working as designed.
Others have brought up truly valid points with regards to the reliability of
it though. Different quirks of MTA configuration and function are difficult
to overcome. I have learned you cannot rely on 'RCPT To:' responding with a
'250' as verification that it is a valid user. I have learned that a domain
need not have an MX record at all, to receive mail.
Learning is why I'm here, and why I posted this question. Thank you for
your input.
JM
Navigation:
[Reply to this message]
|