tumgreyspf

What people are saying about tumgreyspf:

Carl Brewer

I was looking for a greylisting solution for a bunch of UNIX servers here and found your tumgreyspf, and after weighing up all the ones I found, your choice of a filesystem based database rather than SQL was the clincher, and I'm glad to say that I've got it running on a quite busy old RH 7.3 server and it's working a treat.

Introduction

This is tumgreyspf, an external policy checker for the postfix mail server. It can optionally greylist and/or use spfquery to check SPF records to determine if email should be accepted by your server.

SPF is information published by the domain owner about what systems may legitimately send e-mail for the domain. Greylisting takes advantage of spam and viruses that do not follow the RFCs and retry deliveries on temporary failure. We use these checks as part of our mail system and have seen several orders of magnitude reduction in spam, lower system load, and few problems with legitimate mail getting blocked.

It uses the file-system as it's database, no additional database is required to use it.

Download

FTP: ftp.tummy.com:/pub/tummy/tumgreyspf/

Recent changes

WHATSNEW (first 15 lines):

================================
Version 1.32 -- Thu Nov 29, 2007

Rephrasing part of the documentation per suggestion from martin f krafft.
      http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453370

================================
Version 1.31 -- Thu Nov 01, 2007

Patch from Miklos HONTI to fix a bug in the SPF checker that would prevent
      it from continuing on if SPF returns "none".

================================
Version 1.30 -- Tue Oct 16, 2007
[...]

Requirements

Python: You can get source (and binaries for selected systems) from www.python.org.

SPF requires either the C or Perl binary or Python SPF library: tumgreyspf can either call the external SPF checking program from the SPF site, or the Python SPF library. The latter is preferred.

Description and License

tumgreyspf is licensed under the GPL.

Advantages

Does not require a database library, nor does it suffer from database corruption as some other greylist implementations have.
Requires few external dependencies.
Little regular maintenance is required.