TDE personal information management applications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

configure.docbook 79KB

  1. <chapter id="configure">
  2. <chapterinfo>
  3. <authorgroup>
  4. <author>
  5. <firstname>Daniel</firstname>
  6. <surname>Naber</surname>
  7. <affiliation><address>
  8. <email></email>
  9. </address></affiliation>
  10. </author>
  11. <author>
  12. <firstname>David</firstname>
  13. <surname>Rugge</surname>
  14. <affiliation><address>
  15. <email></email>
  16. </address></affiliation>
  17. </author>
  18. <author>
  19. <firstname>Marc</firstname>
  20. <surname>Mutz</surname>
  21. <affiliation>
  22. <orgname>Klar&auml;lvdalens Datakonsult AB</orgname>
  23. <address>
  24. <email></email>
  25. </address>
  26. </affiliation>
  27. </author>
  28. <author>
  29. <firstname>Michel</firstname>
  30. <surname>Boyer de la Giroday</surname>
  31. <affiliation><address>
  32. <email></email>
  33. </address></affiliation>
  34. </author>
  36. </authorgroup>
  37. <date>2004-07-13</date>
  38. <releaseinfo>1.7</releaseinfo>
  39. </chapterinfo>
  40. <title>Configure &kmail;</title>
  41. <sect1 id="configure-generalinfo">
  42. <title>General Information</title>
  43. <para>&kmail;'s configuration window enables you to configure &kmail;
  44. in many ways. You can reach it via
  45. <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
  46. &kmail;...</guimenuitem></menuchoice>.</para>
  47. <para>It is divided into six
  48. pages, each of them represented by one of the
  49. icons in the list on the left hand side of the dialog. Below the pages
  50. will be described in detail.</para>
  51. <para>The dialog has several buttons:</para>
  52. <variablelist>
  53. <varlistentry>
  54. <term><guibutton>Help</guibutton></term>
  55. <listitem><para>This will open this manual at the appropriate page.</para></listitem>
  56. </varlistentry>
  57. <varlistentry>
  58. <term><guibutton>Defaults</guibutton></term>
  59. <listitem><para>This will reset the configuration options on the current
  60. page back to the default values.</para></listitem>
  61. </varlistentry>
  62. <varlistentry>
  63. <term><guibutton>Load Profile...</guibutton></term>
  64. <listitem><para>This will open a dialog which offers several configuration
  65. profiles. You can use these as starting points for your own configuration.</para></listitem>
  66. </varlistentry>
  67. <varlistentry>
  68. <term><guibutton>Reset</guibutton></term>
  69. <listitem><para>This resets all changes you have made since you last saved
  70. the settings.</para></listitem>
  71. </varlistentry>
  72. <varlistentry>
  73. <term><guibutton>OK</guibutton></term>
  74. <listitem><para>This saves the settings and closes the configuration dialog.</para></listitem>
  75. </varlistentry>
  76. <varlistentry>
  77. <term><guibutton>Apply</guibutton></term>
  78. <listitem><para>This saves the settings without closing the configuration
  79. dialog.</para></listitem>
  80. </varlistentry>
  81. <varlistentry>
  82. <term><guibutton>Cancel</guibutton></term>
  83. <listitem><para>This closes the configuration dialog without saving the
  84. changes you have made.</para></listitem>
  85. </varlistentry>
  86. </variablelist>
  87. </sect1>
  88. <sect1 id="configure-identity">
  89. <title>Identities Page</title>
  90. <para>You can find a quick introduction to the
  91. <guilabel>Identities</guilabel> page in the <link
  92. linkend="getting-started">Getting Started</link> section.</para>
  93. <para>This page allows you to create one or more
  94. <emphasis>Identities</emphasis>, &ie; combinations of name, email
  95. address and other settings. For example, you can create one identity
  96. for business communication and one for
  97. personal communication. If you have more than one email
  98. address, you can create one identity per address. You will then be
  99. able to select an identity on a per-message basis.</para>
  100. <para>The page consists of a list of identities and buttons to manage
  101. them. The identities list will always show at
  102. least one identity, which is then the <guilabel>Default</guilabel>
  103. identity.</para>
  104. <para>To add a new identity to the identity list, click on the
  105. <guibutton>New...</guibutton> button.
  106. The <link linkend="configure-identity-newidentitydialog">New identity</link> dialog
  107. will then appear.</para>
  108. <sect2 id="configure-identity-newidentitydialog">
  109. <title>The <guilabel>New Identity</guilabel> Dialog</title>
  110. <para>You have to enter the name of the new identity into the
  111. <guilabel>New Identity</guilabel> edit field. This will be the name
  112. shown in the identity list.</para>
  113. <para>You can choose how the new identity should be initialized by
  114. checking one of the three radio buttons in the middle of the
  115. dialog:</para>
  116. <variablelist>
  117. <varlistentry>
  118. <term><guilabel>With empty fields</guilabel></term>
  119. <listitem>
  120. <para>All fields of the new identity are cleared or preset with
  121. standard values.</para>
  122. </listitem>
  123. </varlistentry>
  124. <varlistentry>
  125. <term><guilabel>Use Control Center settings</guilabel></term>
  126. <listitem>
  127. <para>Uses the settings of the <application>Control
  128. Center</application>'s default email profile (you can edit that one
  129. under <menuchoice><guimenu>Internet &amp; Network</guimenu>
  130. <guimenuitem>Email</guimenuitem></menuchoice> in the
  131. <application>Control Center</application>).</para>
  132. </listitem>
  133. </varlistentry>
  134. <varlistentry>
  135. <term><guilabel>Duplicate existing identity</guilabel></term>
  136. <listitem>
  137. <para>Copies all fields from an existing identity. You can
  138. choose which identity to copy from by selecting the corresponding
  139. entry in the <guilabel>Existing identities</guilabel> popup.</para>
  140. </listitem>
  141. </varlistentry>
  142. </variablelist>
  143. </sect2>
  144. <sect2 id="configure-identity-general">
  145. <title>General</title>
  146. <para>The <guilabel>General</guilabel> tab allows you to specify some
  147. basic settings for the currently selected identity.</para>
  148. <variablelist>
  149. <varlistentry>
  150. <term><guilabel>Your name</guilabel></term>
  151. <listitem>
  152. <para>Enter your full name here (sometimes also called <emphasis>display name</emphasis>).
  153. Although this field is not strictly mandatory, it is recommended to enter
  154. the correct value here.</para>
  155. </listitem>
  156. </varlistentry>
  157. <varlistentry>
  158. <term><guilabel>Organization</guilabel></term>
  159. <listitem>
  160. <para>Enter your organization here. This field is optional.</para>
  161. </listitem>
  162. </varlistentry>
  163. <varlistentry>
  164. <term><guilabel>Email address</guilabel></term>
  165. <listitem>
  166. <para>Enter your email address here, &ie; something like
  167. <userinput></userinput>.</para>
  168. </listitem>
  169. </varlistentry>
  170. </variablelist>
  171. <example>
  172. <title>Example</title>
  173. <para>So if your address is <replaceable>Joe User
  174. &lt;;</replaceable>, you should enter <userinput>Joe
  175. User</userinput> into the <guilabel>Your name</guilabel> field and
  176. <userinput></userinput> into the <guilabel>Email
  177. address</guilabel> field.</para></example>
  178. </sect2>
  179. <sect2 id="configure-identity-cryptography">
  180. <title>
  181. Cryptography
  182. </title>
  183. <para>
  184. The <guilabel>Cryptography</guilabel> tab allows you to
  185. specify &openpgp; and &smime; keys associated with this
  186. identity, as well as choosing the preferred (cryptographic)
  187. message format to use.
  188. </para>
  189. <variablelist>
  190. <varlistentry id="configure-identity-cryptography-openpgp-sign">
  191. <term>
  192. <guilabel>OpenPGP signing key</guilabel>
  193. </term>
  194. <listitem>
  195. <para>
  196. Here you can select the key to be used when
  197. &openpgp;-signing messages written with this identity in
  198. effect.
  199. </para>
  200. <para>
  201. For brevity, only the short key id of selected keys is
  202. shown. Hovering with the mouse over the key list will
  203. show more information in a tooltip.
  204. </para>
  205. <para>
  206. To clear the label press the
  207. <guibutton>Clear</guibutton> button.
  208. </para>
  209. <para>
  210. To change the selected key, press the
  211. <guibutton>Change...</guibutton> button. A dialog
  212. listing all secret &openpgp; keys will be shown allowing
  213. you to select the one to use.
  214. </para>
  215. </listitem>
  216. </varlistentry>
  217. <varlistentry id="configure-identity-cryptography-openpgp-encrypt">
  218. <term>
  219. <guilabel>OpenPGP encryption key</guilabel>
  220. </term>
  221. <listitem>
  222. <para>
  223. Here you can select the key to &openpgp;-encrypt
  224. messages to when this identity and <xref
  225. linkend="configure-security-composing-encrypt-to-self"/>
  226. are in effect. This key is also used for the <xref
  227. linkend="composer-attach-attach-my-public-key"/>
  228. function of the <link
  229. linkend="the-composer-window">Composer</link>.
  230. </para>
  231. <para>
  232. To change the selected key, press the
  233. <guibutton>Change...</guibutton> button. A dialog
  234. listing all &openpgp; keys found in your keyring will be
  235. shown allowing you to select the one to use.
  236. </para>
  237. <para>
  238. You can clear the list of keys and get more information
  239. about them in the same way as described for <xref
  240. linkend="configure-identity-cryptography-openpgp-sign"/>.
  241. </para>
  242. </listitem>
  243. </varlistentry>
  244. <varlistentry id="configure-identity-cryptography-smime-sign">
  245. <term>
  246. <guilabel>&smime; signing certificate</guilabel>
  247. </term>
  248. <listitem>
  249. <para>
  250. Here you can select the certificate to be used when
  251. &smime;-signing messages written with this identity in
  252. effect.
  253. </para>
  254. <para>
  255. To change the selected certificate, press the
  256. <guibutton>Change...</guibutton> button. A dialog
  257. listing all secret &smime; signing certificates will be
  258. shown allowing you to select the one to use.
  259. </para>
  260. <para>
  261. You can clear the list of certificates and get more
  262. information about them in the same way as described for
  263. <xref linkend="configure-identity-cryptography-openpgp-sign"/>.
  264. </para>
  265. </listitem>
  266. </varlistentry>
  267. <varlistentry id="configure-identity-cryptography-smime-encrypt">
  268. <term>
  269. <guilabel>&smime; encryption certificate</guilabel>
  270. </term>
  271. <listitem>
  272. <para>
  273. Here you can select the certificate to &smime;-encrypt
  274. messages to when this identity and <xref
  275. linkend="configure-security-composing-encrypt-to-self"/>
  276. are in effect.
  277. </para>
  278. <para>
  279. To change the selected certificate, press the
  280. <guibutton>Change...</guibutton> button. A dialog
  281. listing all &smime; encryption certificates found in
  282. your local keybox will be shown allowing you to select
  283. the one to use.
  284. </para>
  285. <para>
  286. You can clear the list of certificates and get more
  287. information about them in the same way as described for
  288. <xref linkend="configure-identity-cryptography-openpgp-sign"/>.
  289. </para>
  290. </listitem>
  291. </varlistentry>
  292. <varlistentry id="configure-identity-cryptography-preferred-format">
  293. <term>
  294. <guilabel>Preferred crypto message format</guilabel>
  295. </term>
  296. <listitem>
  297. <para>
  298. Here you can choose which cryptographic message format
  299. to use by default with this identity.
  300. </para>
  301. <para>
  302. You can either select any of the four formats supported
  303. by &kmail; or leave the option at the recommended
  304. default setting of <guilabel>Any</guilabel>, which will
  305. choose a suitable format based on the recipients of the
  306. message, or might even go so far as to create two copies
  307. of the message, one &smime; signed and/or encrypted, the
  308. other &openpgp; signed and/or encrypted.
  309. </para>
  310. </listitem>
  311. </varlistentry>
  312. </variablelist>
  313. </sect2>
  314. <sect2 id="configure-identity-advanced">
  315. <title>Advanced</title>
  316. <para>The <guilabel>Advanced</guilabel> tab allows you to specify some
  317. rarely used or otherwise specialized settings for the currently
  318. selected identity.</para>
  319. <variablelist>
  320. <varlistentry>
  321. <term><guilabel>Reply-To address</guilabel></term>
  322. <listitem>
  323. <para>Enter the address to which replies to your messages should be
  324. sent. Only fill out this field if it is different from your normal
  325. address (specified using the <guilabel>Name</guilabel> and
  326. <guilabel>Email Address</guilabel> on the <link
  327. linkend="configure-identity-general"><guilabel>General</guilabel>
  328. tab</link>), since replies default to the sender's address
  329. anyway.</para>
  330. <note><para>This field is only useful if you want replies to your mail
  331. to go somewhere else than your regular email address, &eg; if you are
  332. using this identity to send messages from an email address that cannot
  333. receive messages. Note that
  334. some mailing lists overwrite this header field with their post address to
  335. make sure that replies go to the list instead of individuals. So the
  336. usefulness of this field is very limited and it should only be used in
  337. rare cases.</para></note>
  338. </listitem>
  339. </varlistentry>
  340. <varlistentry>
  341. <term><guilabel>BCC address</guilabel></term>
  342. <listitem>
  343. <para>Optionally enter an address to which blind copies of your messages
  344. should be sent to. Note that a BCC is only send to this address, when
  345. <menuchoice><guimenu>View</guimenu><guimenuitem>BCC</guimenuitem></menuchoice>
  346. is activated while composing a message. If you want to send a BCC regardless
  347. of this setting, you should look at the <guilabel>Headers</guilabel> tab of the
  348. <guilabel>Composer</guilabel> page.</para>
  349. </listitem>
  350. </varlistentry>
  351. <varlistentry>
  352. <term><guilabel>Sent-mail folder</guilabel></term>
  353. <listitem>
  354. <para>Select the folder into which messages should be filed after sending
  355. when using this identity. <acronym>IMAP</acronym> users should consider changing this to an
  356. <acronym>IMAP</acronym> folder, so their sent-mail is stored on a server instead of being
  357. stored in a local folder. This way they can access these messages at a
  358. different location.</para>
  359. <tip><para>You can exercise more fine-grained control over where to
  360. file sent messages by creating a corresponding <link
  361. linkend="filters">message filter</link> that is applied to outgoing
  362. messages.</para></tip>
  363. </listitem>
  364. </varlistentry>
  365. <varlistentry>
  366. <term><guilabel>Drafts folder</guilabel></term>
  367. <listitem>
  368. <para>Select the folder into which drafts should be filed when using
  369. this identity. <acronym>IMAP</acronym> users should consider changing this to an
  370. <acronym>IMAP</acronym> folder, so their drafts are stored on a server instead of being
  371. stored in a local folder. This way they can easily continue to work
  372. on their drafts at a different location.</para>
  373. </listitem>
  374. </varlistentry>
  375. <varlistentry>
  376. <term><guilabel>Special transport</guilabel></term>
  377. <listitem>
  378. <para>Select or enter an alternative SMTP server to be used when sending
  379. messages using this identity.</para>
  380. <note><para>You need to configure outgoing mail servers first, before
  381. you can choose them from the list. You can do this on the <link
  382. linkend="configure-accounts-sending"><guilabel>Sending</guilabel>
  383. tab</link> of the <link linkend="configure-accounts">
  384. <guilabel>Accounts</guilabel> page</link>.</para></note>
  385. </listitem>
  386. </varlistentry>
  387. </variablelist>
  388. </sect2>
  389. <sect2 id="configure-identity-signature">
  390. <title>Signature</title>
  391. <para>This tab allows you to specify a signature (sometimes called
  392. <quote>footer</quote> or <quote>disclaimer</quote>)
  393. to be appended to each message sent using this identity.</para>
  394. <note><para>This type of signature has nothing to do with the
  395. (digital) signatures for which you can select the keys to use on
  396. the <link linkend="configure-identity-cryptography">Cryptography</link>
  397. tab. It is just bad wording to call this a signature, but since
  398. the term is already used everywhere else, we keep this notation. Just
  399. keep in mind that these signatures and digital signatures are two
  400. completely different things.</para></note>
  401. <para>Check the <guilabel>Enable signature</guilabel> option if you
  402. want to be able to append the signature when using this identity. To
  403. <emphasis>automatically</emphasis> append it to every new message
  404. you also have to select <guilabel>Automatically append
  405. signature</guilabel> in the <guilabel>Composer</guilabel> configuration page.</para>
  406. <para>&kmail; can obtain the signature text from various sources. The
  407. traditional way on Unix is to read the text from a file called
  408. <filename>.signature</filename> in your home folder. This file can
  409. be shared between several programs, so you get the same
  410. signature in each mail program you use.</para>
  411. <para>To read the text from a text file you select
  412. <guilabel>Obtain signature text from file</guilabel>. Enter the
  413. filename in the <guilabel>Specify file</guilabel> edit field or hit
  414. the button to the right of it to browse your filesystem. If you want
  415. to edit the file, hit the <guilabel>Edit File</guilabel>
  416. button.</para>
  417. <para>&kmail; can also read the signature text from the output of a
  418. command. Thus, you can use programs such as
  419. <command>fortune</command> to create a new signature text for
  420. every message. Everything the program prints onto
  421. <acronym>stdout</acronym> is caught and used as the signature
  422. text.</para>
  423. <para>To read the text from the output of a command you select
  424. <guilabel>Obtain signature text from Output of
  425. Command</guilabel>. Enter the command (preferably with full path) in
  426. the <guilabel>Specify command</guilabel> edit field.</para>
  427. <para>As a third option, you can enter the signature text directly in
  428. &kmail;'s configuration dialog. To do this, select <guilabel>Obtain
  429. signature text from input field below</guilabel> and enter the text
  430. into the appearing text box.</para>
  431. <note><para>On the Internet, signatures are by convention separated
  432. from the body of the message by a line containing only the three
  433. character <quote>-- </quote> (dash, dash, space). &kmail; will
  434. automatically prepend the signature text with this line if it is not
  435. already present in the signature text.</para>
  436. <para>If you do not wish the separator to be prepended
  437. automatically by &kmail;, simply add it to the signature
  438. text yourself.</para>
  439. </note>
  440. </sect2>
  441. </sect1>
  442. <sect1 id="configure-accounts">
  443. <title>Accounts Page</title>
  444. <para>You can find a quick introduction to the
  445. <guilabel>Accounts</guilabel> page in the <link
  446. linkend="setting-up-your-account">Setting up your Account</link>
  447. section.</para>
  448. <para>This page allows you to create one or more (incoming and
  449. outgoing) <emphasis>accounts</emphasis>, &ie; combinations of mail
  450. servers, login information and other settings. Typically, you will
  451. create one outgoing (used for sending messages) and one incoming (used to
  452. retrieve messages) account. You can create as many accounts as you want, though,
  453. and assign each one to different <link
  454. linkend="configure-identity">identities</link> or decide on a per-message
  455. basis.</para>
  456. <sect2 id="configure-accounts-sending">
  457. <title>Sending</title>
  458. <para>The <guilabel>Sending</guilabel> tab allows you to define new
  459. outgoing mail servers and set some common options.</para>
  460. <para>For basic information, see <link
  461. linkend="sending-mail">Setting up your Account: Sending</link>.</para>
  462. <para>When you click <guibutton>Add...</guibutton> or
  463. <guibutton>Modify...</guibutton> the <guilabel>Add
  464. transport</guilabel> or <guilabel>Modify transport</guilabel> dialogs
  465. will open respectively. For sending via <application>sendmail</application>
  466. or similar programs
  467. you can specify a name and the location of the
  468. <command>sendmail</command> program. For <acronym>SMTP</acronym> you
  469. can specify <guilabel>Name</guilabel>, <guilabel>Host</guilabel>, and
  470. <guilabel>Port</guilabel> of the server. <guilabel>Server requires
  471. authentication</guilabel> will enable the <guilabel>Login</guilabel>
  472. and <guilabel>Password</guilabel> fields and the
  473. <guilabel>Authentication method</guilabel> buttons on the
  474. <guilabel>Security</guilabel> tab. If you are not sure about the
  475. security settings you can make &kmail; test for the best settings by
  476. using <guibutton>Check What the Server Supports</guibutton>.</para>
  477. <para><guilabel>Confirm before send</guilabel> will pop up a
  478. confirmation box every time you send a message.</para>
  479. <para><guilabel>Send messages in outbox folder</guilabel> lets you specify
  480. when queued messages, &ie; messages in the outbox folder pending to be sent,
  481. should be sent. You can choose between:</para>
  482. <variablelist>
  483. <varlistentry>
  484. <term><guilabel>Never Automatically</guilabel></term>
  485. <listitem><para>Queued messages will only be sent if you select
  486. <menuchoice><guimenu>File</guimenu><guimenuitem>Send queued messages</guimenuitem></menuchoice>.</para></listitem>
  487. </varlistentry>
  488. <varlistentry>
  489. <term><guilabel>On Manual Mail Checks</guilabel></term>
  490. <listitem><para>Queued messages will be sent after you have manually checked
  491. for new mail, &eg; with <menuchoice><guimenu>File</guimenu><guimenuitem>Check Mail</guimenuitem></menuchoice>. Of course, you can also
  492. manually send the queued messages with
  493. <menuchoice><guimenu>File</guimenu><guimenuitem>Send queued messages</guimenuitem></menuchoice>.</para></listitem>
  494. </varlistentry>
  495. <varlistentry>
  496. <term><guilabel>On All Mail Checks</guilabel></term>
  497. <listitem><para>Queued messages will be sent after all checks for new mail,
  498. &ie; after automatic mail checks as well as after manual mail checks.
  499. Of course, you can also manually send the queued messages with
  500. <menuchoice><guimenu>File</guimenu><guimenuitem>Send queued messages</guimenuitem></menuchoice>.</para></listitem>
  501. </varlistentry>
  502. </variablelist>
  503. <para><guilabel>Default send method</guilabel> lets you define what
  504. happens when a message is sent. If <guilabel>Send now</guilabel> is
  505. selected, the message is sent to the mail server immediately, while if
  506. <guilabel>Send later</guilabel> is selected, the message is queued in
  507. the outbox to be sent later with the
  508. <menuchoice><guimenu>File</guimenu><guimenuitem>Send
  509. Queued Messages</guimenuitem></menuchoice> command or automatically when you
  510. check your mail, depending on the setting of
  511. <guilabel>Send messages in outbox folder</guilabel> above.</para>
  512. <para><guilabel>Message property</guilabel> lets you select how your
  513. message will be encoded when it is sent. <guilabel>Allow
  514. 8-bit</guilabel> means that &kmail; will send your message in 8-bit
  515. <acronym>ASCII</acronym>, which means that all special characters such
  516. as accented letters will be sent as-is. If <guilabel>MIME Compliant
  517. (Quoted Printable)</guilabel> is selected, special characters will be
  518. encoded using standard &MIME; encodings, which may be more portable to
  519. mailing systems other than 8-bit <acronym>ASCII</acronym>.
  520. We recommend to use <guilabel>MIME Compliant</guilabel>.</para>
  521. <note><para>Even with <guilabel>Allow 8-bit</guilabel>
  522. selected &kmail; will use <guilabel>MIME
  523. Compliant</guilabel> encoding in some situations, for
  524. example for sending cryptographically signed messages.</para></note>
  525. <para><guilabel>Default domain</guilabel> lets you specify which domain name
  526. should be used to complete email addresses that only consist of the recipient's user
  527. name. For example when you set the default domain to <replaceable></replaceable>
  528. then messages you send to <replaceable>johndoe</replaceable> will be sent to
  529. <replaceable></replaceable>.</para>
  530. </sect2>
  531. <sect2 id="configure-accounts-receiving">
  532. <title>Receiving</title>
  533. <para>For basic information, see <link
  534. linkend="receiving-mail">Setting up your Account: Receiving</link>.</para>
  535. <para><guilabel>Check mail on startup</guilabel> lets you specify whether
  536. KMail should check for new mail immediately after it has been started.</para>
  537. <para>With <guilabel>New Mail Notification</guilabel> you can set
  538. how &kmail; will notify you if new messages have arrived:
  539. <guilabel>Beep</guilabel> will play a short beep sound;
  540. if <guilabel>Detailed new mail notification</guilabel> is enabled then
  541. &kmail; will show the number of new messages for each folder provided
  542. you have chosen to be notified with a dialog. More advanced
  543. notification options, like showing a dialog or running a certain command,
  544. are available via the <guibutton>Other Actions</guibutton> button.</para>
  545. </sect2>
  546. </sect1>
  547. <sect1 id="configure-appearance">
  548. <title>Appearance Page</title>
  549. <sect2 id="configure-appearance-fonts">
  550. <title>Fonts</title>
  551. <para>This section allows you to change the type, size and character set of the
  552. display fonts. <guilabel>Message Body</guilabel> sets the font for
  553. the reader pane, <guilabel>Composer</guilabel> sets the font for
  554. writing messages in the composer window.<!-- fixme in kmail: better wording? -->
  555. There is a separate entry for <guilabel>Message List - Date Field</guilabel>
  556. so you can choose a monospaced font for the date field for better readability.</para>
  557. </sect2>
  558. <sect2 id="configure-appearance-colors">
  559. <title>Colors</title>
  560. <para>This section allows you to change the color of the text.
  561. <guilabel>Recycle colors on deep quoting</guilabel> means that even text that is
  562. quoted more than three times will appear in color. Note that the
  563. <guilabel>Quoted text</guilabel> colors only work in the message reader, not in
  564. the composer. If you want folders which are close to their quota
  565. (space allotment, usually used on IMAP servers) to be displayed in a different color,
  566. you can specify a percentage value as a threshold for this. The color to be used
  567. can be configured along with the other custom colors.<!-- TODO --></para>
  568. </sect2>
  569. <sect2 id="configure-appearance-layout">
  570. <title>Layout</title>
  571. <para>If the <guilabel>Close message window after replying or forwarding</guilabel> option is
  572. activated, KMail will close the message window after replying to or forwarding the message that
  573. is displayed in the window. This only applies to the separate message window, not to the embedded
  574. message preview pane.</para>
  575. <para><guilabel>Show HTML status bar</guilabel> activates a bar at the left side of the reader
  576. pane that tells you if a message is &html; or not. This is important because
  577. &html; messages might imitate the look of a signed and encrypted message, so
  578. you should be aware of the fact that you are reading a &html; message. The &html;
  579. status bar itself cannot be influenced by the &html; code of the message.</para>
  580. <para>The <guilabel>Window Layout</guilabel> section lets you choose the
  581. layout of the main window. You can choose where you want the
  582. <guilabel>Message Preview Pane</guilabel> or choose not to have
  583. it at all.</para>
  584. <para>The <guilabel>Message Structure Viewer</guilabel> option lets you choose when
  585. the structure viewer will be shown: the structure viewer is a part of the main window that
  586. lets you access all parts of a message. <guilabel>Show never</guilabel> will
  587. disable the structure viewer (note that you can still access attachments as icons),
  588. <guilabel>Show always</guilabel> will show the structure viewer even if there is only
  589. one plaintext part. <guilabel>Show only for non-plaintext messages</guilabel> will
  590. display the structure viewer only if it makes sense, &ie; if the current message
  591. has attachments or has &html; parts.</para>
  592. </sect2>
  593. <sect2 id="configure-appearance-headers">
  594. <title>Headers</title>
  595. <para>With <guilabel>Display message sizes</guilabel> selected there will be another
  596. column in the header pane that shows the messages' size.</para>
  597. <para><guilabel>Show crypto icons</guilabel> will add more status information
  598. to the <guilabel>Subject</guilabel> columns in the header pane: every message
  599. that has been signed will have a small <guiicon>Signed</guiicon> icon in front
  600. of the subject, every message that has been encrypted will have a small
  601. <guiicon>Encrypted</guiicon> icon in front of the subject. Note that you have
  602. to select a message once before these icons will appear, until then only
  603. question marks will be displayed.</para>
  604. <para><guilabel>Thread list of message headers</guilabel> will put all the messages
  605. in the header pane in a kind of tree list, so that the replies to a message are
  606. directly below that message.</para>
  607. <para>With <guilabel>Message header threading options</guilabel> you can select
  608. whether threads should appear expanded (<guilabel>open</guilabel>) by
  609. default or whether they should be collapsed (<guilabel>closed</guilabel>).
  610. You can of course still open/close threads using the <guilabel>+</guilabel>/<guilabel>-</guilabel>
  611. buttons.</para>
  612. <para>With <guilabel>Date Display</guilabel> you can choose between several
  613. date formats. The <guilabel>Localized Format</guilabel> is the one you can
  614. specify under <guilabel>Country &amp; Language</guilabel> in &kcontrol;.
  615. For the <guilabel>Custom</guilabel> format you can get
  616. a description of the possible values by pressing
  617. <keycombo action="simul">&Shift;<keycap>F1</keycap></keycombo>
  618. and then clicking on <guilabel>Custom</guilabel> option.</para>
  619. </sect2>
  620. <sect2 id="configure-appearance-systemtray">
  621. <title>System Tray</title>
  622. <para>If you enable the system tray icon then a small &kmail; icon with the
  623. number of unread messages will be shown in the system tray. You can enable
  624. &kmail;'s system tray icon with <guilabel>Enable system tray icon</guilabel>,
  625. and with <guilabel>System Tray Mode</guilabel>
  626. you can specify whether the tray icon should always be shown or only if
  627. you have unread messages.</para>
  628. <para>If the icon is visible then you can hide &kmail;'s main window by
  629. clicking on the icon or by clicking on the window close button. By clicking
  630. on the icon you can make &kmail;'s main window visible again.
  631. If you click on the icon with the <mousebutton>right</mousebutton>
  632. mousebutton then you get a menu with a few useful commands. You can check
  633. for new mail, create a new message or quit &kmail;. Additionally, there is
  634. the entry <guilabel>New Messages In</guilabel> which lists all folders
  635. containing unread messages. If you choose one of those folders then this
  636. folder will be selected in &kmail;'s main window.
  637. </para>
  638. </sect2>
  639. <!-- fixme?: date + less than/greater than broken in kmail? -->
  640. <!-- fixme?: "group" wording in program -->
  641. </sect1>
  642. <sect1 id="configure-composer">
  643. <title>
  644. Composer Page
  645. </title>
  646. <sect2 id="configure-composer-general">
  647. <title>
  648. General
  649. </title>
  650. <variablelist>
  651. <varlistentry id="configure-composer-general-append-signature">
  652. <term>
  653. <guilabel>Automatically append signature</guilabel>
  654. </term>
  655. <listitem>
  656. <para>
  657. If checked, your signature as defined in the <link
  658. linkend="configure-identity-signature">identity
  659. page</link> is automatically included at the end of
  660. all messages you create (&ie; new messages, replies, &etc;).
  661. </para>
  662. </listitem>
  663. </varlistentry>
  664. <varlistentry id="configure-composer-general-smart-quoting">
  665. <term>
  666. <guilabel>Use smart quoting</guilabel>
  667. </term>
  668. <listitem>
  669. <para>
  670. If checked, &kmail; will break long lines but will try
  671. to keep the correct quoting (&eg; the <quote>&gt;
  672. </quote> will always be at the start of the line).
  673. </para>
  674. </listitem>
  675. </varlistentry>
  676. <varlistentry id="configure-composer-general-quote-selection-only">
  677. <term>
  678. <guilabel>Only quote selected text when repyling</guilabel>
  679. </term>
  680. <listitem>
  681. <para>
  682. If checked, &kmail; will quote only the selected text in the message window,
  683. instead of the complete message, when replying.
  684. With this, it is possible to quickly generate replies that quote only the relevant
  685. paragraph to which you are actually replying, and omits the other paragraphs that are
  686. not relevant to the context.
  687. </para>
  688. </listitem>
  689. </varlistentry>
  690. <varlistentry id="configure-composer-general-strip-signatures">
  691. <term>
  692. <guilabel>Remove the signature when replying</guilabel>
  693. </term>
  694. <listitem>
  695. <para>
  696. If checked, &kmail; will remove the signature from the quoted text
  697. when replying to a message. This is useful since it reduces the amount
  698. of quoted text, which makes it easier to read the reply.
  699. </para>
  700. </listitem>
  701. </varlistentry>
  702. <varlistentry id="configure-composer-general-auto-request-mdns">
  703. <term>
  704. <guilabel>Automatically request message disposition notifications</guilabel>
  705. </term>
  706. <listitem>
  707. <para>
  708. If checked, <xref
  709. linkend="composer-options-request-mdn"/> will default to
  710. <emphasis>on</emphasis>. Check this option only if you
  711. know what you are doing. &mdn;s are considered a
  712. nuisance (or are simply ignored) by a lot of people. It
  713. is better to decide to request them on a
  714. message-by-message basis.
  715. </para>
  716. </listitem>
  717. </varlistentry>
  718. <varlistentry id="configure-composer-general-word-wrap">
  719. <term>
  720. <guilabel>Word wrap at column</guilabel>
  721. </term>
  722. <listitem>
  723. <para>
  724. Lets you turn word wrapping on and off in the composer
  725. window and lets you set the column at which words will
  726. be wrapped (you probably should not need to change the
  727. default value, which is <literal>78</literal>).
  728. </para>
  729. </listitem>
  730. </varlistentry>
  731. <varlistentry id="configure-composer-general-too-many-recipients">
  732. <term>
  733. <guilabel>Warn if the number of recipients is larger than</guilabel>
  734. </term>
  735. <listitem>
  736. <para>
  737. If the number of recipients is larger than this value, KMail will
  738. warn and ask for a confirmation before sending the mail.
  739. The default is to warn if there are more than <literal>5</literal> recipients.
  740. This warning can be turned off.
  741. </para>
  742. </listitem>
  743. </varlistentry>
  744. <varlistentry id="configure-composer-general-autosave-interval">
  745. <term>
  746. <guilabel>Autosave interval</guilabel>
  747. </term>
  748. <listitem>
  749. <para>
  750. A backup copy of the text in the composer window can be created
  751. regularly. This option lets you specify the interval used to
  752. create the backup. You can disable autosaving by setting it to
  753. the value <literal>0</literal>.
  754. </para>
  755. </listitem>
  756. </varlistentry>
  757. <varlistentry id="configure-composer-general-forwading-type">
  758. <term>
  759. <guilabel>Default Forwarding Type</guilabel>
  760. </term>
  761. <listitem>
  762. <para>
  763. Lets you decide whether you want to forward messages inline or as an attachment by default.
  764. This changes which type of forwarding mechanism is used when you click the toolbar icon or
  765. when you activate the shortcut for forwarding.
  766. </para>
  767. </listitem>
  768. </varlistentry>
  769. <varlistentry id="configure-composer-general-external-editor">
  770. <term>
  771. <guilabel>External Editor</guilabel>
  772. </term>
  773. <listitem>
  774. <para>
  775. If you do not like the Composer you can use a different
  776. editor. Note that the composer window will still open
  777. and the external editor will open as soon as you type
  778. just one character in the body of the message. If you are
  779. done, save the text and exit the editor. The text will
  780. now appear in the composer window, where you can send
  781. it. Note that your editor may not return immediately,
  782. you have to use &eg;
  783. <userinput>
  784. <command>
  785. gvim <option>-f</option> <varname>%f</varname>
  786. </command>
  787. </userinput> for <application>gvim</application>.
  788. </para>
  789. </listitem>
  790. </varlistentry>
  791. </variablelist>
  792. </sect2>
  793. <sect2 id="configure-composer-phrases">
  794. <title>Phrases</title>
  795. <para>The <guilabel>Phrases</guilabel> tab lets you define the automatically
  796. generated lines that are added to message replies, forwarded messages, and the
  797. character that is added in front of quoted text.
  798. There are special &percnt;-denoted characters that will insert certain
  799. values, which are also displayed at the top of the <guilabel>Phrases</guilabel> section.
  800. You can add reply phrases in languages other than
  801. your default &kde; language using the <guibutton>Add...</guibutton> button.
  802. You can then choose between different languages with the
  803. <guilabel>Language</guilabel> drop down box.
  804. This will only work for languages whose i18n package you have installed.</para>
  805. </sect2>
  806. <sect2 id="configure-composer-subject">
  807. <title>Subject</title>
  808. <para>This section contains a list of prefixes for <quote>Reply</quote> and
  809. <quote>Forward</quote>. If you receive messages that use prefixes different
  810. to the standard ones, you can add them here so &kmail; will recognize
  811. them. This way &kmail; can ignore them for sorting messages and
  812. when setting the subject of a reply or a forwarded messages, and optionally
  813. replace them with <quote>Re:</quote> or <quote>Fwd:</quote>
  814. respectively.</para>
  815. </sect2>
  816. <sect2 id="configure-composer-charset">
  817. <title>Charset</title>
  818. <para>Here you can manage the default charsets used for your own messages.
  819. Every message you send will be checked if it is written in one of the listed
  820. charsets, starting at the top of the list. If it is, this charset will be used.
  821. If it is not, a dialog will show up and tell you that you manually have to choose
  822. a charset using
  823. <menuchoice><guimenu>Options</guimenu><guisubmenu>Set Encoding</guisubmenu></menuchoice>.
  824. </para>
  825. <para>If you select <guilabel>Keep original charset when replying
  826. or forwarding (if possible)</guilabel>, the original message's charset
  827. will be kept, unless there are now characters that cannot be
  828. represented using that charset.</para>
  829. </sect2>
  830. <sect2 id="configure-composer-headers">
  831. <title>Headers</title>
  832. <para>Check the <guilabel>Use custom message-id suffix</guilabel>
  833. checkbox if you want &kmail; to generate Message-Id's with a custom
  834. suffix. Enter the desired suffix in the <guilabel>Custom message-id
  835. suffix</guilabel> field. Please make sure that the suffix that you
  836. specify is world-wide unique. The best thing is to use the name of a
  837. domain which you are the owner of. If you do not check <guilabel>Use
  838. custom Message-Id suffix</guilabel> then &kmail; will automatically
  839. generate the complete Message-Id. If you do not know what this is all
  840. about do not check this option.</para>
  841. <para>The <guilabel>Define custom mime header fields</guilabel> list
  842. sets the headers that &kmail; will use for its outgoing messages. You
  843. can both invent new fields and overwrite existing ones. This feature
  844. is only useful for advanced users.</para>
  845. </sect2>
  846. <sect2 id="configure-composer-attachments">
  847. <title>Attachments</title>
  848. <para>If you have to send attachments with filenames containing non-English
  849. characters to users of Outlook(TM) or Outlook Express(TM) then you might want
  850. to check the <guilabel>Outlook-compatible attachment naming</guilabel> option.
  851. &kmail; will then encode the attachment names in a non-standard way that is
  852. understood by Outlook(TM).</para>
  853. <para>Note that &kmail; will create non-standard compliant messages, and
  854. consequently it is possible that your messages will not be understood by
  855. standard-compliant mail clients. So, unless you have no other choice, you
  856. should not enable this option.</para>
  857. <para>Check the <guilabel>Enable detection of missing attachments</guilabel>
  858. checkbox if you want &kmail; to warn you whenever you are about to send a
  859. message without attachments although the message text contains certain
  860. words which indicate that you wanted to include an attachment. The list
  861. of key words can be modified.</para>
  862. </sect2>
  863. </sect1>
  864. <sect1 id="configure-security">
  865. <title>
  866. Security Page
  867. </title>
  868. <sect2 id="configure-security-reading">
  869. <title>
  870. Reading
  871. </title>
  872. <para>
  873. On this tab you can configure security-relevant options for
  874. reading messages.
  875. </para>
  876. <variablelist>
  877. <varlistentry id="configure-security-reading-prefer-html">
  878. <term>
  879. <guilabel>Prefer HTML to plain text</guilabel>
  880. </term>
  881. <listitem>
  882. <para>
  883. If checked, &kmail; will show &html; messages with their
  884. &html; formatting and layout. We strongly recommend to
  885. leave this option off, as security problems with &html;
  886. might show up. When this option is off, you can still
  887. read &html; messages, but only as plain text.
  888. </para>
  889. </listitem>
  890. </varlistentry>
  891. <varlistentry id="configure-security-reading-external-references">
  892. <term>
  893. <guilabel>Allow messages to load external references from the Internet</guilabel>
  894. </term>
  895. <listitem>
  896. <para>
  897. If checked, &kmail; can load external images, style
  898. sheets &etc; from the Internet when you look at an
  899. &html; message. We strongly recommend to leave this
  900. option off (although it has no effect if you only view
  901. plain text messages). By adding external references to
  902. their messages, people sending spam can detect that and
  903. when you have looked at their message. Note that this
  904. option has no effect on &Java;, JavaScript and Plugins -
  905. these are disabled anyway and cannot be enabled at all.
  906. </para>
  907. </listitem>
  908. </varlistentry>
  909. <varlistentry id="configure-security-reading-mdns">
  910. <term>
  911. <guilabel>Message Disposition Notifications</guilabel>
  912. </term>
  913. <listitem>
  914. <para>
  915. &mdn;s are a generalization of what is commonly called a
  916. <quote>read receipt</quote>. The message author requests
  917. a disposition notification to be sent and the receiver's
  918. mail program generates a reply from which the author can
  919. learn what happened to his message. Common disposition
  920. types include <quote>displayed</quote> (&ie; read),
  921. <quote>deleted</quote> and <quote>dispatched</quote>
  922. (&eg; forwarded).
  923. </para>
  924. <para>
  925. The following options (listed as <guilabel>Send
  926. policy</guilabel>) are available to control
  927. <emphasis>when</emphasis> &kmail; sends &mdn;s:
  928. </para>
  929. <variablelist>
  930. <varlistentry>
  931. <term>
  932. <guilabel>Ignore</guilabel> (recommended)
  933. </term>
  934. <listitem>
  935. <para>
  936. Ignores any request for disposition
  937. notifications. No &mdn; will ever be sent
  938. automatically.
  939. </para>
  940. </listitem>
  941. </varlistentry>
  942. <varlistentry>
  943. <term>
  944. <guilabel>Ask</guilabel>
  945. </term>
  946. <listitem>
  947. <para>
  948. Answers requests only after asking the user for
  949. permission. This way, you can send &mdn;s for
  950. selected messages while denying or ignoring them
  951. for others.
  952. </para>
  953. </listitem>
  954. </varlistentry>
  955. <varlistentry>
  956. <term>
  957. <guilabel>Deny</guilabel>
  958. </term>
  959. <listitem>
  960. <para>
  961. Always sends a <quote>denied</quote>
  962. notification. This is only
  963. <emphasis>slightly</emphasis> better than always
  964. sending &mdn;s. The author will still know that
  965. the messages has been acted upon, he just cannot
  966. tell whether it was deleted or read &etc;
  967. </para>
  968. </listitem>
  969. </varlistentry>
  970. <varlistentry>
  971. <term>
  972. <guilabel>Always send</guilabel>
  973. </term>
  974. <listitem>
  975. <para>
  976. Always sends the requested disposition
  977. notification. That means that the author of the
  978. message gets to know when the message was acted
  979. upon and, in addition, what happened to it
  980. (displayed, deleted, &etc;). This option is
  981. strongly discouraged, but since it makes sense
  982. where privacy is not a concern, &eg; in customer
  983. relationship management, it has been made
  984. available.
  985. </para>
  986. </listitem>
  987. </varlistentry>
  988. </variablelist>
  989. <para>
  990. If you are unsure, experiment a while with
  991. <guilabel>Ask</guilabel> and if you find &kmail;s
  992. questions annoying, switch to <guilabel>Ignore</guilabel>.
  993. </para>
  994. <para>
  995. The following options (listed as <guilabel>Quote
  996. original message</guilabel>) are available to control
  997. <emphasis>how much</emphasis> of the original message
  998. &kmail; sends back in &mdn;s.
  999. </para>
  1000. <variablelist>
  1001. <varlistentry>
  1002. <term>
  1003. <guilabel>Nothing</guilabel>
  1004. </term>
  1005. <listitem>
  1006. <para>
  1007. No parts of the message other than the mandatory
  1008. message-id and the original recipient is included
  1009. in the &mdn; reply. This preserves enough
  1010. information for the sender to find the message in
  1011. his sent messages for which this &mdn; was
  1012. generated.
  1013. </para>
  1014. </listitem>
  1015. </varlistentry>
  1016. <varlistentry>
  1017. <term>
  1018. <guilabel>Full message</guilabel>
  1019. </term>
  1020. <listitem>
  1021. <para>
  1022. Attaches the complete message to the disposition
  1023. notification. Usually, this is overkill. It does
  1024. not add any valuable information that cannot be
  1025. deduced from the message headers alone, but people
  1026. sometimes insist on this, since it is much easier
  1027. for humans to correlate the content of the message
  1028. than just the headers to what they sent earlier.
  1029. </para>
  1030. </listitem>
  1031. </varlistentry>
  1032. <varlistentry>
  1033. <term>
  1034. <guilabel>Only headers</guilabel>
  1035. </term>
  1036. <listitem>
  1037. <para>
  1038. Attaches only the headers to the disposition
  1039. notification. This is usually enough to enable
  1040. both humans (by subject) and computers (by
  1041. message-id) to easily correlate &mdn; and original
  1042. message.
  1043. </para>
  1044. </listitem>
  1045. </varlistentry>
  1046. </variablelist>
  1047. <para>
  1048. If unsure, leave the option at the default.
  1049. </para>
  1050. </listitem>
  1051. </varlistentry>
  1052. <varlistentry>
  1053. <term>
  1054. <guilabel>Do not send MDNs in response to encrypted messages</guilabel>
  1055. </term>
  1056. <listitem>
  1057. <para>
  1058. This option suppresses the sending of &mdn;s if the
  1059. message is encrypted (partially or in whole). This
  1060. thwarts attempts to use &kmail;'s &mdn; feature as an
  1061. <emphasis>oracle</emphasis> to deduce whether you were
  1062. able to decrypt the message or not.
  1063. </para>
  1064. <para>
  1065. Strictly speaking, this option is not needed, since
  1066. &kmail; sends &mdn;s regardless of whether the message
  1067. could be successfully decrypted or not (the disposition
  1068. notification request resides in the unencrypted part of
  1069. the message), but it gives the security-conscious user
  1070. the choice to either send them always if requested
  1071. (option unchecked), or never (option checked).
  1072. </para>
  1073. <para>
  1074. If unsure, leave the option checked.
  1075. </para>
  1076. </listitem>
  1077. </varlistentry>
  1078. <varlistentry>
  1079. <term>
  1080. <guilabel>Automatically import keys and certificates</guilabel>
  1081. </term>
  1082. <listitem>
  1083. <para>
  1084. If checked, &kmail; automatically imports any attachments
  1085. containing &openpgp; keys into your local keyring, and any
  1086. attachments containing &smime; keys into your local key
  1087. box.
  1088. </para>
  1089. <note>
  1090. <para>
  1091. Verifying &smime; signatures always involves importing
  1092. the contained certificates. This option thus does not
  1093. affect this. It is also unrelated to &gpg;'s
  1094. <option>auto-key-retrieve</option> feature, where &gpg;
  1095. will try to import unknown keys from a key server.
  1096. </para>
  1097. </note>
  1098. </listitem>
  1099. </varlistentry>
  1100. </variablelist>
  1101. </sect2>
  1102. <sect2 id="configure-security-composing">
  1103. <title>
  1104. Composing
  1105. </title>
  1106. <para>
  1107. On this tab you can configure security-relevant options for
  1108. composing messages.
  1109. </para>
  1110. <variablelist>
  1111. <varlistentry id="configure-security-composing-automatically-sign">
  1112. <term>
  1113. <guilabel>Automatically sign messages</guilabel>
  1114. </term>
  1115. <listitem>
  1116. <para>
  1117. If checked, the <xref
  1118. linkend="composer-options-sign-message"/> option in the
  1119. composer will default to <emphasis>on</emphasis>.
  1120. </para>
  1121. <para>
  1122. However, you can still switch it on and off on a
  1123. per-message basis.
  1124. </para>
  1125. </listitem>
  1126. </varlistentry>
  1127. <varlistentry id="configure-security-composing-encrypt-to-self">
  1128. <term>
  1129. <guilabel>Always encrypt to self</guilabel>
  1130. </term>
  1131. <listitem>
  1132. <para>
  1133. If checked, any message that is encrypted to the
  1134. recipients will additionally be encrypted to yourself.
  1135. </para>
  1136. <warning>
  1137. <para>
  1138. If you uncheck this option, you may not be able to
  1139. decrypt the messages written by yourself and encrypted
  1140. to other people anymore.
  1141. </para>
  1142. </warning>
  1143. </listitem>
  1144. </varlistentry>
  1145. <varlistentry id="configure-security-composing-store-sent-encrypted">
  1146. <term>
  1147. <guilabel>Store sent messages encrypted</guilabel><!--
  1148. --><footnote>
  1149. <para>
  1150. This options enables a mode of using mail encryption
  1151. that is sometimes (misleadingly) called
  1152. <quote>transport-only</quote> encryption. In this mode
  1153. of operation, the message encryption is stripped off
  1154. as soon as the message has reached its
  1155. destination. The encryption lasts only while the
  1156. message is on its way.
  1157. </para>
  1158. <para>
  1159. &kmail; supports this mode half-heartedly, since such
  1160. functionality should better placed at the mail
  1161. <emphasis>server</emphasis> (<acronym>MTA</acronym>)
  1162. than at the mail <emphasis>client</emphasis>
  1163. (<acronym>MUA</acronym>) level. Thus, future versions
  1164. of &kmail; may drop support for this option.
  1165. </para>
  1166. </footnote>
  1167. </term>
  1168. <listitem>
  1169. <para>
  1170. If checked, messages are stored in your
  1171. <guilabel>sent-mail</guilabel> folder just as you sent
  1172. them (&ie; if they were encrypted, they are also stored
  1173. that way).
  1174. </para>
  1175. <para>
  1176. If unchecked, messages will <emphasis>always</emphasis>
  1177. be stored unencrypted in your
  1178. <guilabel>sent-mail</guilabel> folder, even if they are
  1179. sent encrypted.
  1180. </para>
  1181. </listitem>
  1182. </varlistentry>
  1183. <varlistentry id="configure-security-composing-show-encryption-key">
  1184. <term>
  1185. <guilabel>Always show the encryption keys for approval</guilabel>
  1186. </term>
  1187. <listitem>
  1188. <para>
  1189. If checked, every time you encrypt a message, a dialog
  1190. will appear that presents you with the encryption keys
  1191. that will be used for each recipient. You can then
  1192. review the choice of keys, change them, and approve or
  1193. cancel the encryption operation. We recommend to keep
  1194. this option checked, since it makes the encryption
  1195. process more transparent.
  1196. </para>
  1197. </listitem>
  1198. </varlistentry>
  1199. <varlistentry id="configure-security-composing-opportunistic-encryption">
  1200. <term>
  1201. <guilabel>Automatically encrypt messages whenever possible</guilabel>
  1202. </term>
  1203. <listitem>
  1204. <para>
  1205. Also called <quote>opportunistic encryption</quote>. If
  1206. checked, &kmail; will try to match recipients to
  1207. (&openpgp; or &smime;) keys even when you did
  1208. <emphasis>not</emphasis> specifically request
  1209. encryption. If usable keys are found for all recipients,
  1210. &kmail; will ask whether or not you want to encrypt the
  1211. message.
  1212. </para>
  1213. <para>
  1214. It is highly recommended to turn this on, as it makes
  1215. encrypting messages really easy to use.
  1216. </para>
  1217. </listitem>
  1218. </varlistentry>
  1219. <varlistentry id="configure-security-composing-never-sign-encrypt-drafts">
  1220. <term>
  1221. <guilabel>Never sign/encrypt when saving as draft</guilabel>
  1222. </term>
  1223. <listitem>
  1224. <para>
  1225. If checked, &kmail; will not attempt to sign and/or
  1226. encrypt messages that are merely saved to the
  1227. <guilabel>drafts</guilabel> folder. This is more
  1228. convenient, and does not result in a gross loss of
  1229. security, provided the drafts folder is safe. &imap;
  1230. users might want this options turned off, if their
  1231. <guilabel>drafts</guilabel> folder is on the server.
  1232. </para>
  1233. </listitem>
  1234. </varlistentry>
  1235. </variablelist>
  1236. </sect2>
  1237. <sect2 id="configure-security-warnings">
  1238. <title>
  1239. Warnings
  1240. </title>
  1241. <para>
  1242. On this tab you can switch security-relevant warnings on and
  1243. off.
  1244. </para>
  1245. <variablelist>
  1246. <varlistentry id="configure-security-warnings-warn-send-unsigned">
  1247. <term>
  1248. <guilabel>Warn when trying to send unsigned messages</guilabel>
  1249. </term>
  1250. <listitem>
  1251. <para>
  1252. If checked, &kmail; will show a warning if for whatever
  1253. reason a message would be sent without being digitally
  1254. signed.
  1255. </para>
  1256. </listitem>
  1257. </varlistentry>
  1258. <varlistentry id="configure-security-warnings-warn-send-unencrypted">
  1259. <term>
  1260. <guilabel>Warn when trying to send unencrypted messages</guilabel>
  1261. </term>
  1262. <listitem>
  1263. <para>
  1264. If checked, &kmail; will show a warning if for whatever
  1265. reason a message would be sent without being encrypted.
  1266. </para>
  1267. <note>
  1268. <para>
  1269. While it is common to sign all outgoing messages,
  1270. encrypting them is not. So unless your company has a
  1271. policy of never sending any unencrypted messages, it
  1272. might be a good idea to keep this option switched off
  1273. and rely on <link
  1274. linkend="configure-security-composing-opportunistic-encryption">opportunistic
  1275. encryption</link> to alert you if you
  1276. <emphasis>could</emphasis> send encrypted messages,
  1277. but did not request it.
  1278. </para>
  1279. </note>
  1280. </listitem>
  1281. </varlistentry>
  1282. <varlistentry id="configure-security-warnings-warn-receiver-email-not-in-cert">
  1283. <term>
  1284. <guilabel>Warn if receiver's email address is not in certificate</guilabel>
  1285. </term>
  1286. <listitem>
  1287. <para>
  1288. If checked, &kmail; will emit a warning if an &smime;
  1289. certificate or &openpgp; key will be used for a recipient
  1290. whose email address is not listed in the email addresses
  1291. stored in the certificate.
  1292. </para>
  1293. <para>
  1294. Situations in which this warning will trigger include
  1295. when configuring your per-identity &openpgp; keys or
  1296. &smime; certificates, when encrypting, and when verifying
  1297. signatures, if the signature was made with a certificate
  1298. that does not include the email address of the sender.
  1299. </para>
  1300. </listitem>
  1301. </varlistentry>
  1302. <varlistentry id="configure-security-warnings-warn-near-expire">
  1303. <term>
  1304. <guilabel>Warn if certificates/keys expire soon</guilabel>
  1305. </term>
  1306. <listitem>
  1307. <para>
  1308. If checked, &kmail; will warn when an &smime; certificate
  1309. or &openpgp; key is used which will expire soon.
  1310. </para>
  1311. <para>
  1312. The period in which to warn before key/certificate
  1313. expiration can then be configured separately for signing
  1314. and encryption keys, as well as (in the case of &smime;),
  1315. for end-user certificates, intermediate
  1316. <acronym>CA</acronym> certificates and root
  1317. certificates.
  1318. </para>
  1319. </listitem>
  1320. </varlistentry>
  1321. <varlistentry id="configure-security-warnings-reenable-all-warnings">
  1322. <term>
  1323. <guilabel>Re-Enable All &quot;Don&apos;t Ask Again&quot; Warnings</guilabel>
  1324. </term>
  1325. <listitem>
  1326. <para>
  1327. Apart from the main warnings described above, there are
  1328. more warning and information messages, which contain an
  1329. option to not show them again. If you would like to
  1330. re-enable them after choosing not to show them again,
  1331. you can achieve this by pressing this button.<!--
  1332. --><footnote>
  1333. <para>
  1334. This will re-enable <emphasis>all</emphasis> such
  1335. warnings for &kmail;. It does not make much sense to
  1336. allow more fine-grained selection of which warnings
  1337. to show since you can just check the option to
  1338. suppress them again when they next show up.
  1339. </para>
  1340. </footnote>
  1341. </para>
  1342. </listitem>
  1343. </varlistentry>
  1344. </variablelist>
  1345. </sect2>
  1346. <sect2 id="configure-security-smime-validation">
  1347. <title>
  1348. &smime; Validation
  1349. </title>
  1350. <para>
  1351. This tab contains selected entries from &gpgsm;'s <link
  1352. linkend="configure-security-crypto-backends-configure">dynamic
  1353. backend configuration dialog</link>. Please refer
  1354. to the &gpgsm; manual for a description of these options.
  1355. </para>
  1356. <variablelist>
  1357. <varlistentry id="configure-smime-validation-certificate-crls">
  1358. <term>
  1359. <guilabel>Validate certificates using CRLs</guilabel>
  1360. </term>
  1361. <listitem>
  1362. <para>
  1363. If checked, &smime; certificates are validated using
  1364. Certificate Revocation Lists (<acronym>CRLs</acronym>).
  1365. </para>
  1366. </listitem>
  1367. </varlistentry>
  1368. <varlistentry id="configure-smime-validation-certificate-ocps">
  1369. <term>
  1370. <guilabel>Validate certificates online (OCSP)</guilabel>
  1371. </term>
  1372. <listitem>
  1373. <para>
  1374. If this option is selected, &smime; certificates are validated
  1375. using the Online Certificates Status Protocol
  1376. (<acronym>OCSP</acronym>).
  1377. </para>
  1378. <para>
  1379. Fill in the <acronym>URL</acronym> of the <acronym>OCSP</acronym>
  1380. responder in the field reserved at this effect.
  1381. </para>
  1382. </listitem>
  1383. </varlistentry>
  1384. <varlistentry id="configure-smime-online-certificate-responder-url">
  1385. <term>
  1386. <guilabel>OCSP responder URL</guilabel>
  1387. </term>
  1388. <listitem>
  1389. <para>
  1390. Enter the address of the server for online validation
  1391. of certificates. The <acronym>URL</acronym>
  1392. is usually starting with <emphasis>http://</emphasis>.
  1393. </para>
  1394. </listitem>
  1395. </varlistentry>
  1396. <varlistentry id="configure-smime-online-certificate-responder-signature">
  1397. <term>
  1398. <guilabel>OCSP responder signature</guilabel>
  1399. </term>
  1400. <listitem>
  1401. <para>
  1402. Select or change and enter the &smime; key to use.
  1403. </para>
  1404. </listitem>
  1405. </varlistentry>
  1406. <varlistentry id="configure-smime-online-certificate-responder-ignore">
  1407. <term>
  1408. <guilabel>Ignore service URL of certificates</guilabel>
  1409. </term>
  1410. <listitem>
  1411. <para>
  1412. Check this option to skip online validation using the OCSP.
  1413. This Option requires <emphasis>dirmngr &gt;= 0.9.0</emphasis>.
  1414. </para>
  1415. </listitem>
  1416. </varlistentry>
  1417. <varlistentry id="configure-smime-certificate-validation-policies">
  1418. <term>
  1419. <guilabel>Do not check certificate policies</guilabel>
  1420. </term>
  1421. <listitem>
  1422. <para>
  1423. By default, <guilabel>GnuPG</guilabel> uses the file
  1424. <emphasis>~/.gnupg/policies.txt</emphasis> to check if a
  1425. certificate policy is allowed. If this option is selected,
  1426. policies are not checked.
  1427. </para>
  1428. </listitem>
  1429. </varlistentry>
  1430. <varlistentry id="configure-smime-certificate-validation-consult-crls">
  1431. <term>
  1432. <guilabel>Never consult a CRLs</guilabel>
  1433. </term>
  1434. <listitem>
  1435. <para>
  1436. If this option is checked, Certificate Revocation Lists are
  1437. never used to validate <acronym>&smime;</acronym> certificates.
  1438. </para>
  1439. </listitem>
  1440. </varlistentry>
  1441. <varlistentry id="configure-smime-certificate-validation-fetch-issuer">
  1442. <term>
  1443. <guilabel>Fetch missing issuer certificates</guilabel>
  1444. </term>
  1445. <listitem>
  1446. <para>
  1447. Check this option if you want the missing issuer certificates
  1448. to be fetched when necessary. This applies to both validation
  1449. methods, <acronym>CRLs</acronym> and <acronym>OCSP</acronym>.
  1450. </para>
  1451. </listitem>
  1452. </varlistentry>
  1453. <varlistentry id="configure-smime-certificate-http-requests">
  1454. <term>
  1455. <guilabel>Do not perform any HTTP requests</guilabel>
  1456. </term>
  1457. <listitem>
  1458. <para>
  1459. Entirely disables the use of <acronym>HTTP</acronym> for
  1460. <acronym>&smime;</acronym>.
  1461. </para>
  1462. </listitem>
  1463. </varlistentry>
  1464. <varlistentry id="configure-smime-certificate-http-ignore-distribution-point">
  1465. <term>
  1466. <guilabel>Ignore HTTP CRL Distribution Point of certificates</guilabel>
  1467. </term>
  1468. <listitem>
  1469. <para>
  1470. When looking for the location of a <acronym>CRL</acronym>,
  1471. <quote>the "to-be-tested"</quote>certificate usually contains
  1472. what are known as CRL Distribution Point (<acronym>DP</acronym>) entries,
  1473. which are <acronym>URLs</acronym> describing the way to access
  1474. the <acronym>URL</acronym>. The first found <acronym>DP</acronym>
  1475. entry is used.
  1476. With this option all entries using the <acronym>HTTP</acronym>
  1477. scheme are ignored when looking for a suitable
  1478. <acronym>DP</acronym>.
  1479. </para>
  1480. </listitem>
  1481. </varlistentry>
  1482. <varlistentry id="configure-smime-certificate-http-proxy">
  1483. <term>
  1484. <guilabel>Use system HTTP proxy</guilabel>
  1485. </term>
  1486. <listitem>
  1487. <para>
  1488. If this option is selected, the value of the
  1489. <acronym>HTTP</acronym> proxy shown on the right
  1490. (which comes from the environment variable http_proxy)
  1491. will be used for any <acronym>HTTP</acronym> request.
  1492. </para>
  1493. </listitem>
  1494. </varlistentry>
  1495. <varlistentry id="configure-smime-certificate-http-requests-proxy">
  1496. <term>
  1497. <guilabel>Use this proxy for HTTP requests</guilabel>
  1498. </term>
  1499. <listitem>
  1500. <para>
  1501. Enter here the location of your <acronym>HTTP</acronym> Proxy,
  1502. which will be used for all <acronym>HTTP</acronym> requests
  1503. relating to <acronym>&smime;</acronym>.
  1504. The syntax is <quote>"host:port"</quote>, for instance
  1505. <emphasis></emphasis>.
  1506. </para>
  1507. </listitem>
  1508. </varlistentry>
  1509. <varlistentry id="configure-smime-certificate-ldap-requests">
  1510. <term>
  1511. <guilabel>Do not perform any LDAP requests</guilabel>
  1512. </term>
  1513. <listitem>
  1514. <para>
  1515. Entirely disables the use of <acronym>LDAP</acronym> for
  1516. <acronym>&smime;</acronym>.
  1517. </para>
  1518. </listitem>
  1519. </varlistentry>
  1520. <varlistentry id="configure-smime-certificate-ldap-distribution-point">
  1521. <term>
  1522. <guilabel>Ignore LDAP CRL Distribution Point of certificates</guilabel>
  1523. </term>
  1524. <listitem>
  1525. <para>
  1526. When looking for the location of a <acronym>CRL</acronym>,
  1527. the <quote>"to-be-tested"</quote> certificate usually contains
  1528. what are known as CRL Distribution Point (<acronym>DP</acronym>) entries,
  1529. which are <acronym>URLs</acronym> describing the way to access
  1530. the <acronym>URL</acronym>.
  1531. The first found <acronym>DP</acronym> entry is used.
  1532. With this option all entries using the <acronym>LDAP</acronym>
  1533. scheme are ignored when looking for a suitable
  1534. <acronym>DP</acronym>.
  1535. </para>
  1536. </listitem>
  1537. </varlistentry>
  1538. <varlistentry id="configure-smime-certificate-ldap-proxy-host">
  1539. <term>
  1540. <guilabel>Primary host for LDAP requests</guilabel>
  1541. </term>
  1542. <listitem>
  1543. <para>
  1544. Entering a <acronym>LDAP</acronym> server here will make all
  1545. <acronym>LDAP</acronym> requests go to that server first.
  1546. More precisely, this setting overrides any specified host
  1547. and port part in a <acronym>LDAP URL</acronym> and will also
  1548. be used if host and port have been omitted from the
  1549. <acronym>URL</acronym>. Other <acronym>LDAP</acronym> servers
  1550. will be used only if the connection to the
  1551. <emphasis>proxy</emphasis> failed.
  1552. The syntax is <acronym>HOST</acronym> or
  1553. <acronym>HOST:PORT</acronym>. If <acronym>PORT</acronym> is
  1554. omitted, <quote>port 389</quote>
  1555. (standard <acronym>LDAP</acronym> port) is used.
  1556. </para>
  1557. </listitem>
  1558. </varlistentry>
  1559. </variablelist>
  1560. </sect2>
  1561. <sect2 id="configure-security-crypto-backends">
  1562. <title>
  1563. Crypto Backends
  1564. </title>
  1565. <para>
  1566. On this tab you can configure which crypto backends are to be
  1567. used for &openpgp; and &smime; cryptographic operations (such
  1568. as signing and encrypting).
  1569. </para>
  1570. <para>
  1571. On the right-hand side, you see a list of available
  1572. backends. Below each backend entry, you can see what protocols
  1573. (&openpgp; and/or &smime;) the backend supports. If a protocol
  1574. is not listed, the backend does not support it. If it is
  1575. listed, but grayed out, the backend supports the protocol, but
  1576. some required programs were not found, or other errors
  1577. occurred during initialization. If you press
  1578. <guibutton>Rescan</guibutton>, a dialog box will appear that
  1579. lists reasons for the initialization failure.
  1580. </para>
  1581. <para id="configure-security-crypto-backends-configure">
  1582. To configure a backend, select it in the list of available
  1583. backends and press <guibutton>Configure...</guibutton>. The
  1584. per-backend configuration dialog is dynamically created from
  1585. the information returned by the backend. It may therefore
  1586. change if you update the backend applications, although
  1587. &kmail; itself is unchanged. If the
  1588. <guibutton>Configure...</guibutton> button is disabled, the
  1589. backend does not support a backend configuration dialog.
  1590. </para>
  1591. <para>
  1592. Please refer to the manuals of the applications underlying
  1593. each backend for a description of the options presented in the
  1594. backend configuration dialogs.
  1595. </para>
  1596. <para>
  1597. In front of each backend's protocol entries, you can see a
  1598. checkbox, with which you select which backend is to be used
  1599. for a given protocol. These checkboxes are exclusive per
  1600. protocol, meaning that if you select a backend to perform
  1601. &openpgp; operations, any previously selected &openpgp;
  1602. implementation will be unselected, but the &smime; backend
  1603. selection will be unchanged. If no backend is selected for a
  1604. given protocol, that protocol is effectively disabled for use
  1605. in &kmail;.
  1606. </para>
  1607. </sect2>
  1608. </sect1> <!-- configure-security -->
  1609. <sect1 id="configure-misc">
  1610. <title>Misc Page</title>
  1611. <sect2 id="configure-misc-folders">
  1612. <title>Folders</title>
  1613. <variablelist>
  1614. <varlistentry>
  1615. <term><guilabel>Ask for confirmation before moving all messages to trash</guilabel></term>
  1616. <listitem>
  1617. <para>Enable this option if you want to be asked for confirmation whenever
  1618. you use <menuchoice><guimenu>Folder</guimenu><guimenuitem>Move All Messages to Trash</guimenuitem></menuchoice>.</para>
  1619. </listitem>
  1620. </varlistentry>
  1621. <varlistentry>
  1622. <term><guilabel>Exclude important messages from expiry</guilabel></term>
  1623. <listitem>
  1624. <para>Enable this option if important messages should never be deleted
  1625. during message expiration, &ie; during automatic deletion of old
  1626. messages.</para>
  1627. </listitem>
  1628. </varlistentry>
  1629. <varlistentry id="configure-misc-folders-go-unread">
  1630. <term><guilabel>When trying to find unread messages</guilabel></term>
  1631. <listitem>
  1632. <para>This option controls what happens if you press one of the shortcuts to
  1633. go to the next or previous unread message (&eg; <keycap>Space</keycap>).
  1634. If you ask &kmail; to go to the next unread message although there is no
  1635. unread message below the currently selected message then the following happens:
  1636. <itemizedlist>
  1637. <listitem>
  1638. <para>If <guilabel>Do not Loop</guilabel> is selected then nothing will happen.
  1639. </para>
  1640. </listitem>
  1641. <listitem>
  1642. <para>If <guilabel>Loop in Current Folder</guilabel> is selected then &kmail;
  1643. will search from the beginning of the current folder for an unread message. If
  1644. none is found then nothing happens.</para>
  1645. </listitem>
  1646. <listitem>
  1647. <para>If <guilabel>Loop in All Folders</guilabel> is selected then &kmail;
  1648. will first search in the current folder for another unread message. If none
  1649. is found then &kmail; will search the next folder containing unread messages.
  1650. </para>
  1651. </listitem>
  1652. </itemizedlist>
  1653. Correspondingly, if you ask &kmail; to go to the previous unread message.
  1654. </para>
  1655. </listitem>
  1656. </varlistentry>
  1657. <varlistentry>
  1658. <term><guilabel>When entering a folder</guilabel></term>
  1659. <listitem>
  1660. <para>This option controls what happens if you open a folder.
  1661. <itemizedlist>
  1662. <listitem>
  1663. <para>If <guilabel>Jump to First New Message</guilabel> is selected then &kmail; will select the
  1664. first message it finds that is marked as new.
  1665. </para>
  1666. </listitem>
  1667. <listitem>
  1668. <para>If <guilabel>Jump to First Unread or New Message</guilabel> is selected then &kmail; will
  1669. select the first message it finds that is marked either as new or as unread.
  1670. </para>
  1671. </listitem>
  1672. <listitem>
  1673. <para>If <guilabel>Jump to Last Selected Message</guilabel> is selected then &kmail; will select
  1674. the message that was selected when the folder was open the last time.
  1675. </para>
  1676. </listitem>
  1677. <listitem>
  1678. <para>If <guilabel>Jump to Newest Message</guilabel> is selected then &kmail; will select the newest
  1679. message by date.
  1680. </para>
  1681. </listitem>
  1682. <listitem>
  1683. <para>If <guilabel>Jump to Oldest Message</guilabel> is selected then &kmail; will select the oldest
  1684. message by date.
  1685. </para>
  1686. </listitem>
  1687. </itemizedlist>
  1688. </para>
  1689. </listitem>
  1690. </varlistentry>
  1691. <varlistentry>
  1692. <term><guilabel>Mark selected message as read after...</guilabel></term>
  1693. <listitem>
  1694. <para>When you select a <guilabel>new</guilabel> or
  1695. <guilabel>unread</guilabel> message, &kmail; will change the
  1696. message's status to <guilabel>read</guilabel> after the number of seconds
  1697. entered here. If you disable this option, messages will keep their
  1698. <guilabel>new</guilabel> or <guilabel>unread</guilabel> status.</para>
  1699. </listitem>
  1700. </varlistentry>
  1701. <varlistentry>
  1702. <term><guilabel>Ask for action after dragging messages to another folder</guilabel></term>
  1703. <listitem>
  1704. <para>When you drag a message to a different folder, a small popup will ask
  1705. you if you want to move or copy the message. If you disable this option,
  1706. the message will be moved immediately, without a popup.</para>
  1707. </listitem>
  1708. </varlistentry>
  1709. <varlistentry>
  1710. <term><guilabel>By default, message folders on disk are...</guilabel></term>
  1711. <listitem>
  1712. <para>Here you can set the default <link linkend="folders-format">folder format</link>
  1713. that is used when you create a new folder.</para>
  1714. </listitem>
  1715. </varlistentry>
  1716. <varlistentry>
  1717. <term><guilabel>Open this folder on startup</guilabel></term>
  1718. <listitem>
  1719. <para>Here you can set the folder that should be selected by default if you
  1720. start &kmail;. If you use only &imap; folders then you might want to set
  1721. this to your &imap; inbox folder. If you do that, you can collapse the local
  1722. folders in the folder list, and then they will stay collapsed when &kmail;
  1723. starts.</para>
  1724. </listitem>
  1725. </varlistentry>
  1726. <varlistentry>
  1727. <term><guilabel>Empty trash on program exit</guilabel></term>
  1728. <listitem>
  1729. <para>The trash folder is cleared of messages when you quit &kmail; if this
  1730. option is selected.</para>
  1731. </listitem>
  1732. </varlistentry>
  1733. </variablelist>
  1734. </sect2>
  1735. <sect2 id="configure-misc-groupware">
  1736. <title>Groupware</title>
  1737. <variablelist>
  1738. <varlistentry>
  1739. <term><guilabel>Enable IMAP resource functionality</guilabel></term>
  1740. <listitem>
  1741. <para>Makes it possible to store the entries from the Kontact applications (KOrganizer, KAddressBook and KNotes). This option has to be set whenever you are configuring Kontact as a <guilabel>TDE Kolab client</guilabel>. This option being enabled you will also need to add the appropriate resources from the <guilabel>Trinity Control Center</guilabel> (kcontrol) in the <guilabel>TDE Resources Configuration</guilabel> section. <guilabel>Kolab</guilabel> resources have to be added in case the resource functionality applies to a <guilabel>TDE Kolab client</guilabel> set-up.</para>
  1742. </listitem>
  1743. </varlistentry>
  1744. <varlistentry id="configure-misc-format-groupware-folders">
  1745. <term><guilabel>Format used for the groupware folders</guilabel></term>
  1746. <listitem>
  1747. <para>Choose the storage format for the groupware folders</para>
  1748. <itemizedlist>
  1749. <listitem>
  1750. <para>Default format is <guilabel>Standard (Ical/Vcard)</guilabel> for calendar folders (Ical) and addressbook folders (Vcard). This makes all Kontact features available.</para>
  1751. </listitem>
  1752. <listitem>
  1753. <para><guilabel>Kolab</guilabel> users should choose <guilabel>Kolab XML</guilabel>. This format uses a custom model that matches more closely to the one used in Microsoft Outlook(tm) and gives better compatibility.</para>
  1754. </listitem>
  1755. </itemizedlist>
  1756. </listitem>
  1757. </varlistentry>
  1758. <varlistentry>
  1759. <term><guilabel>Language of the groupware folders</guilabel></term>
  1760. <listitem>
  1761. <para>Choose between the available languages to set the folder names of the <guilabel>IMAP</guilabel> storage to your local language. Note that this option is only aimed for compatibility with Microsoft Outlook(tm). It is not recommended to change its default unless you have to, since it makes changing languages impossible.</para>
  1762. </listitem>
  1763. </varlistentry>
  1764. <varlistentry>
  1765. <term><guilabel>Resource folders are in account</guilabel></term>
  1766. <listitem>
  1767. <para>Select the parent of the <guilabel>IMAP</guilabel> resource folders. You should select the name of your <guilabel>IMAP/DIMAP</guilabel> account. By default the <guilabel>Kolab</guilabel> server sets the <guilabel>IMAP</guilabel> inbox to be the parent.</para>
  1768. </listitem>
  1769. </varlistentry>
  1770. <varlistentry>
  1771. <term><guilabel>Hide groupware folders</guilabel></term>
  1772. <listitem>
  1773. <para>You should not need to see the folders that hold the <guilabel>IMAP</guilabel> resources. However if you want to see them, you can set that by enabling this option.</para>
  1774. </listitem>
  1775. </varlistentry>
  1776. <varlistentry>
  1777. <term><guilabel>Mangle From:/To: headers in replies to invitations</guilabel></term>
  1778. <listitem>
  1779. <para>Enable this option to make Microsoft Outlook(tm) understand your answers to invitations replies.</para>
  1780. </listitem>
  1781. </varlistentry>
  1782. <varlistentry>
  1783. <term><guilabel>Send invitations in the mail body</guilabel></term>
  1784. <listitem>
  1785. <para>Invitations use to be send as attachments to a mail. By enabling this option, you let the invitation mails to be sent in the text of the mail, which is necessary to send invitations and replies to Microsoft Outlook(tm).</para>
  1786. </listitem>
  1787. </varlistentry>
  1788. <varlistentry>
  1789. <term><guilabel>Exchange compatible invitations naming</guilabel></term>
  1790. <listitem>
  1791. <para>Microsoft Outlook, when used in combination with a Microsoft Exchange
  1792. server, has a problem understanding standards-compliant groupware e-mail.
  1793. Enable this option to send groupware invitations in a way that Microsoft
  1794. Exchange understands. The invitation will be sent as an attachment with name <filename>ical.ics</filename>.</para>
  1795. </listitem>
  1796. </varlistentry>
  1797. <varlistentry>
  1798. <term><guilabel>Outlook compatible invitation reply comments</guilabel></term>
  1799. <listitem>
  1800. <para>When the user provides comments when responding to invitations, send the comment in way that Microsoft Outlook(tm) understands. If this option is not enabled, the response comments will not be seen in Outlook.</para>
  1801. </listitem>
  1802. </varlistentry>
  1803. </variablelist>
  1804. </sect2>
  1805. <sect2 id="configure-non-gui-options">
  1806. <title>Options without a user interface representation</title>
  1807. <para>
  1808. Apart from the options presented in the configuration dialog, some options
  1809. can only be set directly in the configuration file ($TDEHOME/share/config/kmailrc)
  1810. or through KIOSK.
  1811. </para>
  1812. <variablelist>
  1813. <varlistentry>
  1814. <term><guilabel>Send Message Distribution Notifications with an empty sender string (SendMDNsWithEmptySender)</guilabel></term>
  1815. <listitem>
  1816. <para>
  1817. Send Message Disposition Notifications with an empty sender string. Some servers might be configured to reject
  1818. such messages, so if you are experiencing problems sending MDNs, make sure this option is set to false. To
  1819. enable this feature, add a line reading:
  1820. SendMDNsWithEmptySender=true
  1821. to the [MDN] section of the kmail configuration file. If there is no such section, simply add "[MDN]" on
  1822. a line by itself just above the option.
  1823. Note that the default setting of "false" strictly speaking violates Internet standards, but is
  1824. set that way for practical reasons, to avoid servers rejecting MDNs that KMail generates because they
  1825. think they are SPAM.
  1826. </para>
  1827. </listitem>
  1828. </varlistentry>
  1829. <varlistentry>
  1830. <term><guilabel>Allow Semicolon As EMail Address Separator (AllowSemicolonAsAddressSeparator)</guilabel></term>
  1831. <listitem>
  1832. <para>
  1833. In RFC2822, the comma (,) is the only allowed separator for email addresses in fields like To, CC and BCC. This option allows to also use the semi-colon (;) as separator. This only affects the user interface, the created messages still use commas only and thus do no violate the standard.
  1834. The option is enabled by default. To disable the feature, add a line reading (under [Composer] section):
  1835. </para>
  1836. <programlisting>AllowSemicolonAsAddressSeparator=false
  1837. </programlisting>
  1838. </listitem>
  1839. </varlistentry>
  1840. <varlistentry>
  1841. <term><guilabel>MaximumAttachmentSize</guilabel></term>
  1842. <listitem>
  1843. <para>
  1844. This allows the maximum file size allowed for attachments in the mail
  1845. composer to be limited.
  1846. To limit attachments to 20 MB ins size, for example, add a line reading (under [Composer] section):
  1847. </para>
  1848. <programlisting>MaximumAttachmentSize=20
  1849. </programlisting>
  1850. </listitem>
  1851. </varlistentry>
  1852. <varlistentry>
  1853. <term><guilabel>CloseDespiteSystemTray</guilabel></term>
  1854. <listitem>
  1855. <para>
  1856. This option allows you to configure the application to close fully, even if there
  1857. is a system tray icon configured, which would normally keep the application running.
  1858. To enable the feature, add a line reading (under [General] section):
  1859. </para>
  1860. <programlisting>CloseDespiteSystemTray=true
  1861. </programlisting>
  1862. </listitem>
  1863. </varlistentry>
  1864. <varlistentry>
  1865. <term><guilabel>CheckOutOfOfficeOnStartup</guilabel></term>
  1866. <listitem>
  1867. <para>
  1868. With this option enabled, KMail will check on every startup if there is an
  1869. active out-of-office configured and show a warning if this is the case.
  1870. To disable the feature, add a line reading (under [OutOfOffice] section):
  1871. </para>
  1872. <programlisting>CheckOutOfOfficeOnStartup=false
  1873. </programlisting>
  1874. </listitem>
  1875. </varlistentry>
  1876. <varlistentry>
  1877. <term><guilabel>Allow out-of-office settings to be adjusted by the user.</guilabel></term>
  1878. <listitem>
  1879. <para>
  1880. In case you don't want users to be able to upload their own out-of-office scripts to
  1881. the server you can add:
  1882. </para>
  1883. <programlisting>AllowOutOfOfficeSettings=false
  1884. </programlisting><para>
  1885. to the [OutOfOffice] section of the kmail configuration file. If there is no such section, simply add "[OutOfOffice]" on
  1886. a line by itself just above the option.
  1887. </para>
  1888. </listitem>
  1889. </varlistentry>
  1890. <varlistentry>
  1891. <term><guilabel>Allow out-of-office scripts to be uploaded by the user, but no settings changed.</guilabel></term>
  1892. <listitem>
  1893. <para>
  1894. If you want to allow your users to upload their own out-of-office scripts but you do not want them to be
  1895. able to change the domain to react to and the react-to-spam setting, you can add:
  1896. </para>
  1897. <programlisting>AllowOutOfOfficeUploadButNoSettings=true
  1898. </programlisting><para>
  1899. to the [OutOfOffice] section of the kmail configuration file. If there is no such section, simply add "[OutOfOffice]" on
  1900. a line by itself just above the option.
  1901. </para>
  1902. </listitem>
  1903. </varlistentry>
  1904. <varlistentry>
  1905. <term><guilabel>Default domain to limit out-of-office replies to.</guilabel></term>
  1906. <listitem>
  1907. <para>
  1908. When editing vacation (out-of-office) scripts, the user can specify a domain to
  1909. limit the sending of such replies to. To pre-load this setting with a default
  1910. value, add
  1911. </para>
  1912. <programlisting>OutOfOfficeDomain=myMailDomain.test
  1913. </programlisting><para>
  1914. to the [OutOfOffice] section of the kmail configuration file. If there is no such section, simply add "[OutOfOffice]" on
  1915. a line by itself just above the option.
  1916. Applying defaults to the out-of-office configuration dialog via the corresponding
  1917. button will restore this domain, in case the user has changed it.
  1918. </para>
  1919. </listitem>
  1920. </varlistentry>
  1921. <varlistentry>
  1922. <term><guilabel>Enable sending of out-of-office replies to messages marked as SPAM.</guilabel></term>
  1923. <listitem>
  1924. <para>
  1925. By default, out-of-office replies are not sent to messages marked as SPAM. To override this
  1926. behavior, add
  1927. </para>
  1928. <programlisting>OutOfOfficeReactToSpam=true
  1929. </programlisting><para>
  1930. to the [OutOfOffice] section of the kmail configuration file. If there is no such section, simply add "[OutOfOffice]" on
  1931. a line by itself just above the option.
  1932. Applying defaults to the out-of-office configuration dialog via the corresponding
  1933. button will restore this setting, in case the user has changed it.
  1934. </para>
  1935. </listitem>
  1936. </varlistentry>
  1937. <varlistentry>
  1938. <term><guilabel>disregardUmask</guilabel></term>
  1939. <listitem>
  1940. <para>
  1941. This option allows you to disregard the users umask setting and use "read-write for the user only".
  1942. To enable the feature, add a line reading (under [General] section):
  1943. </para>
  1944. <programlisting>disregardUmask=false
  1945. </programlisting>
  1946. </listitem>
  1947. </varlistentry>
  1948. <varlistentry>
  1949. <term><guilabel>AutoLostFoundMove</guilabel></term>
  1950. <listitem><para>Activate this option to automate the handling of not yet uploaded messages in disconnected IMAP
  1951. folders that can not be uploaded. This can happen if the folder was removed from the server or your access
  1952. rights have been restricted. Such messages will automatically moved to a newly created lost+found folder if
  1953. this option is enabled, you will be ask how to proceed every time otherwise.
  1954. To enable the feature, add a line reading:
  1955. </para>
  1956. <programlisting>AutoLostFoundMove=true</programlisting>
  1957. <para>to the [Behaviour] section of the configuration file </para>
  1958. </listitem>
  1959. </varlistentry>
  1960. </variablelist>
  1961. </sect2>
  1962. </sect1>
  1963. </chapter>