Robert Covell wrote:
>
> We do this exact thing for our client base. Several of our clients run MJ
> lists that we provide Majorcool as an admin frontend. Each of the clients
> has a different domain (i.e. virtual). So in the config for MJ we have
> separate cf files for each used by the aliases. For Majorcool you have to
> setup different .sh files for each domain (i.e. virtual) that will generate
> a different cgi that is specific for that domain. If you ever change the
> lists (add/del) that MJ is severing you will have to run mj_key_cache
> against the specific cf file for that domain. Hope this helps a little bit.
Actually I really have no idea what you're saying, it seems all rather
vague.
I have tried to run the config for Majorcool twenty times to make sure I
wasn't missing a configuration option that allowed me to specify where the
lists directory was, but there just doesn't seem to be an option like that.
I can generate different cgi/config files for different domains but they
don't do anything else than the previous one... they try to read the lists
dir.
*All* my domains use the same Majordomo installation and the *same*
Majordomo.cf.
--
Shena Delian O'Brien * http://www.darklock.com/shena/
The Graphics Kitty! * http://www.darklock.com/abstract/
Fantasy Age * http://www.darklock.com/fantasy/
Follow-Ups:
References:
|
|
