Comments on: Configure Postfix for the DSPAM content filter

By: jagowan

jagowan — Sat, 26 Apr 2008 13:29:45 +0000

I’M Sorry, I have miss configuration.
After i’ve read your configuration example carefully, it’s working for dspam to filtering incoming only.

By: jagowan

jagowan — Sat, 26 Apr 2008 12:12:26 +0000

hi,

I’m still have problem with outgoing, always check by dspam. Any idea?

By: Richard5

Richard5 — Thu, 25 Jan 2007 15:11:26 +0000

You don’t need PCRE to use the DSPAM functionality. I’ve choosen for a PCRE based filter but you can also use a REGEX filter, it only needs a different syntax (which I don’t know, sorry).

I think you still can recompile the binaries and use them in a server environment. I haven’t got a server myself or the OS version to try it out. As far as I know OS X server config only manages the configuration files and they will still be the same format.

By: Greg Combs

Greg Combs — Thu, 25 Jan 2007 14:48:30 +0000

So I’m setting this up on Mac OS X Server. In order to maintain the functionality of the server administration tools, I can’t recompile the existing postfix and cyrus binaries.

Unfortunately, your recipe as is will not run such that postfix throws up upon the pcre directive in “check_client_access pcre:”. It doesn’t understand pcre. Though I see pcre related things in the sample folder (sample-filter.cf, sample-pcre-access.cf, etc)

Here’s how they do a content filter in main.cf:
content_filter = smtp-amavis:[127.0.0.1]:10024

and then in master.cf:
smtp-amavis unix – – y – 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes

Any ideas on how to set this up without recompiling the binaries?

By: Tim

Tim — Wed, 20 Dec 2006 16:32:54 +0000

Richard,

Am I wrong in that these instructions do not seem to set up a way to retrain dspam for false positives? In the forum – early on – you were using ham aliases?? I dont see any configuration here in addressing false positive retraining?