"John P. Rouillard" <rouilj@terminus.cs.umb.edu> writes:
#
# The example aliases provided with digest look like (unecessary
# elements stripped):
#
# firewalls-digestify: "|/usr/local/mail/majordomo/wrapper digest -r -c /usr/lo
# cal/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-di
# gest-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.
General principles. I had more faith in "resend" being able to get
all the header hacking right than "digest".
# 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.
That, too.
-Brent
--
Brent Chapman Great Circle Associates
Brent@GreatCircle.COM 1057 West Dana Street
+1 415 962 0841 Mountain View, CA 94041
|
|
