Update iRedMail upgrade tutorial:

- Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD.
This commit is contained in:
Zhang Huangbin 2016-04-26 22:44:34 +08:00
parent 0f5c247dbc
commit 184673b30e
2 changed files with 84 additions and 6 deletions

View File

@ -13,6 +13,7 @@
## ChangeLog ## ChangeLog
* 2016-04-26: Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD
* 2016-04-23: [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result * 2016-04-23: [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result
* 2016-04-13: Fixed: not add ssh port number in Fail2ban config file. * 2016-04-13: Fixed: not add ssh port number in Fail2ban config file.
* 2016-03-23: [NEW] Able to enable/disable SOGo access for a single user. * 2016-03-23: [NEW] Able to enable/disable SOGo access for a single user.
@ -104,9 +105,48 @@ chmod 0773 /var/lib/php/session
chmod o+t /var/lib/php/session chmod o+t /var/lib/php/session
``` ```
### Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD
!!! attention
This is __NOT__ applicable to Debian and Ubuntu.
There's a bug in iRedMail-0.9.3 and 0.9.4, it didn't comment out setting
`bypass_banned_checks_maps` in parameter `$policy_bank{'ORIGINATING'} = {}`,
this causes Amavisd won't perform banned file types checking for outgoing
emails sent through SMTP AUTH. Please follw steps below to fix it.
Open Amavisd config file, find parameter `$policy_bank{'ORIGINATING'} =` like
below:
* on RHEL/CentOS: it's `/etc/amavisd/amavisd.conf`
* on FreeBSD: it's `/usr/local/etc/amavisd.conf`
* on OpenBSD: it's `/etc/amavisd.conf`
```
$policy_bank{'ORIGINATING'} = {
...
bypass_banned_checks_maps => [1],
...
};
```
Comment out line `bypass_banned_checks_maps` like below:
```
$policy_bank{'ORIGINATING'} = {
...
#bypass_banned_checks_maps => [1],
...
};
```
Save the change. Restarting amavisd service is required.
### Fixed: not add alias for `virusalert` on non-Debian/Ubuntu OSes ### Fixed: not add alias for `virusalert` on non-Debian/Ubuntu OSes
Note: this is __NOT__ applicable to Debian and Ubuntu. !!! attention
This is __NOT__ applicable to Debian and Ubuntu.
There's a bug in iRedMail-0.9.4, it adds alias `virusalert` on only Debian and There's a bug in iRedMail-0.9.4, it adds alias `virusalert` on only Debian and
Ubuntu, but not other OSes. Please fix it with below commands: Ubuntu, but not other OSes. Please fix it with below commands:
@ -129,7 +169,9 @@ postalias /usr/local/etc/postfix/aliases
### [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result ### [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result
> Note: This is totally optional. !!! attention
Note: This step is totally optional.
It's helpful if you can see SpamAssassin testing result in log file at Amavisd It's helpful if you can see SpamAssassin testing result in log file at Amavisd
log_level 0. log_level 0.

View File

@ -25,6 +25,7 @@
<li><a href="#linux-fixed-not-add-ssh-port-number-in-fail2ban-config-file-jaillocal">[Linux] Fixed: not add ssh port number in Fail2ban config file (jail.local)</a></li> <li><a href="#linux-fixed-not-add-ssh-port-number-in-fail2ban-config-file-jaillocal">[Linux] Fixed: not add ssh port number in Fail2ban config file (jail.local)</a></li>
<li><a href="#rhelcentos-fixed-not-enable-cron-job-to-update-spamassassin-rules">[RHEL/CentOS] Fixed: Not enable cron job to update SpamAssassin rules</a></li> <li><a href="#rhelcentos-fixed-not-enable-cron-job-to-update-spamassassin-rules">[RHEL/CentOS] Fixed: Not enable cron job to update SpamAssassin rules</a></li>
<li><a href="#rhelcentos-fixed-not-create-required-directory-used-to-store-php-session-files">[RHEL/CentOS] Fixed: Not create required directory used to store PHP session files</a></li> <li><a href="#rhelcentos-fixed-not-create-required-directory-used-to-store-php-session-files">[RHEL/CentOS] Fixed: Not create required directory used to store PHP session files</a></li>
<li><a href="#fixed-not-perform-banned-file-types-checking-on-rhelcentosopenbsdfreebsd">Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD</a></li>
<li><a href="#fixed-not-add-alias-for-virusalert-on-non-debianubuntu-oses">Fixed: not add alias for virusalert on non-Debian/Ubuntu OSes</a></li> <li><a href="#fixed-not-add-alias-for-virusalert-on-non-debianubuntu-oses">Fixed: not add alias for virusalert on non-Debian/Ubuntu OSes</a></li>
<li><a href="#optional-add-custom-amavisd-log-template-to-always-log-spamassassin-testing-result">[OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</a></li> <li><a href="#optional-add-custom-amavisd-log-template-to-always-log-spamassassin-testing-result">[OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</a></li>
</ul> </ul>
@ -81,6 +82,7 @@ check <a href="../support.html">the details</a> and <a href="../contact.html">co
</div> </div>
<h2 id="changelog">ChangeLog</h2> <h2 id="changelog">ChangeLog</h2>
<ul> <ul>
<li>2016-04-26: Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD</li>
<li>2016-04-23: [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</li> <li>2016-04-23: [OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</li>
<li>2016-04-13: Fixed: not add ssh port number in Fail2ban config file.</li> <li>2016-04-13: Fixed: not add ssh port number in Fail2ban config file.</li>
<li>2016-03-23: [NEW] Able to enable/disable SOGo access for a single user.</li> <li>2016-03-23: [NEW] Able to enable/disable SOGo access for a single user.</li>
@ -156,8 +158,41 @@ chmod 0773 /var/lib/php/session
chmod o+t /var/lib/php/session chmod o+t /var/lib/php/session
</code></pre> </code></pre>
<h3 id="fixed-not-perform-banned-file-types-checking-on-rhelcentosopenbsdfreebsd">Fixed: Not perform banned file types checking on RHEL/CentOS/OpenBSD/FreeBSD</h3>
<div class="admonition attention">
<p class="admonition-title">Attention</p>
<p>This is <strong>NOT</strong> applicable to Debian and Ubuntu.</p>
</div>
<p>There's a bug in iRedMail-0.9.3 and 0.9.4, it didn't comment out setting
<code>bypass_banned_checks_maps</code> in parameter <code>$policy_bank{'ORIGINATING'} = {}</code>,
this causes Amavisd won't perform banned file types checking for outgoing
emails sent through SMTP AUTH. Please follw steps below to fix it.</p>
<p>Open Amavisd config file, find parameter <code>$policy_bank{'ORIGINATING'} =</code> like
below:
<em> on RHEL/CentOS: it's <code>/etc/amavisd/amavisd.conf</code>
</em> on FreeBSD: it's <code>/usr/local/etc/amavisd.conf</code>
* on OpenBSD: it's <code>/etc/amavisd.conf</code></p>
<pre><code>$policy_bank{'ORIGINATING'} = {
...
bypass_banned_checks_maps =&gt; [1],
...
};
</code></pre>
<p>Comment out line <code>bypass_banned_checks_maps</code> like below:</p>
<pre><code>$policy_bank{'ORIGINATING'} = {
...
#bypass_banned_checks_maps =&gt; [1],
...
};
</code></pre>
<p>Save the change. Restarting amavisd service is required.</p>
<h3 id="fixed-not-add-alias-for-virusalert-on-non-debianubuntu-oses">Fixed: not add alias for <code>virusalert</code> on non-Debian/Ubuntu OSes</h3> <h3 id="fixed-not-add-alias-for-virusalert-on-non-debianubuntu-oses">Fixed: not add alias for <code>virusalert</code> on non-Debian/Ubuntu OSes</h3>
<p>Note: this is <strong>NOT</strong> applicable to Debian and Ubuntu.</p> <div class="admonition attention">
<p class="admonition-title">Attention</p>
<p>This is <strong>NOT</strong> applicable to Debian and Ubuntu.</p>
</div>
<p>There's a bug in iRedMail-0.9.4, it adds alias <code>virusalert</code> on only Debian and <p>There's a bug in iRedMail-0.9.4, it adds alias <code>virusalert</code> on only Debian and
Ubuntu, but not other OSes. Please fix it with below commands:</p> Ubuntu, but not other OSes. Please fix it with below commands:</p>
<ul> <ul>
@ -177,9 +212,10 @@ postalias /usr/local/etc/postfix/aliases
</code></pre> </code></pre>
<h3 id="optional-add-custom-amavisd-log-template-to-always-log-spamassassin-testing-result">[OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</h3> <h3 id="optional-add-custom-amavisd-log-template-to-always-log-spamassassin-testing-result">[OPTIONAL] Add custom Amavisd log template to always log SpamAssassin testing result</h3>
<blockquote> <div class="admonition attention">
<p>Note: This is totally optional.</p> <p class="admonition-title">Attention</p>
</blockquote> <p>Note: This step is totally optional.</p>
</div>
<p>It's helpful if you can see SpamAssassin testing result in log file at Amavisd <p>It's helpful if you can see SpamAssassin testing result in log file at Amavisd
log_level 0.</p> log_level 0.</p>
<p>Open Amavisd config file <code>amavisd.conf</code>, add below lines in BEFORE the last line <code>1; # insure a defined return value</code>:</p> <p>Open Amavisd config file <code>amavisd.conf</code>, add below lines in BEFORE the last line <code>1; # insure a defined return value</code>:</p>