Hi All,
I have used majordomo for mailing lists but only simple one''s no digest or
archiving, but since wanted to try a mailing list with archiving and
digesting. From most of the info I have read and all the debugging getting
this thing worked out, however, I am not sure what is all happening. I
wanted to set up two lists quake2, quake2-digest. I am assuming that
digest sends out mail at intervals designated by the cron job or the
quake2-digest.config. and the regular list gives out mail when it is
spent. Can you take a look at this and offer some suggestions or point out
my flaws.
thanks
Joe
My Current aliase entry.
quake2: "|/usr/local/majordomo-1.94.4/wrapper resend -l quake2 -h
rogueserver.mbayweb.com quake2-outgoing"
quake2-outgoing: :include:/usr/local/majordomo-1.94.4/lists/quake2,
quake2-archive, quake2-digestify
quake2-request: "|/usr/local/majordomo-1.94.4/wrapper majordomo -l quake2"
quake2-approval: rogue
quake2-owner: rogue
owner-quake2: rogue
owner-quake2-outgoing: rogue
quake2-digest: quake2
quake2-digestify: "|/usr/local/majordomo-1.94.4/wrapper digest -r -C -l
quake2-digest quake2-digest-outgoing"
quake2-digest-outgoing:
:include:/usr/local/majordomo-1.94.4/lists/quake2-digest
quake2-digest-request: "|/usr/local/majordomo-1.94.4/wrapper majordomo -l
quake2-digest"
quake2-digest-approval: rogue
owner-quake2-digest-outgoing: rogue
quake2-archive: "|/usr/local/majordomo-1.94.4/wrapper archive2.pl -f
/usr/local/mail/archives/quake2-digest.archive/quake2-digest -m
-a"
|
|
