Interesting idea. I can't imagine how to implement it, though.
And in several years, I've never seen a need for anything like it.
Implementation would be tricky: where would state be kept? Would
it throttle _all_ email messages? Only duplicates from the same
source IP address? Only those for the same REQUEST_URI? Only
those that issue the same warning/error messages?
Need: I've been using this module, in various incarnations, for
maybe 5 years. Sometimes the email volume is more than I want,
but I know how to hit "d" and how to write procmail rules. I
want to make the decisions about which emails are dups. I don't
want to leave that decision up to CGI::Alert. I assume that if
anyone out there is using this module, they know how to handle
email.
If it turns out that someone is actually using CGI::Alert, and
sees this as an important requirement (and can give me guidelines
on how they need it implemented), I'll take a look. But as a
wishlist item, I'm afraid there's just no time or motivation
for me to work on it.
Thank you for the suggestion, though!
