King0770-Notes-Whitelist-Spamassassin-MTA

Revision as of 20:04, 29 December 2016 by King0770 (talk | contribs) (Created page with "<strong>Summary</strong><br> Describing the difference between Whitelisting with Spamassassin and MTA.<br> ==Section I - Whitelist by Spamassassin== <strong>Method 1</strong...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Summary
Describing the difference between Whitelisting with Spamassassin and MTA.

Section I - Whitelist by Spamassassin

Method 1 

touch /opt/zimbra/data/spamassassin/localrules/sauser.cf

Edit sauser.cf file, and add the following. 

whitelist_from jsmith@exampledomain.com

zmamavisdctl restart

Method 2 

su - zimbra
zmprov md perforce.com +amavisWhitelistSender jsmith@exampledomain.com

Method 2a 

zmprov ma rstokes@perforce.com +amavisWhitelistSender jsmith@exampledomain.com

Section II - Whitelist by MTA

RBL Overide

You need to setup an MTA RBL over ride file. As the zimbra user do the following.

1) 
touch /opt/zimbra/conf/postfix_rbl_override

2) Add IP address(es) SPACE OK to the file, one IP address per line, example...

1.2.3.4  OK

3) 
postmap /opt/zimbra/conf/postfix_rbl_override

4)
zmprov mcf +zimbraMtaRestriction "check_client_access lmdb:/opt/zimbra/conf/postfix_rbl_override"

5)
zmmtactl restart

**Note**
After setting up the MTA RBL file, anytime afterwards you need to update the postfix_rbl_override file, you just need to run the postmap command against it; no need to restart the MTA each time the file is updated. 

postmap /opt/zimbra/conf/postfix_rbl_override
Retrieved from "http://wiki.zimbra.com/index.php?title=King0770-Notes-Whitelist-Spamassassin-MTA&oldid=63238"
Jump to: navigation, search