David B Funk a écrit :
> On Wed, 13 Jan 2010, Jason Bertoch wrote:
>
>> Can a list admin disable the spamassas...@hundredacrewood.willspc.net
>> account as we're still getting bounces?
>>
>>
>> -------- Original Message --------
>> Subject: Delivery Status Notification (Failure)
>> Date: Wed, 13 Jan 2010 09:36:54 -0500
>> From: Administrator <administra...@willspc.net>
>> To: Jason Bertoch <ja...@i6ix.com>
>>
>> Subject: Re: SA not picking up rules from /var/lib/spamassassin/
>> Sent: Wed, 13 Jan 2010 09:36:54 -0500
>>
>> did not reach the following recipient(s):
> [snip..]
>
> Just added the following to my SA rules:
>
> # deal with borked administra...@willspc.net 1/14/10
> header L_BORKED_WILLSPC From:raw =~ /"Administrator"
> <administrat...@willspc\.net>/
> describe L_BORKED_WILLSPC Brain-Dead mail site
> score L_BORKED_WILLSPC 100.0
>
> Since I run SA at my incoming MTA and SMTP reject anything with a score
> over 20, I don't see them anymore. ;)
>
As far as I can tell, the major open source MTAs implement access
control. so you don't really need calling SA for this.
for example, with postfix:
smtpd_client_restrictions =
check_client_access cidr:/etc/postfix/kill_client.cidr
check_sender_access cdb:/etc/postfix/killdom
check_helo_access cdb:/etc/postfix/killdom
check_reverse_client_hostname_access cdb:/etc/postfix/killdom
== killdom
willspc.net REJECT backscatter source
.willspc.net REJECT backscatter source
wnahosting.com REJECT backscatter source
.wnahosting.com REJECT backscatter source
== kill_client.cidr
66.194.243.3 REJECT backscatter source
yes, you can add 66.194.243.3 to your firewall kill list....
