Milter-greylist

Benoit Panizzon <panizzon@...> wrote:

> Not realy. As example, our favourite swiss spamer is ordering a new bullet
> proof server in china for allmost every spamrun. He does not just run a
> 'spambot' on them, but a real mailserver. So just greylisting has become
> useless.
> Better would be what I suggested: blacklist tuples (or their IP) which had a
> positive hit in spamassassin. But I understand this is not trivial :-)

Well, we can add such a communication capability (well, in fact you
could write the code, and I could add it to milter-greylist :-). Here
are some ideas of how it could be done:

1) Finish the blacklisting support. That means trying the patch I
released, testing it in various situation, sit down for a while thinking
of how things should really be handled, fix the patch and contribute it
back.

2a) Then there is the communication between other tools and
milter-greylist. A complex approach is to enhance the simple protocol
used for MX sync. We could add dynamic blacklist tuples to that. And it
would be trivial to write a command line tool for using that protocol to
remote-control milter-greylist. 

Then you just have to fork that command line tool from your spamassassin
machinery when you find someone that needs to be blacklisted.

2b) An alternative: you just rebuild a milter-greylist config file from
your spamassassin machinery and you let milter-greylist automatically
reload the config with the new blacklist. 

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