Ask your ISP if they understand what this set of aliases does.
nobody: /dev/null
test: "|/mj1945/wrapper resend -l test test-outgoing, nobody"
owner-test: dan,
test-outgoing: :include:/mj1945/lists/test", test-archiver, test-digestify
owner-test-outgoing: owner-test
test-archiver: "|/mj1945/wrapper archive2.pl -f /mj1945/archives/test -a -M"
test-digestify: "|/mj1945/wrapper digest -r -C -l test-digest test-digest-outgoing, nobody"
#test-request: "|/mj1945/wrapper request-answer test"
test-request: "|/mj1945/wrapper majordomo -l test"
test-approval: owner-test
test-digest: test
owner-test-digest: owner-test
test-digest-outgoing: :include:/mj1945/lists/test-digest,
owner-test-digest-outgoing: owner-test
test-digest-request: "|/mj1945/wrapper majordomo -l test-digest"
test-digest-approval: owner-test
These aliases have dependencies on settings in majordomo.cf of course,
but just to give you an overview;
All messages sent to the list address test, are piped through the resend
script so settings in test.config will be used.
Resend evaluates the message and processes/forwards messages to the
test-outgoing alias (address).
All messages sent to the test-outgoing address are also delivered to the
list subscribers, the archiver alias and the digestify alias.
The archiver alias appends messages to a file.
The digestify alias keeps copies of the message in a special work directory
until a setting in the test-digest.config file is reached, or you execute
a mkdigest command against that list.
Any message sent directly to the test-digest alias (address) are redirected
to the proper alias of test where the message can be properly processed as
above.
Dan Liston
The
Ron Carson wrote:
>
> Hello:
>
> My ISP indicatest that when they set up a digest list it will be a
> separte list from the non-digest list and that messages are not shared
> between the lists. Surely, this can't be correct. Is my ISP or me in
> left field?
>
> Ron
References:
|
|
