Path: g2news2.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.maxwell.syr.edu!newsfeed.icl.net!news-lond.gip.net!news.gsl.net!gip.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!xs4all!transit4.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
From: Matthias Leisi <matth...@leisi.net>
Newsgroups: list.postfix.users
Subject: Suggestions on how to implement whitelist w/postfix
Date: Tue, 14 Nov 2006 17:27:29 +0100
Organization: XS4ALL
Sender: mailn...@mxdrop30.xs4all.nl
Approved: beh...@xs4all.nl
Message-ID: <list.postfix.users#4559EE71.5080606@leisi.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Lines: 32
NNTP-Posting-Host: 194.109.24.215
X-Trace: 1163521740 news.xs4all.nl 325 [::ffff:194.109.24.215]:4999
X-Complaints-To: abuse@xs4all.nl

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I started a project for a collaborative whitelist (see [1]) and would
like to ask for suggestions on how whitelists can / should / may be
implemented in Postfix.

I'm aware of the problems inherent with DNS-based whitelists (especially
unavailability); therefor one format I currently export is a Postfix
cidr_table (see [2]). Unfortunately, that approach does not profit from
the "fine grained" data, eg different "trust scores" and categories.

How could this be done more flexibly? I could imagine that entries with
a "hi" or "med" score would eg bypass a spamfilter completely - but how
would this most elegantly be implemented?

Any suggestions? (The export format can be changed to whatever seems
helpful.)

Thanks,
- -- Matthias

[1] http://www.dnswl.org/
[2] http://www.dnswl.org/data/postfix-dnswl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFFWe5xxbHw2nyi/okRAgUBAJ9UzH5bfLj8hE7/8eTtXmRl1SVaIQCdHUcZ
sS8AI2ecZG4cQ03p62GY2iA=
=9XT4
-----END PGP SIGNATURE-----