Only preserve existing Message-ID when reediting a draft.

[claws.git] / manual / plugins.xml

diff --git a/manual/plugins.xml b/manual/plugins.xml
index d1dd00715db2400a715d9027b19faa1a758708b7..6cb2629ae15374d309caf05b68857d40082db821 100644 (file)
--- a/manual/plugins.xml
+++ b/manual/plugins.xml
@@ -96,8 +96,9 @@
          </para><para>
        Bogofilter's advantage over Spamassassin is its speed.
          </para><para>
-       Bogofilter only can filter emails after an initial learning (mark some
-       spams as Spam, and some legitimate emails as Ham).
+       Bogofilter must be trained before it can filter messages. To train
+       it you will need to mark some spam as Spam, and some legitimate 
+       emails as Ham.
          </para><para>
        Bogofilter is available from <ulink
        url="http://bogofilter.sourceforge.net/"
@@ -162,15 +163,6 @@
          </para>
        </listitem>
       </varlistentry>
-      <varlistentry>
-       <term>GeoLocation</term>
-       <listitem>
-         <para>
-       Provides geolocation functionality based on the addresses contained
-       in the messages.
-         </para>
-       </listitem>
-      </varlistentry>
       <varlistentry>
        <term>Libravatar</term>
        <listitem>
@@ -364,8 +356,8 @@
        If you're a developer, writing a plugin to extend Claws Mail's
        capabilities is probably the best and easiest solution. We will 
        provide hosting to your code, and will be glad to answer your questions
-       in the mailing-list or on the IRC channels, 
-       <literal>#claws</literal> on Freenode or IRCnet.
+       in the mailing-list or on the IRC channel,
+       <literal>#claws</literal> on Freenode.
     </para>
   </section>
 
@@ -397,5 +389,31 @@
     </para>
   </section>
 
+  <section id="plugin_path_config">
+    <title>Plugin path configuration</title>
+    <para>
+    By default, when loading a plugin, its full path is saved in
+    <filename>~/.claws-mail/clawsrc</filename>.
+    </para><para>
+    As most users have only one copy of Claws Mail installed and always
+    use the same installation method, this is not a problem.
+    </para><para>
+    However, if you have multiple copies of Claws Mail installed
+    and want to share the same configuration among them, this may not
+    work, particularly when using different versions of Claws Mail.
+    </para><para>
+    A second installed copy will try to load the plugins installed by
+    the first and, if the versions differ, the plugins will be rejected.
+    </para><para>
+    In order to avoid this problem you can manually edit the plugins
+    section in the <filename>clawsrc</filename> file, replacing the full
+    path with just the plugin file name of those you want to load
+    relative to the copy of Claws Mail being run.
+    </para><para>
+    In so doing, each copy of Claws Mail will try to load those plugins
+    from its own plugin directory, rather than a fixed location.
+    </para>
+  </section>
+
 </section>