random@dxtx.net wrote:
> majordomo-owner: -m
> owner-majordomo: -m
> owner-owner: -m
> listmanager: -m
> corp-pubs: "/etc/smrsh/wrapper mj_filter"
> #
> # new1 (UNAVAILABLE)
> #
> new1: "/etc/smrsh/wrapper mj_list-unavail new1"
> new1-request: "/etc/smrsh/wrapper majordomo -l new1"
I'll answer your question(s) with another question intended to stimulate
some deductive thought: How does mj_build_aliases know who the owner is
for each of the different aliases? Those tidbits are not something
Majordomo normally "knows" about....
For "majordomo-owner" et-al, the info comes from arguments you specify
on the mj_build command line. I think the fact that "-m" is there
indicates that you have something amiss in your invocation.
For each individual list-owner, the info is taken from the list.config
file *after* you have made a modification to the Majordomo source to
support the "owner" feature. See the Install docs -- of MajorCool, that
is -- for the specific changes to be made.
--bill
References:
|
|
