[Amavisadmin-svn] SF.net SVN: amavisadmin: [59] amavisadmin/branches/documentation_1_0/docs

[<str...@us...>]

Revision: 59
          http://amavisadmin.svn.sourceforge.net/amavisadmin/?rev=59&view=rev
Author:   streindl
Date:     2007-01-28 08:57:16 -0800 (Sun, 28 Jan 2007)

Log Message:
-----------
First valid parts of user guide

Modified Paths:
--------------
    amavisadmin/branches/documentation_1_0/docs/user_guide.xml

Added Paths:
-----------
    amavisadmin/branches/documentation_1_0/docs/architecture.png

Added: amavisadmin/branches/documentation_1_0/docs/architecture.png
===================================================================
(Binary files differ)


Property changes on: amavisadmin/branches/documentation_1_0/docs/architecture.png
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream

Modified: amavisadmin/branches/documentation_1_0/docs/user_guide.xml
===================================================================
--- amavisadmin/branches/documentation_1_0/docs/user_guide.xml	2007-01-28 16:44:38 UTC (rev 58)
+++ amavisadmin/branches/documentation_1_0/docs/user_guide.xml	2007-01-28 16:57:16 UTC (rev 59)
@@ -111,20 +111,20 @@
       only after an administrator has approved the request.</para>
 
       <figure id="fig-architecture">
-          <title>Architecture of a system receiving mails and processing them
-          trough Amavisd-new</title>
+        <title>Architecture of a system receiving mails and processing them
+        trough Amavisd-new</title>
 
-          <mediaobject>
-            <imageobject>
-              <imagedata fileref="architecture.png" />
-            </imageobject>
-          </mediaobject>
+        <mediaobject>
+          <imageobject>
+            <imagedata fileref="architecture.png" />
+          </imageobject>
+        </mediaobject>
       </figure>
-      
-      <para>Figure xx gives an overview about the general architecture
-      and how AmavisAdmin fits into the figure. The flow for incoming mails
-      (either internet or intranet) is as follows:</para>
 
+      <para><xref linkend="fig-architecture" /> gives an overview about the
+      general architecture and how AmavisAdmin fits into the figure. The flow
+      for incoming mails (either internet or intranet) is as follows:</para>
+
       <procedure>
         <step>
           <para>The postfix daemon accepts an incoming mail. First basic
@@ -148,7 +148,7 @@
           <para>After performing the checks, general mail informartion is
           stored in the quarantine database. If the mail is containing
           problematic contents (i.e. viruses, SPAM, banned attachments,) also
-          the mail content is stored in the database. </para>
+          the mail content is stored in the database.</para>
         </step>
 
         <step>
@@ -168,14 +168,45 @@
           read his mail or informational mail.</para>
         </step>
       </procedure>
+
+      <para>Assume a customer complains about a problem in one of your
+      products and you can immediately fix the problem and for customer
+      statisfaction, you are going to deliver a hot fix to the customer via
+      e-mail. While sending the file, the Amavisd-new scanner will reject the
+      delivery of the file as it contains an executable which are rejected by
+      your companies security policies.</para>
+
+      <para>You can now log in into AmavisAdmin and you will immediately see
+      this (and probably other) blocked e-mail and as in this case you have a
+      reason to let this mail pass through to the customer, you will ask for
+      releasing the mail. This request will then pass to an admin who will
+      then approve (or reject) the request. After approval the AmavisAdmin
+      daemon will pass the mail trough Amavisd-new as if the mail would have
+      never been blocked.</para>
+
+      <para>AmavisAdmin does a couple of other things, for example keeping the
+      database reasonable small by removing old mails, informing users and
+      adminstrators about new mails to be handled or approved, ...</para>
+
+      <para>The advantage of AmavisAdmin is that there's no need to change the
+      existing flow or policies of handling SPAM/virus mails in the company.
+      By doing minor modifications in the Amavisd-new configuration (if
+      there's a SQL server in the loop already) you can incorporate
+      AmavisAdmin immediately. For details please refer to the installation
+      manual and the administration part later in this document.</para>
     </chapter>
 
     <chapter>
       <title>Logging in</title>
 
       <section>
-        <title>Logging in the first time</title>
+        <title>Connecting to AmavisAdmin</title>
 
+        <para>AmavisAdmin (from the user's perspecive) is a web application
+        that can be used from everywhere by connecting to a specific web page.
+        This can be done using your favourite web-browser to connect to the
+        AmavisAdmin landing page:</para>
+
         <para></para>
       </section>
     </chapter>


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.