On Mon, 15 Mar 1999 00:39:53 -0800 Sherry Beauchamp said:
>>Ben Chi wrote:
>>>
>>> We operate a number of lists here that are rebuilt on a daily basis from
>>> data in the student database.  That is to say, the subscribers are not
>>> specified with ADD commands but rather by submitting them in a XXX LIST
>>> file each morning that overlays the old copy.  Such a file would look
>>> like:
>>
>
>I don't think you have to go to this trouble -- I believe the reason this
>is happening is because your lists are overwriting, and these options were
>at some time in effect.  Since you never DELETE the subscribers from the
>lists, your default options never kick in.  I see two options:

Ben is completely replacing the subscribers, so previous defaults
don't apply.  The problem is that "Default-options" are only relevant
at ADD time, and no other.  There was another comment about doing
a "QUIET SET listname REPRO FOR *@*".  I believe that this is the only
available supported option.  Another option would be to do this once,
obtain the flags from after column 80, and change your build routine
to include them.  This would not be suported, and has the problem
that some of that information includes subscription date, last
probe date, etc.  Since you rebuild the list nightly, there would
be no need for a probe, so this might work.

>
>We similarly regenerate our mailing lists from a database, but we first
>delete all subscribers from the lists rather than overwriting, and we
>haven't had the problem you describe.  You might rewrite your regeneration
>script to delete all lists before rewriting them.

By doing this with a PUT (actually a PUTALL I believe), Ben is
overwriting.  He isn't doing an ADD.  I'm doing a similar thing, but
since we don't change the default options, it isn't a problem for us.
It is faster, and less messy on the console, to do the PUT, and
lots of ADDs.

>
>
>Sherry
/ahw