Digest mode

Rick Walker (walker@cutter.hpl.hp.com)
Thu, 02 Nov 1995 12:39:06 -0800

Dear Andy,

I get enough queries on setting mail modes, that I thought I'd
answer your question on the list.

> I've just asked the listprocesser, but there's no help on "digest".
> If I send "set cp digest" can I "undigest" it later? I want the list
> on digest whilst I'm away on holiday for 2 weeks, then back to not
> digest when I get back. Is this possible?

The query "HELP" sent to listserv@opus.hpl.hp.com gives a comprehensive
list of all listserv commands. There is no help on "DIGEST" because the
command is actually "SET":

"SET CP MAIL ACK" ;send back a carbon-copy of postings
"SET CP MAIL NOACK" ;don't send back acknowledgments
"SET CP MAIL DIGEST" ;bundle daily messages into digests
"SET CP MAIL POSTPONE" ;discard mail until mode is reset

You can change your mail mode as often as you want. It takes effect
on the next message sent.

I changed the default for new subscribers to DIGEST several months ago.
The old default was NOACK. I made the change because it greatly reduces
the number of error messages that I receive when mail starts bouncing.
With DIGEST, I get one error msg per person per day. With ACK or
NOACK, I get 10 or 15 errors per person per day.

I would recommend that most people stay on DIGEST unless their mailers
are very reliable. My policy is that, upon receipt of bounced mail
notification, I set the offending account to DIGEST. I then let the
errors continue for up to three days. If the errors are still occuring,
I then delete the subscriber from the list. With 460 subscribers, I've
had to become fairly ruthless to keep the administrative overhead under

If you ever suspect that you've been bumped off the list, then you might
try a "RECIPIENTS CP" query. If your name is on the distribution list,
then you know that the mail is going out, but is hung up somewhere in
the network. If your name is missing, then you can assume it's been
deleted, and you should resubscribe.

If all else fails, send me a note at walker@opus.hpl.hp.com, and I'll
try to track down the problems at this end...

Best regards,

Rick Walker