From: Bruno Wolff III <bruno@wolff.to>
To: Matthew Price <pricem@juno.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: RFC822 Checker
Date: Fri, 30 Aug 2002 09:26:40 -0500
Message-ID: <20020830142640.GA28639@wolff.to> (raw)
In-Reply-To: <20020830.100812.20767.2685@webmail6.nyc.untd.com>
References: <20020830.100812.20767.2685@webmail6.nyc.untd.com>
On Fri, Aug 30, 2002 at 14:07:28 +0000,
Matthew Price <pricem@juno.com> wrote:
> Howdy,
>
> Does anyone know of an SQL function that will check a string for compliance with the RFC822 mail address spec? I have a script that sends mail from a db (no, I am not a spammer) but I often have mails sitting in my queue because the MTA (correctly) refuses to process some of the bogus things that users enter by mistake.
You might consider storing the unecoded address. If you are using an MTA that
doesn't provide a way to input unencoded addresses (e.g. sendmail), you can
encode the address before passing it to the MTA or adding it into a header
if you need to do that. It isn't even that hard to tack on the person's
name (from somewhere else in your database) or other comment on when putting
the encoded address into a message header.
When collecting input you might ask for confirmation when seeing unusual
addresses. This should cut down on the number of bogus ones that get into
the sysem.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bruno@wolff.to, pricem@juno.com
Subject: Re: RFC822 Checker
In-Reply-To: <20020830142640.GA28639@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox