Spider Boardman <spider@Orb.Nashua.NH.US> writes:
> Yes. (Despite what Dave Barr said.) However, you have to
> twiddle the sample-alias handling of the digest. This does lose
> you the protection of having resend check for admin requests
> along the way, though. For that reason, I recommend doing what
> Dave said anyway, which is to have a closed and unadvertised list
> to which the digest is attached.
Thinking about it further, you can still use resend, why not change
"snork-digest" to:
snork-digest: "|/local/src/majordomo-1.93/wrapper resend -l snork-digest -h my.host.com snork-digester"
This will then gain you the advantage of resend, which will then pass it to
the digester.
> If you really want to have an 'pure' digest, though, here's some
> sample aliases (untested, but derived from an existing setup):
>
> owner-snork-digest: snork-sender,
> snork-digest-approval: snork-sender
> owner-snork-digest-approval: snork-sender
> #owner-snork-digest-outgoing: owner-snork-digest
> snork-digest-request: |"/local/src/majordomo-1.93/wrapper request-answer snork-digest"
> owner-snork-digest-request: snork-sender
> snork-digest-owner: snork-sender
> snork-digest:snork-digester
> snork-digester: |"/local/src/majordomo-1.93/wrapper digester -r -C -l snork-digest snork-digest-outgoing"
> snork-digest-outgoing: :include:/local/share/mail/lists/snork-digest
> snork-sender: :include:/local/share/mail/lists/snork.owner
> owner-snork-sender: snork-sender
Frank
|
|
