Re: Select all invalid e-mail addresses - Mailing list pgsql-general

From Brian Mathis
Subject Re: Select all invalid e-mail addresses
Date
Msg-id 183c528b0510200822q7866c924rba8af314223e1a1e@mail.gmail.com
Whole thread Raw
In response to Re: Select all invalid e-mail addresses  (Douglas McNaught <doug@mcnaught.org>)
Responses Re: Select all invalid e-mail addresses  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
On 10/20/05, Douglas McNaught <doug@mcnaught.org> wrote:
> It performs a MX-lookup, which IMHO is the best way to check for validity.

But that's expensive and slow, and doesn't tell you whether the user
part of the address is valid (and in general, there's no way to
determine that short of actually sending a message).  So what's the
point?

-Doug


That's why I think the better term for this is "well formed".  "Validity" can only be determined by sending to it, but you can tell if an address at least conforms to the specs programmatically.  In the end, when talking about a "valid" address in this context, that is what most people are talking about.

The point is to weed out malformed email addresses, just like you would enforce any other data formatting standards in other types of data.

pgsql-general by date:

Previous
From: "Andrus"
Date:
Subject: Re: Select all invalid e-mail addresses
Next
From: Andrew Sullivan
Date:
Subject: Re: [pgsql-advocacy] Oracle buys Innobase