| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Email data type |
| Date: | 2004-05-17 16:22:20 |
| Message-ID: | 20040517162220.GA3552@gp.word-to-the-wise.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 17, 2004 at 05:01:05PM +0100, Dave Page wrote:
> > a(at)foo(dot)bar is syntactically valid. a(at)foo(dot)invalid is
> > syntactically valid, but should be immediately rejected.
>
> I disagree - just because the database server cannot verify the the
> existence of a domain does not mean that it isn't valid. I think only
> addresses that are syntactically incorrect should be rejected.
I think you're missing the point. Go and take a glance at RFC 2606 -
it's a BCP which defines the .test, .invalid, .example and .localhost
TLDs.
Of course, some users may want to use .invalid email addresses in
their database, despite their being, by definition, invalid. It's
something that will vary depending on their needs.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-05-17 16:25:01 | Re: add server include files to default installation? |
| Previous Message | Steve Crawford | 2004-05-17 16:21:54 | Re: Email data type |