Well...

To Nathan: My reading of Daily-Threshold is that it limits the number of 
postings to the list per day. Why does that affect the CRC check tracking? 
If that's true does it imply that CRC tracking is reset every day at 
midnight? That doesn't fit with what I'm seeing.

To Harry: That's a good idea if I could get everyone to remember it which 
is unlikely. The list name is the generally published alias for sending 
mail to all members of a department. I might be able to educate the people 
that this is currently affecting, but it doesn't solve the problem in the 
long run for all users.

In looking at the documentation for Daily-Threshold, I found a keyword 
called NoCRC. I don't know how I missed this when I was looking before. :( 
I'll give it a try.

Thanks all,

  - Mark



On Fri, 23 Sep 2005, A. Harry Williams wrote:

> On Fri, 23 Sep 2005 08:41:29 -0500 Nathan Brindle said:
>> It remembers the number of messages specified by Daily-Threshold= for
>> the list. (50 default.)
>>
>> Nathan
>>
>> At 07:49 AM 9/23/2005 -0400, you wrote:
>>> Hi,
>>>
>>> We use listserv for some distribution only, announcement type, functions.
>>> Some of these have very similar, if not identical, messages posted regularly
>>> and I'm getting some complaints about messages bouncing with the "duplicate"
>>> message.
>
> We deal with that by putting either the date or date and time inside the
> body of the email for such lists.  It's enough to change the values to
> allow the posting, because it truly isn't a duplicate, and you can show
> that to people.
>
>
>>>
>>> So the question is: how long does listserv remember the CRCs of messages and
>>> is that time tuneable? It would seem to me that for anti-looping purposes
>>> the system would only need to remember CRCs for a week or so. No?
>>>
>>> Thanks for any help,
>>>
>>>  - Mark
>>> --
>>> Mark Berman, Director for Networks & Systems
>>> Williams College, OIT, Jesup Hall
>>> Williamstown, MA. 01267          413-597-2092
>