>From Bryan Montgomery:
> Basically, I was wondering whether anyone out there is using
> majordomo on SCO and could help me.
Yes, we're doing it. Obviously you have to get perl working first.
There are a couple of differences between mmdf and sendmail. Some
make it better. MMDF (at least on our 126.96.36.199) can specify the user
to run as, when it pipes things to a program. Make mmdf the
owner of all majordomo stuff, pipe things with "mmdf|/..." so
mmdf is the uid running it, and don't bother with wrapper. (I've
not seen any security risks to doing it that way, it is certainly
more secure than running it as root, which is the way most of the
folks on the list seem to solve their problems...) MMDF doesn't
cooperate very well if you want to put your own headers on a note,
unless you are running as mmdf or root.
We decided to use mmdf's list channel to handle the outgoing list
mail. (Clever, huh?) This means that we can't just use the sendmail
that comes with it -- or if we can, I hope someone will let me know.
What I've been using is an under-documented progam called /usr/lib/mail/execmail
that seems to work just like sendmail. (It is mentioned in one flow chart
in the paper manual as being an intermediary between mail and submit.)
As long as you make sure there is a $to on the command line it uses,
it seems to work fine. The address for resend (if you are using it for
administrivia checking) is listname-outgoing@list-processor, which
is aliased to the usual ";include:/path/to/lists/listname" type of statement.
I think there is one place in resend where you need to change the sendmail
to execmail, otherwise changing it in majordomo.cf works fine.
email@example.com or MERRILL COOK on Ecunet/PresbyNet