<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Spam Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://www.vavai.net/tag/spam/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/spam/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Sat, 20 Oct 2018 23:55:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Fail2Ban, Zimbra’s DoSFilter and Failed Login Lockout Policy</title>
		<link>https://www.vavai.net/fail2ban-zimbras-dosfilter-and-failed-login-lockout-policy/</link>
					<comments>https://www.vavai.net/fail2ban-zimbras-dosfilter-and-failed-login-lockout-policy/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sat, 20 Oct 2018 23:55:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[DoSFilter]]></category>
		<category><![CDATA[Fail2Ban]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=2053</guid>

					<description><![CDATA[<p>On each Zimbra deployment strategy, I&#8217;ve never activate Failed Login Lockout Policy as it tend to block legitimate user from being logged in due to brute force attack from others. The legitimate users often become a victim for spammer or robot attempt to login. I would also prefer Fail2ban to block login attempt from spammer...</p>
<p>The post <a href="https://www.vavai.net/fail2ban-zimbras-dosfilter-and-failed-login-lockout-policy/">Fail2Ban, Zimbra’s DoSFilter and Failed Login Lockout Policy</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>On each Zimbra deployment strategy, I&#8217;ve never activate Failed Login Lockout Policy as it tend to block legitimate user from being logged in due to brute force attack from others. The legitimate users often become a victim for spammer or robot attempt to login.<br />
I would also prefer Fail2ban to block login attempt from spammer rather than Zimbra&#8217;s built in filter, DoSFilter. But it seems to be changed after looking at (just a short reply <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> ) on a discussion on <a href="https://forums.zimbra.org/viewtopic.php?f=15&amp;t=65051&amp;p=286557#p286557">Zimbra Forums</a>.<br />
<img fetchpriority="high" decoding="async" class="alignnone size-large wp-image-2055" src="http://v2.vavai.net/wp-content/uploads/2018/10/Zimbra-logo-color-1024x225.png" alt="" width="602" height="132" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-1024x225.png 1024w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-300x66.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-768x168.png 768w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color.png 1500w" sizes="(max-width: 602px) 100vw, 602px" /><br />
L Mark Stone of Mission Critical Email write up : <a href="https://www.missioncriticalemail.com/2018/10/19/using-zimbras-dosfilter-and-failed-login-lockout-policy-together/">&#8220;Using Zimbra’s DoSFilter and Failed Login Lockout Policy Together&#8221;</a></p>
<blockquote><p>Zimbra’s DoSFilter (<a href="https://wiki.zimbra.com/wiki/DoSFilter" target="_blank" rel="noopener noreferrer">Denial of Service Filter</a>) is a mechanism to throttle or block IP addresses that have a repeated number of failed logins to your Zimbra system.  Zimbra’s Classes of Service include a Failed Login Lockout policy that will put a mailbox in Locked Out mode, hopefully before a brute force attack is successful.  The two together can improve system security and protect legitimate users, but only if configured appropriately.<br />
DoSFilter is generally easier to configure than fail2ban in multiserver systems, because in a multi-server system the logger host is usually one of the mailbox servers, but you want to do the fail2ban blocking on the MTA and Proxy servers.  Making all that work is complex, and if you are running Network Edition, Zimbra Support can help you troubleshoot DoSFilter; with fail2ban you are on your own.  On single server Zimbra systems, fail2ban works fine, but you’ll need to source up to date Zimbra “jail” configuration files, so yet another reason to favor DoSFilter over fail2ban.</p></blockquote>
<p>As one of top Zimbra Expert involved on Zimbra Forums since the beginning and managing his business focus on email, Mark has his own&#8217;s experience to deal with Zimbra security improvement and his blog post interesting enough to be implemented.</p>
<p>The post <a href="https://www.vavai.net/fail2ban-zimbras-dosfilter-and-failed-login-lockout-policy/">Fail2Ban, Zimbra’s DoSFilter and Failed Login Lockout Policy</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/fail2ban-zimbras-dosfilter-and-failed-login-lockout-policy/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Script to Delete the Spam Queue on Zimbra with Confirmation</title>
		<link>https://www.vavai.net/script-to-delete-the-spam-queue-on-zimbra-with-confirmation/</link>
					<comments>https://www.vavai.net/script-to-delete-the-spam-queue-on-zimbra-with-confirmation/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sat, 20 Oct 2018 02:43:16 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=2047</guid>

					<description><![CDATA[<p>On previous script, we can delete spam from queue by passing sender or recipient address on the script : [code lang=&#8221;bash&#8221;] pfdel email-spammer [/code] But what about situation where spammer filling up queue with random sender and recipient, and it tooks time to delete each message. Yes, we can use Postfix powerful binary, with postsuper...</p>
<p>The post <a href="https://www.vavai.net/script-to-delete-the-spam-queue-on-zimbra-with-confirmation/">Script to Delete the Spam Queue on Zimbra with Confirmation</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>On <a href="http://v2.vavai.net/2018/10/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/">previous script</a>, we can delete spam from queue by passing sender or recipient address on the script :<br />
[code lang=&#8221;bash&#8221;]<br />
pfdel email-spammer<br />
[/code]<br />
<img decoding="async" class="alignnone size-medium wp-image-2049" src="http://v2.vavai.net/wp-content/uploads/2018/10/email-300x108.png" alt="" width="300" height="108" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/email-300x108.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/email.png 640w" sizes="(max-width: 300px) 100vw, 300px" /><br />
But what about situation where spammer filling up queue with random sender and recipient, and it tooks time to delete each message. Yes, we can use Postfix powerful binary, with <strong>postsuper -d ALL</strong> but it will remove entire message, including normal message.<br />
Below is a modified script, to delete spam queue by confirming whether the message are legitimate or not. It will display sender and recipient so we can check each message accordingly.<br />
[code lang=&#8221;bash&#8221;]<br />
#!/bin/sh<br />
#Hapus Layar<br />
clear<br />
/opt/zimbra/postfix/sbin/postqueue -p | grep -A 1 &#8220;$1&#8221; | grep @ | sort | uniq | cut -d &#8220;:&#8221; -f3 | cut -d &#8221; &#8221; -f3 > /tmp/over-quota.txt<br />
USERS=`cat /tmp/over-quota.txt`<br />
echo &#8220;Looping for all users&#8221;<br />
for ACCOUNT in $USERS; do<br />
ACC1=`echo $ACCOUNT | awk -F@ &#8216;{print $1}&#8217;`;<br />
ACC2=`echo $ACCOUNT | cut -d &#8216;.&#8217; -f1`<br />
#echo $ACC1<br />
#echo $ACC2<br />
/opt/zimbra/postfix/sbin/postqueue -p | grep $ACCOUNT -A 3<br />
echo -n &#8220;Remove queue for account : $ACCOUNT [Y/N]? &#8221;<br />
read TANYA<br />
if [ $TANYA == Y ] || [ $TANYA == y ]; then<br />
pfdel $ACCOUNT<br />
fi<br />
echo &#8220;&#8221;<br />
done<br />
echo &#8220;Removal queue messages for $1 has been completed successfully&#8221;<br />
[/code]<br />
The script will also takes time if queue contains too many spam messages, so a better choice is to prevent spam by strengthening server anti spam and enforcing a tight security policy.</p>
<p>The post <a href="https://www.vavai.net/script-to-delete-the-spam-queue-on-zimbra-with-confirmation/">Script to Delete the Spam Queue on Zimbra with Confirmation</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/script-to-delete-the-spam-queue-on-zimbra-with-confirmation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Bash Script for Spam Queue Removal on Zimbra Mail Server (Updated)</title>
		<link>https://www.vavai.net/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/</link>
					<comments>https://www.vavai.net/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Thu, 18 Oct 2018 13:00:03 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mail Server]]></category>
		<category><![CDATA[Perl]]></category>
		<category><![CDATA[Script]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=2036</guid>

					<description><![CDATA[<p>I have a small script-got it from Internet-for Zimbra spam queue removal based on Postfix queue message removal. The script written on Perl language and become a mandatory script on each Zimbra server deployment, as a quick tools to remove spam message from queue caused by compromised account. As of Zimbra 8.7, there is a little...</p>
<p>The post <a href="https://www.vavai.net/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/">Bash Script for Spam Queue Removal on Zimbra Mail Server (Updated)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>I have a small script-got it from Internet-for Zimbra spam queue removal based on Postfix queue message removal. The script written on Perl language and become a mandatory script on each Zimbra server deployment, as a quick tools to remove spam message from queue caused by compromised account.<br />
<figure id="attachment_2038" aria-describedby="caption-attachment-2038" style="width: 1280px" class="wp-caption alignnone"><img decoding="async" class="wp-image-2038 size-full" src="http://54.254.121.108/wp-content/uploads/2018/10/phising.png" alt="" width="1280" height="977" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/phising.png 1280w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/phising-300x229.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/phising-1024x782.png 1024w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/phising-768x586.png 768w" sizes="(max-width: 1280px) 100vw, 1280px" /><figcaption id="caption-attachment-2038" class="wp-caption-text">image from pixabay</figcaption></figure><br />
As of Zimbra 8.7, there is a little change on path for some Postfix binary. On previous version, Postfix binary located on <strong>/opt/zimbra/postfix/ </strong>but since version 8.7, the binary folder moved into <strong>/opt/zimbra/common/ </strong>so I take a little time to change the script.<br />
Below is an updated script, check for Zimbra version and change binary folder accordingly :<br />
[code lang=&#8221;bash&#8221;]<br />
#!/usr/bin/perl -w<br />
#<br />
# pfdel &#8211; deletes message containing specified address from<br />
# Postfix queue. Matches either sender or recipient address.<br />
#<br />
# Usage: pfdel sender-or-recipient-address<br />
#<br />
use strict;<br />
my $LISTQ;<br />
my $POSTSUPER;<br />
# Change these paths if necessary.<br />
system(&#8220;su &#8211; zimbra -c &#8216;zmcontrol -v&#8217; &gt; /tmp/zcs-ver.txt&#8221;);<br />
my $VER=`awk &#8216;/Release 6|Release 7|Release 8.0|Release 8.5|Release 8.6/&#8217; /tmp/zcs-ver.txt`;<br />
#print $VER<br />
if (length($VER) &gt; 0)<br />
{<br />
$LISTQ = &#8220;/opt/zimbra/postfix/sbin/postqueue -p&#8221;;<br />
$POSTSUPER = &#8220;/opt/zimbra/postfix/sbin/postsuper&#8221;;<br />
}<br />
else<br />
{<br />
$LISTQ = &#8220;/opt/zimbra/common/sbin/postqueue -p&#8221;;<br />
$POSTSUPER = &#8220;/opt/zimbra/common/sbin/postsuper&#8221;;<br />
}<br />
my $email_addr = &#8220;&#8221;;<br />
my $qid = &#8220;&#8221;;<br />
my $euid = $&gt;;<br />
if ( @ARGV != 1 ) {<br />
die &#8220;Usage: pfdel \n&#8221;;<br />
} else {<br />
$email_addr = $ARGV[0];<br />
}<br />
if ( $euid != 0 ) {<br />
die &#8220;You must be root to delete queue files.\n&#8221;;<br />
}<br />
open(QUEUE, &#8220;$LISTQ |&#8221;) ||<br />
die &#8220;Can&#8217;t get pipe to $LISTQ: $!\n&#8221;;<br />
my $entry = ; # skip single header line<br />
$/ = &#8220;&#8221;; # Rest of queue entries print on<br />
# multiple lines.<br />
while ( $entry = ) {<br />
if ( $entry =~ / $email_addr$/m ) {<br />
($qid) = split(/\s+/, $entry, 2);<br />
$qid =~ s/[\*\!]//;<br />
next unless ($qid);<br />
#<br />
# Execute postsuper -d with the queue id.<br />
# postsuper provides feedback when it deletes<br />
# messages. Let its output go through.<br />
#<br />
if ( system($POSTSUPER, &#8220;-d&#8221;, $qid) != 0 ) {<br />
# If postsuper has a problem, bail.<br />
die &#8220;Error executing $POSTSUPER: error &#8221; .<br />
&#8220;code &#8221; . ($?/256) . &#8220;\n&#8221;;<br />
}<br />
}<br />
}<br />
close(QUEUE);<br />
if (! $qid ) {<br />
die &#8220;No messages with the address &lt;$email_addr&gt; &#8221; .<br />
&#8220;found in queue.\n&#8221;;<br />
}<br />
exit 0;<br />
[/code]<br />
If you tend to lazy to copy-paste the script, get it from mine :<br />
[code lang=&#8221;bash&#8221;]<br />
wget https://www.vavai.com/pfdel<br />
chmod +x pfdel<br />
[/code]<br />
And to run it, just run this script with root permissions :<br />
[code lang=&#8221;bash&#8221;]<br />
./pfdel email-spammer<br />
[/code]<br />
ex :<br />
[code lang=&#8221;bash&#8221;]<br />
./pfdel spammersampah@vavai.com<br />
[/code]<br />
However, this is only a quick tools to remove spam, but more importantly is prevent spam from being filling into queue.</p>
<p>The post <a href="https://www.vavai.net/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/">Bash Script for Spam Queue Removal on Zimbra Mail Server (Updated)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/bash-script-for-spam-queue-removal-on-zimbra-mail-server-updated/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</title>
		<link>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8-2/</link>
					<comments>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8-2/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Mon, 17 Feb 2014 23:04:49 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mail Server]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Telnet]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1725</guid>

					<description><![CDATA[<p>As a powerful mail server, Zimbra has some system security features applied by default. We can also applying some additional security policy to increase mail server protection, such as applying PolicyD and Fail2Ban All the above security rule may be sufficient, but there are some additional security tips should be considered, especially in the case...</p>
<p>The post <a href="https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8-2/">Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/email.png"><img loading="lazy" decoding="async" class="alignleft wp-image-1829" style="margin: 5px;" src="http://54.254.121.108/wp-content/uploads/2014/02/email.png" alt="email" width="180" height="193" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/email.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/email-280x300.png 280w" sizes="auto, (max-width: 180px) 100vw, 180px" /></a>As a powerful mail server, Zimbra has some system security features applied by default. We can also applying some additional security policy to increase mail server protection, such as applying <a href="http://v2.vavai.net/tag/policyd/">PolicyD</a> and <a href="http://v2.vavai.net/2011/10/tips-improving-zimbra-mail-server-security-with-fail2ban/">Fail2Ban</a><br />
All the above security rule may be sufficient, but there are some additional security tips should be considered, especially in the case of SMTP authorization.<br />
Look at the following mail flow delivery, sent from or into Zimbra :<br />
<strong>From : External User   To : External User, Result : Relay Access Denied</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@yahoo.com</strong>
250 2.1.0 Ok
<strong>rcpt to:zezevavai@gmail.com</strong>
554 5.7.1 &lt;zezevavai@gmail.com&gt;: Relay access denied</pre>
<p><strong><span id="more-2758"></span>From : External User   To : Zimbra User, Result : Accepted with prior Scanning for Spam and Viruses</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@yahoo.com</strong>
250 2.1.0 Ok
<strong>rcpt to:myemail@mycompanydomain.co.id</strong>
250 2.1.5 Ok
<strong>data</strong>
354 End data with &lt;CR&gt;&lt;LF&gt;.&lt;CR&gt;&lt;LF&gt;
<strong>Hello Vavai</strong>
<strong>.</strong>
250 2.0.0 Ok: queued as C78EDB6E001
<strong>quit</strong>
221 2.0.0 Bye</pre>
<p><strong>From : Zimbra User  To : External User, Result : Accepted with prior SMTP Authorization check</strong><br />
Zimbra should be respond our request  with &#8220;Relay Access Denied when trying to send emails without prior authorization</p>
<pre>telnet mail.mycompanydomain.co.id 25
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
ehlo mail
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 6144000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from:vivianchow@mycompanydomain.co.id
250 2.1.0 Ok
rcpt to:myemail@gmail.com
554 5.7.1 &lt;myemail@vavai.com&gt;: Relay access denied</pre>
<p><strong>From : Zimbra User  To : Zimbra User, Result : Accepted WITHOUT prior SMTP Authorization check</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 6144000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@mycompanydomain.co.id</strong>
250 2.1.0 Ok
<strong>rcpt to:vivianchow@mycompanydomain.co.id</strong>
250 2.1.5 Ok</pre>
<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg"><img loading="lazy" decoding="async" class="alignright size-full wp-image-1710" src="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg" alt="zimbra-logo" width="200" height="53" /></a>Look at the last example. I&#8217;m trying to send email from <strong>vivianchow@mycompanydomain.co.id </strong>to <strong>vivianchow@mycompanydomain.co.id </strong>without prior authorization and Zimbra accepted this email whereas should not. How if I&#8217;m trying to send fake email, let&#8217;s say from my boss email into my colleagues?<br />
To prevent the above security hole, below are some modification which are able to be applied on Zimbra 8. This modification will force the user to authenticate and login before sending an email to an internal users.</p>
<ol>
<li>Backup all configuration. Incorrect settings while applying &#8220;sender must login&#8221; policy would interfere Zimbra services and would stop your email communication</li>
<li>Log in as Zimbra user and edit <strong>/opt/zimbra/conf/zmconfigd.cf</strong><br />
Add the following lines right under <strong>POSTCONF smtpd_recipient_restrictions FILE zmconfigd/postfix_recipient_restrictions.cf</strong></p>
<pre>POSTCONF proxy_read_maps FILE zmconfigd/proxy_read_maps.cf</pre>
<p>and add the following lines right under <strong>POSTCONF smtpd_sender_restrictions FILE zmconfigd/smtpd_sender_restrictions.cf</strong></p>
<pre>POSTCONF smtpd_sender_login_maps proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</pre>
</li>
<li>Save your changes and then navigate to /opt/zimbra/conf/zmconfigd/ folder and edit smtpd_sender_restriction.cf
<pre>cd /opt/zimbra/conf/zmconfigd/
vi smtpd_sender_restrictions.cf</pre>
</li>
<li>Put the following code on the top of the lines
<pre>permit_mynetworks, reject_sender_login_mismatch</pre>
</li>
<li>Save your change</li>
<li>Check your read maps settings with the following command :
<pre>postconf | grep proxy_read_maps</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">On my Zimbra 8, the result would shown as below<br />
</span></span></p>
<pre>$local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps $alias_maps</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Create a proxy_read_maps.cf file<br />
</span></span></p>
<pre>vi proxy_read_maps.cf</pre>
<p><span style="line-height: 1.5em;">and add </span><i style="line-height: 1.5em;">proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</i><span style="line-height: 1.5em;"><span style="line-height: 1.5em;"> on the last line of postconf result, so the result is supposedly like this:<br />
</span></span></p>
<pre>$local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps $alias_maps, proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Navigate to /opt/zimbra/conf and create ldap-slm.cf file<br />
</span></span></p>
<pre>cd /opt/zimbra/conf
grep server_host /opt/zimbra/conf/ldap-vam.cf
grep bind_pw /opt/zimbra/conf/ldap-vam.cf
vi ldap-slm.cf</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Content of ldap-slm.cf file<br />
</span></span></p>
<pre>server_host = <b>ldap://HOST:389</b>
server_port = 389
search_base =
query_filter = (&amp;(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s)(zimbraMailCatchAllAddress=%s)(mail=%s))(zimbraMailStatus=enabled))
result_attribute = zimbraMailDeliveryAddress,zimbraMailForwardingAddress,zimbraPrefMailForwardingAddress,zimbraMailCatchAllForwardingAddress,uid
version = 3
<b>start_tls = yes</b>
tls_ca_cert_dir = /opt/zimbra/conf/ca
bind = yes
bind_dn = uid=zmpostfix,cn=appaccts,cn=zimbra
bind_pw = <b>PASSWORD</b>
timeout = 30</pre>
</li>
<li><span style="line-height: 1.5em;">Replace </span><i style="line-height: 1.5em;">server_host  </i><span style="line-height: 1.5em;">and </span><i style="line-height: 1.5em;">bind_pw </i><span style="line-height: 1.5em;">with the result of grep command</span></li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Save all changes and then run the postfix reload to apply the changes<br />
</span></span></p>
<pre>chown zimbra:postfix ldap-slm.cf
postfix reload</pre>
</li>
<li>Test the policy by telnet to your Zimbra server and send an email from internal to internal users without prior authorization
<pre>telnet mail.mycompanydomain.co.id 25
Trying XXX.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@mycompanydomain.co.id</strong>
250 2.1.0 Ok
<strong>rcpt to:vivianchow@mycompanydomain.co.id</strong>
553 5.7.1 vivianchow@mycompanydomain.co.id: Sender address rejected: not logged in</pre>
</li>
</ol>
<p>Notes : Please backup all configuration before trying to set the &#8220;Sender must login&#8221; policy to prevent  unexpected things <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>The post <a href="https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8-2/">Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8-2/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</title>
		<link>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8/</link>
					<comments>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Mon, 17 Feb 2014 23:04:49 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Mail Server]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Telnet]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1725</guid>

					<description><![CDATA[<p>As a powerful mail server, Zimbra has some system security features applied by default. We can also applying some additional security policy to increase mail server protection, such as applying PolicyD and Fail2Ban All the above security rule may be sufficient, but there are some additional security tips should be considered, especially in the case...</p>
<p>The post <a href="https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8/">Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/email.png"><img loading="lazy" decoding="async" class="alignleft wp-image-1829" style="margin: 5px;" src="http://54.254.121.108/wp-content/uploads/2014/02/email.png" alt="email" width="180" height="193" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/email.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/email-280x300.png 280w" sizes="auto, (max-width: 180px) 100vw, 180px" /></a>As a powerful mail server, Zimbra has some system security features applied by default. We can also applying some additional security policy to increase mail server protection, such as applying <a href="http://v2.vavai.net/tag/policyd/">PolicyD</a> and <a href="http://v2.vavai.net/2011/10/tips-improving-zimbra-mail-server-security-with-fail2ban/">Fail2Ban</a><br />
All the above security rule may be sufficient, but there are some additional security tips should be considered, especially in the case of SMTP authorization.<br />
Look at the following mail flow delivery, sent from or into Zimbra :<br />
<strong>From : External User   To : External User, Result : Relay Access Denied</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@yahoo.com</strong>
250 2.1.0 Ok
<strong>rcpt to:zezevavai@gmail.com</strong>
554 5.7.1 &lt;zezevavai@gmail.com&gt;: Relay access denied</pre>
<p><strong><span id="more-1725"></span>From : External User   To : Zimbra User, Result : Accepted with prior Scanning for Spam and Viruses</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@yahoo.com</strong>
250 2.1.0 Ok
<strong>rcpt to:myemail@mycompanydomain.co.id</strong>
250 2.1.5 Ok
<strong>data</strong>
354 End data with &lt;CR&gt;&lt;LF&gt;.&lt;CR&gt;&lt;LF&gt;
<strong>Hello Vavai</strong>
<strong>.</strong>
250 2.0.0 Ok: queued as C78EDB6E001
<strong>quit</strong>
221 2.0.0 Bye</pre>
<p><strong>From : Zimbra User  To : External User, Result : Accepted with prior SMTP Authorization check</strong><br />
Zimbra should be respond our request  with &#8220;Relay Access Denied when trying to send emails without prior authorization</p>
<pre>telnet mail.mycompanydomain.co.id 25
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
ehlo mail
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 6144000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from:vivianchow@mycompanydomain.co.id
250 2.1.0 Ok
rcpt to:myemail@gmail.com
554 5.7.1 &lt;myemail@vavai.com&gt;: Relay access denied</pre>
<p><strong>From : Zimbra User  To : Zimbra User, Result : Accepted WITHOUT prior SMTP Authorization check</strong></p>
<pre><strong>telnet mail.mycompanydomain.co.id 25</strong>
Trying 103.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 6144000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@mycompanydomain.co.id</strong>
250 2.1.0 Ok
<strong>rcpt to:vivianchow@mycompanydomain.co.id</strong>
250 2.1.5 Ok</pre>
<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg"><img loading="lazy" decoding="async" class="alignright size-full wp-image-1710" src="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg" alt="zimbra-logo" width="200" height="53" /></a>Look at the last example. I&#8217;m trying to send email from <strong>vivianchow@mycompanydomain.co.id </strong>to <strong>vivianchow@mycompanydomain.co.id </strong>without prior authorization and Zimbra accepted this email whereas should not. How if I&#8217;m trying to send fake email, let&#8217;s say from my boss email into my colleagues?<br />
To prevent the above security hole, below are some modification which are able to be applied on Zimbra 8. This modification will force the user to authenticate and login before sending an email to an internal users.</p>
<ol>
<li>Backup all configuration. Incorrect settings while applying &#8220;sender must login&#8221; policy would interfere Zimbra services and would stop your email communication</li>
<li>Log in as Zimbra user and edit <strong>/opt/zimbra/conf/zmconfigd.cf</strong><br />
Add the following lines right under <strong>POSTCONF smtpd_recipient_restrictions FILE zmconfigd/postfix_recipient_restrictions.cf</strong></p>
<pre>POSTCONF proxy_read_maps FILE zmconfigd/proxy_read_maps.cf</pre>
<p>and add the following lines right under <strong>POSTCONF smtpd_sender_restrictions FILE zmconfigd/smtpd_sender_restrictions.cf</strong></p>
<pre>POSTCONF smtpd_sender_login_maps proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</pre>
</li>
<li>Save your changes and then navigate to /opt/zimbra/conf/zmconfigd/ folder and edit smtpd_sender_restriction.cf
<pre>cd /opt/zimbra/conf/zmconfigd/
vi smtpd_sender_restrictions.cf</pre>
</li>
<li>Put the following code on the top of the lines
<pre>permit_mynetworks, reject_sender_login_mismatch</pre>
</li>
<li>Save your change</li>
<li>Check your read maps settings with the following command :
<pre>postconf | grep proxy_read_maps</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">On my Zimbra 8, the result would shown as below<br />
</span></span></p>
<pre>$local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps $alias_maps</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Create a proxy_read_maps.cf file<br />
</span></span></p>
<pre>vi proxy_read_maps.cf</pre>
<p><span style="line-height: 1.5em;">and add </span><i style="line-height: 1.5em;">proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</i><span style="line-height: 1.5em;"><span style="line-height: 1.5em;"> on the last line of postconf result, so the result is supposedly like this:<br />
</span></span></p>
<pre>$local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps $sender_bcc_maps $recipient_bcc_maps $smtp_generic_maps $lmtp_generic_maps $alias_maps, proxy:ldap:/opt/zimbra/conf/ldap-slm.cf</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Navigate to /opt/zimbra/conf and create ldap-slm.cf file<br />
</span></span></p>
<pre>cd /opt/zimbra/conf
grep server_host /opt/zimbra/conf/ldap-vam.cf
grep bind_pw /opt/zimbra/conf/ldap-vam.cf
vi ldap-slm.cf</pre>
</li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Content of ldap-slm.cf file<br />
</span></span></p>
<pre>server_host = <b>ldap://HOST:389</b>
server_port = 389
search_base =
query_filter = (&amp;(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s)(zimbraMailCatchAllAddress=%s)(mail=%s))(zimbraMailStatus=enabled))
result_attribute = zimbraMailDeliveryAddress,zimbraMailForwardingAddress,zimbraPrefMailForwardingAddress,zimbraMailCatchAllForwardingAddress,uid
version = 3
<b>start_tls = yes</b>
tls_ca_cert_dir = /opt/zimbra/conf/ca
bind = yes
bind_dn = uid=zmpostfix,cn=appaccts,cn=zimbra
bind_pw = <b>PASSWORD</b>
timeout = 30</pre>
</li>
<li><span style="line-height: 1.5em;">Replace </span><i style="line-height: 1.5em;">server_host  </i><span style="line-height: 1.5em;">and </span><i style="line-height: 1.5em;">bind_pw </i><span style="line-height: 1.5em;">with the result of grep command</span></li>
<li><span style="line-height: 1.5em;"><span style="line-height: 1.5em;">Save all changes and then run the postfix reload to apply the changes<br />
</span></span></p>
<pre>chown zimbra:postfix ldap-slm.cf
postfix reload</pre>
</li>
<li>Test the policy by telnet to your Zimbra server and send an email from internal to internal users without prior authorization
<pre>telnet mail.mycompanydomain.co.id 25
Trying XXX.XXX.XXX.XXX...
Connected to mail.mycompanydomain.co.id.
Escape character is '^]'.
220 mail.mycompanydomain.co.id ESMTP Postfix
<strong>ehlo mail</strong>
250-mail.mycompanydomain.co.id
250-PIPELINING
250-SIZE 51200000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
<strong>mail from:vivianchow@mycompanydomain.co.id</strong>
250 2.1.0 Ok
<strong>rcpt to:vivianchow@mycompanydomain.co.id</strong>
553 5.7.1 vivianchow@mycompanydomain.co.id: Sender address rejected: not logged in</pre>
</li>
</ol>
<p>Notes : Please backup all configuration before trying to set the &#8220;Sender must login&#8221; policy to prevent  unexpected things <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>The post <a href="https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8/">Zimbra Improvement : Restricted Sender/Sender Must Login on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-improvement-restricted-sendersender-must-login-on-zimbra-8/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Zimbra Tips : PolicyD &#038; Rate-Limit Sending Message Implementation on Zimbra 8</title>
		<link>https://www.vavai.net/zimbra-tips-policyd-rate-limit-sending-message-implementation-on-zimbra-8/</link>
					<comments>https://www.vavai.net/zimbra-tips-policyd-rate-limit-sending-message-implementation-on-zimbra-8/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Thu, 06 Feb 2014 13:59:53 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PolicyD]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1498</guid>

					<description><![CDATA[<p>From PolicyD website : Policyd v2 (codenamed &#8220;cluebringer&#8221;) 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...</p>
<p>The post <a href="https://www.vavai.net/zimbra-tips-policyd-rate-limit-sending-message-implementation-on-zimbra-8/">Zimbra Tips : PolicyD &#038; Rate-Limit Sending Message Implementation on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>From PolicyD website : <em>Policyd v2 (codenamed &#8220;cluebringer&#8221;) 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&#8217; long time involvement in large scale mail hosting industry. </em><br />
PolicyD can be integrated into Zimbra to add an anti spam layer, especially for rate-limit sending message. We can set maximum messages both for receiving and sending policy and prevent mail server IP address to be blacklisted due to spam message to outside network.<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vmware_zimbra_logo.jpg"><img loading="lazy" decoding="async" class=" wp-image-1499 alignleft" style="margin: 5px;" alt="vmware_zimbra_logo" src="http://54.254.121.108/wp-content/uploads/2014/02/vmware_zimbra_logo.jpg" width="257" height="199" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vmware_zimbra_logo.jpg 321w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vmware_zimbra_logo-300x233.jpg 300w" sizes="auto, (max-width: 257px) 100vw, 257px" /></a>PolicyD activation procedure on Zimbra 8 is slightly different from the procedures on previous version. Some of  features on PolicyD include Access Control, amavis, CheckHelo, CheckSPF, Greylisting, Quotas and Accounting. The new features can be configured through the Web Administration Policyd as well as standard feature.<br />
Below are PolicyD activation procedure on Zimbra 8, fully tested on Zimbra 8.0.6, the latest version of the time this article was written.<span id="more-1498"></span><br />
<strong>ACTIVATING POLICYD ADDON</strong><br />
[code language=&#8221;bash&#8221;]<br />
su &#8211; zimbra<br />
zmprov ms `zmhostname` +zimbraServiceInstalled cbpolicyd +zimbraServiceEnabled cbpolicyd<br />
zmlocalconfig -e postfix_enable_smtpd_policyd=yes<br />
zmprov mcf +zimbraMtaRestriction &#8220;check_policy_service inet:127.0.0.1:10031&#8221;<br />
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<br />
zmcontrol restart<br />
exit<br />
[/code]<br />
<strong>WEB UI ACTIVATION FOR POLICYD MANAGEMENT</strong><br />
Run the following command by using root permission<br />
[code language=&#8221;bash&#8221;]<br />
cd /opt/zimbra/httpd/htdocs/ &#038;&#038; ln -s ../../cbpolicyd/share/webui<br />
[/code]<br />
Modify file /opt/zimbra/cbpolicyd-2.1.0-beta/share/webui/includes/config.php (vi /opt/zimbra/cbpolicyd-2.1.0-beta/share/webui/includes/config.php) and mark a comment (#) to the line begining with: $DB_DSN and add the following code before line begining with : $DB_USER<br />
[code language=&#8221;bash&#8221;]<br />
$DB_DSN=&#8221;sqlite:/opt/zimbra/data/cbpolicyd/db/cbpolicyd.sqlitedb&#8221;;<br />
[/code]<br />
Reload Web UI (http) service with the following command :<br />
[code language=&#8221;bash&#8221;]<br />
cd /srv/<br />
wget -c http://devlabs.linuxassist.net/attachments/download/230/cluebringer-snapshot-2.1.x-201205100639.tar.gz<br />
tar -zxvf cluebringer-snapshot-2.1.x-201205100639.tar.gz<br />
cd cluebringer-snapshot-2.1.x-201205100639/webui/<br />
cp *.php *.css /opt/zimbra/cbpolicyd/share/webui/<br />
su &#8211; zimbra -c &#8220;zmapachectl restart&#8221;<br />
[/code]<br />
Try to open PolicyD web management by accessing the following URL : http://IpAddressOfZimbra:7780/webui/index.php, the correct result should be similar as below :<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/policyD_webadmin.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1500" alt="policyD_webadmin" src="http://54.254.121.108/wp-content/uploads/2014/02/policyD_webadmin.jpg" width="652" height="433" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/policyD_webadmin.jpg 931w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/policyD_webadmin-300x199.jpg 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/policyD_webadmin-768x510.jpg 768w" sizes="auto, (max-width: 652px) 100vw, 652px" /></a></p>
<p>The post <a href="https://www.vavai.net/zimbra-tips-policyd-rate-limit-sending-message-implementation-on-zimbra-8/">Zimbra Tips : PolicyD &#038; Rate-Limit Sending Message Implementation on Zimbra 8</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-tips-policyd-rate-limit-sending-message-implementation-on-zimbra-8/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 26/85 objects using Disk
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d3b35uem336dgh.cloudfront.net
Lazy Loading (feed)
Minified using Disk
Database Caching 15/38 queries in 0.016 seconds using Disk

Served from: www.vavai.net @ 2026-10-29 02:26:28 by W3 Total Cache
-->