From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JyYCA-0001pH-IH for garchives@archives.gentoo.org; Tue, 20 May 2008 20:12:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F2B66E03C5; Tue, 20 May 2008 20:12:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 2F249E03C5 for ; Tue, 20 May 2008 20:12:25 +0000 (UTC) Received: from stork.gentoo.org (stork.gentoo.org [64.127.104.133]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id A65256580D for ; Tue, 20 May 2008 20:12:24 +0000 (UTC) Received: from swift by stork.gentoo.org with local (Exim 4.68) (envelope-from ) id 1JyYC7-0005cY-Iu for gentoo-doc-cvs@lists.gentoo.org; Tue, 20 May 2008 20:12:23 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: mailfilter-guide.xml Message-Id: From: Sven Vermeulen Date: Tue, 20 May 2008 20:12:23 +0000 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@lists.gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 2d70deb8-8712-460d-b6c7-ed4e0477687e X-Archives-Hash: ed5551fe495e39abe75a5d805f543b23 swift 08/05/20 20:12:23 Modified: mailfilter-guide.xml Log: Coding style Revision Changes Path 1.21 xml/htdocs/doc/en/mailfilter-guide.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mailfilter-guide.xml?rev=1.21&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mailfilter-guide.xml?rev=1.21&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mailfilter-guide.xml?r1=1.20&r2=1.21 Index: mailfilter-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mailfilter-guide.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- mailfilter-guide.xml 3 Aug 2007 01:31:02 -0000 1.20 +++ mailfilter-guide.xml 20 May 2008 20:12:23 -0000 1.21 @@ -1,6 +1,6 @@ - + @@ -36,7 +36,7 @@

This guide describe step by step how to install a spam and virus filtering mail -gateway. It is quite simple to adopt this to a single server solution. +gateway. It is quite simple to adopt this to a single server solution.

@@ -55,11 +55,11 @@

In this setup applications with good security records and readable configuration files have been chosen. The email MTA is postfix which -has a good security record and is fairly easy to setup right. -Postfix will listen normally on port 25 for incoming mail. Upon reception it -will forward it to Amavisd-new on port 10024. Amavisd-new will then filter -the mail through different filters before passing the mail back to Postfix -on port 10025 which in turn will forward the mail to the next mail server. +has a good security record and is fairly easy to setup right. +Postfix will listen normally on port 25 for incoming mail. Upon reception it +will forward it to Amavisd-new on port 10024. Amavisd-new will then filter +the mail through different filters before passing the mail back to Postfix +on port 10025 which in turn will forward the mail to the next mail server.

@@ -67,7 +67,7 @@ virus filtering and spam filtering. In this setup we will be using two helper applications one ClamAV for filtering virus mails and Spamassassin for filtering spam. Spamassassin itself can function as yet another layer of content filtering -framework and utilize the helper applications Vipul's Razor2 and DCC. +framework and utilize the helper applications Vipul's Razor2 and DCC.

@@ -91,8 +91,8 @@

-The first part (chapters 1 to 4) of the guide will describe the basic setup -of a mailfiltering gateway. The next chapters can be implemented individually +The first part (chapters 1 to 4) of the guide will describe the basic setup +of a mailfiltering gateway. The next chapters can be implemented individually with no dependence between each chapter. These chapters describe how to:

@@ -112,13 +112,13 @@ The IMAP folders will be using the maildir format. Having each mail in a separate file makes handling much simpler. If you're using mbox I propose to -give maildir a try. If you're not already using maildir emerge the necessary +give maildir a try. If you're not already using maildir emerge the necessary tools with emerge courier-imap.

A planned fifth part will contain various tips regarding performance and things -you may want to know (running chrooted, postfix restrictions, etc.). +you may want to know (running chrooted, postfix restrictions, etc.).

@@ -126,7 +126,7 @@ know and trust these third parties. In this setup only the decision to quarantine virus mails are based on a single third party. Using Spamassassin's scoring system the decision to stop spam mails are not made by a single -authority except perhaps Spamassassins own static rules. +authority except perhaps Spamassassins own static rules. @@ -137,7 +137,7 @@ link="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?UNIX03/Realtime_Blackhole_Lists_Are_Bad">Realtime Blackhole Lists Are Bad and The Spam -Problem: Moving Beyond RBLs +Problem: Moving Beyond RBLs @@ -152,7 +152,7 @@ experienced with setting up Postfix it might quickly become too complicated if all should be set up at once. If you need help you can find it in the excellent Virtual -Mailhosting System with Postfix Guide in the Gentoo Documentation. +Mailhosting System with Postfix Guide in the Gentoo Documentation.

@@ -165,8 +165,8 @@

-We start out by installing the most important programs: Amavisd-new, -Spamassassin and ClamAV. +We start out by installing the most important programs: Amavisd-new, +Spamassassin and ClamAV.

@@ -177,7 +177,7 @@
 As previously mentioned you should already have a working postfix
 instance running on the box. Basically this shouldn't be much more than
 emerge postfix and have a basic understanding of how Postfix is
-working.  
+working.
 
 
 
@@ -188,12 +188,12 @@
 
 
 If you're not setting up a gateway server but have the mailboxes on
-the same server you only have to create the MX-Record. 
+the same server you only have to create the MX-Record.
 
 
 
 While the programs are emerging fire up another shell and create the needed DNS
-records.  
+records.
 
 
 
@@ -213,7 +213,7 @@
 
 Some ADSL providers might block port 25 and force you to relay mail through one
 of their servers. Typically you have to create a secondary MX-Record
-like MX      20      backup-mx.some-isp.tld 
+like MX      20      backup-mx.some-isp.tld
 
 
 
@@ -240,7 +240,7 @@
 
 
   RazorTCP2703
-      
+
 
 
 

@@ -269,7 +269,7 @@
 #lmtp-amavis    unix -        -       n     -       2  lmtp
 #   -o lmtp_data_done_timeout=1200
 #   -o lmtp_send_xforward_command=yes
-     
+
 127.0.0.1:10025 inet n        -       n     -       -  smtpd
   -o content_filter=
   -o local_recipient_maps=
@@ -306,7 +306,7 @@
 
 
 If you want to reject spam early on in the process you can use the
-Before-Queue (proxy) method instead of the filter method. If you uncomment 
+Before-Queue (proxy) method instead of the filter method. If you uncomment
 the three lines you will have to set content_filter= in
 main.cf. This is not recommended for high traffic servers
 as the number of concurrent connections are limited to the number of
@@ -318,8 +318,8 @@
 
 
 
-If you, for any reason whatsoever, want to send mail from this box and don't 
-want it scanned, add another postfix instance by uncommenting the last two 
+If you, for any reason whatsoever, want to send mail from this box and don't
+want it scanned, add another postfix instance by uncommenting the last two
 lines and substitute with a proper IP.
 
 
@@ -337,7 +337,7 @@
 

 We also need to set the next hop destination for mail. Tell Postfix to filter
 all mail through an external content filter and enable explicit routing to let
-Postfix know where to forward the mail to.  
+Postfix know where to forward the mail to.
 
 
 @@ -367,7 +367,7 @@
 
 The format of the transport file is the normal Postfix hash file.
 Mail to the domain on the left hand side is forwarded to the destination on the
-right hand side.  
+right hand side.
 
 
 @@ -379,13 +379,13 @@
 does not actually read this file so we have to convert it to the proper format
 with postmap /etc/postfix/transport. This creates the file
 /etc/postfix/transport.db. There is no need to reload Postfix as it
-will automatically pick up the changes.  
+will automatically pick up the changes.
 
 
 
-If the next hop mail server is not listening on the standard SMTP port 25 you 
-can tell postfix to use a given port number, like 
-smtp:mail.mydomain.tld:25000.  
+If the next hop mail server is not listening on the standard SMTP port 25 you
+can tell postfix to use a given port number, like
+smtp:mail.mydomain.tld:25000.
 
 
 
@@ -418,7 +418,7 @@
 together severel different technologies. Upon reception of a mail message it
 will extract the mail, filter it through some custom filters, handle white and
 black listing, filter the mail through various virus scanners and finally it
-will filter the mail using SpamAssassin.  
+will filter the mail using SpamAssassin.
 
 
 
@@ -429,13 +429,14 @@
   

     it identifies dangerous file attachments and has policies to handle them
   
-  per-user, per-domain and system-wide policies for:
-  
-    whitelists
-    blacklists
-    spam score thresholds
-    virus and spam policies
-  
+  

+    per-user, per-domain and system-wide policies for:
+    
+      whitelists
+      blacklists
+      spam score thresholds
+      virus and spam policies
+    
   
 
 
@@ -468,21 +469,21 @@
 
  (Insert the domains to be scanned)
-$mydomain = 'example.com';     
+$mydomain = 'example.com';
 (Bind only to loopback interface)
 $inet_socket_bind = '127.0.0.1';
 (Forward to Postfix on port 10025)
 $forward_method = 'smtp:127.0.0.1:10025';
-$notify_method = $forward_method;       
+$notify_method = $forward_method;
 (Define the account to send virus alert emails)
 $virus_admin = "virusalert\@$mydomain";
 (Always add spam headers)
-$sa_tag_level_deflt  = -100; 
+$sa_tag_level_deflt  = -100;
 (Add spam detected header aka X-Spam-Status: Yes)
-$sa_tag2_level_deflt = 5; 
+$sa_tag2_level_deflt = 5;
 (Trigger evasive action at this spam level)
 $sa_kill_level_deflt = $sa_tag2_level_deflt;
-(Do not send delivery status notification to sender.  It does not affect 
+(Do not send delivery status notification to sender.  It does not affect
 delivery of spam to recipient. To do that, use the kill_level)
 $sa_dsn_cutoff_level = 10;
 Don't bounce messages left and right, quarantine
@@ -495,9 +496,9 @@
 
 With this line $sa_tag2_level_deflt = 5; you set the Spamassassin spam
 score to 5. This might be a bit low. As you might have noticed the Amavisd-new
-default is 6.3. If you don't want to see a single spam mail in your 
-mail folder choose 5, but if you don't want to deal with false positives 
-choose 6.3. 
+default is 6.3. If you don't want to see a single spam mail in your
+mail folder choose 5, but if you don't want to deal with false positives
+choose 6.3.
 
 
 
@@ -534,9 +535,9 @@
 LogSyslog
 LogVerbose
 LogFacility LOG_MAIL
-(Change pid file location) 
+(Change pid file location)
 PidFile /var/run/amavis/clamd.pid
-(Set the clamav socket) 
+(Set the clamav socket)
 LocalSocket /var/amavis/clamd
 (Close the connection when this limit is exceeded)
 StreamMaxLength 10M
@@ -552,9 +553,9 @@
 
 
 

-ClamAV comes with the freshclam deamon dedicated to periodical checks 
-of virus signature updates.  Instead of updating virus signatures twice a day 
-we will make freshclam update virus signatures every two hours.  
+ClamAV comes with the freshclam deamon dedicated to periodical checks
+of virus signature updates.  Instead of updating virus signatures twice a day
+we will make freshclam update virus signatures every two hours.
 
 
 @@ -572,7 +573,7 @@
 
 
 Start clamd with freshclam using the init scripts by modifying
-/etc/conf.d/clamd.  
+/etc/conf.d/clamd.
 
 
 @@ -604,10 +605,10 @@
 
 
 
-Razor2 is a collaborative and distributed spam checksum network. Install it 
-with emerge razor and create the needed configuration files. Do this 
-as user amavis by running su - amavis followed razor-admin 
--create.  
+Razor2 is a collaborative and distributed spam checksum network. Install it
+with emerge razor and create the needed configuration files. Do this
+as user amavis by running su - amavis followed razor-admin
+-create.
 
 
 @@ -632,7 +633,7 @@
 
 Like Razor2, dcc is a collaborative and distributed spam checksum network. Its
 philosopy is to count the number of recipients of a given mail identifying each
-mail with a fuzzy checksum.   
+mail with a fuzzy checksum.
 
 
 @@ -681,7 +682,7 @@
 
 You can find inspiration for your local.cf file by trying the SpamAssassin Configuration
-Generator.  
+Generator.
 
 
 
@@ -700,8 +701,8 @@
 
 Once mail really starts passing through this mail gateway you will probably
 discover that the above setup is not perfect. Maybe some of your customers like
-to receive mails that others wouldn't. You can whitelist/blacklist 
-envelope senders quite easily. Uncomment the following line in 
+to receive mails that others wouldn't. You can whitelist/blacklist
+envelope senders quite easily. Uncomment the following line in
 amavisd.conf.
 
 
@@ -710,15 +711,15 @@
 
 
 
-In the sender_scores_sitewide file you put complete email 
-addresses or just the domian parts and then note a positive/negative score 
+In the sender_scores_sitewide file you put complete email
+addresses or just the domian parts and then note a positive/negative score
 to add to the spam score.
 
 
  (Whitelist all emails from the specific email address)
 postmaster@example.net                -3.0
-(Whitelist all emails from the example.net excluding subdomains) 
+(Whitelist all emails from the example.net excluding subdomains)
 .example.net                          1.0
 
 
@@ -728,7 +729,7 @@
 
 
 Placing these addresses outside amavisd.conf is a cleaner and safer
-solution. 
+solution.
 
 
 
@@ -738,14 +739,14 @@
 
 
 
-In a later chapter I will show how to implement per-user policies using 
+In a later chapter I will show how to implement per-user policies using
 MySQL.
 
 
 
 While waiting for a better method you can add the following to
 amavisd.conf to bypass spam checks for postmaster and
-abuse mailboxes.  
+abuse mailboxes.
 
 
 @@ -761,7 +762,7 @@
 link="http://www.ietf.org/rfc/rfc2142.txt">RFC 2142 MAILBOX NAMES FOR COMMON
 SERVICES, ROLES AND FUNCTIONS. Otherwise your domains might end up listed
 in some of the evil lists over at rfc-ignorant.org.  
+link="http://www.rfc-ignorant.org/">rfc-ignorant.org.
 
 
 
@@ -812,8 +813,8 @@
 
 
 
-Now you have updated virus definitions and you know that 
-freshclam.conf is working properly.  
+Now you have updated virus definitions and you know that
+freshclam.conf is working properly.
 
 
 
@@ -843,7 +844,7 @@
 
 

 Now if no strange messages appear in the log file it is time for a new
-test.  
+test.
 
 
 
@@ -858,10 +859,10 @@
 
 
 For some unknown reason you can not complete a manual mail injection to
-amavisd with netcat. Use telnet instead.  
+amavisd with netcat. Use telnet instead.
 
 
-
 
+ # nc localhost 10024
 (Amavis working)
 220 [127.0.0.1] ESMTP amavisd-new service ready
@@ -931,7 +932,7 @@
 
 If you manually want to check some of the mails to ensure that you have no false
 positives you can use the following procmail recipe to sideline spam
-found into different mail folders.  
+found into different mail folders.
 
 
 
@@ -1019,11 +1020,11 @@
 
 
 
-This grants members of the mailusers groups access to amavis 
+This grants members of the mailusers groups access to amavis
 mail.
 
 
- 
+

 This makes the spam and ham folders writable but not readable. This way
 users can safely submit their ham without anyone else being able to read it.
 
@@ -1056,9 +1057,9 @@
  #Auto learn
 0 * * * *          /usr/bin/sa-learn --spam /var/amavis/.maildir/Bayes/.spam/{cur,new} \
-                    > /dev/null 2>&1 
+                    > /dev/null 2>&1
 0 * * * *          /usr/bin/sa-learn --ham /var/amavis/.maildir/Bayes/.ham/{cur,new} > \
-                   /dev/null 2>&1 
+                   /dev/null 2>&1
 
 
 
@@ -1080,7 +1081,7 @@
 
 
 Now modify amavis to redirect spam emails to the spamtrap account and
-keep spamheaders.  
+keep spamheaders.
 
 
 @@ -1102,7 +1103,7 @@
 sa-learn --ham and then redelivered with all headers intact using a
 patched version of smtpclient by Ralf S.
-Engelschall.  
+Engelschall.
 
 
 
@@ -1134,9 +1135,9 @@
 
 

 Now we only have to copy the redeliver.pl file to
-/usr/local/bin/. Download it or use 
-the version below.  
+/usr/local/bin/. Download it or use
+the version below.
 
 
 @@ -1236,7 +1237,7 @@
 
 
 -# wget http://jimsun.linxnet.com/downloads/pflogsumm-1.1.0.tar.gz 
+# wget http://jimsun.linxnet.com/downloads/pflogsumm-1.1.0.tar.gz
 # tar xzf pflogsumm-1.1.0.tar.gz
 # cp pflogsumm-1.1.0/pflogsumm.pl /usr/local/bin/
 
@@ -1302,13 +1303,13 @@
 mail the mail is rejected with a try again later message.
 This means that mail gets delayed but also that stupid spam bots
 that do not implement the RFC protocol will drop the attempt to
-deliver the spam and never retry.  With time spam bots will probably 
-adjust, however it will give other technologies more time to identify 
+deliver the spam and never retry.  With time spam bots will probably
+adjust, however it will give other technologies more time to identify
 the spam.
 
 
 
-If your ISP blocks incoming traffic on port 25 and relays all mail to you 
+If your ISP blocks incoming traffic on port 25 and relays all mail to you
 through their own mail server greylisting will not work.
 
 
@@ -1326,7 +1327,7 @@
 There are other greylisting policy servers for Postfix around (such as Gld, which is in Portage, and SQLgrey). Some of them support
-database backends, auto whitelisting and other neat features. 
+database backends, auto whitelisting and other neat features.
 
 
 
@@ -1367,7 +1368,7 @@
 situations for the mail queue and mail box situations, this is not the
 case with the greylisting database. If the file becomes corrupted
 you may not be able to receive mail at all until you delete the file
-by hand. 
+by hand.
 
 
 
@@ -1403,15 +1404,15 @@
 
 
 
-Be sure to specify check_sender_access AFTER 
+Be sure to specify check_sender_access AFTER
 reject_unauth_destination or else your system could become an
-open mail relay. 
+open mail relay.
 
 
 
 The greylist database gets polluted quickly with bogus addresses. It
 helps if you protect greylist lookups with other restrictions that
-reject unknown senders and/or recipients. 
+reject unknown senders and/or recipients.
 
 
 
@@ -1523,11 +1524,11 @@
 

 SPF allows domain owners to state in their DNS records which IP
 addressess should be allowed to send mails from their domain. This
-will prevent spammers from spoofing the Return-Path. 
+will prevent spammers from spoofing the Return-Path.
 
 
 
-If your ISP blocks incoming traffic on port 25 and relays all mail to you 
+If your ISP blocks incoming traffic on port 25 and relays all mail to you
 through their own mail server SPF will not work.
 
 
@@ -1556,7 +1557,7 @@
 
 
 Spamassassin 3.0 has support for SPF, however it is not enabled by default
-and the new policy daemon in Postfix supports SPF so let's install SPF support 
+and the new policy daemon in Postfix supports SPF so let's install SPF support
 for Postfix.
 
 
@@ -1583,7 +1584,7 @@
 
 
 The spf.pl coming with Postfix is slightly buggy so find
-and uncomment the following line: push @HANDLERS, "sender_permitted_from"; 
+and uncomment the following line: push @HANDLERS, "sender_permitted_from";
 use Mail::SPF::Query;. Furthermore in about line 199 substitute
 comemnt with comment. Alternatively you can download a
 development
@@ -1658,7 +1659,7 @@
 
 
 
-Now that the database is created we'll need to create the necessary tables. 
+Now that the database is created we'll need to create the necessary tables.
 You can cut and paste the following into the mysql prompt:
 
 
@@ -1694,7 +1695,7 @@
    wb         char(1) NOT NULL, -- W or Y / B or N / space=neutral
    PRIMARY KEY (rid,sid)
    );
-  
+
 CREATE TABLE policy (
    id               int unsigned NOT NULL auto_increment,
    policy_name      varchar(32),     -- not used by amavisd-new
@@ -1710,7 +1711,7 @@
    spam_quarantine_to   varchar(64) DEFAULT NULL, -- (optional field)
    spam_tag_level  float,  -- higher score inserts spam info headers
    spam_tag2_level float DEFAULT NULL,  -- higher score inserts
-               -- 'declared spam' info header fields 
+               -- 'declared spam' info header fields
    spam_kill_level float,  -- higher score activates evasive actions, e.g.
                -- reject/drop, quarantine, ...
                -- (subject to final_spam_destiny setting)
@@ -1724,20 +1725,20 @@
 
 
 
-Lookups trying to match email are done with raw (rfc2821-unquoted 
+Lookups trying to match email are done with raw (rfc2821-unquoted
 and unbracketed) addresses as a key, i.e.:
-John "Funny" Smith@example.com 
+John "Funny" Smith@example.com
 
 
 
-Lookups are performed in the following order: SQL, LDAP, 
+Lookups are performed in the following order: SQL, LDAP,
 hash, ACL, regexp, constant. The first that
 returns a definitive answer (not undef/NULL) stops the search.
 
 
 
 If you wish to use whitelisting and blacklisting you must add the
-sender and receiver to mailadr after which you create the relation 
+sender and receiver to mailadr after which you create the relation
 between the two e-mail addresses in wblist and state if it is
 whitelisting (W) or blacklisting (B).
 
@@ -1851,7 +1852,7 @@
 
 
 
-Now that the database is created we'll create the necessary tables. You can cut 
+Now that the database is created we'll create the necessary tables. You can cut
 and paste the following into the mysql prompt:
 
 
@@ -1884,7 +1885,7 @@
           ham_count             int(11)         NOT NULL default '0',
           atime                 int(11)         NOT NULL default '0',
           PRIMARY KEY           (id, token),
-	  INDEX                 (id, atime)
+          INDEX (id, atime)
           ) TYPE=MyISAM;
 
       CREATE TABLE bayes_vars (
@@ -1901,7 +1902,7 @@
           PRIMARY KEY           (id),
           UNIQUE bayes_vars_idx1 (username)
           ) TYPE=MyISAM;
-                        
+
       CREATE TABLE awl (
           username              varchar(100)    NOT NULL default '',
           email                 varchar(200)    NOT NULL default '',
@@ -1934,10 +1935,10 @@
 
 
 -su - amavis 
-sa-learn --sync 
-sa-learn --backup > backup.txt 
-sa-learn --restore backup.txt 
+su - amavis
+sa-learn --sync
+sa-learn --backup > backup.txt
+sa-learn --restore backup.txt
 
 
 
@@ -1993,7 +1994,7 @@
 
 To troubleshoot Amavisd-new start out by stopping it with /etc/init.d/amavisd
 stop and then start it manually in the foreground with amavisd debug
-and watch it for anomalies in the output.  
+and watch it for anomalies in the output.
 
 
 
@@ -2005,18 +2006,18 @@
 
 To troubleshoot Spamassassin you can filter an email through it with
 spamassassin -D < mail. To ensure that the headers are intact you can
-move it from another machine with IMAP.  
+move it from another machine with IMAP.
 
 
 
-If you need to troubleshoot you have to enable login for the user 
-amavis by changing the login shell in /etc/passwd to 
+If you need to troubleshoot you have to enable login for the user
+amavis by changing the login shell in /etc/passwd to
 /bin/bash.
 
 
 
 If you want you can make get the same information and more with Amavisd-new
-using amavisd debug-sa.  
+using amavisd debug-sa.
 
 
 
@@ -2031,7 +2032,7 @@
 link="http://marc.theaimsgroup.com/?l=amavis-user">Amavis User
 mailing list archives. If you find no answer here you can
 subscribe to the Amavis User 
+link="https://lists.sourceforge.net/lists/listinfo/amavis-user">Amavis User
 mailing list
 
 
@@ -2051,31 +2052,41 @@
 
 
 
-Amavisd-new
-INSTALL
-Amavisd-new
-Postfix README
-
-Amavisd-new
-Policy bank documentation
-
-Spamassassin
-SQL README
-Greylisting
-Postfix
-SMTPD_POLICY_README
-Blocking
-spammers with Postfix HELO controls
-SPF Overview
-Jim
-Seymour's Postfix Anti-UCE Cheat Sheet
+  
+    Amavisd-new
+    INSTALL
+  
+  
+    Amavisd-new
+    Postfix README
+  
+  
+    Amavisd-new
+    Policy bank documentation
+  
+  
+    Spamassassin
+    SQL README
+  
+  
+    Greylisting
+  
+  
+    Postfix
+    SMTPD_POLICY_README
+  
+  
+    Blocking
+    spammers with Postfix HELO controls
+  
+  
+    SPF
+    Overview
+  
+  
+    Jim
+    Seymour's Postfix Anti-UCE Cheat Sheet
+  
 
 
 
@@ -2085,17 +2096,24 @@
 
 
 
-Spamassassin
-Amavisd-new
-Amavisd-new
-documentation bits and pieces
-Vipuls's Razor
-Pyzor
-Distributed Checksum
-Clearinghouse
 Maia Mailguard
+  Spamassassin
+  Amavisd-new
+  
+    Amavisd-new
+    documentation bits and pieces
+  
+  Vipuls's Razor
+  Pyzor
+  
+    Distributed Checksum
+    Clearinghouse
+  
+  
+    Maia
+    Mailguard
+  
 
+
 
 
 
@@ -2103,12 +2121,14 @@
 
 
 
-Fairly-Secure Anti-SPAM
-Gateway Using OpenBSD, Postfix, Amavisd-new, SpamAssassin, Razor
-and DCC
+  
+    Fairly-Secure Anti-SPAM
+    Gateway Using OpenBSD, Postfix, Amavisd-new, SpamAssassin, Razor
+    and DCC
+  
 
+
 
 
 
-
 



-- 
gentoo-doc-cvs@lists.gentoo.org mailing list