The example aliases provided with digest look like (unecessary
elements stripped):
firewalls-digestify: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/local/mail/digest/firewalls-digest.cf"
firewalls-digest-send: "|/usr/local/mail/majordomo/wrapper resend -p bulk -l Firewalls-Digest -f Firewalls-Digest-Owner -h GreatCircle.COM -s firewalls-digest-outgoing"
firewalls-digest-outgoing: :include:/usr/local/mail/lists/firewalls-digest
Why use resend when sending out a digest? It looks like digest will
compose all of the headers etc properly without the need to run resend
at all. I.E. all of the rewriting of resend is already embodied in
digest, so why have resend in the loop at all.
It looks like the example aliases slice may have been a historical
setup before digest got enough smarts to set the To:, and Precedence:,
and Reply-to: headers.
The reason I bring this up, is that I am working on integrating digest
into the majordomo package wrt the configuration file
modifications. It would make life a lot easier if digest was able to
be run without using resend at all. Then I would be able to use items like:
trailer_text,
precedence,
reply-to
for digest, if digest was being used as the output filter, or resend
if resend was used as the output filter.
-- John
John Rouillard
Special Projects Volunteer University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480
===============================================================================
My employers don't acknowledge my existence much less my opinions.
|
|
