>>>>> "BR" == Brock Rozen <firstname.lastname@example.org> writes:
BR> How about a field that limits the number of messages sent through the
BR> list per day?
I thought I'd already covered this, but:
1. We're talking about majordomo, not resend, although loop prevention
makes some sense to both. Fortunately resend already has taboo_* which
2. It's hard to do this without limiting proper use. I suspect that my
frequent messages to majordomo-users would get flagged as a loop.
Extending thins to have a list of addresses which aren't flagged as
loops just bloats the whole thing even more. A simple n messages per
day or 1 message per n minutes is simply not good enough.
3. Storing and checking state is expensive. Think of large lists with lots
of contributors. Now you have to a bunch of extra file operations for
every message. People already say that Majordomo has too much overhead.
This is a tough problem. Try to think about the boundary cases, not just
small lists with few subscribers and low traffic.