2
edits
Changes
Jump to navigation
Jump to search
Line 116:
Line 116: + + + + + + + + + + + + + + + + + +
→Spamassassin: Added SPF filter functionality
* http://spamassassin.apache.org/tests_3_2_x.html
* http://spamassassin.apache.org/tests_3_2_x.html
* http://www.rulesemporium.com/
* http://www.rulesemporium.com/
====SPF mail rejection/flagging policy====
SME server can protect based of SPF records using spamassassin and the 'sender_permitted_from' plugin. The following lines will enable the plugin.
mkdir -p /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/0/
cd /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/0/
echo sender_permitted_from spf_deny 1 > 30spf
/sbin/e-smith/expand-template /var/service/qpsmtpd/config/peers/0
Then set your custom rule scores using the [[#Custom_Rule_Scores|Custom Rule Scores]] section of this page. You should base these scores on your settings in server-manager > Configuration > Email > Change e-mail filtering settings or via db config commands for those with that skillset
echo "score SPF_SOFTFAIL 6.000" >> 20localscores
echo "score SPF_FAIL 14.000" >> 20localscores
signal-event email-update
In our testing an email that doesn't match SPF records and the sender domain owner has defined a soft fail, if is attributed 6 points and sorted to junkmail folder. If the sender domain owner has defined a hard fail the email attibuted 14 points and is subsequently rejected.
<br>
References (but instructions changed to meet new qmail structure):
* http://forums.contribs.org/index.php?topic=21631.0
====Pyzor Timeout====
====Pyzor Timeout====