Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!ames!lll-winken!uunet!nuchat!steve
From: steve@nuchat.UUCP (Steve Nuchia)
Newsgroups: comp.mail.sendmail
Subject: Re: sendmail parsing questions: "%"
Message-ID: <7407@nuchat.UUCP>
Date: 29 Apr 89 03:43:15 GMT
References: <701@arisia.Xerox.COM> <1410011@hpfclp.SDE.HP.COM> <237@crdgw1.crd.ge.com> <7306@nuchat.UUCP>
Reply-To: steve@nuchat.UUCP (Steve Nuchia)
Organization: Houston Public Access
Lines: 36

That's me, the 1989 hoof-in-mouth disease poster child |
						       V
In article <7306@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes:
>The hard-wired address parsing logic that invokes the rules takes
>care of the syntactic angle brackets -- the rules never see brackets
>in their input.  Any comments associated with an address, ie

>	Comm Ent <foo@bar>
>or	foo@bar (Comm Ent)

>are stripped off before calling the rules and added back to
>what the rules return when they are done.  If you see something


That is only half right.  The hard logic sees and remembers the
bracketing and comments but passes the whole address to the
rewrite logic.  It then wraps whatever gets returned in the
remembered text.  My sendmail today greeted me with an
address of the form:

	First Last <First Last First Last First Last foo@bar>

proving conclusively that I didn't know what I was doing.

In the above case my S3 was getting "First Last <foo@bar>"
and returning, ultimately, "First Last foo@bar".  This
got the remembered text added back: "First Last <First Last foo@bar>".
A few relays later it was a real mess :-(

So, ignore me, leave the "basic RFC822 parsing" line at the
beginning of S3, and make sure you don't call it from another
rule without defocusing the address first.
-- 
Steve Nuchia	      South Coast Computing Services
uunet!nuchat!steve    POB 890952  Houston, Texas  77289
(713) 964 2462	      Consultation & Systems, Support for PD Software.