summaryrefslogtreecommitdiffstats
path: root/tde-i18n-en_GB/docs/kdepim/kmail/configure.docbook
blob: b6f421a79f633a5759b125afc3f1e8a9c061e732 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
<chapter id="configure">

<chapterinfo>
<authorgroup>
<author
><firstname
>Daniel</firstname
> <surname
>Naber</surname
> <affiliation
><address
> <email
>daniel.naber@t-online.de</email>
</address
></affiliation>
</author>
<author
><firstname
>David</firstname
> <surname
>Rugge</surname
> <affiliation
><address
> <email
>davidrugge@mediaone.net</email>
</address
></affiliation>
</author>
<author
><firstname
>Marc</firstname
> <surname
>Mutz</surname
> <affiliation
><orgname
>Klar&auml;lvdalens Datakonsult AB</orgname
> <address
> <email
>mutz@kde.org</email
> </address
> </affiliation>
</author>
<author
><firstname
>Michel</firstname
> <surname
>Boyer de la Giroday</surname
> <affiliation
><address
> <email
>michel@klaralvdalens-datakonsult.se</email>
</address
></affiliation>
</author>
<othercredit role="translator"
><firstname
>Andrew</firstname
><surname
>Coles</surname
><affiliation
><address
><email
>andrew_coles@yahoo.co.uk</email
></address
></affiliation
><contrib
>Conversion to British English</contrib
></othercredit
> 
</authorgroup>
<date
>2004-07-13</date
> <releaseinfo
>1.7</releaseinfo
> </chapterinfo>

<title
>Configure &kmail;</title>

<sect1 id="configure-generalinfo">
<title
>General Information</title>

<para
>&kmail;'s configuration window enables you to configure &kmail; in many ways. You can reach it via <menuchoice
><guimenu
>Settings</guimenu
><guimenuitem
>Configure &kmail;...</guimenuitem
></menuchoice
>.</para>

<para
>It is divided into six pages, each of them represented by one of the icons in the list on the left hand side of the dialogue. Below the pages will be described in detail.</para>

<para
>The dialogue has several buttons:</para>

<variablelist>
<varlistentry>
<term
><guibutton
>Help</guibutton
></term>
<listitem
><para
>This will open this manual at the appropriate page.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>Defaults</guibutton
></term>
<listitem
><para
>This will reset the configuration options on the current page back to the default values.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>Load Profile...</guibutton
></term>
<listitem
><para
>This will open a dialogue which offers several configuration profiles. You can use these as starting points for your own configuration.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>Reset</guibutton
></term>
<listitem
><para
>This resets all changes you have made since you last saved the settings.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>OK</guibutton
></term>
<listitem
><para
>This saves the settings and closes the configuration dialogue.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>Apply</guibutton
></term>
<listitem
><para
>This saves the settings without closing the configuration dialogue.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guibutton
>Cancel</guibutton
></term>
<listitem
><para
>This closes the configuration dialogue without saving the changes you have made.</para
></listitem>
</varlistentry>
</variablelist>

</sect1>

<sect1 id="configure-identity">
<title
>Identities Page</title>

<para
>You can find a quick introduction to the <guilabel
>Identities</guilabel
> page in the <link linkend="getting-started"
>Getting Started</link
> section.</para>

<para
>This page allows you to create one or more <emphasis
>Identities</emphasis
>, &ie; combinations of name, email address and other settings. For example, you can create one identity for business communication and one for personal communication. If you have more than one email address, you can create one identity per address. You will then be able to select an identity on a per-message basis.</para>

<para
>The page consists of a list of identities and buttons to manage them. The identities list will always show at least one identity, which is then the <guilabel
>Default</guilabel
> identity.</para>

<para
>To add a new identity to the identity list, click on the <guibutton
>New...</guibutton
> button. The <link linkend="configure-identity-newidentitydialog"
>New identity</link
> dialogue will then appear.</para>

<sect2 id="configure-identity-newidentitydialog">
<title
>The <guilabel
>New Identity</guilabel
> Dialogue</title>

<para
>You have to enter the name of the new identity into the <guilabel
>New Identity</guilabel
> edit field. This will be the name shown in the identity list.</para>

<para
>You can choose how the new identity should be initialised by checking one of the three radio buttons in the middle of the dialogue:</para>

<variablelist>

<varlistentry>
<term
><guilabel
>With empty fields</guilabel
></term>
<listitem>
<para
>All fields of the new identity are cleared or preset with standard values.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Use Control Centre settings</guilabel
></term>
<listitem>
<para
>Uses the settings of the <application
>Control Centre</application
>'s default email profile (you can edit that one under <menuchoice
><guimenu
>Internet &amp; Network</guimenu
> <guimenuitem
>Email</guimenuitem
></menuchoice
> in the <application
>Control Centre</application
>).</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Duplicate existing identity</guilabel
></term>
<listitem>
<para
>Copies all fields from an existing identity. You can choose which identity to copy from by selecting the corresponding entry in the <guilabel
>Existing identities</guilabel
> popup.</para>
</listitem>
</varlistentry>

</variablelist>

</sect2>

<sect2 id="configure-identity-general">
<title
>General</title>

<para
>The <guilabel
>General</guilabel
> tab allows you to specify some basic settings for the currently selected identity.</para>
<variablelist>
<varlistentry>
<term
><guilabel
>Your name</guilabel
></term>
<listitem>
<para
>Enter your full name here (sometimes also called <emphasis
>display name</emphasis
>). Although this field is not strictly mandatory, it is recommended to enter the correct value here.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Organisation</guilabel
></term>
<listitem>
<para
>Enter your organisation here. This field is optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Email address</guilabel
></term>
<listitem>
<para
>Enter your email address here, &ie; something like <userinput
>joe@example.com</userinput
>.</para>
</listitem>
</varlistentry>
</variablelist>
<example>
<title
>Example</title>
<para
>So if your address is <replaceable
>Joe User &lt;joe@example.com&gt;</replaceable
>, you should enter <userinput
>Joe User</userinput
> into the <guilabel
>Your name</guilabel
> field and <userinput
>joe@example.com</userinput
> into the <guilabel
>Email address</guilabel
> field.</para
></example>
</sect2>

    <sect2 id="configure-identity-cryptography">
      <title
>Cryptography </title>

      <para
>The <guilabel
>Cryptography</guilabel
> tab allows you to specify &openpgp; and &smime; keys associated with this identity, as well as choosing the preferred (cryptographic) message format to use. </para>

      <variablelist>

	<varlistentry id="configure-identity-cryptography-openpgp-sign">
	  <term>
	    <guilabel
>OpenPGP signing key</guilabel>
	  </term>
	  <listitem>
	    <para
>Here you can select the key to be used when &openpgp;-signing messages written with this identity in effect. </para>
	    <para
>For brevity, only the short key id of selected keys is shown. Hovering with the mouse over the key list will show more information in a tooltip. </para>
	    <para
>To clear the label press the <guibutton
>Clear</guibutton
> button. </para>
	    <para
>To change the selected key, press the <guibutton
>Change...</guibutton
> button. A dialogue listing all secret &openpgp; keys will be shown allowing you to select the one to use. </para>
	  </listitem>
	</varlistentry>

	
	<varlistentry id="configure-identity-cryptography-openpgp-encrypt">
	  <term>
	    <guilabel
>OpenPGP encryption key</guilabel>
	  </term>
	  <listitem>
	    <para
>Here you can select the key to &openpgp;-encrypt messages to when this identity and <xref linkend="configure-security-composing-encrypt-to-self"/> are in effect. This key is also used for the <xref linkend="composer-attach-attach-my-public-key"/> function of the <link linkend="the-composer-window"
>Composer</link
>. </para>
	    <para
>To change the selected key, press the <guibutton
>Change...</guibutton
> button. A dialogue listing all &openpgp; keys found in your keyring will be shown allowing you to select the one to use. </para>
	    <para
>You can clear the list of keys and get more information about them in the same way as described for <xref linkend="configure-identity-cryptography-openpgp-sign"/>. </para>
	  </listitem>
	</varlistentry>

	
	<varlistentry id="configure-identity-cryptography-smime-sign">
	  <term>
	    <guilabel
>S/MIME signing certificate</guilabel>
	  </term>
	  <listitem>
	    <para
>Here you can select the certificate to be used when &smime;-signing messages written with this identity in effect. </para>
	    <para
>To change the selected certificate, press the <guibutton
>Change...</guibutton
> button. A dialogue listing all secret &smime; signing certificates will be shown allowing you to select the one to use. </para>
	    <para
>You can clear the list of certificates and get more information about them in the same way as described for <xref linkend="configure-identity-cryptography-openpgp-sign"/>. </para>
	  </listitem>
	</varlistentry>

	
	<varlistentry id="configure-identity-cryptography-smime-encrypt">
	  <term>
	    <guilabel
>S/MIME encryption certificate</guilabel>
	  </term>
	  <listitem>
	    <para
>Here you can select the certificate to &smime;-encrypt messages to when this identity and <xref linkend="configure-security-composing-encrypt-to-self"/> are in effect. </para>
	    <para
>To change the selected certificate, press the <guibutton
>Change...</guibutton
> button. A dialogue listing all &smime; encryption certificates found in your local keybox will be shown allowing you to select the one to use. </para>
	    <para
>You can clear the list of certificates and get more information about them in the same way as described for <xref linkend="configure-identity-cryptography-openpgp-sign"/>. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-identity-cryptography-preferred-format">
	  <term>
	    <guilabel
>Preferred crypto message format</guilabel>
	  </term>
	  <listitem>
	    <para
>Here you can choose which cryptographic message format to use by default with this identity. </para>
	    <para
>You can either select any of the four formats supported by &kmail; or leave the option at the recommended default setting of <guilabel
>Any</guilabel
>, which will choose a suitable format based on the recipients of the message, or might even go so far as to create two copies of the message, one &smime; signed and/or encrypted, the other &openpgp; signed and/or encrypted. </para>
	  </listitem>
	</varlistentry>

      </variablelist>

    </sect2>

<sect2 id="configure-identity-advanced">
<title
>Advanced</title>

<para
>The <guilabel
>Advanced</guilabel
> tab allows you to specify some rarely used or otherwise specialised settings for the currently selected identity.</para>
<variablelist>

<varlistentry>
<term
><guilabel
>Reply-To address</guilabel
></term>
<listitem>
<para
>Enter the address to which replies to your messages should be sent. Only fill out this field if it is different from your normal address (specified using the <guilabel
>Name</guilabel
> and <guilabel
>Email Address</guilabel
> on the <link linkend="configure-identity-general"
><guilabel
>General</guilabel
> tab</link
>), since replies default to the sender's address anyway.</para>
<note
><para
>This field is only useful if you want replies to your mail to go somewhere else than your regular email address, &eg; if you are using this identity to send messages from an email address that cannot receive messages. Note that some mailing lists overwrite this header field with their post address to make sure that replies go to the list instead of individuals. So the usefulness of this field is very limited and it should only be used in rare cases.</para
></note>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>BCC address</guilabel
></term>
<listitem>
<para
>Optionally enter an address to which blind copies of your messages should be sent to. Note that a BCC is only send to this address, when <menuchoice
><guimenu
>View</guimenu
><guimenuitem
>BCC</guimenuitem
></menuchoice
> is activated while composing a message. If you want to send a BCC regardless of this setting, you should look at the <guilabel
>Headers</guilabel
> tab of the <guilabel
>Composer</guilabel
> page.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Sent-mail folder</guilabel
></term>
<listitem>
<para
>Select the folder into which messages should be filed after sending when using this identity. <acronym
>IMAP</acronym
> users should consider changing this to an <acronym
>IMAP</acronym
> folder, so their sent-mail is stored on a server instead of being stored in a local folder. This way they can access these messages at a different location.</para>

<tip
><para
>You can exercise more fine-grained control over where to file sent messages by creating a corresponding <link linkend="filters"
>message filter</link
> that is applied to outgoing messages.</para
></tip>

</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Drafts folder</guilabel
></term>
<listitem>
<para
>Select the folder into which drafts should be filed when using this identity. <acronym
>IMAP</acronym
> users should consider changing this to an <acronym
>IMAP</acronym
> folder, so their drafts are stored on a server instead of being stored in a local folder. This way they can easily continue to work on their drafts at a different location.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Special transport</guilabel
></term>
<listitem>
<para
>Select or enter an alternative SMTP server to be used when sending messages using this identity.</para>

<note
><para
>You need to configure outgoing mail servers first, before you can choose them from the list. You can do this on the <link linkend="configure-accounts-sending"
><guilabel
>Sending</guilabel
> tab</link
> of the <link linkend="configure-accounts"
> <guilabel
>Accounts</guilabel
> page</link
>.</para
></note>
</listitem>
</varlistentry>

</variablelist>
</sect2>

<sect2 id="configure-identity-signature">
<title
>Signature</title>

<para
>This tab allows you to specify a signature (sometimes called <quote
>footer</quote
> or <quote
>disclaimer</quote
>) to be appended to each message sent using this identity.</para>

<note
><para
>This type of signature has nothing to do with the (digital) signatures for which you can select the keys to use on the <link linkend="configure-identity-cryptography"
>Cryptography</link
> tab. It is just bad wording to call this a signature, but since the term is already used everywhere else, we keep this notation. Just keep in mind that these signatures and digital signatures are two completely different things.</para
></note>

<para
>Check the <guilabel
>Enable signature</guilabel
> option if you want to be able to append the signature when using this identity. To <emphasis
>automatically</emphasis
> append it to every new message you also have to select <guilabel
>Automatically append signature</guilabel
> in the <guilabel
>Composer</guilabel
> configuration page.</para>

<para
>&kmail; can obtain the signature text from various sources. The traditional way on Unix is to read the text from a file called <filename
>.signature</filename
> in your home folder. This file can be shared between several programs, so you get the same signature in each mail program you use.</para>

<para
>To read the text from a text file you select <guilabel
>Obtain signature text from file</guilabel
>. Enter the filename in the <guilabel
>Specify file</guilabel
> edit field or hit the button to the right of it to browse your filesystem. If you want to edit the file, hit the <guilabel
>Edit File</guilabel
> button.</para>

<para
>&kmail; can also read the signature text from the output of a command. Thus, you can use programs such as <command
>fortune</command
> to create a new signature text for every message. Everything the program prints onto <acronym
>stdout</acronym
> is caught and used as the signature text.</para>

<para
>To read the text from the output of a command you select <guilabel
>Obtain signature text from Output of Command</guilabel
>. Enter the command (preferably with full path) in the <guilabel
>Specify command</guilabel
> edit field.</para>

<para
>As a third option, you can enter the signature text directly in &kmail;'s configuration dialogue. To do this, select <guilabel
>Obtain signature text from input field below</guilabel
> and enter the text into the appearing text box.</para>

<note
><para
>On the Internet, signatures are by convention separated from the body of the message by a line containing only the three character <quote
>-- </quote
> (dash, dash, space). &kmail; will automatically prepend the signature text with this line if it is not already present in the signature text.</para>
<para
>If you do not wish the separator to be prepended automatically by &kmail;, simply add it to the signature text yourself.</para>
</note>

</sect2>

</sect1>

<sect1 id="configure-accounts">
<title
>Accounts Page</title>

<para
>You can find a quick introduction to the <guilabel
>Accounts</guilabel
> page in the <link linkend="setting-up-your-account"
>Setting up your Account</link
> section.</para>

<para
>This page allows you to create one or more (incoming and outgoing) <emphasis
>accounts</emphasis
>, &ie; combinations of mail servers, login information and other settings. Typically, you will create one outgoing (used for sending messages) and one incoming (used to retrieve messages) account. You can create as many accounts as you want, though, and assign each one to different <link linkend="configure-identity"
>identities</link
> or decide on a per-message basis.</para>

<sect2 id="configure-accounts-sending">
<title
>Sending</title>

<para
>The <guilabel
>Sending</guilabel
> tab allows you to define new outgoing mail servers and set some common options.</para>

<para
>For basic information, see <link linkend="sending-mail"
>Setting up your Account: Sending</link
>.</para>

<para
>When you click <guibutton
>Add...</guibutton
> or <guibutton
>Modify...</guibutton
> the <guilabel
>Add transport</guilabel
> or <guilabel
>Modify transport</guilabel
> dialogues will open respectively. For sending via <application
>sendmail</application
> or similar programs you can specify a name and the location of the <command
>sendmail</command
> program. For <acronym
>SMTP</acronym
> you can specify <guilabel
>Name</guilabel
>, <guilabel
>Host</guilabel
> and <guilabel
>Port</guilabel
> of the server. <guilabel
>Server requires authentication</guilabel
> will enable the <guilabel
>Login</guilabel
> and <guilabel
>Password</guilabel
> fields and the <guilabel
>Authentication method</guilabel
> buttons on the <guilabel
>Security</guilabel
> tab. If you are not sure about the security settings you can make &kmail; test for the best settings by using <guibutton
>Check What the Server Supports</guibutton
>.</para>

<para
><guilabel
>Confirm before send</guilabel
> will pop up a confirmation box every time you send a message.</para>

<para
><guilabel
>Send messages in outbox folder</guilabel
> lets you specify when queued messages, &ie; messages in the outbox folder pending to be sent, should be sent. You can choose between:</para>
<variablelist>
<varlistentry>
<term
><guilabel
>Never Automatically</guilabel
></term>
<listitem
><para
>Queued messages will only be sent if you select <menuchoice
><guimenu
>File</guimenu
><guimenuitem
>Send queued messages</guimenuitem
></menuchoice
>.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>On Manual Mail Checks</guilabel
></term>
<listitem
><para
>Queued messages will be sent after you have manually checked for new mail, &eg; with <menuchoice
><guimenu
>File</guimenu
><guimenuitem
>Check Mail</guimenuitem
></menuchoice
>. Of course, you can also manually send the queued messages with <menuchoice
><guimenu
>File</guimenu
><guimenuitem
>Send queued messages</guimenuitem
></menuchoice
>.</para
></listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>On All Mail Checks</guilabel
></term>
<listitem
><para
>Queued messages will be sent after all checks for new mail, &ie; after automatic mail checks as well as after manual mail checks. Of course, you can also manually send the queued messages with <menuchoice
><guimenu
>File</guimenu
><guimenuitem
>Send queued messages</guimenuitem
></menuchoice
>.</para
></listitem>
</varlistentry>
</variablelist>

<para
><guilabel
>Default send method</guilabel
> lets you define what happens when a message is sent. If <guilabel
>Send now</guilabel
> is selected, the message is sent to the mail server immediately, while if <guilabel
>Send later</guilabel
> is selected, the message is queued in the outbox to be sent later with the <menuchoice
><guimenu
>File</guimenu
><guimenuitem
>Send Queued Messages</guimenuitem
></menuchoice
> command or automatically when you check your mail, depending on the setting of <guilabel
>Send messages in outbox folder</guilabel
> above.</para>

<para
><guilabel
>Message property</guilabel
> lets you select how your message will be encoded when it is sent. <guilabel
>Allow 8-bit</guilabel
> means that &kmail; will send your message in 8-bit <acronym
>ASCII</acronym
>, which means that all special characters such as accented letters will be sent as-is. If <guilabel
>MIME Compliant (Quoted Printable)</guilabel
> is selected, special characters will be encoded using standard &MIME; encodings, which may be more portable to mailing systems other than 8-bit <acronym
>ASCII</acronym
>. We recommend to use <guilabel
>MIME Compliant</guilabel
>.</para>

<note
><para
>Even with <guilabel
>Allow 8-bit</guilabel
> selected &kmail; will use <guilabel
>MIME Compliant</guilabel
> encoding in some situations, for example for sending cryptographically signed messages.</para
></note>

<para
><guilabel
>Default domain</guilabel
> lets you specify which domain name should be used to complete email addresses that only consist of the recipient's user name. For example when you set the default domain to <replaceable
>kde.org</replaceable
> then messages you send to <replaceable
>joebloggs</replaceable
> will be sent to <replaceable
>joebloggs@kde.org</replaceable
>.</para>

</sect2>

<sect2 id="configure-accounts-receiving">
<title
>Receiving</title>

<para
>For basic information, see <link linkend="receiving-mail"
>Setting up your Account: Receiving</link
>.</para>

<para
><guilabel
>Check mail on startup</guilabel
> lets you specify whether KMail should check for new mail immediately after it has been started.</para>

<para
>With <guilabel
>New Mail Notification</guilabel
> you can set how &kmail; will notify you if new messages have arrived: <guilabel
>Beep</guilabel
> will play a short beep sound; if <guilabel
>Detailed new mail notification</guilabel
> is enabled then &kmail; will show the number of new messages for each folder provided you have chosen to be notified with a dialogue. More advanced notification options, like showing a dialogue or running a certain command, are available via the <guibutton
>Other Actions</guibutton
> button.</para>

</sect2>

</sect1>

<sect1 id="configure-appearance">
<title
>Appearance Page</title>

<sect2 id="configure-appearance-fonts">
<title
>Fonts</title>

<para
>This section allows you to change the type, size and character set of the display fonts. <guilabel
>Message Body</guilabel
> sets the font for the reader pane, <guilabel
>Composer</guilabel
> sets the font for writing messages in the composer window. There is a separate entry for <guilabel
>Message List - Date Field</guilabel
> so you can choose a monospaced font for the date field for better readability.</para>

</sect2>

<sect2 id="configure-appearance-colors">
<title
>Colours</title>

<para
>This section allows you to change the colour of the text. <guilabel
>Recycle colours on deep quoting</guilabel
> means that even text that is quoted more than three times will appear in colour. Note that the <guilabel
>Quoted text</guilabel
> colours only work in the message reader, not in the composer. </para>

</sect2>

<sect2 id="configure-appearance-layout">
<title
>Layout</title>

<para
><guilabel
>Show HTML status bar</guilabel
> activates a bar at the left side of the reader pane that tells you if a message is &html; or not. This is important because &html; messages might imitate the look of a signed and encrypted message, so you should be aware of the fact that you are reading a &html; message. The &html; status bar itself cannot be influenced by the &html; code of the message.</para>

<para
>The <guilabel
>Window Layout</guilabel
> section lets you choose the layout of the main window. You can choose where you want the <guilabel
>Message Preview Pane</guilabel
> or choose not to have it at all.</para>

<para
>The <guilabel
>Message Structure Viewer</guilabel
> option lets you choose when the structure viewer will be shown: the structure viewer is a part of the main window that lets you access all parts of a message. <guilabel
>Show never</guilabel
> will disable the structure viewer (note that you can still access attachments as icons), <guilabel
>Show always</guilabel
> will show the structure viewer even if there is only one plaintext part. <guilabel
>Show only for non-plaintext messages</guilabel
> will display the structure viewer only if it makes sense, &ie; if the current message has attachments or has &html; parts.</para>

</sect2>

<sect2 id="configure-appearance-headers">
<title
>Headers</title>

<para
>With <guilabel
>Display message sizes</guilabel
> selected there will be another column in the header pane that shows the messages' size.</para>

<para
><guilabel
>Show crypto icons</guilabel
> will add more status information to the <guilabel
>Subject</guilabel
> columns in the header pane: every message that has been signed will have a small <guiicon
>Signed</guiicon
> icon in front of the subject, every message that has been encrypted will have a small <guiicon
>Encrypted</guiicon
> icon in front of the subject. Note that you have to select a message once before these icons will appear, until then only question marks will be displayed.</para>

<para
><guilabel
>Thread list of message headers</guilabel
> will put all the messages in the header pane in a kind of tree list, so that the replies to a message are directly below that message.</para>

<para
>With <guilabel
>Message header threading options</guilabel
> you can select whether threads should appear expanded (<guilabel
>open</guilabel
>) by default or whether they should be collapsed (<guilabel
>closed</guilabel
>). You can of course still open/close threads using the <guilabel
>+</guilabel
>/<guilabel
>-</guilabel
> buttons.</para
> 

<para
>With <guilabel
>Date Display</guilabel
> you can choose between several date formats. The <guilabel
>Localised Format</guilabel
> is the one you can specify under <guilabel
>Country &amp; Language</guilabel
> in &kcontrol;. For the <guilabel
>Custom</guilabel
> format you can get a description of the possible values by pressing <keycombo action="simul"
>&Shift;<keycap
>F1</keycap
></keycombo
> and then clicking on <guilabel
>Custom</guilabel
> option.</para>

</sect2>

<sect2 id="configure-appearance-systemtray">
<title
>System Tray</title>

<para
>If you enable the system tray icon then a small &kmail; icon with the number of unread messages will be shown in the system tray. You can enable &kmail;'s system tray icon with <guilabel
>Enable system tray icon</guilabel
>, and with <guilabel
>System Tray Mode</guilabel
> you can specify whether the tray icon should always be shown or only if you have unread messages.</para>

<para
>If the icon is visible then you can hide &kmail;'s main window by clicking on the icon or by clicking on the window close button. By clicking on the icon you can make &kmail;'s main window visible again. If you click on the icon with the <mousebutton
>right</mousebutton
> mousebutton then you get a menu with a few useful commands. You can check for new mail, create a new message or quit &kmail;. Additionally, there is the entry <guilabel
>New Messages In</guilabel
> which lists all folders containing unread messages. If you choose one of those folders then this folder will be selected in &kmail;'s main window. </para>

</sect2>

<!-- fixme?: date + less than/greater than broken in kmail? -->
<!-- fixme?: "group" wording in program -->

</sect1>

  <sect1 id="configure-composer">
    <title
>Composer Page </title>

    <sect2 id="configure-composer-general">
      <title
>General </title>

      <variablelist>
	<varlistentry id="configure-composer-general-append-signature">
	  <term>
	    <guilabel
>Automatically append signature</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, your signature as defined in the <link linkend="configure-identity-signature"
>identity page</link
> is automatically included at the end of all messages you create (&ie; new messages, replies &etc;). </para>
	  </listitem>
	</varlistentry>
	<varlistentry id="configure-composer-general-smart-quoting">
	  <term>
	    <guilabel
>Use smart quoting</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will break long lines but will try to keep the correct quoting (&eg; the <quote
>&gt; </quote
> will always be at the start of the line). </para>
	  </listitem>
	</varlistentry>
	<varlistentry id="configure-composer-general-auto-request-mdns">
	  <term>
	    <guilabel
>Automatically request message disposition notifications</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, <xref linkend="composer-options-request-mdn"/> will default to <emphasis
>on</emphasis
>. Check this option only if you know what you are doing. &mdn;s are considered a nuisance (or are simply ignored) by a lot of people. It is better to decide to request them on a message-by-message basis. </para>
	  </listitem>
	</varlistentry>
	<varlistentry id="configure-composer-general-word-wrap">
	  <term>
	    <guilabel
>Word wrap at column</guilabel>
	  </term>
	  <listitem>
	    <para
>Lets you turn word wrapping on and off in the composer window and lets you set the column at which words will be wrapped (you probably should not need to change the default value, which is <literal
>78</literal
>). </para>
	  </listitem>
	</varlistentry>
	<varlistentry id="configure-composer-general-autosave-interval">
	  <term>
	    <guilabel
>Autosave interval</guilabel>
	  </term>
	  <listitem>
	    <para
>A backup copy of the text in the composer window can be created regularly. This option lets you specify the interval used to create the backup. You can disable autosaving by setting it to the value <literal
>0</literal
>. </para>
	  </listitem>
	</varlistentry>
	<varlistentry id="configure-composer-general-external-editor">
	  <term>
	    <guilabel
>External Editor</guilabel>
	  </term>
	  <listitem>
	    <para
>If you do not like the Composer you can use a different editor. Note that the composer window will still open and the external editor will open as soon as you type just one character in the body of the message. If you are done, save the text and exit the editor. The text will now appear in the composer window, where you can send it. Note that your editor may not return immediately, you have to use &eg; <userinput
> <command
> gvim <option
>-f</option
> <varname
>%f</varname
> </command
> </userinput
> for <application
>gvim</application
>. </para>
	  </listitem>
	</varlistentry>
      </variablelist>

    </sect2>


<sect2 id="configure-composer-phrases">
<title
>Phrases</title>

<para
>The <guilabel
>Phrases</guilabel
> tab lets you define the automatically generated lines that are added to message replies, forwarded messages, and the character that is added in front of quoted text. There are special &percnt;-denoted characters that will insert certain values, which are also displayed at the top of the <guilabel
>Phrases</guilabel
> section. You can add reply phrases in languages other than your default &kde; language using the <guibutton
>Add...</guibutton
> button. You can then choose between different languages with the <guilabel
>Language</guilabel
> drop down box. This will only work for languages whose i18n package you have installed.</para>

</sect2>

<sect2 id="configure-composer-subject">
<title
>Subject</title>

<para
>This section contains a list of prefixes for <quote
>Reply</quote
> and <quote
>Forward</quote
>. If you receive messages that use prefixes different to the standard ones, you can add them here so &kmail; will recognise them. This way &kmail; can ignore them for sorting messages and when setting the subject of a reply or a forwarded messages, and optionally replace them with <quote
>Re:</quote
> or <quote
>Fwd:</quote
> respectively.</para>

</sect2>

<sect2 id="configure-composer-charset">
<title
>Charset</title>

<para
>Here you can manage the default charsets used for your own messages. Every message you send will be checked if it is written in one of the listed charsets, starting at the top of the list. If it is, this charset will be used. If it is not, a dialogue will show up and tell you that you manually have to choose a charset using <menuchoice
><guimenu
>Options</guimenu
><guisubmenu
>Set Encoding</guisubmenu
></menuchoice
>. </para>

<para
>If you select <guilabel
>Keep original charset when replying or forwarding (if possible)</guilabel
>, the original message's charset will be kept, unless there are now characters that cannot be represented using that charset.</para>

</sect2>

<sect2 id="configure-composer-headers">
<title
>Headers</title>

<para
>Check the <guilabel
>Use custom message-id suffix</guilabel
> checkbox if you want &kmail; to generate Message-Id's with a custom suffix. Enter the desired suffix in the <guilabel
>Custom message-id suffix</guilabel
> field. Please make sure that the suffix that you specify is world-wide unique. The best thing is to use the name of a domain which you are the owner of. If you do not check <guilabel
>Use custom Message-Id suffix</guilabel
> then &kmail; will automatically generate the complete Message-Id. If you do not know what this is all about do not check this option.</para>

<para
>The <guilabel
>Define custom mime header fields</guilabel
> list sets the headers that &kmail; will use for its outgoing messages. You can both invent new fields and overwrite existing ones. This feature is only useful for advanced users.</para>

</sect2>

<sect2 id="configure-composer-attachments">
<title
>Attachments</title>

<para
>If you have to send attachments with filenames containing non-English characters to users of Outlook(TM) or Outlook Express(TM) then you might want to check the <guilabel
>Outlook-compatible attachment naming</guilabel
> option. &kmail; will then encode the attachment names in a non-standard way that is understood by Outlook(TM).</para>
<para
>Note that &kmail; will create non-standard compliant messages, and consequently it is possible that your messages will not be understood by standard-compliant mail clients. So, unless you have no other choice, you should not enable this option.</para>

<para
>Check the <guilabel
>Enable detection of missing attachments</guilabel
> checkbox if you want &kmail; to warn you whenever you are about to send a message without attachments although the message text contains certain words which indicate that you wanted to include an attachment. The list of key words can be modified.</para>

</sect2>

</sect1>

  <sect1 id="configure-security">
    <title
>Security Page </title>

    <sect2 id="configure-security-reading">
      <title
>Reading </title>

      <para
>On this tab you can configure security-relevant options for reading messages. </para>

      <variablelist>

	<varlistentry id="configure-security-reading-prefer-html">
	  <term>
	    <guilabel
>Prefer HTML to plain text</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will show &html; messages with their &html; formatting and layout. We strongly recommend to leave this option off, as security problems with &html; might show up. When this option is off, you can still read &html; messages, but only as plain text. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-reading-external-references">
	  <term>
	    <guilabel
>Allow messages to load external references from the Internet</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; can load external images, style sheets &etc; from the Internet when you look at an &html; message. We strongly recommend to leave this option off (although it has no effect if you only view plain text messages). By adding external references to their messages, people sending spam can detect that and when you have looked at their message. Note that this option has no effect on &Java;, JavaScript and Plugins - these are disabled anyway and cannot be enabled at all. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-reading-mdns">
	  <term>
	    <guilabel
>Message Disposition Notifications</guilabel>
	  </term>
	  <listitem>
	    <para
>&mdn;s are a generalisation of what is commonly called a <quote
>read receipt</quote
>. The message author requests a disposition notification to be sent and the receiver's mail program generates a reply from which the author can learn what happened to his message. Common disposition types include <quote
>displayed</quote
> (&ie; read), <quote
>deleted</quote
> and <quote
>dispatched</quote
> (&eg; forwarded). </para>
	    <para
>The following options (listed as <guilabel
>Send policy</guilabel
>) are available to control <emphasis
>when</emphasis
> &kmail; sends &mdn;s: </para>
	    <variablelist>
	      <varlistentry>
		<term
><guilabel
>Ignore</guilabel
> (recommended) </term>
		<listitem>
		  <para
>Ignores any request for disposition notifications. No &mdn; will ever be sent automatically. </para>
		</listitem>
	      </varlistentry>
	      <varlistentry>
		<term>
		  <guilabel
>Ask</guilabel>
		</term>
		<listitem>
		  <para
>Answers requests only after asking the user for permission. This way, you can send &mdn;s for selected messages while denying or ignoring them for others. </para>
		</listitem>
	      </varlistentry>
	      <varlistentry>
		<term>
		  <guilabel
>Deny</guilabel>
		</term>
		<listitem>
		  <para
>Always sends a <quote
>denied</quote
> notification. This is only <emphasis
>slightly</emphasis
> better than always sending &mdn;s. The author will still know that the messages has been acted upon, he just cannot tell whether it was deleted or read &etc; </para>
		</listitem>
	      </varlistentry>
	      <varlistentry>
		<term>
		  <guilabel
>Always send</guilabel>
		</term>
		<listitem>
		  <para
>Always sends the requested disposition notification. That means that the author of the message gets to know when the message was acted upon and, in addition, what happened to it (displayed, deleted &etc;). This option is strongly discouraged, but since it makes sense where privacy is not a concern, &eg; in customer relationship management, it has been made available. </para>
		</listitem>
	      </varlistentry>
	    </variablelist>
	    <para
>If you are unsure, experiment a while with <guilabel
>Ask</guilabel
> and if you find &kmail;s questions annoying, switch to <guilabel
>Ignore</guilabel
>. </para>
	    <para
>The following options (listed as <guilabel
>Quote original message</guilabel
>) are available to control <emphasis
>how much</emphasis
> of the original message &kmail; sends back in &mdn;s. </para>
	    <variablelist>
	      <varlistentry>
		<term>
		  <guilabel
>Nothing</guilabel>
		</term>
		<listitem>
		  <para
>No parts of the message other than the mandatory message-id and the original recipient is included in the &mdn; reply. This preserves enough information for the sender to find the message in his sent messages for which this &mdn; was generated. </para>
		</listitem>
	      </varlistentry>
	      <varlistentry>
		<term>
		  <guilabel
>Full message</guilabel>
		</term>
		<listitem>
		  <para
>Attaches the complete message to the disposition notification. Usually, this is overkill. It does not add any valuable information that cannot be deduced from the message headers alone, but people sometimes insist on this, since it is much easier for humans to correlate the content of the message than just the headers to what they sent earlier. </para>
		</listitem>
	      </varlistentry>
	      <varlistentry>
		<term>
		  <guilabel
>Only headers</guilabel>
		</term>
		<listitem>
		  <para
>Attaches only the headers to the disposition notification. This is usually enough to enable both humans (by subject) and computers (by message-id) to easily correlate &mdn; and original message. </para>
		</listitem>
	      </varlistentry>
	    </variablelist>
	    <para
>If unsure, leave the option at the default. </para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>
	    <guilabel
>Do not send MDNs in response to encrypted messages</guilabel>
	  </term>
	  <listitem>
	    <para
>This option suppresses the sending of &mdn;s if the message is encrypted (partially or in whole). This thwarts attempts to use &kmail;'s &mdn; feature as an <emphasis
>oracle</emphasis
> to deduce whether you were able to decrypt the message or not. </para>
	    <para
>Strictly speaking, this option is not needed, since &kmail; sends &mdn;s regardless of whether the message could be successfully decrypted or not (the disposition notification request resides in the unencrypted part of the message), but it gives the security-conscious user the choice to either send them always if requested (option unchecked), or never (option checked). </para>
	    <para
>If unsure, leave the option checked. </para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>
	    <guilabel
>Automatically import keys and certificates</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; automatically imports any attachments containing &openpgp; keys into your local keyring, and any attachments containing &smime; keys into your local key box. </para>
	    <note>
	      <para
>Verifying &smime; signatures always involves importing the contained certificates. This option thus does not affect this. It is also unrelated to &gpg;'s <option
>auto-key-retrieve</option
> feature, where &gpg; will try to import unknown keys from a key server. </para>
	    </note>
	  </listitem>
	</varlistentry>
      </variablelist>
    </sect2>

    <sect2 id="configure-security-composing">
      <title
>Composing </title>

      <para
>On this tab you can configure security-relevant options for composing messages. </para>

      <variablelist>

	<varlistentry id="configure-security-composing-automatically-sign">
	  <term>
	    <guilabel
>Automatically sign messages</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, the <xref linkend="composer-options-sign-message"/> option in the composer will default to <emphasis
>on</emphasis
>. </para>
	    <para
>However, you can still switch it on and off on a per-message basis. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-composing-encrypt-to-self">
	  <term>
	    <guilabel
>Always encrypt to self</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, any message that is encrypted to the recipients will additionally be encrypted to yourself. </para>
	    <warning>
	      <para
>If you uncheck this option, you may not be able to decrypt the messages written by yourself and encrypted to other people anymore. </para>
	    </warning>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-composing-store-sent-encrypted">
	  <term>
	    <guilabel
>Store sent messages encrypted</guilabel
><!--
	    --><footnote>
	      <para
>This options enables a mode of using mail encryption that is sometimes (misleadingly) called <quote
>transport-only</quote
> encryption. In this mode of operation, the message encryption is stripped off as soon as the message has reached its destination. The encryption lasts only while the message is on its way. </para>
	      <para
>&kmail; supports this mode half-heartedly, since such functionality should better placed at the mail <emphasis
>server</emphasis
> (<acronym
>MTA</acronym
>) than at the mail <emphasis
>client</emphasis
> (<acronym
>MUA</acronym
>) level. Thus, future versions of &kmail; may drop support for this option. </para>
	    </footnote>
	  </term>
	  <listitem>
	    <para
>If checked, messages are stored in your <guilabel
>sent-mail</guilabel
> folder just as you sent them (&ie; if they were encrypted, they are also stored that way). </para>
	    <para
>If unchecked, messages will <emphasis
>always</emphasis
> be stored unencrypted in your <guilabel
>sent-mail</guilabel
> folder, even if they are sent encrypted. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-composing-show-encryption-key">
	  <term>
	    <guilabel
>Always show the encryption keys for approval</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, everytime you encrypt a message, a dialogue will appear that presents you with the encryption keys that will be used for each recipient. You can then review the choice of keys, change them, and approve or cancel the encryption operation. We recommend to keep this option checked, since it makes the encryption process more transparent. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-composing-opportunistic-encryption">
	  <term>
	    <guilabel
>Automatically encrypt messages whenever possible</guilabel>
	  </term>
	  <listitem>
	    <para
>Also called <quote
>opportunistic encryption</quote
>. If checked, &kmail; will try to match recipients to (&openpgp; or &smime;) keys even when you did <emphasis
>not</emphasis
> specifically request encryption. If usable keys are found for all recipients, &kmail; will ask whether or not you want to encrypt the message. </para>
	    <para
>It is highly recommended to turn this on, as it makes encrypting messages really easy to use. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-composing-never-sign-encrypt-drafts">
	  <term>
	    <guilabel
>Never sign/encrypt when saving as draft</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will not attempt to sign and/or encrypt messages that are merely saved to the <guilabel
>drafts</guilabel
> folder. This is more convenient, and does not result in a gross loss of security, provided the drafts folder is safe. &imap; users might want this options turned off, if their <guilabel
>drafts</guilabel
> folder is on the server. </para>
	  </listitem>
	</varlistentry>

      </variablelist>

    </sect2>

    <sect2 id="configure-security-warnings">
      <title
>Warnings </title>

      <para
>On this tab you can switch security-relavant warnings on and off. </para>

      <variablelist>

	<varlistentry id="configure-security-warnings-warn-send-unsigned">
	  <term>
	    <guilabel
>Warn when trying to send unsigned messages</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will show a warning if for whatever reason a message would be sent without being digitally signed. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-warnings-warn-send-unencrypted">
	  <term>
	    <guilabel
>Warn when trying to send unencrypted messages</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will show a warning if for whatever reason a message would be sent without being encrypted. </para>
	    <note>
	      <para
>While it is common to sign all outgoing messages, encrypting them is not. So unless your company has a policy of never sending any unencrypted messages, it might be a good idea to keep this option switched off and rely on <link linkend="configure-security-composing-opportunistic-encryption"
>opportunistic encryption</link
> to alert you if you <emphasis
>could</emphasis
> send encrypted messages, but did not request it. </para>
	    </note>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-warnings-warn-receiver-email-not-in-cert">
	  <term>
	    <guilabel
>Warn if receiver's email address is not in certificate</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will emit a warning if an &smime; certifciate or &openpgp; key will be used for a recipient whose email address is not listed in the email addresses stored in the certificate. </para>
	    <para
>Situations in which this warning will trigger include when configuring your per-identity &openpgp; keys or &smime; certificates, when encrypting, and when verifying signatures, if the signature was made with a certificate that does not include the email address of the sender. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-warnings-warn-near-expire">
	  <term>
	    <guilabel
>Warn if certificates/keys expire soon</guilabel>
	  </term>
	  <listitem>
	    <para
>If checked, &kmail; will warn when an &smime; certificate or &openpgp; key is used which will expire soon. </para>
	    <para
>The period in which to warn before key/certificate expiration can then be configured separately for signing and encryption keys, as well as (in the case of &smime;), for end-user certificates, intermediate <acronym
>CA</acronym
> certificates and root certificates. </para>
	  </listitem>
	</varlistentry>

	<varlistentry id="configure-security-warnings-reenable-all-warnings">
	  <term>
	    <guilabel
>Re-Enable All &quot;Don&apos;t Ask Again&quot; Warnings</guilabel>
	  </term>
	  <listitem>
	    <para
>Apart from the main warnings described above, there are more warning and information messages, which contain an option to not show them again. If you would like to re-enable them after choosing not to show them again, you can achieve this by pressing this button. <footnote
> <para
>This will re-enable <emphasis
>all</emphasis
> such warnings for &kmail;. It does not make much sense to allow more fine-grained selection of which warnings to show since you can just check the option to suppress them again when they next show up. </para>
	      </footnote>
	    </para>
	  </listitem>
	</varlistentry>

      </variablelist>

    </sect2>

    <sect2 id="configure-security-smime-validation">
      <title
>&smime; Validation </title>

      <para
>This tab contains selected entries from &gpgsm;'s <link linkend="configure-security-crypto-backends-configure"
>dynamic backend configuration dialogue</link
>. Please refer to the &gpgsm; manual for a description of these options. </para>
    </sect2>

    <sect2 id="configure-security-crypto-backends">
      <title
>Crypto Backends </title>

      <para
>On this tab you can configure which crypto backends are to be used for &openpgp; and &smime; cryptographic operations (such as signing and encrypting). </para>

      <para
>On the right-hand side, you see a list of available backends. Below each backend entry, you can see what protocols (&openpgp; and/or &smime;) the backend supports. If a protocol is not listed, the backend does not support it. If it is listed, but greyed out, the backend supports the protocol, but some required programs were not found, or other errors occurred during initialisation. If you press <guibutton
>Rescan</guibutton
>, a dialogue box will appear that lists reasons for the initialisation failure. </para>

      <para id="configure-security-crypto-backends-configure"
>To configure a backend, select it in the list of available backends and press <guibutton
>Configure...</guibutton
>. The per-backend configuration dialogue is dynamically created from the information returned by the backend. It may therefore change if you update the backend applications, although &kmail; itself is unchanged. If the <guibutton
>Configure...</guibutton
> button is disabled, the backend does not support a backend configuration dialogue. </para>

      <para
>Please refer to the manuals of the applications underlying each backend for a description of the options presented in the backend configuration dialogues. </para>

      <para
>In front of each backend's protocol entries, you can see a checkbox, with which you select which backend is to be used for a given protocol. These checkboxes are exclusive per protocol, meaning that if you select a backend to perform &openpgp; operations, any previously selected &openpgp; implementation will be unselected, but the &smime; backend selection will be unchanged. If no backend is selected for a given protocol, that protocol is effectively disabled for use in &kmail;. </para>

    </sect2>

  </sect1
> <!-- configure-security -->

<sect1 id="configure-misc">
<title
>Misc Page</title>

<sect2 id="configure-misc-folders">
<title
>Folders</title>

<variablelist>

<varlistentry>
<term
><guilabel
>Ask for confirmation before moving all messages to the wastebin</guilabel
></term>
<listitem>
<para
>Enable this option if you want to be asked for confirmation whenever you use <menuchoice
><guimenu
>Folder</guimenu
><guimenuitem
>Move All Messages to Wastebin</guimenuitem
></menuchoice
>.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Exclude important messages from expiry</guilabel
></term>
<listitem>
<para
>Enable this option if important messages should never be deleted during message expiration, &ie; during automatic deletion of old messages.</para>
</listitem>
</varlistentry>

<varlistentry id="configure-misc-folders-go-unread">
<term
><guilabel
>When trying to find unread messages</guilabel
></term>
<listitem>
<para
>This option controls what happens if you press one of the shortcuts to go to the next or previous unread message (&eg; <keycap
>Space</keycap
>). If you ask &kmail; to go to the next unread message although there is no unread message below the currently selected message then the following happens: <itemizedlist
> <listitem
> <para
>If <guilabel
>Do not Loop</guilabel
> is selected then nothing will happen. </para
> </listitem
> <listitem
> <para
>If <guilabel
>Loop in Current Folder</guilabel
> is selected then &kmail; will search from the beginning of the current folder for an unread message. If none is found then nothing happens.</para
> </listitem
> <listitem
> <para
>If <guilabel
>Loop in All Folders</guilabel
> is selected then &kmail; will first search in the current folder for another unread message. If none is found then &kmail; will search the next folder containing unread messages. </para
> </listitem
> </itemizedlist
> Correspondingly, if you ask &kmail; to go to the previous unread message. </para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Jump to first unread message when entering a folder</guilabel
></term>
<listitem>
<para
>If this option is enabled &kmail; will go to the first unread message when you enter a folder; if it is not enabled, &kmail; will go to first new message or, if there is no new message, to the message that was selected when you last left the folder.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Mark selected message as read after...</guilabel
></term>
<listitem>
<para
>When you select a <guilabel
>new</guilabel
> or <guilabel
>unread</guilabel
> message, &kmail; will change the message's status to <guilabel
>read</guilabel
> after the number of seconds entered here. If you disable this option, messages will keep their <guilabel
>new</guilabel
> or <guilabel
>unread</guilabel
> status.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Ask for action after dragging messages to another folder</guilabel
></term>
<listitem>
<para
>When you drag a message to a different folder, a small popup will ask you if you want to move or copy the message. If you disable this option, the message will be moved immediately, without a popup.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>By default, message folders on disk are...</guilabel
></term>
<listitem>
<para
>Here you can set the default <link linkend="folders-format"
>folder format</link
> that is used when you create a new folder.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Open this folder on startup</guilabel
></term>
<listitem>
<para
>Here you can set the folder that should be selected by default if you start &kmail;. If you use only &imap; folders then you might want to set this to your &imap; inbox folder.</para>
</listitem>
</varlistentry>

<varlistentry>
<term
><guilabel
>Empty wastebin on program exit</guilabel
></term>
<listitem>
<para
>The wastebin folder is cleared of messages when you quit &kmail; if this option is selected.</para
> 
</listitem>
</varlistentry>

</variablelist>

</sect2>

<sect2 id="configure-misc-groupware">
<title
>Groupware</title>

<variablelist>

<varlistentry>
<term
><guilabel
>Enable IMAP resource functionality</guilabel
></term>
<listitem>
<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
>KDE Kolab client</guilabel
>. This option being enabled you will also need to add the appropriate resources from the <guilabel
>KDE Control Center</guilabel
> (kcontrol) in the <guilabel
>KDE Resources Configuration</guilabel
> section. <guilabel
>Kolab</guilabel
> resources have to be added in case the resource functionality applies to a <guilabel
>KDE Kolab client</guilabel
> set-up.</para>
</listitem>
</varlistentry>
<varlistentry id="configure-misc-format-groupware-folders">
<term
><guilabel
>Format used for the groupware folders</guilabel
></term>
<listitem>
<para
>Choose the storage format for the groupware folders</para>
<itemizedlist>
<listitem>
<para
>Default format is <guilabel
>Standard (Ical/Vcard)</guilabel
> for calendar folders (Ical) and addressbook folders (Vcard). This makes all Kontact features available.</para>
</listitem>
<listitem>
<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>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Language of the groupware folders</guilabel
></term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Resource folders are in account</guilabel
></term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Hide groupware folders</guilabel
></term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Mangle From:/To: headers in replies to invitations</guilabel
></term>
<listitem>
<para
>Enable this option to make Microsoft Outlook(tm) understand your answers to invitations replies.</para>
</listitem>
</varlistentry>
<varlistentry>
<term
><guilabel
>Send invitations in the mail body</guilabel
></term>
<listitem>
<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
> 
</listitem>
</varlistentry>
</variablelist>
</sect2>


</sect1>

</chapter>