2 commits - Administrator_Guide/en-US Installation_Guide/en-US

Jeroen van Meeuwen vanmeeuwen at kolabsys.com
Thu Jun 7 17:47:55 CEST 2012


 Administrator_Guide/en-US/Combating_Spam.xml      |  152 ++++++++++++++++++++++
 Installation_Guide/en-US/Preparing_the_System.xml |    7 -
 2 files changed, 156 insertions(+), 3 deletions(-)

New commits:
commit ad007e395ed1cfa8f24d0e55bbdf1619e6600827
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Thu Jun 7 16:47:17 2012 +0100

    Update documentation on default behaviour and tweaking such

diff --git a/Administrator_Guide/en-US/Combating_Spam.xml b/Administrator_Guide/en-US/Combating_Spam.xml
index 81e3225..ea5dacf 100644
--- a/Administrator_Guide/en-US/Combating_Spam.xml
+++ b/Administrator_Guide/en-US/Combating_Spam.xml
@@ -567,6 +567,158 @@ bayes_sql_override_username  root</screen>
 
     </section>
 
+    <section id="sect-Administrator_Guide-Combating_Spam-Default_Amavisd_Behaviour">
+        <title>Default Amavisd Behaviour</title>
+        <para>
+            The default behaviour shown in a Kolab Groupware deployment depends on the default settings that come with the packages delivered mostly through native, distribution-specific software repositories. This chapter documents various aspects of the behaviour Kolab Groupware will show referring to the appropriate settings that will allow a system administrator to modify the behaviour.
+        </para>
+        <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Adding_Spam_Information_Headers">
+            <title>Adding Spam Information Headers</title>
+            <para>
+                Amavisd, by default, adds spam information headers only to messages that;
+            </para>
+
+        </formalpara>
+        <para>
+            <orderedlist>
+                <listitem>
+                    <para>
+                        Are intended for delivery to recipients in local domain name spaces,
+                    </para>
+                    <para>
+                        The list of local domain name spaces Amavisd uses is configured using any of the following settings in <filename>/etc/amavisd/amavisd.conf</filename>:
+                    </para>
+                    <para>
+                        <itemizedlist>
+                            <listitem>
+                                <para>
+                                    <literal>@local_domains</literal>,
+                                </para>
+
+                            </listitem>
+                            <listitem>
+                                <para>
+                                    <literal>@local_domains_acl</literal>,
+                                </para>
+
+                            </listitem>
+                            <listitem>
+                                <para>
+                                    <literal>read_hash(\%local_domains)</literal>
+                                </para>
+
+                            </listitem>
+
+                        </itemizedlist>
+
+                    </para>
+
+                </listitem>
+                <listitem>
+                    <para>
+                        Get a spam score over <literal>2.0</literal> from <application>SpamAssassin</application>.
+                    </para>
+                    <para>
+                        The related setting is <literal>$sa_tag_level_deflt</literal> in <filename>/etc/amavisd/amavisd.conf</filename>.
+                    </para>
+
+                </listitem>
+
+            </orderedlist>
+
+        </para>
+        <formalpara id="form-Administrator_Guide-Default_Amavisd_Behaviour-Spam_Kill_Level">
+            <title>Spam Kill Level</title>
+            <para>
+                The spam kill level controls which score spam must have been marked with before Amavisd considers the message to not be delivered to the intended recipient(s).
+            </para>
+
+        </formalpara>
+        <para>
+            Depending on your platform, the default for this score is <literal>6.31</literal> or <literal>6.9</literal>. When a message is marked with a spam score higher than or equal to this level, Amavisd will take "evasive action". See <xref linkend="sect-Administrator_Guide-Default_Amavisd_Behaviour-Configuring_Evasive_Action" /> for more information on configuring evasive actions.
+        </para>
+        <section id="sect-Administrator_Guide-Default_Amavisd_Behaviour-Configuring_Evasive_Action">
+            <title>Configuring Evasive Action</title>
+            <para>
+                You can control what "evasive action" Amavisd takes using the <literal>$final_spam_destiny</literal> and <literal>$final_virus_destiny</literal> settings in <filename>/etc/amavisd/amavisd.conf</filename>. The default is usually to discard the message, but the following options are available:
+            </para>
+            <para>
+                <itemizedlist>
+                    <listitem>
+                        <formalpara id="form-Administrator_Guide-Configuring_Evasive_Action-D_PASS">
+                            <title>D_PASS</title>
+                            <para>
+                                The message is accepted for delivery to the intended recipient(s), despite having been scored passed the kill or cutoff level, and regardless of bad content.
+                            </para>
+
+                        </formalpara>
+                        <para>
+                            If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+                        </para>
+
+                    </listitem>
+                    <listitem>
+                        <formalpara id="form-Administrator_Guide-Configuring_Evasive_Action-D_BOUNCE">
+                            <title>D_BOUNCE</title>
+                            <para>
+                                The message is not accepted for delivery to the intended recipient(s). A Delivery Status Notification stating delivery failure is sent out to the sender.
+                            </para>
+
+                        </formalpara>
+                        <para>
+                            If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+                        </para>
+
+                    </listitem>
+                    <listitem>
+                        <formalpara id="form-Administrator_Guide-Configuring_Evasive_Action-D_REJECT">
+                            <title>D_REJECT</title>
+                            <para>
+                                The message is rejected by Amavisd, and while Amavisd sends out a 550 SMTP response to the Mail Transfer Agent, said Mail Transfer Agent is responsible for sending out the Delivery Status Notification, if any.
+                            </para>
+
+                        </formalpara>
+                        <para>
+                            If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+                        </para>
+
+                    </listitem>
+                    <listitem>
+                        <formalpara id="form-Administrator_Guide-Configuring_Evasive_Action-D_DISCARD">
+                            <title>D_DISCARD</title>
+                            <para>
+                                The message is simply discarded by Amavisd. The sending Mail Transfer Agent will receive a positive SMTP delivery response, and Amavisd sends out no Delivery Status Notification, nor does it forward the message for delivery to the intended recipients.
+                            </para>
+
+                        </formalpara>
+                        <para>
+                            If a quarantine address has been configured, the quarantine address will receive a copy of the email. See <xref linkend="form-Administrator_Guide-Configuring_Evasive_Action-Configuring_Quarantine" /> to learn how to configure the quarantine address.
+                        </para>
+
+                    </listitem>
+
+                </itemizedlist>
+
+            </para>
+            <formalpara id="form-Administrator_Guide-Configuring_Evasive_Action-Configuring_Quarantine">
+                <title>Configuring Quarantine</title>
+                <para>
+                    Two separate quarantine forwarding addresses can be configured. One is for messages labeled as spam, another for messages suspected to contain a virus.
+                </para>
+
+            </formalpara>
+            <para>
+                A catchall address for spam can be configured by setting the <literal>$spam_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>
+            </para>
+            <para>
+                A catchall address for messages suspected of containing a virus can be configured by setting the <literal>$virus_quarantine_to</literal> setting to a valid recipient address in <filename>/etc/amavisd/amavisd.conf</filename>.
+            </para>
+
+        </section>
+
+
+    </section>
+
 
 </chapter>
 


commit 450907aefaa7092e2da9fbbfe940c1e63d5784be
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date:   Thu Jun 7 13:07:42 2012 +0200

    Correct indentation

diff --git a/Installation_Guide/en-US/Preparing_the_System.xml b/Installation_Guide/en-US/Preparing_the_System.xml
index d0b1a31..7922658 100644
--- a/Installation_Guide/en-US/Preparing_the_System.xml
+++ b/Installation_Guide/en-US/Preparing_the_System.xml
@@ -44,6 +44,7 @@
             <para>
                 Should you decide to partition only after the packages have already been installed, or after the deployment has already been used, first mount the filesystems somewhere else and synchronize the contents over from the original directories over to the new filesystem hierarchy. Please note services should be stopped before doing so, or only corrupt data will be transfered. Remove the original contents of the filesystem after having synchronized, then mount the filesystems under their target mount points.
             </para>
+
         </important>
         <para>
             For large or multi-domain installations, we suggest moving <filename>/var/lib/imap/</filename> and <filename>/var/spool/imap/</filename> to <filename>/srv/imap/[<replaceable>$domain</replaceable>/]config/</filename> and <filename>/srv/imap/[<replaceable>$domain</replaceable>/]default/</filename> respectively. In allowing <filename>/srv/imap/</filename> to be one separate partition, backup using LVM snapshots is easier. Note that <replaceable>$domain</replaceable> in the aforementioned path is optional, and should only be used when multiple, but separate, isolated IMAP servers are to be started.
@@ -56,19 +57,19 @@
                 <itemizedlist>
                     <listitem>
                         <para>
-                            <literal>drwxr-xr-x. 7 mysql mysql 4096 May 11 15:34 /var/lib/mysql/</literal>
+                            <literal>drwxr-xr-x.  7 mysql mysql 4096 May 11 15:34 /var/lib/mysql/</literal>
                         </para>
 
                     </listitem>
                     <listitem>
                         <para>
-                            <literal>drwxr-x---. 20 cyrus mail 4096 May 11 17:04 /var/lib/imap/</literal>
+                            <literal>drwxr-x---. 20 cyrus mail  4096 May 11 17:04 /var/lib/imap/</literal>
                         </para>
 
                     </listitem>
                     <listitem>
                         <para>
-                            <literal>drwx------. 3 cyrus mail 4096 May 11 15:36 /var/spool/imap/</literal>
+                            <literal>drwx------.  3 cyrus mail  4096 May 11 15:36 /var/spool/imap/</literal>
                         </para>
 
                     </listitem>





More information about the commits mailing list