summaryrefslogtreecommitdiff
path: root/manual/en/sylpheed-13.html
diff options
context:
space:
mode:
Diffstat (limited to 'manual/en/sylpheed-13.html')
-rw-r--r--manual/en/sylpheed-13.html473
1 files changed, 473 insertions, 0 deletions
diff --git a/manual/en/sylpheed-13.html b/manual/en/sylpheed-13.html
new file mode 100644
index 0000000..7e5255e
--- /dev/null
+++ b/manual/en/sylpheed-13.html
@@ -0,0 +1,473 @@
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2<HTML>
3<HEAD>
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>Sylpheed User's Manual: Filters, actions and templates</TITLE>
6 <LINK HREF="sylpheed-14.html" REL=next>
7 <LINK HREF="sylpheed-12.html" REL=previous>
8 <LINK HREF="sylpheed.html#toc13" REL=contents>
9</HEAD>
10<BODY>
11<A HREF="sylpheed-14.html">Next</A>
12<A HREF="sylpheed-12.html">Previous</A>
13<A HREF="sylpheed.html#toc13">Contents</A>
14<HR>
15<H2><A NAME="s13">13. Filters, actions and templates</A></H2>
16
17<P>Sylpheed offers three powerfull tools to help you automatically
18and efficently manage you mails. These tools are:
19<P>
20<UL>
21<LI>The <I>filters</I>, that let you sort you incoming messages and move
22them into your folders based on their sender, their content,
23using regular expressions.</LI>
24<LI>The <I>actions</I> feature is a convenient way for the user to launch
25external commands to process a complete message file including
26headers and body or just one of its parts.
27It allows also the use of an external command to filter the whole
28text or just a selected part in the message window or in the
29compose window.</LI>
30<LI>The <I>templates</I> that let you pre-define complete messages
31leaving placeholders in the text to be filled at composition time.</LI>
32</UL>
33<P>
34<P>
35<P>
36<H2><A NAME="ss13.1">13.1 Filters</A>
37</H2>
38
39<P>Written by Nick Selby (sylpheed@nickselby.com)
40<P>Sylpheed provides powerful filters to allow users to automatically
41pre-sort incoming mail based on a set of rules that the user defines.
42As a most simple example, let's say you work at the Acme Grommet Company,
43and you want all e-mail from your co-workers to be placed in one mailbox.
44To accomplish this, you would set up a filter that would place all mail
45whose "From" header includes the phrase "acmegrommet.com" into a specific
46mailbox.
47<P>Sylpheed allows you much more control than just that simple setup;
48you may create filters based on several variables, including an
49"If this AND that" or "If the message contains this OR does NOT contain that"
50etc. It's very cool.
51<P>
52<H3>Finding The Filter Setting Dialog</H3>
53
54<P>The filter settings dialog is located in the <I>Configuration</I> menu,
55under the title "Filter Setting" or from the <I>Tools</I> menu, under in
56the <I>Create filter rules</I> sub menu. You may also use establish a
57keyboard shortcut (see Keyboard Shortcuts).
58<P>
59<P>
60<P>
61<P>
62<H3>Setting Up Filters</H3>
63
64<P>Operator(s) and Processing instructions combine to create a Filter Rule.
65<P>* Operators
66The dialog's first setting option establishes the Operator, the variable
67that will tell the filter what specific text to look for to trigger a
68filter. Each Filter Rule may have up to two operator sets.
69<P>Each Operator variable contains three sections: <I>Header</I>,
70<I>Keyword</I> and <I>Predicate</I>.
71<P>Header is a drop-down box which defines in which message header
72Sylpheed's filter will search. Choices range from <I>Subject</I>
73to <I>X-Mailer</I>.
74<P><I>Keyword</I> is a a text box in which you may enter the text
75for which the filter will search.
76<P>Predicate allows you to choose to filter based on whether the operator
77contains, or does not contain, the text you enter in the Keyword field.
78<P>Example: Create an Operator in which the X-Mailer field of an incoming
79message contains the word 'Eudora'.
80<P>
81<UL>
82<LI>Step 1. Under the <I>Header</I> drop-down box, select
83<I>X-Mailer</I>.</LI>
84<LI>Step 2. In the <I>Keyword</I> text box, type 'eudora'
85(case insensitive)</LI>
86<LI>Step 3. Determine appropriate Predicate setting. Default
87is <I>Contains</I>.</LI>
88</UL>
89<P>The second Operator setting, which is set identically to the
90first, also allows the user to select an AND/OR setting
91declaring the relationship between the two operators.
92<P>Example: Create an Operator set which will process mail with
93a <I>From</I> header of bob@acmegrommet.com AND a subject
94of "2001 Spring Grommet Collection"
95<P>
96<UL>
97<LI>Step 1. Under the first Operator set's Header drop-down
98box, select <I>From</I>.</LI>
99<LI>Step 2. In the <I>Keyword</I> text box, type
100'bob@acmegrommet.com' (case insensitive).</LI>
101<LI>Step 3. Leave <I>Predicate</I> setting on default,
102<I>Contains</I></LI>
103<LI>Step 4. Leave <I>AND/OR</I> box on default setting, <I>and</I>.</LI>
104<LI>Step 5. Under the second Operator set's <I>Header</I>
105drop-down box, select <I>Subject</I>.</LI>
106<LI>Step 6. In the <I>Keyword</I> text box, type
107'2001 spring grommet collection' (case insensitive).</LI>
108<LI>Step 7. Leave <I>Predicate</I> setting on default,
109<I>Contains</I>.</LI>
110</UL>
111<P>
112<H3>Message Processing</H3>
113
114<P>Once you've established the Operator(s) that will define
115which messages will be processed, it's time to tell
116Sylpheed what to do with messages that match the operator(s).
117You may choose between two radio button-selected settings:
118<I>Destination</I> and <I>Don't Receive</I>.
119<P>Selecting <I>Destinations</I> will enable you to route
120the mail into a mailbox which you specify.
121<P>Selecting <I>Don't Receive</I> will instruct Sylpheed
122to not download messages with that operator. Note that with
123<I>Don't Receive</I>, Sylpheed merely leaves the message
124on your mailserver - it does not delete it.
125<P>To specify a mailbox to which you want the message transfered,
126click on the radio button to the left of the word <I>Destination</I>
127in the dialog. (Currently, in order to specify a mailbox you
128must have created that mailbox prior to activating the Filter
129Setting dialog.) Clicking the <I>Select</I> button will open
130a pop-up window containing all mail folders currently active
131in your copy of Sylpheed. Select the mailbox you wish by either
132<P>
133<UL>
134<LI>(a) double clicking on the mail folder name or </LI>
135<LI>(b) clicking the mail folder name and then clicking <I>OK</I>. </LI>
136</UL>
137<P>
138<P>To specify that the message not be retrieved, and left
139on your mail server, click the radio button to the left
140of the words <I>Don't Receive</I>.
141<P>
142<H3>Filter Registration</H3>
143
144<P>Now that you have set the Operator and the Processing Rule,
145all that's left to do is tell Sylpheed to save the entire
146Filter Rule. <B>If you skip this step, the filter won't work</B>.
147<P>The <I>Register Rules</I> configuration has three options:
148<I>Register</I>, <I>Substitute</I> and <I>Delete</I>.
149<P>
150<UL>
151<LI><I>Register</I> saves the Filter Rule.</LI>
152<LI><I>Substitute</I> modifies an existing registered
153Filter Rule.</LI>
154<LI><I>Delete</I> will remove a previously registered
155Filter Rule. </LI>
156</UL>
157<P>Example of Registering A Filter Rule: Create a Filter Rule
158that moves all mail with the subject of "Sylpheed Manual"
159into the (previously created) mail folder "Sylpheed Manual Mail".
160<P>
161<UL>
162<LI>Step 1. Under the first Operator set's <I>Header</I>
163drop-down box, select <I>Subject</I>.</LI>
164<LI>Step 2. In the <I>Keyword</I> text box, type
165'sylpheed manual' (case insensitive).</LI>
166<LI>Step 3. Leave <I>Predicate</I> setting on default,
167<I>Contains</I>. Leave second Operator set empty.</LI>
168<LI>Step 4. Click <I>Destinations</I> radio button;
169select "Sylpheed Manual Mail" folder.</LI>
170<LI>Step 5. Click <I>Register</I>.</LI>
171<LI>Step 6. Click <I>OK</I>.</LI>
172</UL>
173
174<P>Example of Substituting A Filter Rule: Modify a previously
175created Filter Rule that moves all mail with the subject
176of "Sylpheed Manual" to sort mail not to the mail folder
177"Sylpheed Manual Mail" but rather the mail folder "Sylpheed Questions"
178<P>
179<UL>
180<LI>Step 1. Under the first Operator set's <I>Header</I>
181drop-down box, select <I>Subject</I>.</LI>
182<LI>Step 2. In the <I>Keyword</I> text box, type
183'sylpheed manual' (case insensitive).</LI>
184<LI>Step 3. Leave <I>Predicate</I> setting on default,
185<I>Contains</I>. Leave second Operator set empty.</LI>
186<LI>Step 4. Click <I>Destinations</I> radio button;
187select "Sylpheed Questions" folder.</LI>
188<LI>Step 5. Click <I>Substitute</I>.</LI>
189<LI>Step 6. Click <I>OK</I>.</LI>
190</UL>
191<P>Example of Deleting a Filter Rule: Remove the previously
192created Filter Rule which refers to Subject:Sylpheed Questions.
193<P>
194<UL>
195<LI>Step 1. In the <I>Registered Rules</I> select box,
196highlight the filter entitled
197"<I>Subject:Sylpheed Manual: :::Sylpheed Questions:1:1:m</I>"</LI>
198<LI>Step 2. Click the <I>Delete</I> Button.</LI>
199<LI>Step 3. Confirm the deletion by clicking <I>Yes</I> in the
200confirmation pop-up that asks,
201<I>Do you really want to delete this rule?</I></LI>
202<LI>Step 4. Click <I>OK</I>.</LI>
203</UL>
204<P>
205<H3>Registered Rule Order</H3>
206
207<P>One caveat about all this: the order in which Filter Rules
208are created could adversely affect your intended message sorting,
209and one needs to consider this when creating or updating Filter Rules.
210<P>For example, a Filter Rule saying, "Move anything containing 'ABC'
211to Mailbox X" listed above another Filter Rule saying "Move anything
212containing 'ABCDEF' to Mailbox Y" will cause the latter of these
213filters not to process.
214<P>Think about the way Sylpheed goes down its list: first, it would say..
215"Hmm, any messages with ABC? Ah, there's one! Move it".
216Then it would think, "Okay, any messages with ABCDEF?"
217To which the answer would be "no" - that ABCDEF was already
218filtered because it contained "ABC".
219<P>Bummer.
220<P>In order to avoid this, you must ensure that the more complex
221Filter Rule is processed first, by placing it higher than a
222similar, conflicting Filter Rule.
223<P>To move a Registered Rule higher or lower within the Registered
224Rule box, select the rule you would like to move, and click on
225the <I>Up</I> or <I>Down</I> buttons. This will "move" the
226rule up or down, above or below a potentially conflicting Filter Rule.
227<P>
228<H2><A NAME="ss13.2">13.2 How to Filter Messages</A>
229</H2>
230
231<P>Filtering messages can be done in several ways:
232<P>
233<UL>
234<LI>Sylpheed automatically filters incoming mail from
235POP servers.</LI>
236<LI>If you incorporate mail from a unix mailbox, then
237in the <I>Common preferences</I> (<I>Configuration</I> menu),
238you need to check the box called <I>Filter on incorporation</I>.
239You find this box in the <I>Receive</I> tab in the space
240<I>Local spool</I>.</LI>
241<LI>You can also select the option <I>Filter messages</I>
242from the Summary menu.</LI>
243</UL>
244<P>Please note that, at time of writing, Sylpheed does -NOT YET-
245has filtering of IMAP messages enabled.
246<P>
247<H2><A NAME="ss13.3">13.3 Filtering mail with Procmail</A>
248</H2>
249
250<P>If you feel that Sylpheed has not enough options to perform
251filtering for you, then you can look at Sylpheed Claws which
252has more options for filtering. You can find the Claws version
253(the cutting edge, experimental version of Sylpheed)
254sylpheed-claws.sourceforge.net.
255<P>Another option, if you do not want to work with an experimental
256version of Sylpheed, is Procmail. Procmail is a powerful mail
257filtering program that is triggered from the Mail Transport
258Agent (i.e. Sendmail, Postfix, Qmail). Procmail is called by
259default from these programs after receiving e-mail.
260<P>The trick to procmail is to tell it that mail has to be filtered
261into MH mail folders. This is not difficult though.
262<P>Normally procmail moves mail into MBOX format, this is one large
263file containing all mails in a folder. MH uses separate files
264for each e-mail. All you need to do is point the destination
265of a procmail rule to &lt;destination folder&gt;/.
266It is the "slash dot" that does the trick.
267<P>
268<P>
269<H2><A NAME="ss13.4">13.4 Actions</A>
270</H2>
271
272<P>The following section is a copy of
273<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/index.html">Melvin's page</A>.
274<P>
275<P>The "actions" feature is a convenient way for the user to
276launch external commands to process a complete message file
277including headers and body or just one of its parts.
278It allows also the use of an external command to filter the
279whole text or just a selected part in the message window or
280in the compose window. This is a generic tool that allows
281to do any uncommon actions on the messages, and thus extends
282the possibilities of Sylpheed. For example, Sylpheed does not
283include the rot13 cyphering algorithm popular in some
284newsgroups. It does not support natively armored encryption
285or clear signing. It does not support uuencoded messages.
286As all these features can be handled by external programs,
287the actions provide a convenient way to use them from the menu bar.
288<P>
289<H3>Usage</H3>
290
291<P>To create a new action, go to the <I>Configuration</I> menu,
292select the <I>Actions...</I> entry. The <I>Actions setting</I>
293dialog offers to enter the Menu name that will trigger the command.
294The created menu will be found in the <I>Tools -> Actions</I> submenu.
295By inserting a slash / in the menu name, you create a submenu.
296<P>The command is entered in the Command line entry. Note that
297Sylpheed stores every single email in a separate file. This allows
298to use the following syntax for the command:
299<P>
300<UL>
301<LI><I>%f</I> denotes the file name of the selected message.
302If you selected more than one, then the command will be
303launched for each message with the appropriate file name.</LI>
304<LI><I>%F</I> denotes the list of the file names of the
305selected message. If only one message is selected,
306this amounts to <I>%f</I>, but if more messages are
307selected, then the command will be launched only once
308with the list of the file names. (You can use both
309<I>%f</I> and <I>%F</I> in one command: then the
310command will be launched for each selected message
311with the name of this message and with the list of
312all selected messages. I did not find a practical
313example for this.).</LI>
314<LI><I>%p</I> denotes the current selected message part
315of a multipart message. The part is decoded accordingly.
316If the message is not a multipart message, it denotes
317the message body.</LI>
318<LI>Prepending <I>&gt;</I>: this will allow you to send
319to the command's standard input a text that you will
320enter in a dialog window.</LI>
321<LI>Prepending <I>*</I>: this will allow you to send to
322the command's standard input a text that you will enter
323in a dialog window. But in contrast to prepending
324<I>&gt;</I>, the entered text is hidden
325(useful when entering passwords).</LI>
326<LI>Appending an ampersand <I>&amp;</I>: this will run
327the command asynchronously. That means "fire and forget".
328Sylpheed won't wait for the command to finish, nor will
329it catch its output or its error messages.</LI>
330<LI>Prepending the vertical bar <I>|</I> (pipe-in):
331this will send the current displayed text or the current
332selected text from the message view or the compose
333window to the command standard input. The command will
334silently fail if more than one message is selected.</LI>
335<LI>Appending the vertical bar <I>|</I> (pipe-out): this
336will replace the current displayed text or the current
337selected text from the message window or the compose
338window with the command standard output. The command
339will silently fail if more than one message is selected.</LI>
340<LI>Appending the "greater than" sign <I>&gt;</I> will
341insert the command output in the message. The difference
342between the trailing <I>|</I> is that no text will be
343deleted or replaced. Most used when composing mails to
344insert text.</LI>
345</UL>
346<P><B>Note</B>: It is not possible to use actions containing
347<I>%f</I>, <I>%F</I> or <I>%p</I> from the compose window.
348<P>When a command is run, and unless it is run asynchronously,
349Sylpheed will be insensitive to any interaction and it will wait
350for the command to finish. If the command takes too long
351(5 seconds), it will popup a dialog window allowing to stop it.
352This dialog will also be displayed as soon as the command has
353some output: error messages or even its standard output when
354the command is not a "pipe-out" command. When multiple commands
355are being run, they are run in parallel and each command output
356is separated from the outputs of the others.
357<P>
358<H3>Examples</H3>
359
360<P>Here are some examples that are listed in the same syntax
361as used for storing the actions list. You can copy and past
362the definition in your <I>&nbsp;/.sylpheed/actionsrc</I> file
363(exit Sylpheed before). The syntax is very simple: one line
364per action, each action contains the menu name and the command
365line separated by a colon and a space ": ".
366Alternatively, you can use <I>Configuration -> Actions...</I>
367and for each example enter a menu name and copy&amp;paste the
368text after the colon and space ": " in the command definition.
369<P>
370<P>
371<CENTER><TABLE BORDER><TR><TD>
372<BR>
373<B>Purpose</B></TD><TD><B>Definition</B></TD><TD><B>Details</B></TD></TR><TR><TD>
374Decoding uuencoded messages</TD><TD>UUdeview: xdeview %F&amp;</TD><TD>xdeview comes with uudeview. If an encoded file is splitin multiple messages, just select them all and run the command.</TD></TR><TR><TD>
375Display uuencoded image</TD><TD>Display uuencoded: uudec %f&amp;</TD><TD>Displays uuencoded files. The uudec script is to be found here.</TD></TR><TR><TD>
376rot13 cyphering</TD><TD>Rot13: |tr a-zA-Z n-za-mN-ZA-M|</TD><TD>This will apply the rot13 cyphering algorithm to the (selected)text in the message/compose view.</TD></TR><TR><TD>
377Save MS TNEF parts</TD><TD>Save TNEF part: xterm -e tnef-claws %p</TD><TD>Select the TNEF message part then use this action to extractthe attachment.</TD></TR><TR><TD>
378Alter messages</TD><TD>Edit message: gvim -f %F</TD><TD>Allows to edit any received message. Can be used to removeunneeded message parts etc.</TD></TR><TR><TD>
379Pretty format</TD><TD>Par: |par 72Tbgjqw74bEe B=._A_a 72bgi|</TD><TD>par is a utility that can pretty format any text. It does avery good job in indenting quoted messages, and justify text.Used when composing a message</TD></TR><TR><TD>
380Browse</TD><TD>Part/Dillo: dillo %p&amp;</TD><TD>Browse the selected message part in Dillo.</TD></TR><TR><TD>
381Clear Sign</TD><TD>GnuPG/Clear Sign: |gpg-sign-syl|</TD><TD>Clear sign a message. The gpg-sign-syl script is responsiblefor asking the passphrase and for running gnupg. Make surethat you wrap your message correctly before signing, and thatthe resultant text will not be wrapped when sent (by disabling'wrap on send')</TD></TR><TR><TD>
382Verify Clear Signed</TD><TD>GnuPG/Verify: |gpg --no-tty --verify</TD><TD>Verify clear signed messages. The result is displayed in theactions output dialog.</TD></TR><TR><TD>
383Encrypt ASCII Armored</TD><TD>GnuPG/Encrypt: | gpg-enc-syl|</TD><TD>Encrypt message to ASCII armored. The recipient will be askedin a xterm.</TD></TR><TR><TD>
384Decrypt ASCII Armored</TD><TD>GnuPG/Decrypt: *gpg --no-tty --command-fd 0 --passphrase-fd 0 --decrypt %f|</TD><TD>Decrypt ASCII armored messages. The passphrase is to be enteredin the opened action's input dialog.</TD></TR><TR><TD>
385Receive key from server</TD><TD>GnuPG/Receive Selected Key: |gpg --recv-key `cat`</TD><TD>Select a key ID in the message view then call this action toimport it from a key server. GnuPG option file must contain areference to a keyserver. (Suggested by Bob Forsman)</TD></TR><TR><TD>
386Import key from mail</TD><TD>GnuPG/Import Key From Mail: gpg --import %p</TD><TD>Select the message part where the public key is then importit with this action.</TD></TR><TR><TD>
387Insert public key in message</TD><TD>GnuPG/Insert My Public Key: gpg --export -a MYKEYID&gt;</TD><TD>Insert your public key in the message your are composing.Replace MYKEYID with your key id. Needs 0.8.6claws66 or newer.</TD></TR><TR><TD>
388Reporting SPAM</TD><TD>Report as SPAM: spamassassin -r &gt; %f</TD><TD>Use spamassassin to report mail as spam. Redirection (&gt;)is possible only with version 0.7.7.</TD></TR><TR><TD>
389Check spelling</TD><TD>Check spelling: |T=`mktemp $HOME/.sXXXXXX`; cat - &gt; $T;xterm -e ispell $T;cat $T;rm $T|</TD><TD>Open a terminal and check the spelling with ispell</TD></TR><TR><TD>
390Google for message id</TD><TD>Google Msg ID: |google&thinsp;msgid.pl</TD><TD>Search the web for the selected message ID. Needs thegoogle&thinsp;msgid.pl script.</TD></TR><TR><TD>
391
392</TD></TR></TABLE></CENTER>
393<P>
394<P>The gpg-enc-syl script is to be found
395<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-enc-syl">here (gpg-enc-syl)</A>.
396It calls gpg with the --yes command line option that you may want
397to remove it. See gpg manual page for info.
398<P>The gpg-sign-syl script is to be found
399<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-sign-syl">here (gpg-sign-syl)</A>.
400It needs the ssh-askpass utility found in OpenSSH. It can be
401replaced by any X11 tool that asks some (hidden) text which
402is then sent to standard output. Another version that uses
403an xterm is to be found
404<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/gpg-sign-syl-xterm">here (gpg-sign-syl-xterm)</A>.
405<P>The uudec script is to be found
406<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/uudec">here (uudec)</A>.
407It needs uudecode and ImageMagick's display. The latter can be
408replaced by any image viewer that can get input from standard
409input. The script could also be modified to use temporary
410files instead of standard input.
411<P>The google_msgid.pl script is to be found
412<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/google_msgid.pl">here (google_msgid.pl)</A>.
413Example and script by Thorsten Maerz. Edit the script to change
414the browser (default is mozilla).
415<P>The tnef-claws bash script was written by Shawn Lamson and is
416to be found
417<A HREF="http://melvin.hadasht.free.fr/home/sylpheed/actions/tnef-claws">here</A>.
418The script is well commented. You need to have the tnef package
419already installed.
420<P>
421<H2><A NAME="ss13.5">13.5 Templates</A>
422</H2>
423
424<P>With Sylpheed you can define mail templates to use when replying
425to messages. A template can contain raw text (that will be inserted
426in the composed mail without any change), and placeholders that are
427replaced at composition time by the actual value of the selected
428fields from the original message.
429<P>A typical use of the template could be to define the legal notice
430to be appended to your messages (the usual notice that contains a
431text like: "here are my own words and not those of my company, my
432boss is not liable for them, bla, bla, bla").
433<P>To define a new template, in the <I>Configuration</I> menu select
434the <I>Templates</I> entry and fill the form:
435<P>
436<P>
437<P>
438<P>
439<P>The name parameter is used to identify each template, this name
440will then appear in the <I>Tools/Templates</I> menu in the
441composition window.
442The content of the <I>To</I> field will be appended to the original
443content of the corresponding field in the message you are composing.
444The content of the <I>Subject</I> field will replace the orignal subject
445of the message you are composing.
446<P>In the upper pane, type in the text you want to put in the template,
447use the <I>Symbols</I> button to open a help window that contains
448the description of all the placeholders you can use in a template
449(there is one for the sender, one for the date, one for the message
450ID, ...), then use the <I>Register</I> button to validate the
451template. If you do not register the template, when leaving the form
452the template will be canceled. To modify an existing template, select
453it in the lower pane, modify its text, then use the <I>Substitute</I>
454button. As you may guess, the <I>Delete</I> button removes the selected
455template. Finally validate your changes with the <I>OK</I> button.
456If you use the <I>Cancel</I> button, the form is closed and your changes
457are lost (deleted templates are back, added templates are lost).
458<P>
459<P>To use a template, open the composition window and select the template
460from the <I>Tools/Templates</I> menu. You can then choose to insert
461the template into your message or to completely replace the text of the
462message by the template. This only affects the body of the message.
463If you choose to insert the template, its text will be inserted at the
464cursor location.
465<P>The placeholders are taken from the source message when replying, so
466they have no meaning when composing a new message.
467<P>
468<HR>
469<A HREF="sylpheed-14.html">Next</A>
470<A HREF="sylpheed-12.html">Previous</A>
471<A HREF="sylpheed.html#toc13">Contents</A>
472</BODY>
473</HTML>
generated by cgit v1.3 (git 2.53.0) at 2026-09-26 13:37:10 +0000