Re: ISP Level Postgrey

[Craig Sanders <cas@taz.net.au>]

On Wed, Jul 12, 2006 at 09:16:30PM +0200, Marek Podmaka wrote:
> Another option for large scale sites may be rewriting postgrey (or making
> your own grelisting daemon) using some real database such as mysql.

or use postfix-policyd (which can do lots of other stuff as well
as greylisting):

Package: postfix-policyd
Priority: optional
Section: mail
Installed-Size: 324
Maintainer: OndÅej Surý <ondrej@debian.org>
Architecture: i386
Version: 1.78-1
Depends: dbconfig-common, libc6 (>= 2.3.6-6), libmysqlclient15off (>= 5.0.19-1), zlib1g (>= 1:1.2.1), debconf (>= 0.5) | debconf-2.0
Recommends: mysql-server
Filename: pool/main/p/postfix-policyd/postfix-policyd_1.78-1_i386.deb
Size: 67168
MD5sum: 5afb69d4a526cd58f46c3a256654901c
SHA1: f45b220a2c7beaff2dde4e62f43e48cf6827f7ae
SHA256: be900dbab59679732cd820070c30c5314df9e592c213d8a08e591c78c81ace8b
Description: anti-spam plugin for Postfix
 Policyd is an anti-spam plugin for Postfix (MySQL based) that
 does  Greylisting, Sender-(envelope  or SASL)-based throttling
 (on messages and / or volume  per defined time unit), Spamtrap
 monitoring / blacklisting and HELO auto blacklisting.


there is, or was, a postgres version of this around too. i was trialling
it a year or two ago but decided i didn't want my mail system dependant
on an SQL database.

craig

ps: i've found that even a few seconds is enough greylisting delay to
block a lot of spam and viruses. spamware almost never tries again,
but it's not at all uncommon for legit MTAs to retry within 10 or 15
seconds....and then not again for an hour or more.

-- 
craig sanders <cas@taz.net.au>           (part time cyborg)