On Fri, 2 Apr 1999, Saleel Majeed wrote:
> Hi;
>
> My web hoster is having huge difficulties setting up MajorDomo. They
/snip/
>
> All us clients are able to modify these features perfectly in the config
> files, and MD even returns the "new config file accepted" email, but none of
> the features take effect.
/snip/
>
> >From what I've already heard on this list, I'm guessing it has something to
> do with "resend". But I have absolutely no idea what this is...
>
I think you've hit the nail on the head. Ask your host to read a little
more thoroughly the NEWLIST document. In the part where it describes the
aliases which must be defined for a new list, it gives first a very
simplistic set of examples, then goes right on to a *second* example which
includes the resend script. Use the second example. If you want to set
up digests or archiving, even deeper reading is required.
Quoting NEWLIST:
These would look like this:
test: :include:/usr/test/majordomo-1.94.3/lists/test
owner-test: you,
test-request: "|/usr/test/majordomo-1.94.3/wrapper request-answer
test"
test-approval: you
It's more likely that the outgoing messages to the list will be
passed through "resend" to catch Majordomo commands, as well as
give other useful features. A typical set of aliases without anything
fancy, such as archiving or digesting, would look like this:
test: "|/usr/test/majordomo-1.94.3/wrapper resend -l test
test-list"
test-list: :include:/usr/test/majordomo-1.94.3/lists/test
owner-test: you,
test-owner: you
test-request: "|/usr/test/majordomo-1.94.3/wrapper majordomo -l
test"
--
Rick Green
Please note my new address: <rtg@mich.com>
--------------------------------------------------------------------
Microsoft has just announced it is renaming Windows NT version 5 to
"Windows 2000."
Is that the ultimate millennium bug or what?
References:
|
|
