Clearer explanation in faq/amavisd.sql.db.md.
This commit is contained in:
parent
3dafc31c92
commit
4b4cb32e0c
|
@ -37,7 +37,8 @@ Amavisd has two settings to use its SQL tables:
|
|||
### `@lookup_sql_dsn`
|
||||
|
||||
* Table `amavisd.mailaddr` stores email addresses __NOT__ hosted on your server.
|
||||
Note: value of column `mailaddr.email` could be something like below:
|
||||
|
||||
Note: value of column `mailaddr.email` could be something like below:
|
||||
|
||||
* `@.`: a catch-all address.
|
||||
* `@domain.com`: entire domain.
|
||||
|
@ -50,12 +51,17 @@ Amavisd has two settings to use its SQL tables:
|
|||
The addresses are used in several tables:
|
||||
|
||||
* `amavisd.wblist`: used by Amavisd. If sender (of inbound message) is
|
||||
blacklisted, Amavisd will quarantine this email.
|
||||
blacklisted, Amavisd will quarantine this email. But if you have iRedAPD
|
||||
plugin `amavisd_wblist` enabled, this smtp session will be rejected before
|
||||
queued by Postfix, so Amavisd doesn't know this rejected message at all.
|
||||
* `amavisd.outbound_wblist`. New in iRedMail-0.9.3, used by iRedAPD plugin
|
||||
`amavisd_wblist` for white/blacklisting for outbound message.
|
||||
|
||||
* `amavisd.users` stores mail addresses hosted on your server. Value of column
|
||||
`users.email` uses same format as `amavisd.mailaddr` mentioned above.
|
||||
* `amavisd.users` stores mail addresses hosted on your server. __NOTE__: you
|
||||
don't need to sync all existing mail users in this table, just add mail users
|
||||
you want to define a per-account spam policy in this table.
|
||||
|
||||
Value of column `users.email` uses same format as `amavisd.mailaddr` mentioned above.
|
||||
|
||||
* `amavisd.wblist` stores white/blacklists for inbound message. `wblist.sid`
|
||||
(sender id) refers to `mailaddr.id`, `wblist.rid` (recipient id) refers to
|
||||
|
|
|
@ -62,8 +62,8 @@
|
|||
<h3 id="lookup_sql_dsn"><code>@lookup_sql_dsn</code></h3>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Table <code>amavisd.mailaddr</code> stores email addresses <strong>NOT</strong> hosted on your server.
|
||||
Note: value of column <code>mailaddr.email</code> could be something like below:</p>
|
||||
<p>Table <code>amavisd.mailaddr</code> stores email addresses <strong>NOT</strong> hosted on your server.</p>
|
||||
<p>Note: value of column <code>mailaddr.email</code> could be something like below:</p>
|
||||
<ul>
|
||||
<li><code>@.</code>: a catch-all address.</li>
|
||||
<li><code>@domain.com</code>: entire domain.</li>
|
||||
|
@ -76,14 +76,18 @@
|
|||
<p>The addresses are used in several tables:</p>
|
||||
<ul>
|
||||
<li><code>amavisd.wblist</code>: used by Amavisd. If sender (of inbound message) is
|
||||
blacklisted, Amavisd will quarantine this email.</li>
|
||||
blacklisted, Amavisd will quarantine this email. But if you have iRedAPD
|
||||
plugin <code>amavisd_wblist</code> enabled, this smtp session will be rejected before
|
||||
queued by Postfix, so Amavisd doesn't know this rejected message at all.</li>
|
||||
<li><code>amavisd.outbound_wblist</code>. New in iRedMail-0.9.3, used by iRedAPD plugin
|
||||
<code>amavisd_wblist</code> for white/blacklisting for outbound message.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>amavisd.users</code> stores mail addresses hosted on your server. Value of column
|
||||
<code>users.email</code> uses same format as <code>amavisd.mailaddr</code> mentioned above.</p>
|
||||
<p><code>amavisd.users</code> stores mail addresses hosted on your server. <strong>NOTE</strong>: you
|
||||
don't need to sync all existing mail users in this table, just add mail users
|
||||
you want to define a per-account spam policy in this table.</p>
|
||||
<p>Value of column <code>users.email</code> uses same format as <code>amavisd.mailaddr</code> mentioned above.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>amavisd.wblist</code> stores white/blacklists for inbound message. <code>wblist.sid</code>
|
||||
|
|
Loading…
Reference in New Issue