Milter-greylist

Fabien Tassin <fta+miltergreylist@...> wrote:

> > I added the flushaddr feature, which canbe used to remove any entry
> > with the source IP of the message that matched an ACL. See the man
> > page for the details.
> 
> hmm. I don't see how it could match my description of auto-blacklist.
> I mean, it's an instantaneous flush, right?

Yes.

> auto-blacklist has a remanency similar to auto-whitelisting, ie, you kill
> all that happened *before* and continue to kill *after* for a while.
> That's the advantage compared to instantaneous flush.
> Or did I misunderstood something?

auto-blacklisting needs heavy changes. I'd like to make the code settle
a bit so that it gets stable and buildable for everyone. We'll se after
the 3.0 release for auto-blacklisting, except if someone steps in and
contribute a patch right now.

Moreover, you can already have the auto-blacklisting with current
features: have your spamtrap feed a local DNSRBL with a given timeout,
tell milter-greylist to blacklist using this DNSRBL and you are done.

FWIW, I once wrote some code that was supposed to run in the .forward of
a spamtrap. It parse the header and adds the sender IP address to a
DNSRBL, and remove it after some time. Look for DST at the URL below:

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...