On Sun, 10 Nov 1996, Brock Rozen wrote:
> Wouldn't it also require saving state on a grand scale? (whole messages)
>
> Saving state on message ids for 24 hours (per id) is fine. I even have
> such a filter on my own personal mail system which saves a few k of ids.
> Saving addresses and subjects also is fine, if only for 24 hours. But
> saving whole messages for just 24 hours can take up considerable space.
Saving state on message id's only helps you if the exact same message gets
resent repeatedly, ie: via a broken mail system. This is, of course,
something that should be done, but my problem is with messages that are
from automated sources (ie: bounces and vacation programs) which generate
unique message ID's.
A subject match may be useful, but I think a better way would be to have
a database of e-mail address vs. # of messages received in a 24 hour
period. In terms of majordomo itself, I would like it see it send a
maximum of 2 help messages every 24 hours, and then silently ignore any
further messages that do not contain valid commands. I don't know if
you'd want to use that sort of a scheme to protect a mailing list, but if
so it could be useful on the order of, say, 10 or 20 posts per day from
the same individual.
I don't think any of these techniques alone are going to solve the
problem, but most are very easy to implement so why not do all we can.
If you make it configurable, the user can decide to turn off the more
aggressive measures.
Evan
--
Evan Champion * Director, Network Operations
mailto:evanc@synapse.net * Directeur, Exploitation du reseau
http://www.synapse.net/ * Synapse Internet
Follow-Ups:
References:
|
|
