Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site umd5.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!mit-eddie!think!harvard!seismo!umcp-cs!cvl!umd5!zben From: zben@umd5.UUCP Newsgroups: net.mail,net.mail.headers Subject: Re: Handling %'s and forwarding mail Message-ID: <628@umd5.UUCP> Date: Tue, 2-Jul-85 13:37:45 EDT Article-I.D.: umd5.628 Posted: Tue Jul 2 13:37:45 1985 Date-Received: Fri, 5-Jul-85 04:31:41 EDT References: <226@harvard.ARPA> <487@grkermi.UUCP> Reply-To: zben@umd5.UUCP (Ben Cranston) Distribution: net Organization: U of Md, CSC, College Park, Md Lines: 25 Xref: watmath net.mail:906 net.mail.headers:494 Summary: Some site require their own name? In article <487@grkermi.UUCP> starkman@mit-athena.ARPA (Eic N. Starkman) writes: >In article <226@harvard.ARPA> kevin@harvard.ARPA (Kevin Crowston) writes: >>What if I wanted to send all of my mail by forwarding it to a >>local "smart" machine with a decent mailer and letting it do >>all of the delivery? E.g. xyz is the smart machine; do I say >> >> RCPT TO:<@xyz.arpa:person1@site1.arpa,person2@site2.arpa> >You should use a separate RCPT TO: line for each person to receive the >message. > RCPT TO:> RCPT TO: >You don't need to put the @xyz thing in...after all, XYZ knows its own name. > The responses to the other questions look OK to me, its pretty much what we are doing for our BitNet gateway. Looking at headers is bad practice, for if the message has been forwarded once before it gets to you, the header will in general be out-of-sync with the out-of-band addresses. Unfortunately, the IBM mail system we interface with DOES look at the headers, so I have been forced to develop code to correlate the inband and out-of-band addresses. Some of our implementations, however, REQUIRE an "ourname" to be found at the head of the address, basically as an error check on other peoples site tables. So I disagree with the "you don't need to put in the @xyz thing" above... -- Ben Cranston ...{seismo!umcp-cs,ihnp4!rlgvax}!cvl!umd5!zben zben@umd2.ARPA