Grouped filters, actions and templates into chapter 13, updated the filters description (to match Sylpheed v0.8.10), added the actions section (from Melvin's page), started the template section (not yet written).

1 files changed, 672 insertions, 11 deletions

diff --git a/manual/en/syl_013.sgml b/manual/en/syl_013.sgml
index bdbe411..353c00d 100644
--- a/manual/en/syl_013.sgml
+++ b/manual/en/syl_013.sgml
@@ -1,23 +1,684 @@
-<sect>Handling MIME types
+<sect>Filters, actions and templates
+<p>
+Sylpheed offers three powerfull tools to help you automatically
+and efficently manage you mails. These tools are:
 
-<sect1>How Sylpheed checks for Mime types<p>
+<itemize>
+	<item>
+		The <it>filters</it>, that let you sort you incoming messages and move
+		them into your folders based on their sender, their content,
+		using regular expressions.
+	</item>
+	<item>
+		The <it>actions</it> feature is a convenient way for the user to launch 
+		external commands to process a complete message file including 
+		headers and body or just one of its parts.
+		It allows also the use of an external command to filter the whole 
+		text or just a selected part in the message window or in the 
+		compose window.
+	</item>
+	<item>
+		The <it>templates</it> that let you pre-define complete messages
+		leaving placeholders in the text to be filled at composition time.
+	</item>
+</itemize>
 
-(Thanks to Adriaan Penning for writing this!)<p>
 
-Two files, mime.types and mailcap, are involved in determining the mime type of an attachment, and the application associated with that mime type. The mime.types file is used to determine the mimetype of attachments you add when composing a message. The mime.types file consists of lines like:<p>
 
-application/pdf                    pdf<p>
+<sect1>Filters
+<p>
+Written by Nick Selby (sylpheed@nickselby.com)
+<p>
+Sylpheed provides powerful filters to allow users to automatically 
+pre-sort incoming mail based on a set of rules that the user defines. 
+As a most simple example, let's say you work at the Acme Grommet Company, 
+and you want all e-mail from your co-workers to be placed in one mailbox. 
+To accomplish this, you would set up a filter that would place all mail 
+whose "From" header includes the phrase "acmegrommet.com" into a specific 
+mailbox.
+<p>
+Sylpheed allows you much more control than just that simple setup; 
+you may create filters based on several variables, including an 
+"If this AND that" or "If the message contains this OR does NOT contain that"
+etc. It's very cool.
 
-Sylpheed looks for this file in SYSCONFDIR (determined at compile time), /etc/ and $HOME/.sylpheed/ 
+<sect2>Finding The Filter Setting Dialog
+<p>
+The filter settings dialog is located in the <it>Configuration</it> menu, 
+under the title "Filter Setting" or from the <it>Tools</it> menu, under in
+the <it>Create filter rules</it> sub menu. You may also use establish a 
+keyboard shortcut (see Keyboard Shortcuts).
 
-If this file doesn't exist or has the wrong format, every attachment will have 	`application/octet-stream' as it's mime type, so the recipients mail client may not know what application to use to view the attachment.
+<figure loc="here">
+<ph vspace="1cm">
+<img src="snapshots/filters.png">
+</figure>
 
-To change the default application that sylpheed uses to view an attachment that	somebody mailed you, look for a mailcap file like /etc/mailcap or $HOME/.mailcap
+</sect2>
+<sect2>Setting Up Filters<p>
+Operator(s) and Processing instructions combine to create a Filter Rule.
 
-For example, you can add a line like this in $HOME/.mailcap if you want to view pdf	files with xpdf:<p>
+* Operators
+The dialog's first setting option establishes the Operator, the variable 
+that will tell the filter what specific text to look for to trigger a 
+filter. Each Filter Rule may have up to two operator sets.
+<p>
+Each Operator variable contains three sections: <it>Header</it>, 
+<it>Keyword</it> and <it>Predicate</it>.
+<p>
+Header is a drop-down box which defines in which message header 
+Sylpheed's filter will search. Choices range from <it>Subject</it> 
+to <it>X-Mailer</it>. 
 
-application/pdf ; xpdf %s
+<it>Keyword</it> is a a text box in which you may enter the text 
+for which the filter will search. 
 
+Predicate allows you to choose to filter based on whether the operator 
+contains, or does not contain, the text you enter in the Keyword field.
+<p>
+Example: Create an Operator in which the X-Mailer field of an incoming 
+message contains the word 'Eudora'.
+
+<itemize>
+	<item>
+		Step 1. Under the <it>Header</it> drop-down box, select 
+		<it>X-Mailer</it>.
+	</item>
+	<item>
+		Step 2. In the <it>Keyword</it> text box, type 'eudora' 
+		(case insensitive)
+	</item>
+	<item>
+		Step 3. Determine appropriate Predicate setting. Default 
+		is <it>Contains</it>.
+	</item>
+</itemize>
+
+The second Operator setting, which is set identically to the 
+first, also allows the user to select an AND/OR setting 
+declaring the relationship between the two operators. 
+<p>
+Example: Create an Operator set which will process mail with 
+a <it>From</it> header of bob@acmegrommet.com AND a subject
+of "2001 Spring Grommet Collection"
+
+<itemize>
+	<item>
+		Step 1. Under the first Operator set's Header drop-down 
+		box, select <it>From</it>.
+	</item>
+	<item>
+		Step 2. In the <it>Keyword</it> text box, type 
+		'bob@acmegrommet.com' (case insensitive).
+	</item>
+	<item>
+		Step 3. Leave <it>Predicate</it> setting on default, 
+		<it>Contains</it>
+	</item>
+	<item>
+		Step 4. Leave <it>AND/OR</it> box on default setting, <it>and</it>.
+	</item>
+	<item>
+		Step 5.	Under the second Operator set's <it>Header</it> 
+		drop-down box, select <it>Subject</it>.
+	</item>
+	<item>
+		Step 6. In the <it>Keyword</it> text box, type 
+		'2001 spring grommet collection' (case insensitive).
+	</item>
+	<item>
+		Step 7. Leave <it>Predicate</it> setting on default,
+		<it>Contains</it>.
+	</item>
+</itemize>
+
+</sect2>
+
+<sect2>Message Processing
+<p>
+Once you've established the Operator(s) that will define 
+which messages will be processed, it's time to tell 
+Sylpheed what to do with messages that match the operator(s). 
+You may choose between two radio button-selected settings: 
+<it>Destination</it> and <it>Don't Receive</it>.
+<p>
+Selecting <it>Destinations</it> will enable you to route 
+the mail into a mailbox which you specify.
+<p>
+Selecting <it>Don't Receive</it> will instruct Sylpheed 
+to not download messages with that operator. Note that with 
+<it>Don't Receive</it>, Sylpheed merely leaves the message 
+on your mailserver - it does not delete it. 
+
+To specify a mailbox to which you want the message transfered, 
+click on the radio button to the left of the word <it>Destination</it>
+in the dialog. (Currently, in order to specify a mailbox you 
+must have created that mailbox prior to activating the Filter 
+Setting dialog.) Clicking the <it>Select</it> button will open 
+a pop-up window containing all mail folders currently active 
+in your copy of Sylpheed. Select the mailbox you wish by either 
+
+<itemize>
+	<item>
+		(a) double clicking on the mail folder name or 
+	</item>
+	<item>
+		(b) clicking the mail folder name and then clicking <it>OK</it>.         
+	</item>
+</itemize>
+
+<p>
+To specify that the message not be retrieved, and left 
+on your mail server, click the radio button to the left 
+of the words <it>Don't Receive</it>.
+
+</sect2>
+
+<sect2>Filter Registration
+<p>
+Now that you have set the Operator and the Processing Rule, 
+all that's left to do is tell Sylpheed to save the entire 
+Filter Rule. <bf>If you skip this step, the filter won't work</bf>.
+<p>
+The <it>Register Rules</it> configuration has three options: 
+<it>Register</it>, <it>Substitute</it> and <it>Delete</it>. 
+
+<itemize>
+	<item>
+		<it>Register</it> saves the Filter Rule.
+	</item>
+	<item>
+		<it>Substitute</it> modifies an existing registered 
+		Filter Rule.
+	</item>
+	<item>
+		<it>Delete</it> will remove a previously registered 
+		Filter Rule. 
+	</item>
+</itemize>
+
+Example of Registering A Filter Rule: Create a Filter Rule 
+that moves all mail with the subject of "Sylpheed Manual" 
+into the (previously created) mail folder "Sylpheed Manual Mail".
+
+<itemize>
+	<item>
+		Step 1. Under the first Operator set's <it>Header</it> 
+		drop-down box, select <it>Subject</it>.
+	</item>
+	<item>
+		Step 2. In the <it>Keyword</it> text box, type 
+		'sylpheed manual' (case insensitive).
+	</item>
+	<item>
+		Step 3. Leave <it>Predicate</it> setting on default, 
+		<it>Contains</it>. Leave second Operator set empty.
+	</item>
+	<item>
+		Step 4. Click <it>Destinations</it> radio button; 
+		select "Sylpheed Manual Mail" folder.
+	</item>
+	<item>
+		Step 5. Click <it>Register</it>.
+	</item>
+	<item>
+		Step 6. Click <it>OK</it>.
+	</item>
+</itemize> 
+
+Example of Substituting A Filter Rule: Modify a previously 
+created Filter Rule that moves all mail with the subject 
+of "Sylpheed Manual" to sort mail not to the mail folder 
+"Sylpheed Manual Mail" but rather the mail folder "Sylpheed Questions"  
+
+<itemize>
+	<item>
+		Step 1. Under the first Operator set's <it>Header</it> 
+		drop-down box, select <it>Subject</it>.
+	</item>
+	<item>
+		Step 2. In the <it>Keyword</it> text box, type 
+		'sylpheed manual' (case insensitive).
+	</item>
+	<item>
+		Step 3. Leave <it>Predicate</it> setting on default, 
+		<it>Contains</it>. Leave second Operator set empty.
+	</item>
+	<item>
+		Step 4. Click <it>Destinations</it> radio button; 
+		select "Sylpheed Questions" folder.
+	</item>
+	<item>
+		Step 5. Click <it>Substitute</it>.
+	</item>
+	<item>
+		Step 6. Click <it>OK</it>.
+	</item>
+</itemize>
+
+Example of Deleting a Filter Rule: Remove the previously 
+created Filter Rule which refers to Subject:Sylpheed Questions.
+
+<itemize>
+	<item>
+		Step 1. In the <it>Registered Rules</it> select box, 
+		highlight the filter entitled 
+		"<it>Subject:Sylpheed Manual: :::Sylpheed Questions:1:1:m</it>"
+	</item>
+	<item>
+		Step 2. Click the <it>Delete</it> Button.
+	</item>
+	<item>
+		Step 3. Confirm the deletion by clicking <it>Yes</it> in the 
+		confirmation pop-up that asks, 
+		<it>Do you really want to delete this rule?</it>
+	</item>
+	<item>
+		Step 4. Click <it>OK</it>.
+	</item>
+</itemize>
+
+</sect2>
+
+<sect2>Registered Rule Order
+<p>
+One caveat about all this: the order in which Filter Rules 
+are created could adversely affect your intended message sorting, 
+and one needs to consider this when creating or updating Filter Rules. 
+<p>
+For example, a Filter Rule saying, "Move anything containing 'ABC' 
+to Mailbox X" listed above another Filter Rule saying "Move anything 
+containing 'ABCDEF' to Mailbox Y" will cause the latter of these 
+filters not to process. 
+<p>
+Think about the way Sylpheed goes down its list: first, it would say..
+"Hmm, any messages with ABC? Ah, there's one! Move it". 
+Then it would think, "Okay, any messages with ABCDEF?" 
+To which the answer would be "no" - that ABCDEF was already 
+filtered because it contained "ABC".
+<p>
+Bummer.
+<p>
+In order to avoid this, you must ensure that the more complex 
+Filter Rule is processed first, by placing it higher than a 
+similar, conflicting Filter Rule. 
+<p>
+To move a Registered Rule higher or lower within the Registered 
+Rule box, select the rule you would like to move, and click on 
+the <it>Up</it> or <it>Down</it> buttons. This will "move" the 
+rule up or down, above or below a potentially conflicting Filter Rule.   
+
+</sect2>
 </sect1>
-</sect>
 
+<sect1>How to Filter Messages
+<p>
+Filtering messages can be done in several ways:
+
+<itemize>
+	<item>
+		Sylpheed automatically filters incoming mail from 
+		POP servers.
+	</item>
+	<item>
+		If you incorporate mail from a unix mailbox, then 
+		in the <it>Common preferences</it> (<it>Configuration</it> menu), 
+		you need to check the box called <it>Filter on incorporation</it>. 
+		You find this box in the <it>Receive</it> tab in the space 
+		<it>Local spool</it>.
+	</item>
+	<item>
+		You can also select the option <it>Filter messages</it> 
+		from the Summary menu.
+	</item>
+</itemize>
+
+Please note that, at time of writing, Sylpheed does -NOT YET- 
+has filtering of IMAP messages enabled.
+
+</sect1>
+
+<sect1>Filtering mail with Procmail
+<p>
+If you feel that Sylpheed has not enough options to perform 
+filtering for you, then you can look at Sylpheed Claws which 
+has more options for filtering. You can find the Claws version 
+(the cutting edge, experimental version of Sylpheed) 
+sylpheed-claws.sourceforge.net.
+<p>
+Another option, if you do not want to work with an experimental 
+version of Sylpheed, is Procmail. Procmail is a powerful mail 
+filtering program that is triggered from the Mail Transport 
+Agent (i.e. Sendmail, Postfix, Qmail). Procmail is called by 
+default from these programs after receiving e-mail.
+<p>
+The trick to procmail is to tell it that mail has to be filtered 
+into MH mail folders. This is not difficult though.
+<p>
+Normally procmail moves mail into MBOX format, this is one large 
+file containing all mails in a folder. MH uses separate files 
+for each e-mail. All you need to do is point the destination 
+of a procmail rule to &lt;destination folder&gt;/.  
+It is the "slash dot" that does the trick.
+
+
+<sect1>Actions
+<p>
+The following section is a copy of 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/index.html" name="Melvin's page">.
+
+<p>
+The "actions" feature is a convenient way for the user to 
+launch external commands to process a complete message file 
+including headers and body or just one of its parts. 
+It allows also the use of an external command to filter the 
+whole text or just a selected part in the message window or 
+in the compose window. This is a generic tool that allows 
+to do any uncommon actions on the messages, and thus extends 
+the possibilities of Sylpheed. For example, Sylpheed does not 
+include the rot13 cyphering algorithm popular in some 
+newsgroups. It does not support natively armored encryption 
+or clear signing. It does not support uuencoded messages. 
+As all these features can be handled by external programs, 
+the actions provide a convenient way to use them from the menu bar.
+
+<sect2>Usage
+<p>
+To create a new action, go to the <it>Configuration</it> menu,
+select the <it>Actions...</it> entry. The <it>Actions setting</it>
+dialog offers to enter the Menu name that will trigger the command. 
+The created menu will be found in the <it>Tools -> Actions</it> submenu. 
+By inserting a slash / in the menu name, you create a submenu.
+
+The command is entered in the Command line entry. Note that 
+Sylpheed stores every single email in a separate file. This allows 
+to use the following syntax for the command:
+
+<itemize>
+	<item>
+		<it>%f</it> denotes the file name of the selected message. 
+		If you selected more than one, then the command will be 
+		launched for each message with the appropriate file name.
+	</item>
+	<item>
+		<it>%F</it> denotes the list of the file names of the 
+		selected message. If only one message is selected, 
+		this amounts to <it>%f</it>, but if more messages are 
+		selected, then the command will be launched only once 
+		with the list of the file names. (You can use both 
+		<it>%f</it> and <it>%F</it> in one command: then the 
+		command will be launched for each selected message 
+		with the name of this message and with the list of 
+		all selected messages. I did not find a practical 
+		example for this.).
+	</item>
+	<item>
+		<it>%p</it> denotes the current selected message part 
+		of a multipart message. The part is decoded accordingly. 
+		If the message is not a multipart message, it denotes 
+		the message body.
+	</item>
+	<item>
+		Prepending <it>&gt;</it>: this will allow you to send 
+		to the command's standard input a text that you will 
+		enter in a dialog window.
+	</item>
+	<item>
+		Prepending <it>*</it>: this will allow you to send to 
+		the command's standard input a text that you will enter 
+		in a dialog window. But in contrast to prepending 
+		<it>&gt;</it>, the entered text is hidden 
+		(useful when entering passwords).
+	</item>
+	<item>
+		Appending an ampersand <it>&amp;</it>: this will run 
+		the command asynchronously. That means "fire and forget". 
+		Sylpheed won't wait for the command to finish, nor will 
+		it catch its output or its error messages.
+	</item>
+	<item>
+		Prepending the vertical bar <it>|</it> (pipe-in): 
+		this will send the current displayed text or the current 
+		selected text from the message view or the compose 
+		window to the command standard input. The command will 
+		silently fail if more than one message is selected.
+	</item>
+	<item>
+		Appending the vertical bar <it>|</it> (pipe-out): this 
+		will replace the current displayed text or the current 
+		selected text from the message window or the compose 
+		window with the command standard output. The command 
+		will silently fail if more than one message is selected.
+	</item>
+	<item>
+		Appending the "greater than" sign <it>&gt;</it> will 
+		insert the command output in the message. The difference 
+		between the trailing <it>|</it> is that no text will be 
+		deleted or replaced. Most used when composing mails to 
+		insert text.
+	</item>
+</itemize>
+
+<bf>Note</bf>: It is not possible to use actions containing 
+<it>%f</it>, <it>%F</it> or <it>%p</it> from the compose window.
+<p>
+When a command is run, and unless it is run asynchronously, 
+Sylpheed will be insensitive to any interaction and it will wait 
+for the command to finish. If the command takes too long 
+(5 seconds), it will popup a dialog window allowing to stop it. 
+This dialog will also be displayed as soon as the command has 
+some output: error messages or even its standard output when 
+the command is not a "pipe-out" command. When multiple commands 
+are being run, they are run in parallel and each command output 
+is separated from the outputs of the others.
+<p>
+<sect3>Examples
+<p>
+Here are some examples that are listed in the same syntax 
+as used for storing the actions list. You can copy and past 
+the definition in your <it>~/.sylpheed/actionsrc</it> file 
+(exit Sylpheed before). The syntax is very simple: one line 
+per action, each action contains the menu name and the command 
+line separated by a colon and a space ": ". 
+Alternatively, you can use <it>Configuration -> Actions...</it> 
+and for each example enter a menu name and copy&amp;paste the 
+text after the colon and space ": " in the command definition.
+
+
+<table>
+	<tabular ca="lll">
+		<bf>Purpose</bf>
+	<colsep>
+		<bf>Definition</bf>
+	<colsep>
+		<bf>Details</bf>
+	<rowsep>
+
+		Decoding uuencoded messages
+	<colsep>
+		UUdeview: xdeview %F&amp;
+	<colsep>
+		xdeview comes with uudeview. If an encoded file is split 
+		in multiple messages, just select them all and run the command.
+	<rowsep>
+
+		Display uuencoded image
+	<colsep>
+		Display uuencoded: uudec %f&amp;
+	<colsep>
+		Displays uuencoded files. The uudec script is to be found here.
+	<rowsep>
+
+		rot13 cyphering
+	<colsep>
+		Rot13: &verbar;tr a-zA-Z n-za-mN-ZA-M&verbar;
+	<colsep>
+		This will apply the rot13 cyphering algorithm to the (selected)
+		text in the message/compose view.
+	<rowsep>
+
+		Save MS TNEF parts
+	<colsep>
+		Save TNEF part: xterm -e tnef-claws %p
+	<colsep>
+		Select the TNEF message part then use this action to extract 
+		the attachment.
+	<rowsep>
+
+		Alter messages
+	<colsep>
+		Edit message: gvim -f %F
+	<colsep>
+		Allows to edit any received message. Can be used to remove 
+		unneeded message parts etc.
+	<rowsep>
+
+		Pretty format
+	<colsep>
+		Par: &verbar;par 72Tbgjqw74bEe B=.&lowbar;A&lowbar;a 72bgi&verbar;
+	<colsep>
+		par is a utility that can pretty format any text. It does a 
+		very good job in indenting quoted messages, and justify text. 
+		Used when composing a message
+	<rowsep>
+
+		Browse
+	<colsep>
+		Part/Dillo: dillo %p&amp;
+	<colsep>
+		Browse the selected message part in Dillo.
+	<rowsep>
+
+		Clear Sign
+	<colsep>
+		GnuPG/Clear Sign: &verbar;gpg-sign-syl&verbar;
+	<colsep>
+		Clear sign a message. The gpg-sign-syl script is responsible 
+		for asking the passphrase and for running gnupg. Make sure 
+		that you wrap your message correctly before signing, and that 
+		the resultant text will not be wrapped when sent (by disabling 
+		'wrap on send')
+	<rowsep>
+
+		Verify Clear Signed
+	<colsep>
+		GnuPG/Verify: &verbar;gpg --no-tty --verify
+	<colsep>
+		Verify clear signed messages. The result is displayed in the 
+		actions output dialog.
+	<rowsep>
+
+		Encrypt ASCII Armored
+	<colsep>
+		GnuPG/Encrypt: &verbar; gpg-enc-syl&verbar;
+	<colsep>
+		Encrypt message to ASCII armored. The recipient will be asked 
+		in a xterm.
+	<rowsep>
+
+		Decrypt ASCII Armored
+	<colsep>
+		GnuPG/Decrypt: *gpg --no-tty --command-fd 0 --passphrase-fd 0 --decrypt %f&verbar;
+	<colsep>
+		Decrypt ASCII armored messages. The passphrase is to be entered 
+		in the opened action's input dialog.
+	<rowsep>
+
+		Receive key from server
+	<colsep>
+		GnuPG/Receive Selected Key: &verbar;gpg --recv-key `cat`
+	<colsep>
+		Select a key ID in the message view then call this action to 
+		import it from a key server. GnuPG option file must contain a 
+		reference to a keyserver. (Suggested by Bob Forsman)
+	<rowsep>
+
+		Import key from mail
+	<colsep>
+		GnuPG/Import Key From Mail: gpg --import %p
+	<colsep>
+		Select the message part where the public key is then import 
+		it with this action.
+	<rowsep>
+
+		Insert public key in message
+	<colsep>
+		GnuPG/Insert My Public Key: gpg --export -a MYKEYID&gt;
+	<colsep>
+		Insert your public key in the message your are composing. 
+		Replace MYKEYID with your key id. Needs 0.8.6claws66 or newer.
+	<rowsep>
+
+		Reporting SPAM
+	<colsep>
+		Report as SPAM: spamassassin -r &gt; %f
+	<colsep>
+		Use spamassassin to report mail as spam. Redirection (&gt;) 
+		is possible only with version 0.7.7.
+	<rowsep>
+
+		Check spelling
+	<colsep>
+		Check spelling: &verbar;T=`mktemp $HOME/.sXXXXXX`; cat - &gt; $T;xterm -e ispell $T;cat $T;rm $T&verbar;
+	<colsep>
+		Open a terminal and check the spelling with ispell
+	<rowsep>
+
+		Google for message id
+	<colsep>
+		Google Msg ID: &verbar;google_msgid.pl
+	<colsep>
+		Search the web for the selected message ID. Needs the 
+		google_msgid.pl script.
+	<rowsep>
+
+	</tabular>
+</table>
+
+
+The gpg-enc-syl script is to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-enc-syl" name="here (gpg-enc-syl)">. 
+It calls gpg with the --yes command line option that you may want 
+to remove it. See gpg manual page for info.
+
+The gpg-sign-syl script is to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-sign-syl" name="here (gpg-sign-syl)">. 
+It needs the ssh-askpass utility found in OpenSSH. It can be 
+replaced by any X11 tool that asks some (hidden) text which 
+is then sent to standard output. Another version that uses 
+an xterm is to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-sign-syl-xterm" name="here (gpg-sign-syl-xterm)">.
+
+The uudec script is to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/uudec" name="here (uudec)">.
+It needs uudecode and ImageMagick's display. The latter can be
+replaced by any image viewer that can get input from standard 
+input. The script could also be modified to use temporary 
+files instead of standard input.
+
+The google_msgid.pl script is to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/google_msgid.pl" name="here (google_msgid.pl)">. 
+Example and script by Thorsten Maerz. Edit the script to change 
+the browser (default is mozilla).
+
+The tnef-claws bash script was written by Shawn Lamson and is 
+to be found 
+<url url="http://melvin.hadasht.free.fr/home/sylpheed/actions/tnef-claws" name="here">.
+The script is well commented. You need to have the tnef package 
+already installed.
+
+</sect1>
+
+<sect1>Templates
+<p>
+
+<figure loc="here">
+<ph vspace="1cm">
+<img src="snapshots/template.png">
+</figure>
+
+### FIXME: write this section.
+
+</sect1>
+
+</sect>