Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] White list at spamhaus.org

2010-10-29 by Christian Pélissier

Forget previous mail. ACL are working (whitelisting  depends on ACL
order if you use both list.dnswl.org and swl.spamhaus.org ).

Here is a feedback from spamhaus :

"SWL (and DWL) are new services and we are ramping them up slowly,
starting from zero. It is not surprising that you don't yet encounter a
listed IP. We would expect the service to be having noticeable effects
in many weeks or maybe some months more."



Le ven. 29/10/2010 à 14:29, Christian Pélissier a écrit :
>   
> 
> 
> Since september 2010 spamhaus has also a whitelisting DNS service. See
> :
> 
> http://www.spamhauswhitelist.com/en/
> 
> I have changed greylist.conf and add the following lines.
> 
> dnsrbl "MTAWL16" swl.spamhaus.org 127.0.2.2
> dnsrbl "MTAWL17" swl.spamhaus.org 127.0.2.3
> dnsrbl "MTAWL18" swl.spamhaus.org 127.0.2.102
> dnsrbl "MTAWL19" swl.spamhaus.org 127.0.2.103
> racl whitelist dnsrbl "MTAWL16"
> racl whitelist dnsrbl "MTAWL17"
> racl whitelist dnsrbl "MTAWL18"
> racl whitelist dnsrbl "MTAWL19"
> 
> After 3 hours I did'nt found any line matching spamhaus ACLs in my
> syslog file : line like looking like 
> 
> Oct 29 12:25:44 emix milter-greylist: [ID 902575 mail.info]
> o9TAPTo8029733: skipping greylist because address @IP is in DNSRBL,
> ....
> ACL 90
> 
> What is wrong in my config ?
> 
> PS.
> 
> DNS query looks to be the same :
> 
> here with the test address 127.0.0.2 :
> 
> $ host 2.0.0.127.swl.spamhaus.org
> 2.0.0.127.swl.spamhaus.org has address 127.0.2.2
> 
> $ host 2.0.0.127.list.dnswl.org
> 2.0.0.127.list.dnswl.org has address 127.0.10.0
> 
> -- 
> Christian Pélissier
> 
> 
> 
> 
> 
-- 
Christian Pélissier
Office National d'Études et de Recherches Aérospatiales
BP 72 92322 Chatillon
Tel: 33 1 46 73 44 19, Fax: 33 1 46 73 41 50

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.