On 18 Jul 1996, Jason L Tibbitts III wrote:
> Ideally each list could have it's own mailer configuration so that one list
> could just run "sendmail -flist-owner" while another could specify it's own
> queuing directory and another could call some other program for delivery.
> (My specific case involves calling TLB for delivery, which would eliminate
> the need to have any outgoing aliases. Unfortunately TLB needs the name of
> a list-specific config file on the command line.)
> The problem I'm running into is that we've been relying on the aliases file
> for any kind of list-specific configuration that you don't want the list
> owner to be able to change (like the use of archive2.pl and such).
The issues to be concerned about are:
1) Security holes. If the list-owner can change what program gets called
then they might open up some holes. I'm not an expert on this, but it's
something to be concerned about.
2) Breaking it. What if the list-owner puts something in that no longer
works? Will there be a default setting? Will they know what to change it
back to? Will majordomo accept invalid settings?
I think a solution that we should think of should go like this.
Incorporate in majordomo.cf a new variable called mailer_default. It will
specify what the default command line setting is for lists that are not
specified seperately. To cover up a security hole, the configuration for
each list would then be either in a seperate file and be called up each
time a list had to send a message, or it could be in the majordomo.cf
file. This way, only the administrator could change it, while still
allowing each list to have it's own setting. If a list didn't have a
setting then it would default to mailer_default.
Thus, if a system ALWAYS wanted to use a specific mailer, it would only
have to specify mailer_default. If a system wanted different ones for each
list, it could do that also. If they forgot to specify some lists, it
would STILL work by going to the default. Since the settings are listed in
majordomo.cf you cover a potential security hole by not having them in
each list's individual config file (although if it's NOT a security hole,
then I see no reason not to put it there).
Also, just for incompetency's sake, it'd be nice if you could specify:
list_mailer = $mailer_default
Thus, if you broke it and don't know what to go back to, you could still
always go back to the default and know that that works.
Thanks,
-------------------------------------------------------------------------
| Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen |
-------------------------------------------------------------------------
Follow-Ups:
References:
|
|
