On Mon, Mar 22, 2010 at 07:51, micah anderson <mi...@riseup.net> wrote:
> From a user who has unfortunately been saddled with a dynamic IP that > previously was used by a spammer. No amount of explanation to these > users about this is going to assuage their feelings, and there isn't > really anything that can be done by them. They can complain to their ISP > I guess, they could also find another ISP, but these are not > particularly productive steps towards resolving this problem. > > I'm interested in other suggestions that I offer people as alternatives, > but until then I think I may need to remove Botnet from the equation. Or you could just put that relay into your botnet cf file so that it doesn't get scored by botnet. That's what the botnet_pass_ip entries are there for. Using the example you just gave, you could just do: botnet_pass_ip ^213\.6\.61\.151$ Then just do whatever you need to in your spamassassin environment to make that live (reload something, etc.). Then that particular host wont ever trigger botnet again.
