| blob | 1a7024b24db163aca7c6dc970118c16e0ed5d216 |
1 <?xml version="1.0" encoding="utf-8"?>
2 <section id="ch_advanced">
3 <title>Advanced features</title>
4 <section id="adv_actions">
5 <title>Actions</title>
6 <para>
7 Actions allow you to use all the power of the Unix command-line with
8 your emails. You can define various commands, taking parameters such
9 as the current email file, a list of emails, the currently selected
10 text, and so on. In this way, you'll be able to perform various tasks
11 such as editing a raw mail in your text editor,
12 <emphasis>hide</emphasis> what you mean using ROT-13, apply patches
13 contained in emails directly, and so on. The only limit is your
14 imagination. You can create and configure Actions via the
15 <quote>/Configuration/Actions...</quote> menu.
16 </para>
17 <para>
18 The <quote>Tools/Actions/</quote> menu will contain one submenu
19 item for each action that you have created. When you have selected
20 one or more messages in the Message List, or are viewing a message
21 in the Message View, selecting one of these menu items will invoke
22 the action, and, depending on how it was defined, will pass the
23 message(s) to it.
24 </para>
25 <para>
26 Additionally, it is possible to add toolbar entries for your
27 actions. To do so, open the <quote>Configuration/Preferences</quote>
28 menu and select <quote>Toolbars/Main Window</quote>.
29 Select <quote>User Action</quote> in the <quote>Item type</quote>
30 dropdown menu, then select the Action in the <quote>Event executed on click</quote>
31 dropdown menu, and click the <quote>Icon</quote> button to select the
32 icon that you want to use.
33 </para>
34 <blockquote>
35 <example>
36 <title>Simple <quote>Open With...</quote></title>
37 <variablelist>
38 <varlistentry>
39 <term>
40 Menu name: <emphasis>Open with/kate</emphasis>
41 Command Line: <command>kate %p</command>
42 </term>
43 <listitem>
44 <para>
45 Opens the file of the selected decoded MIME part
46 (<emphasis>%p</emphasis>) with the <emphasis>kate</emphasis> text
47 editor.
48 </para>
49 </listitem>
50 </varlistentry>
51 </variablelist>
52 </example>
53 <example>
54 <title>Spam management using <ulink
55 url="http://bogofilter.sourceforge.net/">Bogofilter</ulink>
56 </title>
57 <variablelist>
58 <varlistentry>
59 <term>
60 Menu name: <emphasis>Bogofilter/Mark as Ham</emphasis>
61 Command Line: <command>bogofilter -n -v -B "%f"</command>
62 </term>
63 <listitem>
64 <para>
65 Marks the currently selected mails (<emphasis>%f</emphasis>) as
66 <quote>not spam</quote> using <emphasis>Bogofilter</emphasis>.
67 </para>
68 </listitem>
69 </varlistentry>
70 <varlistentry>
71 <term>
72 Menu name: <emphasis>Bogofilter/Mark as Spam</emphasis>
73 Command Line: <command>bogofilter -s -v -B "%f"</command>
74 </term>
75 <listitem>
76 <para>
77 Marks the currently selected mails (<emphasis>%f</emphasis>) as
78 <quote>spam</quote> using <emphasis>Bogofilter</emphasis>.
79 </para>
80 </listitem>
81 </varlistentry>
82 </variablelist>
83 </example>
84 <example>
85 <title>Search Google using an external script</title>
86 <variablelist>
87 <varlistentry>
88 <term>
89 Menu name: <emphasis>Search/Google</emphasis>
90 Command Line: <command>|/path/to/google_search.pl</command>
91 </term>
92 <listitem>
93 <para>
94 Searches Google for the currently selected text
95 (<emphasis>|</emphasis>) using the external script <emphasis><ulink
96 url="http://www.claws-mail.org/tools.php"
97 >google_search.pl</ulink></emphasis>.
98 </para>
99 </listitem>
100 </varlistentry>
101 </variablelist>
102 </example>
103 </blockquote>
104 </section>
105 <section id="adv_templates">
106 <title>Templates</title>
107 <para>
108 Templates are used in composition windows, and act as a model for
109 emails. Templates can be filled with static text and dynamic parts,
110 such as the original sender's name (<quote>Dear %N, ...</quote>),
111 the date, etc. When applying a template, the dynamic fields will be
112 replaced with the relevant values. You can configure templates via
113 the <quote>Tools</quote> menu.
114 </para><para>
115 When applying a template, you will be asked to <quote>Insert</quote>
116 or <quote>Replace</quote>, the difference between replacing and
117 inserting is only concerned with the message body.
118 <quote>Replace</quote> will replace the current composition window
119 message body with the body defined in the template, clearing it if
120 the template body is empty. <quote>Insert</quote> will insert
121 the template's body, if set, at the current cursor position.
122 </para><para>
123 Whether you choose to Insert or Replace, any To, Cc or Bcc field
124 that is defined in the template will be appended to the compose
125 window's recipients list. If it is defined, the template's Subject
126 will always replace the compose window's Subject.
127 </para><para>
128 Symbols can be used in all parts of the templates and will be
129 substituted with their respective dynamic value if possible, otherwise
130 no value will be used. This often makes more sense if you apply a
131 template when replying or forwarding, otherwise most of the symbols
132 value will be undefined. There is no restriction on which symbols can
133 be used in template parts, even if inserting the body (%M or %Q) may
134 make no sense in common situations.
135 </para><para>
136 When applying a template, the body is processed first, then the To, Cc,
137 Bcc and Subject fields follow.
138 </para><para>
139 Further information and examples of usage can be found in the
140 user-contributed FAQ on the Claws Mail website <ulink
141 url="http://www.claws-mail.org/faq/"
142 >http://www.claws-mail.org/faq/</ulink>.
143 </para>
144 </section>
145 <section id="adv_processing">
146 <title>Processing</title>
147 <para>
148 Processing rules are the same as Filtering rules, except that they are
149 applied when entering a folder or when manually applied from a folder's
150 context menu and apply only to this folder. You can use them to automatically
151 move old mails into an archive folder, or for further dispatching of
152 emails, and more. You can set each folder's Processing rules by
153 right-clicking on it.
154 </para><para>
155 Processing rules are accompanied by Pre-processing and Post-processing
156 rules. Like Processing rules, they apply when opening a folder or manually
157 applying them from a folder's context menu, but like Filtering rules,
158 they are shared across all folders. You can configure them from the
159 <quote>Tools</quote> menu. Pre-processing rules are executed before the
160 folder's specific Processing rules, while Post-processing rules are executed
161 afterwards.
162 </para>
163 </section>
164 <section id="adv_colour_labels">
165 <title>Colour Labels</title>
166 <para>
167 Colour labels can be used to denote a message as having a particular
168 significance. To set a colour label simply right-click a message in the
169 Message List and use the <quote>Color label</quote> submenu.
170 </para><para>
171 Colour labels are user-configurable. Both the colour and the label can
172 be set by the user. Preferences can be found on the
173 <quote>Configuration/Preferences/Display/Colors</quote> page.
174 </para>
175 </section>
176 <section id="adv_ml_support">
177 <title>Mailing-List support</title>
178 <para>
179 Claws Mail offers mailing-list support from the
180 <quote>Message/Mailing-List/</quote> submenu. When you have a
181 mailing-list message selected, the submenu allows you to quickly
182 initiate subscribing, unsubscribing, posting, getting help, contacting
183 the list owner, and viewing the list archive; either by opening a new
184 Compose window with the appropriate address pre-filled, or by opening
185 the URL in your web browser.
186 </para>
187 </section>
188 <section id="adv_plugins">
189 <title>Plugins</title>
190 <para>
191 Plugins are the mechanism for extending Claws Mail' capabilities.
192 For example, imagine that you want to store your mails in a remote
193 <acronym>SQL</acronym> database. In most mailers out there this is
194 simply impossible without reworking the internals of the mailer. With
195 Claws Mail you can simply write a plugin to achieve the task.
196 </para><para>
197 This is just an example of the possibilities. A good number of plugins
198 developed for Claws Mail already exist, and more are to come. The
199 <link linkend="ch_plugins">Extending Claws Mail section</link>
200 gives details of them.
201 </para>
202 </section>
203 <section id="deploying">
204 <title>Deploying Claws Mail</title>
205 <para>
206 The initial configuration wizard tries to guess various fields using
207 information gathered from the system, such as username, hostname, and
208 more. As it is oriented towards general use, the default values often
209 have to be fixed. However, this wizard is customisable, in a manner
210 designed to allow system administrators to deploy Claws Mail easily
211 over various users of one machine, or even over multiple machines
212 installed via some replication tool.
213 </para><para>
214 The first part consists of creating a wizard configuration template
215 and setting the various default parameters of a new Claws Mail
216 installation.
217 </para>
218 <itemizedlist>
219 <listitem>
220 <para>
221 Start with a user who does not have a <filename class="directory"
222 >~/.claws-mail</filename> directory, ideally a new user.
223 </para>
224 </listitem>
225 <listitem>
226 <para>
227 Start Claws Mail and go through the wizard. The values you fill in
228 will be of no use for the future deployment, so you can click
229 next-next-next.
230 </para>
231 </listitem>
232 <listitem>
233 <para>
234 Once the wizard is finished and you have Claws Mail' main window
235 opened, configure the various defaults you want to have in the master.
236 You can load plugins, add people or LDAP servers in the addressbook,
237 create filtering rules, and so on.
238 </para>
239 </listitem>
240 <listitem>
241 <para>
242 If needed, and if the deployed Claws Mail will use MH folders, you
243 can create subdirectories in the mailbox.
244 </para>
245 </listitem>
246 <listitem>
247 <para>
248 Next, quit Claws Mail.
249 </para>
250 </listitem>
251 <listitem>
252 <para>
253 Now, edit the newly created wizard template file,
254 <filename>~/.claws-mail/accountrc.tmpl</filename>. In this file,
255 you will see different variables, corresponding to the wizard's fields.
256 You can leave some commented, in which case the usual default will be
257 used, or specify values or variables. Not all fields can contain
258 variables; for example, <literal>smtpauth</literal>,
259 <literal>smtpssl</literal> and <literal>recvssl</literal> are booleans,
260 either 0 or 1, and <literal>recvtype</literal> is an integer value. The
261 other fields, like <literal>name</literal>, <literal>email</literal>,
262 or <literal>recvuser</literal>, are parsed by the wizard and the
263 variables they contain are replaced by values. This allows you to
264 specify everything as needed for your site, even if you have strange
265 server names or server logins.
266 </para>
267 </listitem>
268 <listitem>
269 <para>
270 Save this file, and delete both
271 <filename>~/.claws-mail/accountrc</filename>, (which contains your
272 dummy account) and
273 <filename>~/.claws-mail/folderlist.xml</filename>, (so that the
274 folder tree will be correctly parsed for new users). Recursively copy
275 <filename class="directory">.claws-mail</filename> to
276 <filename class="directory">/etc/skel/</filename>; if the deployed
277 Claws Mail will use MH folders, also copy the created
278 <filename class="directory">Mail</filename> directory. chown all of
279 <filename class="directory">/etc/skel/.claws-mail</filename>
280 and <filename class="directory">/etc/skel/Mail</filename> to
281 <literal>root:root</literal> for security reasons.
282 </para>
283 </listitem>
284 <listitem>
285 <para>
286 Test! Create a new user, login as that user, run Claws Mail. If you
287 filled everything as you wanted, this user will just have to fill in
288 his passwords.
289 </para>
290 </listitem>
291 <listitem>
292 <para>
293 Now, if you're creating a master for a site-wide deployment, you can
294 continue with this process. If you were just doing it for one machine,
295 you're done!
296 </para>
297 </listitem>
298 </itemizedlist>
299 <para>
300 Here are the different variables of the <filename>accountrc.tmpl</filename>
301 file:
302 </para>
303 <variablelist>
304 <varlistentry>
305 <term><literal>domain</literal></term>
306 <listitem>
307 <para>
308 Your domain name (example.com). If not set, it'll be extracted from the
309 hostname.
310 </para>
311 </listitem>
312 </varlistentry>
313 <varlistentry>
314 <term><literal>name</literal></term>
315 <listitem>
316 <para>
317 The user's name. If not set, it'll be extracted from Unix login
318 information, which is usually ok.
319 </para>
320 </listitem>
321 </varlistentry>
322 <varlistentry>
323 <term><literal>email</literal></term>
324 <listitem>
325 <para>
326 The user's email. If not set, it'll be extracted from
327 <literal>$name</literal> and <literal>$domain</literal>.
328 </para>
329 </listitem>
330 </varlistentry>
331 <varlistentry>
332 <term><literal>organization</literal></term>
333 <listitem>
334 <para>
335 Your organization. If not set, it'll be empty.
336 </para>
337 </listitem>
338 </varlistentry>
339 <varlistentry>
340 <term><literal>smtpserver</literal></term>
341 <listitem>
342 <para>
343 The SMTP server to use. If not set, it'll be
344 <literal>smtp.$domain</literal>.
345 </para>
346 </listitem>
347 </varlistentry>
348 <varlistentry>
349 <term><literal>smtpauth</literal></term>
350 <listitem>
351 <para>
352 0 or 1. Whether to authenticate on the SMTP server. If not set, it'll
353 be 0.
354 </para>
355 </listitem>
356 </varlistentry>
357 <varlistentry>
358 <term><literal>smtpuser</literal></term>
359 <listitem>
360 <para>
361 The login on the SMTP server. If not set, it'll be empty (same login as
362 for reception will be used).
363 </para>
364 </listitem>
365 </varlistentry>
366 <varlistentry>
367 <term><literal>smtppass</literal></term>
368 <listitem>
369 <para>
370 The password on the SMTP server. If not set, it'll be empty (if
371 <literal>smtppass</literal> is empty but <literal>smtpuser</literal> is
372 not, the user will be asked for the password).
373 </para>
374 </listitem>
375 </varlistentry>
376 <varlistentry>
377 <term><literal>recvtype</literal></term>
378 <listitem>
379 <para>
380 The type of server to receive from. 0 for POP3, 3 for IMAP4, 5 for a
381 local MBOX file. If not set, it'll be 0 (POP3).
382 </para>
383 </listitem>
384 </varlistentry>
385 <varlistentry>
386 <term><literal>recvserver</literal></term>
387 <listitem>
388 <para>
389 The reception server. If not set, it'll be
390 <literal>(pop|imap).$domain</literal>, depending on
391 <literal>$recvtype</literal>.
392 </para>
393 </listitem>
394 </varlistentry>
395 <varlistentry>
396 <term><literal>recvuser</literal></term>
397 <listitem>
398 <para>
399 The login on the reception server. If not set, it'll be extracted from
400 the Unix login information.
401 </para>
402 </listitem>
403 </varlistentry>
404 <varlistentry>
405 <term><literal>recvpass</literal></term>
406 <listitem>
407 <para>
408 The password on the reception server. If not set, it'll be empty (the
409 user will be asked for it once per session).
410 </para>
411 </listitem>
412 </varlistentry>
413 <varlistentry>
414 <term><literal>imapdir</literal></term>
415 <listitem>
416 <para>
417 The IMAP subdirectory. If not set, it'll be empty, which is often
418 sufficient.
419 </para>
420 </listitem>
421 </varlistentry>
422 <varlistentry>
423 <term><literal>mboxfile</literal></term>
424 <listitem>
425 <para>
426 The MBOX file to receive from if <literal>$recvtype</literal> is 5.
427 If not set, <literal>/var/mail/$LOGIN</literal>.
428 </para>
429 </listitem>
430 </varlistentry>
431 <varlistentry>
432 <term><literal>mailbox</literal></term>
433 <listitem>
434 <para>
435 The MH mailbox to store mail in (for <literal>$recvtype</literal> 0 or
436 5). If not set, it'll be <quote>Mail</quote>.
437 </para>
438 </listitem>
439 </varlistentry>
440 <varlistentry>
441 <term><literal>smtpssl</literal></term>
442 <listitem>
443 <para>
444 0 or 1. Whether to use SSL for sending mail. If not set, it'll be 0.
445 </para>
446 </listitem>
447 </varlistentry>
448 <varlistentry>
449 <term><literal>recvssl</literal></term>
450 <listitem>
451 <para>
452 0 or 1. Whether to use SSL for receiving mail. If not set, it'll be 0.
453 </para>
454 </listitem>
455 </varlistentry>
456 </variablelist>
457 <para>
458 Here are the different variables you can use in the
459 <literal>domain</literal>, <literal>name</literal>,
460 <literal>email</literal>, <literal>organization</literal>,
461 <literal>smtpserver</literal>, <literal>smtpuser</literal>,
462 <literal>smtppass</literal>, <literal>recvserver</literal>,
463 <literal>recvuser</literal>, <literal>recvpass</literal>,
464 <literal>imapdir</literal>, <literal>mboxfile</literal> and
465 <literal>mailbox</literal> fields:
466 </para>
467 <variablelist>
468 <varlistentry>
469 <term><literal>$DEFAULTDOMAIN</literal></term>
470 <listitem>
471 <para>
472 The domain name as extracted from Unix hostname information.
473 Often wrong.
474 </para>
475 </listitem>
476 </varlistentry>
477 <varlistentry>
478 <term><literal>$DOMAIN</literal></term>
479 <listitem>
480 <para>
481 The domain name as set in the domain variable, the first of the
482 template file.
483 </para>
484 </listitem>
485 </varlistentry>
486 <varlistentry>
487 <term><literal>$USERNAME</literal></term>
488 <listitem>
489 <para>The user's real name.</para>
490 </listitem>
491 </varlistentry>
492 <varlistentry>
493 <term><literal>$LOGIN</literal></term>
494 <listitem>
495 <para>The user's Unix login.</para>
496 </listitem>
497 </varlistentry>
498 <varlistentry>
499 <term><literal>$NAME_MAIL</literal></term>
500 <listitem>
501 <para>
502 The user's real name as set in the name variable of the template field,
503 in lowercase and with spaces replaced by dots.
504 <quote>Colin Leroy</quote> becomes <quote>colin.leroy</quote>.
505 </para>
506 </listitem>
507 </varlistentry>
508 <varlistentry>
509 <term><literal>$EMAIL</literal></term>
510 <listitem>
511 <para>
512 The email address as set in the email variable of the template field.
513 </para>
514 </listitem>
515 </varlistentry>
516 </variablelist>
517 <para>
518 Be sure not to use a variable before defining it.
519 </para>
520 </section>
521 <section id="adv_hidden">
522 <title>Hidden preferences</title>
523 <para>
524 There are a number of hidden preferences in Claws Mail, preferences
525 that some users who we wanted to please couldn't live without, but
526 which did not have a place in the GUI in our opinion. You can find the
527 following, and change them while Claws Mail is not running, in
528 <filename>~/.claws-mail/clawsrc</filename>.
529 </para>
530 <para>
531 There's a small tool written in Perl-GTK called Clawsker which
532 provides a user-friendly GUI for tweaking these settings instead of
533 direct editing of <filename>clawsrc</filename>. You can read more
534 about it on the <ulink url="http://www.claws-mail.org/clawsker">Clawsker
535 page</ulink>.
536 </para>
537 <variablelist>
538 <varlistentry>
539 <term><literal>addressbook_use_editaddress_dialog</literal></term>
540 <listitem>
541 <para>
542 Use a separate dialogue to edit a person's details.
543 '0' will use a form embedded in the addressbook's main window.
544 </para>
545 </listitem>
546 </varlistentry>
547 <varlistentry>
548 <term><literal>bold_unread</literal></term>
549 <listitem>
550 <para>
551 Show unread messages in the Message List using a bold font.
552 </para>
553 </listitem>
554 </varlistentry>
555 <varlistentry>
556 <term><literal>cache_max_mem_usage</literal></term>
557 <listitem>
558 <para>
559 The maximum amount of memory to use to cache messages, in kB.
560 </para>
561 </listitem>
562 </varlistentry>
563 <varlistentry>
564 <term><literal>cache_min_keep_time</literal></term>
565 <listitem>
566 <para>
567 The minimum time in minutes to keep a cache in memory. Caches more
568 recent than this time will not be freed, even if the memory usage is
569 too high.
570 </para>
571 </listitem>
572 </varlistentry>
573 <varlistentry>
574 <term><literal>compose_no_markup</literal></term>
575 <listitem>
576 <para>
577 Don't use bold and italic text in Compose dialogue's account selector.
578 </para>
579 </listitem>
580 </varlistentry>
581 <varlistentry>
582 <term><literal>emphasis_color</literal></term>
583 <listitem>
584 <para>
585 The colour used for the X-Mailer line when its value is Claws Mail.
586 </para>
587 </listitem>
588 </varlistentry>
589 <varlistentry>
590 <term><literal>enable_dotted_lines</literal></term>
591 <listitem>
592 <para>
593 Use the <emphasis>old</emphasis> dotted line look in the main window
594 GtkTreeView components, (Folder List and Message List), instead of the
595 <emphasis>modern</emphasis> lineless look.
596 </para>
597 </listitem>
598 </varlistentry>
599 <varlistentry>
600 <term><literal>enable_hscrollbar</literal></term>
601 <listitem>
602 <para>
603 Enable the horizontal scrollbar in the Message List.
604 </para>
605 </listitem>
606 </varlistentry>
607 <varlistentry>
608 <term><literal>enable_swap_from</literal></term>
609 <listitem>
610 <para>
611 Display the sender's email address in the To column of the
612 Sent folder instead of the recipient's.
613 </para>
614 </listitem>
615 </varlistentry>
616 <varlistentry>
617 <term><literal>folderview_vscrollbar_policy</literal></term>
618 <listitem>
619 <para>
620 Specify the policy of vertical scrollbar of Folder List.
621 '0' is always shown, '1' is automatic, '2' is always hidden.
622 </para>
623 </listitem>
624 </varlistentry>
625 <varlistentry>
626 <term><literal>hover_timeout</literal></term>
627 <listitem>
628 <para>
629 Time in milliseconds that will cause a folder tree to expand
630 when the mouse cursor is held over it during drag 'n' drop.
631 </para>
632 </listitem>
633 </varlistentry>
634 <varlistentry>
635 <term><literal>live_dangerously</literal></term>
636 <listitem>
637 <para>
638 Don't ask for confirmation before definitive deletion of emails.
639 </para>
640 </listitem>
641 </varlistentry>
642 <varlistentry>
643 <term><literal>log_error_color</literal></term>
644 <term><literal>log_in_color</literal></term>
645 <term><literal>log_msg_color</literal></term>
646 <term><literal>log_out_color</literal></term>
647 <term><literal>log_warn_color</literal></term>
648 <term><literal>log_status_ok_color</literal></term>
649 <term><literal>log_status_nok_color</literal></term>
650 <term><literal>log_status_skip_color</literal></term>
651 <listitem>
652 <para>
653 The colours used in the log window.
654 </para>
655 </listitem>
656 </varlistentry>
657 <varlistentry>
658 <term><literal>outgoing_fallback_to_ascii</literal></term>
659 <listitem>
660 <para>
661 0 or 1. The outgoing encoding of a message will use 7bit US-ASCII
662 whenever it is suitable for the message content, ignoring the
663 <quote>Outgoing encoding</quote> option unless it is necessary. Turning
664 this option off forces the user-defined encoding to be used, regardless
665 of message content. Default is 1, turned on.
666 </para>
667 </listitem>
668 </varlistentry>
669 <varlistentry>
670 <term><literal>primary_paste_unselects</literal></term>
671 <listitem>
672 <para>
673 0 or 1. Causes the primary buffer to be cleared and the insertion
674 point to be repositioned when the middle mouse button is used
675 for pasting text. Default is 0, turned off.
676 </para>
677 </listitem>
678 </varlistentry>
679 <varlistentry>
680 <term><literal>respect_flowed_format</literal></term>
681 <listitem>
682 <para>
683 0 or 1. Respect format=flowed on text/plain message parts. This
684 will cause some mails to have long lines, but will fix some URLs
685 that would otherwise be wrapped. Default is 0, turned off.
686 </para>
687 </listitem>
688 </varlistentry>
689 <varlistentry>
690 <term><literal>save_parts_readwrite</literal></term>
691 <listitem>
692 <para>
693 Saves temporary files when opening attachment with write bit set.
694 </para>
695 </listitem>
696 </varlistentry>
697 <varlistentry>
698 <term><literal>skip_ssl_cert_check</literal></term>
699 <listitem>
700 <para>
701 Disables the verification of SSL certificates.
702 </para>
703 </listitem>
704 </varlistentry>
705 <varlistentry>
706 <term><literal>statusbar_update_step</literal></term>
707 <listitem>
708 <para>
709 Update stepping in progress bars.
710 </para>
711 </listitem>
712 </varlistentry>
713 <varlistentry>
714 <term><literal>stripes_color_offset</literal></term>
715 <listitem>
716 <para>
717 Specify the value to use when creating alternately coloured lines in
718 GtkTreeView components. The smaller the value, the less visible the
719 difference in the alternating colours of the lines.
720 </para>
721 </listitem>
722 </varlistentry>
723 <varlistentry>
724 <term><literal>textview_cursor_visible</literal></term>
725 <listitem>
726 <para>
727 Display the cursor in the message view.
728 </para>
729 </listitem>
730 </varlistentry>
731 <varlistentry>
732 <term><literal>thread_by_subject_max_age</literal></term>
733 <listitem>
734 <para>
735 Number of days to include a message in a thread when using
736 <quote>Thread using subject in addition to standard headers</quote>.
737 </para>
738 </listitem>
739 </varlistentry>
740 <varlistentry>
741 <term><literal>toolbar_detachable</literal></term>
742 <listitem>
743 <para>
744 Show handles in the toolbars.
745 </para>
746 </listitem>
747 </varlistentry>
748 <varlistentry>
749 <term><literal>two_line_vertical</literal></term>
750 <listitem>
751 <para>
752 Spread message list information over two lines when using the
753 three column layout.
754 </para>
755 </listitem>
756 </varlistentry>
757 <varlistentry>
758 <term><literal>unsafe_ssl_certs</literal></term>
759 <listitem>
760 <para>
761 Allows Claws to remember multiple SSL certificates for a given
762 server/port. This is disabled by default.
763 </para>
764 </listitem>
765 </varlistentry>
766 <varlistentry>
767 <term><literal>use_networkmanager</literal></term>
768 <listitem>
769 <para>
770 Use NetworkManager to switch offline automatically. This is enabled
771 by default.
772 </para>
773 </listitem>
774 </varlistentry>
775 <varlistentry>
776 <term><literal>use_stripes_everywhere</literal></term>
777 <listitem>
778 <para>
779 Enable alternately coloured lines in GtkTreeView components.
780 </para>
781 </listitem>
782 </varlistentry>
783 <varlistentry>
784 <term><literal>use_stripes_in_summaries</literal></term>
785 <listitem>
786 <para>
787 Enable alternately coloured lines in the main window GtkTreeView
788 components, (Folder List and Message List). The only useful way to
789 use this option is to set it to 0 when use_stripes_everywhere is set
790 to 1.
791 </para>
792 </listitem>
793 </varlistentry>
794 <varlistentry>
795 <term><literal>utf8_instead_of_locale_for_broken_mail</literal></term>
796 <listitem>
797 <para>
798 Use UTF-8 encoding for broken mails instead of current locale.
799 </para>
800 </listitem>
801 </varlistentry>
802 <varlistentry>
803 <term><literal>warn_dnd</literal></term>
804 <listitem>
805 <para>
806 Display a confirmation dialogue on drag 'n' drop of folders.
807 </para>
808 </listitem>
809 </varlistentry>
810 </variablelist>
811 </section>
812 <section id="adv_autofaces">
813 <title>Autofaces</title>
814 <para>
815 Claws Mail allows setting the Face and X-Face headers directly
816 from files, either globally for all defined accounts
817 or on a per-account basis. These files must be placed in the
818 <filename>~/.claws-mail/autofaces/</filename> directory.
819 </para>
820 <para>
821 If they exist, the global Face and/or X-Face headers for all
822 accounts are taken from the <filename>face</filename> and/or
823 <filename>xface</filename> files respectively. In a similar
824 manner, Face and/or X-Face headers for a specific account can
825 be provided by <filename>face.</filename><emphasis>accountname</emphasis>
826 and/or <filename>xface.</filename><emphasis>accountname</emphasis>,
827 where <emphasis>accountname</emphasis> is the name of the account you
828 want this header to be associated with.
829 </para>
830 <para>
831 If the name of the account contains characters which may be unsuitable
832 for the underlying filesystem (including spaces) these are replaced by
833 underscores (<quote>_</quote>) when searching for the autofaces of
834 that account. For example, if your account is called
835 <quote><My Mail></quote>, the name for the X-Face filename for
836 that account would be
837 <filename>~/.claws-mail/autofaces/xface._My_Mail_</filename>.
838 Be aware that this feature doesn't check the content of the files,
839 or for duplication of headers, (most mailers, including Claws
840 Mail, will ignore duplicates and display the last one only).
841 </para>
842 </section>
843 </section>