</para><para>
Bogofilter's advantage over Spamassassin is its speed.
</para><para>
+ 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/"
>http://bogofilter.sourceforge.net/</ulink>.
<listitem>
<para>
Enables the rendering of HTML messages using the GTK+ port of the
- WebKit library.
+ WebKit library. By default, no remote content is loaded.
+ </para><para>
+ Plugin preferences can be found in
+ <quote>Configuration/Preferences/Plugins/Fancy</quote>.
</para>
</listitem>
</varlistentry>
</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>
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>
</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>