On Mon, 28 Sep 1998, Debbie Douglass wrote:
> Yes, I know this. I just wanted to know how to force a digest to
> occur -now- without having to wait until the normal distribution
> time.  Now I'm I resetting the digest distribution time in my
> list header to see if that will force it.

Ok, forcing a digest distribution is easy, just do a
QUIET SET listname MAIL FOR *@*

Everyone set DIGEST will get your "forced" digest.  Of course those
already set MAIL will not get it, and you will be turning on delivery
for those set NOMAIL.  If you want EVERYONE to see the digest, first,
QUIET SET listname MAIL FOR *@*
then
QUIET SET listname DIGEST FOR *@*
then
QUIET SET listname MAIL FOR *@*

and bingo, everyone subscribed to your list will get your "forced"
digest.  You will also probably have a lot of disgruntled subscribers, and
those already DIGEST will get it twice.  There may be a new flame war
directed at you.  That could be mollified somewhat if you have
scrupulously kept track of who was set DIGEST, MAIL, and INDEX before you
started wholesale changes, and you restore everyone to their chosen
options very quickly.  Most likely you will still get a lot of complaints,
on and off list.

I think most of the responses on list have been intended to indicate this
"forcing a digest" is perhaps not the best way to go about this, stop and
rethink.  I know mine was meant that way.

I would rather explain to 3,200 subscribers why I made the list fully
moderated to stop a flame war, than why I was playing hob with everyone's
mail options and sorry, if it isn't the option you want reset it yourself.

LISTSERV is rich in options for dealing with things like this, consider
all of them, combinations of them, whatever best suits.  As far as I can
see, making a lot more work for yourself and making all your subscribers
angry (even more work) at the same time is not the best solution.

You wanted bluntness, there it is.

Douglas