Path: utzoo!attcan!uunet!cs.utexas.edu!bcm!shell!nuchat!steve From: steve@nuchat.UUCP (Steve Nuchia) Newsgroups: comp.mail.sendmail Subject: Re: sendmail parsing questions: "%" Message-ID: <7306@nuchat.UUCP> Date: 27 Apr 89 16:39:23 GMT References: <701@arisia.Xerox.COM> <1410011@hpfclp.SDE.HP.COM> <237@crdgw1.crd.ge.com> Reply-To: steve@nuchat.UUCP (Steve Nuchia) Organization: Houston Public Access Lines: 27 In article <237@crdgw1.crd.ge.com> barnett@crdgw1.crd.ge.com (Bruce G. Barnett) writes: >In article <1410011@hpfclp.SDE.HP.COM>, diamant@hpfclp (John Diamant) writes: >>Right. The angle brackets are required for source routes. >But most sendmail.cf files I have seen include something like: > R$*<$+>$* $1$2$3 >It may be that the spec says angle brackets are required, >but is that really the case? The angle brackets you see inside sendmail rulesets are put there to "focus" the address by the rules themselves. This is not a requirement but a convention. 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 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 like R$*<$*>$* $2 basic RFC822 parsing near the beginning of S3 it is a no-op. -- Steve Nuchia South Coast Computing Services uunet!nuchat!steve POB 890952 Houston, Texas 77289 (713) 964 2462 Consultation & Systems, Support for PD Software.