plugins.xml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419
  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 the <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="https://www.claws-mail.org/plugins.php"
  29. >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="https://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="https://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. >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/">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>Keyword Warner</term>
  157. <listitem>
  158. <para>
  159. Shows a warning when sending or queueing a message and a reference
  160. to one or more keywords is found in the message text.
  161. </para>
  162. </listitem>
  163. </varlistentry>
  164. <varlistentry>
  165. <term>Libravatar</term>
  166. <listitem>
  167. <para>
  168. Enables the display of avatar images associated with user profiles at
  169. libravatar.org or the user's avatar enabled domains.
  170. More information: <ulink
  171. url="https://www.claws-mail.org/plugin.php?plugin=libravatar"
  172. >www.claws-mail.org/plugin.php?plugin=libravatar</ulink>
  173. </para>
  174. </listitem>
  175. </varlistentry>
  176. <varlistentry>
  177. <term>Mail Archiver</term>
  178. <listitem>
  179. <para>
  180. Enables folders and subfolders to be archived in several different
  181. formats.
  182. </para>
  183. </listitem>
  184. </varlistentry>
  185. <varlistentry>
  186. <term>mailMBOX</term>
  187. <listitem>
  188. <para>
  189. Handles mailboxes in MBox format.
  190. </para>
  191. </listitem>
  192. </varlistentry>
  193. <varlistentry>
  194. <term>NewMail</term>
  195. <listitem>
  196. <para>
  197. Writes a message header summary to a log file, (Default:
  198. <filename>~/Mail/NewLog</filename>), on arrival of new mail
  199. <emphasis>after</emphasis> sorting.
  200. </para>
  201. </listitem>
  202. </varlistentry>
  203. <varlistentry>
  204. <term>Notification</term>
  205. <listitem>
  206. <para>
  207. Provides various ways to notify the user of new and unread email.
  208. More information: <ulink
  209. url="https://www.claws-mail.org/plugin.php?plugin=notification"
  210. >www.claws-mail.org/plugin.php?plugin=notification</ulink>
  211. </para>
  212. </listitem>
  213. </varlistentry>
  214. <varlistentry>
  215. <term>PDF Viewer</term>
  216. <listitem>
  217. <para>
  218. Allows rendering of PDF and PostScript attachments using the Poppler
  219. library and GhostScript external program.
  220. More information: <ulink
  221. url="https://www.claws-mail.org/plugin.php?plugin=pdf_viewer"
  222. >www.claws-mail.org/plugin.php?plugin=pdf_viewer</ulink>
  223. </para>
  224. </listitem>
  225. </varlistentry>
  226. <varlistentry>
  227. <term>Perl</term>
  228. <listitem>
  229. <para>
  230. Intended to extend the filtering possibilities of Claws Mail. It
  231. provides a Perl interface to Claws Mail' filtering mechanism,
  232. allowing the use of full Perl power in email filters.
  233. </para>
  234. </listitem>
  235. </varlistentry>
  236. <varlistentry>
  237. <term>PGP/Core, PGP/Inline and PGP/MIME</term>
  238. <listitem>
  239. <para>
  240. Handles PGP signed and/or encrypted mails. You can decrypt mails,
  241. verify signatures or sign and encrypt your own mails. Uses GnuPG/GPGME,
  242. <ulink url="https://www.gnupg.org/software/gpgme/"
  243. >www.gnupg.org/software/gpgme/</ulink>.
  244. More information: <ulink
  245. url="https://www.claws-mail.org/plugin.php?plugin=gpg"
  246. >www.claws-mail.org/plugin.php?plugin=gpg</ulink>
  247. </para>
  248. </listitem>
  249. </varlistentry>
  250. <varlistentry>
  251. <term>Python</term>
  252. <listitem>
  253. <para>
  254. This plugin provides Python integration features.
  255. More information: <ulink
  256. url="http://www.claws-mail.org/plugin.php?plugin=python"
  257. >www.claws-mail.org/plugin.php?plugin=python</ulink>
  258. </para>
  259. </listitem>
  260. </varlistentry>
  261. <varlistentry>
  262. <term>RSSyl</term>
  263. <listitem>
  264. <para>
  265. Allows you to read your favorite newsfeeds in Claws. RSS 1.0, 2.0 and
  266. Atom feeds are currently supported.
  267. More information: <ulink
  268. url="https://www.claws-mail.org/plugin.php?plugin=rssyl"
  269. >www.claws-mail.org/plugin.php?plugin=rssyl</ulink>
  270. </para>
  271. </listitem>
  272. </varlistentry>
  273. <varlistentry>
  274. <term>S/MIME</term>
  275. <listitem>
  276. <para>
  277. Handles S/MIME signed and/or encrypted mails. You can decrypt mails,
  278. verify signatures or sign and encrypt your own mails. Uses GnuPG/GPGME
  279. and GpgSM, <ulink url="ftp://ftp.gnupg.org/gcrypt/gpgme/"
  280. >ftp://ftp.gnupg.org/gcrypt/gpgme/</ulink>.
  281. </para>
  282. </listitem>
  283. </varlistentry>
  284. <varlistentry>
  285. <term>SpamAssassin</term>
  286. <listitem>
  287. <para>
  288. The SpamAssassin plugin comes with two major features:
  289. </para><para>
  290. The ability to scan incoming mail received from a POP, IMAP or LOCAL
  291. account using SpamAssassin. It can optionally delete mail identified
  292. as spam or save it to a designated folder. Mail scanning can be turned
  293. off, which is useful if your email is scanned on your server.
  294. </para><para>
  295. The ability for users to teach SpamAssassin to recognise spam or ham.
  296. You can train SpamAssassin by marking messages as spam or ham from the
  297. Message List contextual menu, or using the relevant toolbar button in
  298. the main window or the message window (see
  299. <quote>Configuration/Preferences/Toolbars</quote>). Messages
  300. marked as spam are optionally saved to a designated folder.
  301. </para><para>
  302. Plugin preferences can be found in
  303. <quote>Configuration/Preferences/Plugins/SpamAssassin</quote>.
  304. </para><para>
  305. SpamAssassin's advantage over Bogofilter is that it's not only a
  306. bayesian filter, but it also performs various local and network tests
  307. to determine spaminess.
  308. </para><para>
  309. SpamAssassin is available from <ulink
  310. url="http://spamassassin.apache.org/"
  311. >spamassassin.apache.org/</ulink>. Version 3.1.x or higher is
  312. required to use the learning feature in TCP mode.
  313. </para>
  314. </listitem>
  315. </varlistentry>
  316. <varlistentry>
  317. <term>SpamReport</term>
  318. <listitem>
  319. <para>
  320. This plugin reports spam to various places.
  321. Currently the sites <ulink url="http://spam-signal.fr"
  322. >spam-signal.fr</ulink> and <ulink url="http://spamcop.net"
  323. >spamcop.net</ulink> are supported, and the <ulink
  324. url="http://lists.debian.org">Debian lists (lists.debian.org)</ulink>
  325. spam nomination system.
  326. </para>
  327. </listitem>
  328. </varlistentry>
  329. <varlistentry>
  330. <term>TNEF parse</term>
  331. <listitem>
  332. <para>
  333. This plugin enables reading <literal>application/ms-tnef</literal> attachments.
  334. More information: <ulink
  335. url="https://www.claws-mail.org/plugin.php?plugin=tnef_parser"
  336. >www.claws-mail.org/plugin.php?plugin=tnef_parser</ulink>
  337. </para>
  338. </listitem>
  339. </varlistentry>
  340. <varlistentry>
  341. <term>vCalendar</term>
  342. <listitem>
  343. <para>
  344. Enables vCalendar message handling like that produced by Evolution or
  345. Outlook, and Webcal subscriptions.
  346. More information: <ulink
  347. url="https://www.claws-mail.org/plugin.php?plugin=vcalendar"
  348. >www.claws-mail.org/plugin.php?plugin=vcalendar</ulink>
  349. </para>
  350. </listitem>
  351. </varlistentry>
  352. </variablelist>
  353. <para>
  354. If you're a developer, writing a plugin to extend Claws Mail's
  355. capabilities is probably the best and easiest solution. We will
  356. provide hosting to your code, and will be glad to answer your questions
  357. in the mailing-list or on the IRC channel,
  358. <literal>#claws</literal> on <ulink url="https://libera.chat">Libera.chat</ulink>.
  359. </para>
  360. </section>
  361. <section id="plugins_network">
  362. <title>Network access from the plugins</title>
  363. <para>
  364. Some of the external plugins, for example RSSyl, vCalendar, Libravatar
  365. or Fancy, need Internet access for their operations (retrieving feeds in
  366. the case of RSSyl or vCalendar, and fetching images in the case of
  367. Libravatar or Fancy). These plugins use the Curl library. Hence, if your
  368. Internet access is restricted by a proxy, you will need to tell libCurl
  369. to use this proxy. This is done by setting an environment variable,
  370. <literal>http_proxy</literal>. For example,
  371. <literal>http_proxy=http://user:passwd@myproxy.example.com:8080</literal>
  372. will tell libCurl to connect to port 8080 of the machine
  373. myproxy.example.com, with the user <quote>user</quote> and password
  374. <quote>passwd</quote> to connect to the Internet.
  375. </para><para>
  376. You can either set this variable before starting Claws Mail by
  377. using, for example,
  378. <command>http_proxy=http://user:passwd@myproxy.example.com:8080
  379. claws-mail</command>, or you can set it in your
  380. <filename>~/.bashrc</filename> file (or your shell equivalent), by
  381. adding the following line<footnote><para>Other shells may have
  382. diferent syntaxes, check your shell's manual page.</para></footnote>:
  383. <command
  384. >export http_proxy=http://user:passwd@myproxy.example.com:8080</command>
  385. (you'll have to reconnect to have it taken into account).
  386. </para>
  387. </section>
  388. <section id="plugin_path_config">
  389. <title>Plugin path configuration</title>
  390. <para>
  391. By default, when loading a plugin, its full path is saved in
  392. <filename>~/.claws-mail/clawsrc</filename>.
  393. </para><para>
  394. As most users have only one copy of Claws Mail installed and always
  395. use the same installation method, this is not a problem.
  396. </para><para>
  397. However, if you have multiple copies of Claws Mail installed
  398. and want to share the same configuration among them, this may not
  399. work, particularly when using different versions of Claws Mail.
  400. </para><para>
  401. A second installed copy will try to load the plugins installed by
  402. the first and, if the versions differ, the plugins will be rejected.
  403. </para><para>
  404. In order to avoid this problem you can manually edit the plugins
  405. section in the <filename>clawsrc</filename> file, replacing the full
  406. path with just the plugin file name of those you want to load
  407. relative to the copy of Claws Mail being run.
  408. </para><para>
  409. In so doing, each copy of Claws Mail will try to load those plugins
  410. from its own plugin directory, rather than a fixed location.
  411. </para>
  412. </section>
  413. </section>