<?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>Telnet Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://www.vavai.net/tag/telnet/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/telnet/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Mon, 17 Feb 2014 23:04:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<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 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="(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 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 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 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="(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>
	</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 30/54 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/31 queries in 0.012 seconds using Disk

Served from: www.vavai.net @ 2026-10-29 06:56:51 by W3 Total Cache
-->