README.claws 31 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871
  1. README.claws
  2. ------------
  3. [last revision: 2005-05-09]
  4. Summary:
  5. 1. What is Sylpheed-Claws?
  6. 2. Plugins
  7. 3. Switching between Sylpheed Claws and Sylpheed
  8. 4. Actions
  9. 5. Icon Themes
  10. 6. Spell Checking
  11. 7. Quick Search
  12. 8. Custom toolbar
  13. 9. Partial downloading of POP3 mails
  14. 10. Other things that Claws does differently
  15. 11. Tools
  16. 12. How to contribute
  17. 13. How to request features
  18. 14. Installing Claws from CVS
  19. 15. Release History
  20. 16. Useful Links
  21. 1. What is Sylpheed-Claws?
  22. --------------------------
  23. Sylpheed-Claws is an extended version of Sylpheed, a light weight mail
  24. user agent for UNIX. Features in this branch may (or may not) end up in
  25. Sylpheed.
  26. Hiroyuki's ChangeLog is also included in the Claws branch distribution,
  27. so it should be easy to spot which features were merged with Sylpheed
  28. (and which features were not).
  29. For brevity Sylpheed-Claws is referred to as Claws, and Sylpheed as either
  30. Sylpheed or Main.
  31. 2. Plugins
  32. ----------
  33. All plugins, except SpamAssassin, are built automatically
  34. if the required libraries are present.
  35. Plugins are installed in $PREFIX/lib/sylpheed/plugins/
  36. and have a suffix of '.so'
  37. To load a plugin go to '/Configuration/Plugins' and click
  38. the 'Load Plugin' button.
  39. Select the plugin that you want and click 'OK'
  40. o Clam AntiVirus
  41. Enables the scanning of message attachments in mail
  42. received from a POP, IMAP or LOCAL account using Clam
  43. AntiVirus. It can optionally delete the mail or save it
  44. to a designated folder. Preferences can be found in
  45. '/Configuration/Preferences/Filtering/Clam AntiVirus'.
  46. Clam AntiVirus is available from http://clamav.sourceforge.net/
  47. o Dillo HTML Viewer
  48. Enables the viewing of html messages using the Dillo web
  49. browser, version 0.7.0 or newer. It uses Dillo's --local
  50. option by default for safe browsing. Preferences can be
  51. found in '/Configuration/Preferences/Message View/Dillo Browser'.
  52. Dillo is available from http://www.dillo.org/
  53. o MathML Viewer
  54. Enables the viewing of attachments that have the
  55. Content-Type 'text/mathml' using the GtkMathView widget
  56. which is available from
  57. http://helm.cs.unibo.it/mml-widget/
  58. o PGP/MIME
  59. Handles PGP/MIME signed and/or encrypted mails. You can
  60. decrypt mails, verify signatures or sign and encrypt your
  61. own mails.Uses GnuPG/GPGME, <ftp://ftp.gnupg.org/gcrypt/gpgme/>
  62. o SpamAssassin
  63. Enables the scanning of incoming mail received from a POP,
  64. IMAP or LOCAL account using SpamAssassin. It can optionally
  65. delete mail identified as spam or save it to a designated
  66. folder. Preferences can be found in '/Configuration/
  67. Preferences/Filtering/SpamAssassin'.
  68. SpamAssassin is available from http://spamassassin.org
  69. Configure option:
  70. --enable-spamassassin-plugin
  71. o Trayicon
  72. Places an icon in the system tray that indicates whether
  73. you have any new mail. A tooltip also shows the current
  74. new, unread and total number of messages
  75. More plugins can be found here:
  76. http://sylpheed-claws.sourceforge.net/plugins.php
  77. 3. Switching between Sylpheed Claws and Sylpheed
  78. ------------------------------------------------
  79. From Sylpheed to Sylpheed Claws
  80. -------------------------------
  81. From the user perspective Claws is just a fancy Sylpheed, so it uses the
  82. same Sylpheed setting files located in ~/.sylpheed. However, you may wish
  83. to use the ./configure option --with-config-dir=RCDIR, so that you can
  84. preserve your Sylpheed settings.
  85. It's always a good idea to back up all files in ~/.sylpheed in case
  86. you want to switch back to Sylpheed and didn't use the --with-config-dir
  87. option. (You don't have to backup the directories.)
  88. If you use a new configuration directory you will need to manually copy
  89. all of your address book files, ~/.sylpheed/addrbook*
  90. There are some things that frequently come up when switching to Claws:
  91. * What happened to my filter rules?
  92. Claws uses a new filtering system. Your old Sylpheed filter rules will not
  93. be used. In subdirectory tools/ of the distribution there is a Perl script
  94. called filter_conv.pl which converts old filter rules to the claws
  95. filtering system, see tools/README for details. This currently only supports
  96. conversion from Sylpheed's old filtering system, < 0.9.99.
  97. * What happened to the compose email and compose news buttons?
  98. There's a composite button for both composing mail and news. It is toggled
  99. between composing mail and news automatically when a mail or news folder
  100. is selected.
  101. * And to the Preferences and Execute buttons?
  102. Sorry, they're not there.
  103. From Sylpheed Claws to Sylpheed
  104. -------------------------------
  105. Moving from Claws to Sylpheed is also simple. Sylpheed should neglect the things
  106. Claws put in the settings files. This also means that the old rules will work
  107. again.
  108. If you want to switch back to Claws at a later time, and are using the same config
  109. directory for both, make sure you back up at least ~/.sylpheed/matcherrc (the
  110. Claws filtering rules), and ~/.sylpheed/sylpheedrc (which may have some claws
  111. specific settings).
  112. When switching back to Sylpheed you will not lose messages or message flags (color
  113. labels, read / unread status of messages).
  114. 4. Actions
  115. ----------
  116. The "actions" feature is a convenient way for the user to launch external
  117. commands to process a complete message file including headers and body or
  118. just one of its parts. It allows also the use of an external command to
  119. filter the whole text or just a selected part in the message window or in
  120. the compose window. This is a generic tool that allows to do any uncommon
  121. actions on the messages, and thus extends the possibilities of Sylpheed.
  122. For example, Sylpheed does not include the rot13 cyphering algorithm
  123. popular in some newsgroups. It does not support natively armored
  124. encryption or clear signing. It does not support uuencoded messages. As
  125. all these features can be handled by external programs, the actions
  126. provide a convenient way to use them from the menu bar.
  127. a. Usage
  128. --------
  129. To create a new action, go to Configuration -> Actions.... The "Action
  130. Creation" dialog offers to enter the Menu name that will trigger the
  131. command. The created menu will be found in the Tools -> Actions submenu.
  132. By inserting a slash / in the menu name, you create a submenu.
  133. The command is entered in the Command line entry. Note that Sylpheed
  134. stores every single email in a separate file. This allows to use the
  135. following syntax for the command:
  136. * %f denotes the file name of the selected message. If you selected more
  137. than one, then the command will be launched for each message with
  138. the appropriate file name
  139. * %F denotes the list of the file names of the selected message. If only
  140. one message is selected, this amounts to %f, but if more messages
  141. are selected, then the command will be launched only once with the
  142. list of the file names. (You can use both %f and %F in one command:
  143. then the command will be launched for each selected message with
  144. the name of this message and with the list of all selected
  145. messages. I did not find a practical example for this.)
  146. * %p denotes the current selected message part of a multipart message.
  147. The part is decoded accordingly. If the message is not a multipart
  148. message, it denotes the message body.
  149. * Prepending >: this will allow you to send to the command's standard
  150. input a text that you will enter in a dialog window.
  151. * Prepending *: this will allow you to send to the command's standard
  152. input a text that you will enter in a dialog window. But in
  153. contrast to prepending >, the entered text is hidden (useful when
  154. entering passwords).
  155. * Appending an ampersand &: this will run the command asynchronously.
  156. That means "fire and forget". Sylpheed won't wait for the command
  157. to finish, nor will it catch its output or its error messages.
  158. * Prepending the vertical bar | (pipe-in): this will send the current
  159. displayed text or the current selected text from the message view
  160. or the compose window to the command standard input. The command
  161. will silently fail if more than one message is selected.
  162. * Appending the vertical bar | (pipe-out): this will replace the current
  163. displayed text or the current selected text from the message window
  164. or the compose window by the command standard output. The command
  165. will silently fail if more than one message is selected.
  166. Note: It is not possible to use actions containing %f, %F or %p from the
  167. compose window.
  168. When a command is run, and unless it is run asynchronously, Sylpheed will
  169. be insensitive to any interaction and it will wait for the command to
  170. finish. If the command takes too long (5 seconds), it will popup a dialog
  171. window allowing to stop it. This dialog will also be displayed as soon as
  172. the command has some output: error messages or even its standard output
  173. when the command is not a "pipe-out" command. When multiple commands are
  174. being run, they are run in parallel and each command output is separated
  175. from the outputs of the others.
  176. a. Examples
  177. -----------
  178. Here are some examples that are listed in the same syntax as used for
  179. storing the actions list. You can copy and past the definition in your
  180. ~/.sylpheed/actionsrc file (exit Sylpheed before). The syntax is very
  181. simple: one line per action, each action contains the menu name and the
  182. command line separated by a colon and a space ": "
  183. Purpose: rot13 cyphering
  184. Definition: Rot13: |tr a-zA-Z n-za-mN-ZA-M|
  185. Details: This will apply the rot13 cyphering algorithm to the
  186. (selected) text in the message/compose view.
  187. Purpose: Decoding uuencoded messages
  188. Definition: UUdeview: xdeview %F&
  189. Details: xdeview comes with uudeview. If an encoded file is split in
  190. multiple messages, just select them all and run the command.
  191. Purpose: Display uuencoded image
  192. Definition: Display uuencoded: uudec %f&
  193. Details: Displays uuencoded files. The uudec[1] script can be found in
  194. the 'tools' directory of the distribution package.
  195. Purpose: Alter messages
  196. Definition: Edit message: gvim -f %F
  197. Details: Allows editing of any received message. Can be used to remove
  198. unneeded message parts, etc.
  199. Purpose: Pretty format
  200. Definition: Par: |par 72Tbgjqw74bEe B=._A_a 72bg|
  201. Details: par is a utility that can pretty format any text. It does a
  202. very good job in indenting quoted messages, and justifying
  203. text. Used when composing a message
  204. Purpose: Browse
  205. Definition: Part/Dillo: dillo %p&
  206. Details: Browse the selected message part in Dillo.
  207. Purpose: Clear Sign
  208. Definition: GnuPG/Clear Sign: |gpg-sign-syl|
  209. Details: Clear sign a message. The gpg-sign-syl[2] script is responsible
  210. for asking the passphrase and for running gnupg.
  211. Purpose: Verify Clear Signed
  212. Definition: GnuPG/Verify: |gpg --no-tty --verify
  213. Details: Verify clear signed messages. The result is displayed in the
  214. actions output dialog.
  215. Purpose: Decrypt ASCII Armored
  216. Definition: GnuPG/Decrypt: *gpg --no-tty --command-fd 0 --passphrase-fd 0 --decrypt %f|
  217. Details: Decrypt ASCII armored messages. The passphrase is entered
  218. into the opened action's input dialog.
  219. [1] The uudec script can be found in the 'tools' directory of the
  220. distribution package. It needs uudecode and ImageMagick's display. The
  221. latter can be replaced by any image viewer that can get input from
  222. standard input. The script could also be modified to use temporary files
  223. instead of standard input.
  224. [2] The gpg-sign-syl script can be found in the 'tools' directory of the
  225. distribution package.
  226. 5. Icon Themes
  227. --------------
  228. Claws has support for different icon sets. Several icon sets can be
  229. downloaded from http://sylpheed-claws.sourceforge.net/themes.php
  230. You will need to create a directory called 'themes' in your config
  231. directory, unpack them into this directory, and then use the interface
  232. to select them, /Configuration/Preferences/Display/Themes
  233. This interface can also be used to install new themes.
  234. 6. Spell Checking
  235. -----------------
  236. a. Requirements
  237. b. Configuration and installation
  238. c. Usage
  239. d. Known problems
  240. a. Requirements
  241. ---------------
  242. The spell checker in Sylpheed-Claws requires the GNU/aspell library
  243. (http://www.gnu.org/software/aspell), version 0.50 or newer.
  244. You also need the dictionaries. Check GNU/aspell home page for how
  245. to download and install them.
  246. NB: The old dictionaries used by the old aspell will not work.
  247. b. Configuring Claws
  248. --------------------
  249. Spell checking is enabled if you configure Claws appropriately. Add
  250. the option '--enable-aspell' when configuring, e.g.:
  251. ./configure --enable-aspell
  252. The configure script needs the 'aspell' executable to be in your path.
  253. If it is in unusual places, use '--with-aspell-prefix' to tell the path of
  254. the aspell executable. E.g., if aspell's full path is
  255. /foo/bar/bin/aspell, then use:
  256. ./configure --enable-aspell --with-aspell-prefix=/foo/bar
  257. The '--with-aspell-prefix=PREFIX' option will let the configure
  258. script search for includes and libraries in PREFIX/include and PREFIX/lib.
  259. You can also specify manually the includes and libraries path by using
  260. either following options:
  261. --with-aspell-includes=/foo/bar/include
  262. and/or
  263. --with-aspell-libs=/rab/oof/lib
  264. as appropriate.
  265. The configure script summarizes the options compiled in. Check that
  266. it lists 'GNU/aspell = yes'.
  267. Then proceed as usual, with 'make' and 'make install'.
  268. c. Usage
  269. --------
  270. After successful compiling, you need to tell Sylpheed where your
  271. dictionaries reside. The configure script should have found it,
  272. but in case it did not, run 'aspell config dict-dir' on the
  273. shell to get the path to the dictionaries.
  274. Then run Sylpheed and go to /Configuration/Preferences/Compose/Spell Checker.
  275. Check the box 'Enable spell checker' and use the file selector ('...' button)
  276. to select the path where the dictionaries reside. Within the file selector,
  277. go to that directory and select *any* file in the file lists. Click OK.
  278. Then, you should be able to select your default dictionary.
  279. When composing, misspelled words are highlighted. Click on any
  280. highlighted word with the right mouse button to get a list of
  281. suggestions. The first entry of the menu just displays the unknown
  282. word. Selecting 'Accept in this session' (or hitting MOD1-Space,
  283. where MOD1 is usually the ALT key) will ignore this word and accept
  284. it in this message. Selecting the next entry, "Add to dictionary", which
  285. is bound to MOD1-Enter combination, will add the unknown word to your
  286. personal dictionary to learn it. The next entries are the suggested words.
  287. The first 15 suggestions can be accessed by typing one of the first letters
  288. of Latin alphabet (if this does not suit your language, please send
  289. a mail to melvin.hadasht@free.fr). Aspell has a 'learn from mistake'
  290. function that can be used by pressing the MOD1 key and selecting the
  291. suggestion (with the keyboard or with the mouse). See GNU/aspell manual
  292. §6.3 for an explanation of this feature (also called 'replacement storing').
  293. If you click with the right mouse button everywhere else, or if you
  294. shift-right-click even on a misspelled word, you get the
  295. configuration menu. 'Check all' highlights all misspelled words.
  296. With this menu, you can also change the dictionary while editing.
  297. Finally, you can change the suggestion mode, and the learn from
  298. misktakes feature.
  299. Spell checking can also be done using keyboard shortcuts. In the
  300. 'Edit' menu of the compose window, there are two menus 'Check backwards
  301. misspelled word' and 'Forward to next misspelled word'. Add to them
  302. appropriate keyboard shortcuts. 'Check backwards misspelled word'
  303. checks backwards from cursor position for the first misspelled word.
  304. If it finds one, it displays the suggestions lists which can be handled
  305. with the keyboard as described before. When the suggestion menu is
  306. closed, the cursor returns to its original position to be able to
  307. continue editing. The 'Forward to next misspelled word' do the same
  308. thing in the other direction but moves the cursor at the end of the
  309. misspelled word. This way, you can spell check easily a whole message
  310. starting from its beginning and using the 'Forward to next misspelled
  311. word' keyboard short cut.
  312. d. Known problems
  313. -----------------
  314. No known problems as the time of this writing (0.8.2claws3).
  315. 7. Quick Search with extended search
  316. ------------------------------------
  317. Quick Search, with its powerful Extended search function,
  318. enables searching through folder's messages.
  319. Extended Search allows one to define criteria that messages must
  320. have in order to match and be displayed in the summary view pane.
  321. Search types titled From, Subject and To are self explanatory.
  322. Search type extended allows one to use Sylpheed's powerful
  323. filtering engine to select messages. Examples:
  324. from regexpcase "foo"
  325. subject regexp "Bug" & to regexp "sylpheed-claws"
  326. Additionally, it is possible to use simpler yet equally
  327. powerfull patterns for message selections. Mutt users will
  328. immediately recognise most of the available patterns:
  329. Pattern Parameter Selects
  330. ----------------------------------------------------
  331. a all messages
  332. ag # messages whose age is greater than #
  333. al # messages whose age is lower than #
  334. b S messages which contain S in the message body
  335. B S messages which contain S in the whole message
  336. c S messages carbon-copied to S
  337. C S message is either to: or cc: to S
  338. D deleted messages
  339. e S messages which contain S in the Sender field
  340. E S true if execute "S" succeeds
  341. f S messages originating from user S
  342. F forwarded messages
  343. h S messages which contain header S
  344. i S messages which contain S in Message-Id header
  345. I S messages which contain S in inreplyto header
  346. L locked messages
  347. n S messages which are in newsgroup S
  348. N new messages
  349. O old messages
  350. r messages which have been replied to
  351. R read messages
  352. s S messages which contain S in subject
  353. se # messages whose score is equal to #
  354. sg # messages whose score is greater than #
  355. sl # messages whose score is lower than #
  356. Se # messages whose size is equal to #
  357. Sg # messages whose size is greater than #
  358. Ss # messages whose size is smaller than #
  359. t S messages which have been sent to S
  360. T marked messages
  361. U unread messages
  362. x S messages which contain S in References header
  363. y S messages which contain S in X-Label header
  364. # means number
  365. S means regexp string
  366. It is possible to use logical operators AND (&), OR (|) and
  367. NOT (! or ~). Case sensitive search is achieved with %.
  368. Examples:
  369. T marked messages
  370. U unread messages
  371. f "john beavis" messages from john beavis
  372. %f "John Beavis" messages from John Beavis (case sensitive)
  373. ~s foo messages which do not have foo in the subject
  374. f foo & ~s bar messages from foo that do not have bar in thesubject
  375. 8. Custom toolbar
  376. -----------------
  377. /Configuration/Preferences/Customize Toolbars lets you define the
  378. toolbar you want. The configuration dialog enables you to set an icon,
  379. an appropriate text, and map an action to it. Actions to choose
  380. from are predefined. You can also have your "Sylpheed Actions" (refer
  381. to "Actions" above) on your toolbar.
  382. Example:
  383. * Configuration->Actions
  384. - add an entry "Dillo: dillo %p&"
  385. * Configuration->Custom toolbar
  386. - select Sylpheed Actions Feature
  387. - select "Dillo: dillo %p&" from drop down list
  388. - choose an icon and click ok
  389. 9. Partial downloading of POP3 mails
  390. ------------------------------------
  391. Messages over the configured size limit, (/[Account preferences]/
  392. Receive/Message size limit), will be partially retrieved. These
  393. messages will have a Notice View displayed (above the Message View),
  394. informing of the partially retrieved state and the total size of the
  395. message. The Notice View will also contain two buttons, 'Mark for
  396. download' and 'Mark for deletion'. If the user clicks 'Mark for
  397. download', the message will be downloaded in full at the next message
  398. retrieval, (and the partial one deleted); if the user checks 'Mark for
  399. deletion' it will be removed from the server after the normal delay
  400. as specified in the POP3 account's 'Receive' preferences.
  401. If a user moves a partially retrieved message to the Trash folder
  402. it will be deleted on the server at the next retrieval after the
  403. Trash folder has been emptied.
  404. 10. Other things that Claws does differently
  405. --------------------------------------------
  406. Claws does a lot of things differently. Here is a quick run-down of
  407. just a few of them:
  408. * auto address replacement in summary view
  409. This matches a plain email address with a person in the address book.
  410. This feature is enabled in /Configuration/Preferences/Common/Display
  411. 'Display sender using addressbook'
  412. * manual selection of MIME types for attachments
  413. You can change the MIME type of an attachment by right-clicking in the
  414. attachment list, selecting Property in the menu. The MIME type list
  415. is a combo box with the known MIME types.
  416. * sharing mail folders
  417. You can also share or use shared mail folders. Right-click a folder and
  418. select Properties. Change the Folder chmod setting.
  419. * simplify subject string
  420. It is possible to remove parts of subject string from the displayed
  421. subject line.
  422. Example:
  423. True Subject: [Sylpheed-claws-users] This is a test
  424. Displayed Subject: This is a test
  425. Regexp: \[Sylpheed-claws-(devel|users)\]
  426. This is a per folder property. Right click on a folder and select
  427. Properties, enable Simplify Subject RegExp check box.
  428. * new cache
  429. New cache is a new data cache structure for sylpheed, that will
  430. solve many of the problems sylpheed currently has with updates to
  431. flags. But you will also notice a large speed gain when you open
  432. these folders.
  433. New cache uses two new configuration parameters that can be
  434. adjusted in ~/[RCDIR]/sylpheedrc (no gui for them available yet).
  435. cache_max_mem_usage (default: 4096)
  436. the maximum kB of memory sylpheed should use.
  437. It will try to keep the memory usage below this
  438. value, but it will always use the assigned
  439. amount of memory for speed gain.
  440. cache_min_keep_time (default: 15)
  441. the minimum time in minutes sylpheed will keep
  442. the folder cache in memory. If a cache is more
  443. recent than this time it will not be freed even
  444. if the memory usage is above the maximum. You
  445. should probably set this value higher than your
  446. mail check interval. Otherwise the cache will
  447. always be freed between checks even if the folder
  448. is accessed on every check, which will cause much
  449. disk IO.
  450. The check if memory can be freed is currently done after the
  451. active folder has been changed or whenever a new cache is read,
  452. i.e. triggered by mail incorporation.
  453. New mails in MH folders are not detected automatically like before,
  454. when you enter the folder. You have to update the folder manually,
  455. or activate the auto update setting in the options.
  456. * SMTP Message Size Declaration
  457. If the server supports it, oversize messages will not be sent and
  458. the maximum allowed message size will be displayed in the log,
  459. (/Tools/Log window/).
  460. * Reply-finder
  461. Clicking on the replied icon in the Status (S) column of the summary
  462. view will attempt to find and display your reply that is stored in
  463. your Outbox.
  464. * pop before smtp authentication
  465. * Automatic saving of message when composing
  466. * signature in the message view can be coloured
  467. * built-in gdb crash handler
  468. * extra Font configuration
  469. * message scoring
  470. * 'hide read messages' feature
  471. * Request Return-Receipt
  472. * ability to change folder order
  473. * 'ignore thread' marking
  474. * message priority setting
  475. * Automatic message drafting and cache saving on kill
  476. * SSL certificate management and checking
  477. * Indication of unread answers to marked mails:
  478. '(!)' is appended to the folder name when a marked message
  479. has a response
  480. * address auto-completion includes a dynamic LDAP search
  481. * address auro-completion works on nicknames and aliases
  482. * Password encryption in config files is implemented using
  483. unix encrypt and setkey functions.
  484. This is not an exhaustive list.
  485. 11. Tools
  486. ---------
  487. You will find all of these tools in the 'tools' directory:
  488. acroread2sylpheed.pl
  489. send PDFs from Adobe Reader 7
  490. calypso_convert.pl
  491. import mbox files exported by calypso
  492. convert_mbox.pl
  493. convert mbox format to MH format
  494. eud2gc.py
  495. convert a Eudora (v.3?) addressbook to vCard
  496. (GnomeCard) format
  497. filter_conv.pl
  498. convert sylpheed main's filter rules, (< 0.9.99),
  499. into Claws' filtering format
  500. freshmeat_search.pl
  501. Actions script to lookup the selected text on
  502. Freshmeat www.freshmeat.net using the configured
  503. browser
  504. gif2xface.pl
  505. convert a gif file to an xface
  506. google_msgid.pl
  507. Actions script to lookup selected message-id on
  508. google using mozilla.
  509. google_search.pl
  510. Actions script to lookup up the selected text on
  511. google using the configured browser
  512. gpg-sign-syl
  513. GnuPG cleartext-signing script for use with
  514. Actions
  515. kmail2sylpheed.pl
  516. convert a Kmail addressbook to a Sylpheed
  517. addressbook
  518. kmail2sylpheed_v2.pl
  519. new version of the address book conversion script
  520. for newer versions of Kmail/Kaddressbook
  521. maildir2sylpheed.pl
  522. convert a maildir format mailbox into MH format
  523. multiwebsearch.pl
  524. search any searchable website for the selected text
  525. nautilus2sylpheed.sh
  526. enables sending files from the Nautilus file manager
  527. to Sylpheed
  528. OOo2sylpheed.pl
  529. enable OpenOffice to send documents through
  530. sylpheed
  531. outlook2sylpheed.pl
  532. convert an Outlook contacts list to a Sylpheed
  533. addressbook
  534. sylpheed-switcher
  535. enable quick-switching between claws and main
  536. in a non-destructive way
  537. sylprint.pl
  538. process a Sylpheed mail and print it using enscript
  539. if available or lpr if not
  540. tb2sylpheed
  541. convert an addressbook exported from The Bat! into
  542. a Sylpheed addressbook
  543. textviewer.sh
  544. attempt to view an attachment as plain text
  545. update-po
  546. translators' tool that eases the creation of
  547. *.po files
  548. uudec
  549. decode UUencoded mails, for use with Actions
  550. kdeservicemenu/*
  551. Service Menus for Konqueror to allow attaching files and
  552. compressing/attaching files/directories to a new Compose
  553. window
  554. 12. How to contribute
  555. ---------------------
  556. You are encourged to send patches via the Sylpheed-Claws sourceforge
  557. project's Patch Tracker.
  558. http://sourceforge.net/tracker/?atid=384600&group_id=25528&func=browse
  559. If that's too troublesome, either contact Paul Mangan
  560. <twb@users.sourceforge.net> or consider posting to the
  561. Sylpheed-Claws-users mailing list.
  562. http://lists.sourceforge.net/lists/listinfo/sylpheed-claws-users
  563. Bugs can be reported with Claws' bugzilla at:
  564. http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi
  565. Of course, you can also post to the Sylpheed-Claws-users mailing list.
  566. Also, we really try to incorporate good contributions, but sometimes we
  567. don't have enough time. If the contribution is really big, or requires
  568. a long time to stabilise, send a mail to Paul Mangan
  569. <twb@users.sourceforge.net>. We can probably arrange access to the
  570. Sylpheed-Claws CVS tree.
  571. 13. How to request features
  572. ---------------------------
  573. Ask around in Sylpheed-Claws-users ML. Note that some developers may
  574. have already thought about your feature, may,perhaps, be implementing it,
  575. or the feature was already discussed and rejected for whatever reason.
  576. You might want to go ahead and hack a patch for it. (That would be very
  577. cool!) Another possibility is to use the Feature Request Tracker at the
  578. sourceforge project.
  579. http://sourceforge.net/tracker/?group_id=25528&atid=384601
  580. 14. Installing Claws from CVS
  581. -----------------------------
  582. a. Downloading
  583. --------------
  584. To download the latest cvs cd to the directory where you wish to download
  585. to and type the following information:
  586. cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/sylpheed-claws login
  587. When prompted for a password press the RETURN key.
  588. After anonymously logging in:
  589. cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/sylpheed-claws co -r gtk2 sylpheed-claws
  590. b. Installing
  591. -------------
  592. To compile and install use the following commands:
  593. ./autogen.sh [add configure options as required]
  594. make
  595. make install [as root]
  596. You will need a full set of development tools installed to be able to run
  597. autogen.sh. See also ac/README.
  598. 15. Release History
  599. -------------------
  600. GTK 2 Version
  601. -------------
  602. 2005-05-09 1.9.9
  603. 2005-03-18 1.9.6
  604. GTK 1 Version
  605. -------------
  606. 2005-05-09 1.0.4a
  607. 2005-03-24 1.0.4
  608. 2005-03-10 1.0.3
  609. 2005-02-08 1.0.1
  610. 2005-01-17 1.0.0
  611. 2004-12-06 0.9.13
  612. 2004-09-27 0.9.12b
  613. 2004-08-23 0.9.12a
  614. 2004-06-28 0.9.12
  615. 2004-05-31 0.9.11claws
  616. 2004-03-08 0.9.10claws
  617. 2004-02-06 0.9.9claws
  618. 2003-12-19 0.9.8claws
  619. 2003-11-26 0.9.7claws
  620. 2003-10-02 0.9.6claws
  621. 2003-09-10 0.9.5claws
  622. 2003-08-04 0.9.4claws
  623. 2003-07-12 0.9.3claws
  624. 2003-05-24 0.9.0claws
  625. 2003-03-12 0.8.11claws
  626. 2003-02-12 0.8.10claws
  627. 2003-01-24 0.8.9claws
  628. 2002-12-26 0.8.8claws
  629. 2002-12-23 0.8.7claws
  630. 2002-11-25 0.8.6claws
  631. 2002-10-07 0.8.5claws
  632. 2002-09-22 0.8.3claws
  633. 2002-08-28 0.8.2claws
  634. 2002-07-30 0.8.1claws
  635. 2002-07-23 0.8.0claws
  636. 2002-06-15 0.7.8claws
  637. 2002-05-18 0.7.6claws
  638. 2002-04-28 0.7.5claws
  639. 2002-03-11 0.7.4claws
  640. 2002-02-19 0.7.2claws
  641. 2002-02-14 0.7.1claws
  642. 2002-01-14 0.7.0claws
  643. 2001-12-16 0.6.6claws
  644. 2001-10-16 0.6.5claws8
  645. 2001-09-30 0.6.2claws
  646. 2001-08-14 0.6.1claws
  647. 2001-07-13 0.5.1claws
  648. 2001-07-01 0.5.0claws3
  649. 2001-06-16 0.4.99claws
  650. 2001-05-29 0.4.99claws3
  651. 2001-05-11 0.4.67claws1
  652. 16. Useful links
  653. ----------------
  654. Homepage
  655. http://sylpheed-claws.sourceforge.net/
  656. Sylpheed-Claws for Windows homepage
  657. http://sylpheed-claws.sourceforge.net/win32/
  658. FAQ
  659. http://sylpheed-claws.sourceforge.net/phpwiki/
  660. Project page
  661. http://sourceforge.net/projects/sylpheed-claws/
  662. Downloads
  663. http://sourceforge.net/project/showfiles.php?group_id=25528
  664. External Plugins
  665. http://sylpheed-claws.sourceforge.net/plugins.php
  666. Icon Themes
  667. http://sylpheed-claws.sourceforge.net/themes.php
  668. CVS webview
  669. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/sylpheed-claws/sylpheed-claws/?only_with_tag=gtk2
  670. Users Mailing List subscription page
  671. http://lists.sourceforge.net/lists/listinfo/sylpheed-claws-users/
  672. Users Mailing List archive
  673. http://sourceforge.net/mailarchive/forum.php?forum=sylpheed-claws-users/
  674. Commits Announcement List subscription page
  675. http://lists.sourceforge.net/lists/listinfo/sylpheed-claws-commits/
  676. Commits Announcement List archive
  677. http://sourceforge.net/mailarchive/forum.php?forum=sylpheed-claws-commits/
  678. Bug Tracker
  679. http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi
  680. Feature Request Tracker
  681. http://sourceforge.net/tracker/?group_id=25528&atid=384601
  682. Patch Tracker
  683. http://sourceforge.net/tracker/?group_id=25528&atid=384600
  684. Internationalisation Status
  685. http://sylpheed-claws.sourceforge.net/i18n.php