Now as User zimbra (su zimbra) zimbra zcs @: ~ / amavisd $ pyzor - homedir / opt / zimbra / amavisd

SPF (Sender Policy Framework) is a system that tries to prevent sending forged messages is done through the settings on your DNS when an email is sent, the server will check the TXT / SPF entries in your DNS server, and through it know which server can deliver mail originating from your domain, if someone is sending mail @ yourdomain servers without being cited in the record TXT / SPF MTA server can be configured to reject it. It's a very efficient way to avoid problems with your domain.
Now become zimbra (su zimbra) and create an account on razor razor-admin-home = / opt / zimbra flipboard / amavisd / .razor-create razor-admin-home = / opt / zimbra / amavisd / .razor razor-discover -admin-home = / opt / zimbra flipboard / amavisd / .razor-register
Now as User zimbra (su zimbra) zimbra zcs @: ~ / amavisd $ pyzor - homedir / opt / zimbra / amavisd / .pyzor discover downloading servers from http://pyzor.sourceforge.net/cgi-bin/inform-servers -0-3-x Traceback (most recent call last): File "/ usr / bin / pyzor", line 8, in <module> pyzor.client.run () File "/ var/lib/python-support/python2 .5/pyzor/client.py ", line 1005, in run ExecCall (.) run () File" / var/lib/python-support/python2.5/pyzor/client.py ", line 184, in run self . servers = self.get_servers (servers_fn) File "/ var/lib/python-support/python2.5/pyzor/client.py", line 411, in get_servers servers.read (open (servers_fn)) File "/ var / lib/python-support/python2.5/pyzor/client.py flipboard ", line 117, in read self.append (pyzor.Address.from_str (line)) File" / var/lib/python-support/python2.5 / pyzor / __init__.py ", line 458, in from_str fields [1] = int (fields [1]) IndexError: list index out of range
To resolve this problem, put the line below in servers within the / opt / zimbra / amavisd / .pyzor directory file because flipboard it will work. @ zimbra zcs :/ opt / zimbra $ echo "82.94.255.100:24441"> / opt / zimbra / amavisd / .pyzor / servers
Now let's do a test to see if our pyzor can connect to the server. @ zimbra zcs :/ opt / zimbra / amavisd / .pyzor $ pyzor - homedir / opt / zimbra / amavisd / .pyzor ping 82.94.255.100:24441 (200, 'OK') Adjusting spamassassin flipboard to work with and Razor2 pyzor
Edit the / opt / zimbra / conf / spamassassin / local.cf ok_languages es es ok_locales trusted_networks 127. 10.70. 192.168. use_bayes flipboard skip_rbl_checks 1 0 1 use_razor2 dns_available yes # # Optional Score Increases # # Choose your preferred flipboard values ... score SPF_FAIL 10,000 10,000 SPF_HELO_FAIL score score score PYZOR_CHECK RAZOR2_CHECK 2.500 2.500 score BAYES_99 4.300 score BAYES_90 3.500 score BAYES_80 3.000 bayes_ignore_header Received: from mail3.example . bayes_ignore_header with Received: from localhost bayes_ignore_header Received: from mail1.example.com bayes_ignore_header Received: from mail2.example.com Adjusting settings amavisd-new
Edit the / opt / zimbra / conf / amavisd.conf $ sa_tag_level_deflt = -10.0; # Add spam info headers flipboard if at, or above que sa_tag2_level_deflt $ level = 6.6; # Add 'spam detected' headers at level que sa_kill_level_deflt = $ 15; # Triggers spam evasive actions sa_dsn_cutoff_level = $ 15; # Spam level beyond Which the DSN is not sent $ sa_quarantine_cutoff_level = 15; # Spam level beyond Which quarantine is off $ sa_mail_body_size_limit = 512 * 1024; # Do not waste time on SA if mail is larger $ sa_local_tests_only = 0; # Only tests Which do not require internet access? http://wiki.zimbra.com/index.php?title=Improving_Anti-spam_system # # SPF http://wiki.zimbra.com/index.php?title=Improving_Anti-spam_system http://wiki.zimbra Razor2. com / index.php? title = Improving_Anti-spam_system # # pyzor http://wiki.zimbra.com/index.php?title=Improving_Anti-spam_system Spamassassin_Config http://www.openspf.org/ http://razor. sourceforge.net / postgrey http://pyzor.sourceforge.net/ flipboard integrating the Zimbra
The postgrey is an implementation of "greylisting" concept. Very effective in combating SPAM greylisting is in a special queue for message flipboard delivery, it works as follows when an MTA attempt to deliver a message to your MTA server postgrey refuse to post, giving a reject code with 550 (or is, try later), if a real server configured in accordance with RFC's SMTP, it attempts to deliver the message again after some time, the second attempt the postgrey frees shipping. If a system of SPAM he just goes to the next message from your list and does not try to deliver that message was rejected. The postgrey is a simple system, with a simple concept, but extremely functional and greatly reduces SPAM and VIRUS, your flow, and your queue will greatly decrease.
Let us understand what is what! - Delay specifies the time an MTA remained in greylisting (how long he will refuse the mta msgs). - Max-age mean how long postgrey will keep this information in the cache postgrey whitelist
The postgrey whitelist possesses two types, one for clients and one p