<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									[HowTo] Enabling CBPolicyD in Zimbra 7.1.1 - Zimbra HowTo				            </title>
            <link>https://community.zextras.com/forum/zimbra-howto/howto-enabling-cbpolicyd-in-zimbra-7-1-1/</link>
            <description>Zextras Community Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Thu, 08 Oct 2026 10:41:59 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title> Enabling CBPolicyD in Zimbra 7.1.1</title>
                        <link>https://community.zextras.com/forum/zimbra-howto/howto-enabling-cbpolicyd-in-zimbra-7-1-1/#post-19</link>
                        <pubDate>Wed, 15 Jun 2011 10:15:28 +0000</pubDate>
                        <description><![CDATA[WARNING: This guide applies to Zimbra 7.1.1. If you are running Zimbra 7.2.0+ or Zimbra 8.0.2+ please find the official docs at Postfix Policyd - Zimbra :: WikiThis guide explains how to ena...]]></description>
                        <content:encoded><![CDATA[<i><span style="font-size:1.0em"><b>WARNING: This guide applies to Zimbra 7.1.1. If you are running Zimbra 7.2.0+ or Zimbra 8.0.2+ please find the official docs at <a href="http://wiki.zimbra.com/wiki/Postfix_Policyd" class="bbcode_url">Postfix Policyd - Zimbra :: Wiki</a></b></span></i><br><br>This guide explains how to enable and configure Cluebringer Policyd, a new antispam system included in Zimbra 7.0. Unleash the power of your Zimbra!<br><b><br>What is CBPolicyd<br></b>Quote from policyd.org, CBPolicyd official website:
<div class="bbcode_quote">
<div class="bbcode_quote_head">Quote:</div>
<div class="bbcode_quote_body">Policyd v2 (codenamed "cluebringer") is a multi-platform policy server for popular MTAs. This policy daemon is designed mostly for large scale mail hosting environments. The main goal is to implement as many spam combating and email compliance features as possible while at the same time maintaining the portability, stability and performance required for mission critical email hosting of today. Most of the ideas and methods implemented in Policyd v2 stem from Policyd v1 as well as the authors' long time involvement in large scale mail hosting industry.</div>
</div><br>CBPolicyd is included in Zimbra since version 7, but it has become usable in version 7.1. This guide refers to version 7.1.1 as its support for CBPolicyd has been enhanced since 7.1. Different modules can be activated within CBPolicyd to enable different funcions. Those modules are:
<ul class="bbcode_list">
<li>Access Control: Simple access control on all the incoming/outgoing</li>
<li>Accounting: Message count and cumulative size policies</li>
<li>Amavis: Amavisd-new integration</li>
<li>CheckHelo: Helo/Ehlo checks and blacklisting</li>
<li>CheckSPF: Sender Policy Framework support</li>
<li>Graylist: Anti-spam Graylisting support</li>
<li>Quotas: Message count and cumulative size policies</li>
</ul>
The Amavis module will not be in this guide, since Zimbra already has it's own Amavis support.<br><b><br>Enabling and configuring CBPolicyd in Zimbra 7.1.1</b>
<ul class="bbcode_list">
<li>Switch to the zimbra user    su - zimbra</pre>
<li>Enable the cbpolicyd service (server-wide) via zmprov:    <pre>zmprov ms servername +zimbraServiceInstalled cbpolicyd +zimbraServiceEnabled cbpolicyd</pre><span style="font-size:1px">(mind that "+" in front of "zimbraServiceEnabled cbpolicyd". Miss it and you'll end up having cbpolicyd as the ONLY service enabled)</span></li>
<li>In most recent Zimbra versions a CBpolicyD zimbraMtaRestriction exists. If not, add a new one: <pre>zmprov mcf +zimbraMtaRestriction "check_policy_service inet:127.0.0.1:10031"</pre></li>
<li>Configure the CBPolicyd logging and active modules    <pre>zmlocalconfig -e cbpolicyd_log_level=4; zmlocalconfig -e cbpolicyd_log_detail=modules,tracking,policies; zmlocalconfig -e cbpolicyd_module_accesscontrol=1 cbpolicyd_module_checkhelo=1 cbpolicyd_module_checkspf=1 cbpolicyd_module_greylisting=1 cbpolicyd_module_quotas=1</pre><span style="font-size:1px">(sets loglevel to Debug, detailed logging of Modules, Policies and Tracking, enables all the modules excluding Amavis)</span></li>
<li>Restart the MTA service to apply all the configurations    <pre>zmmtactl restart</pre></li>
</ul>


<b>Activating the WEB UI for CBPolicyd 
This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd">THIS guide</a> for the official command line management howto.

</b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet. 
All operations must be executed as 'root' except where specified.

CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/. 
To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server: 
   <pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>su - zimbra</pre></li>
<li>Enable the cbpolicyd service (server-wide) via zmprov:    zmprov ms servername +zimbraServiceInstalled cbpolicyd +zimbraServiceEnabled cbpolicyd</pre><span style="font-size:1px">(mind that "+" in front of "zimbraServiceEnabled cbpolicyd". Miss it and you'll end up having cbpolicyd as the ONLY service enabled)</span>
<li>In most recent Zimbra versions a CBpolicyD zimbraMtaRestriction exists. If not, add a new one: <pre>zmprov mcf +zimbraMtaRestriction "check_policy_service inet:127.0.0.1:10031"</pre></li>
<li>Configure the CBPolicyd logging and active modules    <pre>zmlocalconfig -e cbpolicyd_log_level=4; zmlocalconfig -e cbpolicyd_log_detail=modules,tracking,policies; zmlocalconfig -e cbpolicyd_module_accesscontrol=1 cbpolicyd_module_checkhelo=1 cbpolicyd_module_checkspf=1 cbpolicyd_module_greylisting=1 cbpolicyd_module_quotas=1</pre><span style="font-size:1px">(sets loglevel to Debug, detailed logging of Modules, Policies and Tracking, enables all the modules excluding Amavis)</span></li>
<li>Restart the MTA service to apply all the configurations    <pre>zmmtactl restart</pre></li>
</ul>


<b>Activating the WEB UI for CBPolicyd 
This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd">THIS guide</a> for the official command line management howto.

</b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet. 
All operations must be executed as 'root' except where specified.

CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/. 
To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server: 
   <pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>zmprov ms servername +zimbraServiceInstalled cbpolicyd +zimbraServiceEnabled cbpolicyd</pre><span style="font-size:.67em">(mind that "+" in front of "zimbraServiceEnabled cbpolicyd". Miss it and you'll end up having cbpolicyd as the ONLY service enabled)</span></li>
<li>In most recent Zimbra versions a CBpolicyD zimbraMtaRestriction exists. If not, add a new one: zmprov mcf +zimbraMtaRestriction "check_policy_service inet:127.0.0.1:10031"</pre>
<li>Configure the CBPolicyd logging and active modules    <pre>zmlocalconfig -e cbpolicyd_log_level=4; zmlocalconfig -e cbpolicyd_log_detail=modules,tracking,policies; zmlocalconfig -e cbpolicyd_module_accesscontrol=1 cbpolicyd_module_checkhelo=1 cbpolicyd_module_checkspf=1 cbpolicyd_module_greylisting=1 cbpolicyd_module_quotas=1</pre><span style="font-size:1px">(sets loglevel to Debug, detailed logging of Modules, Policies and Tracking, enables all the modules excluding Amavis)</span></li>
<li>Restart the MTA service to apply all the configurations    <pre>zmmtactl restart</pre></li>
</ul>


<b>Activating the WEB UI for CBPolicyd 
This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd">THIS guide</a> for the official command line management howto.

</b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet. 
All operations must be executed as 'root' except where specified.

CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/. 
To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server: 
   <pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>zmprov mcf +zimbraMtaRestriction "check_policy_service inet:127.0.0.1:10031"</pre></li>
<li>Configure the CBPolicyd logging and active modules    zmlocalconfig -e cbpolicyd_log_level=4; zmlocalconfig -e cbpolicyd_log_detail=modules,tracking,policies; zmlocalconfig -e cbpolicyd_module_accesscontrol=1 cbpolicyd_module_checkhelo=1 cbpolicyd_module_checkspf=1 cbpolicyd_module_greylisting=1 cbpolicyd_module_quotas=1</pre><span style="font-size:1px">(sets loglevel to Debug, detailed logging of Modules, Policies and Tracking, enables all the modules excluding Amavis)</span>
<li>Restart the MTA service to apply all the configurations    <pre>zmmtactl restart</pre></li>
</ul>


<b>Activating the WEB UI for CBPolicyd 
This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd">THIS guide</a> for the official command line management howto.

</b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet. 
All operations must be executed as 'root' except where specified.

CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/. 
To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server: 
   <pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>zmlocalconfig -e cbpolicyd_log_level=4; zmlocalconfig -e cbpolicyd_log_detail=modules,tracking,policies; zmlocalconfig -e cbpolicyd_module_accesscontrol=1 cbpolicyd_module_checkhelo=1 cbpolicyd_module_checkspf=1 cbpolicyd_module_greylisting=1 cbpolicyd_module_quotas=1</pre><span style="font-size:.67em">(sets loglevel to Debug, detailed logging of Modules, Policies and Tracking, enables all the modules excluding Amavis)</span></li>
<li>Restart the MTA service to apply all the configurations    zmmtactl restart</pre>
</ul>


<b>Activating the WEB UI for CBPolicyd 
This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd">THIS guide</a> for the official command line management howto.

</b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet. 
All operations must be executed as 'root' except where specified.

CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/. 
To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server: 
   <pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>zmmtactl restart</pre></li>
</ul><br><br><b>Activating the WEB UI for CBPolicyd<br>This is only valid for servers with the zimbra-spell package installed - in case of a standalone MTA please refer to <a href="http://wiki.zimbra.com/wiki/How-to_for_cbpolicyd" class="bbcode_url">THIS guide</a> for the official command line management howto.<br><br></b>Now that CBPolicyd is fully active you need a GUI to configure it, since its features are not implemented in the Zimbra Administration Console yet.<br>All operations must be executed as 'root' except where specified.<br><br>CBPolicyd Web UI is located in /opt/zimbra/cbpolicyd/share/webui/.<br>To enable it "one shot" for a quick test (this configuration will be erased if you update Zimbra) just create a symlink of the webui in the document root of Zimbra's Apache server:<br>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre>
Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER: 
   <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>cd /opt/zimbra/httpd/htdocs/ &amp;&amp; ln -s ../../cbpolicyd/share/webui</pre><br>Then, edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:<br>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
Reload the httpd services with
    <pre>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre><br>Reload the httpd services with<br>su - zimbra -c "zmapachectl restart"</pre>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a> 
<U>
REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.
</U>
To enable the webui in a more complete way, follow this steps:
<ul>
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    <pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>su - zimbra -c "zmapachectl restart"</pre><br>You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/webui/index.php">http://yourzimbraserver:7780/webui/index.php</a><br><u><br>REMEMBER: This method is suggested only for internal testing, as it has no access control enabled and does not persist after a Zimbra update.<br></u><br>To enable the webui in a more complete way, follow this steps:
<ul class="bbcode_list">
<li>Copy the cluebringer-httpd.conf file from the CBPolicyd folder to the Zimbra's conf/ folder:    cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>cp /opt/zimbra/cbpolicyd/share/contrib/httpd/cluebringer-httpd.conf /opt/zimbra/conf/</pre></li>
<li>Edit the copied file with your favourite editor (i personally like nano, less scary than vi/m and less nerdysh than emacs)The result should look like:Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:1px">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>Alias /cluebringer /opt/zimbra/cbpolicyd/share/webui/    # Comment out the following 3 lines to make web ui accessible from anywhere    Order Deny,Allow    Deny from all    Allow from 192.168.1.0/255.255.255.0</pre><span style="font-size:.67em">(the ip range/netmask after the "Allow from" directive must match the ip range you want to grant access to the web ui.</span></li>
<li>Edit the "/opt/zimbra/conf/httpd.conf" file and add the following line at the end of the file:</li>
</ul>
 Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul>
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    <pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre> Include /opt/zimbra/conf/cluebringer-httpd.conf </pre>
<ul class="bbcode_list">
<li>Edit the /opt/zimbra/cbpolicyd-2.0.10/share/webui/includes/config.php file putting a "#" front of all the lines beginning with $DB_DSN and adding the following line just before the line beginning with $DB_USER:    $DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre>
<li>Reload the httpd services with    <pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>$DB_DSN="sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb";</pre></li>
<li>Reload the httpd services with    su - zimbra -c "zmapachectl restart"</pre>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://policyd.org/content/policyd-support">Policyd.org Support</a>


<span style="font-size:3px"><b>WARNING</b></span> 
Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:<pre>create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>su - zimbra -c "zmapachectl restart"</pre></li>
</ul>
You can now access the webui from <a class="go2wpf-bbcode" rel="nofollow" target="_blank" href="http://yourzimbraserver:7780/cluebringer/index.php">http://yourzimbraserver:7780/cluebringer/index.php</a>To learn how to configure CBPolicyD refer to the official documentation at <a href="http://policyd.org/content/policyd-support" class="bbcode_url">Policyd.org Support</a><br><br><br><span style="font-size:1.0em"><b>WARNING</b></span><br>Zimbra 7.1.1, 7.1.2 and 7.1.3 had a misconfiguration in the default logrotate config...Check the /etc/logrotate.d/zimbra file, find the "/opt/zimbra/log/cbpolicyd.log" section and change this line:create 0644 syslog adm</pre>to this:<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>create 0644 syslog adm</pre>to this:create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with <pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>create 0644 zimbra zimbra</pre>then change the ownership of the existing log file with chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service with<pre>su - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>chown zimbra:zimbra /opt/zimbra/log/cbpolicyd.log</pre>and then restart the cbpolicyd service withsu - zimbra -c "zmcbpolicydctl restart"</pre>
<b>
Cleaning up the CBPolicyD Database
</b>Old and outdated entries are not automatically purged from CBPolicyd's database.
A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!

<pre>
<span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre>su - zimbra -c "zmcbpolicydctl restart"</pre><br><b><br>Cleaning up the CBPolicyD Database<br></b>Old and outdated entries are not automatically purged from CBPolicyd's database.<br>A tool called "cbpadmin" is provided to take care of this operation, so you just need to schedule the execution of this tool through cron to keep your db slim and healthy!<br><br><span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span>
</pre>



Special thanks to Mishikal for contributing some nice suggestions!<pre><br><span style="color:#000000"><span style="font-family:monospace">35 3 * * * /opt/zimbra/cbpolicyd/bin/cbpadmin --config=/opt/zimbra/conf/cbpolicyd.conf  --cleanup &gt;/dev/null</span></span><br></pre><br><br><br><br>Special thanks to Mishikal for contributing some nice suggestions!]]></content:encoded>
						                            <category domain="https://community.zextras.com/forum/zimbra-howto/">Zimbra HowTo</category>                        <dc:creator>Cine</dc:creator>
                        <guid isPermaLink="true">https://community.zextras.com/forum/zimbra-howto/howto-enabling-cbpolicyd-in-zimbra-7-1-1/#post-19</guid>
                    </item>
							        </channel>
        </rss>
		