plugins.xml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <section id="ch_plugins">
  3. <title>Extending Claws Mail</title>
  4. <section id="plugins_default">
  5. <title>Plugins</title>
  6. <para>
  7. Claws Mail's capabilities are extended by plugins, which are
  8. listed below.
  9. </para><para>
  10. Plugins are installed in <filename class="directory"
  11. >$PREFIX/lib/claws-mail/plugins/</filename> and have a suffix of
  12. <quote>.so</quote>. To load a plugin go to
  13. <quote>Configuration/Plugins</quote> and click the
  14. <quote>Load Plugin</quote> button. Select the plugin that you want and
  15. click <quote>Open</quote> button.
  16. </para><para>
  17. If you don't find the plugin you're looking for, it is possible that
  18. your Operating System distribution provides it in a separate package.
  19. In this case, search for the plugin in your package manager.
  20. </para><para>
  21. Some plugins provide the same functionality as others, (for example, the
  22. 3 anti-Spam plugins). In this case you will have to choose which
  23. one to load, as Claws Mail will refuse to load more than one of
  24. the same type.
  25. </para>
  26. <para>
  27. There is a list of all plugins available at <ulink
  28. url="http://www.claws-mail.org/plugins.php"
  29. >http://www.claws-mail.org/plugins.php</ulink>.
  30. </para>
  31. <variablelist>
  32. <varlistentry>
  33. <term>ACPI Notifier</term>
  34. <listitem>
  35. <para>
  36. Enables new mail notification via the LEDs found on some laptops like
  37. Acer, Asus, Fujitsu and IBM laptops.
  38. More information: <ulink
  39. url="http://www.claws-mail.org/plugin.php?plugin=acpinotifier"
  40. >www.claws-mail.org/plugin.php?plugin=acpinotifier</ulink>
  41. </para>
  42. </listitem>
  43. </varlistentry>
  44. <varlistentry>
  45. <term>AddressKeeper</term>
  46. <listitem>
  47. <para>
  48. Saves all unknown recipient addresses (<quote>To</quote>,
  49. <quote>Cc</quote> and/or <quote>Bcc</quote>) to a designated
  50. addressbook folder.
  51. </para>
  52. </listitem>
  53. </varlistentry>
  54. <varlistentry>
  55. <term>AttachWarner</term>
  56. <listitem>
  57. <para>
  58. Reminds you about possibly forgotten attachments. Checks for common
  59. expressions found when attaching a file and warns you if no attachment
  60. was added to the mail you're sending.
  61. More information: <ulink
  62. url="http://www.claws-mail.org/plugin.php?plugin=attachwarner"
  63. >www.claws-mail.org/plugin.php?plugin=attachwarner</ulink>
  64. </para>
  65. </listitem>
  66. </varlistentry>
  67. <varlistentry>
  68. <term>AttRemover</term>
  69. <listitem>
  70. <para>
  71. Allows you to remove attachments from emails.
  72. </para>
  73. </listitem>
  74. </varlistentry>
  75. <varlistentry>
  76. <term>Bogofilter</term>
  77. <listitem>
  78. <para>
  79. The Bogofilter plugin comes with two major features:
  80. </para><para>
  81. The ability to scan incoming mail received from a POP, IMAP or LOCAL
  82. account using Bogofilter. It can optionally delete mail identified
  83. as spam or save it to a designated folder. Mail scanning can be turned
  84. off.
  85. </para><para>
  86. The ability for users to teach Bogofilter to recognise spam or ham.
  87. You can train Bogofilter by marking messages as spam or ham from the
  88. Message List contextual menu, or using the relevant toolbar button in
  89. the main window or the message window (see
  90. <quote>Configuration/Preferences/Toolbars</quote>). Messages
  91. marked as spam are optionally saved to a designated folder.
  92. </para><para>
  93. Plugin preferences can be found in
  94. <quote>Configuration/Preferences/Plugins/Bogofilter</quote>.
  95. </para><para>
  96. Bogofilter's advantage over Spamassassin is its speed.
  97. </para><para>
  98. Bogofilter must be trained before it can filter messages. To train
  99. it you will need to mark some spam as Spam, and some legitimate
  100. emails as Ham.
  101. </para><para>
  102. Bogofilter is available from <ulink
  103. url="http://bogofilter.sourceforge.net/"
  104. >http://bogofilter.sourceforge.net/</ulink>.
  105. </para>
  106. </listitem>
  107. </varlistentry>
  108. <varlistentry>
  109. <term>BSFilter</term>
  110. <listitem>
  111. <para>
  112. BSFilter is a plugin that is very similar to the Bogofilter plugin
  113. but uses the bsfilter (<ulink url="http://bsfilter.org/index-e.html"
  114. >bsfilter.org/index-e.html</ulink>) bayesian spam filter as a backend.
  115. </para><para>
  116. Like Bogofilter, you have to train it with spam and ham
  117. messages in order for bsfilter to start recognising spam.
  118. </para><para>
  119. Plugin preferences can be found in
  120. <quote>Configuration/Preferences/Plugins/BSFilter</quote>.
  121. </para>
  122. </listitem>
  123. </varlistentry>
  124. <varlistentry>
  125. <term>Clamd</term>
  126. <listitem>
  127. <para>
  128. Allows scanning all messages received from IMAP, POP or local accounts
  129. using the clam daemon part of the ClamAV (AntiVirus) software (<ulink
  130. url="http://www.clamav.net/">http://www.clamav.net/</ulink>).
  131. </para>
  132. </listitem>
  133. </varlistentry>
  134. <varlistentry>
  135. <term>Fancy</term>
  136. <listitem>
  137. <para>
  138. Enables the rendering of HTML messages using the GTK+ port of the
  139. WebKit library. By default, no remote content is loaded.
  140. </para><para>
  141. Plugin preferences can be found in
  142. <quote>Configuration/Preferences/Plugins/Fancy</quote>.
  143. </para>
  144. </listitem>
  145. </varlistentry>
  146. <varlistentry>
  147. <term>Fetchinfo</term>
  148. <listitem>
  149. <para>
  150. Inserts headers containing some download information, like UIDL,
  151. Claws Mail' account name, POP server, user ID and retrieval time.
  152. </para>
  153. </listitem>
  154. </varlistentry>
  155. <varlistentry>
  156. <term>GData</term>
  157. <listitem>
  158. <para>
  159. Provides an interface to Google services using the gdata library.
  160. Currently, the only implemented functionality is to include Google
  161. Contacts in the Tab-address completion.
  162. </para>
  163. </listitem>
  164. </varlistentry>
  165. <varlistentry>
  166. <term>Libravatar</term>
  167. <listitem>
  168. <para>
  169. Enables the display of avatar images associated with user profiles at
  170. libravatar.org or the user's avatar enabled domains.
  171. More information: <ulink
  172. url="http://www.claws-mail.org/plugin.php?plugin=libravatar"
  173. >www.claws-mail.org/plugin.php?plugin=libravatar</ulink>
  174. </para>
  175. </listitem>
  176. </varlistentry>
  177. <varlistentry>
  178. <term>Mail Archiver</term>
  179. <listitem>
  180. <para>
  181. Enables folders and subfolders to be archived in several different
  182. formats.
  183. </para>
  184. </listitem>
  185. </varlistentry>
  186. <varlistentry>
  187. <term>mailMBOX</term>
  188. <listitem>
  189. <para>
  190. Handles mailboxes in MBox format.
  191. </para>
  192. </listitem>
  193. </varlistentry>
  194. <varlistentry>
  195. <term>NewMail</term>
  196. <listitem>
  197. <para>
  198. Writes a message header summary to a log file, (Default:
  199. <filename>~/Mail/NewLog</filename>), on arrival of new mail
  200. <emphasis>after</emphasis> sorting.
  201. </para>
  202. </listitem>
  203. </varlistentry>
  204. <varlistentry>
  205. <term>Notification</term>
  206. <listitem>
  207. <para>
  208. Provides various ways to notify the user of new and unread email.
  209. More information: <ulink
  210. url="http://www.claws-mail.org/plugin.php?plugin=notification"
  211. >www.claws-mail.org/plugin.php?plugin=notification</ulink>
  212. </para>
  213. </listitem>
  214. </varlistentry>
  215. <varlistentry>
  216. <term>PDF Viewer</term>
  217. <listitem>
  218. <para>
  219. Allows rendering of PDF and PostScript attachments using the Poppler
  220. library and GhostScript external program.
  221. More information: <ulink
  222. url="http://www.claws-mail.org/plugin.php?plugin=pdf_viewer"
  223. >www.claws-mail.org/plugin.php?plugin=pdf_viewer</ulink>
  224. </para>
  225. </listitem>
  226. </varlistentry>
  227. <varlistentry>
  228. <term>Perl</term>
  229. <listitem>
  230. <para>
  231. Intended to extend the filtering possibilities of Claws Mail. It
  232. provides a Perl interface to Claws Mail' filtering mechanism,
  233. allowing the use of full Perl power in email filters.
  234. </para>
  235. </listitem>
  236. </varlistentry>
  237. <varlistentry>
  238. <term>PGP/Core, PGP/Inline and PGP/MIME</term>
  239. <listitem>
  240. <para>
  241. Handles PGP signed and/or encrypted mails. You can decrypt mails,
  242. verify signatures or sign and encrypt your own mails. Uses GnuPG/GPGME,
  243. <ulink url="ftp://ftp.gnupg.org/gcrypt/gpgme/"
  244. >ftp://ftp.gnupg.org/gcrypt/gpgme/</ulink>.
  245. More information: <ulink
  246. url="http://www.claws-mail.org/plugin.php?plugin=gpg"
  247. >www.claws-mail.org/plugin.php?plugin=gpg</ulink>
  248. </para>
  249. </listitem>
  250. </varlistentry>
  251. <varlistentry>
  252. <term>Python</term>
  253. <listitem>
  254. <para>
  255. This plugin provides Python integration features.
  256. More information: <ulink
  257. url="http://www.claws-mail.org/plugin.php?plugin=python"
  258. >www.claws-mail.org/plugin.php?plugin=python</ulink>
  259. </para>
  260. </listitem>
  261. </varlistentry>
  262. <varlistentry>
  263. <term>RSSyl</term>
  264. <listitem>
  265. <para>
  266. Allows you to read your favorite newsfeeds in Claws. RSS 1.0, 2.0 and
  267. Atom feeds are currently supported.
  268. More information: <ulink
  269. url="http://www.claws-mail.org/plugin.php?plugin=rssyl"
  270. >www.claws-mail.org/plugin.php?plugin=rssyl</ulink>
  271. </para>
  272. </listitem>
  273. </varlistentry>
  274. <varlistentry>
  275. <term>S/MIME</term>
  276. <listitem>
  277. <para>
  278. Handles S/MIME signed and/or encrypted mails. You can decrypt mails,
  279. verify signatures or sign and encrypt your own mails. Uses GnuPG/GPGME
  280. and GpgSM, <ulink url="ftp://ftp.gnupg.org/gcrypt/gpgme/"
  281. >ftp://ftp.gnupg.org/gcrypt/gpgme/</ulink>.
  282. </para>
  283. </listitem>
  284. </varlistentry>
  285. <varlistentry>
  286. <term>SpamAssassin</term>
  287. <listitem>
  288. <para>
  289. The SpamAssassin plugin comes with two major features:
  290. </para><para>
  291. The ability to scan incoming mail received from a POP, IMAP or LOCAL
  292. account using SpamAssassin. It can optionally delete mail identified
  293. as spam or save it to a designated folder. Mail scanning can be turned
  294. off, which is useful if your email is scanned on your server.
  295. </para><para>
  296. The ability for users to teach SpamAssassin to recognise spam or ham.
  297. You can train SpamAssassin by marking messages as spam or ham from the
  298. Message List contextual menu, or using the relevant toolbar button in
  299. the main window or the message window (see
  300. <quote>Configuration/Preferences/Toolbars</quote>). Messages
  301. marked as spam are optionally saved to a designated folder.
  302. </para><para>
  303. Plugin preferences can be found in
  304. <quote>Configuration/Preferences/Plugins/SpamAssassin</quote>.
  305. </para><para>
  306. SpamAssassin's advantage over Bogofilter is that it's not only a
  307. bayesian filter, but it also performs various local and network tests
  308. to determine spaminess.
  309. </para><para>
  310. SpamAssassin is available from <ulink
  311. url="http://spamassassin.apache.org/"
  312. >http://spamassassin.apache.org/</ulink>. Version 3.1.x or higher is
  313. required to use the learning feature in TCP mode.
  314. </para>
  315. </listitem>
  316. </varlistentry>
  317. <varlistentry>
  318. <term>SpamReport</term>
  319. <listitem>
  320. <para>
  321. This plugin reports spam to various places.
  322. Currently the sites <ulink url="http://spam-signal.fr"
  323. >spam-signal.fr</ulink> and <ulink url="http://spamcop.net"
  324. >spamcop.net</ulink> are supported, and the <ulink
  325. url="http://lists.debian.org">Debian lists (lists.debian.org)</ulink>
  326. spam nomination system.
  327. </para>
  328. </listitem>
  329. </varlistentry>
  330. <varlistentry>
  331. <term>TNEF parse</term>
  332. <listitem>
  333. <para>
  334. This plugin enables reading <literal>application/ms-tnef</literal> attachments.
  335. More information: <ulink
  336. url="http://www.claws-mail.org/plugin.php?plugin=tnef_parser"
  337. >www.claws-mail.org/plugin.php?plugin=tnef_parser</ulink>
  338. </para>
  339. </listitem>
  340. </varlistentry>
  341. <varlistentry>
  342. <term>vCalendar</term>
  343. <listitem>
  344. <para>
  345. Enables vCalendar message handling like that produced by Evolution or
  346. Outlook, and Webcal subscriptions.
  347. More information: <ulink
  348. url="http://www.claws-mail.org/plugin.php?plugin=vcalendar"
  349. >www.claws-mail.org/plugin.php?plugin=vcalendar</ulink>
  350. </para>
  351. </listitem>
  352. </varlistentry>
  353. </variablelist>
  354. <para>
  355. If you're a developer, writing a plugin to extend Claws Mail's
  356. capabilities is probably the best and easiest solution. We will
  357. provide hosting to your code, and will be glad to answer your questions
  358. in the mailing-list or on the IRC channel,
  359. <literal>#claws</literal> on Freenode.
  360. </para>
  361. </section>
  362. <section id="plugins_network">
  363. <title>Network access from the plugins</title>
  364. <para>
  365. Some of the external plugins, for example RSSyl, vCalendar, Libravatar
  366. or Fancy, need Internet access for their operations (retrieving feeds in
  367. the case of RSSyl or vCalendar, and fetching images in the case of
  368. Libravatar or Fancy). These plugins use the Curl library. Hence, if your
  369. Internet access is restricted by a proxy, you will need to tell libCurl
  370. to use this proxy. This is done by setting an environment variable,
  371. <literal>http_proxy</literal>. For example,
  372. <literal>http_proxy=http://user:passwd@myproxy.example.com:8080</literal>
  373. will tell libCurl to connect to port 8080 of the machine
  374. myproxy.example.com, with the user <quote>user</quote> and password
  375. <quote>passwd</quote> to connect to the Internet.
  376. </para><para>
  377. You can either set this variable before starting Claws Mail by
  378. using, for example,
  379. <command>http_proxy=http://user:passwd@myproxy.example.com:8080
  380. claws-mail</command>, or you can set it in your
  381. <filename>~/.bashrc</filename> file (or your shell equivalent), by
  382. adding the following line<footnote><para>Other shells may have
  383. diferent syntaxes, check your shell's manual page.</para></footnote>:
  384. <command
  385. >export http_proxy=http://user:passwd@myproxy.example.com:8080</command>
  386. (you'll have to reconnect to have it taken into account).
  387. </para>
  388. </section>
  389. <section id="plugin_path_config">
  390. <title>Plugin path configuration</title>
  391. <para>
  392. By default, when loading a plugin, its full path is saved in
  393. <filename>~/.claws-mail/clawsrc</filename>.
  394. </para><para>
  395. As most users have only one copy of Claws Mail installed and always
  396. use the same installation method, this is not a problem.
  397. </para><para>
  398. However, if you have multiple copies of Claws Mail installed
  399. and want to share the same configuration among them, this may not
  400. work, particularly when using different versions of Claws Mail.
  401. </para><para>
  402. A second installed copy will try to load the plugins installed by
  403. the first and, if the versions differ, the plugins will be rejected.
  404. </para><para>
  405. In order to avoid this problem you can manually edit the plugins
  406. section in the <filename>clawsrc</filename> file, replacing the full
  407. path with just the plugin file name of those you want to load
  408. relative to the copy of Claws Mail being run.
  409. </para><para>
  410. In so doing, each copy of Claws Mail will try to load those plugins
  411. from its own plugin directory, rather than a fixed location.
  412. </para>
  413. </section>
  414. </section>