Let me answer your second question first. The user
removes themself from the normal list and adds themself
to the -digest of the same list. This *can* all be done
in the same message to majordomo.
Ratsky wrote:
> What do my config settings for digest mean in plain English?
> Thanks a million! Is it all set to do digests properly?
> How do I switch someone to digest mode?
> John
# digest_archive
# [absolute_dir] (undef) <digest>
# The directory where the digest archive is kept. This item does
# not currently work. Leave it blank.
>
> digest_archive =
You need to leave this one blank.
>
> # digest_issue [integer] (1) <digest>
> # The issue number of the next issue
> digest_issue = 1
When your digests are sent out, this issue number gets
incremented by one. Just like the issue number of any
other magazine or periodical.
>
> # digest_maxdays [integer] (undef) <digest>
> # automatically generate a new digest when the age of the oldest
> # article in the queue exceeds this number of days.
> digest_maxdays =
The digest script queues up messages until this setting,
the next setting, or maxlength is exceeded. If the oldest
message in the queue is "older", not equal to, this setting,
a digest will be created that combines all the messages in
the queue to one message.
# maxlength
# [integer] (40000) <resend,digest>
# The maximum size of an unapproved message in characters. When
# used with digest, a new digest will be automatically generated if
# the size of the digest exceeds this number of characters.
maxlength = 40000
This one does the same as above, but instead of days old,
the trigger is on the total number of bytes added up for
every message in the queue.
>
> # digest_maxlines [integer] (undef) <digest>
> # automatically generate a new digest when the size of the digest
> # exceeds this number of lines.
> digest_maxlines =
Again, this is the same as the previous two, but the number of
message body lines (and maybe headers too) for the total queue
of messages is the trigger to create and send the digest.
>
> # digest_name [string] (cpps) <digest>
> # The subject line for the digest. This string has the volume and
> # issue appended to it.
> digest_name = cpps
This works like subject_prefix, except this is expand to include
the v1-n001 appended too. V for volume number and N for issue
number.
>
> # digest_rm_footer [word] (undef) <digest>
> # The value is the name of the list that applies the header and
> # footers to the messages that are received by digest. This allows
> # the list supplied headers and footers to be stripped before the
> # messages are included in the digest.
> digest_rm_footer =
If you use the message_footer setting in the non-digest version
of your list, this setting will remove it from all messages in
the digest waiting queue as it combines them all for distribution
as a single message.
>
> # digest_rm_fronter [word] (undef) <digest>
> # Works just like digest_rm_footer, except it removes the front
> # material.
> digest_rm_fronter =
Same as above, but for the top side of the message body instead
of the bottom.
>
> # digest_volume [integer] (1) <digest>
> # The current volume number
> digest_volume = 1
This goes along with the digest_issue setting. The difference
here is that this one is not automatically incremented each
year like magazines and periodicals are.
>
> # digest_work_dir [absolute_dir] (undef) <digest>
> # The directory used as scratch space for digest. Don't change
> # this unless you know what you are doing
> digest_work_dir =
Leave it blank. It will just get you into trouble.
Dan Liston
Follow-Ups:
-
Re: Digest
From: "Roger B.A. Klorese" <rogerk@queernet.org>
References:
|
|
