Great Circle Associates Majordomo-Workers
(November 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Majordomo mails itself
From: Brock Rozen <brozen @ webdreams . com>
Date: Thu, 7 Nov 1996 03:29:33 -0500 (EST)
To: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Cc: majordomo-workers @ greatcircle . com
In-reply-to: <ufaram7f3ak.fsf@sina.hpc.uh.edu>

On 6 Nov 1996, Jason L Tibbitts III wrote:

> I think the second suggestion makes sense, but there's always a better one
> somewhere.  I don't think there's anything that will prevent all loops.

How about a field that limits the number of messages sent through the list
per day? 

Could be just like the config file keeps track of the digest numbers.
You'd need three fields, from what I can see. One keeps the current
number, one keeps the max number, one keeps the date of the last message
sent.

Whenever a message gets sent through and passes through all the
Approve stages, it'd read the date of the last message sent. If it's not
the same date, it resets the counter to 1 (since this message is the first
to get sent through). If it's not the first, it then reads the max and
current and compares. If current ge (>=) max then reject the message. If
not then let it go through and increase the current by one.

 ------------------------------------------------------------------------- 
 | Brock Rozen | brozen@webdreams.com | http://www.webdreams.com/~brozen | 
 ------------------------------------------------------------------------- 



Follow-Ups:
References:
Indexed By Date Previous: Re: Majordomo mails itself
From: Brock Rozen <brozen@webdreams.com>
Next: Re: Dealing with multiple Reply-To:s and other message faults
From: Brock Rozen <brozen@webdreams.com>
Indexed By Thread Previous: Re: Majordomo mails itself
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Majordomo mails itself
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com