Page History

...

Let's try the hard way to secure our mailsystems. Not as convenient as using spamd and spamc is the approach mentioned in the postfix FilterReadme. Some guys at http://www.WorldDesign.com/index.cfm/rd/mta/spampd.htm have published a spamd replacement that works as a SMTP-proxy. The advantage over spamd/spamc is efficiency (no fork/exec()ed processes or temporary files required for failsafe operation) and the ability to use before-queue content filtering.

...

#!/bin/sh
sa-update && /etc/init.d/spampd restart
true

• Wiki Markup

  Scott Lamb writes: "The cron script must \[...\] restart spampd for the changes to take effect. \[...\] on [RedHat]-based distributions, {{sa-update && /sbin/service spampd restart}} will do. (sa-update returns false if no updates were available.) This might cause mails in progress at the time to get a 4xx failure with 'queue file write error' because spampd does not support graceful restarts. That's harmless; the remote system will retry." \\

(6) Edit /etc/postfix/master.cf. The following replaces the initial "smtp" entry:

...

By default, spampd passes through all emails over 65536 bytes. This is set by --maxsize. Increasing this limit can cause memory usage problemsproblems on systems with very little RAM. Larger email can be blocked by postfix with the main.cf option:

...