peter@aucs.AcadiaU.ca (Peter Steele) (02/14/91)
We are using two Unix machines and two PC networks, all tied together
over ethernet. We use elm on the Unix machines and Pegasus mail on
the PCs. We have mailing groups set up for different interests and
we want to archive all messages sent to those groups. For example,
we might have a mailing group called network-tr for "Network Trouble
Report" with members tom@thor, fred@loki, joe@zeus, and last but not
least network-tr@archive-host (where archive-host is one of our Unix
machines). What I did was set up an alias on archive-host that looks
like
network-tr: "| cat >> /u/archive/network-tr"
which simply appends any messages send to network-tr@archive-host to
the file "network-tr" on account "archive". People log into account
archive and browse the archives using elm. However, the only way I can
seem to get this to work is to make the account and file world writeable,
which is not acceptable. I've played around with group protection but
can't seem to get something that works. When an alias like this is
executed, what daemon is doing it? I would think I could then make the
archive files to be owned by that entity so that it can append to the
archive files and give the archive account group read/only access so
that people can log into archive and read the archives with elm. Does
this sound reasonable or should I take another approach?
--
Peter Steele, Systems Software Analyst
Acadia University, Wolfville, NS, Canada B0P1X0 (902)542-2201x121
UUCP: {uunet|watmath|utai|garfield}!cs.dal.ca!aucs!Peter
BITNET: Peter@Acadia Internet: Peter@aucs.AcadiaU.CArickert@mp.cs.niu.edu (Neil Rickert) (02/14/91)
In article <1991Feb14.133533.10078@aucs.AcadiaU.ca> peter@aucs.acadiau.ca (Peter Steele) writes: > > network-tr: "| cat >> /u/archive/network-tr" > > However, the only way I can >seem to get this to work is to make the account and file world writeable, >which is not acceptable. I've played around with group protection but >can't seem to get something that works. When an alias like this is This is a 'sendmail' feature, although some label it as a misfeature. For a local sender, the command is executed with the permissions of the mail sender. For a sender from a different system, it uses the permissions of daemon. The term 'local sender' above needs some interpretation. On a network which shares common mail names, a sender on any of the workstations in the network might be considered local. I don't guarantee the following will work. It may depend on the version of 'sendmail'. Try: network-tr: :include:/usr/lib/mail/network-tr and in the file /usr/lib/mail/network-tr have the single entry: "| cat >> /u/archive/network-tr" Of course you can choose a different name and path for your ':include:' file if you wish. But try making it owned by daemon and in group daemon. Recent versions of sendmail use the ownership/group of the ':include:' file to run such a program. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science <rickert@cs.niu.edu> Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940