Re: empty quoted strings and other oddities

Keith Moore <> Wed, 02 October 2002 13:06 UTC

Received: (from majordomo@localhost) by (8.11.6/8.11.3) id g92D6L618528 for ietf-822-bks; Wed, 2 Oct 2002 06:06:21 -0700 (PDT)
Received: from ( []) by (8.11.6/8.11.3) with ESMTP id g92D6Jv18520 for <>; Wed, 2 Oct 2002 06:06:19 -0700 (PDT)
Received: from (localhost []) by (cf 8.9.3) with ESMTP id g92D6D026932; Wed, 2 Oct 2002 09:06:13 -0400 (EDT)
Message-Id: <>
From: Keith Moore <>
To: "Gary Feldman" <>
Subject: Re: empty quoted strings and other oddities
In-reply-to: (Your message of "Wed, 02 Oct 2002 08:33:36 EDT.") <002001c26a0f$f05437a0$b7880fce@alice>
Date: Wed, 02 Oct 2002 09:06:13 -0400
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

> > so? there are lots of addresses which are valid syntax but
> > not valid because the domain is not defined or the IP
> > address (in the domain literal) does not exist or is not
> > assigned to a host.
> I'm not sure I buy that reasoning.  You seem to be saying that since it's
> not possible to detect all invalid addresses syntactically that the ability
> to trap some syntactically (or more than currently trapped) is irrelevant.

no, I'm saying that 

- there is useful separation of function here between detecting syntax
  errors and detecting addresses that are invalid for other reasons that 
  should not be discarded 

- being able to detect that a few very-seldom-used addresses are
  illegal by means of syntax is of infintesimal value

- trying to detect a significant number of invalid addresses by means
  of syntax is likely to both increase errors (because there are more
  things that can go wrong) and to impair the utility of email addresses 
  at some future date.  

in other words, it's a fool's errand.