On 30 Apr 1997, Rich Pieri wrote:
> As they should. What you want to do now is cross your list aliases so that
> mail to "list" and mail to "list-digest" go to both the subcribers of
> "list" and the digest program which will eventually send out a digest to
> the subscribers of "list-digest":
That part works great. Here is a section of my aliases for verification
(please excuse line wraps):
biglist : "|/majordomo/wrapper resend -l
biglist -h creighton.edu biglist-outgoing"
biglist-outgoing : :include:/majordomo/lists/biglist,
"|/majordomo/wrapper archive2.pl -a -m -f
/majordomo/archive/biglist.archive/biglist", biglist-digestify
biglist-digestify : "|/majordomo/wrapper digest -r -C -l
biglist-digest biglist-digest-outgoing"
biglist-digest : biglist
biglist-digest-outgoing : :include:/majordomo/lists/biglist-digest
Anyone responding to a digest goes through the correct channels and is
posted to both lists. But the digest headers include the actual system
name instead of the site-hidden version. Its not a big deal, but we move
things occasionally and in the long run it is easier this way.
List Headers (looking good!):
From: Virtual Joe <jduche@creighton.edu>
Reply-To: biglist@creighton.edu
To: biglist@creighton.edu
Subject: [BigList] Nun joke...
Digest Headers (notice addition of system name):
From: "[BigList-Digest]" <owner-biglist-digest@mail.creighton.edu>
Reply-To: biglist-digest@mail.creighton.edu
To: biglist-digest@mail.creighton.edu
Subject: [BigList-Digest] V1 #65
See what I mean? If I set the resend_host, the digest is created but not
sent out. I hate that.
*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*
*: Joe Ducharme jduche@creighton.edu :*
*: Creighton University Omaha, NE USA 68178 :*
*: <<Virtual Joe -=> http://www.creighton.edu/~jduche/>> :*
*: "Time flies like an arrow, Fruit flies like a banana." :*
*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*:*
|
|
