New: html/amavisd.wblist.html.

This commit is contained in:
Zhang Huangbin 2016-01-04 09:48:49 +08:00
parent 527cfe596a
commit 5899ce5fb0
7 changed files with 163 additions and 5 deletions

View File

@ -0,0 +1,64 @@
# Whitelists and Blacklists
[TOC]
This tutorial shows you how to whitelist and blacklist senders or recipients
with iRedAdmin-Pro and script shipped in iRedAPD (since iRedAPD-1.7.1).
## Manage whitelists and blacklists with iRedAdmin-Pro
With iRedAdmin-Pro, you can manage several levels of whitelists and blacklists:
* Global white/blacklists: under menu `System -> Anti Spam -> Whitelists & Blacklists`.
* Per-domain white/blacklists: in domain profile page, under tab `Whitelists and Blacklists`.
* Per-user white/blacklists: in user profile page, under tab `Whitelists and Blacklists`.
Screenshot attached below.
## Manage whitelists and blacklists with SQL commands
Since iRedAPD-1.7.1, iRedAPD ships script `tools/wblist_admin.py` to help you
manage white/blacklists. To get full usage message, please run this script
without argument like this:
```
# cd /opt/iredapd/tools/
# python wblist_admin.py
```
Sample usages:
* Add server-wide whitelisted or blacklisted senders:
```
# python wblist_admin.py --add --whitelist 202.96.134.133 john@example.com @test.com @.abc.com
# python wblist_admin.py --add --blacklist 202.96.134.133 john@example.com @test.com @.abc.com
```
* Show server-wide whitelisted and blacklisted senders:
```
# python wblist_admin.py --list --whitelist
# python wblist_admin.py --list --blacklist
```
* For per-domain or per-user white/blacklists, please add argument `--account`.
like below:
```
# python wblist_admin.py --account mydomain.com --add --whitelist 202.96.134.133
# python wblist_admin.py --account user@mydomain.com --add --blacklist 202.96.134.133
# python wblist_admin.py --account mydomain.com --list --whitelist
# python wblist_admin.py --account user@mydomain.com --list --blacklist
```
* For outbound messages, please add argument `--outbound`. like below:
```
# python wblist_admin.py --outbound --account mydomain.com --add --whitelist 202.96.134.133
```
Screenshot of iRedAdmin-Pro:
![](http://www.iredmail.org/images/iredadmin/system_wblist.png)

View File

@ -51,6 +51,8 @@ Detailed release notes are available [here](./iredapd.releases.html).
### Migrate from Cluebringer to iRedAPD
> NOTE: If your server doesn't have Cluebringer installed, please ignore this step.
In iRedMail-0.9.3, Cluebringer has been removed and replaced by iRedAPD.
Cluebringer is not under active development and no new release since 2013 (the
latest stable release doesn't support IPv6). iRedAPD offers greylisting and
@ -67,6 +69,8 @@ throttling settings from Cluebringer to iRedAPD:
Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
latest stable release immediately: [How to upgrade Roundcube](http://trac.roundcube.net/wiki/Howto_Upgrade)
Note: package `rsync` must be installed on your server before upgrading.
### Postfix: Add additional aliases
ClamAV may detect virus in email, notification will be sent to system account
@ -147,8 +151,8 @@ $originating = 1;
* Open Postfix config file `/etc/postfix/master.cf` (Linux/OpenBSD) or
`/usr/local/etc/postfix/master.cf` (FreeBSD), update transport `submission`
to use `content_filter=smtp-amavis:[127.0.0.1]:10026` as content filter like
below:
to uncomment `content_filter=smtp-amavis:[127.0.0.1]:10026` line, so that we
can use Amavisd with policy bank `ORIGINATING` as content filter. like below:
```
submission inet n - n - - smtpd

View File

@ -40,3 +40,4 @@ Detailed release notes are available [here](./iredapd.releases.html).
Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
latest stable release immediately: [How to upgrade Roundcube](http://trac.roundcube.net/wiki/Howto_Upgrade)
Note: package `rsync` must be installed on your server before upgrading.

83
html/amavisd.wblist.html Normal file
View File

@ -0,0 +1,83 @@
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Whitelists and Blacklists</title>
<link rel="stylesheet" type="text/css" href="./css/markdown.css" />
</head>
<body>
<div id="navigation">
<a href="http://www.iredmail.org" target="_blank">iRedMail web site</a>
// <a href="./index.html">Document Index</a>
</div><h1 id="whitelists-and-blacklists">Whitelists and Blacklists</h1>
<div class="toc">
<ul>
<li><a href="#whitelists-and-blacklists">Whitelists and Blacklists</a><ul>
<li><a href="#manage-whitelists-and-blacklists-with-iredadmin-pro">Manage whitelists and blacklists with iRedAdmin-Pro</a></li>
<li><a href="#manage-whitelists-and-blacklists-with-sql-commands">Manage whitelists and blacklists with SQL commands</a></li>
</ul>
</li>
</ul>
</div>
<p>This tutorial shows you how to whitelist and blacklist senders or recipients
with iRedAdmin-Pro and script shipped in iRedAPD (since iRedAPD-1.7.1).</p>
<h2 id="manage-whitelists-and-blacklists-with-iredadmin-pro">Manage whitelists and blacklists with iRedAdmin-Pro</h2>
<p>With iRedAdmin-Pro, you can manage several levels of whitelists and blacklists:</p>
<ul>
<li>Global white/blacklists: under menu <code>System -&gt; Anti Spam -&gt; Whitelists &amp; Blacklists</code>.</li>
<li>Per-domain white/blacklists: in domain profile page, under tab <code>Whitelists and Blacklists</code>.</li>
<li>Per-user white/blacklists: in user profile page, under tab <code>Whitelists and Blacklists</code>.</li>
</ul>
<p>Screenshot attached below.</p>
<h2 id="manage-whitelists-and-blacklists-with-sql-commands">Manage whitelists and blacklists with SQL commands</h2>
<p>Since iRedAPD-1.7.1, iRedAPD ships script <code>tools/wblist_admin.py</code> to help you
manage white/blacklists. To get full usage message, please run this script
without argument like this:</p>
<pre><code># cd /opt/iredapd/tools/
# python wblist_admin.py
</code></pre>
<p>Sample usages:</p>
<ul>
<li>Add server-wide whitelisted or blacklisted senders:</li>
</ul>
<pre><code># python wblist_admin.py --add --whitelist 202.96.134.133 john@example.com @test.com @.abc.com
# python wblist_admin.py --add --blacklist 202.96.134.133 john@example.com @test.com @.abc.com
</code></pre>
<ul>
<li>Show server-wide whitelisted and blacklisted senders:</li>
</ul>
<pre><code># python wblist_admin.py --list --whitelist
# python wblist_admin.py --list --blacklist
</code></pre>
<ul>
<li>For per-domain or per-user white/blacklists, please add argument <code>--account</code>.
like below:</li>
</ul>
<pre><code># python wblist_admin.py --account mydomain.com --add --whitelist 202.96.134.133
# python wblist_admin.py --account user@mydomain.com --add --blacklist 202.96.134.133
# python wblist_admin.py --account mydomain.com --list --whitelist
# python wblist_admin.py --account user@mydomain.com --list --blacklist
</code></pre>
<ul>
<li>For outbound messages, please add argument <code>--outbound</code>. like below:</li>
</ul>
<pre><code># python wblist_admin.py --outbound --account mydomain.com --add --whitelist 202.96.134.133
</code></pre>
<p>Screenshot of iRedAdmin-Pro:</p>
<p><img alt="" src="http://www.iredmail.org/images/iredadmin/system_wblist.png" /></p><p style="text-align: center; color: grey;">All documents are available in <a href="https://bitbucket.org/zhb/iredmail-docs/src">BitBucket repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. If you found something wrong, please do <a href="http://www.iredmail.org/contact.html">contact us</a> to fix it.<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-3293801-21', 'auto');
ga('send', 'pageview');
</script>
</body></html>

View File

@ -84,6 +84,7 @@
<li><a href="allow.member.to.send.email.as.mail.list.html">Allow member to send email as mailing list or mail alias</a></li>
<li><a href="allow.user.to.send.email.without.authentication.html">Allow user to send email without smtp authentication</a></li>
<li><a href="amavisd.per-recipient.policy.lookup.html">Amavisd: Enable per-recipient policy lookup</a></li>
<li><a href="amavisd.wblist.html">Whitelists and Blacklists</a></li>
<li><a href="authenticate.without.domain.name.html">Authenticate without domain part in email address</a></li>
<li><a href="change.server.hostname.html">Change server hostname</a></li>
<li><a href="concurrent.processing.html">Process more emails concurrently</a></li>

View File

@ -102,6 +102,9 @@ sql&gt; INSERT INTO greylisting (account, priority, sender, sender_priority, act
<p>Detailed release notes are available <a href="./iredapd.releases.html">here</a>.</p>
<h3 id="migrate-from-cluebringer-to-iredapd">Migrate from Cluebringer to iRedAPD</h3>
<blockquote>
<p>NOTE: If your server doesn't have Cluebringer installed, please ignore this step.</p>
</blockquote>
<p>In iRedMail-0.9.3, Cluebringer has been removed and replaced by iRedAPD.
Cluebringer is not under active development and no new release since 2013 (the
latest stable release doesn't support IPv6). iRedAPD offers greylisting and
@ -117,6 +120,7 @@ in next iRedAdmin-Pro release.</p>
<h3 id="upgrade-roundcube-webmail-to-the-latest-stable-release">Upgrade Roundcube webmail to the latest stable release</h3>
<p>Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
latest stable release immediately: <a href="http://trac.roundcube.net/wiki/Howto_Upgrade">How to upgrade Roundcube</a></p>
<p>Note: package <code>rsync</code> must be installed on your server before upgrading.</p>
<h3 id="postfix-add-additional-aliases">Postfix: Add additional aliases</h3>
<p>ClamAV may detect virus in email, notification will be sent to system account
<code>virusalert</code>.</p>
@ -197,8 +201,8 @@ quarantined mails.</p>
<li>
<p>Open Postfix config file <code>/etc/postfix/master.cf</code> (Linux/OpenBSD) or
<code>/usr/local/etc/postfix/master.cf</code> (FreeBSD), update transport <code>submission</code>
to use <code>content_filter=smtp-amavis:[127.0.0.1]:10026</code> as content filter like
below:</p>
to uncomment <code>content_filter=smtp-amavis:[127.0.0.1]:10026</code> line, so that we
can use Amavisd with policy bank <code>ORIGINATING</code> as content filter. like below:</p>
</li>
</ul>
<pre><code>submission inet n - n - - smtpd

View File

@ -51,7 +51,8 @@ latest stable release:
<p>Detailed release notes are available <a href="./iredapd.releases.html">here</a>.</p>
<h3 id="upgrade-roundcube-webmail-to-the-latest-stable-release">Upgrade Roundcube webmail to the latest stable release</h3>
<p>Please follow Roundcube official tutorial to upgrade Roundcube webmail to the
latest stable release immediately: <a href="http://trac.roundcube.net/wiki/Howto_Upgrade">How to upgrade Roundcube</a></p><p style="text-align: center; color: grey;">All documents are available in <a href="https://bitbucket.org/zhb/iredmail-docs/src">BitBucket repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. If you found something wrong, please do <a href="http://www.iredmail.org/contact.html">contact us</a> to fix it.<script>
latest stable release immediately: <a href="http://trac.roundcube.net/wiki/Howto_Upgrade">How to upgrade Roundcube</a></p>
<p>Note: package <code>rsync</code> must be installed on your server before upgrading.</p><p style="text-align: center; color: grey;">All documents are available in <a href="https://bitbucket.org/zhb/iredmail-docs/src">BitBucket repository</a>, and published under <a href="http://creativecommons.org/licenses/by-nd/3.0/us/" target="_blank">Creative Commons</a> license. If you found something wrong, please do <a href="http://www.iredmail.org/contact.html">contact us</a> to fix it.<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)