Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!smoot
From: smoot@cs.utexas.edu (Smoot Carl-Mitchell)
Newsgroups: comp.mail.uucp
Subject: Re: uucp mail question
Keywords: uucp mail somewhere address paths
Message-ID: <11155@cs.utexas.edu>
Date: 14 Aug 90 00:12:54 GMT
References: <987@fico2.UUCP> <863@gvlv2.GVL.Unisys.COM> <1990Aug13.221553.17992@mp.cs.niu.edu>
Distribution: usa
Organization: U. Texas CS Dept., Austin, Texas
Lines: 23

In article <1990Aug13.221553.17992@mp.cs.niu.edu> rickert@mp.cs.niu.edu (Neil Rickert) writes:
>
>From ADMS-RAD.Unisys.COM!chris Mon Aug 13 15:01:00 1990
>
> This is the best choice in many cases.  Many versions of 'rmail' will accept
>it, in spite of their being no 'remote from' because there is at least an '!'.
>Furthermore, if this is pumped into 'sendmail', most versions of 'sendmail.cf'
>will convert 'ADMS-RAD.Unisys.COM!chris' to 'chris@ADMS-RAD.Unisys.COM'
>leaving a valid RFC822 address.

All this ``From_'' line nonesense is why I wrote a version of rmail which
takes only domain names and adds the sender's domain address as a
argument to rmail with an '-f' flag.  Its really a sendmail firewall which
disallows remote uucp users from doing all the esoteric things which sendmail
can do (rebuild alias DB, enter test mode, use an alternate configuration, etc).

I call it ``rmaild'' and it assumes there is no ``From_'' lines in the 
message header.  Works pretty well.  I use it to send mail from 
``tic.com'' to the Internet with uucp transport, but I look like I'm
just another domain address.  If you want details, send me e-mail.
-- 
Smoot Carl-Mitchell, Texas Internet Consulting
smoot@tic.com, smoot@cs.utexas.edu