Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id PAA04235; Thu, 1 Jun 1995 15:27:38 -0400 X-Resent-To: drums@CS.UTK.EDU ; Thu, 1 Jun 1995 15:27:36 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from troy.software.com by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id PAA04176; Thu, 1 Jun 1995 15:25:50 -0400 Received: from rome.software.com ([198.17.234.100]) by troy.software.com (post.office MTA v1.6 ID#0-1001) with ESMTP id AAA93; Thu, 1 Jun 1995 12:21:16 -0700 X-Mailer: exmh version 1.5.3 12/28/94 To: Mark Crispin cc: drums@CS.UTK.EDU Subject: Re: changes In-reply-to: Your message of "Thu, 01 Jun 1995 01:31:47 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 01 Jun 1995 12:21:46 -0700 From: michael.derrico@software.com (Michael D'Errico) Message-ID: <19950601192115375.AAA93@rome.software.com> > I don't know if this is permitted by the charter or not, but I would like to > eliminate the following foolish (and commonly violated) requirements of 822: > > 1) Simplify the syntax, remove obnoxious restrictions: > a) Remove ".", "[", and "]" from specials. > b) Redefine local-part as word. > c) Redefine domain as atom. > d) Remove sub-domain, domain-literal, and domain-ref This would certainly clean up my address parser, but there is at least one case that would not carry forward to the new definition. Since is defined to be either an or a , you could no longer have something like: From: "Michael D'Errico"."Technical Support"@Software.com Granted this format is rarely (if ever) used, but it would become illegal under the new definition. Also, any mailer that currently folds long lines based on tokens could break a new system that uses these rules. For example, half of a domain name could be separated from the other half by CR LF SPACE (I believe zmailer used to do this). I'm in favor of these simpler rules, but we also need to make sure we consider all the effects. Mike