Milter-greylist

--- In milter-greylist@yahoogroups.com, manu@... wrote:
> I'm not really hostile, but I'd like comments from other users. Any
> input, anyone?

I'd like to pursue this a little more. From what you and another has posted
a reasonable implementation would be as follows:

An optional global (non-acl) conf argument, that defaults to off, i.e. current
behavior. Optionally, purge whitelists and perhaps -- as a parameter --
greylists.

To go over the rational again for this behavior; if, for example, spamassassin
is running via another milter (or clamAV), then the greylist delay may be the
only reason spamassassin "hit" the e-mail and bounced due to very high spam
scores. If auto-whitelisted, the same spammer may well get through with
later spams. Purging the entries enforces a new delay.

The objection that the mailer may temp fail under overload is possible, but current 
Sendmail has several throttling parameters to prevent this, thus only a small minority of 
sites are at risk of this; obviously, they should leave it this option disabled. Further, since
milter-greylist keeps everything in memory, high volume SMTP sites already have an issue 
with excessive memory use by the milter.