Milter-greylist

According to Emmanuel Dreyfus:
> > > 
> > > It now reports blacklist as greylist, hidding the spamtraps but still flushing the bad ips from the db.
> > > Let see if that helps.
> > 
> > hm, doesn't work.
> > 
> > sm-mta reports "reject=550 5.7.1 Command rejected" while it was "reject=551 5.7.1 Go away!" before.
> > I assume it's because m-g returned SMFIS_REJECT and not SMFIS_TEMPFAIL. I patched it.
> > Let see now.
> 
> Why don't you just use flushaddr with an acl greylist statement? It should
> work too...

Yes but with grey, the entry that triggered the flush will end-up in the db, right?
I mean, it seems the flush occurs *before* grey or auto-white are commited to the db.

For now, I'm only experiencing various things to see what could work.

In fact, i'm more interested by killing the whole flow so neither are good.
It's really auto-black that could do that.
I could still do a local dnsrbl fed by something monitoring the logs
for "black" events but I don't like spam interacting (write) with a DNS server
in production. I've done that in the past using nsupdate but I'd prefer
milter to do that internaly (less dependancies, no monitoring, etc).

/Fabien