[evolution] User Docs: Clarify Bogofilter usage again. Fixes bug #665008

[Andre Klapper <aklapper src gnome org>]

commit ee82d456d057ac63ff3e9193d8bbe882bf02192c
Author: Andre Klapper <a9016009 gmx de>
Date:   Wed Mar 7 18:08:32 2012 +0100

    User Docs: Clarify Bogofilter usage again. Fixes bug #665008

 help/C/mail-spam-marking.page |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/help/C/mail-spam-marking.page b/help/C/mail-spam-marking.page
index cb9ce30..90cc9d6 100644
--- a/help/C/mail-spam-marking.page
+++ b/help/C/mail-spam-marking.page
@@ -12,6 +12,9 @@
       <email its:translate="no">ak-47 gmx net</email>
     </credit>
     <credit type="author">
+      <name its:translate="no">Pete Biggs</name>
+    </credit>
+    <credit type="author">
       <name its:translate="no">Barbara Tobias</name>
       <email its:translate="no">barbtobias09 gmail com</email>
     </credit>
@@ -26,7 +29,7 @@
 
 <title>Marking Mail as Junk</title>
 
-<p>While SpamAssassin comes with a set of predefined rules, Bogofilter needs to be taught first before it will automatically filter junk mail. In any case, when you first start using junk mail blocking, check the <gui>Junk</gui> mail folder frequently to be sure that legitimate mail doesn't get flagged as junk mail.</p>
+<p>While SpamAssassin comes with a set of predefined rules, Bogofilter needs to be taught first before it will automatically filter junk mail. If you only train Bogofilter on bad messages, it will assume all mail is bad (because it does not know any difference) hence it will not make any decisions until the database is sufficiently large to determine what is and is not spam. In any case, when you first start using junk mail blocking, check the <gui>Junk</gui> mail folder frequently to be sure that legitimate mail doesn't get flagged as junk mail.</p>
 
 <section id="marking-junk">
 <title>Manually Marking Junk Mail</title>