Less Configuration = More Time For Beer

I've been looking at all the configuration parameters that are recommended for configuring Postfix for anti-spam prevention, and there's quite a lot to learn.

This Postfix webpage gives a pretty thorough explanation and it's all good stuff.
http://www.postfix.org/uce.html

But with this many configuration parameters there's a lot of tweaking to do to get good spam protection.

body_checks check_client_access check_etrn_access check_helo_access check_recipient_access check_recipient_maps check_sender_access content_filter default_rbl_reply defer_if_permit header_checks invalid_hostname_reject_code maps_rbl_reject_code non_fqdn_reject_code permit_auth_destination permit_mx_backup permit_mx_backup_networks permit_mynetworks rbl_reply_maps reject_code reject_invalid_hostname reject_non_fqdn_hostname reject_non_fqdn_recipient reject_non_fqdn_sender reject_rbl reject_rbl_client reject_rhsbl_client reject_rhsbl_recipient reject_rhsbl_sender reject_sender_login_mismatch reject_unauth_destination reject_unauth_pipelining reject_unknown_client reject_unknown_hostname reject_unknown_recipient_domain reject_unknown_sender_domain relay_domains relay_domains_reject_code smtpd_client_restrictions smtpd_etrn_restrictions smtpd_expansion_filter smtpd_helo_required smtpd_helo_restrictions smtpd_recipient_restrictions smtpd_sender_login_maps smtpd_sender_restrictions unknown_client_reject_code unknown_hostname_reject_code warn_if_reject

Traffic Control, on the other-hand, is inherently designed to fight spam. The process of throttling unknown senders is so effective at removing spam, even before the email content is sent to your servers, that we can all have more time for the finer things in life.