Paul Wolstenholme said:
>
> I have just set up Majordomo 1.9.4 and MajorCool 1.3.0. I've setup a
> basic test list that works find. The problem I am having relates to
> setting up archived a digested lists via MajorCool. I can't get them to work.
> I thought that if you included the -a and/or -d in the
> mj_build_aliases.arg file that mj_build_aliases would great a archived
> and digested list if archive and digest exist is the usr/local/majordomo
> directory. Any assistance setting up archives with MajorCool would be
> appreciated.
All lists are not automatically archived and/or digested. There must
be some controls in place to know which are applicable; these
controls come in the form of "archive=yes/no" and "digest=yes/no"
keywords that have been added to Majordomo. So -a is only half the
story. You also need a list with archive=yes set. This is evidenced
in the snippet: if (&cf_ck_bool($list,'archive') && $opt_a) {
Digest support is similar, but be forewarned it probably doesn't
work. We don't run digests at my site, so I have had no reason to
validate the code. The whole reason mj_build_aliases is in /contrib/
is because it hasn't been sanity-checked by enough people. If I had
confidence that it worked for more than just me, I would make it a
more visible component rather than buried in the /contrib/ section.
--bill
Follow-Ups:
References:
|
|
