|
Sender: |
|
Date: |
Thu, 4 Mar 2010 16:59:12 -0500 |
Reply-To: |
|
Message-ID: |
|
Content-Transfer-Encoding: |
7bit |
Subject: |
|
From: |
|
Content-Type: |
text/plain; charset=ISO-8859-1 |
In-Reply-To: |
<000301cabbc6$5bdab8e0$13902aa0$@edu> |
MIME-Version: |
1.0 |
Comments: |
|
On 3/4/2010 13:13, Steve Eckard wrote:
> Here I go again. Hope these questions don't seem to silly, but I ask because
> I don't know. I have a user who is subscribed to a list which does not have
> the digest keyword defined in the configuration. However, it seems she is
> getting a number of messages at one time indicating the digestification. I
> guess I do not know what the following means in that "users sign up for
> digestified". How do they do that and receive them without the digest being
> defined in the congiguration. It seems contradictory to me. Thanks once
> again.
>
> Users sign up for digestified rather than immediate delivery with 'SET
> listnameDIGests', while indexes are selected with 'SET listname INDex'.
> These two options are alternatives to MAIL and NOMAIL. When switching around
> between these delivery options, users will observe the following behavior
> (digests will be assumed to be daily for the sake of clarity):
>
Some LISTSERV keywords have default values; digest= is one of them.
The list owner controls the availability and frequency of digests
through the "Digest=" list header keyword, which defaults to "Digest=
No" for lists without an archive and "Digest= Yes,Same,Daily" for
archived lists.
Apparently, this list is archived, so it defaults to daily digests.
--
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame
|
|
|