On Wed, Jan 08, 2003 at 11:02:35PM +0000, Lee W wrote: | <snip> | > Thanks for the suggestion. I did look into cyrus however I dismissed it | > because it did not appear to support SQL databases, which almost all of | > Postfix lookup tables can be read from.
AFAIK cyrus and postfix use the same auth stuff, which can be routed
through PAM and PAM has modules for postgres, mysql, and probably
others. I guess I'm not sure what exactly you need that isn't
provided.
| I think I just found an answer to my own question. The latest postfix
| (2.0) is the first version to have an in-built filtering mechanism.
| From what I read in the FILTER_README file is requires the use of
| external filtering programs that exit with particular codes to tell
| postfix what to do.
|
| In theory this is exactly what I (and possibly others) have been looking
| for.
Hmm, what do you mean by "filter"? postfix' filter stuff (either by
using header_checks and body_checks or by using an external tool like
spamassassin) only allows the following actions to be taken :
OK (deliver as usual)
REJECT (bounce the message)
DROP (drop the message on the floor, no one will ever know)
If that is all you're looking for, then yes you can do it with just
postfix.
If you are looking for "filter" in the sense of "this is from
debian-users, put it in the debian-users folder; that is from
postfix-users, put it in the postfix-users folder" then you'll need an
MDA (like maildrop, procmail, cyrus' sieve, or even exim) to do that.
(oh, BTW, the sort of filtering described in the FILTER_README can be
done with postfix 1.11 too, AFAIK)
HTH,
-D
--
If any of you lacks wisdom, he should ask God, who gives generously to
all without finding fault, and it will be given to him. But when he
asks he must believe and not doubt, because he who doubts is like a wave
of the sea, blown and tossed by the wind.
James 1:5-6
http://dman.ddts.net/~dman/
msg23118/pgp00000.pgp
Description: PGP signature
