This is what I have in my milter-greylist's greylist.conf.

The google entries are accurate as of a week or so ago, taken from their
SPF record. 

list "broken mta" addr {   \
        12.5.136.141/32    \ # Southwest Airlines (unique sender)
        12.5.136.142/32    \ # Southwest Airlines
        12.5.136.143/32    \ # Southwest Airlines
        12.5.136.144/32    \ # Southwest Airlines
        12.107.209.244/32  \ # kernel.org (unique sender)
        12.107.209.250/32  \ # sourceware.org (unique sender)
        63.82.37.110/32    \ # SLmail
        63.169.44.143/32   \ # Southwest Airlines
        63.169.44.144/32   \ # Southwest Airlines
        64.7.153.18/32     \ # sentex.ca (common pool)
        64.12.136.0/24     \ # AOL (common pool)
        64.12.137.0/24     \ # AOL
        64.12.138.0/24     \ # AOL
        64.18.0.0/20       \ # google
        64.124.204.39      \ # moveon.org (unique sender)
        64.125.132.254/32  \ # collab.net (unique sender)
        64.233.160.0/19    \ # google
        66.94.237.16/28    \ # Yahoo Groups servers (common pool)
        66.94.237.32/28    \ # Yahoo Groups servers (common pool)
        66.94.237.48/30    \ # Yahoo Groups servers (common pool)
        66.100.210.82/32   \ # Groupwise?
        66.102.0.0/20      \ # google
        66.135.192.0/19    \ # Ebay
        66.162.216.166/32  \ # Groupwise?
        66.206.22.82/32    \ # Plexor
        66.206.22.83/32    \ # Plexor
        66.206.22.84/32    \ # Plexor
        66.206.22.85/32    \ # Plexor
        66.218.66.0/23     \ # Yahoo Groups servers (common pool)
        66.218.67.0/23     \ # Yahoo Groups servers (common pool)
        66.218.68.0/23     \ # Yahoo Groups servers (common pool)
        66.218.69.0/23     \ # Yahoo Groups servers (common pool)
        66.249.80.0/20     \ # google
        66.27.51.218/32    \ # ljbtc.com (Groupwise)
        72.14.192.0/18     \ # google
        74.125.0.0/16      \ # google
        152.163.225.0/24   \ # AOL
        194.245.101.88/32  \ # Joker.com
        195.235.39.19/32   \ # Tid InfoMail Exchanger v2.20
        195.238.2.0/24     \ # skynet.be (wierd retry pattern, common
pool)
        195.238.3.0/24     \ # skynet.be
        195.46.220.208/32  \ # mgn.net
        195.46.220.209/32  \ # mgn.net
        195.46.220.210/32  \ # mgn.net
        195.46.220.211/32  \ # mgn.net
        195.46.220.221/32  \ # mgn.net
        195.46.220.222/32  \ # mgn.net
        195.238.2.0/24     \ # skynet.be (wierd retry pattern)
        195.238.3.0/24     \ # skynet.be
        204.107.120.10/32  \ # Ameritrade (no retry)
        205.188.0.0/16     \ # AOL
        205.206.231.0/24   \ # SecurityFocus.com (unique sender)
        207.115.63.0/24    \ # Prodigy - retries continually
        207.126.144.0      \ # google
        207.171.168.0/24   \ # Amazon.com
        207.171.180.0/24   \ # Amazon.com
        207.171.187.0/24   \ # Amazon.com
        207.171.188.0/24   \ # Amazon.com
        207.171.190.0/24   \ # Amazon.com
        209.85.128.0/17    \ # google
        209.132.176.174/32 \ # sourceware.org mailing lists (unique
sender)
        211.29.132.0/24    \ # optusnet.com.au (wierd retry pattern)
        213.136.52.31/32   \ # Mysql.com (unique sender)
        216.33.244.0/24    \ # Ebay
        216.239.32.0/19    \ # google
        217.158.50.178/32  \ # AXKit mailing list (unique sender)
}

Cheers,

Phil

--
Phil Randal
Networks Engineer
Herefordshire Council
Hereford, UK

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Charles
Gregory
Sent: 12 August 2008 12:58
To: ClamAV users ML
Subject: Re: [Clamav-users] [0.0] Re: simplest replacement for ancient
amavis-perl

On Mon, 11 Aug 2008, Dennis Peterson wrote:
> ..... A problem I've seen with greylisting is the round-robin MTA
pool.
> Each is told in turn to come back later and if the pool is large it 
> can take a long time to cycle through all of them.

I don't suppose anyone has a list of these available for a "whitelist"
or "avoid greylisting"? Preferably a list of IP's not domains?

- Charles

_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to