In list.lst on         Wed, 23 Aug 1995 03:02:55 -0500,
Winship <[log in to unmask]> writes:
> Wouldn't a "distribute"  job take care of that?  Or if you don't want
> to do that, put your item in the filelist, then do a "give" for the
> whole list?
>
> Totally off the wall, if one's list has digest subscribers, and one
> changes the list header to turn off digest, then puts it back to
> allow digest again, what happens?  Digest subscribers blown away?
> Everyone reset to mail then back to digest? Total crash of the list?
> LISTSERV won't accept the header change so don't try it?  Other?
 
This is a bit sloppy, but it should work, especially if you
read/reply to e-mail offline, so that everything happens in
sequence:
 
        To LISTSERV:
        Q listname WITH DIGEST
 
                Make a 2nd copy of the received list and do
                the following:
 
                Edit out everything except the addresses.
 
                -UNDIGEST-
                QUIET SET listname MAIL FOR [log in to unmask]
                QUIET SET listname MAIL FOR [log in to unmask]
                QUIET SET listname MAIL FOR [log in to unmask]
 
                -REDIGEST-
                QUIET SET listname DIGEST FOR [log in to unmask]
                QUIET SET listname DIGEST FOR [log in to unmask]
                QUIET SET listname DIGEST FOR [log in to unmask]
 
        Create the urgent message in a text file  -URGENT-
 
        Send -UNDIGEST- to LISTSERV
                all digest subscribers will receive the rest
                of the current digest
 
        Send -URGENT- to listname
 
        Send -REDIGEST- to LISTSERV
 
 
This should work, shouldn't it, Eric?
 
 
Ken
[log in to unmask]
current owner of the Children's Rights List <[log in to unmask]>
current owner of the Minister's Discussion List <[log in to unmask]>