Great Circle Associates Majordomo-Users
(December 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Digesting
From: Dan Liston <dliston @ netscape . com>
Organization: iPlanet E-Commerce Solutions, A Sun Netscape Alliance
Date: Thu, 21 Dec 2000 20:44:46 -0600
To: Todd Lyons <todd @ mrball . net>
Cc: ryan @ rhinointernet . com, Majordomo Users <majordomo-users @ greatcircle . com>
References: <OF75EE6C38.39ED9DDB-ON072569BB.005CF16A@rhinonet.com> <3A41362D.D450DEF5@mrball.net>

Todd Lyons wrote:
> 
> Then, this section is what makes the digest work.  Note the one odd line
> (cerritoslug-digest: cerritoslug).  The functionality of that line eludes me
> slightly, but it has to be there.  Doublecheck to make sure that yours has
> the same structure as these.

The functionality is to send mail addressed directly to the digest back 
into the primary list, where it can "then" be digestified.  How can a 
message be part of a digest if it was never included in what gets digested.
The digest is a compilation of messages from "the list", not a separate list
to have individual messages.  

Another point to make about digests, is if you use "restrict_post" in the
listname.config file that only allows list members to post, you should add
the listname-digest users post too.  Technically, a digest should never be
posted to directly, not even by the list owner.  If an announcement goes
out to the list, the list owner can force a digest to go out with a message
to majorodomo like;

mkdigest listname-digest listname-digest-outgoing listname-digest.passwd
 
Dan Liston



References:
Indexed By Date Previous: avoid attach and formatted messages
From: "Ricardo M. Morales" <especiales@interlap.com.ar>
Next: Re: avoid attach and formatted messages
From: "Adam H. Kerman" <ahk@chinet.com>
Indexed By Thread Previous: Re: Digesting
From: Todd Lyons <todd@mrball.net>
Next: Re: Digesting
From: Mike Oliver <Mike.Oliver@eng.sun.com>

Google
 
Search Internet Search www.greatcircle.com