[ uunet!eworks.com!schapin writes: ]
> I think I must be missing something.... I am trying to set up archiving for
> my mailing lists. I read thru the documentation and it said you needed to
> use one of the archiving scripts, so I set up archive2.pl. I set up the
> aliases file the way it showed in the script, but I think I must be missing
> something. The aliases entry looks like this:
> list-archive: "|/usr/local/majordomo/wrapper archive
> -f /usr/local/majordomo/list-archive/list
> -m -a"
> The permissions are fine and I am not getting any errors in my logs. What I
> seem to be missing is the part that sends the post to list-archive. I saw
> nothing in the docs about doing that.
> Any help at all (and no flames please, I *did* read the docs :-)
Including this starting about line 51 of NEWLIST?
Finally, a more complete set of aliases that provides digestification,
archiving, and header manipulation would look like:
test:"|/tools/majordomo/wrapper resend -l test -h cs.umb.edu test-outgoin
# I put the digest and archive programs on the outgoing list so that
# messages bounced by resend don't end up in the digest or archive
# unless I send them through resend explicitly.
"| /tools/majordomo/wrapper digest -r -C -l test-digest test-digest-ou
---> "| /tools/majordomo/wrapper archive2.pl -a -m
---> -f /usr/local/mail/archive/test/test.archive"
# archive produces a monthly archive with the -m flag.
And this from Doc/majordomo.ora?
The aliases are:
- "listname-outgoing" is the actual list of people subscribed to
the list. The sendmail ":include:" directive reads the
---> subscribers list at the time a message is sent. If the list is
---> archived, add the name of the archive alias (like
---> "listname-archive") too.