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
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
6642
6643
6644
6645
6646
6647
6648
6649
6650
6651
6652
6653
6654
6655
6656
6657
6658
6659
6660
6661
6662
6663
6664
6665
6666
6667
6668
6669
6670
6671
6672
6673
6674
6675
6676
6677
6678
6679
6680
6681
6682
6683
6684
6685
6686
6687
6688
6689
6690
6691
6692
6693
6694
6695
6696
6697
6698
6699
6700
6701
6702
6703
6704
6705
6706
6707
6708
6709
6710
6711
6712
6713
6714
6715
6716
6717
6718
6719
6720
6721
6722
6723
6724
6725
6726
6727
6728
6729
6730
6731
6732
6733
6734
6735
6736
6737
6738
6739
6740
6741
6742
6743
6744
6745
6746
6747
6748
6749
6750
6751
6752
6753
6754
6755
6756
6757
6758
6759
6760
6761
6762
6763
6764
6765
6766
6767
6768
6769
6770
6771
6772
6773
6774
6775
6776
6777
6778
6779
6780
6781
6782
6783
6784
6785
6786
6787
6788
6789
6790
6791
6792
6793
6794
6795
6796
6797
6798
6799
6800
6801
6802
6803
6804
6805
6806
6807
6808
6809
6810
6811
6812
6813
6814
6815
6816
6817
6818
6819
6820
6821
6822
6823
6824
6825
6826
6827
6828
6829
6830
6831
6832
6833
6834
6835
6836
6837
6838
6839
6840
6841
6842
6843
6844
6845
6846
6847
6848
6849
6850
6851
6852
6853
6854
6855
6856
6857
6858
6859
6860
6861
6862
6863
6864
6865
6866
6867
6868
6869
6870
6871
6872
6873
6874
6875
6876
6877
6878
6879
6880
6881
6882
6883
6884
6885
6886
6887
6888
6889
6890
6891
6892
6893
6894
6895
6896
6897
6898
6899
6900
6901
6902
6903
6904
6905
6906
6907
6908
6909
6910
6911
6912
6913
6914
6915
6916
6917
6918
6919
6920
6921
6922
6923
6924
6925
6926
6927
6928
6929
6930
6931
6932
6933
6934
6935
6936
6937
6938
6939
6940
6941
6942
6943
6944
6945
6946
6947
6948
6949
6950
6951
6952
6953
6954
6955
6956
6957
6958
6959
6960
6961
6962
6963
6964
6965
6966
6967
6968
6969
6970
6971
6972
6973
6974
6975
6976
6977
6978
6979
6980
6981
6982
6983
6984
6985
6986
6987
6988
6989
6990
6991
6992
6993
6994
6995
6996
6997
6998
6999
7000
7001
7002
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012
7013
7014
7015
7016
7017
7018
7019
7020
7021
7022
7023
7024
7025
7026
7027
7028
7029
7030
7031
7032
7033
7034
7035
7036
7037
7038
7039
7040
7041
7042
7043
7044
7045
7046
7047
7048
7049
7050
7051
7052
7053
7054
7055
7056
7057
7058
7059
7060
7061
7062
7063
7064
7065
7066
7067
7068
7069
7070
7071
7072
7073
7074
7075
7076
7077
7078
7079
7080
7081
7082
7083
7084
7085
7086
7087
7088
7089
7090
7091
7092
7093
7094
7095
7096
7097
7098
7099
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7111
7112
7113
7114
7115
7116
7117
7118
7119
7120
7121
7122
7123
7124
7125
7126
7127
7128
7129
7130
7131
7132
7133
7134
7135
7136
7137
7138
7139
7140
7141
7142
7143
7144
7145
7146
7147
7148
7149
7150
7151
7152
7153
7154
7155
7156
7157
7158
7159
7160
7161
7162
7163
7164
7165
7166
7167
7168
7169
7170
7171
7172
7173
7174
7175
7176
7177
7178
7179
7180
7181
7182
7183
7184
7185
7186
7187
7188
7189
7190
7191
7192
7193
7194
7195
7196
7197
7198
7199
7200
7201
7202
7203
7204
7205
7206
7207
7208
7209
7210
7211
7212
7213
7214
7215
7216
7217
7218
7219
7220
7221
7222
7223
7224
7225
7226
7227
7228
7229
7230
7231
7232
7233
7234
7235
7236
7237
7238
7239
7240
7241
7242
7243
7244
7245
7246
7247
7248
7249
7250
7251
7252
7253
7254
7255
7256
7257
7258
7259
7260
7261
7262
7263
7264
7265
7266
7267
7268
7269
7270
7271
7272
7273
7274
7275
7276
7277
7278
7279
7280
7281
7282
7283
7284
7285
7286
7287
7288
7289
7290
7291
7292
7293
7294
7295
7296
7297
7298
7299
7300
7301
7302
7303
7304
7305
7306
7307
7308
7309
7310
7311
7312
7313
7314
7315
7316
7317
7318
7319
7320
7321
7322
7323
7324
7325
7326
7327
7328
7329
7330
7331
7332
7333
7334
7335
7336
7337
7338
7339
7340
7341
7342
7343
7344
7345
7346
7347
7348
7349
7350
7351
7352
7353
7354
7355
7356
7357
7358
7359
7360
7361
7362
7363
7364
7365
7366
7367
7368
7369
7370
7371
7372
7373
7374
7375
7376
7377
7378
7379
7380
7381
7382
7383
7384
7385
7386
7387
7388
7389
7390
7391
7392
7393
7394
7395
7396
7397
7398
7399
7400
7401
7402
7403
7404
7405
7406
7407
7408
7409
7410
7411
7412
7413
7414
7415
7416
7417
7418
7419
7420
7421
7422
7423
7424
7425
7426
7427
7428
7429
7430
7431
7432
7433
7434
7435
7436
7437
7438
7439
7440
7441
7442
7443
7444
7445
7446
7447
7448
7449
7450
7451
7452
7453
7454
7455
7456
7457
7458
7459
7460
7461
7462
7463
7464
7465
7466
7467
7468
7469
7470
7471
7472
7473
7474
7475
7476
7477
7478
7479
7480
7481
7482
7483
7484
7485
7486
7487
7488
7489
7490
7491
7492
7493
7494
7495
7496
7497
7498
7499
7500
7501
7502
7503
7504
7505
7506
7507
7508
7509
7510
7511
7512
7513
7514
7515
7516
7517
7518
7519
7520
7521
7522
7523
7524
7525
7526
7527
7528
7529
7530
7531
7532
7533
7534
7535
7536
7537
7538
7539
7540
7541
7542
7543
7544
7545
7546
7547
7548
7549
7550
7551
7552
7553
7554
7555
7556
7557
7558
7559
7560
7561
7562
7563
7564
7565
7566
7567
7568
7569
7570
7571
7572
7573
7574
7575
7576
7577
7578
7579
7580
7581
7582
7583
7584
7585
7586
7587
7588
7589
7590
7591
7592
7593
7594
7595
7596
7597
7598
7599
7600
7601
7602
7603
7604
7605
7606
7607
7608
7609
7610
7611
7612
7613
7614
7615
7616
7617
7618
7619
7620
7621
7622
7623
7624
7625
7626
7627
7628
7629
7630
7631
7632
7633
7634
7635
7636
7637
7638
7639
7640
7641
7642
7643
7644
7645
7646
7647
7648
7649
7650
7651
7652
7653
7654
7655
7656
7657
7658
7659
7660
7661
7662
7663
7664
7665
7666
7667
7668
7669
7670
7671
7672
7673
7674
7675
7676
7677
7678
7679
7680
7681
7682
7683
7684
7685
7686
7687
7688
7689
7690
7691
7692
7693
7694
7695
7696
7697
7698
7699
7700
7701
7702
7703
7704
7705
7706
7707
7708
7709
7710
7711
7712
7713
7714
7715
7716
7717
7718
7719
7720
7721
7722
7723
7724
7725
7726
7727
7728
7729
7730
7731
7732
7733
7734
7735
7736
7737
7738
7739
7740
7741
7742
7743
7744
7745
7746
7747
7748
7749
7750
7751
7752
7753
7754
7755
7756
7757
7758
7759
7760
7761
7762
7763
7764
7765
7766
7767
7768
7769
7770
7771
7772
7773
7774
7775
7776
7777
7778
7779
7780
7781
7782
7783
7784
7785
7786
7787
7788
7789
7790
7791
7792
7793
7794
7795
7796
7797
7798
7799
7800
7801
7802
7803
7804
7805
7806
7807
7808
7809
7810
7811
7812
7813
7814
7815
7816
7817
7818
7819
7820
7821
7822
7823
7824
7825
7826
7827
7828
7829
7830
7831
7832
7833
7834
7835
7836
7837
7838
7839
7840
7841
7842
7843
7844
7845
7846
7847
7848
7849
7850
7851
7852
7853
7854
7855
7856
7857
7858
7859
7860
7861
7862
7863
7864
7865
7866
7867
7868
7869
7870
7871
7872
7873
7874
7875
7876
7877
7878
7879
7880
7881
7882
7883
7884
7885
7886
7887
7888
7889
7890
7891
7892
7893
7894
7895
7896
7897
7898
7899
7900
7901
7902
7903
7904
7905
7906
7907
7908
7909
7910
7911
7912
7913
7914
7915
7916
7917
7918
7919
7920
7921
7922
7923
7924
7925
7926
7927
7928
7929
7930
7931
7932
7933
7934
7935
7936
7937
7938
7939
7940
7941
7942
7943
7944
7945
7946
7947
7948
7949
7950
7951
7952
7953
7954
7955
7956
7957
7958
7959
7960
7961
7962
7963
7964
7965
7966
7967
7968
7969
7970
7971
7972
7973
7974
7975
7976
7977
7978
7979
7980
7981
7982
7983
7984
7985
7986
7987
7988
7989
7990
7991
7992
7993
7994
7995
7996
7997
7998
7999
8000
8001
8002
8003
8004
8005
8006
8007
8008
8009
8010
8011
8012
8013
8014
8015
8016
8017
8018
8019
8020
8021
8022
8023
8024
8025
8026
8027
8028
8029
8030
8031
8032
8033
8034
8035
8036
8037
8038
8039
8040
8041
8042
8043
8044
8045
8046
8047
8048
8049
8050
8051
8052
8053
8054
8055
8056
8057
8058
8059
8060
8061
8062
8063
8064
8065
8066
8067
8068
8069
8070
8071
8072
8073
8074
8075
8076
8077
8078
8079
8080
8081
8082
8083
8084
8085
8086
8087
8088
8089
8090
8091
8092
8093
8094
8095
8096
8097
8098
8099
8100
8101
8102
8103
8104
8105
8106
8107
8108
8109
8110
8111
8112
8113
8114
8115
8116
8117
8118
8119
8120
8121
8122
8123
8124
8125
8126
8127
8128
8129
8130
8131
8132
8133
8134
8135
8136
8137
8138
8139
8140
8141
8142
8143
8144
8145
8146
8147
8148
8149
8150
8151
8152
8153
8154
8155
8156
8157
8158
8159
8160
8161
8162
8163
8164
8165
8166
8167
8168
8169
8170
8171
8172
8173
8174
8175
8176
8177
8178
8179
8180
8181
8182
8183
8184
8185
8186
8187
8188
8189
8190
8191
8192
8193
8194
8195
8196
8197
8198
8199
8200
8201
8202
8203
8204
8205
8206
8207
8208
8209
8210
8211
8212
8213
8214
8215
8216
8217
8218
8219
8220
8221
8222
8223
8224
8225
8226
8227
8228
8229
8230
8231
8232
8233
8234
8235
8236
8237
8238
8239
8240
8241
8242
8243
8244
8245
8246
8247
8248
8249
8250
8251
8252
8253
8254
8255
8256
8257
8258
8259
8260
8261
8262
8263
8264
8265
8266
8267
8268
8269
8270
8271
8272
8273
8274
8275
8276
8277
8278
8279
8280
8281
8282
8283
8284
8285
8286
8287
8288
8289
8290
8291
8292
8293
8294
8295
8296
8297
8298
8299
8300
8301
8302
8303
8304
8305
8306
8307
8308
8309
8310
8311
8312
8313
8314
8315
8316
8317
8318
8319
8320
8321
8322
8323
8324
8325
8326
8327
8328
8329
8330
8331
8332
8333
8334
8335
8336
8337
8338
8339
8340
8341
8342
8343
8344
8345
8346
8347
8348
8349
8350
8351
8352
8353
8354
8355
8356
8357
8358
8359
8360
8361
8362
8363
8364
8365
8366
8367
8368
8369
8370
8371
8372
8373
8374
8375
8376
8377
8378
8379
8380
8381
8382
8383
8384
8385
8386
8387
8388
8389
8390
8391
8392
8393
8394
8395
8396
8397
8398
8399
8400
8401
8402
8403
8404
8405
8406
8407
8408
8409
8410
8411
8412
8413
8414
8415
8416
8417
8418
8419
8420
8421
8422
8423
8424
8425
8426
8427
8428
8429
8430
8431
8432
8433
8434
8435
8436
8437
8438
8439
8440
8441
8442
8443
8444
8445
8446
8447
8448
8449
8450
8451
8452
8453
8454
8455
8456
8457
8458
8459
8460
8461
8462
8463
8464
8465
8466
8467
8468
8469
8470
8471
8472
8473
8474
8475
8476
8477
8478
8479
8480
8481
8482
8483
8484
8485
8486
8487
8488
8489
8490
8491
8492
8493
8494
8495
8496
8497
8498
8499
8500
8501
8502
8503
8504
8505
8506
8507
8508
8509
8510
8511
8512
8513
8514
8515
8516
8517
8518
8519
8520
8521
8522
8523
8524
8525
8526
8527
8528
8529
8530
8531
8532
8533
8534
8535
8536
8537
8538
8539
8540
8541
8542
8543
8544
8545
8546
8547
8548
8549
8550
8551
8552
8553
8554
8555
8556
8557
8558
8559
8560
8561
8562
8563
8564
8565
8566
8567
8568
8569
8570
8571
8572
8573
8574
8575
8576
8577
8578
8579
8580
8581
8582
8583
8584
8585
8586
8587
8588
8589
8590
8591
8592
8593
8594
8595
8596
8597
8598
8599
8600
8601
8602
8603
8604
8605
8606
8607
8608
8609
8610
8611
8612
8613
8614
8615
8616
8617
8618
8619
8620
8621
8622
8623
8624
8625
8626
8627
8628
8629
8630
8631
8632
8633
8634
8635
8636
8637
8638
8639
8640
8641
8642
8643
8644
8645
8646
8647
8648
8649
8650
8651
8652
8653
8654
8655
8656
8657
8658
8659
8660
8661
8662
8663
8664
8665
8666
8667
8668
8669
8670
8671
8672
8673
8674
8675
8676
8677
8678
8679
8680
8681
8682
8683
8684
8685
8686
8687
8688
8689
8690
8691
8692
8693
8694
8695
8696
8697
8698
8699
8700
8701
8702
8703
8704
8705
8706
8707
8708
8709
8710
8711
8712
8713
8714
8715
8716
8717
8718
8719
8720
8721
8722
8723
8724
8725
8726
8727
8728
8729
8730
8731
8732
8733
8734
8735
8736
8737
8738
8739
8740
8741
8742
8743
8744
8745
8746
8747
8748
8749
8750
8751
8752
8753
8754
8755
8756
8757
8758
8759
8760
8761
8762
8763
8764
8765
8766
8767
8768
8769
8770
8771
8772
8773
8774
8775
8776
8777
8778
8779
8780
8781
8782
8783
8784
8785
8786
8787
8788
8789
8790
8791
8792
8793
8794
8795
8796
8797
8798
8799
8800
8801
8802
8803
8804
8805
8806
8807
8808
8809
8810
8811
8812
8813
8814
8815
8816
8817
8818
8819
8820
8821
8822
8823
8824
8825
8826
8827
8828
8829
8830
8831
8832
8833
8834
8835
8836
8837
8838
8839
8840
8841
8842
8843
8844
8845
8846
8847
8848
8849
8850
8851
8852
8853
8854
8855
8856
8857
8858
8859
8860
8861
8862
8863
8864
8865
8866
8867
8868
8869
8870
8871
8872
8873
8874
8875
8876
8877
8878
8879
8880
8881
8882
8883
8884
8885
8886
8887
8888
8889
8890
8891
8892
8893
8894
8895
8896
8897
8898
8899
8900
8901
8902
8903
8904
8905
8906
8907
8908
8909
8910
8911
8912
8913
8914
8915
8916
8917
8918
8919
8920
8921
8922
8923
8924
8925
8926
8927
8928
8929
8930
8931
8932
8933
8934
8935
8936
8937
8938
8939
8940
8941
8942
8943
8944
8945
8946
8947
8948
8949
8950
8951
8952
8953
8954
8955
8956
8957
8958
8959
8960
8961
8962
8963
8964
8965
8966
8967
8968
8969
8970
8971
8972
8973
8974
8975
8976
8977
8978
8979
8980
8981
8982
8983
8984
8985
8986
8987
8988
8989
8990
8991
8992
8993
8994
8995
8996
8997
8998
8999
9000
9001
9002
9003
9004
9005
9006
9007
9008
9009
9010
9011
9012
9013
9014
9015
9016
9017
9018
9019
9020
9021
9022
9023
9024
9025
9026
9027
9028
9029
9030
9031
9032
9033
9034
9035
9036
9037
9038
9039
9040
9041
9042
9043
9044
9045
9046
9047
9048
9049
9050
9051
9052
9053
9054
9055
9056
9057
9058
9059
9060
9061
9062
9063
9064
9065
9066
9067
9068
9069
9070
9071
9072
9073
9074
9075
9076
9077
9078
9079
9080
9081
9082
9083
9084
9085
9086
9087
9088
9089
9090
9091
9092
9093
9094
9095
9096
9097
9098
9099
9100
9101
9102
9103
9104
9105
9106
9107
9108
9109
9110
9111
9112
9113
9114
9115
9116
9117
9118
9119
9120
9121
9122
9123
9124
9125
9126
9127
9128
9129
9130
9131
9132
9133
9134
9135
9136
9137
9138
9139
9140
9141
9142
9143
9144
9145
9146
9147
9148
9149
9150
9151
9152
9153
9154
9155
9156
9157
9158
9159
9160
9161
9162
9163
9164
9165
9166
9167
9168
9169
9170
9171
9172
9173
9174
9175
9176
9177
9178
9179
9180
9181
9182
9183
9184
9185
9186
9187
9188
9189
9190
9191
9192
9193
9194
9195
9196
9197
9198
9199
9200
9201
9202
9203
9204
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223
9224
9225
9226
9227
9228
9229
9230
9231
9232
9233
9234
9235
9236
9237
9238
9239
9240
9241
9242
9243
9244
9245
9246
9247
9248
9249
9250
9251
9252
9253
9254
9255
9256
9257
9258
9259
9260
9261
9262
9263
9264
9265
9266
9267
9268
9269
9270
9271
9272
9273
9274
9275
9276
9277
9278
9279
9280
9281
9282
9283
9284
9285
9286
9287
9288
9289
9290
9291
9292
9293
9294
9295
9296
9297
9298
9299
9300
9301
9302
9303
9304
9305
9306
9307
9308
9309
9310
9311
9312
9313
9314
9315
9316
9317
9318
9319
9320
9321
9322
9323
9324
9325
9326
9327
9328
9329
9330
9331
9332
9333
9334
9335
9336
9337
9338
9339
9340
9341
9342
9343
9344
9345
9346
9347
9348
9349
9350
9351
9352
9353
9354
9355
9356
9357
9358
9359
9360
9361
9362
9363
9364
9365
9366
9367
9368
9369
9370
9371
9372
9373
9374
9375
9376
9377
9378
9379
9380
9381
9382
9383
9384
9385
9386
9387
9388
9389
9390
9391
9392
9393
9394
9395
9396
9397
9398
9399
9400
9401
9402
9403
9404
9405
9406
9407
9408
9409
9410
9411
9412
9413
9414
9415
9416
9417
9418
9419
9420
9421
9422
9423
9424
9425
9426
9427
9428
9429
9430
9431
9432
9433
9434
9435
9436
9437
9438
9439
9440
9441
9442
9443
9444
9445
9446
9447
9448
9449
9450
9451
9452
9453
9454
9455
9456
9457
9458
9459
9460
9461
9462
9463
9464
9465
9466
9467
9468
9469
9470
9471
9472
9473
9474
9475
9476
9477
9478
9479
9480
9481
9482
9483
9484
9485
9486
9487
9488
9489
9490
9491
9492
9493
9494
9495
9496
9497
9498
9499
9500
9501
9502
9503
9504
9505
9506
9507
9508
9509
9510
9511
9512
9513
9514
9515
9516
9517
9518
9519
9520
9521
9522
9523
9524
9525
9526
9527
9528
9529
9530
9531
9532
9533
9534
9535
9536
9537
9538
9539
9540
9541
9542
9543
9544
9545
9546
9547
9548
9549
9550
9551
9552
9553
9554
9555
9556
9557
9558
9559
9560
9561
9562
9563
9564
9565
9566
9567
9568
9569
9570
9571
9572
9573
9574
9575
9576
9577
9578
9579
9580
9581
9582
9583
9584
9585
9586
9587
9588
9589
9590
9591
9592
9593
9594
9595
9596
9597
9598
9599
9600
9601
9602
9603
9604
9605
9606
9607
9608
9609
9610
9611
9612
9613
9614
9615
9616
9617
9618
9619
9620
9621
9622
9623
9624
9625
9626
9627
9628
9629
9630
9631
9632
9633
9634
9635
9636
9637
9638
9639
9640
9641
9642
9643
9644
9645
9646
9647
9648
9649
9650
9651
9652
9653
9654
9655
9656
9657
9658
9659
9660
9661
9662
9663
9664
9665
9666
9667
9668
9669
9670
9671
9672
9673
9674
9675
9676
9677
9678
9679
9680
9681
9682
9683
9684
9685
9686
9687
9688
9689
9690
9691
9692
9693
9694
9695
9696
9697
9698
9699
9700
9701
9702
9703
9704
9705
9706
9707
9708
9709
9710
9711
9712
9713
9714
9715
9716
9717
9718
9719
9720
9721
9722
9723
9724
9725
9726
9727
9728
9729
9730
9731
9732
9733
9734
9735
9736
9737
9738
9739
9740
9741
9742
9743
9744
9745
9746
9747
9748
9749
9750
9751
9752
9753
9754
9755
9756
9757
9758
9759
9760
9761
9762
9763
9764
9765
9766
9767
9768
9769
9770
9771
9772
9773
9774
9775
9776
9777
9778
9779
9780
9781
9782
9783
9784
9785
9786
9787
9788
9789
9790
9791
9792
9793
9794
9795
9796
9797
9798
9799
9800
9801
9802
9803
9804
9805
9806
9807
9808
9809
9810
9811
9812
9813
9814
9815
9816
9817
9818
9819
9820
9821
9822
9823
9824
9825
9826
9827
9828
9829
9830
9831
9832
9833
9834
9835
9836
9837
9838
9839
9840
9841
9842
9843
9844
9845
9846
9847
9848
9849
9850
9851
9852
9853
9854
9855
9856
9857
9858
9859
9860
9861
9862
9863
9864
9865
9866
9867
9868
9869
9870
9871
9872
9873
9874
9875
9876
9877
9878
9879
9880
9881
9882
9883
9884
9885
9886
9887
9888
9889
9890
9891
9892
9893
9894
9895
9896
9897
9898
9899
9900
9901
9902
9903
9904
9905
9906
9907
9908
9909
9910
9911
9912
9913
9914
9915
9916
9917
9918
9919
9920
9921
9922
9923
9924
9925
9926
9927
9928
9929
9930
9931
9932
9933
9934
9935
9936
9937
9938
9939
9940
9941
9942
9943
9944
9945
9946
9947
9948
9949
9950
9951
9952
9953
9954
9955
9956
9957
9958
9959
9960
9961
9962
9963
9964
9965
9966
9967
9968
9969
9970
9971
9972
9973
9974
9975
9976
9977
9978
9979
9980
9981
9982
9983
9984
9985
9986
9987
9988
9989
9990
9991
9992
9993
9994
9995
9996
9997
9998
9999
10000
10001
10002
10003
10004
10005
10006
10007
10008
10009
10010
10011
10012
10013
10014
10015
10016
10017
10018
10019
10020
10021
10022
10023
10024
10025
10026
10027
10028
10029
10030
10031
10032
10033
10034
10035
10036
10037
10038
10039
10040
10041
10042
10043
10044
10045
10046
10047
10048
10049
10050
10051
10052
10053
10054
10055
10056
10057
10058
10059
10060
10061
10062
10063
10064
10065
10066
10067
10068
10069
10070
10071
10072
10073
10074
10075
10076
10077
10078
10079
10080
10081
10082
10083
10084
10085
10086
10087
10088
10089
10090
10091
10092
10093
10094
10095
10096
10097
10098
10099
10100
10101
10102
10103
10104
10105
10106
10107
10108
10109
10110
10111
10112
10113
10114
10115
10116
10117
10118
10119
10120
10121
10122
10123
10124
10125
10126
10127
10128
10129
10130
10131
10132
10133
10134
10135
10136
10137
10138
10139
10140
10141
10142
10143
10144
10145
10146
10147
10148
10149
10150
10151
10152
10153
10154
10155
10156
10157
10158
10159
10160
10161
10162
10163
10164
10165
10166
10167
10168
10169
10170
10171
10172
10173
10174
10175
10176
10177
10178
10179
10180
10181
10182
10183
10184
10185
10186
10187
10188
10189
10190
10191
10192
10193
10194
10195
10196
10197
10198
10199
10200
10201
10202
10203
10204
10205
10206
10207
10208
10209
10210
10211
10212
10213
10214
10215
10216
10217
10218
10219
10220
10221
10222
10223
10224
10225
10226
10227
10228
10229
10230
10231
10232
10233
10234
10235
10236
10237
10238
10239
10240
10241
10242
10243
10244
10245
10246
10247
10248
10249
10250
10251
10252
10253
10254
10255
10256
10257
10258
10259
10260
10261
10262
10263
10264
10265
10266
10267
10268
10269
10270
10271
10272
10273
10274
10275
10276
10277
10278
10279
10280
10281
10282
10283
10284
10285
10286
10287
10288
10289
10290
10291
10292
10293
10294
10295
10296
10297
10298
10299
10300
10301
10302
10303
10304
10305
10306
10307
10308
10309
10310
10311
10312
10313
10314
10315
10316
10317
10318
10319
10320
10321
10322
10323
10324
10325
10326
10327
10328
10329
10330
10331
10332
10333
10334
10335
10336
10337
10338
10339
10340
10341
10342
10343
10344
10345
10346
10347
10348
10349
10350
10351
10352
10353
10354
10355
10356
10357
10358
10359
10360
10361
10362
10363
10364
10365
10366
10367
10368
10369
10370
10371
10372
10373
10374
10375
10376
10377
10378
10379
10380
10381
10382
10383
10384
10385
10386
10387
10388
10389
10390
10391
10392
10393
10394
10395
10396
10397
10398
10399
10400
10401
10402
10403
10404
10405
10406
10407
10408
10409
10410
10411
10412
10413
10414
10415
10416
10417
10418
10419
10420
10421
10422
10423
10424
10425
10426
10427
10428
10429
10430
10431
10432
10433
10434
10435
10436
10437
10438
10439
10440
10441
10442
10443
10444
10445
10446
10447
10448
10449
10450
10451
10452
10453
10454
10455
10456
10457
10458
10459
10460
10461
10462
10463
10464
10465
10466
10467
10468
10469
10470
10471
10472
10473
10474
10475
10476
10477
10478
10479
10480
10481
10482
10483
10484
10485
10486
10487
10488
10489
10490
10491
10492
10493
10494
10495
10496
10497
10498
10499
10500
10501
10502
10503
10504
10505
10506
10507
10508
10509
10510
10511
10512
10513
10514
10515
10516
10517
10518
10519
10520
10521
10522
10523
10524
10525
10526
10527
10528
10529
10530
10531
10532
10533
10534
10535
10536
10537
10538
10539
10540
10541
10542
10543
10544
10545
10546
10547
10548
10549
10550
10551
10552
10553
10554
10555
10556
10557
10558
10559
10560
10561
10562
10563
10564
10565
10566
10567
10568
10569
10570
10571
10572
10573
10574
10575
10576
10577
10578
10579
10580
10581
10582
10583
10584
10585
10586
10587
10588
10589
10590
10591
10592
10593
10594
10595
10596
10597
10598
10599
10600
10601
10602
10603
10604
10605
10606
10607
10608
10609
10610
10611
10612
10613
10614
10615
10616
10617
10618
10619
10620
10621
10622
10623
10624
10625
10626
10627
10628
10629
10630
10631
10632
10633
10634
10635
10636
10637
10638
10639
10640
10641
10642
10643
10644
10645
10646
10647
10648
10649
10650
10651
10652
10653
10654
10655
10656
10657
10658
10659
10660
10661
10662
10663
10664
10665
10666
10667
10668
10669
10670
10671
10672
10673
10674
10675
10676
10677
10678
10679
10680
10681
10682
10683
10684
10685
10686
10687
10688
10689
10690
10691
10692
10693
10694
10695
10696
10697
10698
10699
10700
10701
10702
10703
10704
10705
10706
10707
10708
10709
10710
10711
10712
10713
10714
10715
10716
10717
10718
10719
10720
10721
10722
10723
10724
10725
10726
10727
10728
10729
10730
10731
10732
10733
10734
10735
10736
10737
10738
10739
10740
10741
10742
10743
10744
10745
10746
10747
10748
10749
10750
10751
10752
10753
10754
10755
10756
10757
10758
10759
10760
10761
10762
10763
10764
10765
10766
10767
10768
10769
10770
10771
10772
10773
10774
10775
10776
10777
10778
10779
10780
10781
10782
10783
10784
10785
10786
10787
10788
10789
10790
10791
10792
10793
10794
10795
10796
10797
10798
10799
10800
10801
10802
10803
10804
10805
10806
10807
10808
10809
10810
10811
10812
10813
10814
10815
10816
10817
10818
10819
10820
10821
10822
10823
10824
10825
10826
10827
10828
10829
10830
10831
10832
10833
10834
10835
10836
10837
10838
10839
10840
10841
10842
10843
10844
10845
10846
10847
10848
10849
10850
10851
10852
10853
10854
10855
10856
10857
10858
10859
10860
10861
10862
10863
10864
10865
10866
10867
10868
10869
10870
10871
10872
10873
10874
10875
10876
10877
10878
10879
10880
10881
10882
10883
10884
10885
10886
10887
10888
10889
10890
10891
10892
10893
10894
10895
10896
10897
10898
10899
10900
10901
10902
10903
10904
10905
10906
10907
10908
10909
10910
10911
10912
10913
10914
10915
10916
10917
10918
10919
10920
10921
10922
10923
10924
10925
10926
10927
10928
10929
10930
10931
10932
10933
10934
10935
10936
10937
10938
10939
10940
10941
10942
10943
10944
10945
10946
10947
10948
10949
10950
10951
10952
10953
10954
10955
10956
10957
10958
10959
10960
10961
10962
10963
10964
10965
10966
10967
10968
10969
10970
10971
10972
10973
10974
10975
10976
10977
10978
10979
10980
10981
10982
10983
10984
10985
10986
10987
10988
10989
10990
10991
10992
10993
10994
10995
10996
10997
10998
10999
11000
11001
11002
11003
11004
11005
11006
11007
11008
11009
11010
11011
11012
11013
11014
11015
11016
11017
11018
11019
11020
11021
11022
11023
11024
11025
11026
11027
11028
11029
11030
11031
11032
11033
11034
11035
11036
11037
11038
11039
11040
11041
11042
11043
11044
11045
11046
11047
11048
11049
11050
11051
11052
11053
11054
11055
11056
11057
11058
11059
11060
11061
11062
11063
11064
11065
11066
11067
11068
11069
11070
11071
11072
11073
11074
11075
11076
11077
11078
11079
11080
11081
11082
11083
11084
11085
11086
11087
11088
11089
11090
11091
11092
11093
11094
11095
11096
11097
11098
11099
11100
11101
11102
11103
11104
11105
11106
11107
11108
11109
11110
11111
11112
11113
11114
11115
11116
11117
11118
11119
11120
11121
11122
11123
11124
11125
11126
11127
11128
11129
11130
11131
11132
11133
11134
11135
11136
11137
11138
11139
11140
11141
11142
11143
11144
11145
11146
11147
11148
11149
11150
11151
11152
11153
11154
11155
11156
11157
11158
11159
11160
11161
11162
11163
11164
11165
11166
11167
11168
11169
11170
11171
11172
11173
11174
11175
11176
11177
11178
11179
11180
11181
11182
11183
11184
11185
11186
11187
11188
11189
11190
11191
11192
11193
11194
11195
11196
11197
11198
11199
11200
11201
11202
11203
11204
11205
11206
11207
11208
11209
11210
11211
11212
11213
11214
11215
11216
11217
11218
11219
11220
11221
11222
11223
11224
11225
11226
11227
11228
11229
11230
11231
11232
11233
11234
11235
11236
11237
11238
11239
11240
11241
11242
11243
11244
11245
11246
11247
11248
11249
11250
11251
11252
11253
11254
11255
11256
11257
11258
11259
11260
11261
11262
11263
11264
11265
11266
11267
11268
11269
11270
11271
11272
11273
11274
11275
11276
11277
11278
11279
11280
11281
11282
11283
11284
11285
11286
11287
11288
11289
11290
11291
11292
11293
11294
11295
11296
11297
11298
11299
11300
11301
11302
11303
11304
11305
11306
11307
11308
11309
11310
11311
11312
11313
11314
11315
11316
11317
11318
11319
11320
11321
11322
11323
11324
11325
11326
11327
11328
11329
11330
11331
11332
11333
11334
11335
11336
11337
11338
11339
11340
11341
11342
11343
11344
11345
11346
11347
11348
11349
11350
11351
11352
11353
11354
11355
11356
11357
11358
11359
11360
11361
11362
11363
11364
11365
11366
11367
11368
11369
11370
11371
11372
11373
11374
11375
11376
11377
11378
11379
11380
11381
11382
11383
11384
11385
11386
11387
11388
11389
11390
11391
11392
11393
11394
11395
11396
11397
11398
11399
11400
11401
11402
11403
11404
11405
11406
11407
11408
11409
11410
11411
11412
11413
11414
11415
11416
11417
11418
11419
11420
11421
11422
11423
11424
11425
11426
11427
11428
11429
11430
11431
11432
11433
11434
11435
11436
11437
11438
11439
11440
11441
11442
11443
11444
11445
11446
11447
11448
11449
11450
11451
11452
11453
11454
11455
11456
11457
11458
11459
11460
11461
11462
11463
11464
11465
11466
11467
11468
11469
11470
11471
11472
11473
11474
11475
11476
11477
11478
11479
11480
11481
11482
11483
11484
11485
11486
11487
11488
11489
11490
11491
11492
11493
11494
11495
11496
11497
11498
11499
11500
11501
11502
11503
11504
11505
11506
11507
11508
11509
11510
11511
11512
11513
11514
11515
11516
11517
11518
11519
11520
11521
11522
11523
11524
11525
11526
11527
11528
11529
11530
11531
11532
11533
11534
11535
11536
11537
11538
11539
11540
11541
11542
11543
11544
11545
11546
11547
11548
11549
11550
11551
11552
11553
11554
11555
11556
11557
11558
11559
11560
11561
11562
11563
11564
11565
11566
11567
11568
11569
11570
11571
11572
11573
11574
11575
11576
11577
11578
11579
11580
11581
11582
11583
11584
11585
11586
11587
11588
11589
11590
11591
11592
11593
11594
11595
11596
11597
11598
11599
11600
11601
11602
11603
11604
11605
11606
11607
11608
11609
11610
11611
11612
11613
11614
11615
11616
11617
11618
11619
11620
11621
11622
11623
11624
11625
11626
11627
11628
11629
11630
11631
11632
11633
11634
11635
11636
11637
11638
11639
11640
11641
11642
11643
11644
11645
11646
11647
11648
11649
11650
11651
11652
11653
11654
11655
11656
11657
11658
11659
11660
11661
11662
11663
11664
11665
11666
11667
11668
11669
11670
11671
11672
11673
11674
11675
11676
11677
11678
11679
11680
11681
11682
11683
11684
11685
11686
11687
11688
11689
11690
11691
11692
11693
11694
11695
11696
11697
11698
11699
11700
11701
11702
11703
11704
11705
11706
11707
11708
11709
11710
11711
11712
11713
11714
11715
11716
11717
11718
11719
11720
11721
11722
11723
11724
11725
11726
11727
11728
11729
11730
11731
11732
11733
11734
11735
11736
11737
11738
11739
11740
11741
11742
11743
11744
11745
11746
11747
11748
11749
11750
11751
11752
11753
11754
11755
11756
11757
11758
11759
11760
11761
11762
11763
11764
11765
11766
11767
11768
11769
11770
11771
11772
11773
11774
11775
11776
11777
11778
11779
11780
11781
11782
11783
11784
11785
11786
11787
11788
11789
11790
11791
11792
11793
11794
11795
11796
11797
11798
11799
11800
11801
11802
11803
11804
11805
11806
11807
11808
11809
11810
11811
11812
11813
11814
11815
11816
11817
11818
11819
11820
11821
11822
11823
11824
11825
11826
11827
11828
11829
11830
11831
11832
11833
11834
11835
11836
11837
11838
11839
11840
11841
11842
11843
11844
11845
11846
11847
11848
11849
11850
11851
11852
11853
11854
11855
11856
11857
11858
11859
11860
11861
11862
11863
11864
11865
11866
11867
11868
11869
11870
11871
11872
11873
11874
11875
11876
11877
11878
11879
11880
11881
11882
11883
11884
11885
11886
11887
11888
11889
11890
11891
11892
11893
11894
11895
11896
11897
11898
11899
11900
11901
11902
11903
11904
11905
11906
11907
11908
11909
11910
11911
11912
11913
11914
11915
11916
11917
11918
11919
11920
11921
11922
11923
11924
11925
11926
11927
11928
11929
11930
11931
11932
11933
11934
11935
11936
11937
11938
11939
11940
11941
11942
11943
11944
11945
11946
11947
11948
11949
11950
11951
11952
11953
11954
11955
11956
11957
11958
11959
11960
11961
11962
11963
11964
11965
11966
11967
11968
11969
11970
11971
11972
11973
11974
11975
11976
11977
11978
11979
11980
11981
11982
11983
11984
11985
11986
11987
11988
11989
11990
11991
11992
11993
11994
11995
11996
11997
11998
11999
12000
12001
12002
12003
12004
12005
12006
12007
12008
12009
12010
12011
12012
12013
12014
12015
12016
12017
12018
12019
12020
12021
12022
12023
12024
12025
12026
12027
12028
12029
12030
12031
12032
12033
12034
12035
12036
12037
12038
12039
12040
12041
12042
12043
12044
12045
12046
12047
12048
12049
12050
12051
12052
12053
12054
12055
12056
12057
12058
12059
12060
12061
12062
12063
12064
12065
12066
12067
12068
12069
12070
12071
12072
12073
12074
12075
12076
12077
12078
12079
12080
12081
12082
12083
12084
12085
12086
12087
12088
12089
12090
12091
12092
12093
12094
12095
12096
12097
12098
12099
12100
12101
12102
12103
12104
12105
12106
12107
12108
12109
12110
12111
12112
12113
12114
12115
12116
12117
12118
12119
12120
12121
12122
12123
12124
12125
12126
12127
12128
12129
12130
12131
12132
12133
12134
12135
12136
12137
12138
12139
12140
12141
12142
12143
12144
12145
12146
12147
12148
12149
12150
12151
12152
12153
12154
12155
12156
12157
12158
12159
12160
12161
12162
12163
12164
12165
12166
12167
12168
12169
12170
12171
12172
12173
12174
12175
12176
12177
12178
12179
12180
12181
12182
12183
12184
12185
12186
12187
12188
12189
12190
12191
12192
12193
12194
12195
12196
12197
12198
12199
12200
12201
12202
12203
12204
12205
12206
12207
12208
12209
12210
12211
12212
12213
12214
12215
12216
12217
12218
12219
12220
12221
12222
12223
12224
12225
12226
12227
12228
12229
12230
12231
12232
12233
12234
12235
12236
12237
12238
12239
12240
12241
12242
12243
12244
12245
12246
12247
12248
12249
12250
12251
12252
12253
12254
12255
12256
12257
12258
12259
12260
12261
12262
12263
12264
12265
12266
12267
12268
12269
12270
12271
12272
12273
12274
12275
12276
12277
12278
12279
12280
12281
12282
12283
12284
12285
12286
12287
12288
12289
12290
12291
12292
12293
12294
12295
12296
12297
12298
12299
12300
12301
12302
12303
12304
12305
12306
12307
12308
12309
12310
12311
12312
12313
12314
12315
12316
12317
12318
12319
12320
12321
12322
12323
12324
12325
12326
12327
12328
12329
12330
12331
12332
12333
12334
12335
12336
12337
12338
12339
12340
12341
12342
12343
12344
12345
12346
12347
12348
12349
12350
12351
12352
12353
12354
12355
12356
12357
12358
12359
12360
12361
12362
12363
12364
12365
12366
12367
12368
12369
12370
12371
12372
12373
12374
12375
12376
12377
12378
12379
12380
12381
12382
12383
12384
12385
12386
12387
12388
12389
12390
12391
12392
12393
12394
12395
12396
12397
12398
12399
12400
12401
12402
12403
12404
12405
12406
12407
12408
12409
12410
12411
12412
12413
12414
12415
12416
12417
12418
12419
12420
12421
12422
12423
12424
12425
12426
12427
12428
12429
12430
12431
12432
12433
12434
12435
12436
12437
12438
12439
12440
12441
12442
12443
12444
12445
12446
12447
12448
12449
12450
12451
12452
12453
12454
12455
12456
12457
12458
12459
12460
12461
12462
12463
12464
12465
12466
12467
12468
12469
12470
12471
12472
12473
12474
12475
12476
12477
12478
12479
12480
12481
12482
12483
12484
12485
12486
12487
12488
12489
12490
12491
12492
12493
12494
12495
12496
12497
12498
12499
12500
12501
12502
12503
12504
12505
12506
12507
12508
12509
12510
12511
12512
12513
12514
12515
12516
12517
12518
12519
12520
12521
12522
12523
|
<HTML><HEAD><TITLE>Alpine Technical Notes: Configuration and Preferences</TITLE></HEAD><BODY>
<H1>Configuration and Preferences</H1>
<H2><A NAME="pine-conf">Alpine Configuration</A></H2>
There is very little in <EM>Alpine</EM> which <STRONG>requires</STRONG> compile-time
configuration. In most cases, the compiled-in preferences will suit users
and administrators just fine. When running <EM>Alpine</EM> on a UNIX system, the
default built-in configuration can be changed by setting variables in the
system configuration files, <CODE>/usr/local/lib/pine.conf</CODE>
or <CODE>/usr/local/lib/pine.conf.fixed</CODE>.
(Actually, these files can be changed using the configure arguments
--with-system-pinerc=VALUE or --with-system-fixed-pinerc=VALUE.)
The location of the pine.conf file can be changed with the -P command line
argument.
Both <EM>Alpine</EM>
and <EM>PC-Alpine</EM> also use personal (user-based) configuration files.
On UNIX machines, the personal configuration file is the
file <CODE>~/.pinerc</CODE>.
For <EM>PC-Alpine</EM> systems, the personal configuration file is in
<CODE>$PINERC</CODE> or <CODE><PineRC registry value></CODE> or
<CODE>${HOME}\ALPINE\PINERC</CODE> or
<CODE><ALPINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
Or the personal configuration file can be specified with the -p command
line argument.
<P>
All of these configuration files, other than the fixed system
config <CODE>pine.conf.fixed</CODE> on UNIX systems, may optionally
be remote configuration files instead of local files.
This is discussed further in the following section and in
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>.
<P>
After the personal configuration, <EM>Alpine</EM> may optionally use
a personal exceptions configuration file which is specified with the
command line option "-x exceptions_config".
"Exceptions_config" may also be either a local file or a remote
configuration folder.
For Unix <EM>Alpine</EM>, if you don't have a "-x" command line option,
<EM>Alpine</EM> will look for the file "<CODE>.pinercex</CODE>"
in the same local directory that the regular config file is located in.
If the regular config file is remote then Unix <EM>Alpine</EM> looks in the home
directory for "<CODE>.pinercex</CODE>".
<P>
For <EM>PC-Alpine</EM>, if you don't have a "-x" command line option,
<EM>PC-Alpine</EM> will use the value of the
environment variable <CODE>$PINERCEX</CODE>.
If that is not set, <EM>PC-Alpine</EM> will look for
the local file "<CODE>PINERCEX</CODE>"
in the same local directory that the regular config file is located in.
If the regular config file is remote then <EM>PC-Alpine</EM> looks in the
local directory specified by the "-aux local_directory" command
line argument, or the directory <CODE>${HOME}\ALPINE</CODE>, or
in <CODE><ALPINE.EXE </CODE>directory<CODE>></CODE>.
<P>
The syntax of a non-list configuration variable is this:
<BLOCKQUOTE>
<variable> = <value><BR>
</BLOCKQUOTE>
If the value is absent then the variable is unset. To set a variable to
the empty value two double quotes (""). This is equivalent to an absent value
except that it overrides any system-wide default value that may be set. Quotes
may be used around any value. All values are strings and end at the end
of the line or the closing quote. Leading and trailing space is ignored
unless it is included in the quotes. There is one variable,
<EM>use-only-domain-name</EM>, for which the only
appropriate values are <EM>yes</EM> and <EM>no</EM>. That's because it is
a variable from the early days of <EM>Alpine</EM> before features existed.
<P>
There is also a
second type of variable, lists. A list is a comma-separated list of
values. The syntax for a list is:
<BLOCKQUOTE>
<variable> = <value> [, <value> , ... ]<BR>
</BLOCKQUOTE>
A list can be continued on subsequent lines by beginning the line with
white-space. Both the per-user and global configuration files may contain
comments which are lines beginning with a <CODE>#</CODE>. <P>
For UNIX <EM>Alpine</EM>, there are five ways in which each variable can be set.
In decreasing order of precedence they are:
<OL>
<LI> the system-wide <EM>fixed</EM> configuration file
<LI> a command line argument
<LI> the personal exceptions file
<LI> the personal configuration file
<LI> the system-wide configuration file.
</OL><P>
If the variable is not set in any of those places, there is a default
setting in the source code.
<P>
So, system-wide fixed settings always take precedence over command line
flags, which take precedence over per-user exception settings, which take precedence over per-user settings, which take precedence
over system-wide configuration settings.
<EM>PC-Alpine</EM> has the same list, except that it
does not use a system-wide <EM>fixed</EM> configuration file.
This can be modified slightly by using inheritance, which is covered below.
<P>
You may get a sample/fresh copy of the system configuration file by
running <EM>alpine -conf</EM>. The result will be printed on the standard
output with very short comments describing each variable. (The online help in
the Setup screens provides much longer comments.) If you need to fix some
of the configuration variables, you would use the same template for the
fixed configuration file as for the regular system-wide configuration
file. (If it isn't clear, the purpose of the fixed configuration file is
to allow system administrators to restrict the configurability of <EM>Alpine</EM>.
It is by no means a bullet-proof method.) <EM>Alpine</EM> will automatically create
the personal configuration file the first time it is run, so there is no
need to generate a sample. <EM>Alpine</EM> reads and writes the personal
configuration file occasionally during normal operation. Users will not
normally look at their personal configuration file, but will use the
Setup screens from within <EM>Alpine</EM> to set the values in this file. If a
user does add additional comments to the personal configuration file they
will be retained.
<P>
References to environment variables may be included in the <EM>Alpine</EM>
configuration files. The format is <CODE>$variable</CODE> or
<CODE>${variable}.</CODE> The character <CODE>~</CODE> will be expanded to the
<CODE>$HOME</CODE> environment variable.
For a more complete explanation of how environment variables work, see
the section
<A HREF="config-notes.html#env-variables">Using Environment Variables</A>.<P>
When environment variables are used for <EM>Alpine</EM> settings which take lists,
you must have an environment variable set for each member of the list.
That is, <EM>Alpine</EM> won't properly recognize an environment variable which is
set equal to a comma-delimited list. It is OK to reference unset
environment variables in the <EM>Alpine</EM> configuration file, which
will expand to nothing. <P>
<H3>Remote and Local Configuration</H3>
There are two types of storage for configuration information.
<EM>Local</EM> configuration files are used by default.
These are just regular files on the UNIX system or on the PC.
<EM>Remote</EM> configuration folders are stored on an IMAP server.
The advantage of using a remote configuration is that the same information
may be accessed from multiple platforms.
For example, if you use one computer at work and another at home, the same
configuration could be used from both places.
A configuration change from one place would be seen in both places.
Technical information about remote configuration is in
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>.
<H3>Generic and Exceptional Configuration</H3>
If you use <EM>Alpine</EM> from more than one platform it may be convenient
to split your configuration information into two pieces, a generic piece
and exceptions which apply to a particular platform.
For example, suppose you use <EM>Alpine</EM> from home and from work.
Most of your configuration settings are probably the
same in both locations, so those settings belong in the generic settings
configuration.
However, you may use a different SMTP server and INBOX
from home than you do from work.
The "smtp-server" and "inbox-path" variables could be
part of your exceptional configuration so that they could be different in the
two places.
<P>
You can use the command line option "-x config"
to split your configuration into generic and exceptional pieces.
Config may be either local or remote.
<P>
For most people, splitting the configuration information into two pieces is
only going to be useful if the generic information is accessed remotely.
If you already have a local pinerc file with settings you like you may find
that the command Setup/RemoteConfigSetup will be useful in helping you
convert to a remote configuration.
The command line flag
<A HREF="cmd-line.html#copy_pinerc">copy_pinerc</A>
may also be useful.
<H3>Configuration Inheritance</H3>
Configuration inheritance is a power user feature.
It is confusing and not completely supported by the configuration
user interface.
<P>
For configuration variables which are lists, like "smtp-server" or
"incoming-folders",
the inheritance mechanism makes it possible to <EM>combine</EM>
the values of options from different configuration locations instead
of <EM>replacing</EM> the value.
<A HREF="config-notes.html#config-inheritance">Configuration Inheritance</A>
has more information about how inheritance is used.
<P>
<HR>
<H2><A NAME="gen-conf">General Configuration Variables</A></H2>
The following is a list of all <EM>Alpine</EM> configuration variables, in
alphabetical order. Note that not all variables apply to all versions of
<EM>Alpine</EM> and that some variables are only applicable in a system configuration
file and some are only applicable in a personal configuration file.
These are configuration <EM>variables</EM>.
<A HREF="#features-conf">Configuration <EM>Features</EM></A>
are in a separate section.
<P>
<DL COMPACT>
<DT> <A NAME="addrbook-sort-rule"><EM>addrbook-sort-rule</EM></A>
<DD> This variable sets up the default address book sorting. Currently,
<EM>Alpine</EM> will accept the values <EM>dont-sort</EM>,
<EM>fullname-with-lists-last</EM>, <EM>fullname</EM>,
<EM>nickname-with-lists-last</EM>, and <EM>nickname</EM>. The default is
to sort by fullname with lists last.
If you use an address book from more than one computer and those
computers sort the address book differently then the sort order
will be the order where the last change to the address book was
made.
There are two reasons the sorting might be different on different
systems.
First, the addrbook-sort-rule may be set differently in the two
places.
Second, the collation rules on the two computers may be different.
For example, one system might ignore special characters while the other
doesn't or one may sort upper and lower case letters together while
the other doesn't.
In any case, the order you see is the order on the system where the
last change was made, for example by an address book edit or a
Take Address command.
<P>
This option is displayed as "Addressbook Sort Rule".
<P>
<DT> <A NAME="pers-abook"><EM>address-book</EM></A>
<DD> A list of personal address books.
Each entry in the list is an
optional nickname followed by a pathname or file name relative to the home
directory.
The nickname is separated from the rest of the line with whitespace.
Instead of a local pathname or file name, a remote folder name can be given.
This causes the address book to
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>.
Remote folder syntax is discussed in
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>.
This list of address books will be combined with the
<A HREF="#glob-abook"><EM>global-address-book</EM></A>
list to arrive at the complete set of address books. <P>
<DT> <A NAME="abook-formats"><EM>addressbook-formats</EM></A>
<DD> This option specifies the format that address books are displayed in.
By default, address books are displayed with the nicknames in the first
column, the fullnames in the second column, and addresses in the third
column. The system figures out reasonable defaults for the widths of the
columns. An address book may be given a different format by listing
special tokens in the order you want them to display. The possible tokens
are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT. More details are included
in the online help for this variable. <P>
<DT> <A NAME="alt-addresses"><EM>alt-addresses</EM></A>
<DD> This option provides a place for you to list alternate email addresses
you may have.
Each address in the list should be the actual email address part of an
address, without the full name field or the angle brackets.
For example:
<P>
<CENTER><SAMP>user@example.com</SAMP></CENTER>
<P>
The matching is case-insensitive, so this would match any of
<SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
<SAMP>USER@EXAMPLE.COM</SAMP> as well.
<P>
If set, the option affects the behavior of the Reply
command and the "+" symbol in the MESSAGE INDEX, which denotes that
a message has been addressed specifically to you.
<P>
In the default INDEX display
the personal name (or email address) of
the person listed in the message's "From:" header
field is usually displayed except when that address is yours or one of your
alternate addresses.
In that case you will usually see the name of
the first person specified in the
message's "To:" header field
with the prefix "To: " prepended.
<P>
With respect to Reply, the reply-to-all option will exclude addresses
listed here.
<P>
The feature
<A HREF="#copy-to-to-from">copy-to-address-to-from-if-it-is-us</A>
is somewhat related to this option.
<P>
In addition to a list of actual addresses,
you may use regular expressions (as used with egrep with the ignore case flag)
to describe the addresses you want to match.
<EM>Alpine</EM> will somewhat arbitrarily interpret your entry as a regular
expression if it contains any of the characters
*, |, +, ?, {, [, ^, $, or \.
Otherwise, it will be treated literally.
The feature
<A HREF="#disable-regex">disable-regular-expression-matching-for-alternate-addresses</A>
may be used to turn off regular expression processing regardless of whether or not
special characters appear in the entry.
<P>
A description of how regular expressions work is beyond the
scope of this help text, but some examples follow.
<P>
The entry
<P>
<CENTER><SAMP>.*@example.com</SAMP></CENTER>
<P>
in the alt-addresses list would mean that any
address with a domain name of <SAMP>example.com</SAMP> (such as
<SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
one of your alternate addresses.
Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
Complicating things further, the dollar sign
is special in the <EM>Alpine</EM> configuration (it signifies environment variable expansion)
so the dollar sign should be doubled or backslash escaped for <EM>Alpine</EM>'s sake.
Quotes around the whole expression will not escape the dollar sign successfully.
So this example should look like
<P>
<CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
<P>
<P>
The entry
<P>
<CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
<P>
would match
<SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
as <SAMP>fred@example.com</SAMP>.
<P>
You could match all addresses that look like
<SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
entry
<P>
<CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
<P>
Notice that you have to escape the plus sign with a backslash because plus
is a special character in regular expressions.
If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
the expression
<P>
<CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
<P>
would do it, but it would be easier to just add fred@example.com as a
separate entry.
<P>
One more example, a match of all first-level subdomains, is given by
<P>
<CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
<P>
<P>
Because the regular expression matching is based on an old library
(<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
but they should be close.
<P>
This option is displayed as "Alternate Addresses".
<DT> <A NAME="bugs-add"><EM>bugs-additional-data</EM></A>
<DD> System-wide configuration files only. Program/Script used by
<EM>Report Bug</EM> command. Output from the program/script is
captured and attached to the bug report. <P>
<DT> <A NAME="bugs"><EM>bugs-fullname</EM></A>,
<EM>bugs-address</EM>, <EM>local-fullname</EM>, <EM>local-address</EM>,
<EM>suggest-fullname</EM>, and <EM>suggest-address</EM>
<DD> System-wide configuration files only. These are used by the bug
report commands which can be accessed from some of the Help screens.
<P>
<DT> <A NAME="busy-cue-rate"><EM>busy-cue-rate</EM></A>
<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that
something is happening with a small animated display in the status
message line near the bottom of the screen.
This option sets how frequently the characters (for example, a spinning bar)
in the active status message lines are updated.
At most, it can be set to be updated 20 times per second.
<P>
Setting this value to zero will prevent display of the animations
altogether.
<P>
The option
<A HREF="#busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A>
can be used to remove the randomness from this animated display.
<P>
<DT> <A NAME="char-set"><EM>character-set</EM></A>
<DD> This is now obsolete, replaced by three separate variables:
<EM>display-character-set</EM>,
<EM>keyboard-character-set</EM>, and
<EM>posting-character-set</EM>.
See the section on
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for more
details.<P>
<DT> <A NAME="color-style"><EM>color-style</EM></A>
<DD> UNIX <EM>Alpine</EM> only (color is automatically on with <EM>PC-Alpine</EM>).
If the terminal or terminal emulator you are using is capable of displaying
colors, this variable controls whether or not
color will be used in <EM>Alpine</EM>.
If you turn color on and things are set up correctly,
you should see color appear on the screen immediately.
Modern terminal emulators are usually capable of displaying colors.
<P>
This variable may be set to any of the following values:
<P>
<DL>
<DT>no-color</DT>
<DD>Don't use color.
</DD>
<DT>use-termdef</DT>
<DD>In order to decide if your terminal is capable of color,
<EM>Alpine</EM> looks in
the terminal capabilities database, TERMINFO or TERMCAP, depending on
how <EM>Alpine</EM> was compiled.
This is a good option to choose if you switch between a color and a non-color
terminal with the same <EM>Alpine</EM> configuration.
<EM>Alpine</EM> will know to use color on the color terminal because
it is described
in the termcap entry, and <EM>Alpine</EM> will know to use black and white on the
non-color terminal.
<A HREF="config-notes.html#color-config-notes">Color Details</A>
has more information about configuring a termcap entry for color.
This is usually something a system administrator does.
</DD>
<DT>force-ansi-8color</DT>
<DD>Because setting up a termcap entry is confusing and because the
terminal capabilities database is often not correctly configured for color,
this choice and the next may be easier for you to use.
If your terminal emulator responds to ANSI color escape sequences, which
many do, this option will
cause <EM>Alpine</EM> to believe your terminal will respond
to the escape sequences which produce eight different foreground and background
colors.
The escape sequences used to set the foreground colors are
<P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
where the color_number is an ASCII digit between 0 and 7.
The numbers 0 through 7 should correspond to the colors black, red, green,
yellow, blue, magenta, cyan, and white.
Some terminal emulators use a pre-ANSI scheme which swaps
the colors blue and red and the colors yellow and cyan.
This will cause the default colors to be different, but other than that
things should work fine.
There is also a 9th color available, the last one shown, which is the default
color from the terminal emulator.
When used as a background color some people refer to this color as
"transparent", which is why the letters "TRAN" are
shown in the color swatch of the SETUP COLOR screen.
The foreground transparent color is shown as
the color of the "TRAN" text.
(The transparent color will not work correctly in a PC-Alpine configuration.)
The escape sequences used to set the background colors are the same
as for the foreground colors except a "4" replaces the "3".
<P>
Note: With the Tera Term terminal emulator this setting works well.
You should also have the Tera Term "Full color" option turned OFF.
You may find the "Full color" option in Tera Term's "Setup"
menu, in the "Window" submenu.
</DD>
<DT>force-ansi-16color</DT>
<DD>Many terminal emulators know about the same eight colors above
plus eight more.
This option attempts to use all 16 colors.
The same escape sequences as for the eight-color terminal are used
for the first eight colors.
The escape sequences used to set foreground colors 8-15 are the same as
for 0-7 except the "3" is replaced with a "9".
The background color sequences for colors 8-15 are the same as for 0-7
except the "4" is replaced with "10".
You can tell if the 16 colors are working by turning on this option
and then going into one of the color configuration screens, for example,
the configuration screen for Normal Color.
If you see 16 different colors to select from (plus a 17th for
the transparent color), it's working.
</DD>
<DT>force-xterm-256color</DT>
<DD>Some versions of xterm (and some other terminal emulators)
have support for 256 colors.
The escape sequences used to set the foreground colors are
<P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
where the color_number is an ASCII digit between 0 and 255.
Background colors are the same with the 38 replaced with a 48.
The numbers 0 through 15 are probably similar to the 16 color version
above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
The terminal default (transparent) color is the 257th color at the bottom.
Some terminal emulators will misinterpret these escape sequences causing
the terminal to blink or overstrike characters or to do something else
undesirable.
<P>
The PuTTY terminal emulator has an option called "Allow terminal to
use xterm 256-colour mode" which allows PuTTY to work well with
this 256-color setting.
</DD>
</DL>
<P>
There are two other possible color values which may be useful in some
situations.
In the color configuration screens there will sometimes be a color which has
the label "NORM" inside its color swatch.
If this is selected the corresponding foreground or background
<A HREF="#normal-color"><EM>Normal Color</EM></A>
will be used.
Another similar color is the one that has the
label "NONE" inside its color swatch.
The meaning of this setting is that no color changing will be done.
This NONE color is only useful in contexts where <EM>Alpine</EM> is already
coloring the text some color other than the Normal Color.
For example, if the
<A HREF="#reverse-color"><EM>Reverse Color</EM></A> is set then the current
line in the MESSAGE INDEX will be colored.
If one of the index symbols (for example, the Index-to-me Symbol) has the NONE
color as its background then the symbol's foreground color will be used
to draw the actual text but the background color will be the same as whatever
the background color already was.
The color values which end up in the configuration file for these special
values are the 11-character words "norm-padded", "none-padded",
and "transparent".
<P>
The normal default is "no-color".
<P>
Once you've turned on color you may set the
colors of many objects on the screen individually.
The <A HREF="#color-config">Color Configuration</A> section has more
information, or you may just try it by
running the "Setup" command and typing "K"
for Kolor to enter the color configuration screen (Kolor instead of Color
because C means Config).
Most categories of color which <EM>Alpine</EM> supports are configurable there.
<A HREF="#index-color-config">Index line color</A> is configured separately.
<P>
<DT> <A NAME="composer-word-separators"><EM>composer-word-separators</EM></A>
<DD> This option affects how a "word" is defined in the composer.
The definition of a word is used when using the Forward Word and Backward
Word commands in the composer, as well as when using the spell checker.
Whitespace is always considered a word separator.
Punctuation (like question marks, periods, commas, and so on) is always
a word separator if it comes at the end of a word.
By default, a punctuation character which is in the middle of a word does
not break up that word as long as the character before and the character
after it are both alphanumeric.
If you add a character to this option it will be considered a
word separator even when it occurs in the middle of an alphanumeric word.
For example, if you want to skip through each part of an address instead
of skipping the whole address at once you might want to include"@"
and "." in this list.
If you want the word-skipper to stop on each part of a UNIX filename you
could add "/" to the list.
The equal sign and dash are other possibilities you might find helpful.
<P>
<DT> <A NAME="composer-wrap-column"><EM>composer-wrap-column</EM></A>
<DD> This option specifies an aspect of <EM>Alpine</EM>'s Composer. This gives the
maximum width that auto-wrapped lines will have. It's also the maximum
width of lines justified using the ^J Justify command. The normal default
is <EM>74</EM>. The largest allowed setting is normally <EM>80</EM> in order to
prevent very long lines from being sent in outgoing mail. When the mail
is actually sent, trailing spaces will be stripped off of each line.
<P>
<DT> <A NAME="current-indexline-style"><EM>current-indexline-style</EM></A>
<DD> <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A>.
<P>
<DT> <A NAME="cust-hdr"><EM>customized-hdrs</EM></A>
<DD> You may add your own custom headers to outgoing messages.
Each header you specify here must include the header tag
(Reply-To:, Approved:, etc.)
and may optionally include a value for that header.
If you want to see these custom headers each time you compose a message,
you must add them to your
<A HREF="#def-comp"><EM>default-composer-hdrs</EM></A> list,
otherwise they become part
of the rich header set which you only see when you press the rich header
command.
(If you are looking for a way to change which headers are <EM>displayed</EM>
when you view a message, take a look at the
<A HREF="#viewer-hdrs"><EM>viewer-hdrs</EM></A>
option instead.)
Here's an example which shows how you might set your From address
<P>
<CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
<P>
and another showing how you might set a Reply-To address
<P>
<CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
<P>
You may also set non-standard header values here.
For example, you could add
<P>
<CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
<P>
or even
<P>
<CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
<P>
If you include a value after the colon then that header will be included
in your outgoing messages unless you delete it before sending.
If a header in the Customized-Headers list has only a tag but no value, then
it will not be included in outgoing messages unless you edit a value
in manually.
For example, if
<P>
<CENTER><SAMP>Reply-To:</SAMP></CENTER>
<P>
is in the list, then the Reply-To header will be available for editing
but won't be included unless a value is added while in the composer.
<P>
It's actually a little more complicated than that.
The values of headers that you set with the Customized-Headers option are
defaults.
If the message you are about to compose already has a value for a header,
that value is used instead of a value from your Customized-Headers.
For example, if you are Replying to a message the Subject field
will already be filled in.
In that case, if the Customized-Headers list contains a Subject line, the
custom subject will <EM>NOT</EM> be used.
The subject derived from the subject of the message you are Replying
to will be used instead.
<P>
It is also possible to make header setting even more complicated and more
automatic by using
<A HREF="#role-config"><EM>Roles</EM></A>,
but if all you want to do is set a default value for a header, you don't
need to think about Roles.
<P>
If you change your From address you may also find it useful to add the
changed From address to the
<A HREF="#alt-addresses"><EM>alt-addresses</EM></A>
configuration option.
<P>
Limitation: Because commas are used to separate the list of
Customized-Headers, it is not possible to have the value of a
header contain a comma.
Nor is there currently an "escape" mechanism provided
to make this work.
<P>
This option is displayed as "Customized Headers".
<P>
<DT> <A NAME="dead-letter-files"><EM>dead-letter-files</EM></A>
<DD> This option affects <EM>Alpine</EM>'s behavior when you cancel a message being
composed. <EM>Alpine</EM>'s usual behavior is to write the canceled message to
a file named
"dead.letter" in your home directory, or
"DEADLETR" when using <EM>PC-Alpine</EM>,
overwriting any previous message.
<P>
If you set this option to a value higher than one, then that many copies
of dead letter files will be saved.
For example, if you set this option to "3" then you may have
files named
"DEADLETR",
"DEADLETR2", and
"DEADLETR3"; or
"dead.letter",
"dead.letter2", and
"dead.letter3".
In this example, the most recently cancelled message will be in
"dead.letter",
and the third most recently cancelled message will be in
"dead.letter3".
The fourth most recently cancelled message will no longer be saved.
<P>
If you set this option to zero, then NO record of canceled messages is
maintained.
<P>
If the feature
<A HREF="#quell-dead-letter-on-cancel">Quell-Dead-Letter-On-Cancel</A>
is set, that overrides whatever you set for this option.
If this option had existed at the time, then the Quell feature would not
have been added, but it is still there for backwards compatibility.
So, in order for this option to have the desired effect, make sure the
Quell feature is turned off.
<P>
<DT> <A NAME="def-comp"><EM>default-composer-hdrs</EM></A>
<DD> You can control which headers you want visible when composing outgoing
email using this option.
You can specify any of the regular set, any
Rich Header,
or any <A HREF="#cust-hdr"><EM>Customized-Hdrs</EM></A>
which you have already defined.
If you use this setting at all, you must specify all the
headers you want to see, you can't just add to the regular header set.
The default set is To:, Cc:, Attchmnt:, and Subject:.
<P>
Note that the "Newsgroups:" header will be abbreviated in the Composer
display, but should be spelled out in full here.
<P>
This option is displayed as "Default Composer Headers".
<P>
<DT> <A NAME="def-fcc"><EM>default-fcc</EM></A>
<DD> The name of the folder to which all outgoing mail goes is set here.
The compiled-in default is <EM>sent-mail</EM> (UNIX) or <EM>sentmail</EM>
(PC). It can be set to "" (two double quotes with nothing between them)
to turn off saving copies of outgoing mail. If <EM>default-fcc</EM> is a
relative file name, then it is relative to your default collection for
saves (see <A HREF="#fold-coll"><EM>folder-collections</EM></A>). <P>
This option is displayed as "Default Fcc (File carbon copy)".
<P>
<DT> <A NAME="def-save"><EM>default-saved-msg-folder</EM></A>
<DD> This option determines the default folder name for <EM>Saves</EM>...
If this is not a path name, it will be in the default collection for saves.
Any valid folder specification, local or IMAP, is allowed. This default
folder only applies when the
<A HREF="#saved-msg-name"><EM>saved-msg-name-rule</EM></A>
doesn't override it.
Unix <EM>Alpine</EM> default is normally
<EM>saved-messages</EM> in the default folder collection.
<EM>PC-Alpine</EM> default is <EM>SAVEMAIL</EM>
(normally stored as <EM>SAVEMAIL.MTX</EM>). <P>
This option is displayed as "Default Saved Message Folder".
<P>
<DT> <A NAME="disable-these-auths"><EM>disable-these-authenticators</EM></A>
<DD> This variable is a list of SASL (Simple Authentication and Security
Layer) authenticators which will be disabled.
SASL is a mechanism for
authenticating to IMAP, POP3, SMTP, and other network servers.
<P>
<EM>Alpine</EM> matches its list of supported authenticators with the server to
determine the most secure authenticator that is supported by both.
If no matching authenticators are found, <EM>Alpine</EM> will revert to plaintext
login (or, in the case of SMTP, will be unable to authenticate at all).
<P>
The candidates for disabling are listed below.
There may be more if you compile <EM>Alpine</EM> with additional authenticators
and/or a newer version of the c-client library.
<P>
<UL>
<LI> GSSAPI
<LI> CRAM-MD5
<LI> PLAIN
<LI> LOGIN
</UL>
<P>
Normally, you will not disable any authenticators.
There are two exceptions:
<P>
<OL>
<LI> You use a broken server that advertises an authenticator,
but does not actually implement it.
<LI> You have a Kerberos-capable version of <EM>Alpine</EM> and the server is
also Kerberos-capable, but you can not obtain Kerberos
credentials on the server machine, thus you desire to disable
GSSAPI (which in turn disables <EM>Alpine</EM>'s Kerberos support).
</OL>
<P>
It is never necessary to disable authenticators, since <EM>Alpine</EM> will try
other authenticators before giving up.
However, disabling the relevant authenticator avoids annoying error messages.
<P>
<DT> <A NAME="disable-these-drivers"><EM>disable-these-drivers</EM></A>
<DD> This variable is a list of mail drivers which will be disabled.
The candidates for disabling are listed below.
There may be more in the future if you compile <EM>Alpine</EM> with
a newer version of the c-client library.
<P>
<UL>
<LI> mbox
<LI> mbx
<LI> mh
<LI> mix
<LI> mmdf
<LI> mtx
<LI> mx
<LI> news
<LI> phile
<LI> tenex
<LI> unix
</UL>
<P>
The <EM>mbox</EM> driver enables the following behavior: if there is a
file called <CODE>mbox</CODE>
in your home directory, and if that file is either empty or in Unix mailbox
format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
will automatically transfer mail from the system mail spool directory into the
<CODE>mbox</CODE> file and
delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
this will not happen.
<P>
It is not recommended to disable the driver which supports the system default
mailbox format. On most non-SCO systems, that driver is the
<EM>unix</EM> driver.
On most SCO systems, it is the <EM>mmdf</EM> driver.
The system default driver may be
configured to something else on your system; check with your system manager
for additional information.
<P>
It is most likely not very useful for you to disable any of the drivers other
than possibly <EM>mbox</EM>.
You could disable some of the others if you know for
certain that you don't need them but the performance gain in doing so
is very modest.
<P>
<DT> <A NAME="disp-char-set"><EM>display-character-set</EM></A>
<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>
<DT> <A NAME="display-filters"><EM>display-filters</EM></A>
<DD> This option defines a list of text-filtering commands (programs or
scripts) that may be used to filter text portions of received messages
prior to their use (e.g., presentation in the "Message Text" display
screen). For security reasons, the full path name of the filter command
must be specified.
<P>
Display filters do not work with <EM>PC-Alpine</EM>.
<P>
The command is executed and the message is piped into its standard input.
The standard output of the command is read back by <EM>Alpine</EM>. The
<EM>_TMPFILE_</EM> token (see below) overrides this default behavior.
<P>
The filter's use is based on the configured <EM>trigger</EM> string. The
format of a filter definition is:
<P>
<CENTER><trigger> <command> <arguments></CENTER>
<P>
You can specify as many filters as you wish, separating them with a comma.
Each filter can have only one trigger and command. Thus, two trigger
strings which invoke the same command require separate filter
specifications.
<P>
The <EM>trigger</EM> is simply text that, if found in the message,
will invoke the associated command. If the trigger contains any space
characters, it must be placed within quotes. Likewise, should you
wish a filter to be invoked unconditionally, define the trigger as the
null string, "" (two consecutive double-quote characters). If the
trigger string is found anywhere in the text of the message the filter
is invoked. Placing the trigger text within the tokens defined below
changes where within the text the trigger must be before considering
it a match.
<P>
Trigger Modifying Tokens:
<DL>
<DT><EM>_CHARSET(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the text is in a character set matching <VAR>string</VAR>
(e.g., ISO-8859-2 or ISO-2022-JP).
<DT><EM>_LEADING(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the enclosed <VAR>string</VAR> is found to be the first
non-whitespace text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.
<DT><EM>_BEGINNING(<VAR>string</VAR>)_</EM>
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command
if the enclosed <VAR>string</VAR> is found at the beginning
of any line in the text.
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
the space character.
</DL>
<P>
The "command" and "arguments" portion is simply
the command line to be invoked if the trigger string is found. Below
are tokens that <EM>Alpine</EM> will recognize and replace with special values
when the command is actually invoked.
<P>
Command Modifying Tokens:
<DL>
<DT><EM>_TMPFILE_</EM>
<DD>When the command is executed, this token is
replaced with the path and name of the temporary
file containing the text to be filtered. <EM>Alpine</EM>
expects the filter to replace this data with the
filter's result.
NOTE: Use of this token implies that the text to
be filtered is not piped into standard input of the
executed command and its standard output is ignored.
<EM>Alpine</EM> restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.
<DT><EM>_RESULTFILE_</EM>
<DD>When the command is executed, this token is
replaced with the path and name of a temporary
file intended to contain a status message from the
filter. <EM>Alpine</EM> displays this in the message status
field.
<DT><EM>_DATAFILE_</EM>
<DD>When the command is executed, this token is
replaced with the path and name of a temporary
file that <EM>Alpine</EM> creates once per session and deletes
upon exit. The file is intended to be used by the
filter to store state information between instances
of the filter.
<DT><EM>_PREPENDKEY_</EM>
<DD>When the command is executed, this token indicates that a random
number will be passed down the input stream before the message text.
This number could be used as a session key.
It does not appear as a command-line argument.
It is sent in this way to improve security.
The number is unique to the current <EM>Alpine</EM> session
and is only generated once per session.
</DL>
<P>
The feature
<A HREF="#disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A> is related.
<P>
Performance caveat/considerations:
<BR>
Testing for the trigger and invoking the filter doesn't come for free.
There is overhead associated with searching for the trigger string, testing
for the filter's existence and actually piping the text through the filter.
The impact can be reduced if the Trigger Modifying Tokens above are
employed.
<P>
Limitation:
<BR>
If Header Colors are being used, the sequences of bytes which indicate
color changes will be contained in the text which is passed to the
display-filter.
If this causes problems you'll need to turn off Header Colors.
The thirteen bytes which indicate a color change are
the character \377 followed by
\010 for a foreground color or \011 for a background color.
Then comes eleven characters of RGB data which looks something like
255, 0,255, depending on the particular color, of course.
<P>
<DT> <A NAME="download-command"><EM>download-command</EM></A>
<DD> This option affects the behavior of the <EM>Export</EM> command.
It specifies a Unix program name, and any necessary command line arguments,
that <EM>Alpine</EM> can use to transfer the exported message to your
personal computer's disk.
<P>
<DT> <A NAME="download-command-prefix"><EM>download-command-prefix</EM></A>
<DD> This option is used in conjunction with the <EM>download-command</EM>
option.
It defines text to be written to the terminal emulator (via standard
output) immediately prior to starting the download command. This is
useful for integrated serial line file transfer agents that permit command
passing (e.g., Kermit's APC method). <P>
<DT> <A NAME="editor"><EM>editor</EM></A>
<DD> UNIX <EM>Alpine</EM> only. Sets the name of the alternate editor for composing
mail (message text only, not headers). It will be invoked with the "^_"
command or it will be invoked automatically if the
<A HREF="#enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A>
feature is set. <P>
<DT> <A NAME="empty-header-message"><EM>empty-header-message</EM></A>
<DD> When sending, if both the To and Cc fields are empty and you
are sending the message to a Bcc,
<EM>Alpine</EM> will put a special address in the To line. The default value is
"undisclosed-recipients: ;". The reason for this is to avoid
embarrassment caused by some Internet mail transfer software that
interprets a "missing" To: header as an error and replaces it with an
Apparently-to: header that may contain the addresses you entered on the
Bcc: line, defeating the purpose of the Bcc. You may change the part
of this message that comes before the ": ;" by setting the
<EM>empty-header-message</EM> variable to something else.
<P>
<DT> <A NAME="fcc-name-rule"><EM>fcc-name-rule</EM></A>
<DD> Determines default folder name for fcc when composing. Currently,
<EM>Alpine</EM> will accept the values <EM>default-fcc</EM>, <EM>by-recipient</EM>,
or <EM>last-fcc-used</EM>. If set to <EM>default-fcc</EM>, then <EM>Alpine</EM> will
use the value defined in the <A HREF="#def-fcc"><EM>default-fcc</EM></A>
variable (which itself
has a default) for the Fcc header field. If set to <EM>by-recipient</EM>,
then <EM>Alpine</EM> will use the name of the recipient as a folder name for the fcc.
The relevant recipient is the first address in the To field. If set to
"last-fcc-used", then <EM>Alpine</EM> will offer to Fcc to whatever folder
you used previously.
In all cases, the field can still be edited after it is
initially assigned. If the fcc field in the address book is set for the
first To address, that value over-rides any value derived from this rule.
<P>
<DT> <A NAME="feat-list"><EM>feature-list</EM></A>
<DD> This is a list of the many features (options) which may be turned on
or off. There is a separate section titled
<A HREF="#features-conf">Configuration Features</A> which explains
each of the features. There is some additional explanation about the
<EM>feature-list</EM> variable itself
in <A HREF="config-notes.html#feature-list"><EM>Feature List Variable</EM></A>.
<P>
<DT> <A NAME="file-directory"><EM>file-directory</EM></A>
<DD> <EM>PC-Alpine</EM> only.
This value affects the Composer's "^J Attach" command,
the Attachment Index Screen's "S Save" command, and the
Message Index's "E Export" command.
<P>
Normally, when a filename is supplied that lacks a leading "path"
component, <EM>Alpine</EM> assumes the file exists in the user's home directory.
Under Windows operating systems, this definition isn't always clear. This
feature allows you to explicitly set where <EM>Alpine</EM> should look for files
without a leading path.
<P>
NOTE: this feature's value is ignored if either
<A HREF="#use-current-dir"><EM>use-current-dir</EM></A> feature
is set or the PINERC has a value for the
<A HREF="#operating-dir"><EM>operating-dir</EM></A> variable.
<P>
<DT> <A NAME="fold-coll"><EM>folder-collections</EM></A>
<DD> This is a list of one or more collections where saved mail is stored.
See the sections describing
<A HREF="config-notes.html#collections">folder collections and collection syntax</A> for more information.
The first collection in this list is the default
collection for <EM>Save</EM>s,
including <A HREF="#def-fcc"><EM>default-fcc</EM>'s</A>.
<P>
<DT> <A NAME="folder-ext"><EM>folder-extension</EM></A>
<DD> <EM>PC-Alpine</EM> only. File extension used for local folder names. This
is <CODE>.MTX</CODE> by default.
<P>
<DT> <A NAME="reopen-rule"><EM>folder-reopen-rule</EM></A>
<DD> <EM>Alpine</EM> normally checks for new mail in the currently open folder
and in the INBOX every few <A HREF="#mail-check"><EM>minutes</EM></A>.
<P>
There are some situations where automatic new-mail checking does not work.
For example, if a mail folder is opened using the POP protocol or a newsgroup
is being read using the NNTP protocol, then new-mail checking is disabled.
<P>
It may be possible to check for new mail in these cases by reopening the
folder.
<EM>Alpine</EM> does not do this for you automatically, but you may do the commands
manually to cause this to happen.
You reopen by going back to the folder list screen from the message
index screen with the "<" command,
and then going back into the message index screen with
the ">" command.
(Actually, any method you would normally use to open a folder will work the
same as the "<" followed by ">" method.
For example, the GoTo Folder command will work, or you may use L to go to the
Folder List screen and Carriage Return to reopen the folder.)
<P>
There are some cases where <EM>Alpine</EM> knows that reopening the folder should
be useful as a way to discover new mail.
At the time of this writing, connections made using the POP protocol,
news reading using the NNTP protocol, local news reading, and local
ReadOnly folders which are in the traditional UNIX or the MMDF format all
fall into this category.
There are other cases where it <EM>may</EM> be a way to discover new mail, but <EM>Alpine</EM>
has no way of knowing, so it might also just be an exercise in futility.
All remote, ReadOnly folders other than those listed just above fall into this
category.
The setting of this option together with the type of folder
controls how <EM>Alpine</EM> will react to the apparent attempt to reopen a folder.
<P>
If you don't reopen, then you will just be back in
the message index with no change.
You left the index and came back, but the folder remained "open"
the whole time.
However, if you do reopen the folder, the folder is closed and then reopened.
In this case, the current state of the open folder is lost.
The New status, Important and Answered flags,
selected state, Zoom state, collapsed or expanded state of threads,
current message number,
and any other temporary state is all lost when the reopen happens.
For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
<P>
In the possibilities listed below, the text says "POP/NNTP" in
several places.
That really implies the case where <EM>Alpine</EM> knows it is a good way to discover
new mail, which is more than just POP and NNTP, but POP and NNTP are
the cases of most interest.
This option probably has more possible values than it deserves. They are:
<P>
<DL>
<DT>Always reopen</DT>
<DD><EM>Alpine</EM> will not ask whether you want to reopen but will just do the reopen
whenever you type a command that implies a reopen, regardless of the
access method.
In other words, it is assumed you would always answer Yes if asked
about reopening.
</DD>
<DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but
will ask you whether to reopen other remote folders,
with a default answer of Yes.
</DD>
<DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but
will ask you whether to reopen other remote folders,
with a default answer of No.
</DD>
<DT>Yes for POP/NNTP, No for other remote</DT>
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, and
will assume a No answer for all other remote folders.
</DD>
<DT>Always ask [Yes]</DT>
<DD><EM>Alpine</EM> will not differentiate based on access method.
It will always ask for all remote folders, with a default answer of Yes.
</DD>
<DT>Always ask [No]</DT>
<DD><EM>Alpine</EM> will not differentiate based on access method.
It will always ask for all remote folders, with a default answer of No.
</DD>
<DT>Ask about POP/NNTP [Yes], No for other remote</DT>
<DD><EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer
of Yes.
It will never attempt to reopen other remote folders.
</DD>
<DT>Ask about POP/NNTP [No], No for other remote</DT>
<DD>This is the default.
<EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer
of No.
It will never attempt to reopen other remote folders.
</DD>
<DT>Never reopen</DT>
<DD><EM>Alpine</EM> will never attempt to reopen already open folders.
</DD>
</DL>
<P>
Remember, wherever it says POP or NNTP above it really means POP or NNTP or
any of the other situations where it is likely that reopening is a good way
to discover new mail.
<P>
There is an alternative that may be of useful in some situations.
Instead of manually checking for new mail you can set up a
<A HREF="config-notes.html#maildrop">Mail Drop</A>
and automatically check for new mail.
<P>
<DT> <A NAME="folder-sort-rule"><EM>folder-sort-rule</EM></A>
<DD> This option controls the order in which folder list entries will be
presented in the FOLDER LIST screen. Choose one of the following:
<DL>
<DT> <EM>Alphabetical</EM>
<DD> sort by alphabetical name independent of type
<DT> <EM>Alpha-with-dirs-last</EM>
<DD> sort by alphabetical name grouping directory entries
to the end of the list
<DT> <EM>Alpha-with-dirs-first</EM>
<DD> sort by alphabetical name grouping directory entries
to the start of the list
</DL>
The normal default is <EM>Alphabetical</EM>.
<P>
<DT> <A NAME="font-name"><EM>font-name</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="font-size"><EM>font-size</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="font-style"><EM>font-style</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="forced-abook"><EM>forced-abook-entry</EM></A>
<DD> System-wide <EM>Alpine</EM> configuration files only.
Force these address book
entries into all writable personal address books.
This is a list variable. Each item in the list has the form:
<BLOCKQUOTE>
Nickname | Fullname | Address <BR>
</BLOCKQUOTE>
with optional whitespace in all the obvious places.
<P>
<DT> <A NAME="form-letter-folder"><EM>form-letter-folder</EM></A>
<DD> A Form Letter Folder is a mail folder that is intended to
contain messages that you have composed and that are intended to be
sent in their original form repeatedly.
<P>
Setting this variable will alter <EM>Alpine</EM>'s usual behavior when you
execute the Compose command. Normally, <EM>Alpine</EM> offers a chance to
continue a postponed or interrupted message should one or the other
exist. When this variable is set to a folder name that exists, <EM>Alpine</EM>
will also offer the chance to select a message from the folder to
insert into the composer, much like when continuing a postponed message.
The difference, however, is that <EM>Alpine</EM> will not automatically delete
the selected message from the Form Letter Folder.
<P>
Setting this variable will also affect <EM>Alpine</EM>'s behavior when you
Postpone a message from the composer. Normally, <EM>Alpine</EM> simply stashes
the message away in your
<A HREF="#postponed-folder"><EM>Postponed-Folder</EM></A>.
Regardless of the specified folder's existence, <EM>Alpine</EM> will ask which
folder you intend the message to be stored in. Choose the
"F" option to store the message in your Form Letter Folder.
This is the most common way to add a message to the folder.
<P>
Another method of adding messages to the folder is via the <EM>Alpine</EM>
composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
you expect to send in the same form again, you can enter the Form
Letter Folder's name in this field. <EM>Alpine</EM>, as usual, will copy the
message as it's sent. Note, when you later select this message from
your Form Letter Folder, it will have the same recipients as the original
message.
<P>
To delete a message from the Form Letter Folder, you can either select
the folder from a suitable FOLDER LIST screen, or use the Delete
command in the MESSAGE INDEX offered when selecting from the folder as
part of the Compose command. You can delete a Form Letter Folder just
as any other folder from a suitable FOLDER LIST screen.
<P>
You may find that the <A HREF="#role-config"><EM>Roles</EM></A>
facility can be used
to replace the Form Letter Folder.
<P>
<DT> <A NAME="glob-abook"><EM>global-address-book</EM></A>
<DD> A list of shared address books. Each entry in the list is an
optional nickname followed by a pathname or file name relative to the home
directory.
A SPACE character separates the nickname from the rest of the line.
Instead of a local pathname or file name, a remote folder name can be given.
This causes the address book to
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>.
Remote folder syntax is discussed in
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>.
This list will be added to the
<A HREF="#pers-abook"><EM>address-book</EM></A> list to
arrive at the complete set of address books. Global address books are
defined to be ReadOnly. <P>
<DT> <A NAME="goto-default-rule"><EM>goto-default-rule</EM></A>
<DD> This value affects <EM>Alpine</EM>'s behavior when using
the <EM>Goto</EM> command.
There are five possible values for this option:
<P>
<DL>
<DT> <EM>folder-in-first-collection</EM>
<DD> <EM>Alpine</EM> will offer the most recently visited folder in the default
collection found in the "Collection List" screen as the default.
<P>
<DT> <EM>inbox-or-folder-in-first-collection</EM>
<DD> If the current folder is <EM>INBOX</EM>,
<EM>Alpine</EM> will offer the most recently visited folder in the
default collection found in the "Collection List" screen.
If the current folder is other than <EM>INBOX</EM>,
<EM>INBOX</EM> is offered as the default.
<P>
<DT> <EM>inbox-or-folder-in-recent-collection</EM>
<DD> This is <EM>Alpine</EM>'s default behavior.
If the current folder is <EM>INBOX</EM>,
<EM>Alpine</EM> will offer the last open
folder as the default.
If the current folder is other than <EM>INBOX</EM>,
<EM>INBOX</EM> is offered as the default.
<P>
<DT> <EM>first-collection-with-inbox-default</EM>
<DD> Instead of offering the most recently visited folder in the default
collection, the default collection is offered but with <EM>INBOX</EM> as
the default folder.
If you type in a folder name it will be in the default collection.
If you simply accept the default, however, your <EM>INBOX</EM> will be opened.
<P>
<DT> <EM>most-recent-folder</EM>
<DD> The last accepted value simply causes the most recently opened
folder to be offered as the default regardless of the currently opened
folder.
<P>
</DL>
NOTE: The default while a newsgroup is open remains the same; the last
open newsgroup. <P>
<DT> <A NAME="header-general-background-color"><EM>header-general-background-color</EM></A>
<DT> <A NAME="header-general-foreground-color"><EM>header-general-foreground-color</EM></A>
<DD> <A HREF="#header-colors"><EM>Header Colors</EM></A>.
<P>
<DT> <A NAME="image-viewer"><EM>image-viewer</EM></A>
<DD> This variable names the program to call for displaying parts of a
MIME message that are of type IMAGE. If your system supports the
<EM>mailcap</EM> system, you don't need to set this variable. <P>
<DT> <A NAME="inbox-path"><EM>inbox-path</EM></A>
<DD> This specifies the name of the folder to use for the <EM>INBOX</EM>.
By default this is unset and the system's default is used.
The most common reason for
setting this is to open an IMAP mailbox for the <EM>INBOX</EM>. For example,
<EM>{imap5.u.example.edu}inbox</EM> will open the user's standard
<EM>INBOX</EM> on the mail server, <EM>imap5</EM>. <P>
<DT> <A NAME="incoming-archive-folders"><EM>incoming-archive-folders</EM></A>
<DD> This is like <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>,
only more general. This is a list
of folder pairs, with the first separated from the second in the pair by a
space. The first folder in a pair is the folder you want to archive, and
the second folder is the folder that read messages from the first should
be moved to. Depending on how you define the
<A HREF="#auto-read-msg"><EM>auto-move-read-msgs</EM></A>
feature, you may or may not be asked when you leave
the first folder if you want read messages to be moved to the second
folder. In either case, moving the messages means they will be deleted
from the first folder. <P>
If these are not path names, they will be in the default collection for
<EM>Save</EM>s. Any valid folder specification, local or remote (via IMAP), is
allowed. There is no default. <P>
<DT> <A NAME="incoming-check-interval"><EM>incoming-check-interval</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
This option specifies, in seconds, how often <EM>Alpine</EM> will check
for new mail and state changes in Incoming Folders when Incoming Folders
Checking is turned on.
The default is 3 minutes (180).
This value applies only to folders that are local to the system that
<EM>Alpine</EM> is running on or that are accessed using the IMAP protocol.
The similar option
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>
applies to all other monitored folders.
<P>
<DT> <A NAME="incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
This option together with the option
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>
specifies, in seconds, how often <EM>Alpine</EM> will check
for new mail and state changes in Incoming Folders when Incoming Folders
Checking is turned on.
The default for this option is 3 minutes (180).
For folders that are local to this system or
that are accessed using the IMAP protocol
the value of the option
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>
is used.
For all other monitored folders, the value of this option is used.
<P>
The reason there are two separate options is because it is usually
less expensive to check local and IMAP folders than it is to check
other types, like POP or NNTP folders.
You may want to set this secondary value to a higher number than
the primary check interval.
<P>
<DT> <A NAME="incoming-check-list"><EM>incoming-check-list</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When monitoring the Incoming Message Folders for Unseen messages Alpine will
normally monitor all Incoming Folders.
You may use this option to restrict the list of monitored folders to a
subset of all Incoming Folders.
<P>
<DT> <A NAME="incoming-check-timeout"><EM>incoming-check-timeout</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
Sets the time in seconds that Alpine will
attempt to open a network connection used for monitoring for Unseen
messages in Incoming Folders. The default is 5.
If a connection has not completed within this many seconds Alpine will
give up and consider it a failed connection.
<P>
<DT> <A NAME="inc-fold"><EM>incoming-folders</EM></A>
<DD> This is a list of one or more folders other than <EM>INBOX</EM> that
may receive new messages. This list is slightly special in that it is
always expanded in the folder lister. In the future, it may become more
special. For example, it would be nice
if <EM>Alpine</EM> would monitor the folders
in this list for new mail. <P>
<DT> <A NAME="incoming-startup-rule"><EM>incoming-startup-rule</EM></A>
<DD> This rule affects <EM>Alpine</EM>'s behavior when opening
the <EM>INBOX</EM> or
another folder from the "INCOMING MESSAGE FOLDERS".
This rule tells <EM>Alpine</EM>
which message to make the current message when an incoming folder is opened.
There are seven possible values for this option:
<P>
<DL>
<DT> <EM>first-unseen</EM>
<DD> The current message will be the first unseen message which has not been
marked deleted, or the last message if all of the messages have been seen.
This is the default setting.
<P>
<DT> <EM>first-recent</EM>
<DD> This is similar to <EM>first-unseen</EM>. Instead of first unseen
it is the first recent message. A message is considered to be recent if it
arrived since the last time the folder was open (by any mail client, not just
the current one). So this option causes the
current message to be set to the first undeleted-recent message, or the
last message if none is both undeleted and recent.
<P>
<DT> <EM>first-important</EM>
<DD> This will result in the current message being set to the first
message marked Important (but not Deleted).
If no messages are marked Important, then it will be the last message.
<P>
<DT> <EM>first-important-or-unseen</EM>
<DD> This selects the minimum of the first unseen and the first important
messages.
<P>
<DT> <EM>first-important-or-recent</EM>
<DD> This selects the first of the first recent and the first important
messages.
<P>
<DT> <EM>first</EM>
<DD> Set the current message to the first undeleted message unless all
are deleted. In that case set it to the last message.
<P>
<DT> <EM>last</EM>
<DD> Set the current message to the last undeleted message unless all
are deleted. In that case set it to the last message.
<P>
</DL>
<P>
<DT> <A NAME="incoming-unseen-background-color"><EM>incoming-unseen-background-color</EM></A>
<DT> <A NAME="incoming-unseen-foreground-color"><EM>incoming-unseen-foreground-color</EM></A>
<DD> <A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>.
<P>
<DT> <A NAME="index-answered-background-color"><EM>index-answered-background-color</EM></A>
<DT> <A NAME="index-answered-foreground-color"><EM>index-answered-foreground-color</EM></A>
<DT> <A NAME="index-arrow-background-color"><EM>index-arrow-background-color</EM></A>
<DT> <A NAME="index-arrow-foreground-color"><EM>index-arrow-foreground-color</EM></A>
<DT> <A NAME="index-deleted-background-color"><EM>index-deleted-background-color</EM></A>
<DT> <A NAME="index-deleted-foreground-color"><EM>index-deleted-foreground-color</EM></A>
<DT> <A NAME="index-from-background-color"><EM>index-from-background-color</EM></A>
<DT> <A NAME="index-from-foreground-color"><EM>index-from-foreground-color</EM></A>
<DT> <A NAME="index-highpriority-background-color"><EM>index-highpriority-background-color</EM></A>
<DT> <A NAME="index-highpriority-foreground-color"><EM>index-highpriority-foreground-color</EM></A>
<DT> <A NAME="index-important-background-color"><EM>index-important-background-color</EM></A>
<DT> <A NAME="index-important-foreground-color"><EM>index-important-foreground-color</EM></A>
<DT> <A NAME="index-lowpriority-background-color"><EM>index-lowpriority-background-color</EM></A>
<DT> <A NAME="index-lowpriority-foreground-color"><EM>index-lowpriority-foreground-color</EM></A>
<DT> <A NAME="index-new-background-color"><EM>index-new-background-color</EM></A>
<DT> <A NAME="index-new-foreground-color"><EM>index-new-foreground-color</EM></A>
<DT> <A NAME="index-opening-background-color"><EM>index-opening-background-color</EM></A>
<DT> <A NAME="index-opening-foreground-color"><EM>index-opening-foreground-color</EM></A>
<DT> <A NAME="index-recent-background-color"><EM>index-recent-background-color</EM></A>
<DT> <A NAME="index-recent-foreground-color"><EM>index-recent-foreground-color</EM></A>
<DT> <A NAME="index-subject-background-color"><EM>index-subject-background-color</EM></A>
<DT> <A NAME="index-subject-foreground-color"><EM>index-subject-foreground-color</EM></A>
<DT> <A NAME="index-to-me-background-color"><EM>index-to-me-background-color</EM></A>
<DT> <A NAME="index-to-me-foreground-color"><EM>index-to-me-foreground-color</EM></A>
<DT> <A NAME="index-unseen-background-color"><EM>index-unseen-background-color</EM></A>
<DT> <A NAME="index-unseen-foreground-color"><EM>index-unseen-foreground-color</EM></A>
<DD> <A HREF="#index-colors"><EM>Index Colors</EM></A>.
<P>
<DT> <A NAME="index-format"><EM>index-format</EM></A>
<DD> This option is used to customize the content of lines in the
MESSAGE INDEX screen. Each line is intended
to convey some amount of immediately relevant information about each
message in the current folder.
<P>
<EM>Alpine</EM> provides a pre-defined set of informational fields with
reasonable column widths automatically computed. You can, however,
replace this default set by listing special tokens in the order you
want them displayed.
<P>
The list of available tokens is
<A HREF="#index-tokens"><EM>here</EM></A>.
<P>
Spaces are used to separate listed tokens. Additionally, you can
specify how much of the screen's width the taken's associated data
should occupy on the index line by appending the token with a pair of
parentheses enclosing either a number or percentage. For example,
"SUBJECT(13)" means to allocate 13 characters of space to the subject
column, and "SUBJECT(20%)" means to
allocate 20% of the available space
to the subjects column, while plain "SUBJECT" means the system will
attempt to figure out a reasonable amount of space.
<P>
There is always one space between every pair of columns, so if you use fixed
column widths (like 13) you should remember to take that into account.
Several of the fields are virtually fixed-width, so it doesn't make
much sense to specify the width for them. The fields STATUS,
FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
and DESCRIPSIZE all fall into that category.
You <EM>may</EM> specify widths for those if you wish, but
you're probably better off letting the system pick those widths. <P>
<P>
The default is equivalent to:
<P>
<CENTER><SAMP>index-format=STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
<P>
This means that the four fields without percentages will be allocated
first, and then 33% and 67% of the <EM>remaining</EM> space will go to
the from and subject fields. If one of those two fields is specified
as a percentage and the other is left for the system to choose, then
the percentage is taken as an absolute percentage of the screen, not
of the space remaining after allocating the first four columns. It
doesn't usually make sense to do it that way. If you leave off all
the widths, then the subject and from fields (if both are present) are
allocated space in a 2 to 1 ratio, which is almost exactly the same as
the default.
<P>
What you are most likely to do with this configuration option is to
specify which fields appear at all, which order they appear in, and the
percentage of screen that is used for the from and subject fields if you
don't like the 2 to 1 default.
<P>
If you want to retain the default format that <EM>Pine</EM> 4.64 had, use
<P>
<CENTER><SAMP>Index-Format=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
<P>
<EM>and</EM> set the feature
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A>.
<P>
<DT> <A NAME="initial-keystroke-list"><EM>initial-keystroke-list</EM></A>
<DD> This is a comma-separated list of keystrokes which <EM>Alpine</EM> executes on
startup. Items in the list are usually just characters, but there are
some special values. <EM>SPACE,</EM> <EM>TAB,</EM> and <EM>CR</EM> mean a
space character, tab character, and a carriage return, respectively.
<EM>F1</EM> through <EM>F12</EM> stand for the twelve function keys.
<EM>UP, DOWN, LEFT, </EM>and<EM> RIGHT </EM>stand for the arrow keys.
Control characters are represented with <EM>^<char></EM>. A
restriction is that you can't mix function keys and character keys in this
list even though you can, in some cases, mix them when running <EM>Alpine</EM>. A
user can always use only <EM>character</EM> keys in the startup list even
if he or she is using <EM>function</EM> keys normally, or vice versa. If
an element in this list is a string surrounded by double quotes (")
then it will be expanded into the individual characters in the string,
excluding the double quotes. <P>
<DT> <A NAME="kblock-count"><EM>kblock-passwd-count</EM></A>
<DD> System-wide <EM>Alpine</EM> configuration files only. Number of times a user
will have to enter a password when they run the keyboard lock command in
the main menu. <P>
<DT> <A NAME="keyb-char-set"><EM>keyboard-character-set</EM></A>
<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>
<DT> <A NAME="keylabel-background-color"><EM>keylabel-background-color</EM></A>
<DT> <A NAME="keylabel-foreground-color"><EM>keylabel-foreground-color</EM></A>
<DD> <A HREF="#keylabel-color"><EM>KeyLabel Color</EM></A>.
<P>
<DT> <A NAME="keyname-background-color"><EM>keyname-background-color</EM></A>
<DT> <A NAME="keyname-foreground-color"><EM>keyname-foreground-color</EM></A>
<DD> <A HREF="#keyname-color"><EM>KeyName Color</EM></A>.
<P>
<DT> <A NAME="keywords"><EM>keywords</EM></A>
<DD> You may define your own set of keywords and optionally set them on a
message by message basis.
These are similar to the "Important" flag which the user
may set using the Flag command.
The difference is that the Important flag is always present for each folder.
User-defined keywords are chosen by the user.
You may set up the list of possible keywords here, or you may add keywords
from the Flag Details screen that you
can get to after typing the
Flag (*)
command.
After the keywords have been defined,
then you use the Flag command
to set or clear the keywords in each message.
The behavior of the flag command may be modified by using the
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A> option or the
<A HREF="#enable-flag-screen-keyword-shortcut"><EM>Enable-Flag-Screen-Keyword-Shortcut</EM></A> option.
<P>
Keywords may be used when Selecting messages (Select Keyword).
Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
Filter rules may be used to set keywords automatically.
Keywords may be displayed as part of the Subject of a message by using
the SUBJKEY or SUBJKEYINIT tokens in the
<A HREF="#index-format">Index-Format</A> option.
The <A HREF="#keyword-surrounding-chars"><EM>Keyword-Surrounding-Chars</EM></A>
option may be used to modify the display of keywords using
SUBJKEY and SUBJKEYINIT slightly.
Keywords may also be displayed in a column of their own in the MESSAGE INDEX
screen by using the KEY or KEYINIT tokens.
It is also possible to color keywords in the index using the
Setup/Kolor screen
(<A HREF="#keyword-colors">Keyword Colors</A>).
Keywords are not supported by all mail servers.
<P>
You may give keywords nicknames if you wish.
If the keyword definition you type in contains a SPACE character, then the
actual value of the keyword is everything after the last SPACE and the
nickname for that keyword is everything before the last SPACE.
For example, suppose you are trying to interoperate with another email program
which uses a particular keyword with an unpleasant name.
Maybe it uses a keyword called
<P>
<CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
<P>
but for you that keyword means that the message is work-related.
You could define a keyword to have the value
<P>
<CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
<P>
and then you would use the name "Work" when dealing with
that keyword in <EM>Alpine</EM>.
If you defined it as
<P>
<CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
<P>
the nickname would be everything before the last SPACE, that is the nickname
would be "My Work".
<P>
Some commonly used keywords begin with dollar signs.
This presents a slight complication, because the dollar sign is normally used
to signify
<A HREF="config-notes.html#env-variables">environment variable expansion</A>
in the <EM>Alpine</EM> configuration.
In order to specify a keyword which begins with a dollar sign you must
precede the dollar sign with a second dollar sign to escape its special
meaning.
For example, if you want to include the keyword
<P>
<CENTER><SAMP>$Label1</SAMP></CENTER>
<P>
as one of your possible keywords, you must enter the text
<P>
<CENTER><SAMP>$$Label1</SAMP></CENTER>
<P>
instead.
<P>
<DT> <A NAME="keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>
<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX and MESSAGE
TEXT screens.
If you have modified the
<A HREF="#index-format"><EM>Index-Format</EM></A> option
so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
are used to display keywords or their initials along with the Subject; then
this option may be used to modify the resulting display slightly.
By default, the keywords or initials displayed for these tokens will be
surrounded with curly braces ({ and }) and a trailing space.
For example, if keywords "Work" and "Now" are set for
a message, the "SUBJKEY" token will normally look like
<P>
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
<P>
and the SUBJKEYINIT token would look like
<P>
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
<P>
The default character before the keywords is the left brace ({) and the
default after the keywords is the right brace followed by a space (} ).
<P>
This option allows you to change that.
You should set it to two values separated by a space.
The values may be quoted if they include space characters.
So, for example, the default value could be specified explicitly by setting this
option to
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="{" "} "</SAMP></CENTER>
<P>
The first part wouldn't need to be quoted (but it doesn't hurt).
The second part does need the quotes because it includes a space character.
If you wanted to change the braces to brackets you could use
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="[" "] "</SAMP></CENTER>
<P>
Inside the quotes you can use backslash quote to mean quote, so
<P>
<CENTER><SAMP>Keyword-Surrounding-Chars="\"" "\" "</SAMP></CENTER>
<P>
would produce
<P>
<CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
<P>
It is also possible to color keywords in the index using the
Setup/Kolor screen
(<A HREF="#keyword-colors">Keyword Colors</A>).
<P>
It is not possible to change the fact that a space character is used to
separate the keywords if more than one keyword is set for a message.
It is also not possible to change the fact that there are no separators
between the keyword initials if more than one keyword is set.
<P>
This option is displayed as "Keyword Surrounding Characters".
<P>
<DT> <A NAME="last-time"><EM>last-time-prune-questioned</EM></A>
<DD> Personal configuration file only. This variable records the month
the user was last asked if his or her <EM>sent-mail</EM> folders should
be pruned.
The format is <EM>yy.mm</EM>.
This is automatically updated by <EM>Alpine</EM> when
the the pruning is done or declined.
If a user wanted to make <EM>Alpine</EM> stop
asking this question he or she could set this time to something
far in the future.
This may not be set in the system-wide configuration files.
Note: The <EM>yy</EM> year is actually the number of years since 1900, so it
will be equal to 101 in the year 2001.
<P>
<DT> <A NAME="last-version-used"><EM>last-version-used</EM></A>
<DD> Personal configuration file only.
This is set automatically by <EM>Alpine</EM>.
It is used to keep track of the last version of <EM>Alpine</EM> that
was run by the user.
Whenever the version number increases, a new version message is printed out.
This may not be set in the system-wide configuration files.
<P>
<DT> <A NAME="ldap-servers"><EM>ldap-servers</EM></A>
<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library
when it was compiled. This variable is normally managed by <EM>Alpine</EM> though
it can be set in the system-wide configuration files as well as the personal
configuration. It is a list variable. Each item in the
list contains quite a bit of extra information besides just the server name.
To put this into a system-wide config file the easiest thing to do is to
configure a personal <EM>Alpine</EM> for the LDAP server then copy the
configuration line
into the system-wide config file. Each item in the list looks like:
<BLOCKQUOTE>
<CODE>
server_name[:port] <SPACE> "quoted stuff" </CODE><BR>
</BLOCKQUOTE>
The <CODE>server_name</CODE> is just a hostname and it is followed by
an optional colon and port number. The default <CODE>port</CODE> is 389.
Following the server name is a single SPACE character followed by
a bunch of characters inside double quotes. The part inside the quotes is
a set of <EM>tag</EM> = <EM>value</EM> pairs.
Each tag is preceded by a slash (/) and followed
by an equal sign. The value for that tag is the text up to the next slash.
An example of some <CODE>quoted stuff</CODE> is:
<BLOCKQUOTE>
<CODE>
"/base=o=University of Washington, c=US/impl=0/.../nick=My Server"
</CODE><BR>
</BLOCKQUOTE>
This would set the search base for this server to
<CODE>o=University of Washington, c=US</CODE>, set the implicit bit to zero,
and set the nickname for the server to <CODE>My Server</CODE>.
All of the tags correspond directly to items in the Setup/Directory screen
so experiment with that if you want to see what the possible tags and values
are.
<P>
<DT> <A NAME="literal-signature"><EM>literal-signature</EM></A>
<DD> With this option your actual signature, as opposed to
the name of a file containing your signature,
is stored in the <EM>Alpine</EM> configuration file.
If this is defined it takes precedence over the <EM>signature-file</EM> option.
<P>
This is simply a different way to store the signature data.
The signature is stored inside your <EM>Alpine</EM> configuration file
instead of in a separate signature file.
Tokens contained in the signature work the same way they do with the regular
<A HREF="#sig-file">signature-file</A>.
<P>
The Setup/Signature command in <EM>Alpine</EM>'s Main Menu will edit
the <EM>literal-signature</EM> by default. However, if no
<EM>literal-signature</EM> is defined and the file named in the
<EM>signature-file</EM> option exists, then the latter will be used
instead. Compose (Reply, Forward, ...) will default to using the
<EM>literal-signature</EM> if defined, otherwise it will use the contents
of the file named in <EM>signature-file</EM>.
<P>
The <EM>Alpine</EM> composer is used to edit the literal-signature.
The result of that edit is first converted to a C-style string before it
is stored in the configuration file.
In particular, the two character sequence \n (backslash followed by
the character "n") will be used to signify a
line-break in the signature.
You don't have to enter the \n, but it will be visible in the
SETUP CONFIGURATION window after you are done editing the signature.
<P>
<DT> <A NAME="mail-check"><EM>mail-check-interval</EM></A>
<DD> This option specifies, in seconds,
how often <EM>Alpine</EM> will check for new mail.
If set to zero, new-mail checking is disabled.
(You can always manually force a new-mail check by typing ^L (Ctrl-L), which is also
the command to refresh the screen, or by typing the Next command when the
current message is the last message of the folder.)
There is a minimum value for this option, normally 15 seconds.
The default value is normally 150 seconds.
The higher you set this option, the easier it is on the server.
<P>
There are some situations where automatic new-mail checking does not work.
See the discussion about new-mail checking in <A HREF="#reopen-rule"><EM>folder-reopen-rule</EM></A>.
<P>
The new-mail checking will not happen exactly at the frequency that you specify.
For example, <EM>Alpine</EM> may elect to defer a non-INBOX mail check if you
are busy typing.
Or, it may check more frequently than you have specified if that is
thought to be necessary to keep the server from closing the connection
to the folder due to inactivity.
If <EM>Alpine</EM> checks for new mail as a side effect of another command, it will reset
the timer, so that new-mail checking may seem to happen irregularly instead of
every X seconds like clockwork.
<P>
If you are anxious to know about new mail as soon as possible, set the check
interval low, and you'll know about the new mail by approximately
that amount of time after it arrives.
If you aren't so worried about knowing right away, set this option to a
higher value.
That will save the server some processing time and may save you some of
the time you spend waiting for new-mail checks to happen if you are
dealing with a slow server or slow network connection.
<P>
If you suspect that new-mail checking is causing slow downs for you,
you may want to look into the options
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>,
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> and
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A>,
which refine when mail checking is done.
<P>
If the mailbox being check uses a <A HREF="config-notes.html#maildrop">Mail Drop</A> then
there is a minimum time
(<A HREF="#maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A>)
between new-mail checks.
Because of this minimum you may notice that new mail does not
appear promptly when you expect it.
The reason for this is to protect the server from over-zealous opening and
closing of the Mail Drop folder, since that is a costly operation.
<P>
A side effect of disabling mail checking is that there will be situations
in which the user's IMAP connection will be broken due to inactivity timers
on the server. Another side effect is that the
<A HREF="#user-input"><EM>user-input-timeout</EM></A>
option won't work.
<P>
<DT> <A NAME="mail-check-noncurr"><EM>mail-check-interval-noncurrent</EM></A>
<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, as well as the
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A> and
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> options.
If the "Mail-Check-Interval" option is set to zero, then automatic
new-mail checking is disabled and this option will have no effect.
<P>
Normally this option is set to zero, which means that the value used will be
the same as the value for the "Mail-Check-Interval".
If you set this option to a value different from zero
(usually larger than the value for "Mail-Check-Interval")
then that is the check interval that will be used
for folders which are not the currently open folder or the INBOX.
You may not even have any folders that are noncurrent and not the INBOX.
If you do, it is likely that they are due to
<A HREF="#stay-open-folders">Stay-Open-Folders</A>
you have configured.
This option also affects the rate of mail checking done on cached
connections to folders you previously had open but are no longer actively
using.
You aren't expected to understand that last sentence, but if you are interested
take a look at
<A HREF="#max-remote-connections">Max-Remote-Connections</A>,
and the related options.
<P>
<DT> <A NAME="mail-directory"><EM>mail-directory</EM></A>
<DD> This variable was more important in previous versions of <EM>Alpine</EM>. Now
it is used only as the default for storing personal folders (and only if
there are no <A HREF="#fold-coll"><EM>folder-collections</EM></A> defined).
The default value is
<EM>~/mail</EM> on UNIX and <EM>${HOME}\MAIL</EM> on a PC. <P>
<DT> <A NAME="mailcap-search-path"><EM>mailcap-search-path</EM></A>
<DD> This variable is used to replace <EM>Alpine</EM>'s default
mailcap file search path.
It takes one or more file names (full paths must be specified) in
which to look for mail capability data. <P>
<DT> <A NAME="maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A>
<DD> New-mail checking for a
<A HREF="config-notes.html#maildrop">Mail Drop</A>
is a little different from new
mail checking for a regular folder.
One of the differences is that the connection to the Mail Drop is not
kept open and so the cost of checking
(delay for you and additional load for the server) may be significant.
Because of this additional cost we set a minimum time that
must pass between checks.
This minimum only applies to the automatic checking done by <EM>Alpine</EM>.
If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
at the end of a folder index, then the check is done right away.
<P>
This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
new-mail checks.
You may want to set this minimum high in order to avoid experiencing some
of the delays associated with the checks.
Note that the time between checks is still controlled by the regular
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> option.
When <EM>Alpine</EM> is about to do an automatic check for new mail (because
the Mail-Check-Interval has expired) then if the time since the last
new-mail check
of any open Mail Drops has been greater than the MailDrop-Check-Minimum,
the Mail Drop is checked for new mail as well.
Therefore, it is only useful to set this option to a value that is higher
than the Mail-Check-Interval.
<P>
If this option is set to zero, automatic Mail Drop new-mail
checking is disabled.
There is a minimum value, normally 60 seconds.
The default value is normally 60 seconds as well.
This applies to the INBOX and to the currently open folder if that is
different from the INBOX.
<P>
<DT> <A NAME="max-remote-connections"><EM>max-remote-connections</EM></A>
<DD> This option affects low-level behavior of <EM>Alpine</EM>.
The default value for this option is <EM>2</EM>.
If your INBOX is accessed using the IMAP protocol
from an IMAP server, that connection is kept open throughout the
duration of your <EM>Alpine</EM> session, independent of the value of this option.
The same is true of any
<A HREF="#stay-open-folders">Stay-Open-Folders</A>
you have defined.
This option controls <EM>Alpine</EM>'s behavior when connecting to remote IMAP folders
other than your INBOX or your Stay-Open-Folders.
It specifies the maximum number of remote IMAP connections (other than
those mentioned above) that <EM>Alpine</EM> will use for accessing the rest of your
folders.
If you set this option to zero, you will turn off most remote connection
re-use.
It's difficult to understand exactly what this option does, and it is usually
fine to leave it set to its default value.
It is probably more likely that you will be interested in setting the
<A HREF="#stay-open-folders">Stay-Open-Folders</A> option
instead of changing the value of this option.
A slightly longer explanation of what is going on with this option
is given in the next paragraphs.
<P>
There are some time costs involved in opening and closing remote IMAP
folders, the main costs being the time you have to wait for the connection
to the server and the time for the folder to open.
Opening a folder may involve not only the time the server takes to do its
processing but time that <EM>Alpine</EM> uses to do filtering.
These times can vary widely.
They depend on how loaded the server is, how large
the folder being opened is, and how you set up filtering, among other things.
Once <EM>Alpine</EM> has opened a connection to a particular folder, it will attempt
to keep that connection open in case you use it again.
In order to do this,
<EM>Alpine</EM> will attempt to use the Max-Remote-Connections (the value of
this option) IMAP connections you have allotted for this purpose.
<P>
For example, suppose the value of this option is set to "2".
If your INBOX is accessed on a remote server using the IMAP protocol, that
doesn't count as one of the remote connections but it is always kept open.
If you then open another IMAP folder, that would be your first
remote connection counted as one of the Max-Remote-Connections connections.
If you open a third folder the second will be left open, in case you
return to it.
You won't be able to tell it has been left open.
It will appear to be closed when you leave the folder but the connection
will remain in the background.
Now suppose you go back to the second folder (the first folder after the
INBOX).
A connection to that folder is still open so you won't have to wait
for the startup time to open it.
Meanwhile, the connection to the third folder will be left behind.
Now, if you open a fourth folder, you will bump into the
Max-Remote-Connections limit, because this will be the third folder other
than INBOX and you have the option set to "2".
The connection that is being used for
the third folder will be re-used for this new fourth folder.
If you go back to the third folder after this, it is no longer already
connected when you get there.
You'll still save some time since <EM>Alpine</EM> will re-use the connection to the
fourth folder and you have already logged in on that connection,
but the folder will have to be re-opened from scratch.
<P>
If a folder is large and the startup cost is dominated by the time it takes
to open that folder or to run filters on it, then it will pay to make the
value of this option large enough to keep it open.
On the other hand, if you only revisit a handful of folders or if
the folders are small, then it might
make more sense to keep this number small so that the reconnect
time (the time to start up a new connection and authenticate)
is eliminated instead.
<P>
You may also need to consider the impact on the server.
On the surface, a larger number here may cause a larger impact on the
server, since you will have more connections open to the server.
On the other hand, not only will <EM>you</EM> be avoiding the startup costs
associated with reopening a folder, but the <EM>server</EM> will be
avoiding those costs as well.
<P>
When twenty five minutes pass without any active use of an IMAP connection
being saved for possible re-use, that connection will be shut down,
<P>
This option is displayed as "Maximum Remote Connections".
<P>
<DT> <A NAME="meta-message-background-color"><EM>meta-message-background-color</EM></A>
<DT> <A NAME="meta-message-foreground-color"><EM>meta-message-foreground-color</EM></A>
<DD> <A HREF="#meta-message-color"><EM>Meta-message Color</EM></A>.
<P>
<DT> <A NAME="mimetype-search-path"><EM>mimetype-search-path</EM></A>
<DD> This variable is used to replace <EM>Alpine</EM>'s default mime.types file
search path. It takes one or more file names (full paths must be
specified) in which to look for file-name-extension to MIME type mapping
data. See the Config Notes for details on <EM>Alpine</EM>'s usage of the <A
HREF="config-notes.html#mime.types">MIME.Types File</A>. <P>
<DT> <A NAME="new-version-threshold"><EM>new-version-threshold</EM></A>
<DD> When a new version of <EM>Alpine</EM> is run for the first time it offers a
special explanatory screen to the user upon startup. This option
helps control when and if that special screen appears for users that
have previously run <EM>Alpine</EM>. It takes as its value a <EM>Alpine</EM> version
number. <EM>Alpine</EM> versions less than the specified value will suppress this
special screen while versions equal to or greater than that specified
will behave normally. <P>
<DT> <A NAME="newmail-fifo-path"><EM>newmail-fifo-path</EM></A>
<DD> This option is only available in UNIX <EM>Alpine</EM>.
However, there is a very similar feature built in to <EM>PC-Alpine</EM>.
In <EM>PC-Alpine</EM>'s Config menu at the top of the screen
is an option called "New Mail Window".
<P>
You may have <EM>Alpine</EM> create a FIFO special file (also called a named pipe, see mkfifo(3) and fifo(4)) where
it will send a one-line message each time a new message is received in
the current folder, the INBOX, or any open
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
To protect against two different <EM>Alpine</EM>s both writing to the same FIFO, <EM>Alpine</EM>
will only create the FIFO and write to it if it doesn't already exist.
<P>
A possible way to use this option would be to have a separate window
on your screen running the command
<P>
<CENTER><SAMP>cat filename</SAMP></CENTER>
<P>
where "filename" is the name of the file given for this option.
Because the file won't exist until after you start <EM>Alpine</EM>, you must <EM>first</EM>
start <EM>Alpine</EM> and <EM>then</EM> run the "cat" command.
You may be tempted to use "tail -f filename" to view the new
mail log.
However, the common implementations of the tail command will not do what you
are hoping.
<P>
The width of the messages produced for the FIFO may be altered with the
<A HREF="#newmail-window-width">NewMail-Window-Width</A> option.
<P>
On some systems, fifos may only be created in a local filesystem.
In other words, they may not be in NFS filesystems.
This requirement is not universal.
If the system you are using supports it, it should work.
(It is often the case that your home directory is in an NFS filesystem.
If that is the case, you might try using a file in the "/tmp"
filesystem, which is usually a local filesystem.)
Even when it is possible to use an NFS-mounted filesystem as a place to name
the fifo (for example, your home directory), it will still be the case that
the reader (probably the "cat" command) and the
writer (<EM>Alpine</EM>) of the fifo must be running on the same system. <P>
<DT> <A NAME="newmail-window-width"><EM>newmail-window-width</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This option is only useful if you have turned on the
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option.
That option causes new mail messages to be sent to a fifo file.
Those messages will be 80 characters wide by default.
You can change the width of the messages by changing this option.
For example, if you are reading those messages in another window you might
want to set this width to the width of that other window. <P>
For UNIX <EM>Alpine</EM>, this option is only useful if you have turned on the
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option.
That option causes new mail messages to be sent to a fifo file.
Those messages will be 80 characters wide by default.
You can change the width of those messages by changing this option.
For example, if you are reading those messages in another window you might
want to set this width to the width of that other window.
<P>
If you are using <EM>PC-Alpine</EM>, it has an option in the Config menu to turn
on the "New Mail Window".
The present option also controls the width of that window.
<DT> <A NAME="news-active"><EM>news-active-file-path</EM></A>
<DD> This option tells <EM>Alpine</EM> where to look for the "active file" for
newsgroups when accessing news locally, rather than via NNTP. The default
path is usually <CODE>/usr/lib/news/active</CODE>. <P>
<DT> <A NAME="news-coll"><EM>news-collections</EM></A>
<DD> This is a list of collections where news folders are located. See
the section describing <A HREF="config-notes.html#collections">collections</A>
for more information. <P>
<DT> <A NAME="news-spool"><EM>news-spool-directory</EM></A>
<DD> This option tells <EM>Alpine</EM> where to look for the "news spool" for
newsgroups when accessing news locally, rather than via NNTP. The default
path is usually <CODE>/usr/spool/news</CODE>. <P>
<DT> <A NAME="newsrc-path"><EM>newsrc-path</EM></A>
<DD> This option overrides the default name <EM>Alpine</EM> uses for your "newsrc"
news status and subscription file. If set, <EM>Alpine</EM> will take this value as
the full pathname for the desired newsrc file. <P>
<DT> <A NAME="nntp-range"><EM>nntp-range</EM></A>
<DD> This option applies only to newsgroups accessed using the NNTP protocol.
It does not, for example,
apply to newsgroups accessed using an IMAP-to-NNTP proxy.
<P>
When you open a connection to a News server using the NNTP protocol, you
normally have access to all of the articles in each newsgroup.
If a server keeps a large backlog of messages it may speed performance
some to restrict attention to only the newer messages in a group.
This option allows you to set how many article numbers should be checked
when opening a newsgroup.
You can think of "nntp-range" as specifying the maximum number
of messages you ever want to see.
For example, if you only ever wanted to look at the last 500 messages in each
newsgroup you could set this option to 500.
In actuality, it isn't quite that.
Instead, for performance reasons, it specifies the range of article
numbers to be checked, beginning
with the highest numbered article and going backwards from there.
If there are messages that have been canceled or deleted
their article numbers are still counted as part of the range.
<P>
So, more precisely, setting the "nntp-range" will cause article
numbers
<P><CENTER>last_article_number - nntp-range + 1 through last_article_number</CENTER>
<P>
to be considered when reading a newsgroup.
The number of messages that show up in your index will be less than or equal
to the value of "nntp-range".
<P>
The purpose of this option is simply to speed up access when reading news.
The speedup comes because <EM>Alpine</EM> can ignore all but the last nntp-range article
numbers, and can avoid downloading any information about the ignored articles.
There is a cost you pay for this speedup.
That cost is that there is no way for you to see those ignored articles.
The articles that come before the range you specify are invisible to you and
to <EM>Alpine</EM>, as if they did not exist at all.
There is no way to see those messages using, for example, an unexclude command
or something similar.
The only way to see those articles is to set this option high enough (or
set it to zero) and then to reopen the newsgroup.
<P>
If this option is set to 0 (which is also the default),
then the range is unlimited.
This option applies globally to all NNTP servers and to all newsgroups
on those servers.
There is no way to set different values for different newsgroups or servers.
<P>
<DT> <A NAME="nntp-server"><EM>nntp-server</EM></A>
<DD> One or more NNTP servers (host name or IP address) which <EM>Alpine</EM> will
use for reading and posting news.
If you read and post news to and from a single
NNTP server, you can get away with only setting the <EM>nntp-server</EM>
variable and leaving the <EM>news-collections</EM> variable unset.
<P>
When you define an NNTP server, <EM>Alpine</EM> implicitly defines a
news collection for you, assuming that server as the news server
and assuming that you will use the NNTP protocol and a local newsrc
configuration file for reading news.
See also <A HREF="#configuring-news">Configuring News</A>.
<P>
Your NNTP server may offer NNTP "AUTHINFO SASL"
or "AUTHINFO USER" authentication.
It may even require it.
If your NNTP server does offer such authentication you may specify a user name
parameter to cause <EM>Alpine</EM> to attempt to authenticate.
The same is true for the server name in a folder collection which uses NNTP.
This parameter requires an associated value,
the username identifier with which to establish the server connection.
An example might be:
<P>
<CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
<P>
If authentication is offered by the server, this will cause <EM>Alpine</EM> to
attempt to use it.
If authentication is not offered by the server, this will cause <EM>Alpine</EM>
to fail with an error similar to:
<P>
<CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
<P>
For more details about the server name possibilities see
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A>.
<P>
<DT> <A NAME="norm-back"><EM>normal-background-color</EM></A>
<DT> <A NAME="normal-foreground-color"><EM>normal-foreground-color</EM></A>
<DD> <A HREF="#normal-color"><EM>Normal Color</EM></A>.
<P>
<DT> <A NAME="opening-text-separator-chars"><EM>opening-text-separator-chars</EM></A>
<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX screen.
With some setups the text of the subject is followed
by the opening text of the message if there is any room available in the index line.
If you have configured your
<A HREF="#index-format"><EM>Index-Format</EM></A> option
to include one of the Subject tokens which causes this behavior
(SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
to modify what is displayed slightly.
By default, the Subject is separated from the opening text of the message by
the three characters space dash space;
<P>
<CENTER><SAMP>" - "</SAMP></CENTER>
<P>
Use this option to set it to something different.
The value must be quoted if it includes any space characters.
For example, the default value could be specified explicitly by setting this
option to
<P>
<CENTER><SAMP>Opening-Text-Separator-Chars=" - "</SAMP></CENTER>
<P>
This option is displayed as "Opening Text Separator Characters".
<P>
<DT> <A NAME="operating-dir"><EM>operating-dir</EM></A>
<DD> System-wide <EM>Alpine</EM> configuration files only.
This names the root of the
tree to which the user is restricted when reading and writing folders and
files. It is usually used in the <EM>fixed</EM> configuration file. <P>
<DT> <A NAME="patterns-filters2"><EM>patterns-filters2</EM></A>
<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#filter-config"><EM>Filtering</EM></A>.
This variable is normally maintained through the Setup/Rules/Filters
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a filters file is to use the InsertFile command in
the Setup/Rules/Filters screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing filter patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of filter files is for sharing filters.
<P>
This option is displayed as "Patterns Filters".
<P>
<DT> <A NAME="patterns-indexcolors"><EM>patterns-indexcolors</EM></A>
<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used for
<A HREF="#index-color-config"><EM>Index Line Colors</EM></A>.
This variable is normally maintained through the Setup/Rules/Indexcolor
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a indexcolor file is to use the InsertFile command in
the Setup/Rules/Indexcolor screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of indexcolor files is for sharing indexcolors.
<P>
<DT> <A NAME="patterns-other"><EM>patterns-other</EM></A>
<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#other-config"><EM>Miscellaneous Rules</EM></A> configuration.
This variable is normally maintained through the Setup/Rules/Other
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a rules file is to use the InsertFile command in
the Setup/Rules/Other screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing rules into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
<P>
<DT> <A NAME="patterns-roles"><EM>patterns-roles</EM></A>
<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#role-config"><EM>Roles</EM></A>.
This variable is normally maintained through the Setup/Rules/Roles
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a roles file is to use the InsertFile command in
the Setup/Rules/Roles screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing roles into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of role files is for sharing roles.
<P>
<DT> <A NAME="patterns-scores2"><EM>patterns-scores2</EM></A>
<DD> Matching patterns and their corresponding actions are stored in
this variable.
These patterns are used with
<A HREF="#scoring-config"><EM>Scoring</EM></A>.
This variable is normally maintained through the Setup/Rules/SetScores
configuration screen.
It is a list variable.
Each member of the list is a single pattern/action pair, or it can be
a file which contains zero or more lines of pattern/action pairs.
The only way to create a scores file is to use the InsertFile command in
the Setup/Rules/SetScores screen with a filename which doesn't yet exist.
Then use the Shuffle command to move existing scoring patterns into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
The purpose of scoring files is for sharing scoring rules.
<P>
This option is displayed as "Patterns Scores".
<P>
<DT> <A NAME="patterns-search"><EM>patterns-search</EM></A>
<DD> Matching patterns for use with the Select command are stored in
this variable.
These patterns are used with
<A HREF="#search-rules-config"><EM>Search Rules</EM></A> configuration.
This variable is normally maintained through the Setup/Rules/searCh
configuration screen.
It is a list variable.
Each member of the list is a single pattern, or it can be
a file which contains zero or more lines of patterns.
The only way to create a rules file is to use the InsertFile command in
the Setup/Rules/searCh screen with a filename which doesn't yet exist. Then use
the Shuffle command to move existing rules into the file.
This isn't very convenient but it isn't thought that many users will
need this functionality.
<P>
<DT> <A NAME="personal-name"><EM>personal-name</EM></A>
<DD> Personal configuration file only.
User's full personal name. On UNIX systems, the default is taken
from the accounts data base (<CODE>/etc/passwd</CODE>).
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>
<DT> <A NAME="personal-print-category"><EM>personal-print-category</EM></A>
<DD> Personal configuration file only.
This is the category that the default print command belongs to. There
are three categories. Category 1 is an attached printer which uses the ANSI
escape sequence, category 2 is the standard system print command, and
category 3 is the set of custom printer commands defined by the user.
This just helps <EM>Alpine</EM> figure out where to put the cursor when the user
runs the <EM>Setup/Printer</EM> command. This is not used by <EM>PC-Alpine</EM>.
<P>
<DT> <A NAME="personal-print-command"><EM>personal-print-command</EM></A>
<DD> Personal configuration file only.
This corresponds to the third category in the printer menu, the
personally selected print commands. This variable
contains the list of custom commands that the user has entered in the
<EM>Setup/Printer</EM> screen. This is not used by <EM>PC-Alpine</EM>.
<P>
<DT> <A NAME="posting-char-set"><EM>posting-character-set</EM></A>
<DD> See the discussion in
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for
details.<P>
<DT> <A NAME="postponed-folder"><EM>postponed-folder</EM></A>
<DD> The folder where postponed messages are stored. The default is
<EM>postponed-msgs</EM> (Unix) or <EM>POSTPOND</EM> (PC). <P>
<DT> <A NAME="print-font-name"><EM>print-font-name</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="print-font-size"><EM>print-font-size</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="print-font-style"><EM>print-font-style</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P>
<DT> <A NAME="printer"><EM>printer</EM></A>
<DD> Personal configuration file only.
This is the current setting for a user's printer.
This variable is set from <EM>Alpine</EM>'s <EM>Setup/Printer</EM> screen.
<P>
<DT> <A NAME="prompt-background-color"><EM>prompt-background-color</EM></A>
<DT> <A NAME="prompt-foreground-color"><EM>prompt-foreground-color</EM></A>
<DD> <A HREF="#prompt-color"><EM>Prompt Color</EM></A>.
<P>
<DT> <A NAME="pruned-folders"><EM>pruned-folders</EM></A>
<DD> This variable allows you to define a list of one or more folders that
<EM>Alpine</EM> will offer to prune for you in the same way it automatically offers
to prune your "sent-mail" folder each month.
Each folder in this list must be a folder in your default folder collection
(the first folder collection if you have more than one), and it is just
the relative name of the folder in the collection, not the fully-qualified name.
It is similar to sent-mail.
Instead of something like
<P>
<CENTER><SAMP>pruned-folders={servername}mail/folder</SAMP></CENTER>
<P>
the correct value to use would be
<P>
<CENTER><SAMP>folder</SAMP></CENTER>
<P>
There is an assumption here that your first collection is the folders in
<P>
<CENTER><SAMP>{servername}mail</SAMP></CENTER>
<P>
Once a month, for each folder listed, <EM>Alpine</EM> will offer to move
the contents of the folder to a new folder of the same name but with
the previous month's date appended. <EM>Alpine</EM> will then look for any such
date-appended folder names created for a previous month, and offer each
one it finds for deletion.
<P>
If you decline the first offer, no mail is moved and no new folder is
created.
<P>
The new folders will be created
in your default folder collection.
<P>
<DT> <A NAME="pruning-rule"><EM>pruning-rule</EM></A>
<DD> By default, <EM>Alpine</EM> will ask at the beginning of each month whether or not
you want to rename your sent-mail folder to a name like sent-mail-month-year.
(See the feature <A HREF="#prune-uses-yyyy-mm">prune-uses-yyyy-mm</A> to
change the format of the folder to sent-mail-yyyy-mm.)
It will also ask whether you would like to delete old sent-mail folders.
If you have defined
<A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>
or
<A HREF="#pruned-folders"><EM>pruned-folders</EM></A>
<EM>Alpine</EM> will also ask about pruning those folders.
With this option you may provide an automatic answer to the rename questions
and you may tell <EM>Alpine</EM> to not ask about deleting old folders.<P>
<DT> <A NAME="quote1-background-color"><EM>quote1-background-color</EM></A>
<DT> <A NAME="quote1-foreground-color"><EM>quote1-foreground-color</EM></A>
<DT> <A NAME="quote2-background-color"><EM>quote2-background-color</EM></A>
<DT> <A NAME="quote2-foreground-color"><EM>quote2-foreground-color</EM></A>
<DT> <A NAME="quote3-background-color"><EM>quote3-background-color</EM></A>
<DT> <A NAME="quote3-foreground-color"><EM>quote3-foreground-color</EM></A>
<DD> <A HREF="#quote-colors"><EM>Quote Colors</EM></A>.
<P>
<DT> <A NAME="quote-replace-string"><EM>quote-replace-string</EM></A>
<DD> This option specifies what string to use as a quote when <b>viewing</b> a
message. The standard way of quoting messages when replying is the string
"> " (quote space).
With this variable set, viewing a message will
replace occurrences of "> " with the replacement string.
This setting works best when
<A HREF="#reply-ind-string">Reply-Indent-String</A>
or the equivalent setting in your correspondents' mail programs
is set to the default "> ", but it will also work fine with the
Reply-Indent-String set to ">".
<P>
Enable the feature
<A HREF="#quote-replace-nonflowed">Quote-Replace-Nonflowed</A>
to also have quote-replacement performed on non-flowed messages.
<P>
Setting this option will replace ">" and
"> " with the new setting. This string may include trailing
spaces. To preserve those spaces enclose the full string in double quotes.
<P>
No padding to separate the text of the message from the quote string is
added. This means that if you do not add trailing spaces to the value of
this variable, text will be displayed right next to the quote string,
which may be undesirable. This can be avoided by adding a new string
separated by a space from your selection of quote string replacement. This
last string will be used for padding. For example, setting this variable to
">" " " has the effect of setting
">" as the quote-replace-string, with the text padded by
a space from the last quote string to make it more readable.
<P>
One possible setting for this variable could be
" " (four spaces wrapped in quotes), which
would have the effect of indenting each level of quoting four spaces and
removing the ">"'s. Different levels of quoting could be made
more discernible by setting colors for quoted text.
<P>
Replying to or forwarding the viewed message will preserve the original
formatting of the message, so quote-replacement will not be performed on
messages that are being composed.
<P>
<DT> <A NAME="quote-suppression-threshold"><EM>quote-suppression-threshold</EM></A>
<DD> This option should be used with care.
It will cause some of the quoted text to be eliminated from the
display when viewing a message in the MESSAGE TEXT screen.
For example, if you set the Quote-Suppression-Threshold to the
value "5",
this will cause quoted text that is longer than five lines to be truncated.
Quoted text of five or fewer consecutive lines will be displayed in its entirety.
Quoted text of more than six lines will have the first five lines displayed
followed by a line that looks something like
<P>
<CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
<P>
As a special case, if exactly one line of quoted text would be hidden, the
entire quote will be shown instead.
So for the above example, quoted text which is exactly six lines long will
will be shown in its entirety.
(In other words, instead of hiding a single line and adding a line
that announces that one line was hidden, the line is just shown.)
<P>
If the sender of a message has carefully chosen the quotes that he or she
includes, hiding those quotes may change the meaning of the message.
For that reason, <EM>Alpine</EM> requires that when you want to set the value of this
variable to something less than four lines, you actually have to set it
to the negative of that number.
So if you want to set this option to "3", you actually have to
set it to "-3".
The only purpose of this is to get you to think about whether or not you
really want to do this!
If you want to delete all quoted text you set the value of this option
to the special value "-10".
<P>
The legal values for this option are
<P>
<TABLE>
<TR>
<TD> 0 </TD>
<TD> Default, don't hide anything </TD>
</TR>
<TR>
<TD> -1,-2,-3 </TD>
<TD> Suppress quote lines past 1, 2, or 3 lines </TD>
</TR>
<TR>
<TD> 4,5,6,... </TD>
<TD> Suppress if more than that many lines </TD>
</TR>
<TR>
<TD> -10 </TD>
<TD> Suppress all quoted lines </TD>
</TR>
</TABLE>
<P>
If you set this option to a non-default value you may sometimes wish to
view the quoted text that is not shown.
When this is the case, the HdrMode (Header Mode) command may be used to
show the hidden text.
Typing the "H" command once will show the hidden text.
Typing a second "H" will also turn on Full Header mode.
The presence or absence of the HdrMode command is determined by the
<A HREF="#enable-full-header-cmd">"Enable-Full-Header-Cmd"</A>
Feature-List option in your <EM>Alpine</EM> configuration, so you will want to
be sure that is turned on if you use quote suppression.
<P>
For the purposes of this option, a quote is a line that begins with the
character ">".
<P>
Quotes are only suppressed when displaying a message on the screen.
The entire quote will be left intact when printing or forwarding or something
similar.
<P>
<DT> <A NAME="read-msg-fold"><EM>read-message-folder</EM></A>
<DD> If set, mail in the <EM>INBOX</EM> that has been read but not deleted
is moved here, or rather, the user is asked whether or not he or she wants
to move it here upon quitting <EM>Alpine</EM>. <P>
<DT> <A NAME="remote-abook-history"><EM>remote-abook-history</EM></A>
<DD> Sets how many extra copies of
<A HREF="low-level.html#addrbook">remote address book</A>
data will be kept in each remote address book folder.
The default is three.
These extra copies are simply old versions of the data. Each time a change
is made a new copy of the address book data is appended to the folder. Old
copies are trimmed, if possible, when <EM>Alpine</EM> exits.
An old copy can be put back into use by
deleting and expunging newer versions of the data from the folder.
Don't delete the first message from the folder. It is a special header
message for the remote address book and it must be there.
This is to prevent regular folders from being used as remote address book
folders and having their data destroyed.
<P>
<DT> <A NAME="remote-abook-metafile"><EM>remote-abook-metafile</EM></A>
<DD> Personal configuration file only.
This is usually set by <EM>Alpine</EM> and is the name of a file
that contains data about
<A HREF="low-level.html#addrbook">remote address books</A> and
<A HREF="low-level.html#remote-config">remote configuration files</A>.
<P>
<DT> <A NAME="remote-abook-validity"><EM>remote-abook-validity</EM></A>
<DD> Sets the minimum number of minutes that a
remote address book will be considered up to date.
Whenever an entry contained in a remote address book is used,
if more than this many minutes have
passed since the last check the remote server will be queried to see if the
address book has changed.
If it has changed, the local copy is updated.
The default value is five minutes.
The special value of -1 means never check.
The special value of zero means only check when the address book is first
opened.
<P>
No matter what the value, the validity check is always done when the
address book is about to be changed by the user.
The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
while in the address book maintenance screen for the remote address book.
<P>
<DT> <A NAME="reply-ind-str"><EM>reply-indent-string</EM></A>
<DD> This variable specifies an aspect of <EM>Alpine</EM>'s <EM>Reply</EM>
command.
When a message is replied to and the text of the message is included, the
included text usually has the string "> " prepended
to each line indicating it is quoted text.
<P>
This option specifies a different value for that string.
If you wish to use a string which begins or ends with a space,
enclose the string in double quotes.
<P>
Besides simple text, the prepended string can be based
on the message being replied to.
The following tokens are substituted for the message's corresponding value:
<DL>
<DT>_FROM_</DT>
<DD>This token gets replaced with the message sender's "username".
At most six characters are used.
</DD>
<DT>_NICK_</DT>
<DD>This token gets replaced with the nickname of the message sender's
address as found in your addressbook.
If no addressbook entry is found,
Pine replaces the characters "_NICK_" with nothing.
At most six characters are used.
</DD>
<DT>_INIT_</DT>
<DD>This token gets replaced with the initials of the sender of the message.
</DD>
</DL>
When the
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>
feature is enabled, you are given the opportunity to edit the string, whether
it is the default or one automatically generated using the above tokens.
<P>
<DT> <A NAME="reply-leadin"><EM>reply-leadin</EM></A>
<DD> This option is used to customize the content of the introduction line
that is included when replying to a message and including the original
message in the reply.
The normal default (what you will get if you delete this variable) looks
something like:
<P>
<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
<P>
where the day of the week is only included if it is available in the
original message.
You can replace this default with text of your own.
The text may contain tokens that are replaced with text
that depends on the message you are replying to.
For example, the default is equivalent to:
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
<P>
Since this variable includes regular text mixed with special tokens
the tokens have to be surrounded by underscore characters.
For example, to use the token "<SAMP>PREFDATE</SAMP>"
you would need to use "<SAMP>_PREFDATE_</SAMP>",
not "<SAMP>PREFDATE</SAMP>".
<P>
The list of available tokens is
<A HREF="#index-tokens"><EM>here</EM></A>.
<P>
By default, the text is all on a single line and is followed by a blank line.
If your <EM>Reply-Leadin</EM> turns out to be longer
than 80 characters when replying to a particular message, it is shortened.
However, if you use the token
<P>
<CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
<P>
anywhere in the value, no end of line or blank line is appended, and no
shortening is done.
The _NEWLINE_ token may be used to get rid of the blank line following
the text, to add more blank lines, or to form a multi-line
<EM>Reply-Leadin</EM>.
To clarify how _NEWLINE_ works recall that the default value is:
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
<P>
That is equivalent to
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
<P>
In the former case, two newlines are added automatically because
no _NEWLINE_ token appears in the value of the option (for backwards
compatibility). In the latter case, the newlines are explicit.
If you want to remove the blank line that follows the
<EM>Reply-Leadin</EM> text use a single
_NEWLINE_ token like
<P>
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
<P>
Because of the backwards compatibility problem, it is not possible to
remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
and that will cause the automatic adding of two newlines!
If you want, you may embed newlines in the middle of the text, as well,
producing a multi-line <EM>Reply-Leadin</EM>.
<P>
By default, no attempt is made to localize the date.
If you prefer a localized form you may find that one of the tokens
_PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
If you want more control one of the many other date tokens, such as _DATEISO_,
might be better.
<P>
For the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals"><EM>here</EM></A>.
<P>
In the very unlikely event that you want to include a literal token
in the introduction line you must precede it with a backslash character.
For example,
<P>
<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
<P>
would produce something like
<P>
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
<P>
It is not possible to have a literal backslash followed by an expanded token.
<P>
<DT> <A NAME="reverse-background-color"><EM>reverse-background-color</EM></A>
<DT> <A NAME="reverse-foreground-color"><EM>reverse-foreground-color</EM></A>
<DD> <A HREF="#reverse-color"><EM>Reverse Color</EM></A>.
<P>
<DT> <A NAME="rsh-command"><EM>rsh-command</EM></A>
<DD> Sets the format of the command used to
open a UNIX remote shell connection. The default is
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
provided command. The first is for the command's pathname, the second is
for the host to connect to, the third is for the user to connect as, and
the fourth is for the connection method (typically <CODE>imap</CODE>).
<P>
<DT> <A NAME="rsh-open-timeout"><EM>rsh-open-timeout</EM></A>
<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a UNIX remote shell connection.
The default is 15, the minimum non-zero value is 5,
and the maximum is unlimited. If this is set to zero rsh connections
will be completely disabled.
<P>
<DT> <A NAME="rsh-path"><EM>rsh-path</EM></A>
<DD> Sets the name of the command used to open a UNIX remote shell
connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
<P>
<DT> <A NAME="saved-msg-name"><EM>saved-msg-name-rule</EM></A>
<DD> Determines default folder name when <EM>Sav</EM>ing.
If set to <EM>default-folder</EM> (which is the default setting),
then <EM>Alpine</EM> will offer the folder "saved-messages" (UNIX) or "SAVEMAIL"
(PC) for <EM>Sav</EM>ing messages. The default folder offered in this way
may be changed by using the configuration variable
<A HREF="#def-save"><EM>default-saved-msg-folder</EM></A>.
<P>
If this rule is set to <EM>last-folder-used</EM>, <EM>Alpine</EM> offers to
<EM>Save</EM> to the folder you last successfully <EM>Saved</EM> a message
to (this session).
The first time you <EM>Save</EM> a message in a session,
<EM>Alpine</EM> offers to <EM>Save</EM> the message to the default folder.
<P>
Choosing any of the <EM>by-</EM> options causes <EM>Alpine</EM> to attempt
to get the chosen option's value for the message being <EM>Saved</EM> (or
for the first message being Saved if using an aggregate Save).
For example, if <EM>by-from</EM> is chosen, <EM>Alpine</EM> attempts to
get the value of who the message
came from (i.e. the from address). <EM>Alpine</EM> then attempts to
<EM>Save</EM> the message to a folder matching that value.
If <EM>by-from</EM> is chosen and no value is
obtained, <EM>Alpine</EM> uses <EM>by-sender</EM>.
The opposite is also true.
If <EM>by-recipient</EM> was chosen and the message was posted to a newsgroup,
<EM>Alpine</EM> will use the newsgroup name.
If <EM>by-replyto</EM> is chosen and no value is
obtained, <EM>Alpine</EM> uses <EM>by-from</EM>.
<P>
If any of the "by-realname" options are chosen, <EM>Alpine</EM> will attempt
to use the personal name part of the address instead of the mailbox part.
If any of the "by-nick" options are chosen, the
address is looked up in your address book and if found, the
nickname for that entry is used.
Only simple address book entries are checked, not distribution lists.
Similarly, if any of the
"by-fcc" options are chosen, the fcc from the corresponding
address book entry is used.
If by-realname, or the by-nick or by-fcc lookups result in no value,
then if the chosen option ends with the "then-from",
"then-sender", "then-replyto",
or "then-recip" suffix, <EM>Alpine</EM>
reverts to the same behavior as "by-from",
"by-sender", "by-replyto", or "by-recip"
depending on which option was specified.
If the chosen option doesn't end with one of
the "then-" suffixes, then <EM>Alpine</EM> reverts to the default
folder when no match is found in the address book.
<P>
Here is an example to make some of the options clearer.
If the message is From
<P>
<CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
<P>
and this rule is set to "by-from", then the default folder offered
in the save dialog would be "flint".
<P>
If this rule is set to "by-realname-of-from" then the default would
be "Fred Flintstone".
<P>
If this rule is set to "by-nick-of-from" then <EM>Alpine</EM> will search
for the address "flint@bedrock.org" in your address book.
If an entry is found and it has a nickname associated with it, that nickname
will be offered as the default folder.
If not, the default saved message folder will be offered as the default.
<P>
If this rule is set to "by-fcc-of-from" then <EM>Alpine</EM> will search
for the address "flint@bedrock.org" in your address book.
If an entry is found and it has an Fcc associated with it, that Fcc
will be offered as the default folder.
If not, the default saved message folder will be offered as the default.
<P>
If this rule is set to "by-nick-of-from-then-from" then <EM>Alpine</EM> will search
for the address "flint@bedrock.org" in your address book.
If an entry is found and it has a nickname associated with it, that nickname
will be offered as the default folder.
If it is not found (or has no nickname) then the default offered will be
the same as it would be for the "by-from" rule.
That is, it would be "flint"
<P>
This option is displayed as "Saved Message Name Rule".
<P>
<DT> <A NAME="scroll-margin"><EM>scroll-margin</EM></A>
<DD> This option controls when <EM>Alpine</EM>'s line-by-line scrolling occurs.
Typically, when a selected item is at the top or bottom screen edge
and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are pressed, the
displayed items are scrolled down or up by a single line.
<P>
This option allows you to tell <EM>Alpine</EM> the number of lines from the top and
bottom screen edge that line-by-line scrolling should occur. For example,
setting this value to one (1) will cause <EM>Alpine</EM> to scroll the display
when you move to select an item on the display's top or
bottom edge (instead of moving when you move off the edge of the screen).
<P>
By default, this variable is zero (0), indicating that scrolling happens
when you move up or down to select an item immediately off the display's
top or bottom edge.
<P>
<DT> <A NAME="selectable-item-background-color"><EM>selectable-item-background-color</EM></A>
<DT> <A NAME="selectable-item-foreground-color"><EM>selectable-item-foreground-color</EM></A>
<DD> <A HREF="#selectable-item-color"><EM>Selectable-item Color</EM></A>.
<P>
<DT> <A NAME="sending-filters"><EM>sending-filters</EM></A>
<DD> This option defines a list of text-filtering commands (programs and
scripts) that may be selectively invoked to process a message just before
it is sent. If set, the Composer's <EM>^X Send</EM> command will allow you to
select which filter (or none) to apply to the message before it is sent.
For security reasons, the full path of the filter program must be
specified.
<P>
Sending filters do not work with <EM>PC-Alpine</EM> and sending filters are
not used if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>
Command Modifying Tokens:
<DL>
<DT><EM>_RECIPIENTS_</EM>
<DD>When the command is executed, this token is replaced
with the space delimited list of recipients of the
message being sent.
<DT><EM>_TMPFILE_</EM>
<DD>
When the command is executed, this token is
replaced with the path and name of the temporary
file containing the text to be filtered. <EM>Alpine</EM>
expects the filter to replace this data with the
filter's result.
NOTE: Use of this token implies that the text to
be filtered is not piped into standard input of the
executed command and its standard output is ignored.
<EM>Alpine</EM> restores the tty modes before invoking the
filter in case the filter interacts with the user
via its own standard input and output.
<DT><EM>_RESULTFILE_</EM>
<DD>When the command is executed, this token is
replaced with the path and name of a temporary
file intended to contain a status message from the
filter. <EM>Alpine</EM> displays this in the message status
field.
<DT><EM>_DATAFILE_</EM>
<DD>When the command is executed, this token is replaced
in the command line with the path and name of a
temporary file that <EM>Alpine</EM> creates once per session
and deletes upon exit. The file is intended to be
used by the filter to store state information between
instances of the filter.
<DT><EM>_PREPENDKEY_</EM>
<DD>When the command is executed, this token indicates
that a random number will be passed down the input
stream before the message text. It is not included as a command-line argument.
This number could be used as a session key. It is sent in this way
to improve security. The number is unique to the
current <EM>Alpine</EM> session and is only generated once per
session.
<DT><EM>_INCLUDEALLHDRS_</EM>
<DD>When the command is executed, this token indicates
that the headers of the message will be passed down the input stream
before the message text.
It is not included as a command-line argument.
The filter should, of course, remove the headers before returning control
to <EM>Alpine</EM>.
<DT><EM>_MIMETYPE_</EM>
<DD>When the command is executed, this token is replaced in the
command name with a temporary file name used to accept any new MIME
Content-Type information necessitated by the output of the filter.
Upon the filter's exit, if the file contains new MIME type
information, <EM>Alpine</EM> verifies its format and replaces the outgoing
message's MIME type information with that contained in the file. This
is basically a cheap way of sending something other than Text/Plain.
</DL>
<P>
<DT> <A NAME="sendmail-path"><EM>sendmail-path</EM></A>
<DD> This names the path to an
alternative program, and any necessary arguments, to be used in posting
mail messages. See the section on <A
HREF="background.html#SMTP">SMTP and Sendmail</A> for more details.
<P>
<DT> <A NAME="sig-file"><EM>signature-file</EM></A></A>
<DD> This is the name of a file which will be automatically inserted into
outgoing messages.
It typically contains information such as your
name, email address and organizational affiliation.
<EM>Alpine</EM> adds the
signature into the message as soon as you enter the composer so you
can choose to remove it or edit it on a message by message basis.
Signature file placement in message replies is controlled by the
<A HREF="#sig-at-bot">signature-at-bottom</A>
setting in the feature list.
<P>
This defaults to
<CODE>~/.signature</CODE> on UNIX and <PINERC
directory><CODE>\PINE.SIG</CODE> on a PC. <P>
To create or edit your signature file choose Setup from the Main Menu
and then select S for Signature (Main/Setup/Signature).
This puts you
into the Signature Editor where you can enter a <EM>few</EM> lines of
text containing your identity and affiliation.
<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.
<P>
Instead of storing the data in a local file, the
signature data may be stored remotely in an IMAP folder.
In order to do this,
you must use a remote name for the file.
A remote signature-file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/signature</SAMP></CENTER>
<P>
The syntax used here is the same as the syntax used for remote configuration
files from the command line.
Note that you may not access an existing signature file remotely,
you have to create a new <EM>folder</EM> which contains the signature data.
If the name you use here for the signature file is a remote name, then when
you edit the file from the Setup/Signature command the data will be stored
remotely in the folder.
You aren't required to do anything special to create the folder, it
gets created automatically if you use a remote name.
<P>
Besides regular text, the signature file may also contain
(or a signature program may produce) tokens which
are replaced with text which usually depends on the message you are replying
to or forwarding.
For example, if the signature file contains the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
anywhere in the text, then that token is replaced by the date
the message you are replying to or forwarding was sent.
If it contains
<P>
<CENTER><SAMP>_CURDATE_</SAMP></CENTER>
<P>
that is replaced with the current date.
The first is an example of a token which depends on the message you
are replying to (or forwarding) and the second is an example which
doesn't depend on anything other than the current date.
You have to be a little careful with this facility since tokens which
depend on the message you are replying to or forwarding will be replaced
by nothing in the case where you are composing a new message from scratch.
The use of <A HREF="#role-config"><EM>roles</EM></A> may help you
in this respect.
It allows you to use different signature files in different cases.
<P>
The list of tokens available for use in the signature file is
<A HREF="#index-tokens"><EM>here</EM></A>.
<P>
Instead of, or along with the use of <EM>roles</EM> to give you
different signature files in different situations, there is also
a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
This is explained in detail
<A HREF="#reply-token-conditionals"><EM>here</EM></A>.
This isn't for the faint of heart.
<P>
In the very unlikely event that you want to include a literal token
in the signature you must precede it with a backslash character.
For example,
<P>
<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
<P>
would produce something like
<P>
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
<P>
It is not possible to have a literal backslash followed by an expanded token.
<P>
<DT> <A NAME="signature-background-color"><EM>signature-background-color</EM></A>
<DT> <A NAME="signature-foreground-color"><EM>signature-foreground-color</EM></A>
<DD> <A HREF="#signature-color"><EM>Signature Color</EM></A>.
<P>
<DT> <A NAME="smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
If the option
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A>
is set then this option will have no effect.
<P>
Normally, Public Certificates for use with S/MIME will be stored in the directory
which is the value of this option.
Those certificates will be stored in PEM format, one certificate per file.
The name of the file for the certificate corresponding to
<P>
<CENTER><SAMP>emailaddress</SAMP></CENTER>
<P>
should be
<P>
<CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
<P>
For example, a file for user@example.com would be in the file
<P>
<CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
<P>
in this directory.
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
Typically, the public certificates that you have will come from S/MIME signed
messages that are sent to you.
<EM>Alpine</EM> will extract the public certificate from the signed message and store
it in the certificates directory.
These PEM format public certificates look something like:
<PRE>
-----BEGIN CERTIFICATE-----
MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
...
2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
-----END CERTIFICATE-----
</PRE>
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Public Cert Directory".
<P>
<DT> <A NAME="smime-public-cert-container"><EM>smime-public-cert-container</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>
<P>
This option gives you a way to store certificates remotely on an IMAP server
instead of storing the certificates one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Public Cert Container".
<P>
<DT> <A NAME="smime-private-key-directory"><EM>smime-private-key-directory</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
In order to sign outgoing S/MIME messages you will need a
personal digital ID certificate.
You will usually get such a certificate from a certificate authority such as
Thawte or CAcert.
(In order to encrypt outgoing messages you don't need a personal digital ID, you
need the public certificate of the recipient instead.)
If the option
<A HREF="#smime-private-key-container"><EM>smime-private-key-container</EM></A>
is set then this option will have no effect.
<P>
Normally, Private Keys for use with S/MIME will be stored in the directory
which is the value of this option.
Those certificates will be stored in PEM format, one certificate per file.
The name of the file for the certificate corresponding to your
<P>
<CENTER><SAMP>emailaddress</SAMP></CENTER>
<P>
should be
<P>
<CENTER><SAMP>emailaddress.key</SAMP></CENTER>
<P>
For example, if your address is user@example.com the name of the file would be
<P>
<CENTER><SAMP>user@example.com.key</SAMP></CENTER>
<P>
in this directory.
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
Typically, the private key that you have will come from a Certificate
Authority.
The private key should be stored in a PEM format file that
looks something like:
<PRE>
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
...
oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
-----END RSA PRIVATE KEY-----
</PRE>
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Private Key Directory".
<P>
<DT> <A NAME="smime-private-key-container"><EM>smime-private-key-container</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-private-key-directory"><EM>smime-private-key-directory</EM></A>.
<P>
This option gives you a way to store keys remotely on an IMAP server
instead of storing the keys one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Private Key Container".
<P>
<DT> <A NAME="smime-cacert-directory"><EM>smime-cacert-directory</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
If the option
<A HREF="#smime-cacert-container"><EM>smime-cacert-container</EM></A>
is set then this option will have no effect.
<P>
CACert is a shorthand name for certification authority certificate.
Normally <EM>Alpine</EM> will use the CACerts that are located in the standard system
location for CACerts.
It may be the case that one of your correspondents has a Digital ID which has
been signed by a certificate authority that is not in the regular set of system certificate
authorities.
You may supplement the system list by adding further certificates of your own.
These should be stored in the directory
which is the value of this option.
The certificates will be stored in PEM format, one certificate per file.
The names of the files can be anything ending in ".crt".
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
These PEM format CA certificates look very similar to your public
certificates for particular email addresses
(<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Cert Authority Directory".
<P>
<DT> <A NAME="smime-cacert-container"><EM>smime-cacert-container</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
If this option is set it will be used instead of
<A HREF="#smime-cacert-directory"><EM>smime-cacert-directory</EM></A>.
<P>
This option gives you a way to store certificates remotely on an IMAP server
instead of storing the certificates one per file locally.
In order to do that you just give this option a remote folder name for a folder
which does not yet exist.
The name is similar to the name you might use for a remote configuration file.
A remote folder name might look something like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
<P>
Use the Setup/SMIME screen to modify this variable.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This option is displayed as "S/MIME - Cert Authority Container".
<P>
<DT> <A NAME="smtp-server"><EM>smtp-server</EM></A>
<DD> One or more SMTP servers (host name or IP address) which <EM>Alpine</EM> will
use for outgoing mail. If not set, <EM>Alpine</EM> passes outgoing email to the
<EM>sendmail</EM> program on the local machine. <EM>PC-Alpine</EM> users must have
this variable set in order to send mail as they have no <EM>sendmail</EM>
program.
<P>
Your SMTP server may offer SMTP AUTH authentication.
It may even require it.
If your SMTP server offers SMTP AUTH authentication you may specify a
"user" name parameter to cause <EM>Alpine</EM> to attempt to authenticate.
This parameter requires an associated value,
the username identifier with which to establish the server
connection.
An example might be:
<P>
<CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
<P>
If AUTH authentication is offered by the server, this will cause <EM>Alpine</EM> to
attempt to use it.
If AUTH authentication is not offered by the server, this will cause <EM>Alpine</EM>
to fail sending with an error similar to:
<P>
<CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
<P>
Another type of authentication that is used by some ISPs is called
"POP before SMTP" or "IMAP before SMTP",
which means that you have to authenticate
yourself to the POP or IMAP server by opening a mailbox before you
can send mail.
To do this, you usually only have to open your INBOX.
<P>
You may tell <EM>Alpine</EM> to use the
<A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
port (587) instead of the SMTP port (25) by including the "submit"
parameter
in this option.
At this time "/submit" is simply equivalent to specifying
port 587, though it may imply more than that at some point in the future.
Some ISPs are blocking port 25 in order to reduce the amount of spam
being sent to their users.
You may find that the submit option allows you to get around such a block.
<P>
<CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
<P>
To specify any non-standard port number on the SMTP server you may follow
the hostname with a colon followed by the portnumber.
<P>
<CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
<P>
Normally, when a connection is made to the Smtp-Server <EM>Alpine</EM> will attempt
to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
If that fails then a non-encrypted connection will be attempted instead.
You may specify that a TLS connection is required if you wish.
If you append "/tls" to the name then the connection will fail
instead of falling back to a non-secure connection.
<P>
<CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
<P>
See the
<A HREF="config-notes.html#smtp-server">SMTP Servers</A>
section or the
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A>
section for some more details.
<P>
This option is displayed as "SMTP Server (for sending)".
<P>
<DT> <A NAME="sort-key"><EM>sort-key</EM></A>
<DD> This variable sets up the default Message Index sorting.
The default is to
sort by arrival order (the order the messages arrived in the folder).
It has the same functionality as the
<EM>-sort</EM> command line argument and the <EM>$</EM> command in the
"Folder Index". If a <EM>sort-key</EM> is set, then all folders open during
the session will have that as the default sort order. <P>
<DT> <A NAME="speller"><EM>speller</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
For <EM>PC-Alpine</EM>, you must install the aspell library code that you
may get from
<A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
<P>
This option affects the behavior of the <EM>^T</EM> (spell check)
command in the Composer.
It specifies the program invoked by <EM>^T</EM> in the Composer.
By default, <EM>Alpine</EM> uses the system's "spell" command.
<EM>Alpine</EM> will use the
command defined by this option (if any) instead.
When invoking the spell-checking program,
<EM>Alpine</EM> appends a tempfile name (where the message is passed)
to the command line.
<EM>Alpine</EM> expects the speller to correct the
spelling in that file. When you exit from the speller
program <EM>Alpine</EM> will read the
tmpfile back into the composer.
<P>
For Unix <EM>Alpine</EM> the program <EM>ispell</EM> works well as an
alternate spell checker.
If your Unix system has <EM>ispell</EM> it is probably reasonable to make
it the default speller by configuring it as the default in the
system configuration file, <CODE>/usr/local/lib/pine.conf</CODE>.
<P>
If this option is not set, then the system's <EM>spell</EM> command is used.
The spell command does not work the same as the alternate speller.
It produces a list of misspelled words on its standard output, instead,
and doesn't take a tempfile as an argument.
Don't set this speller option to the standard Unix spell command.
That won't work. If you want to use the standard Unix spell command,
set the speller option to nothing.
<DT> <A NAME="ssh-command"><EM>ssh-command</EM></A>
<DD> Sets the format of the command used to
open a UNIX secure shell connection. The default is
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
provided command. The first is for the command's pathname, the second is
for the host to connect to, the third is for the user to connect as, and
the fourth is for the connection method (typically <CODE>imap</CODE>).
<P>
<DT> <A NAME="ssh-open-timeout"><EM>ssh-open-timeout</EM></A>
<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a UNIX secure shell connection.
The default is 15, the minimum non-zero value is 5,
and the maximum is unlimited. If this is set to zero ssh connections
will be completely disabled.
<P>
<DT> <A NAME="ssh-path"><EM>ssh-path</EM></A>
<DD> Sets the name of the command used to open a UNIX secure shell
connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
<P>
<DT> <A NAME="standard-printer"><EM>standard-printer</EM></A>
<DD> System-wide configuration file only. Specifies a list of commands
for category 2 of the <EM>Setup/Printer</EM> screen, the standard print command
section. This is not used by <EM>PC-Alpine</EM>.
<P>
<DT> <A NAME="status-background-color"><EM>status-background-color</EM></A>
<DT> <A NAME="status-foreground-color"><EM>status-foreground-color</EM></A>
<DD> <A HREF="#status-color"><EM>Status Color</EM></A>.
<P>
<DT> <A NAME="status-message-delay"><EM>status-message-delay</EM></A>
<DD> This option has evolved over time, causing the possible values to be
counter-intuitive.
Read carefully before you set this option.
First we explain what the option does, then there is a longer discussion
following that.
<P>
If this is set to zero, the default value, it has <EM>no</EM> effect.
Positive and negative values serve two similar, but different purposes.
<P>
If it is set to a positive number, it causes the cursor to move to the
status line whenever a status message is printed and pause there for this
many seconds.
It will probably only be useful if the
<A HREF="#show-cursor"><EM>show-cursor</EM></A>
feature is
also turned on.
Setting this option to a positive number can only be used to
<EM>increase</EM> the status message delay.
This may be useful for Braille displays, or other non-traditional displays.
<P>
If it is set to a negative number the interpretation is a bit complicated.
Negative numbers are used to <EM>decrease</EM> the amount of delay <EM>Alpine</EM> uses to
allow you to read important status messages.
Of course, this may cause you to miss some important messages.
If you see a message flash by but miss what it says you can use the
Journal command from the Main menu to read it.
If you set this option to a negative value, the delay will be
no more than one second less than the absolute value
of the value you set.
So if you set it to -1, the delay will be no more than zero seconds, no
delay at all.
If you set it to -2, the delay will be no more than 1 second.
And so on, -3 is 2 seconds, -4 is 3 seconds, ...
If the delay that <EM>Alpine</EM> would have used by default is less than this delay,
then the smaller delay set by <EM>Alpine</EM> will be used.
Setting this option to a negative value can only reduce the amount of
delay, never increase it.
<P>
Here is a more detailed explanation.
Status messages are the messages which show up spontaneously in the
status message line, the third line from the bottom of the screen.
By default, <EM>Alpine</EM> assigns each status message it produces a minimum
display time.
Some status messages have a minimum display time of zero.
You can see an example of such a message by paging up in this help text
until you reach the top of the screen.
If you try to page past the top you will see the message
<P>
<CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
<P>
in the status line.
If there is another more important use of the status message line this message
might be replaced quickly, or it even might not be shown at all.
However, if there is no reason to get rid of the message, it might stay
there for several seconds while you read the help.
An example where it is replaced immediately happens when you page up in
the help text past the top of the screen, but then type the "WhereIs"
command right after paging up.
The message will disappear immediately without causing a delay (unless you
have set this option to a positive value) to allow you to type input for
the "WhereIs" command.
Since it isn't a very important message, <EM>Alpine</EM> has set its minimum display
time to zero seconds.
<P>
Other messages have minimum display times of three or more seconds.
These are usually error messages that <EM>Alpine</EM> thinks you ought to see.
For example, it might be a message about a failed Save or a failed folder open.
It is often the case that this minimum display time won't delay you in
any way because the status message line is not needed for another reason.
However, there are times when <EM>Alpine</EM> has to delay what it is doing in
order to display a status message for the minimum display time.
This happens when a message is being displayed and <EM>Alpine</EM> wants to ask
for input from the keyboard.
For example, when you Save a message you use the status message line.
You get a prompt there asking for the name of the folder to save to.
If there is a status message being displayed that has not
yet displayed for its minimum
time <EM>Alpine</EM> will display that status message surrounded with the characters
> and < to show you that it is delaying.
That might happen, for example, if you tried to save to a folder that
caused an error, then followed that immediately with another Save command.
You might find yourself waiting for a status message like
<P>
<CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
<P>
to finish displaying for three seconds.
If that is something you find happening to you frequently, you may use
negative values of this option to decrease or eliminate that delay, at
the risk of missing the message.
<P>
<DT> <A NAME="stay-open-folders"><EM>stay-open-folders</EM></A>
<DD> This option affects low-level behavior of <EM>Alpine</EM>.
There is no default value for this option.
It is related to the options
<A HREF="#preopen-stayopen-folders">Preopen-Stayopen-Folders</A>,
<A HREF="#max-remote-connections">Max-Remote-Connections</A>,
and <A HREF="#offer-expunge-of-stayopen-folders">offer-expunge-of-Stayopen-Folders</A>.
<P>
Note: changes made to this list take effect the next time you open a
folder in the list.
<P>
This is a list of folders that will be permanently kept open once they
are first opened.
The names in this list may be either the nickname of an Incoming folder
or the full technical specification of a folder.
The folders in this list need not be remote IMAP folders, they could usefully
be local folders, as well.
If a folder in the list is a newsgroup or is not accessed either locally
or via IMAP, then the entry will be ignored.
For example, folders accessed via NNTP or POP3 will not be kept open, since
the way that new mail is found with those protocols involves closing and
reopening the connection.
<P>
Once a Stay Open folder has been opened, new-mail checking will continue
to happen on that folder for the rest of the <EM>Alpine</EM> session.
Your INBOX is always implicitly included in this Stay-Open list and doesn't
need to be added explicitly.
<P>
Another difference that you may notice between a Stay Open folder and a
non-Stay Open folder is which message is selected as the current message
when you enter the folder index.
Normally, the starting position for an incoming folder (which most Stay Open
folders will likely be) is controlled by the
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>.
However, if a folder is a Stay Open folder, when you re-enter the folder
after the first time the current message will be the same as it was when
you left the folder.
An exception is made if you use the TAB command to get to the folder.
In that case, the message number will be incremented by one from what it
was when you left the folder.
<P>
The above special behavior is thought to be useful.
However, it is special and different from what you might at first expect.
The feature
<A HREF="#use-reg-start-rule"><EM>Use-Regular-Startup-Rule-for-Stayopen-Folders</EM></A>
may be used to turn off this special treatment.
<P>
If the message that was current when you left the folder no longer exists,
then the regular startup rule will be used instead.
<P>
This option is displayed as "Stayopen Folders".
<P>
<DT> <A NAME="tcp-open-timeout"><EM>tcp-open-timeout</EM></A>
<DD> Sets the time in seconds that <EM>Alpine</EM> will
attempt to open a network connection. The default is 30, the minimum is 5,
and the maximum is system defined (typically 75). If a connection has not
completed within this many seconds <EM>Alpine</EM> will give up and consider it a
failed connection.
<P>
<DT> <A NAME="tcp-query-timeout"><EM>tcp-query-timeout</EM></A>
<DD> When <EM>Alpine</EM> times out a network read or write it will normally just display
a message saying "Still waiting".
However, if enough time has elapsed since it started waiting it will offer
to let you break the connection.
That amount of time is set by this option, which defaults to 60 seconds,
has a minimum of 5 seconds, and a maximum of 1000 seconds.
<P>
<DT> <A NAME="tcp-read-warning-timeout"><EM>tcp-read-warning-timeout</EM></A>
<DD> Sets the time in seconds that <EM>Alpine</EM> will
wait for a network read before warning you that things are moving slowly
and possibly giving you the option to break the connection.
The default is 15 seconds. The minimum is 5 seconds and the maximumn is
1000 seconds.
<P>
<DT> <A NAME="tcp-write-warning-timeout"><EM>tcp-write-warning-timeout</EM></A>
<DD> Sets the time in seconds that <EM>Alpine</EM> will
wait for a network write before warning you that things are moving slowly
and possibly giving you the option to break the connection.
The default is 0 which means it is unset. If set to a non-zero value, the
minimum is 5 and the maximum is 1000.
<DT> <A NAME="threading-display-style"><EM>threading-display-style</EM></A>
<DD> When a folder is sorted by Threads or OrderedSubject,
this option will affect the MESSAGE INDEX display.
By default, <EM>Alpine</EM> will display the MESSAGE INDEX in the
"show-thread-structure" style if a folder is sorted
by Threads or OrderedSubject.
The possible values are:
<P>
<DL>
<DT><EM>none</EM></DT>
<DD>Regular index display.
The same index line as would be displayed without threading is used.
The only difference will be in the order of the messages.
</DD>
<DT><EM>show-thread-structure</EM></DT>
<DD>Threaded Subjects will be indented and vertical bars and horizontal
lines will be added to make it easier to see the relationships among
the messages in a thread (a conversation).
</DD>
<DT><EM>mutt-like</EM></DT>
<DD>This is the same as the option above except that the Subject
is suppressed (is blank) if it matches the previous Subject in the thread.
The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
Here is an example of what a mutt-like index might look like.
In this example, the first column represents the message number, the
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
is set to "regular-index-with-expanded-threads", and the
<A HREF="#threading-lastreply-character"><EM>Threading-Lastreply-Character</EM></A>
is set to a backslash:
<PRE>
1 Some topic
2 . Subject original message in thread
3 |-> reply to 2
4 . |-> another reply to 2
5 . | \-> reply to 4
6 . | \-> reply to 5
7 | \-> reply to 6
8 |-> another reply to 2
9 . |->New subject another reply to 2 but with a New subject
10 | |-> reply to 9
11 | \-> another reply to 9
12 | \-> reply to 11
13 \-> final reply to 2
14 Next topic
</PRE>
</DD>
<DT><EM>indent-subject-1</EM></DT>
<DD>Threaded Subjects will be indented one space per level of the conversation.
The bars and lines that show up in the show-thread-structure display will
not be there with this style.
</DD>
<DT><EM>indent-subject-2</EM></DT>
<DD>Same as above but indent two spaces per level instead of one space.
</DD>
<DT><EM>indent-from-1</EM></DT>
<DD>Similar to indent-subject-1, except that instead of indenting the
Subject field one space the From field of a thread will be indented one
space per level of the conversation.
</DD>
<DT><EM>indent-from-2</EM></DT>
<DD>Same as above but indent two spaces per level instead of one space.
</DD>
<DT><EM>show-structure-in-from</EM></DT>
<DD>The structure of the thread is illustrated with indenting, vertical bars,
and horizontal lines just like with the show-thread-structure option, but
the From field is used to show the relationships instead of the Subject field.
</DD>
</DL>
<P>
<DT> <A NAME="threading-expanded-character"><EM>threading-expanded-character</EM></A>
<DD> The Threading-Expanded-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
other than <EM>none</EM>.
The value of this option is a single character.
This character is used to indicate that part of a thread has been expanded
and could be collapsed if desired with
the "/" Collapse/Expand command.
By default, the value of this option is a dot (.).
<P>
If this option is set to the Empty Value, then the column (and the following
blank column) will be deleted from the display.
<P>
This option is closely related to the
<A HREF="#threading-indicator-character"><EM>threading-indicator-character</EM></A>
option.
Another similar option which affects the thread display is the
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option.
<DT> <A NAME="threading-index-style"><EM>threading-index-style</EM></A>
<DD> When a folder is sorted by Threads or OrderedSubject,
this option will affect the INDEX displays.
The possible values are:
<P>
<DL>
<DT><EM>regular-index-with-expanded-threads</EM></DT>
<DD>This is the default display.
If the configuration option
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
is set to something other than "none", then this setting
will cause <EM>Alpine</EM> to start off with a MESSAGE INDEX with all of
the threads expanded.
That is, each message will have a line in the MESSAGE INDEX display.
The Collapse/Expand command (/) may be used to manually collapse or
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>).
<P>
This setting affects the display when the folder is first threaded.
The collapsed state may also be re-initialized by re-sorting the folder manually
using the SortIndex command ($).
After re-sorting the threads will once again all be expanded, even if you
have previously collapsed some of them.
<P>
If "threading-display-style" is set to "none", then
the display will be the regular default <EM>Alpine</EM> MESSAGE INDEX, but sorted
in a different order.
</DD>
<DT><EM>regular-index-with-collapsed-threads</EM></DT>
<DD>If the configuration option
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
is set to something other than "none", then this setting
will cause <EM>Alpine</EM> to start out with all of the threads collapsed instead of
starting out with all of the threads expanded.
The Collapse/Expand command (/) may be used to manually collapse or
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>).
<P>
This setting affects the display when the folder is first threaded.
The collapsed state may also be re-initialized by re-sorting the folder manually
using the SortIndex command ($).
After re-sorting the threads will once again all be collapsed, even if you
have previously expanded some of them.
</DD>
<DT><EM>separate-index-screen-always</EM></DT>
<DD>With this setting and the next, you will see an index of threads
instead of an
index of messages, provided you have sorted by Threads or OrderedSubject.
<P>
The THREAD INDEX contains a '*' in the first column if any message in the thread
is marked Important.
If not, it contains a '+' if any message in the thread is to you.
The second column is blank. The third column contains a 'D' if all of the
messages in the thread are deleted.
Otherwise, it contains an 'N' if any of the messages in the thread are New.
<P>
When you view a particular thread from the THREAD INDEX you will be
in the MESSAGE INDEX display
but the index will only contain messages from the thread you are viewing.
</DD>
<DT><EM>separate-index-screen-except-for-single-messages</EM></DT>
<DD>This is very similar to the option above.
When you are in the THREAD INDEX, one of the available commands
is "ViewThd".
With the setting "separate-index-screen-always" (the option above)
when you view a particular thread you will be in the
MESSAGE INDEX display and the index will only contain messages from
the thread you are viewing.
If the thread you are viewing consists of a single message, the MESSAGE INDEX
will be an index with only one message in it.
If you use this "separate-index-screen-except-for-single-messages"
setting instead, then that index which contains a single message
will be skipped and you will go directly from the THREAD INDEX into the
MESSAGE TEXT screen.
</DD>
</DL>
<P>
<DT> <A NAME="threading-indicator-character"><EM>threading-indicator-character</EM></A>
<DD> The Threading-Indicator-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
other than <EM>none</EM> and sorting by Threads or OrderedSubject.
The value of this option is a single character.
This character is used to indicate that part of a thread (a conversation) is
hidden beneath a message.
The message could be expanded
if desired with the "/" Collapse/Expand command.
By default, the value of this option is the greater than sign (>).
<P>
If this option is set to the Empty Value, then the column (and the following
blank column) will be deleted from the display.
<P>
This option is closely related to the
<A HREF="#threading-expanded-character"><EM>threading-expanded-character</EM></A>
option.
Another similar option which affects the thread display is the
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option.
<P>
<DT> <A NAME="threading-lastreply-character"><EM>threading-lastreply-character</EM></A>
<DD>The Threading-Lastreply-Character option has a small effect on the MESSAGE
INDEX display when using a
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A>
of <EM>show-thread-structure</EM>, <EM>mutt-like</EM>, or
<EM>show-structure-in-from</EM>; and sorting by Threads or OrderedSubject.
The value of this option is a single character.
This character is used instead of the vertical line character when there are
no more replies directly to the parent of the current message.
It can be used to "round-off" the bottom of the vertical line
by setting it to a character such as a backslash (\) or
a backquote (`).
The default value of this option is the backslash character (\).
This option may not be set to the Empty Value.
In that case, the default will be used instead.
<P>
This option is displayed as "Threading Last Reply Character".
<P>
<DT> <A NAME="title-background-color"><EM>title-background-color</EM></A>
<DT> <A NAME="title-foreground-color"><EM>title-foreground-color</EM></A>
<DD> <A HREF="#title-color"><EM>Title Color</EM></A>.
<P>
<DT> <A NAME="title-closed-background-color"><EM>title-closed-background-color</EM></A>
<DT> <A NAME="title-closed-foreground-color"><EM>title-closed-foreground-color</EM></A>
<DD> <A HREF="#title-closed-color"><EM>Title-closed Color</EM></A>.
<P>
<DT> <A NAME="titlebar-color-style"><EM>titlebar-color-style</EM></A>
<DD> <A HREF="#titlebar-style"><EM>titlebar-color-style</EM></A>.
<P>
<DT> <A NAME="unknown-character-set"><EM>unknown-character-set</EM></A>
<DD> A text message should either be made up of all US-ASCII characters
or it should contain a charset label which tells the software which
character set encoding to use to interpret the message.
Sometimes a malformed message may be unlabeled but contain non-ascii text.
This message is outside of the standards so any attempt to read it could fail.
When <EM>Alpine</EM> attempts to read such a message it will try to interpret the
text in the character set you specify here.
For example, if you have correspondents who send you unlabeled messages that
are usually made up of characters from the WINDOWS-1251 character set, setting
this unknown-character-set to <CODE>WINDOWS-1251</CODE> will
allow you to read those messages.
Of course, if the unlabeled message is actually in some other character set,
then you may see garbage on your screen.
<P>
In the Setup/Config screen you may choose from a list of all the
character sets <EM>Alpine</EM> knows about by using the "T" ToCharsets command.
<P>
<DT> <A NAME="upload-command"><EM>upload-command</EM></A>
<DD> This option affects the behavior of the Composer's <EM>^R</EM> (Read File)
and <EM>^J</EM> (Attach File, in the header) commands. It
specifies a Unix program name, and any necessary command line arguments,
that <EM>Alpine</EM> can use to transfer files from your personal computer into
messages that you are composing. <P>
<DT> <A NAME="upload-command-prefix"><EM>upload-command-prefix</EM></A>
<DD> This option is used in
conjunction with the <EM>upload-command</EM> option.
It defines text to be written to the terminal emulator (via standard
output) immediately prior to starting the upload command. This is useful for
integrated serial line file transfer agents that permit command passing
(e.g., Kermit's APC method). <P>
<DT> <A NAME="url-viewers"><EM>url-viewers</EM></A>
<DD> List of programs to use to open Internet URLs.
This value affects <EM>Alpine</EM>'s handling of URLs that are found in the text of
messages you read. Normally, only URLs <EM>Alpine</EM> can handle directly are
automatically offered for selection in the "Message Text" screen. When
one or more comma delimited Web browsers capable of deciphering URLs on
their command line are added here, <EM>Alpine</EM> will choose the first available
browser to display URLs it doesn't recognize.
<P>
Additionally, to support various connection methods and browsers, each
entry in this list can begin with the special token
<CODE>_TEST(test-string)_</CODE>.
The <CODE>test-string</CODE> is a shell command that <EM>Alpine</EM>
will run and which must exit with a status of zero for <EM>Alpine</EM> to consider
that browser for use (the other criteria is that the browser must exist
as a full path or a path relative to your home directory).
<P>
Now for an example:
<BLOCKQUOTE>
<CODE>
url-viewers=_TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape,
/usr/local/bin/lynx,
C:\BIN\NETSCAPE.BAT </CODE><BR>
</BLOCKQUOTE>
This example shows that for the first browser in the list to be used the
environment variable <CODE>DISPLAY</CODE> must be defined.
If it is, then the file <CODE>/usr/local/bin/netscape</CODE> must exist.
If either condition is not met, then the file
<CODE>/usr/local/bin/lynx</CODE> must exist.
If it doesn't, then the final path and file must
exist. Note that the last entry is a DOS/Windows path. This is one way
to support <EM>Alpine</EM> running on more than one architecture with the same
configuration file.
<P>
<DT> <A NAME="use-only"><EM>use-only-domain-name</EM></A>
<DD> Can be set to <EM>yes</EM> or <EM>no.</EM> Anything but
<EM>yes</EM> means <EM>no.</EM> If set to <EM>yes</EM> the first label in
the host name will be lopped off to get the domain name and the domain
name will be used for outgoing mail and such. That is, if the host name
is <EM>carson.u.example.edu</EM> and this variable is set to <EM>yes,</EM>
then <EM>u.example.edu</EM> will be used on outgoing mail. Only
meaningful if <A HREF="#user-domain"><EM>user-domain</EM></A> is NOT set. <P>
<DT> <A NAME="user-domain"><EM>user-domain</EM></A>
<DD> Sets the domain or host name for the user, overriding the system host
or domain name. See the <A HREF="config-notes.html#domain"><EM>domain name section</EM></A>.
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>
<DT> <A NAME="user-id"><EM>user-id</EM></A>
<DD> <EM>PC-Alpine</EM> only and personal configuration file only.
Sets the username that is placed on all outgoing
messages. The username is the part of the address that comes before the "@".
The easiest way to change the full From address is with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable.
<P>
<DT> <A NAME="user-input"><EM>user-input-timeout</EM></A>
<DD> If this is set to an integer greater than zero, then this is the number
of <EM>hours</EM> to wait for user input before <EM>Alpine</EM> times out.
If <EM>Alpine</EM> is
in the midst of composing a message or is waiting for user response to
a question, then it will not timeout.
However, if <EM>Alpine</EM> is sitting idle waiting for
the user to tell it what to do next and the user does not give any
input for this many hours, <EM>Alpine</EM> will exit.
No expunging or moving of read
messages will take place.
It will exit similarly to the way it would exit
if it received a hangup signal.
This may be useful for cleaning up unused <EM>Alpine</EM> sessions which have been
forgotten by their owners.
The <EM>Alpine</EM> developers envision system administrators
setting this to a value of several hours (24?) so that it won't surprise
a user who didn't want to be disconnected.
<P>
<DT> <A NAME="viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A>
<DD> This variable holds the optional Header Colors and patterns which
have been defined by the user. This is usually modified by using
the <A HREF="#header-colors"><EM>Header Colors</EM></A> section
of the Setup Color screen.
<P>
<DT> <A NAME="viewer-hdrs"><EM>viewer-hdrs</EM></A>
<DD> You may change the default list of headers that are viewed by listing
the headers you want to view here. If the headers in your <EM>viewer-hdrs</EM>
list are present in the message, then they will be shown. The order of
the headers you list will also be honored. If the special
value <EM>all-except</EM>
is included as the first header in the <EM>viewer-hdrs</EM> list, then all
headers in the message except those in the list will be shown. The values
are all case insensitive.<P>
This option is displayed as "Viewer Headers".
<P>
<DT> <A NAME="viewer-margin-left"><EM>viewer-margin-left</EM></A>
<DD> This variable controls the left-hand vertical margin's width in
<EM>Alpine</EM>'s Message Viewing screen.
Its value is the number of space characters preceding each displayed line.
For consistency with
<A HREF="#viewer-margin-right">Viewer-Margin-Right</A>,
you may specify the column number to start in
(column numbering begins with number 1)
instead of the width of the margin by appending a lower case letter
"c" to the number.
For example, a value of "2c" means to start the text in column two,
which is entirely equivalent to a value of "1", which means to
leave a margin of 1 space.
<P>
The default is a left margin of 0 (zero).
Misconfigurations (for example, negative values or values with starting
left columns greater than the ending right column)
are silently ignored.
If the number of columns for text between the Viewer-Margin-Left and
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used
instead.
<P>
<DT> <A NAME="viewer-margin-right"><EM>viewer-margin-right</EM></A>
<DD> This variable controls the right-hand vertical margin's width in
<EM>Alpine</EM>'s Message Viewing screen.
Its value is the number of space characters following each displayed line.
You may specify the column number to end the text in
(column numbering begins with number 1)
instead of the width of the margin by appending a lower case letter
"c" to the number.
For example, a value of "76c" means to end the text in column 76.
If the screen is 80 characters wide, this is equivalent to a value
of "4", which means to leave a margin of 4 spaces.
However, if you use different size screens at different times, then these
two values are not equivalent.
<P>
The default right margin is 4.
Misconfigurations (for example, negative values or values with starting
left columns greater than the ending right column)
are silently ignored.
If the number of columns for text between the
<A HREF="#viewer-margin-left">Viewer-Margin-Left</A> and
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used
instead.
<P>
<DT> <A NAME="overlap"><EM>viewer-overlap</EM></A>
<DD> This option specifies an aspect of <EM>Alpine</EM>'s Message Viewing screen.
When the space bar is used to page forward in a message, the number of
lines specified by the <EM>viewer-overlap</EM> variable
will be repeated from the
bottom of the screen. That is, if this was set to two lines, then the
bottom two lines of the screen would be repeated on the top of the next
screen. The normal default value is "2". <P>
<DT> <A NAME="window-position"><EM>window-position</EM></A>
<DD> Winsock version of <EM>PC-Alpine</EM> only. Window position in the format:
CxR+X+Yn Where C and R are the window size in characters and X and Y are
the screen position of the top left corner of the window. <P>
</DL>
<HR>
<H2><A NAME="features-conf">Configuration Features</A></H2>
There are several features (options) which may be turned off or on.
The configuration variable
<A HREF="#feat-list"><EM>feature-list</EM></A> is a list of all the
features that are turned on or off.
If the name of a feature is in
the list it will be turned on.
If the name of a feature with the characters
<CODE>no-</CODE> prepended is in the list, it will turn the feature off.
This is useful for overriding system-wide defaults.
This is because, unlike all the other configuration variables,
the <EM>feature-list</EM> is additive.
That is, first the system-wide <EM>feature-list</EM> is read
and then the user's <EM>feature-list</EM> is read. This makes it possible
for the system manager to turn some of the features on by default while
still allowing the user to cancel that default.
For example, if the system manager has
turned on the <EM>allow-talk</EM> feature by default then a user may turn
it back off by including the feature <EM>no-allow-talk</EM> in his or her
personal configuration file. Of course, these details are usually handled
by <EM>Alpine</EM> when the user turns an option on or off from inside the
<EM>Setup/Config</EM> screen.
<P>
System managers should take some care when turning on features by default.
Some of the documentation assumes that all of the features are off by
default, so it could be confusing for a user if some are on by default instead.
Feature names are case-independent.
<P>
Here is an alphabetical list of possible features.
<DL COMPACT>
<DT> <A NAME="allow-from"><EM>allow-changing-from</EM></A>
<DD> Prior to <EM>Pine</EM> 4.00 there was a <EM>compile</EM>-time option called
ALLOW_CHANGING_FROM. That has been replaced by a <EM>runtime</EM> feature.
If this feature is turned on then the From line can be changed just like
all the other header fields that can be changed. See the configuration
variables <A HREF="#cust-hdr"><EM>customized-hdrs</EM></A>
and <A HREF="#def-comp"><EM>default-composer-hdrs</EM></A>
for more information on editing headers.
<P>
The default value for this feature
is ON, so that editing of From headers is allowed
by default.
<P>
<DT> <A NAME="allow-talk"><EM>allow-talk</EM></A>
<DD> Unix <EM>Alpine</EM> only. By default, permission for
others to <EM>talk</EM> to your terminal is turned
off when you are running <EM>Alpine</EM>. When this feature is set, permission is
instead turned on.
<P>
Note: The <EM>talk</EM> program has nothing to do with <EM>Alpine</EM> or email. The
<EM>talk</EM> daemon on your system will
attempt to print a message on your screen
when someone else is trying to contact you. If you wish to see these
messages while you are running <EM>Alpine</EM>, you should enable this feature.
<P>
If you do enable this feature and see a <EM>talk</EM> message, you must
suspend or quit <EM>Alpine</EM> before you can respond.
<P>
<DT> <A NAME="alternate-compose-menu"><EM>alternate-compose-menu</EM></A>
<DD>This feature controls the menu that is displayed when Compose is selected.
If set, a list of options will be presented, with each option representing
the type of composition that could be used. This feature is most useful for
users who want to avoid being prompted with each option separately, or who
want to avoid the checking of remote postponed or form letter folders.
The possible types of composition are:
<P>
New, for starting a new composition. Note that if New is selected and roles
are set, roles are checked for matches and applied according to the setting
of the matching role.
<P>
Interrupted, for continuing an interrupted composition. This option is only
offered if an interrupted message folder is detected.
<P>
Postponed, for continuing postponed compositions. This option is offered
if a postponed-folder is set in the config <EM>REGARDLESS OF</EM> whether or not
the postponed folder actually exists. This option is especially handy
for avoiding having to check for the existence of a remote postponed folder.
<P>
Form, for using form letters. This option is offered if the form-letter-folder
is set in the config, and is not checked for existence for reasons similar
to those explained by the postponed option.
<P>
setRole, for selecting a role to apply to a composition.
<P>
<DT> <A NAME="alternate-role-menu"><EM>alternate-role-menu</EM></A>
<DD> Normally the Role Command allows you to choose
a role and compose a new message using that role.
When this feature is set, the role command will first ask whether you want to
Compose a new message, Forward the current message, Reply to the
current message, or Bounce the current message.
If you are not in the MESSAGE INDEX and are not viewing a message,
then there is no current message and the question will be skipped.
After you have chosen to Compose, Forward, Reply or Bounce you will
then choose the role to be used.
<P>
When Bouncing the "Set From" address is used for the
Resent-From header, the "Set Fcc" value is used for the Fcc
provided that the option
<A HREF="#fcc-on-bounce">"Fcc-On-Bounce"</A> is turned on,
and the "Use SMTP Server" value is used for the SMTP server, if
set.
Other actions of the role are ignored when Bouncing.
<P>
This feature is displayed as "Alternate Role (#) Menu".
<P>
<DT> <A NAME="assume-slow-link"><EM>assume-slow-link</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature affects <EM>Alpine</EM>'s display routines. If set, the normal
inverse-video cursor (used to highlight the current item in a list) will be
replaced by an <EM>arrow</EM> cursor and other screen update optimizations for
low-speed links (e.g. 2400 bps dialup connections) will be activated.
One of the optimizations is that colored index lines (set up with Indexcolor
Rules) will not be colored.
This might be useful if <I>you</I> know you have a slow speed link but for some
reason <EM>Alpine</EM> doesn't know.
<P>
<DT> <A NAME="auto-read-msg"><EM>auto-move-read-msgs</EM></A>
<DD> This feature controls an aspect
of <EM>Alpine</EM>'s behavior upon quitting. If set,
and the <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>
variable is also set, then <EM>Alpine</EM> will
automatically transfer all read messages from the <EM>INBOX</EM> to
the designated folder and mark
them as deleted in the <EM>INBOX</EM>. Messages in the <EM>INBOX</EM> marked
with an <EM>N</EM> (meaning New, or unseen) are not affected.
<P>
This feature is displayed as "Auto Move Read Messages".
<P>
<DT> <A NAME="auto-open-next-unread"><EM>auto-open-next-unread</EM></A>
<DD> This feature controls the behavior of the TAB key when traversing folders
in the optional <A HREF="#inc-fold"><EM>incoming-folders</EM></A>
collection or in optional <A HREF="#news-coll"><EM>news-collections</EM></A>.
<P>
When the TAB (Next New) key is pressed, and there are no more unseen
messages in the current (incoming message or news) folder, <EM>Alpine</EM> will
search the list of folders in the current collection for one containing
New or Recent (new since the last time the folder was opened) messages.
This behavior may be modified slightly with the
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A>
feature which causes <EM>Alpine</EM> to look for Unseen messages instead of Recent
messages.
By default, when such a folder is found,
<EM>Alpine</EM> will ask whether you wish to
open the folder.
If this feature is set, <EM>Alpine</EM> will automatically open the
folder without prompting.
<P>
<DT> <A NAME="auto-unselect-after-apply"><EM>auto-unselect-after-apply</EM></A>
<DD> This feature affects the behavior of the Apply command. If set,
the Apply command will do the operation you specify, but then will
implicitly do an "UnSelect All", so that you will automatically be back in
the normal Index view after the Apply.
<P>
<DT> <A NAME="auto-unzoom-after-apply"><EM>auto-unzoom-after-apply</EM></A>
<DD> If set, and if
you are currently looking at a Zoomed Index view of selected messages,
the <EM>Apply</EM> command will do the operation you specify, but then will
implicitly do an <EM>UnZoom</EM>, so that you will automatically be back in
the normal Index view after the <EM>Apply</EM>.
This feature is set by default.
<P>
<DT> <A NAME="auto-zoom-after-select"><EM>auto-zoom-after-select</EM></A>
<DD> If set, the <EM>; select</EM> command will automatically
perform a <EM>Zoom</EM> after the <EM>select</EM> is complete.
This feature is set by default.
<P>
<DT> <A NAME="busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A>
<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that
something is happening with a small animated display in the status
message line near the bottom of the screen.
Setting this feature will cause that animation to be the same
each time instead of having <EM>Alpine</EM> choose a random animation.
You may turn the animation off altogether by setting the
<A HREF="#busy-cue-rate"><EM>busy-cue-rate</EM></A>
option to zero.
<P>
<DT> <A NAME="check-newmail-when-quitting"><EM>check-newmail-when-quitting</EM></A>
<DD> If set, <EM>Alpine</EM> will check for new mail after you give the
Quit command.
If new mail has arrived since the previous check, you will be notified
and given the choice of quitting or not quitting.
<P>
<DT> <A NAME="combined-addrbook-display"><EM>combined-addrbook-display</EM></A>
<DD> This feature affects the address book display screens.
Normally, expanding an address book from the ADDRESS BOOK LIST screen
will cause the remaining address books and directory servers to disappear
from the screen, leaving only the entries of the expanded address book.
If this feature is set, then the other address books will remain on the screen,
so that all of the address books can be present at once.
<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the entries in the
current address book, not all of the entries in all of the address books.
The WhereIs command will change a little.
It will search through all of the text on the screen plus all of the entries
from expanded address books.
<P>
When this feature is set, the setting of the feature
<A HREF="#expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A>
has an effect.
<P>
This feature is displayed as "Combined Addressbook Display".
<P>
<DT> <A NAME="combined-folder-display"><EM>combined-folder-display</EM></A>
<DD> This feature affects the folder list display screens.
Normally, each folder list is viewed within its collection only. This
command allows folder lists to be viewed within a single screen that
combines the contents of all collections.
<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
current collection, not all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.
<P>
When this feature is set, the setting of the feature
<A HREF="#expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A>
has an effect.
<P>
<DT> <A NAME="combined-subdirectory-display"><EM>combined-subdirectory-display</EM></A>
<DD> This feature affects the Folder List screen when
the
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A>
feature is enabled. Normally, selecting a directory from the Folder
List takes you into a new screen displaying only the contents of
that directory.
<P>
Enabling this feature will cause the contents of the selected
directory to be
displayed within the boundaries of the
<A HREF="background.html#collections"><EM>Collection</EM></A>
it is a part of. All previously displayed collections will remain
in the screen.
<P>
The way that commands work won't be changed.
For example, the Select All command will select all of the folders in the
directory, as opposed to all of the entries in all of the collections.
The WhereIs command will change a little.
It will search through all of the folders in the current collection as well
as all the folder in any other expanded collection.
<P>
<DT> <A NAME="compose-cancel-confirm-uses-yes"><EM>compose-cancel-confirm-uses-yes</EM></A>
<DD> This feature affects what happens when you type ^C to cancel a composition.
By default, if you attempt to cancel a composition by typing ^C, you will be
asked to confirm the cancellation by typing a "C"
for <EM>C</EM>onfirm.
It logically ought to be a "Y" for <EM>Y</EM>es, but that is
risky because the "^C Y" needed to cancel a message
is close (on the keyboard) to the "^X Y" needed to send a message.
<P>
If this feature is set the confirmation asked for
will be a "<EM>Y</EM>es"
instead of a "<EM>C</EM>onfirm" response.
<P>
<DT> <A NAME="compose-cut-from-cursor"><EM>compose-cut-from-cursor</EM></A>
<DD> If set, the <EM>^K</EM> command in the composer will cut from the
current cursor position to the end of the line,
rather than cutting the entire line.
<P>
This feature is displayed as "Ctrl-K Cuts From Cursor".
<P>
<DT> <A NAME="compose-maps-delete-key-to-ctrl-d"><EM>compose-maps-delete-key-to-ctrl-d</EM></A>
<DD> If set, Delete will be equivalent to ^D, and delete
the current character. Normally <EM>Alpine</EM> defines the Delete key
to be equivalent to ^H, which deletes the <EM>previous</EM>
character.
<P>
This feature is displayed as "Delete Key Maps to Ctrl-D".
<P>
<DT> <A NAME="compose-rejects-unqualified-addrs"><EM>compose-rejects-unqualified-addrs</EM></A>
<DD> If set, unqualified names entered as addresses will be treated as errors
unless they match an addressbook nickname or are looked up successfully
on an LDAP server. <EM>Alpine</EM> will not attempt to turn
them into complete addresses by adding your local domain (which <EM>Alpine</EM> normally
does by default).
<P>
A complete (fully-qualified) address is one containing a username
followed by an <EM>@</EM> symbol, followed by a host or domain name (e.g.
<EM>jsmith@example.com</EM>). An unqualified name is one without the
<EM>@</EM> symbol
and host or domain name (e.g. <EM>jsmith</EM>).
<P>
This feature is displayed as "Compose Rejects Unqualified Addresses".
<P>
<DT> <A NAME="compose-send-offers-first-filter"><EM>compose-send-offers-first-filter</EM></A>
<DD> If you have <A HREF="#sending-filters"><EM>sending-filters</EM></A>
configured, setting this feature will cause the first filter in the
<EM>sending-filters</EM> list to be offered as the default
instead of <EM>unfiltered</EM>, the usual default.
<P>
<DT> <A NAME="compose-sets-newsgroup-without-confirm"><EM>compose-sets-newsgroup-without-confirm</EM></A>
<DD> If you enter the
composer while reading a newsgroup, you will normally be prompted to
determine whether you intend the new message to be posted to the current
newsgroup or not. If this feature is set, <EM>Alpine</EM> will not prompt you
in this situation, and will assume that you do indeed wish to post
to the newsgroup you are reading.
<P>
This feature is displayed as "Compose Sets Newsgroup Without Confirming".
<P>
<DT> <A NAME="confirm-role-even-for-default"><EM>confirm-role-even-for-default</EM></A>
<DD> If you have roles, when you Reply to or Forward a message, or Compose
a new message, <EM>Alpine</EM>
will search through your roles for one which matches.
Normally, if no matches are found you will be placed into the composer
with no opportunity to select a role.
If this feature is set, then you will be asked to confirm that you don't
want a role.
This will give you the opportunity to select a role (with the ^T command).
If you confirm no role with a Return, you will be placed in
the composer with no role.
You may also confirm with either an "N" or a "Y".
These behave the same as if you pressed the Return.
(The "N" and "Y" answers are available because they
match what you might type if there was a role match.)
<P>
If you are using the alternate form of the Compose command called
"Role", then all of your roles will be available to you,
independent of the value of this feature and of the values set for all of
Reply Use, Forward Use, and Compose Use.
<P>
<DT> <A NAME="continue-tab-without-confirm"><EM>continue-tab-without-confirm</EM></A>
<DD> Normally, when you use the TAB NextNew
command and there is a problem checking a folder, you are asked
whether you want to continue with the search in the following folder or not.
This gives you a chance to stop the NextNew processing.
<P>
If this feature is set you will not be asked.
It will be assumed that you want to continue.
<P>
This feature is displayed as "Continue NextNew Without Confirming".
<P>
<DT> <A NAME="convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>
<DD> Normally, the message dates that you see in the
MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
For example, if a message was sent to you from a few timezones to the east
it might appear that it was sent from the future;
or if it was sent from somewhere to the west it might appear
as if it is from yesterday even though it was sent only a few minutes ago.
If this feature is set an attempt will be made to convert the dates
to your local timezone to be displayed.
<P>
Note that this does not affect the results of Select by Date or of
anything else other than these displayed dates.
When viewing the message you may look at the original unconverted value of the Date
header by using the HdrMode Command.
<P>
<DT> <A NAME="copy-to-to-from"><EM>copy-to-address-to-from-if-it-is-us</EM></A>
<DD> This feature affects the From address used when Replying to a message.
It is probably only useful if you have some
<A HREF="#alt-addresses">alt-addresses</A>
defined.
When enabled, it checks to see if any of the addresses in the To or Cc
fields of the message you are replying to is one of your addresses.
If it is, and there is only one of them, then that address is used as
the From address in the message you are composing.
In other words, you will be using a From address that is the same
as the To address that was used to get the mail to you in the first place.
<P>
If a role is being used and it has a From address defined, that From address will
be used rather than the one derived from this feature.
<P>
<DT> <A NAME="delete-skips-deleted"><EM>delete-skips-deleted</EM></A>
<DD> If set, this
feature will cause the <EM>Delete</EM> command to
advance past other messages that
are marked deleted. In other words, pressing <EM>D</EM> will both mark the
current message deleted and advance to the next message that is not marked
deleted.
This feature is set by default.
<P>
<DT> <A NAME="disable-config-cmd"><EM>disable-config-cmd</EM></A>
<DD> If set, the configuration
screen <EM>Setup/Config</EM> will not be available at all.
<P>
<DT> <A NAME="disable-save-input-history"><EM>disable-save-input-history</EM></A>
<DD> Many of the prompts that ask for input in the status line near the
bottom of the screen will respond to Up Arrow and Down Arrow
with the history of previous entries.
For example, in the MESSAGE INDEX screen when you use the WhereIs
command the text you entered will be remembered and can be recalled
by using the Up Arrow key.
Another example, when saving a message the folders saved to will
be remembered and can be recalled using the arrow keys.
<P>
In the Save prompt, some users prefer that the Up and Down arrow keys
be used for the Previous Collection and Next Collection commands
instead of for a history of previous saves.
If this option is set the Up and Down arrow keys will become synonyms for the
Previous Collection and Next Collection (^P and ^N) commands in the
prompt for the name of a folder to Save to or in the prompt for the
name of a folder to GoTo.
When this feature is not set (the default), ^P and ^N will change the
collection and the arrow keys will show the history.
<P>
<DT> <A NAME="disable-kblock"><EM>disable-keyboard-lock-cmd</EM></A>
<DD> In the Main <EM>Alpine</EM> menu there is a Keyboard locking
command (<EM>KBLock</EM>). If this feature is set, that command won't be
available to the user.
<P>
<DT> <A NAME="disable-keymenu"><EM>disable-keymenu</EM></A>
<DD> If set, the command key menu that normally appears on the
bottom two lines of the screen will not usually be there. Asking for
help with <EM>^G</EM> or <EM>?</EM> will cause the key menu to
appear instead of causing the help message to come up. If you want to
actually see the help text,
another <EM>^G</EM> or <EM>?</EM> will show it to you.
After the key menu has popped
up with the help key it will remain there for an <EM>O Other</EM> command but
will disappear if any other command is typed.
<P>
<DT> <A NAME="disable-password-caching"><EM>disable-password-caching</EM></A>
<P>
<DD> Normally, loginname/password combinations are cached in <EM>Alpine</EM>
so that the user does not have to enter the same password more than once
in a session.
A disadvantage to this approach is that the password must be stored in
the memory image of the running <EM>Alpine</EM> in order that it can be reused.
In the event that <EM>Alpine</EM> crashes and produces a core dump, and that core
dump is readable by others, the loginname and password could possibly be read
from the core dump.
<P>
If this feature is set, then the passwords will not be cached and
the user will have to retype the password whenever <EM>Alpine</EM> needs it.
Even with this feature set there is still some chance that the core
file will contain a password, so care should be taken to make the
core files unreadable.
<P>
NOTE: If PASSFILE caching is enabled, this does not disable it.
That is a separate and independent feature.
<P>
<DT> <A NAME="disable-password-cmd"><EM>disable-password-cmd</EM></A>
<DD> If set the <EM>Newpassword</EM> command usually available under the
<EM>Setup</EM> command will not be available.
<P>
<DT> <A NAME="disable-pipes-in-sigs"><EM>disable-pipes-in-sigs</EM></A>
<DD> If set it will be an error to append a vertical bar (|) to the name
of a signature file.
Appending a vertical bar normally causes the signature file to be executed
to produce the signature.
<P>
<DT> <A NAME="disable-pipes-in-templates"><EM>disable-pipes-in-templates</EM></A>
<DD> If set it will be an error to append a vertical bar (|) to the name
of a template file.
Appending a vertical bar normally causes the signature file to be executed
to produce the signature.
<P>
<DT> <A NAME="disable-regex"><EM>disable-regular-expression-matching-for-alternate-addresses</EM></A>
<DD> Normally, the
<A HREF="#alt-addresses">alt-addresses</A>
option is interpreted as a regular expression.
One type of address that might cause trouble is an address that
contains a plus sign.
If you want to have an address with a plus as one of your
alternate addresses
and you don't want to use regular expressions, then setting this
feature will cause <EM>Alpine</EM> to treat the addresses you list literally instead.
<P>
<DT> <A NAME="disable-roles-setup-cmd"><EM>disable-roles-setup-cmd</EM></A>
<DD> If set the <EM>Roles</EM> command usually available under the
<EM>Setup</EM> command will not be available.
<P>
<DT> <A NAME="disable-roles-sig-edit"><EM>disable-roles-sig-edit</EM></A>
<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow
editing of signature files with the F subcommand.
<P>
<DT> <A NAME="disable-roles-template-edit"><EM>disable-roles-template-edit</EM></A>
<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow
editing of template files with the F subcommand.
<P>
<DT> <A NAME="disable-sender"><EM>disable-sender</EM></A>
<DD> If set, <EM>Alpine</EM> will not generate a "Sender:" or "X-X-Sender" header.
This may be desirable on a system which is virtually hosting many domains,
and the sysadmin has other methods available for tracking a message to
its originator.
<P>
This feature is displayed as "Do Not Generate Sender Header".
<P>
<DT> <A NAME="disable-setlocale-collate"><EM>disable-setlocale-collate</EM></A>
<DD> This is a hard to understand feature that should only be used in rare cases.
Normally, the C function call
<P>
<CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
<P>
is used by <EM>Alpine</EM>.
If you want to try turning it off,
setting this feature will turn it off.
This part of the locale has to do with the sort order
of characters in your locale.
<P>
<DT> <A NAME="disable-shared-namespaces"><EM>disable-shared-namespaces</EM></A>
<DD> If this hidden feature is set
the automatic search for namespaces "ftp",
"imapshared", and "imappublic" by the underlying library
will be disabled.
The reason this feature exists is because there are some implementations
of system password lookup routines which are very slow when presented with
a long loginname which does not exist.
This feature could be set to prevent the delay at startup time when the
names above are searched for in the password file.
<P>
<DT> <A NAME="disable-signature-edit-cmd"><EM>disable-signature-edit-cmd</EM></A>
<DD> If set the <EM>Signature</EM> editing command usually available under the
<EM>Setup</EM> command will not be available.
<P>
<DT> <A NAME="disable-take-fullname"><EM>disable-take-fullname-in-addresses</EM></A>
<DD> Normally, when TakeAddr is used to copy an address or addresses
from a message into an address book entry, <EM>Alpine</EM> will try to preserve
the full name associated with each address in the list of addresses.
The reason for this is so that if the entry is a list or later becomes a
list, then information about the individual addresses in the list
is preserved.
If you would rather just have the simple addresses in the list of addresses,
set this feature. For example, with the default setting you might
see something like this in the ADDRESS BOOK editor after you type TakeAddr
<P>
<PRE>
Nickname : nick
Fullname : Bedrock Elders
Fcc :
Comment :
Addresses : Fred Flintstone <flint@bedrock.org>,
Barney Rubble <rubble@bedrock.org>
</PRE>
<P>
but with this feature set it would look like
<P>
<PRE>
Nickname : nick
Fullname : Bedrock Elders
Fcc :
Comment :
Addresses : flint@bedrock.org,
rubble@bedrock.org
</PRE>
<P>
instead. Note the difference in the Addresses field.
<P>
<DT> <A NAME="disable-take-last-comma-first"><EM>disable-take-last-comma-first</EM></A>
<DD> Normally, when <EM>TakeAddr</EM> is used to copy an address
from a message into an address book, <EM>Alpine</EM> will attempt to rewrite the
full name of the address in the form:
<BLOCKQUOTE>
Last, First <BR>
</BLOCKQUOTE>
instead of
<BLOCKQUOTE>
First Last <BR>
</BLOCKQUOTE>
It does this because many people find it useful to sort by Last name instead
of First name. If this feature is set, then the <EM>TakeAddr</EM> command will
not attempt to reverse the name in this manner.
<P>
<DT> <A NAME="disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature affects <EM>Alpine</EM>'s behavior when using
<A HREF="#display-filters"><EM>Display-Filters</EM></A>.
Normally, before the display filter is run, the terminal mode is reset
to what it was before you started <EM>Alpine</EM>.
This may be necessary if the filter requires the use of the terminal.
For example, it may need to interact with you.
If you set this feature, then the terminal mode will not be reset.
One thing that turning on this feature should fix is the coloring of
quoted text in the message view, which
breaks because the terminal reset resets the color state of the terminal
(<A HREF="#color-config">Color Configuration</A>).
<P>
<DT> <A NAME="downgrade-multipart-to-text"><EM>downgrade-multipart-to-text</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail. Internet
standards require <EM>Alpine</EM> to translate all non-ASCII characters in
messages that it sends using MIME encoding. This encoding can be
ostensibly broken for recipients if any agent between <EM>Alpine</EM> and the
recipient, such as an email list expander, appends text to the
message, such as list information or advertising. When sending such
messages <EM>Alpine</EM> attempts to protect such encoding by placing extra
MIME boundaries around the message text.
<P>
These extra boundaries are invisible to recipients that
use MIME-aware email programs (the vast majority). However, if
you correspond with users of email programs that are not MIME-aware,
or do not handle the extra boundaries gracefully, you can
use this feature to prevent <EM>Alpine</EM> from including the extra
MIME information. Of course, it will increase the likelihood
that non-ASCII text you send may appear corrupt to the recipient.
<P>
<DT> <A NAME="enable-8bit-esmtp-negotiation"><EM>enable-8bit-esmtp-negotiation</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail.
By default, this feature is set.
Internet standards
require that all electronic mail messages traversing the global Internet
consist of 7bit ASCII characters unless a pair of cooperating mail
transfer agents explicitly agree to allow 8bit messages. In general,
then, exchanging messages in non-ASCII characters requires MIME encoding.
<P>
However, there are now Internet standards that allow for unencoded 8bit
exchange of messages between cooperating systems. When this feature is set
<EM>Alpine</EM> will try to negotiate unencoded 8bit transmission during the
sending process. Should the negotiation fail, <EM>Alpine</EM> will fall back to its
ordinary encoding rules.
<P>
Note, this feature relies on your system's mail transport agent or
configured <A HREF="#smtp-server"><EM>smtp-server</EM></A>
having the negotiation mechanism introduced in
"Extended SMTP" (ESMTP) and the specific extension called <EM>8BITMIME</EM>.
<P>
<DT> <A NAME="enable-8bit-nntp-posting"><EM>enable-8bit-nntp-posting</EM></A>
<DD> The Internet standard for exchanging USENET news messages (RFC-1036)
specifies that USENET messages should conform to Internet mail standards
and contain only 7bit characters, but much of the news transport software
in use today is capable of successfully sending messages containing 8bit
characters. Hence, many people believe that it is appropriate to send 8bit
news messages without any MIME encoding.
<P>
Moreover, there is no Internet standard for explicitly negotiating 8bit
transfer, as there is for Internet email. Therefore, <EM>Alpine</EM> provides the
option of posting unencoded 8bit news messages, though not as the default.
Setting this feature will turn OFF <EM>Alpine</EM>'s MIME encoding of newsgroup
postings that contain 8bit characters.
<P>
Note, articles may cross a path or pass through news transport software
that is unsafe or even hostile to 8bit characters. At best this will only
cause the posting to become garbled. The safest way to transmit 8bit
characters is to leave <EM>Alpine</EM>'s MIME encoding turned on, but recipients
who lack MIME-aware tools are often annoyed when they receive MIME-encoded
messages.
<P>
<DT> <A NAME="enable-aggregate-command-set"><EM>enable-aggregate-command-set</EM></A>
<DD> When this feature is set you may use the commands and subcommands that relate to
performing operations on more than one message at a time.
We call these "aggregate operations".
In particular, the <EM>; Select</EM>, <EM>A Apply</EM>, and
<EM>Z Zoom</EM> commands are enabled by this feature.
<EM>Select</EM> is used to <EM>tag</EM> one
or more messages meeting the specified criteria. <EM>Apply</EM> can then be used
to apply any message command to all of the selected/tagged messages.
Further, the <EM>Zoom</EM> command allows you to toggle the "Folder Index" view
between just those Selected and all messages in the folder.
<P>
This feature also enables the <EM>^X</EM> subcommand in
the "Folder Index" <EM>WhereIs</EM>
command which causes
all messages matching the <EM>WhereIs</EM> argument to become
selected.
<P>
You may also use aggregate operations in the address book screens where
you are operating on address book entries instead of on messages.
<P>
<DT> <A NAME="enable-alt-ed"><EM>enable-alternate-editor-cmd</EM></A>
<DD> If this feature is set (the default), and the <A HREF="#editor"><EM>editor</EM></A>
variable is not set, entering
the <EM>^_</EM> (Control-underscore) key while
composing a message will prompt you
for the name of the editor you would like to use.
<P>
If the environment variable <CODE>$EDITOR</CODE> is set,
this value will be offered as a default.
If the <EM>editor</EM> variable is set, the <EM>^_</EM> key will activate
the specified editor without prompting, in which case it is not necessary to
set the <EM>enable-alternate-editor-cmd</EM> feature.
This feature is not available in <EM>PC-Alpine</EM>.
<P>
This feature is displayed as "Enable Alternate Editor Command".
<P>
<DT> <A NAME="enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A>
<DD> If this feature and the <A HREF="#editor"><EM>editor</EM></A>
variable are both set, <EM>Alpine</EM> will
automatically activate the specified editor when the cursor is moved from
the header of the message being composed into the message text. For
replies, the alternate editor will be activated immediately. If this
feature is set but the <EM>editor</EM> variable is not set,
then <EM>Alpine</EM> will
automatically ask for the name of an alternate editor when the cursor
is moved out of the headers, or if a reply is being done.
This feature is not available in <EM>PC-Alpine</EM>.
<P>
<DT> <A NAME="enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A>
<DD> This feature controls the behavior of the left and right arrow keys.
If set, the left and right arrow keys will operate like the usual
navigation keys <EM><</EM> and <EM>></EM>.
This feature is set by default.
<P>
If you set this feature, and do not like the changed behavior of the up/down
arrow keys when navigating through the FOLDER LIST screen --
<B>first</B> from column to column, if more than one folder is
displayed per row,
and <B>then</B> from row to row -- you may either also wish to set the feature
<A HREF="#enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A>,
<A HREF="#single-column-folder-list"><EM>single-column-folder-list</EM></A>,
or use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
folders in each column.
<P>
<DT> <A NAME="enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A>
<DD> This feature controls the behavior of the left and right arrow keys
in the FOLDER LIST screen when the
<A HREF="#enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A>
feature is set.
This feature is set by default.
<P>
When this feature is set, the left and right
arrow keys in the FOLDER LIST screen
move the highlight bar to the left or right, and the up and
down arrows move it up or down.
<P>
When the "Enable-Arrow-Navigation" feature is set and this
feature is not set;
the left and right arrow keys in the Folder List screen strictly
track the commands bound to the '<' and '>' keys, and the up
and down arrow keys move the highlight bar to the previous and next
folder or directory name.
<P>
<DT> <A NAME="enable-background-sending"><EM>enable-background-sending</EM></A>
<DD> If set, this
feature enables a subcommand in the composer's <EM>Send?</EM> confirmation
prompt. The subcommand allows you to tell <EM>Alpine</EM> to handle the actual
posting in the background. While this feature usually allows posting
to appear to happen very fast, it has no affect on the actual delivery
time it takes a message to arrive at its destination.
<P>
This feature isn't supported on all systems. All DOS and Windows,
as well as several Unix ports, do not recognize this feature.
It is not possible to use background sending if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>
Error handling is significantly different when this feature is
enabled. Any message posting failure results in the message
being appended to your <EM>Interrupted</EM> mail folder. When you
type the <EM>Compose</EM> command, <EM>Alpine</EM> will notice this folder and
offer to extract any messages contained. Upon continuing a
failed message, <EM>Alpine</EM> will display the nature of the failure
in the status message line.
<P>
Under extreme conditions, it is possible for message data to
get lost. Do not enable this feature if you typically run close
to any sort of disk-space limits or quotas.
<P>
<DT> <A NAME="enable-bounce-cmd"><EM>enable-bounce-cmd</EM></A>
<DD> Setting this feature enables the <EM>B Bounce</EM> command,
which will prompt
for an address and <EM>remail</EM> the message to the new recipient.
This command
is used to re-direct messages that you have received in error, or need to
be redirected for some other reason (e.g. list moderation). The final
recipient will see a header indicating that you have Resent the msg, but
the message's From: header will show the original author of the message,
and replies to it will go back to that author, and not to you.
<P>
This feature is displayed as "Enable Bounce Command".
<P>
<DT> <A NAME="enable-cruise-mode"><EM>enable-cruise-mode</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when you hit the "Space Bar" at
the end of a displayed message. Typically, <EM>Alpine</EM> complains that the end
of the text has already been reached. Setting this feature causes such
keystrokes to be interpreted as if the <EM>Tab</EM> key had been hit, thus
taking you to the next <EM>interesting</EM> message, or scanning ahead to the
next incoming folder with <EM>interesting</EM> messages.
<P>
<DT> <A NAME="enable-cruise-mode-delete"><EM>enable-cruise-mode-delete</EM></A>
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s <EM>enable-cruise-mode</EM>
feature. Setting this feature causes <EM>Alpine</EM> to implicitly delete read
messages when it moves on to display the next <EM>interesting</EM> message.
<P>
NOTE: Beware when enabling this feature <B>and</B> the
<A HREF="#expunge-wo-confirm"><EM>expunge-without-confirm</EM></A> feature.
<P>
This feature is displayed as "Enable Cruise Mode With Deleting".
<P>
<DT> <A NAME="enable-delivery-status-notification"><EM>enable-delivery-status-notification</EM></A>
<DD> If set, this
feature enables a subcommand in the composer's "Send?" confirmation
prompt. The subcommand allows you to tell <EM>Alpine</EM> to request the type of
Delivery Status Notification (DSN) which you would like. Most users will
be happy with the default, and need not enable this feature. See the online
help for more details.
<P>
It is not possible to use delivery status notifications if the feature
<A HREF="#send-without-confirm">send-without-confirm</A> is set.
<P>
Note that this is not a method to request <EM>READ</EM> receipts, which tells
the sender when the receiver has read the message. In this case we're talking
about notification of delivery to the mailbox, not notification that the
message has been seen.
<P>
<DT> <A NAME="enable-dot-files"><EM>enable-dot-files</EM></A>
<DD> If set, files beginning with dot (".") will be
visible in the file browser. For example, you'll be able to select them
when using the browser to add an attachment to a message.
<P>
<DT> <A NAME="enable-dot-folders"><EM>enable-dot-folders</EM></A>
<DD> If set, folders beginning with dot (".") may be added
and viewed.
This feature is displayed as "Enable Hidden Folders".
<P>
<DT> <A NAME="enable-exit-via-lessthan-command"><EM>enable-exit-via-lessthan-command</EM></A>
<DD> If set, then on screens where there is an <EM>Exit</EM> command
but no <EM><</EM> command, the <EM><</EM> key will perform
the same function as the <EM>Exit</EM> command.
This feature is set by default.
<P>
<DT> <A NAME="enable-fast-recent-test"><EM>enable-fast-recent-test</EM></A>
<DD> This feature controls the behavior of the TAB key when traversing folders
in the optional
<A HREF="#enable-incoming-folders">Incoming-Folders</A>
collection or in optional News-Collections.
<P>
When the TAB
(NextNew)
key is pressed, the default behavior is to
explicitly examine the status of the folder for the number of recent
messages (messages delivered since the last time it was viewed).
Depending on the size and number of messages in the folder, this test
can be time consuming.
<P>
Enabling this feature will cause <EM>Alpine</EM> to only test for the existence of
any recent messages rather than to obtain the count. This is much faster
in many cases. The downside is that you're not given the number of recent
messages when prompted to view the next folder.
If the feature
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A>
is turned on, then the present feature will have no effect.
<P>
<DT> <A NAME="enable-flag-cmd"><EM>enable-flag-cmd</EM></A>
<DD> Setting this feature enables the <EM>* Flag</EM> command,
which allows you to
manipulate the status flags associated with a message.
By default, <EM>Flag</EM>
will set the <EM>Important</EM> flag, which results in an asterisk being
displayed in column one of the "Folder Index" for such messages.
<P>
This feature is displayed as "Enable Flag Command".
<P>
<DT> <A NAME="enable-flag-screen-implicitly"><EM>enable-flag-screen-implicitly</EM></A>
<DD> This feature modifies the behavior of the <EM>* Flag</EM> command
(provided it too is enabled).
By default, when the <EM>* Flag</EM> command is selected,
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the
option of entering the detailed flag manipulation screen via the <EM>^T</EM>
key. Enabling this feature causes <EM>Alpine</EM> to immediately enter the detailed
flag screen rather than first offer the simple prompt.
The
<A HREF="#enable-flag-screen-keyword-shortcut">Enable-Flag-Screen-Keyword-Shortcut</A> option offers a slightly different way of setting keywords.
<P>
<DT> <A NAME="enable-flag-screen-keyword-shortcut"><EM>enable-flag-screen-keyword-shortcut</EM></A>
<DD> This feature modifies the behavior of the
Flag command and the Select command.
By default, when the "* Flag" command is selected,
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the
option of entering the detailed flag manipulation screen via the "^T"
key.
If you have
<A HREF="#keywords">keywords</A>
defined, then enabling this feature adds a shortcut way to set or unset
keywords.
You use "*" followed by the first letter of a keyword (or the nickname of
a keyword if you've given it a nickname) and that will set the keyword.
<P>
An example is easier to understand than the explanation.
The flag command can always be used to set the system flags.
For example, to set the Answered flag you would type
<P>
<CENTER><SAMP>* A</SAMP></CENTER>
<P>
Now suppose you have defined a keyword "Work" using the Keywords
option in the Config screen.
By default, to set a keyword like "Work" you would usually
have to go to the Flag Details screen using
the "^T To Flag Details" command.
Instead, if you have enabled this feature, you may type
<P>
<CENTER><SAMP>* W</SAMP></CENTER>
<P>
to set the Work flag, or
<P>
<CENTER><SAMP>* ! W</SAMP></CENTER>
<P>
to unset it.
Just like for the other flag setting commands, the case of the letter does
not matter, so "w" or "W" both set the "Work"
keyword.
<P>
Notice that you can only use this trick for one keyword that begins
with "W".
If you happen to have a "Work" keyword and another keyword that is
"WIFI" the "* W" command will set the first one in
your list of keywords.
Also, there are five letters which are reserved for system
flags and the NOT command.
If you type "* A" it will always set the Answered flag, not
your "Aardvark" keyword.
In order to set the "Aardvark" keyword you'll still have to use
the Flag Details screen.
<P>
Because enabling the
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A>
option causes <EM>Alpine</EM> to skip directly to the Flag Details screen when the
Flag command is used,
setting it will cause this feature to have no effect at all.
<P>
Similarly, when Selecting by Keyword, setting this option will allow you
to use Keyword initials instead of full keywords.
<P>
<DT> <A NAME="enable-full-header-cmd"><EM>enable-full-header-cmd</EM></A>
<DD> This feature enables the <EM>H Full Headers</EM> command which
toggles between
the display of all headers in the message and the normal edited view of
headers. The <EM>Full Header</EM> command also controls
which headers are included
for <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>,
and <EM>Reply</EM> functions. (For <EM>Reply</EM>, the
<EM>Full Header</EM> mode will respect
the <EM>include-headers-in-reply</EM> feature setting.)
<P>
If Full Header mode is turned on and you Forward a message, you will
be asked if you'd like to forward the message as an attachment, as opposed
to including the text of the message in the body of your new message.
<P>
If you have also turned on the
<A HREF="#quote-suppression-threshold">"Quote Suppression"</A>
option then the Full Headers command actually rotates through three states
instead of just two.
The first is the normal view with long quotes suppressed.
The second is the normal view but with the long quotes included.
The last enables the display of all headers in the message.
When using Export, Pipe, Print, Forward, or Reply the quotes are
never suppressed, so the first two states are identical.
<P>
Normally, the Header Mode will reset
to the default behavior when moving to a new message.
The mode can be made to persist from message to message by setting the feature
<A HREF="#quell-full-header-auto-reset">Quell-Full-Header-Auto-Reset</A>.
<P>
This feature is displayed as "Enable Full Header Command".
<P>
<DT> <A NAME="enable-full-header-and-text"><EM>enable-full-header-and-text</EM></A>
<DD>
<P>This feature affects how the <EM>H Full Headers</EM> command displays
message text. If set, the raw message text will be displayed. This
especially affects MIME formatted email, where the entire MIME format
will be displayed. This feature similarly affects how messages are
included for the <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>,
and <EM>Reply</EM> functions.
<DT> <A NAME="enable-goto-in-file-browser"><EM>enable-goto-in-file-browser</EM></A>
<DD> Setting this causes <EM>Alpine</EM> to offer the <EM>G Goto</EM> command in
the file browser. The Goto command allows you to explicitly type in the
desired directory.
That is the default.
<P>
<DT> <A NAME="enable-incoming-folders"><EM>enable-incoming-folders</EM></A>
<DD> If set, this feature defines a pseudo-folder collection called
<EM>INCOMING MESSAGE FOLDERS</EM>.
Initially, the only folder included in this collection
will be your <EM>INBOX</EM>, which will no longer show up in your default
saved-message folder collection.
<P>
This feature is displayed as "Enable Incoming Folders Collection".
<P>
<DT> <A NAME="enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
<DD> This feature is only operational if you have enabled the optional
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
If you do have Incoming Message Folders and you also set this feature,
then the number of Unseen messages in each folder will be displayed
in the FOLDER LIST screen for the Incoming Message Folders.
The number of Unseen messages in a folder will be displayed in parentheses
to the right of the name of each folder.
If there are no Unseen messages in a folder then only the name
is displayed, not a set of parentheses with zero inside them.
A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
the Incoming Message Folders to cause an immediate update.
<P>
If a check for Unseen messages fails for a particular folder then Alpine
will no longer attempt to check that folder for the duration of the
session and this will be indicated by a question mark inside the
parentheses.
<P>
The features
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>,
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>,
<A HREF="#incoming-check-list"><EM>incoming-check-list</EM></A>,
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>,
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>, and
<A HREF="#incoming-check-timeout"><EM>incoming-check-timeout</EM></A>
all affect how this feature behaves.
<P>
<DT> <A NAME="disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A>
<DD> This feature affects the display of dates in the MESSAGE INDEX.
Normally an attempt is made to localize the dates
used in the MESSAGE INDEX display to your locale.
This is controlled with the
LC_TIME locale setting on a UNIX system.
On Windows the Regional Options control panel may be used to set the date format.
At the programming level, <EM>Alpine</EM> is using the strftime routine
to print the parts of a date.
<P>
If this feature is set, dates are displayed in English and
with the conventions of the United States.
<P>
<DT> <A NAME="enable-jump-shortcut"><EM>enable-jump-shortcut</EM></A>
<DD> When this feature is set you may enter a number (followed by RETURN)
and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
screens. In other words, it obviates the need for typing the <EM>J</EM> for the
<EM>Jump</EM> command.
<P>
<DT> <A NAME="enable-lame-list-mode"><EM>enable-lame-list-mode</EM></A>
<DD> This feature modifies the method <EM>Alpine</EM> uses to ask your IMAP
server for folder names to display in the the FOLDER LIST screen.
It is intended to compensate for a small set of IMAP servers that
are programmed to ignore a part of the request, and thus respond
to <EM>Alpine</EM>'s query with nonsensical results.
<P>
If you find that <EM>Alpine</EM> is erroneously displaying blank folder lists,
try enabling this feature.
<P>
NOTE: Enabling this feature has consequences for the Goto and Save
commands. Many servers allow access to folders outside the area
reserved for your personal folders via some reserved character,
typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
allows, at the Goto and Save prompts, quick access to folders
outside your personal folder collection without requiring a specific
collection definition. This behavior will generally not be available
when this feature is enabled.
<P>
This feature is displayed as "Compensate for Deficient IMAP servers".
<P>
<DT> <A NAME="enable-mail-check-cue"><EM>enable-mail-check-cue</EM></A>
<DD> If set, this will cause an asterisk to appear in the upper
left-hand corner of the screen whenever <EM>Alpine</EM> checks for new mail, and two
asterisks whenever <EM>Alpine</EM> saves (checkpoints) the state of the current
mailbox to disk.
<P>
<DT> <A NAME="enable-mailcap-param-substitution"><EM>enable-mailcap-param-substitution</EM></A>
<DD> If set, this will allow mailcap named parameter substitution to occur
in mailcap entries.
By default, this is turned off to prevent security problems which may occur
with some incorrect mailcap configurations.
For more information, RFC1524 and look for "named parameters" in the
text of the RFC.
<P>
This feature is displayed as "Enable Mailcap Parameter Substitution".
<P>
<DT> <A NAME="enable-mouse-in-xterm"><EM>enable-mouse-in-xterm</EM></A>
<DD>
This feature controls whether or not an X terminal mouse can be used with
<EM>Alpine</EM>. If set, and the $DISPLAY variable indicates that an X terminal is
being used, the left mouse button on the mouse can be used to select text
or commands.
Clicking on a command at the bottom of the screen will behave as if you had
typed that command.
Clicking on an index line will move the current message highlight to
that line.
Double-clicking on an index line will view the message.
Double-clicking on a link will view the link.
<P>
This type of mouse support will also work in some terminal emulators which are
not actually X terminals, but which have extra code to support the xterm
style mouse.
For those emulators you not only need to turn this feature on but you also
have to set the $DISPLAY environment variable even though it isn't needed
for your terminal.
That will cause <EM>Alpine</EM> to think that it is an xterm and to properly interpret the
escape sequences sent by the mouse.
<P>
Note: if this feature is set, the behavior of X terminal cut-and-paste is
also modified. It is sometimes possible to hold the shift key down while clicking
left or middle mouse buttons for the normal xterm cut/paste operations.
There is also an <EM>Alpine</EM> command to toggle this mode on or off.
The command is Ctrl-\ (Control-backslash).
<P>
<DT> <A NAME="enable-msg-view-addresses"><EM>enable-msg-view-addresses</EM></A>
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
Setting this feature causes <EM>Alpine</EM> to select possible email addresses
from the displayed text and display them in boldface for selection.
<P>
The first available email address is displayed in inverse. This is the
"selected" address.
Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to enter the message
composition screen with the To field filled in with the selected address.
<P>
Use the up and down arrow keys to change which of the addresses
displayed in boldface is the current selection.
<P>
This feature is displayed as "Enable Message View Address Links".
<P>
<DT> <A NAME="enable-msg-view-attachments"><EM>enable-msg-view-attachments</EM></A>
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
Setting this feature causes <EM>Alpine</EM> to present attachments in boldface.
The first available attachment is displayed in inverse. This is the
"selected" attachment. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected attachment. Use the up and down arrow keys to change which of the
attachments displayed in boldface is the current selection.
<P>
Speaking of arrow keys, the Up and Down Arrows will select the next
and previous attachments if one is available on the screen for selection.
Otherwise, they will simply adjust the viewed text one line up or down.
<P>
Similarly, when selectable items are present in a message, the Ctrl-F
key can be used to select the next item in the message independent
of which portion of the viewed message is currently displayed. The
Ctrl-B key can be used to select the previous item in the same way.
<P>
This feature is displayed as "Enable Message View Attachment Links".
<P>
<DT> <A NAME="enable-msg-view-forced-arrows"><EM>enable-msg-view-forced-arrows</EM></A>
<DD> This feature modifies Up and Down arrow key behavior in <EM>Alpine</EM>'s
"Message Text" screen when selectable Attachments, URL's, or
web-hostnames are presented. <EM>Alpine</EM>'s usual behavior is to move to
the next or previous selectable item if currently displayed or
simply to adjust the screen view by one line if the next selectable line
is off the screen.
<P>
Setting this feature causes the Up and Down arrow keys to behave as
if no selectable items were present in the message.
<P>
Note, the <EM>Ctrl-F</EM> (next selectable item) and
<EM>Ctrl-B</EM> (previous selectable item) functionality is unchanged.
<P>
This feature is displayed as "Enable Message View Forced Arrows".
<P>
<DT> <A NAME="enable-msg-view-urls"><EM>enable-msg-view-urls</EM></A>
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
When this feature is set (the default) <EM>Alpine</EM> will select possible URLs from the
displayed text and display them in boldface for selection.
<P>
The first available URL is displayed in inverse. This is the
"selected" URL. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected URL via either built-in means as with <CODE>mailto:</CODE>,
<CODE>imap:</CODE>, <CODE>news:</CODE>, and <CODE>nntp:</CODE>,
or via an external application as defined
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable.
<P>
Use the up and down arrow keys to change which of the URLs displayed in boldface
is the current selection.
<P>
This feature is displayed as "Enable Message View URL Links".
<P>
<DT> <A NAME="enable-msg-view-web-hostnames"><EM>enable-msg-view-web-hostnames</EM></A>
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen.
When this feature is set (the default) <EM>Alpine</EM> will select possible web hostnames
from the displayed text and display them in boldface for selection.
<P>
The first available hostname is displayed in inverse. This is the
"selected" hostname. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display
the selected hostname via an external application as defined
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable.
<P>
Use the up and down arrow keys to change which of the hostnames displayed in
boldface is the current selection.
<P>
This feature is displayed as "Enable Message View Web Hostname Links".
<P>
<DT> <A NAME="enable-multiple-newsrcs"><EM>enable-multiple-newsrcs</EM></A>
<DD> This feature makes it so <EM>Alpine</EM> can use multiple newsrcs based on
the news server being connected to, which allows for separate lists
of subscribed-to newsgroups. When this feature is not set, there is only
one list of newsgroups.
<P>
Under this feature, the name of a newsrc is based on the news server.
For example, if your <a href="#newsrc-path">newsrc-path</a>
is set to ".newsrc", and the news server you are connecting to is
news.example.com, then the newsrc to be used is .newsrc-news.example.com.
Setting this feature for the first time will allow for the option of using
your old newsrc the next time you read news.
<P>
If this feature is set, then the feature
<A HREF="#mult-newsrc-hostnames-as-typed">Mult-Newsrc-Hostnames-As-Typed</A>
also may affect the name of the newsrc file that is used.
<P>
<DT> <A NAME="enable-newmail-in-xterm-icon"><EM>enable-newmail-in-xterm-icon</EM></A>
<DD> This feature controls whether or not <EM>Alpine</EM> will attempt to announce new
mail arrival when it is running in an X terminal window and that window
is iconified.
If set, and the <CODE>$DISPLAY</CODE> variable indicates that an X
terminal is being used, <EM>Alpine</EM> will send appropriate escape sequences to
the X terminal to modify the label on <EM>Alpine</EM>'s icon to indicate that new
mail has arrived. <EM>Alpine</EM> will also modify the <EM>Alpine</EM> window's title to
indicate new mail.
See also <A HREF="#enable-newmail-short-text-in-icon">Enable-Newmail-Short-Text-in-Icon</A>.
<P>
<DT> <A NAME="enable-newmail-short-text-in-icon"><EM>enable-newmail-short-text-in-icon</EM></A>
<DD> This feature controls the text to be displayed in an icon in the event
of a new message arrival. Normally, the message will
be the one that is displayed on the screen. This feature shortens the
message to a count of the number of new messages in brackets. This may be
more useful for those who use the window's title bar in the task bar as a
new mail indicator. This feature is only useful if the
<A HREF="#enable-newmail-in-xterm-icon">Enable-Newmail-in-Xterm-Icon</A>
is also set. Like the Enable-Newmail-in-Xterm-Icon
feature, this feature is only relevant when run in an xterm environment.
<P>
<DT> <A NAME="enable-partial-match-lists"><EM>enable-partial-match-lists</EM></A>
<DD> This feature affects the subcommands available when <EM>Sav</EM>ing
or Opening a new folder. If set, the subcommand <EM>^X ListMatches</EM> will be
available. This command allows you to type in a substring of the folder
you are looking for and when you type <EM>^X</EM> it will display all folders
which contain that substring in their names.
This feature is set by default.
<P>
<DT> <A NAME="enable-print-via-y-command"><EM>enable-print-via-y-command</EM></A>
<DD> By default, <EM>Alpine</EM>'s print command is available by pressing the <EM>%</EM>
key. In older versions of <EM>Pine</EM>, the print command was accessed by
pressing the <EM>Y</EM> key.
<P>
Enabling this feature will cause <EM>Alpine</EM> to recognize both the old
command, <EM>Y</EM>, and the new <EM>%</EM> method for invoking
printing. Note, key menu labels are not changed as a result of
enabling this feature.
<P>
<DT> <A NAME="enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>
<DD> This feature affects the Reply command's "Include original message
in Reply?" prompt. When enabled, it causes the
"Edit Indent String" sub-command to appear which allows
you to edit the string <EM>Alpine</EM> would otherwise use to denote included
text from the message being replied to.<P>
Thus, you can change <EM>Alpine</EM>'s default message quote character (usually
an angle bracket) on a per message basis. So you could change your quoted message to
look, for example, like this:<p>
<pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
John: I just wanted to say hello and to congratulate you
John: on a job well done!</pre><p>
The configuration option
<A HREF="#reply-ind-str">"reply-indent-string"</A>
may be used to change what appears as the default string to be edited.
<P>
NOTE: Edited reply-indent-strings only apply to the message
currently being replied to.
<P>
<DT> <A NAME="enable-rules-under-take"><EM>enable-rules-under-take</EM></A>
<DD> Normally, the Take command takes addresses from a message and helps you
put them into your Address Book.
If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
you may find it useful
to be able to Take information from a message's headers and put it into
a new Rule.
When this feature is set, you will be given an extra prompt which gives
you the choice to Take into the Address Book or Take into a rule.
<P>
This feature is displayed as "Enable Take Rules".
<P>
<DT> <A NAME="enable-search-and-replace"><EM>enable-search-and-replace</EM></A>
<DD> If set <EM>Alpine</EM>'s composer offers the <EM>R Replace</EM> command
option inside the <EM>W WhereIs</EM> command.
<P>
<DT> <A NAME="enable-sigdashes"><EM>enable-sigdashes</EM></A>
<DD> If set and a <EM>signature-file</EM> exists, the line consisting of
the three characters "<CODE>-- </CODE>" (dash dash space) is included
before the signature.
This only happens if the signature doesn't already contain such a line.
<P>
In addition, when you Reply or Followup to a message containing one of
these special lines and choose to include its text, <EM>Alpine</EM> will observe
the convention of not including text beyond the special line in your
reply.
<P>
<DT> <A NAME="enable-suspend"><EM>enable-suspend</EM></A>
<DD> Setting this feature will allow you to type <EM>^Z</EM>
and temporarily suspend <EM>Alpine</EM>. Not available on <EM>PC-Alpine</EM>.
<P>
<DT> <A NAME="enable-tab-completion"><EM>enable-tab-completion</EM></A>
<DD> This feature enables the <EM>TAB</EM> key when
at a prompt for a filename. In this
case, <EM>TAB</EM> will cause the
partial name already entered to be automatically
completed, provided the partial name is unambiguous.
This feature is set by default.
<P>
Similarly, this feature also enables TAB completion of address book
nicknames when at a prompt for a nickname,
or when typing in an address field in the composer.
<P>
<DT> <A NAME="enable-take-export"><EM>enable-take-export</EM></A>
<DD> Normally, the Take command takes addresses from a message and helps you
put them into your Address Book.
When this feature is set, you will be given an extra prompt which gives you
the choice to Take addresses into a file instead of your Address
Book.
Only the user@domain_name part of the address is put in the file.
<P>
<DT> <A NAME="enable-tray-icon"><EM>enable-tray-icon</EM></A>
<DD> <EM>PC-Alpine</EM> only. This option restores a behavior of
previous versions of PC-Alpine. These
versions, when started, installed a PC-Alpine icon in the notification
tray of Window's Taskbar. The primary use of this icon was to indicate
new mail arrival by turning red (while the Taskbar icon remained green).
Additionally, the icon now changes to yellow to signify that a mail folder
has been closed unexpectedly.
<P>
Rather than add another icon to the Taskbar, this version of PC-Alpine will
color its Taskbar entry's icon red (as well as the icon in the Window
Title). This feature is only provided for backwards compatibility.
<P>
<DT> <A NAME="enable-unix-pipe-cmd"><EM>enable-unix-pipe-cmd</EM></A>
<DD> This feature enables the <EM>| Pipe</EM> command
that sends the current message
to the specified Unix command for external processing.
<P>
This feature is displayed as "Enable Unix Pipe Command".
<P>
<DT> <A NAME="enable-verbose-smtp-posting"><EM>enable-verbose-smtp-posting</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s message sending. When enabled,
<EM>Alpine</EM> will send a <CODE>VERB</CODE> (i.e., VERBose) command
early in the posting process
intended to cause the server SMTP to provide a more detailed account of
the transaction. This feature is typically only useful to system
administrators and other support personnel as an aid in troubleshooting
problems.
Note, this feature relies on a specific capability of the system's mail
transport agent or configured <A HREF="#smtp-server"><EM>smtp-server</EM></A>.
<P>
<DT> <A NAME="expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A>
<DD> If multiple address books (either personal or global) are defined, and you
wish to have them all expanded implicitly upon entering the ADDRESS BOOK
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="#combined-addrbook-display"><EM>combined-addrbook-display</EM></A>
is also set.
<P>
<DT> <A NAME="expanded-view-of-distribution-lists"><EM>expanded-view-of-distribution-lists</EM></A>
<DD> If this feature is set, then distribution lists in the address book
screen will always be expanded automatically.
<P>
<DT> <A NAME="expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A>
<DD> If multiple folder collections are defined, and you
wish to have them all expanded implicitly upon entering the FOLDER LIST
screen, then set this feature. This feature will have no effect unless the
feature
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A>
is also set.
<P>
<DT> <A NAME="expose-hidden-config"><EM>expose-hidden-config</EM></A>
<DD> The purpose of this feature is to allow you to change configuration
features and variables which are normally hidden.
This is particularly useful if you are using a remote configuration file,
where it is difficult to edit the file manually, but it may also be used
on a local pinerc configuration file.
<P>
If set, most configuration variables and features which are normally
hidden from view will show up in the Setup/Configuration screen.
They will be at the bottom of the configuration screen.
You can find them by searching for the word "hidden".
<P>
Note that this is an advanced feature which should be used with care.
The reason that this part of the configuration is normally hidden is because
there is a significant potential for causing problems if you change these
variables.
If something breaks after a change try changing it back to see if that is
what is causing the problem.
There are also some variables which are normally hidden because they are
manipulated through <EM>Alpine</EM> in other ways.
For example, the "address-book" variable is normally set using
the Setup/AddressBooks screen, so there is little reason to edit it directly.
The "incoming-folders" variable is normally changed by using
the Add, Delete, and Rename commands in the FOLDER LIST screen,
and the "last-time-prune-questioned" variable is normally used
internally by <EM>Alpine</EM> and not set directly by the user.
<P>
<DT> <A NAME="expunge-only-manually"><EM>expunge-only-manually</EM></A>
<DD> Normally, when you close a folder which contains deleted messages you are
asked if you want to expunge those messages from the folder permanently.
If this feature is set, you won't be asked and the deleted messages will
remain in the folder.
If you choose to set this feature you will have to expunge the
messages manually using the eXpunge command, which you can use while
in the MESSAGE INDEX screen.
If you do not expunge deleted messages the size of your
folder will continue to increase until you are out of disk space.
<P>
<DT> <A NAME="expunge-wo-confirm"><EM>expunge-without-confirm</EM></A>
<DD> If set, you will not be prompted to confirm your intent before
the expunge takes place. Actually, you will still be prompted for confirmation
if the folder is not the <EM>INBOX</EM> folder or another folder in the
Incoming Folders collection. See the <EM>expunge-without-confirm-everywhere</EM>
feature which follows.
<P>
This feature is displayed as "Expunge Without Confirming".
<P>
<DT> <A NAME="expunge-without-confirm-everywhere"><EM>expunge-without-confirm-everywhere</EM></A>
<DD> The regular <EM>expunge-without-confirm</EM> feature actually only
works for the <EM>INBOX</EM> folder and for other folders in the "Incoming
Folders" collection. If this feature is set then you also won't be prompted
to confirm expunges for all other folders.
<P>
This feature is displayed as "Expunge Without Confirming Everywhere".
<P>
<DT> <A NAME="fcc-on-bounce"><EM>fcc-on-bounce</EM></A>
<DD> If set, normal Fcc (File Carbon Copy) processing will be
done for bounced messages,
just as if you had composed a message to the address you are
bouncing to. If not set, no Fcc of the message will be saved.
<P>
This feature is displayed as "Include Fcc When Bouncing Messages".
<P>
<DT> <A NAME="fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A>
<DD> This features controls an aspect of <EM>Alpine</EM>'s composer.
The only time this feature will be used is if you attempt to send mail
which has no recipients but does have an Fcc.
Normally, <EM>Alpine</EM> will ask if you really mean to copy the message only to
the Fcc.
That is, it asks if you really meant to have no recipients.
If this feature is set, you
will <B>not</B> be prompted to confirm your intent to make only a copy
of a message with no recipients.
<P>
This feature is closely related to
<A HREF="#warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A>.
The difference between this feature and that feature is that this feature
considers a Bcc to be a recipient while that feature will ask for confirmation
even if there is a Bcc when there is no To, Cc, or Newsgroup.
The default values also differ. This feature defaults to asking the question
and you have to turn it off.
The warn-if-blank-to-and-cc-and-newsgroups feature defaults to not asking
unless you turn it on.
<P>
This feature is displayed as "Send to Fcc Only Without Confirming".
<P>
<DT> <A NAME="fcc-without-attachments"><EM>fcc-without-attachments</EM></A>
<DD> This features controls the way FCC's (File Carbon Copies) are
made of the messages you send.
<P>
Normally, <EM>Alpine</EM> saves an exact copy of your message as it was sent.
When this feature is enabled, the "body" of the message
you send (the text you type in the composer) is preserved in the
copy as before, however all attachments are replaced with text
explaining what had been sent rather than the attachments themselves.
<P>
This feature also affects <EM>Alpine</EM>'s "Send ?" confirmation prompt
in that a new "^F Fcc Attchmnts" option becomes available which
allows you to interactively set whether or not attachments are saved
to the Fcc'd copy.
<P>
This feature is displayed as "Fcc Does Not Include Attachments".
<P>
<DT> <A NAME="force-arrow-cursor"><EM>force-arrow-cursor</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display routine.
If set, the normal inverse-video cursor will be
replaced by a simple "arrow" cursor, which normally occupies the
second column of the index display.
<P>
This is the same index cursor you get if you turn on
<A HREF="#assume-slow-link">Assume-Slow-Link</A>, but the index
line coloring will still be present if this feature is turned on and
Assume-Slow-Link is off.
<P>
An alternative version of the Arrow cursor is available by including the
ARROW
token in the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
<P>
It ought to be the case that this feature also affects the ATTACHMENT INDEX,
but that is not implemented.
<P>
<DT> <A NAME="hide-nntp-path"><EM>hide-nntp-path</EM></A>
<DD> Normally the Path header that <EM>Alpine</EM> generates when posting to a newsgroup
contains the name of the computer from which the message is being sent and
the user name.
Some believe that this information is used by spammers.
If this feature is set, that information will be replaced with the text
<P>
<CENTER><SAMP>not-for-mail</SAMP></CENTER>
<P>
instead.
<P>
It should be noted that many servers being connected to will still reveal
the information that this feature attempts to protect.
<P>
<DT> <A NAME="include-attachments-in-reply"><EM>include-attachments-in-reply</EM></A>
<DD> If set, any MIME
attachments that were part of the original message will automatically be
included in a <EM>Reply</EM>.
<P>
<DT> <A NAME="include-header-in-reply"><EM>include-header-in-reply</EM></A>
<DD> If set, and a
message being replied to is included in the <EM>Reply</EM>,
then headers from that
message will also be part of the reply.
<P>
<DT> <A NAME="include-text-in-reply"><EM>include-text-in-reply</EM></A>
<DD> Normally, <EM>Alpine</EM> will ask whether you
wish to include the original message in your <EM>Reply</EM>.
If this feature is set and the feature
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A>
is <EM>not</EM> set, then the original message will be included in the reply
automatically, without prompting.
<P>
<DT> <A NAME="incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When incoming folder checking is turned on the default is to display
the number of unseen messages in each folder.
More precisely, it is the number of undeleted unseen messages.
Using this option you may also display the total number of messages
in each folder.
Instead of a single number representing the number of unseen messages
you will get two numbers separated by a slash character.
The first is the number of unseen messages and the second is the
total number of messages.
<P>
You may also use the recent message count instead of the unseen message
count by turning on the feature
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>.
<P>
<DT> <A NAME="incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>
<DD> This option has no effect unless the feature
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is set, which in turn has no effect unless
<A HREF="#inc-fold"><EM>incoming-folders</EM></A>
is set.
<P>
When incoming folder checking is turned on the default is to display
the number of unseen messages in each folder.
More precisely, it is the number of undeleted unseen messages.
Using this option you may display the number of recent messages instead
of the number of unseen messages.
A message is only counted as recent if this is the first session to
see it, so the recent count might be less than the unseen count.
The difference between the two would be accounted for by the unseen messages
in the folder which were there previously but have not been looked at yet.
<P>
If you simultaneously run more than one email client at a time
(for example, you run more than one <EM>Alpine</EM> in parallel) then turning
this feature on can cause some confusion.
The confusion stems from the fact that each message is only considered to be
recent in one session.
That means that the counts of new messages may be different in the two
<EM>Alpine</EM>s running side by side, because each incoming message will only be
counted as recent in one of the two sessions.
<P>
You may also display the total number of messages
in each folder by using the
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>
option.
<P>
<DT> <A NAME="ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>
<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library
when it was compiled.
If both the per-directory-server option
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>
and this feature are set,
then when an implicit directory lookup is done from the
composer you will automatically be prompted to add the result of the
directory lookup to your address book.
<P>
This feature is displayed as "LDAP Result to Addressbook Add".
<P>
<DT> <A NAME="maildrops-preserve-state"><EM>maildrops-preserve-state</EM></A>
<DD>
This feature affects the way
<A HREF="config-notes.html#maildrop">Mail Drops</A> work.
Normally, when mail is moved from a Mail Drop folder to a destination
folder, the state changes that have taken place since the mail was originally
delivered are lost.
Any Seen/New, Answered, Important/Flagged state that has changed will be
ignored.
All of the mail will be considered unSeen, unAnswered, and unImportant after
it is moved.
<P>
If this feature is set, then the state changes will not be lost.
<P>
In any case, messages which are already marked Deleted when the
mail is to be copied from the Mail Drop will be ignored.
<P>
<DT> <A NAME="mark-fcc-seen"><EM>mark-fcc-seen</EM></A>
<DD> This features controls the way FCCs (File Carbon Copies) are
made of the messages you send.
Normally, when <EM>Alpine</EM> saves a copy of a message you sent as an Fcc, that
copy will be marked as Unseen.
When you look at the folder it was saved in the message will appear to
be a New message until you read it.
When this feature is enabled, the message will be marked as having
been Seen.
<P>
<DT> <A NAME="mark-for-cc"><EM>mark-for-cc</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display.
By default, a '+' is displayed in the first column if the
message is addressed directly to you.
When this feature is set and the message is not addressed to you, then a
'-' character is displayed if the message is instead Cc'd directly
to you.
<P>
<DT> <A NAME="mult-newsrc-hostnames-as-typed"><EM>mult-newsrc-hostnames-as-typed</EM></A>
<DD> This feature will be of little use to most users.
It has no effect unless the feature
<A HREF="#enable-multiple-newsrcs">Enable-Multiple-Newsrcs</A>
is set.
When the Enable-Multiple-Newsrcs feature is set
then the setting of this feature may have an effect on the names of the
newsrc files used.
Normally, the name of the news server will be canonicalized before it is
used in the newsrc file name.
For example, if you type the news server name
<P>
<CENTER><SAMP>servername</SAMP></CENTER>
<P>
it is likely that the canonical name will be something like
<P>
<CENTER><SAMP>servername.example.com</SAMP></CENTER>
<P>
Or it may be the case that
<P>
<CENTER><SAMP>servername.example.com</SAMP></CENTER>
<P>
is really an alias (a DNS CNAME) for
<P>
<CENTER><SAMP>othername.example.com</SAMP></CENTER>
<P>
If this feature is not set, then the canonicalized names will be used.
If this feature is set, then the name you typed in (or put in your
configuration) will be used.
<P>
This feature is displayed as "Multiple Newsrc Hostnames as Typed".
<P>
<DT> <A NAME="news-approximates-new-status"><EM>news-approximates-new-status</EM></A>
<DD> This feature causes certain messages to be marked as <EM>New</EM> in the
MESSAGE INDEX of newsgroups.
This feature is set by default.
<P>
When opening a newsgroup, <EM>Alpine</EM> will consult
your <EM>newsrc</EM> file and
determine the last message you have previously disposed of via the <EM>D</EM>
key. If this feature is set, any subsequent messages will be shown in the
Index with an <EM>N</EM>, and the first of these messages will be highlighted.
Although this is only an approximation of true <EM>New</EM> or <EM>Unseen</EM>
status, it provides a useful cue to distinguish more-or-less recent
messages from those you have seen previously, but are not yet ready to
mark deleted.
<P>
Background: your <EM>newsrc</EM> file (used to store message status information
for newsgroups) is only capable of storing a single flag, and <EM>Alpine</EM> uses
this to record whether or not you are "done with" a message, as
indicated by marking the message as <EM>Deleted</EM>. Unfortunately, this
means that <EM>Alpine</EM> has no way to record exactly which messages you have
previously seen, so it normally does not show the <EM>N</EM> status flag for
any messages in a newsgroup. This feature enables a starting
<I>approximation</I> of seen/unseen status that may be useful.
<P>
<DT> <A NAME="news-deletes-across-groups"><EM>news-deletes-across-groups</EM></A>
<DD> This feature controls what <EM>Alpine</EM> does when you delete a
message in a newsgroup that appears in more than one newsgroup.
Such a message is sometimes termed a "crossposting"
in that it was posted across several newsgroups.
<P>
<EM>Alpine</EM>'s default behavior when you delete such a message is to remove
only the copy in the current newsgroup from view when you use the
"Exclude" command or the next time you visit the newsgroup.
<P>
Enabling this feature causes <EM>Alpine</EM> to remove every occurrence of the
message from all newsgroups it appears in and to which you are
subscribed.
<P>
NOTE: As currently implemented, enabling this feature may increase the
time it takes the Expunge command and newsgroup closing to complete.
<P>
<DT> <A NAME="news-offers-catchup-on-close"><EM>news-offers-catchup-on-close</EM></A>
<DD> This feature controls what <EM>Alpine</EM> does as it closes a newsgroup.
When set, <EM>Alpine</EM> will offer to delete all messages from the newsgroup
as you are quitting <EM>Alpine</EM> or opening a new folder.
<P>
This feature is useful if you typically read all the interesting messages
in a newsgroup each time you open it. This feature saves you from
having to delete each message in a newsgroup as you read it or from
selecting all the messages and doing an
aggregate delete before you move on to the next folder or newsgroup.
<P>
<DT> <A NAME="news-post-without-validation"><EM>news-post-without-validation</EM></A>
<DD> This feature controls whether the NNTP server is queried as newsgroups
are entered for posting. Validation over slow links (e.g. dialup using
SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
<P>
<DT> <A NAME="news-read-in-newsrc-order"><EM>news-read-in-newsrc-order</EM></A>
<DD> This feature controls the order that newsgroups will be presented. If
set, they will be presented in the same order as they occur in
your <EM>newsrc</EM> file.
If not set, the newsgroups
will be presented in alphabetical order.
<P>
<DT> <A NAME="next-thread-without-confirm"><EM>next-thread-without-confirm</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s Next and Prev commands in
the case where you are using one of the
"separate-index-screen" styles for the configuration option
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
and currently have the folder sorted by a Threaded or OrderedSubject sort.
When you are Viewing a particular thread you have a
MESSAGE INDEX of only the messages in that thread.
If you press the Next command with the last message in the thread highlighted
you will normally be asked if you want to "View next thread?",
assuming there is a next thread to view.
If this feature is set it will be assumed that you always want to view the
next thread and you won't be asked to confirm that.
Similarly, if the first message of the thread is highlighted and you
press the Prev command, this feature will prevent the question
"View previous thread".
<P>
This feature only has an effect in the MESSAGE INDEX screen.
If you then view a particular message from that screen and press the
Next command, you will be sent to the next thread without being asked,
independent of the setting of this feature.
<P>
The feature
<A HREF="#auto-open-next-unread">auto-open-next-unread</A>,
also has some similar effects.
<P>
This feature is displayed as "Read Next Thread Without Confirming".
<P>
<DT> <A NAME="offer-expunge-of-inbox"><EM>offer-expunge-of-inbox</EM></A>
<DD> The INBOX is normally treated differently from regular folders in several
ways.
One of the differences is that the normal "close" sequence of
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you
leave the INBOX to view another folder.
The "close" sequence normally includes the Expunging
of deleted messages
(either automatically or after a prompt, controlled by the features
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>,
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the
handling of the
<A HREF="#read-msg-fold">Read-Message-Folder</A>.
<P>
If this feature is set the "close" sequence handling will take
place every time you leave the INBOX.
The INBOX will still be kept open, but the offer to Expunge and the archiving
to the Read-Message-Folder
will take place each time you leave the INBOX instead of only once at the
end of the session.
<P>
<DT> <A NAME="offer-expunge-of-stayopen-folders"><EM>offer-expunge-of-stayopen-folders</EM></A>
<DD> This feature is related to the option
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
Stay Open folders are treated differently from regular folders in several
ways.
One of the differences is that the normal "close" sequence of
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you
leave the folder to view another folder.
The "close" sequence normally includes the Expunging
of deleted messages
(either automatically or after a prompt, controlled by the features
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>,
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the
handling of
<A HREF="#incoming-archive-folders">Incoming-Archive-Folders</A>.
<P>
If this feature is set the "close" sequence handling will take
place when you leave the Stay Open folder.
The folder will still be kept open, but the offer to Expunge and the archiving
will take place each time you leave the folder instead of only once at the
end of the session.
This feature does not affect the INBOX, which will still only be processed
when you exit <EM>Alpine</EM>.
<P>
<DT> <A NAME="pass-c1-control-characters-as-is"><EM>pass-c1-control-characters-as-is</EM></A>
<DD> It is probably not useful to set this option.
This is a legacy option left behind "just in case".
Multi-byte characters which have an octet which has the same
value as a control character are permitted through whether or not
this option is turned on.
<P>
If the feature <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A>
is set, then this feature has no effect.
However, if you wish to filter out regular control characters but pass the
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
you may leave <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A>
unset and set this feature.
<P>
<DT> <A NAME="pass-control-characters-as-is"><EM>pass-control-characters-as-is</EM></A>
<DD> It is probably not useful to set this option.
This is a legacy option left behind "just in case".
Multi-byte characters which have an octet which has the same
value as a control character are permitted through whether or not
this option is turned on.
<P>
If set, all characters in a message will be sent to the
screen. Normally, control characters are automatically suppressed in
order to avoid inadvertently changing terminal setup parameters.
Control characters are usually displayed as two character sequences like
<P><CENTER><SAMP> ^C </SAMP></CENTER><P>
for Control-C,
<P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
for ESCAPE,
<P><CENTER><SAMP> ^? </SAMP></CENTER><P>
for DELETE, and
<P><CENTER><SAMP> ~E </SAMP></CENTER><P>
for the character with value 133 (0x85).
(The DEL character is displayed as ^?, regular control characters are displayed
as the character ^ followed by the character obtained by adding the
five low-order bits of the character to 0x40, and the C1
control characters 0x80 - 0x9F are displayed as the character ~ followed by the
character obtained by adding the
five low-order bits of the character to 0x40.)
Sometimes, in cases where changing a single control character into a
two-character sequence would confuse <EM>Alpine</EM>'s display routines,
a question mark is substituted for the control character.
<P>
If you wish to filter out regular control characters but pass the
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
you may leave this feature unset and set the feature <A HREF="#pass-c1-control-characters-as-is">pass-c1-control-characters-as-is</A> instead.
<P>
<DT> <A NAME="predict-nntp-server"><EM>predict-nntp-server</EM></A>
<DD> This feature allows <EM>Alpine</EM> to assume that the open NNTP server at the
time of composition is the NNTP server to which the message should be
posted. This is especially recommended when there are multiple News
collections. If this feature is not set, <EM>Alpine</EM> will try to post to the first server in
the <a href="#nntp-server">nntp-server</a> variable. Setting
this feature also negates the need to add News collection servers to
the nntp-server variable.
<P>
This feature can be especially handy when used in conjunction with
<a href="#enable-multiple-newsrcs">enable-multiple-newsrcs</a>.
<P>
This option is displayed as "NNTP Server (for news)".
<P>
<DT> <A NAME="prefer-plain-text"><EM>prefer-plain-text</EM></A>
<DD> A message being viewed may contain alternate versions of the same content.
Those alternate versions are ordered by the sending software such that the
first alternative is the least preferred and the last alternative is the
most preferred. <EM>Alpine</EM> will normally display the most-preferred version that
it knows how to display. This is most often encountered where the two
alternate versions are a plain text version and an HTML version, with the
HTML version listed last as the most preferred.
<P>
If this option is set, then any plain text version will be preferred to
all other versions.
<P>
<DT> <A NAME="preopen-stayopen-folders"><EM>preopen-stayopen-folders</EM></A>
<DD> This feature is related to the option
<A HREF="#stay-open-folders">Stay-Open-Folders</A>.
Normally, Stay Open folders are only opened on demand, when the user
asks to open them.
From then on they are kept open for the duration of the session.
However, if this feature is set, then the Stay Open folders will all be
opened at startup, at the same time that the INBOX is opened.
<P>
<DT> <A NAME="preserve-start-stop-characters"><EM>preserve-start-stop-characters</EM></A>
<DD> This feature controls how special control key characters, typically
<EM>^S</EM> and <EM>^Q</EM>, are interpreted when input to <EM>Alpine</EM>.
These characters
are known as the "start" and "stop" characters and are sometimes used in
communications paths to control data flow between devices that operate at
different speeds.
<P>
By default, <EM>Alpine</EM> turns the system's handling of these special characters
off except during printing. However, if you see <EM>Alpine</EM> reporting input errors
such as:
<BLOCKQUOTE>
[ Command "^Q" not defined for this screen. ] <BR>
</BLOCKQUOTE>
and, at the same time, see your display become garbled, then it is likely
that setting this option will solve the problem. Be aware, though, that
enabling this feature will also cause <EM>Alpine</EM> to ostensibly "hang"
whenever the <EM>Ctrl-S</EM> key combination is entered as the system is now
interpreting such input as a "stop output" command. To "start
output" again, simply type <EM>Ctrl-Q</EM>.
<P>
This feature is displayed as "Preserve Start/Stop Characters".
<P>
<DT> <A NAME="print-formfeed-between-messages"><EM>print-formfeed-between-messages</EM></A>
<DD> Setting this feature causes a formfeed to be printed between messages when
printing multiple messages with the <EM>Apply Print</EM> command.
<P>
<DT> <A NAME="print-includes-from-line"><EM>print-includes-from-line</EM></A>
<DD> If this feature is set, then the Unix mail style From line is included
at the start of each message that is printed. This line looks something
like the following, with the address replaced by the address from the
From line of the message being printed:
<BLOCKQUOTE>
From user@domain.somewhere.com Mon May 13 14:11:06 1996 <BR>
</BLOCKQUOTE>
<P>
<DT> <A NAME="print-index-enabled"><EM>print-index-enabled</EM></A>
<DD> This feature controls the behavior of the <EM>Print</EM> command
when in the
"Folder Index" screen.
If set, the <EM>Print</EM> command will give you a prompt
asking if you wish to print the message index, or the currently highlighted
message. If not set, the message will be printed.
<P>
<DT> <A NAME="print-offers-custom-cmd-prompt"><EM>print-offers-custom-cmd-prompt</EM></A>
<DD> When this feature is set, the <EM>Print</EM> command
will have an additional
subcommand called <EM>C CustomPrint</EM>.
If selected, you will have
the opportunity to enter any system print command, instead of being
restricted to using those that have been previously configured in the
<EM>Setup/Printer</EM> screen.
<P>
This feature is displayed as "Print Offers Custom Command Prompt".
<P>
<DT> <A NAME="prune-uses-yyyy-mm"><EM>prune-uses-yyyy-mm</EM></A>
<DD> By default, <EM>Alpine</EM> asks monthly whether or not you would like to rename
some folders to a new name containing the date.
It also asks whether or not you would like to delete some old folders.
See the <A HREF="#pruning-rule">pruning-rule</A> option for an
explanation.
<P>
By default, the name used when renaming a folder looks like
<P>
<CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
<P>
For example, the first time you run <EM>Alpine</EM> in May of 2004,
the folder "sent-mail" might be renamed to
<P>
<CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
<P>
If this feature is set, the name used will be of the form
<P>
<CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
<P>
where "yyyy" is the year and "mm" is the two-digit
month (01, 02, ..., 12).
For the April, 2004 example above, it would instead be
<P>
<CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
<P>
because April is the 4th month of the year.
A reason you might want to set this feature is so that the folders
will sort in chronological order.
<P>
<DT> <A NAME="publiccerts-in-keychain"><EM>publiccerts-in-keychain</EM></A>
<DD> Mac OS X <EM>Alpine</EM> only.
<P>
If this feature is set the Mac OS X default keychain will be used as the place
to store public certificates instead of a
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>
or a
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A>.
<P>
This feature is displayed as "S/MIME -- Public Certs in MacOS Keychain".
<P>
<DT> <A NAME="quell-attachment-extension-warn"><EM>quell-attachment-extension-warn</EM></A>
<DD> This feature suppresses the extra warning you can get when trying
to view an attachment for which there is no mime-type match. Turning
on this feature will just run the program according to extension
instead of first warning the user that it will run according to the
file's extension.
<P>
This feature can be used along side
<A HREF="#quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A>
to preserve the behavior exhibited in <EM>Pine</EM> versions prior to <EM>Pine</EM> 4.50.
<P>
This feature is displayed as "Suppress Attachment Extension Warning".
<P>
<DT> <A NAME="quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A>
<DD> By default, when you attempt to view an attachment externally
from the "Attachment View" screen, you are asked if you
really want to view the selected attachment.
<P>
If this feature is set, you will <B>not</B> be prompted to confirm
your selection. Prior to <EM>Pine</EM> 4.50, the default behavior was to not
prompt. This feature was added for those wanting to preserve that
behavior.
<P>
This feature is displayed as "Suppress Attachment Extra Prompt".
<P>
<DT> <A NAME="quell-berkeley-format-timezone"><EM>quell-berkeley-format-timezone</EM></A>
<DD> POSIX mandates a timezone in UNIX mailbox format folder delimiters
(the line which begins with From <SPACE>).
Some versions of Berkeley mail have trouble with this, and don't recognize
the line as a message delimiter.
If this feature is set, the timezone will be left off the delimiter line.
<P>
This feature is displayed as "Suppress Berkeley Format Timezone".
<P>
<DT> <A NAME="quell-charset-warning"><EM>quell-charset-warning</EM></A>
<DD> By default, if the message you are viewing contains characters that are
not representable in your
<A HREF="#disp-char-set"><EM>display-character-set</EM></A>
then <EM>Alpine</EM> will
add a warning to the start of the displayed text.
If this option is set, then that editorial message will be suppressed.
<P>
Setting this feature also suppresses the comment about the character set
in header lines.
For example, when viewing a message you might see
<P>
<CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
<P>
in the From header if your Character-Set is something other than ISO-8859-2.
If you set this feature, the comment about the character set will
no longer be there.
<P>
This feature is displayed as "Suppress Character Set Warning".
<P>
<DT> <A NAME="quell-content-id"><EM>quell-content-id</EM></A>
<DD> This feature changes the behavior of <EM>Alpine</EM> when sending messages.
It is intended to work around a bug in Microsoft's Outlook XP mail user
agent.
As of this writing, Microsoft has acknowledged the bug but
has not added it to the Knowledge Base.
We have been told that there will be a post-SP1 hotfix for Outlook XP.
This particular bug has bug fix number OfficeQFE:4781.
The nature of the bug is that messages with attachments which
contain a Content-ID header (which standard <EM>Alpine</EM> attachments do)
do not show the attachment indicator (a paperclip) when viewed with
Outlook XP.
So the user has no indication that the message contains an attachment.
<P>
If this feature is set then <EM>Alpine</EM> will remove most Content-ID headers
before sending a message.
If an attachment is of type MESSAGE, then the existing Content-ID headers
inside the message will be left intact.
This would only happen with <EM>Alpine</EM> if a message was forwarded as an attachment
or if a message with a message attached was forwarded.
Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
the Content-ID headers of the alternative parts will not be removed.
<P>
Because the Content-ID header is a standard part of MIME it is possible
that setting this feature will break something.
For example, if an attachment has a Content-ID header which is necessary
for the correct functioning of that attachment, it is possible that <EM>Alpine</EM>
may remove that header when the attachment is forwarded.
However, it seems fairly safe at this time.
<P>
This feature is displayed as "Suppress Content-ID".
<P>
<DT> <A NAME="quell-dead-letter-on-cancel"><EM>quell-dead-letter-on-cancel</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when you cancel a message being
composed. <EM>Alpine</EM>'s usual behavior is to write the canceled message to
a file named <CODE>dead.letter</CODE> in your home directory (under UNIX;
<CODE>DEADLETR</CODE> under WINDOWS/DOS) overwriting any previous message.
Under some conditions (some routine), this can introduce a noticeable delay.
<P>
Setting this feature will cause <EM>Alpine</EM> NOT to write canceled compositions
into the file called <CODE>dead.letter</CODE>.
<P>
This feature affects the newer option
<A HREF="#dead-letter-files"><EM>Dead-Letter-Files</EM></A>, which specifies the
number of dead letter files to keep around.
If this feature is set, then the Dead-Letter-Files option has no effect.
<P>
This feature is displayed as "Do Not Save to Deadletter on Cancel".
<P>
<DT> <A NAME="quell-empty-directories"><EM>quell-empty-directories</EM></A>
<DD> This feature causes <EM>Alpine</EM> to remove from the display any directories
that do not contain at least one file or directory. This can be useful
to prevent overly cluttered folder lists when a collection is stored on
a server that treats all names as both a folder and a directory.
<P>
Note, enabling this feature can cause surprising behavior! For example,
you can still use Add to create a directory, but unless you immediately
enter that directory and create a folder, that newly created directory
may not be displayed next time you enter the folder list.
<P>
This feature is displayed as "Hide Empty Directories".
<P>
<DT> <A NAME="quell-extra-post-prompt"><EM>quell-extra-post-prompt</EM></A>
<DD> This feature causes <EM>Alpine</EM> to skip the extra question about
posting a message which may go to thousands of readers when you
are about to post to a newsgroup.
<P>
This feature is displayed as "Suppress Extra Posting Prompt".
<P>
<DT> <A NAME="quell-filtering-done-message"><EM>quell-filtering-done-message</EM></A>
<DD> This feature causes <EM>Alpine</EM> to suppress the "filtering done" message.
<P>
This feature is displayed as "Suppress Filtering Done Message".
<P>
<DT> <A NAME="quell-filtering-messages"><EM>quell-filtering-messages</EM></A>
<DD> This feature causes <EM>Alpine</EM> to suppress the messages about
moving filtered messages and setting flags in messages, due to Filter Rules.
<P>
This feature is displayed as "Suppress Filtering Messages".
<P>
<DT> <A NAME="quell-flowed-text"><EM>quell-flowed-text</EM></A>
<DD> <EM>Alpine</EM> generates flowed text where possible.
The method for generating flowed text is defined by
<A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
the benefit of doing so is
to send message text that can properly be viewed both on normal width displays
and on displays with smaller or larger than normal screen widths.
With flowed text, a space at the end of a line tells the receiving mail
client that the following line belongs to the same paragraph.
Quoted text will also be affected, with only the innermost
level of ">" quoting being followed by a space.
However, if you have changed the
<A HREF="#reply-ind-str">"Reply-Indent-String"</A>
so that it is not equal to the default value of "> ", then
quoted text will not be flowed.
For this reason, we recommend that you leave your
"Reply-Indent-String" set to the default.
<P>
This feature turns off the generation of flowed text, as it might be
desired to more tightly control how a message is displayed on the receiving end.
<P>
If this feature is <EM>not</EM> set, you can control on a message by message
basis whether or not flowed text is generated.
You do this by typing ^V at the Send confirmation prompt that you get
after typing ^X to send a message.
^V is a toggle which turns flowing off and back on if typed again.
If for some reason flowing cannot be done on a particular message, then the
^V command will not be available.
This would be the case, for example, if this feature was set, or if your
"Reply-Indent-String" was set to a non-default value.
If the feature
<A HREF="#send-without-confirm">Send-Without-Confirm</A> is set,
then the opportunity to control on a message by message basis
whether or not flowed text is generated is lost.
<P>
When this feature is not set and you have typed ^V to turn off flowing,
the Send confirmation prompt will change to look like
<P>
<CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
<P>
<A HREF="#strip-whitespace-before-send">Strip-Whitespace-Before-Send</A> will
also turn off the sending of flowed text messages, but it differs in that
it also trims all trailing white space from a message before sending it.
<P>
If alternate editors are used extensively, be aware that a message will still
be sent flowed if this feature is unset. In most cases this will be fine,
but if the editor has a "flowed text" mode, it would be best to
use that.
<P>
This feature is displayed as "Do Not Send Flowed Text".
<P>
<DT> <A NAME="quell-folder-internal-msg"><EM>quell-folder-internal-msg</EM></A>
<DD> This feature determines whether or not <EM>Alpine</EM> will create
"pseudo messages" in folders that are in standard Unix or
MMDF format.
<P>
<EM>Alpine</EM> will normally create these
pseudo messages when they are not already
present in a standard Unix or MMDF folder.
Their purpose is to record
certain mailbox state data needed for correct IMAP and POP server operation,
and also for <EM>Alpine</EM> to be able to mark messages as Answered when
the Reply has been postponed.
<P>
Sites which do not use IMAP/POP for remote mail access, and which need to
support mail tools that are adversely affected by the presence of the
pseudo-messages (e.g. some mail notification tools) may enable this
feature to tell <EM>Alpine</EM> not to create them.
Note that <EM>Alpine</EM>'s "Answered" flag
capability will be adversely affected if this is done.
<P>
Note too that, even if this feature is enabled, <EM>Alpine</EM> will not remove
pseudo-messages when it encounters them (e.g. those created by UW's imapd
or ipopd servers.)
This feature has no effect on folders that are not in
standard Unix or MMDF format, as pseudo-messages are not needed in the
other formats to record mailbox state information.
<P>
This feature is displayed as "Prevent Folder Internal Message".
<P>
<DT> <A NAME="quell-full-header-auto-reset"><EM>quell-full-header-auto-reset</EM></A>
<DD> The HdrMode Command
normally resets to the default state when switching to a new message.
For example, if you've used the "H" command to turn on Full
Headers for a message you are viewing, and then you type the Next command
to look at the next message, the full headers will no longer be shown.
Setting this feature disables that reset.
Instead, the Header Mode remains the same from message to message.
<P>
The presence or absence of the HdrMode command is determined by the
<A HREF="#enable-full-header-cmd">"Enable-Full-Header-Cmd"</A>
Feature-List option.
<P>
This feature is displayed as "Suppress Full Header Auto Reset".
<P>
<DT> <A NAME="quell-imap-envelope-update"><EM>quell-imap-envelope-update</EM></A>
<DD> In the MESSAGE INDEX screen, if the open folder is being accessed
using IMAP, <EM>Alpine</EM> normally tries to paint the index lines on the screen
as soon as the information arrives from the IMAP server.
This means that the index information makes it onto the screen more quickly
than it otherwise would.
This sometimes results in behavior that bothers some users.
For example, when paging to a new page of the index, it may be possible for
the lines to be painted on the screen in a random order, rather than from
top to bottom.
<P>
Setting this feature causes <EM>Alpine</EM> to wait for all of the information
to be gathered before it paints the index screen.
Once it collects all of the information, the screen will be painted quickly
from top to bottom.
<P>
This feature is displayed as "Suppress IMAP Envelope Update".
<P>
<DT> <A NAME="quell-lock-failure-warnings"><EM>quell-lock-failure-warnings</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when it encounters a problem
acquiring a mail folder lock. Typically, a secondary file associated
with the mail folder being opened is created as part of the locking
process. On some systems, such file creation has been administratively
precluded by the system configuration.
<P>
<EM>Alpine</EM> issues a warning when such failures occur, which can become bothersome
if the system is configured to disallow such actions. Setting this
feature causes <EM>Alpine</EM> to remain silent when this part of lock creation fails.
<P>
WARNING: systems that have been configured in a way that precludes locking
introduce some risk of mail folder corruption when more than one program
attempts to modify the mail folder. This is most likely to occur to one's
<EM>INBOX</EM> or other "Incoming Message Folder".
<P>
This feature is displayed as "Suppress Lock Failure Warnings".
<P>
<DT> <A NAME="quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>
<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, the
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A>.
<P>
If this option is set, then the normal new-mail checking which happens
while you are composing will not happen for folders other than your
INBOX (which depends on the setting
of "Quell-Mailchecks-Composing-Inbox").
<P>
You might want to set this option if you are experiencing delays while
composing which you think might be related to the speed of the new-mail
checks.
<P>
Even with this option turned on, an occasional new-mail check may be done
in order to keep the server from killing the connection to the folder.
For example, IMAP servers may remove a connection to a folder if there
has been no activity on the connection for 30 minutes or more.
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the
30 minutes is up even though you have turned on this feature to quell
those checks.
<P>
Besides new-mail checks, checkpoint operations on the folders
will also be quelled when you set this option.
The purpose of checkpointing is to write the changes to a folder out to
disk periodically in order to avoid losing those changes when system or
software problems occur.
New-mail checking and checkpointing while you are not composing are not
affected by this option.
<P>
This feature is displayed as "Prevent Mailchecks While Composing Except for INBOX".
<P>
<DT> <A NAME="quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A>
<DD> This option is closely related to the
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A>
option, the
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>.
<P>
If this option is set, then the normal new-mail checking which happens
while you are composing will not happen for your INBOX.
Checking of other folders is controlled in a similar way with the
"Quell-Mailchecks-Composing-Except-Inbox" option.
<P>
You might want to set this option if you are experiencing delays while
composing which you think might be related to the speed of the new-mail
checks.
<P>
Even with this option turned on, an occasional new-mail check may be done
in order to keep the server from killing the connection to the folder.
For example, IMAP servers may remove a connection to a folder if there
has been no activity on the connection for 30 minutes or more.
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the
30 minutes is up even though you have turned on this feature to quell
those checks.
<P>
Besides new-mail checks, checkpoint operations on the INBOX
will also be quelled when you set this option.
The purpose of checkpointing is to write the changes to a folder out to
disk periodically in order to avoid losing those changes when system or
software problems occur.
New-mail checking and checkpointing while you are not composing are not
affected by this option.
<P>
This feature is displayed as "Prevent Mailchecks While Composing for INBOX".
<P>
<DT> <A NAME="quell-maildomain-warning"><EM>quell-maildomain-warning</EM></A>
<DD> When your configuration is set up so that your domain name contains no dots,
it is usually a configuration error.
By default, <EM>Alpine</EM> will warn you about this when you start it up.
You will see a warning message that looks like
<P>
<CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
<P>
If this feature is set, the warning is turned off.
This feature is displayed as "Suppress Maildomain Warning".
<P>
<DT> <A NAME="quell-news-envelope-update"><EM>quell-news-envelope-update</EM></A>
<DD> In the MESSAGE INDEX screen, if the open folder is being accessed
using NNTP (News), <EM>Alpine</EM> normally tries to paint the index lines on the screen
as soon as the information arrives from the NNTP server.
This means that the index information makes it onto the screen more quickly
than it otherwise would.
This sometimes results in behavior that bothers some users.
For example, when paging to a new page of the index, it may be possible for
the lines to be painted on the screen in a random order, rather than from
top to bottom.
<P>
Setting this feature causes <EM>Alpine</EM> to wait for all of the information
to be gathered before it paints the index screen.
Once it collects all of the information, the screen will be painted quickly
from top to bottom.
<P>
This feature is displayed as "Suppress News Envelope Update".
<P>
<DT> <A NAME="quell-partial-fetching"><EM>quell-partial-fetching</EM></A>
<DD> Partial fetching is a feature of the IMAP protocol.
By default, <EM>Alpine</EM>
will use partial fetching when copying the contents of a message or attachment
from the IMAP server to <EM>Alpine</EM>.
This means that the fetch will be done in many
small chunks instead of one big chunk. The main benefit of this approach is
that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
to stop the fetch early. In some cases partial fetching may cause a performance
problem so that the fetching of data takes significantly longer when partial
fetching is used. Turning on this feature will turn off partial fetching.
<P>
This feature is displayed as "Prevent Partial Fetching".
<P>
<DT> <A NAME="quell-personal-name-prompt"><EM>quell-personal-name-prompt</EM></A>
<DD> <EM>PC-Alpine</EM> only. This feature quells the prompting for a
<A HREF="#personal-name">personal-name</A>. This prompt normally happens
before composing a message, and only happens when there is no personal name
already set.
<P>
<DT> <A NAME="quell-server-after-link-in-html"><EM>quell-server-after-link-in-html</EM></A>
<DD> By default, links in HTML text are displayed with the host the link
references appended, within square brackets, to the link text. <EM>Alpine</EM>
does this to help indicate where a link will take you, particularly when
the link text might suggest a different destination.
<P>
Setting this feature will prevent the server name from being appended
to the displayed text.
<P>
This feature is displayed as "Suppress Server After Link in HTML".
<P>
<DT> <A NAME="quell-ssl-largeblocks"><EM>quell-ssl-largeblocks</EM></A>
<DD> This feature (<EM>PC-Alpine</EM> only) changes the behavior of fetching messages
and attachments so that the message data is fetched in chunks no larger
than 12K bytes.
This works around a bug in Microsoft's SSL/TLS support.
Some versions of Microsoft SSL are not able to read full-sized (16K)
SSL/TLS packets.
Some servers will send such packets and this will
cause <EM>PC-Alpine</EM> to crash with the error
<P>
<CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
<P>
Microsoft is aware of the problem and has developed a hotfix for it, but as of
this writing the hotfix has not yet been added to the Knowledge Base.
<P>
This feature is displayed as "Prevent SSL Largeblocks".
<P>
<DT> <A NAME="quell-status-message-beeping"><EM>quell-status-message-beeping</EM></A>
<DD> If set status messages will never emit a beep.
<P>
This feature is displayed as "Suppress Status Message Beeping".
<P>
<DT> <A NAME="quell-timezone-comment-when-sending"><EM>quell-timezone-comment-when-sending</EM></A>
<DD> Normally, when <EM>Alpine</EM> generates a Date header for outgoing mail,
it will try to include the symbolic timezone at the end of the
header inside parentheses.
The symbolic timezone is often three characters long, but on
some operating systems, it may be longer.
Apparently there are some SMTP servers in the world which will reject an
incoming message if it has a Date header longer than about 80 characters.
If this feature is set, the symbolic timezone normally generated by
<EM>Alpine</EM> will not be included.
You probably don't need to worry about this feature unless you run into
the problem described above.
<P>
This feature is displayed as "Suppress Timezone Comment When Sending".
<P>
<DT> <A NAME="quell-user-id-prompt"><EM>quell-user-id-prompt</EM></A>
<DD> <EM>PC-Alpine</EM> only. This feature quells the prompting for a
<A HREF="#user-id">user-id</A>
if the information can be obtained from the login name used
to open the INBOX. Normally, this prompt happens before composing
a message, and only happens when there is no user-id already set
in the configuration.
<P>
With this feature set, composing a message is only possible after
establishing a connection to the INBOX.
<P>
<DT> <A NAME="quell-user-lookup-in-passwd-file"><EM>quell-user-lookup-in-passwd-file</EM></A>
<DD> This feature controls an aspect of
<EM>Alpine</EM>'s Composer, and if needed, will usually be set by the
system manager in <EM>Alpine</EM>'s system-wide configuration file.
Specifically, if this feature is set, <EM>Alpine</EM> will not attempt to look
in the system password file to find a Full Name for the entered address.
<P>
Normally, names you enter into address fields (e.g. To: or Cc:) are
checked against your address book(s) to see if they match an address book
nickname.
Failing that, (in Unix <EM>Alpine</EM>) the name is then checked against
the Unix password file. If the entered name matches a username in the
system password file, <EM>Alpine</EM> extracts the corresponding Full Name information
for that individual, and adds that to the address being entered.
<P>
However, password file matching can have surprising (incorrect) results if
other users of the system do not receive mail at the domain you are using.
That is, if either the <A HREF="#user-domain"><EM>user-domain</EM></A>
or <A HREF="#use-only"><EM>use-only-domain-name</EM></A> option
is set such that the administrative domain of other users on the system
isn't accurately reflected, <EM>Alpine</EM> should be told that a password
file match is coincidental,
and Full Name info will be incorrect.
For example, a
personal name from the password file could get falsely paired with the
entered name as it is turned into an address in the configured domain.
<P>
If you are seeing this behavior, enabling this feature will prevent Unix
<EM>Alpine</EM> from looking up names in the password file to find the Full Name
for incomplete addresses you enter.
<P>
This feature is displayed as "Prevent User Lookup in Password File".
<P>
<DT> <A NAME="quit-without-confirm"><EM>quit-without-confirm</EM></A>
<DD> This feature controls whether or not <EM>Alpine</EM> will ask for confirmation when a
<EM>Quit</EM> command is received.
<P>
This feature is displayed as "Quit Without Confirming".
<P>
<DT> <A NAME="quote-replace-nonflowed"><EM>quote-replace-nonflowed</EM></A>
<DD> This feature, which is only active when
<A HREF="#quote-replace-string">Quote-Replace-String</A> is
also set,
enables quote-replacement on non-flowed messages. It is off
by default because a non-flowed message is more dependent on its format,
and thus quote-replacement may cause less-than-pleasing results.
Setting this feature will cause quote-replacement similar to that of flowed
messages, but with the added possibility of long lines being wrapped
into new lines if the Quote-Replacement-String is longer than the string
it is replacing, which is "> ".
<P>
<DT> <A NAME="reply-always-uses-reply-to"><EM>reply-always-uses-reply-to</EM></A>
<DD> If set, <EM>Alpine</EM>
will not prompt when a message being replied to contains a <EM>Reply-To:</EM>
header value, but will simply use its value (as opposed to using the
<EM>From:</EM> field's value).
<P>
<DT> <A NAME="return-to-inbox-without-confirm"><EM>return-to-inbox-without-confirm</EM></A>
<DD>
Normally, when you use the TAB
command and there are no more folders or newsgroups to visit, you are asked
if you want to return to the INBOX.
If this feature is set you will not be asked.
It will be assumed that you do want to return to the INBOX.
<P>
This feature is displayed as "Return to INBOX Without Confirming".
<P>
<DT> <A NAME="save-aggregates-copy-sequence"><EM>save-aggregates-copy-sequence</EM></A>
<DD> This feature will optimize an aggregate copy operation, if
possible, by issuing a single IMAP <EM>COPY</EM> command with a
list of the messages to be copied.
This feature is set by default.
This may reduce network traffic and elapsed time for the Save.
<EM>However, many IMAP servers (including the UW IMAP server) do
not preserve the order of messages when this optimization is applied.</EM>
If this feature is not set,
<EM>Alpine</EM> will copy each message individually and the order of the
messages will be preserved.
<P>
This feature is displayed as "Save Combines Copies (may be out of order)".
<P>
<DT> <A NAME="save-partial-wo-confirm"><EM>save-partial-msg-without-confirm</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s Save command.
By default, when you Save a message that has some deleted parts, you will
be asked to confirm that you want to Save with a prompt that looks like:
<P>
<CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
<P>
If this feature is set, you will not be asked.
<P>
This feature is displayed as "Save Partial Message Without Confirming".
<P>
<DT> <A NAME="save-will-advance"><EM>save-will-advance</EM></A>
<DD> If set, <EM>Save</EM> will
(in addition to copying the current message to the designated folder) also
advance to the next message.
<P>
<DT> <A NAME="save-will-not-delete"><EM>save-will-not-delete</EM></A>
<DD> If set, <EM>Save</EM> will
not mark the message Deleted (its default behavior) after it has been
copied to the designated folder.
<P>
<DT> <A NAME="save-will-quote"><EM>save-will-quote-leading-froms</EM></A>
<DD> This feature controls an aspect of the <EM>Save</EM> command
(and also the way
outgoing messages are saved to an FCC folder). If set, <EM>Alpine</EM> will add
a leading <CODE>></CODE> character in front of message
lines beginning with "From" when they are
saved to another folder, including lines syntactically
distinguishable from the type of message separator line commonly used on
Unix systems.
<P>
The default behavior is that a <CODE>></CODE> will be prepended only to lines
beginning with "From " that might otherwise be confused with a message
separator line on Unix systems. If <EM>Alpine</EM> is the only mail program you use,
this default is reasonable. If another program you use has trouble
displaying a message with an unquoted From saved by <EM>Alpine</EM>, you should
enable this feature. This feature only applies to the common Unix mailbox
format that uses message separator lines beginning with "From ". If
<EM>Alpine</EM> has been configured to use a different mailbox format (possibly
incompatible with other mail programs), then this issue does not arise,
and the feature is irrelevant.
<P>
<DT> <A NAME="scramble-message-id"><EM>scramble-message-id</EM></A>
<DD> Normally the Message-ID header that <EM>Alpine</EM> generates when sending a message
contains the name of the computer from which the message is being sent.
Some believe that this hostname could be used by spammers or could
be used by others for nefarious purposes.
If this feature is set, that name will be transformed with a simple
Rot13 transformation.
The result will still have the correct syntax for a Message-ID but the
part of the MessageID that is often a domain name will not be an actual
domain name because the letters will be scrambled.
<P>
It is possible (but unlikely?) that some spam detection
software will use that as a reason to reject the mail as spam.
It has also been reported that some spam detection software uses the
fact that there are no dots after the "@" as a reason to reject
messages.
If your <EM>PC-Alpine</EM> Message-ID is using a name without a dot that is because
that is what Windows thinks is your "Full computer name".
The method used to set this varies from one type of Windows to another but
check under Settings -> Control Panel -> System and
look for Network Identification or Computer Name or something similar.
How to set it is beyond the scope of <EM>Alpine</EM>.
<P>
This feature is displayed as "Scramble the Message-ID When Sending".
<P>
<DT> <A NAME="select-without-confirm"><EM>select-without-confirm</EM></A>
<DD> This feature controls an aspect of
<EM>Alpine</EM>'s <EM>Save</EM>, <EM>Export</EM>, and <EM>Goto</EM> commands.
These commands all take text input to specify the name of the folder or
file to be used, but allow you to press <EM>^T</EM> for a
list of possible names.
If set, the selected name will be used immediately, without further
opportunity to confirm or edit the name.
<P>
This feature is displayed as "Select Ctrl-T Foldername Without Confirming".
<P>
<DT> <A NAME="send-without-confirm"><EM>send-without-confirm</EM></A>
<DD> By default, when you send or post a message you will be asked to confirm
with a question that looks something like:
<P>
<CENTER><SAMP>Send message?</SAMP></CENTER>
<P>
If this feature is set, you
will <B>not</B> be prompted to confirm your intent to send
and your message will be sent.
<P>
If this feature is set it disables some possibilities and renders some
other features meaningless.
You will not be able to use
<A HREF="#sending-filters">Sending Filters</A>,
Verbose sending mode,
<A HREF="#enable-background-sending">Background Sending</A>,
<A HREF="#enable-delivery-status-notification">Delivery Status Notifications</A>,
or ^V to turn off the generation of flowed text for this message.
These options are normally available as suboptions in the Send prompt, but
with no Send prompt the options are gone.
<P>
A somewhat related feature is
<A HREF="#quell-extra-post-prompt">quell-extra-post-prompt</A>.
which may be used to eliminate the extra confirmation
question when posting to a newsgroup.
<P>
This feature is displayed as "Send Without Confirming".
<P>
<DT> <A NAME="separate-folder-and-directory-display"><EM>separate-folder-and-directory-display</EM></A>
<DD> This feature affects folder collections wherein a folder
and directory can have the same name. By default, <EM>Alpine</EM> displays them
only once, denoting that it is both a folder and directory by appending
the folder name with the hierarchy character enclosed
in square brackets.
<P>
Enabling this feature will cause <EM>Alpine</EM> to display such names
separately marking the name representing a directory with a trailing
hierarchy delimiter (typically the slash, "/", character).
<P>
The feature also alters the command set slightly. By default, the
right-arrow descends into the directory, while hitting the Return key will
cause the folder by that name to be opened.
<P>
With this feature set, the Return key will open the highlighted folder, or
enter the highlighted directory.
<P>
<DT> <A NAME="show-cursor"><EM>show-cursor</EM></A>
<DD> If set, the system
cursor will move to convenient locations in the displays. For example,
to the beginning of the status field of the highlighted index line, or
to the highlighted word after a successful <EM>WhereIs</EM> command.
It is intended to draw your attention to the <EM>interesting</EM>
spot on the screen.
<P>
<DT> <A NAME="show-plain-text-internally"><EM>show-plain-text-internally</EM></A>
<DD> This feature modifies the method <EM>Alpine</EM> uses to display Text/Plain
MIME attachments from the Attachment Index screen. Normally, the
"View" command searches for any externally defined (usually
via the Mailcap file) viewer,
and displays the selected text within that viewer.
<P>
Enabling this feature causes <EM>Alpine</EM> to ignore any external viewer
settings and always display text with <EM>Alpine</EM>'s internal viewer.
<P>
<DT> <A NAME="show-selected-in-boldface"><EM>show-selected-in-boldface</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s aggregate operation commands;
in particular, the <EM>Select</EM> and <EM>WhereIs</EM> commands.
<EM>Select</EM> and <EM>WhereIs</EM> (with
the <EM>^X</EM> subcommand) will search the current folder
for messages meeting a
specified criteria, and <EM>tag</EM> the resulting
messages with an <EM>X</EM> in the
first column of the applicable lines in the "Folder Index". If this feature
is set, instead of using the <EM>X</EM> to denote a selected message,
<EM>Alpine</EM> will attempt to display those index lines in boldface.
Whether this is preferable to the <EM>X</EM> will depend on personal
taste and the type of terminal being used.
<P>
<DT> <A NAME="show-sort"><EM>show-sort</EM></A>
<DD> If this feature is set and there is sufficient space on the screen,
a short indication of the current sort order will be
added in the titlebar (the top line on the screen), before the name
of the folder.
For example, with the default Arrival sort in effect,
the display would have the characters
<P><CENTER>[A]</CENTER><P>
added between the title of the screen and the folder name.
The letters are the same as the letters you may type to manually
sort a folder with the SortIndex command ($).
The letters in the table below are the ones that may show
up in the titlebar line.
<P>
<TABLE>
<TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
<TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
<TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
<TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
<TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
<TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
<TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
<TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
<TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
<TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
</TABLE>
<P>
If the sort order is Reversed, the letter above will be preceded by the letter
"R", for example
<P><CENTER>[RS]</CENTER><P>
means that a Reverse Subject sort is in effect.
For the case where the sort is in Reverse Arrival order, the "A" is
left out, and just an "R" is shown.
<P><CENTER>[R]</CENTER>
<P>
This feature is displayed as "Show Sort in Titlebar".
<P>
<DT> <A NAME="sig-at-bot"><EM>signature-at-bottom</EM></A>
<DD> If this feature
is set, and a message being <EM>Repl</EM>ied to is being included in
the reply, then the
contents of the signature file (if any) will be inserted after the included
message.
This feature does not affect the results of a <EM>Forward</EM> command.
<P>
<DT> <A NAME="single-column-folder-list"><EM>single-column-folder-list</EM></A>
<DD> If set, the "Folder List" screen will list one folder per line
instead of several per line.
<P>
<DT> <A NAME="slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>
<DD> Normally, the Collapse/Expand Thread command Collapses or Expands the subthread which
starts at the currently highlighted message, if any.
If this feature is set, then the slash command Collapses or Expands the
<EM>entire</EM> current thread instead of just the subthread.
<P>
<DT> <A NAME="smime-dont-do-smime"><EM>smime-dont-do-smime</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
Setting this feature turns off all of <EM>Alpine</EM>'s S/MIME support.
You might want to set this if you are having trouble due to the S/MIME support.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as "S/MIME -- Turn off S/MIME".
<P>
<DT> <A NAME="smime-encrypt-by-default"><EM>smime-encrypt-by-default</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
It affects <EM>Alpine</EM>'s behavior when you send a message.
If this option is set, the "Encrypt" option will default to ON when sending messages.
<P>
Only the default value is affected.
In any case, you may still toggle the Encrypt option on or off before sending
with the "E Encrypt" command (provided you have a the public digital ID
for the recipient).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as "S/MIME -- Encrypt by Default".
<P>
<DT> <A NAME="smime-remember-passphrase"><EM>smime-remember-passphrase</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
If this option is set, you will only have to enter your passphrase for your private key
once during an <EM>Alpine</EM> session.
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as "S/MIME -- Remember S/MIME Passphrase".
<P>
<DT> <A NAME="smime-sign-by-default"><EM>smime-sign-by-default</EM></A>
<DD> UNIX <EM>Alpine</EM> only.
<P>
This feature only has an effect if your version of <EM>Alpine</EM> includes
support for S/MIME.
It affects <EM>Alpine</EM>'s behavior when you send a message.
If this option is set, the "Sign" option will default to ON when sending messages.
<P>
Only the default value is affected.
In any case, you may still toggle the Signing option on or off before sending
with the "G Sign" command (provided you have a personal digital ID
certificate).
<P>
<UL>
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A>
</UL><P>
This feature is displayed as "S/MIME -- Sign by Default".
<P>
<DT> <A NAME="sort-default-fcc-alpha"><EM>sort-default-fcc-alpha</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen.
If set, the default FCC folder will be sorted alphabetically with the other
folders instead of appearing right after the INBOX.
<P>
This feature is displayed as "Sort Default Fcc Folder Alphabetically".
<P>
<DT> <A NAME="sort-default-save-alpha"><EM>sort-default-save-alpha</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen.
If set, the default save folder will be sorted alphabetically with the other
folders instead of appearing right after the INBOX (and default FCC folder).
<P>
This feature is displayed as "Sort Default Save Folder Alphabetically".
<P>
<DT> <A NAME="spell-check-before-sending"><EM>spell-check-before-sending</EM></A>
<DD> When this feature is set, every composed message will be spell-checked before
being sent.
<P>
<DT> <A NAME="store-window-position-in-config"><EM>store-window-position-in-config</EM></A>
<DD> Normally, <EM>PC-Alpine</EM> will store its window size and position in the
Windows Registry.
This is convenient if you want to use the same remote
configuration from more than one PC.
If you use multiple configuration files to start <EM>PC-Alpine</EM>, you may want
to store the window size and position in the configuration file instead
of in the Registry.
Setting this feature causes that to happen.
<P>
<DT> <A NAME="strip-from-sigdashes-on-reply"><EM>strip-from-sigdashes-on-reply</EM></A>
<DD> This feature doesn't do anything if the feature
<A HREF="#enable-sigdashes"><EM>enable-sigdashes</EM></A> is turned on.
However, if the <EM>enable-sigdashes</EM> feature is not turned on,
then turning on this feature enables support for the convention
of not including text beyond the sigdashes line when Replying or Following
up to a message and including the text of that message.
<P>
In other words, this is a way to turn on the signature stripping behavior
without also turning on the dashes-adding behavior.
<P>
<DT> <A NAME="strip-whitespace-before-send"><EM>strip-whitespace-before=send</EM></A>
<DD> Trailing whitespace is not stripped from
a message before sending. Trailing whitespace should have no effect on an
email message, and in flowed text can aid in delimiting paragraphs.
However, the old behavior of stripping trailing whitespace was in place
to better deal with older clients that couldn't handle certain types of
text encodings. This feature restores the old behavior
<P>
Trailing whitespace is of aid to flowed-text-formatted messages, which are
generated by default but can be turned off via the
<A HREF="#quell-flowed-text">quell-flowed-text</A> feature.
strip-whitespace-before-send also has the effect of turning off sending
of flowed text.
<P>
This feature is displayed as "Strip Whitespace Before Sending".
<P>
<DT> <A NAME="suppress-asterisks-in-password-prompt"><EM>suppress-asterisks-in-password-prompt</EM></A>
<DD> When you are running <EM>Alpine</EM> you will sometimes be asked for a password
in a prompt on the third line from the bottom of the screen.
Normally each password character you type will cause an asterisk to echo
on the screen. That gives you some feedback to know that your typing is
being recognized.
There is a very slight security risk in doing it this way because someone
watching over your shoulder might be able to see how many characters there
are in your password.
If you'd like to suppress the echoing of the asterisks set this feature.
<P>
<DT> <A NAME="suppress-user-agent-when-sending"><EM>suppress-user-agent-when-sending</EM></A>
<DD> If this feature is set then <EM>Alpine</EM> will not generate a
<CODE>User-Agent</CODE> header in outgoing messages.
<P>
<DT> <A NAME="tab-checks-recent"><EM>tab-checks-recent</EM></A>
<DD> In a FOLDER LIST screen, the TAB key usually just changes which
folder is highlighted.
If this feature is set, then the TAB key will cause the number of
recent messages and the total number of messages in the highlighted folder
to be displayed instead.
<P>
This feature is displayed as "Tab Checks for Recent Messages".
<P>
<DT> <A NAME="tab-uses-unseen-for-next-folder"><EM>tab-uses-unseen-for-next-folder</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when using the TAB
NextNew Command
to move from one folder to the next.
<EM>Alpine</EM>'s usual behavior is to search for folders
with <EM>Recent</EM> messages in them.
Recent messages are messages which have arrived since the last time the
folder was opened.
<P>
Setting this feature causes <EM>Alpine</EM> to search for <EM>Unseen</EM>
messages instead of Recent messages.
Unseen messages remain Unseen until you view them (or flag then as Seen with
the Flag Command).
Setting this feature allows you to locate messages you have not read
instead of only recently received messages.
When this feature is set, the feature
<A HREF="#enable-fast-recent-test">Enable-Fast-Recent-Test</A>
will have no effect, so the checking may be slower.
<P>
Another reason why you might want to use this feature is that <EM>Alpine</EM> sometimes
opens folders implicitly behind the scenes, and this clears the
Recent status of all messages in the folder.
One example where this happens is when Saving or filtering a
message to another folder.
If that message has some <A HREF="#keywords">keywords</A>
set, then because of some shortcomings
in the IMAP specification, the best way to ensure that those keywords are
still set in the saved copy of the message is to open the folder and
set the keywords explicitly.
Because this clears the Recent status of all messages in that folder the
folder will not be found by the NextNew command unless this feature is set.
<P>
<DT> <A NAME="tab-visits-next-new-message-only"><EM>tab-visits-next-new-message-only</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when using the <EM>TAB</EM>
key to move from one message to the next.
<EM>Alpine</EM>'s usual behavior is to select the next
<EM>Unread</EM> message or message flagged as <EM>Important</EM>.
<P>
Setting this feature causes <EM>Alpine</EM> to skip the
messages flagged as <EM>Important</EM>,
and select <EM>Unread</EM> messages exclusively.
Tab behavior when there are no
new messages left to select remains unchanged.
<P>
<DT> <A NAME="termdef-takes-precedence"><EM>termdef-takes-precedence</EM></A>
<DD> This feature may affect <EM>Alpine</EM>'s low-level input routines. Termcap (or
terminfo, depending on how your copy of <EM>Alpine</EM> was compiled and linked)
is the name of the database which describes terminal capabilities. In
particular, it describes the sequences of characters that various keys
will emit.
<P>
An example would be the Up Arrow key on the keyboard. Up
Arrow is not a distinct character on most Unix systems. When you press
the Up Arrow key a short sequence of characters are produced. This
sequence is supposed to be described in the termcap database by the
"ku" capability (or by the "kcuu1" capability if you
are using terminfo instead of termcap).
<P>
By default, <EM>Alpine</EM> defines some terminal
escape sequences that are commonly used. For example, the sequence
"ESC O A" is recognized as an Up Arrow key. The sequence
"ESC [ A"
is also recognized as an Up Arrow key. These are chosen because common
terminals like VT100's or ANSI standard terminals produce these
sequences when you press the Up Arrow key.
<P>
If your system's termcap
(terminfo) database assigns some other function to the sequence
"ESC O A"
it is usually ignored by <EM>Alpine</EM>. Also, if your termcap (terminfo)
database assigns a sequence which doesn't begin with an escape
character (<SAMP>ESC</SAMP>) it is usually ignored by <EM>Alpine</EM>.
This usually works fine
because most terminals emit the escape sequences that <EM>Alpine</EM> has defined
by default. We have also found that it is usually better to have these
defaults take precedence over the definitions contained in the database
because the defaults are more likely to be correct than the database.
<P>
There are some terminals where this breaks down. If you want <EM>Alpine</EM> to
believe the definitions given in your termcap (terminfo) database in
preference to the defaults the <EM>Alpine</EM> itself sets up, then you may turn
this feature on. Then, sequences of characters which are defined in
both termcap (terminfo) and in <EM>Alpine</EM>'s set of defaults will be
interpreted the way that termcap (terminfo) says they should be
interpreted. Also, if your terminal capabilities database assigns a
sequence which doesn't begin with escape, it will not be ignored.
<P>
<DT> <A NAME="thread-index-shows-important-color"><EM>thread-index-shows-important-color</EM></A>
<DD> This option affects only the THREAD INDEX screen.
Whether or not you ever see a THREAD INDEX screen depends on the setting
of the configuration option
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A>
and on the sort order of the index.
If a message within a thread is flagged as Important
and this option is set, then
the entire line in the THREAD INDEX will be colored the color of the
Index-important Symbol, which can be set using the
Setup Kolor screen.
<P>
<DT> <A NAME="try-alternative-authentication-driver-first"><EM>try-alternative-authentication-driver-first</EM></A>
<DD> This feature affects how <EM>Alpine</EM> connects to IMAP servers.
It's utility has largely been overtaken by events,
but it may still be useful in some circumstances.
If you only connect to modern IMAP servers that support
"TLS" you can ignore this feature.
<P>
Details:
<P>
By default, <EM>Alpine</EM> will attempt to connect to an IMAP server on the
normal IMAP service port (143), and if the server offers "Transport Layer
Security" (TLS) and <EM>Alpine</EM> has been compiled with encryption capability,
then a secure (encrypted) session will be negotiated.
<P>
With this feature enabled, before connecting on the normal IMAP port, <EM>Alpine</EM>
will first attempt to connect to an alternate IMAP service port (993) used
specifically for encrypted IMAP sessions via the Secure Sockets Layer
(SSL) method.
If the SSL attempt fails, <EM>Alpine</EM> will then try the default
behavior described in the previous paragraph.
<P>
TLS negotiation on the normal port is preferred, and supersedes the use of
SSL on port 993, but older servers may not provide TLS support.
This feature may be convenient when accessing IMAP servers that do not support
TLS, but do support SSL connections on port 993.
However, it is important to understand that with this feature enabled,
<EM>Alpine</EM> will <EM>attempt</EM> to make a secure connection if that is possible,
but it will proceed to make an insecure connection if that is the only
option offered by the server, or if the <EM>Alpine</EM> in question has been built
without encryption capability.
<P>
Note that this feature specifies a per-user (or system-wide) default
behavior, but host/folder specification flags may be used to control the
behavior of any specific connection.
This feature interacts with some of
the possible host/folder path specification flags as follows:
<P>
The <SAMP>/tls</SAMP> host flag, for example,
<P>
<CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
<P>
will over-ride this feature for the specified host by bypassing the
SSL connection attempt.
Moreover, with <SAMP>/tls</SAMP> specified,
the connection attempt will fail if the
service on port 143 does not offer TLS support.
<P>
The <SAMP>/ssl</SAMP> host flag, for example,
<P>
<CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
<P>
will insist on an SSL connection for the specified host,
and will fail if the SSL service on port 993 is not available.
<EM>Alpine</EM> will not subsequently retry a connection
on port 143 if <SAMP>/ssl</SAMP> is specified.
<P>
<DT> <A NAME="unselect-will-not-advance"><EM>unselect-will-not-advance</EM></A>
<DD> Normally, when the Unselect current message command (:) is typed when the
current message is selected, the message will be unselected and the next
message will become the current message.
If this feature is set, the cursor will not advance to the next message.
Instead, the current message will remain the current message after
unselecting.
<P>
<DT> <A NAME="use-current-dir"><EM>use-current-dir</EM></A>
<DD> This feature controls an aspect of several commands. If set, your
"current working directory" will be used instead of your home directory
for all of the following operations:
<UL>
<LI> <EM>Export</EM> in the "Folder Index" and "Message Text" screens
<LI> Attachment <EM>Save</EM> in the "Message Text" and "Attachment Text" screens
<LI> <EM>^R</EM> file inclusion in the Composer
<LI> <EM>^J</EM> file attachment in the Composer
</UL>
<P>
This feature is displayed as "Use Current Directory".
<P>
<DT> <A NAME="use-function-keys"><EM>use-function-keys</EM></A>
<DD> This feature specifies that <EM>Alpine</EM> will
respond to function keys instead of
the normal single-letter commands. In this mode, the key menus at the
bottom of each screen will show function key designations instead of the
normal mnemonic key.
<P>
<DT> <A NAME="use-reg-start-rule"><EM>use-regular-startup-rule-for-stayopen-folders</EM></A>
<DD> This feature affects which message is selected as the current message
when you enter a
<A HREF="#stay-open-folders">Stay Open</A> folder.
<P>
Normally, the starting position for an incoming folder (which most Stay Open
folders will likely be) is controlled by the
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>.
However, if a folder is a Stay Open folder, when you re-enter the folder
after the first time the current message will be the same as it was when
you left the folder.
An exception is made if you use the TAB command to get to the folder.
In that case, the message number will be incremented by one from what it
was when you left the folder.
<P>
The above special behavior is thought to be useful.
However, it is special and different from what you might at first expect.
If this feature is set, then Stay Open folders will not be treated specially
as far as the startup rule is concerned.
<P>
<DT> <A NAME="use-resent-to-in-rules"><EM>use-resent-to-in-rules</EM></A>
<DD> This feature is turned off by default because turning it on causes problems
with some deficient IMAP servers.
In <EM>Alpine</EM> Filters and other types of Rules, if the
Pattern
contains a To header pattern and this feature is turned on,
then a check is made in the message to see
if a Resent-To header is present, and that is used instead of the To header.
If this feature is not turned on, then the regular To header will always
be used.
<P>
<DT> <A NAME="use-sender-not-x-sender"><EM>use-sender-not-x-sender</EM></A>
<DD> Normally <EM>Alpine</EM> on Unix adds a header line labeled <EM>X-X-Sender</EM>,
if the sender is different from the <EM>From:</EM> line.
<P>
The standard specifies that this header
line should be labeled <EM>Sender</EM>, not <EM>X-X-Sender</EM>.
Setting this feature causes
<EM>Sender</EM> to be used instead of <EM>X-X-Sender</EM>. The standard also states
that the data associated with this header field should not be used as a Reply address.
Unfortunately, certain implementations of mail list management servers will use the
Sender address for such purposes. These implementations often even recognize the
<EM>X-Sender</EM> fields as being equivalent to the <EM>Sender</EM> field, and use it
if present. This is why <EM>Alpine</EM> defaults to <EM>X-X-Sender</EM>.
<P>
Note, <EM>PC-Alpine</EM> always adds
either an <EM>X-X-Sender</EM> line if there is an open, remote mailbox, or an
<EM>X-Warning: UNAuthenticated User</EM> otherwise
<P>
This feature is displayed as "Use Sender Instead of X-X-Sender".
<P>
<DT> <A NAME="use-subshell-for-suspend"><EM>use-subshell-for-suspend</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when process suspension
is enabled and then activated via the <EM>^Z</EM> key.
<EM>Alpine</EM> suspension allows one to
temporarily interact with the operating system command "shell" without
quitting <EM>Alpine</EM>,
and then subsequently resume the still-active <EM>Alpine</EM> session.
<P>
When the <EM>enable-suspend</EM> feature is set and subsequently the
<EM>^Z</EM> key is pressed,
<EM>Alpine</EM> will normally suspend itself and return temporary
control to <EM>Alpine</EM>'s parent shell process.
However, if this feature is set, <EM>Alpine</EM> will instead create an
inferior subshell process.
This is useful when the parent process is not intended to be used
interactively.
Examples include invoking <EM>Alpine</EM> via the <CODE>-e</CODE> argument
of the Unix <EM>xterm</EM> program, or via a menu system.
<P>
Note that one typically resumes a suspended <EM>Alpine</EM> by entering the Unix
<EM>fg</EM> command, but if this feature is set, it will be necessary to enter
the <EM>exit</EM> command instead.
<P>
<DT> <A NAME="use-system-translation"><EM>use-system-translation</EM></A>
<DD> UNIX <EM>Alpine</EM> only. <EM>Alpine</EM> normally uses its own internal software to convert between the multi-byte
representation of characters and the Unicode representation of those
same characters
( see the section on <A HREF="low-level.html#char-set">International Character Sets</EM></A>).
It converts from the multi-byte characters your keyboard produces to Unicode,
and from Unicode to the multi-byte characters your display expects.
Alpine also uses its own internal software to decide how much space on
the screen a particular Unicode character will occupy.
<P>
Setting this feature tells <EM>Alpine</EM> to use the system-supplied routines to
perform these tasks instead.
In particular there are three tasks and three system routines that will
be used for these tasks.
<P>
To convert from multi-byte to Unicode the routine
<P>
<CENTER><SAMP>mbstowcs</SAMP></CENTER>
<P>
is used.
To convert from Unicode to multi-byte the routine
<P>
<CENTER><SAMP>wcrtomb</SAMP></CENTER>
<P>
is used.
And to find the screen width a particular Unicode character will
occupy the routine used is
<P>
<CENTER><SAMP>wcwidth</SAMP></CENTER>
<P>
This feature has been only lightly tested.
The internal routines should normally be used unless you run into
a problem that you think may be solved by using the system routines.
Note that your environment needs to be set up for these
routines to work correctly.
In particular, the LANG or LC_CTYPE variable in your environment will
need to be set.
<P>
<DT> <A NAME="vertical-folder-list"><EM>vertical-folder-list</EM></A>
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen. If set,
the folders will be listed alphabetically down the columns rather
than across the columns as is the default.
<P>
This feature is displayed as "Use Vertical Folder List".
<P>
<DT> <A NAME="warn-if-blank-subject"><EM>warn-if-blank-subject</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being
composed.
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent
has a subject or not.
If not, you will be asked if you want to send the message anyway.
<P>
<DT> <A NAME="warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A>
<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being
composed.
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent
has either a To address, a Cc address, or a Newsgroup.
If none of these is set,
you will be asked if you want to send the message anyway.
<P>
This feature is closely related to
<A HREF="#fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A>.
<EM>Alpine</EM> will normally ask if you want to copy a message only to the Fcc.
This feature also applies to cases where there is a Bcc but still no To, Cc,
or Newsgroup.
If the Fcc-Only-Without-Confirm feature is set and you are sending a
message with only an Fcc, then you won't be asked about sending with
a blank To and Cc and Newsgroups header even if this feature is set.
Similarly, if you have already been asked if you want to send to the Fcc
only and you have answered Yes, then you won't be asked again about sending with
blank To, Cc, and Newsgroups headers even if this feature is set.
<P>
</DL>
<P>
<H2><A NAME="hidden-config">Hidden Config Variables and Features</A></H2>
There are several configuration variables and features which are normally hidden
from the user. That is, they don't appear on any of the configuration
screens. Some of these are suppressed because they are intended to be used
by system administrators, and in fact may only be set in system-wide
configuration files. Others are available to users but are thought to be
of such little value to most users that their presence on the Config
screens would cause more confusion than help.
Others are hidden in the Setup/Config screen because they are normally
configured in one of the other configuration screens. For example, all
of the colors are hidden because the normal way to configure colors is
through Setup/Colors not Setup/Config.
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A>
to cause most of these hidden variables and features to show up at the bottom
of the Setup/Config screen.
<H3>Hidden Variables Not Settable by Users</H3>
These variables are settable only in system-wide configuration files.
<UL>
<LI> <A HREF="#bugs-add">bugs-additional-data</A>
<LI> <A HREF="#bugs">bugs-address</A>
<LI> <A HREF="#bugs">bugs-fullname</A>
<LI> <A HREF="#forced-abook">forced-abook-entry</A>
<LI> <A HREF="#kblock-count">kblock-passwd-count</A>
<LI> <A HREF="#bugs">local-address</A>
<LI> <A HREF="#bugs">local-fullname</A>
<LI> <A HREF="#mail-directory">mail-directory</A>
<LI> <A HREF="#standard-printer">standard-printer</A>
<LI> <A HREF="#bugs">suggest-address</A>
<LI> <A HREF="#bugs">suggest-fullname</A>
</UL>
<H3>Hidden Variables Which are Settable by Users</H3>
These variables are not shown to users but are settable by means
of hand editing the personal configuration file. This first group
is usually maintained by <EM>Alpine</EM> and there will usually
be no reason to edit them by hand.
<UL>
<LI> <A HREF="#last-version-used">last-version-used</A>
<LI> <A HREF="#patterns-filters2">patterns-filters2</A>
<LI> <A HREF="#patterns-indexcolors">patterns-indexcolors</A>
<LI> <A HREF="#patterns-roles">patterns-roles</A>
<LI> <A HREF="#patterns-scores2">patterns-scores2</A>
<LI> <A HREF="#remote-abook-metafile">remote-abook-metafile</A>
</UL>
<P>
This group is usually correct but may be changed by system managers or
users in special cases.
<UL>
<LI> <A HREF="#disable-these-auths">disable-these-authenticators</A>
<LI> <A HREF="#disable-these-drivers">disable-these-drivers</A>
<LI> <A HREF="#last-time">last-time-prune-questioned</A>
<LI> <A HREF="#new-version-threshold">new-version-threshold</A>
<LI> <A HREF="#remote-abook-history">remote-abook-history</A>
<LI> <A HREF="#remote-abook-validity">remote-abook-validity</A>
<LI> <A HREF="#rsh-command">rsh-command</A>
<LI> <A HREF="#rsh-open-timeout">rsh-open-timeout</A>
<LI> <A HREF="#rsh-path">rsh-path</A>
<LI> <A HREF="#sendmail-path">sendmail-path</A>
<LI> <A HREF="#ssh-command">ssh-command</A>
<LI> <A HREF="#ssh-open-timeout">ssh-open-timeout</A>
<LI> <A HREF="#ssh-path">ssh-path</A>
<LI> <A HREF="#tcp-open-timeout">tcp-open-timeout</A>
<LI> <A HREF="#tcp-query-timeout">tcp-query-timeout</A>
<LI> <A HREF="#tcp-read-warning-timeout">tcp-read-warning-timeout</A>
<LI> <A HREF="#tcp-write-warning-timeout">tcp-write-warning-timeout</A>
<LI> <A HREF="#use-function-keys">use-function-keys</A>
</UL>
<P>
System managers are usually interested in setting these in the system-wide
configuration files, though users may set them if they wish.
<UL>
<LI> <A HREF="#operating-dir">operating-dir</A>
<LI> <A HREF="#user-input">user-input-timeout</A>
</UL>
<P>
<H3>Hidden Features Which are Settable by Users</H3>
These are <EM>features</EM> (as opposed to variables) which users or system
administrators may set. Some of them only make sense for administrators.
To turn these on manually, the configuration file should be edited and the
feature added to the <EM>feature-list</EM> variable.
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A>
to cause these hidden features to show up in the Setup/Config screen.
They will be at the bottom of the screen.
<UL>
<LI> <A HREF="#disable-config-cmd">disable-config-cmd</A>
<LI> <A HREF="#disable-kblock">disable-keyboard-lock-cmd</A>
<LI> <A HREF="#disable-password-cmd">disable-password-cmd</A>
<LI> <A HREF="#disable-pipes-in-sigs">disable-pipes-in-sigs</A>
<LI> <A HREF="#disable-pipes-in-templates">disable-pipes-in-templates</A>
<LI> <A HREF="#disable-roles-setup-cmd">disable-roles-setup-cmd</A>
<LI> <A HREF="#disable-roles-sig-edit">disable-roles-sig-edit</A>
<LI> <A HREF="#disable-roles-template-edit">disable-roles-template-edit</A>
<LI> <A HREF="#disable-setlocale-collate">disable-setlocale-collate</A>
<LI> <A HREF="#disable-shared-namespaces">disable-shared-namespaces</A>
<LI> <A HREF="#disable-signature-edit-cmd">disable-signature-edit-cmd</A>
</UL>
<P>
<H2><A NAME="ret-var">Retired Variables and Features</A></H2>
Variables and features that are no longer used by the current <EM>Alpine</EM> version.
When an obsolete variable is encountered, its value is applied to any new
corresponding setting.
The replaced values include:
<P>
<DL COMPACT>
<DT> <EM>character-set</EM>
<DD> Replaced by three separate variables:
<EM>display-character-set</EM>,
<EM>keyboard-character-set</EM>, and
<EM>posting-character-set</EM>.
<DT> <EM>compose-mime</EM>
<DT> <EM>elm-style-save</EM>
<DD> Replaced by <EM>saved-msg-name-rule</EM>
<DT> <EM>feature-level</EM>
<DD> Replaced by <EM>feature-list.</EM>
<DT> <EM>header-in-reply</EM>
<DD> Replaced by <EM>include-header-in-reply</EM> in the
<EM>feature-list.</EM>
<DT> <EM>old-style-reply</EM>
<DD> Replaced by <EM>signature-at-bottom</EM> in the
<EM>feature-list.</EM>
<DT> <EM>use-old-unix-format-write</EM>
<DD> No replacement.
<DT> <EM>patterns</EM>
<DD> Replaced by four separate patterns variables:
<EM>patterns-roles</EM>,
<EM>patterns-filters</EM>,
<EM>patterns-scores</EM>, and
<EM>patterns-indexcolors</EM>.
Since then, <EM>patterns-filters</EM> has also become obsolete and is replaced
by <EM>patterns-filters2</EM>; <EM>patterns-scores</EM> is replaced by
<EM>patterns-scores2</EM>.
<DT> <EM>save-by-sender</EM>
<DD> Replaced by <EM>saved-msg-name-rule.</EM>
<DT> <EM>show-all-characters</EM>
<DD> No replacement, it always works this way now.
</DL>
<P>
<H2><A NAME="index-tokens"></A>Tokens for Index and Replying</H2>
This set of special tokens may be used in the
<A HREF="#index-format"><EM>index-format</EM></A> option,
in the <A HREF="#reply-leadin"><EM>reply-leadin</EM></A> option,
in signature files,
in template files used in
<A HREF="#role-config"><EM>roles</EM></A>,
and in the folder name that is the target of a Filter Rule.
Some of them aren't available in all situations.
<P>
The tokens are used as they appear below for the <EM>Index-Format</EM>
option, but they must be surrounded by underscores for the
<EM>Reply-Leadin</EM> option, in signature and template files,
and in the target of Filter Rules.
<P>
<H3><EM>Tokens Available for all Cases (except Filter Rules)</EM></H3>
<DL>
<DT>SUBJECT</DT>
<DD>
This token represents the Subject the sender gave the message.
Alternatives for use in the index screen are
SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
You may color the subject text in the MESSAGE INDEX screen differently by using the
<A HREF="#index-subject-color">Index Subject Color</A>
and the
<A HREF="#index-opening-color">Index Opening Color</A>.
options available from
the Setup Kolor screen.
</DD>
<DT>FROM</DT>
<DD>
This token represents the personal name (or email address if the name
is unavailable) of the person specified in the message's "From:"
header field.
You may color the from text in the MESSAGE INDEX screen differently by using the
<A HREF="#index-from-color">Index From Color</A>
option available from the Setup Kolor screen.
</DD>
<DT>ADDRESS</DT>
<DD>
This is similar to the "FROM" token, only it is always the
email address, never the personal name.
For example, "mailbox@domain".
</DD>
<DT>MAILBOX</DT>
<DD>
This is the same as the "ADDRESS" except that the
domain part of the address is left off.
For example, "mailbox".
</DD>
<DT>SENDER</DT>
<DD>
This token represents the personal name (or email address) of the person
listed in the message's "Sender:" header field.
</DD>
<DT>TO</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's "To:" header field.
</DD>
<DT>NEWSANDTO</DT>
<DD>
This token represents the newsgroups from the
message's "Newsgroups:" header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's "To:" header field.
</DD>
<DT>TOANDNEWS</DT>
<DD>
Same as "NEWSANDTO" except in the opposite order.
</DD>
<DT>NEWS</DT>
<DD>
This token represents the newsgroups from the
message's "Newsgroups:" header field.
</DD>
<DT>CC</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's "Cc:" header field.
</DD>
<DT>RECIPS</DT>
<DD>
This token represents the personal names (or email addresses if the names
are unavailable) of the persons specified in both the
message's "To:" header field and
the message's "Cc:" header field.
</DD>
<DT>NEWSANDRECIPS</DT>
<DD>
This token represents the newsgroups from the
message's "Newsgroups:" header field <EM>and</EM>
the personal names (or email addresses if the names
are unavailable) of the persons specified in the
message's "To:" and "Cc:" header fields.
</DD>
<DT>RECIPSANDNEWS</DT>
<DD>
Same as "NEWSANDRECIPS" except in the opposite order.
</DD>
<DT>INIT</DT>
<DD>
This token represents the initials from the personal name
of the person specified in the message's "From:"
header field.
If there is no personal name, it is blank.
</DD>
<DT>DATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format MMM DD. For example, "Oct 23".
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>,
which adjusts for the timezone the message was sent from,
may have an affect on the value of this token as well as the values of
all of the other DATE or TIME tokens.
Some of the DATE and TIME tokens are displayed in a locale-specific
way unless the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is set.
</DD>
<DT>SMARTDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It is "Today" if the message was sent today,
"Yesterday" for yesterday,
"Wednesday" if it was last Wednesday, and so on. If the
message is from last year and is more than six months old it includes the year, as well.
There is no adjustment made for different time zones, so you'll get
the day the message was sent according to the time zone the sender
was in.
See the SMARTDATE alternatives below, as well.
</DD>
<DT>SMARTTIME</DT>
<DD>
This token represents the most relevant elements of the date on which
the message was sent (according to the "Date" header field),
in a compact form. If the message was sent today, only the time is used
(e.g. "9:22am", "10:07pm"); if it was sent during
the past week, the day of the week and the hour are used
(e.g. "Wed09am", "Thu10pm"); other dates are
given as date, month, and year (e.g. "23Aug00",
"9Apr98").
There is no adjustment made for different time zones, so you'll get
the day/time the message was sent according to the time zone the sender
was in.
</DD>
<DT>SMARTDATETIME</DT>
<DD>
This is a combination of SMARTDATE and SMARTTIME.
It is SMARTDATE unless the SMARTDATE value is "Today", in which
case it is SMARTTIME.
See the SMARTDATETIME alternatives below, as well.
</DD>
<DT>DATEISO</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format YYYY-MM-DD. For example, "1998-10-23".
</DD>
<DT>SHORTDATEISO</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format YY-MM-DD. For example, "98-10-23".
</DD>
<DT>SHORTDATE1</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format MM/DD/YY. For example, "10/23/98".
</DD>
<DT>SHORTDATE2</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format DD/MM/YY. For example, "23/10/98".
</DD>
<DT>SHORTDATE3</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format DD.MM.YY. For example, "23.10.98".
</DD>
<DT>SHORTDATE4</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format YY.MM.DD. For example, "98.10.23".
</DD>
<DT>LONGDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
</DD>
<DT>SMARTDATE alternatives</DT>
<DD>
There are several versions of SMARTDATE which are all the same except
for the way they format dates far in the past.
SMARTDATE formats the date using the information from your locale settings
to format the date string. It may end up formatting dates so that they look
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>
may have an affect on the values of these tokens.
If you want more control you may use one of the following.
<DL>
<DT>SMARTDATE</DT> <DD>If the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set
then this will be locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.
If the Disable-Index-Locale-Dates option is set then this is equivalent
to SMARTDATES1.</DD>
<DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
<DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
<DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
<DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
<DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
<DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
</DL>
</DD>
<DT>SMARTDATETIME alternatives</DT>
<DD>
There are several versions of SMARTDATETIME which are all very similar.
The ones which end in 24 use a 24-hour clock for Today's messages instead
of a 12-hour clock.
The other variation is
for the way they format dates far in the past.
SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
to format the date string. It may end up formatting dates so that they look
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
The feature
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>
may have an affect on the values of these tokens.
The possible choices are:
<DL>
<DT>SMARTDATETIME</DT> <DD>Locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.</DD>
<DT>SMARTDATETIME</DT> <DD>If the option
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set
then this will be locale specific. Control this with the
LC_TIME locale setting on a UNIX system. On Windows
the Regional Options control panel may be used to set the Short date
format. At the programming level, the strftime routine is what <EM>Alpine</EM>
uses to print the date.
If the Disable-Index-Locale-Dates option is set then this is equivalent
to SMARTDATETIMES1.</DD>
<DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
<DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
<DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
<DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
<DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
<DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
<DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
<DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
</DL>
</DD>
<DT>DAYDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It looks like "Sat, 23 Oct 1998".
This token is never converted in any locale-specific way.
</DD>
<DT>PREFDATE</DT>
<DD>
This token represents the date on which the message was sent, according
to the "Date" header field.
It is your operating system's idea of the preferred date representation for the current locale.
Internally it uses the %x version of the date from the strftime routine.
</DD>
<DT>PREFTIME</DT>
<DD>
This token represents the time at which the message was sent, according
to the "Date" header field.
It is the preferred time representation for the current locale.
Internally it uses the %X version of the time from the strftime routine.
</DD>
<DT>PREFDATETIME</DT>
<DD>
This token represents the date and time at which the message was sent, according
to the "Date" header field.
It is the preferred date and time representation for the current locale.
Internally it uses the %c version of the time from the strftime routine.
</DD>
<DT>DAY</DT>
<DD>
This token represents the day of the month on which the message was sent,
according to the "Date" header field.
For example, "23" or "9".
</DD>
<DT>DAY2DIGIT</DT>
<DD>
This token represents the day of the month on which the message was sent,
according to the "Date" header field.
For example, "23" or "09".
It is always 2 digits.
</DD>
<DT>DAYORDINAL</DT>
<DD>
This token represents the ordinal number which is the day of
the month on which the message was sent,
according to the "Date" header field.
For example, "23rd" or "9th".
</DD>
<DT>DAYOFWEEK</DT>
<DD>
This token represents the day of the week on which the message was sent,
according to the "Date" header field.
For example, "Sunday" or "Wednesday".
</DD>
<DT>DAYOFWEEKABBREV</DT>
<DD>
This token represents the day of the week on which the message was sent,
according to the "Date" header field.
For example, "Sun" or "Wed".
</DD>
<DT>MONTHABBREV</DT>
<DD>
This token represents the month the message was sent, according
to the "Date" header field.
For example, "Oct".
</DD>
<DT>MONTHLONG</DT>
<DD>
This token represents the month in which the message was sent, according
to the "Date" header field.
For example, "October".
</DD>
<DT>MONTH</DT>
<DD>
This token represents the month in which the message was sent, according
to the "Date" header field.
For example, "10" or "9".
</DD>
<DT>MONTH2DIGIT</DT>
<DD>
This token represents the month in which the message was sent, according
to the "Date" header field.
For example, "10" or "09".
It is always 2 digits.
</DD>
<DT>YEAR</DT>
<DD>
This token represents the year the message was sent, according
to the "Date" header field.
For example, "1998" or "2001".
</DD>
<DT>YEAR2DIGIT</DT>
<DD>
This token represents the year the message was sent, according
to the "Date" header field.
For example, "98" or "01".
It is always 2 digits.
</DD>
<DT>TIME24</DT>
<DD>
This token represents the time at which the message was sent, according
to the "Date" header field.
There is no adjustment made for different time zones, so you'll get
the time the message was sent according to the time zone the sender
was in.
It has the format HH:MM. For example, "17:28".
</DD>
<DT>TIME12</DT>
<DD>
This token represents the time at which the message was sent, according
to the "Date" header field.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, "5:28pm" or "11:13am".
</DD>
<DT>TIMEZONE</DT>
<DD>
This token represents the numeric timezone from
the "Date" header field.
It has the format [+-]HHMM. For example, "-0800".
</DD>
</DL>
<P>
<H3><EM>Tokens Available Only for Index-Format</EM></H3>
<DL>
<DT>MSGNO</DT>
<DD>
This token represents the message's current position in the folder which,
of course, may change as the folder is sorted or new mail arrives.
</DD>
<DT>STATUS</DT>
<DD>
This token represents a three character wide field displaying various
aspects of the message's state.
The first character is either blank,
a '*' for message marked Important, or a '+' indicating a message
addressed directly to you (as opposed to your having received it via a
mailing list, for example).
When the feature
<A HREF="#mark-for-cc"><EM>mark-for-cc</EM></A>
is set, if the first character would have been
blank then it will instead be a '-' if the message is cc'd to you.
The second character is typically blank,
though the arrow cursor may occupy it if either the
<A HREF="#assume-slow-link"><EM>assume-slow-link</EM></A>
or the
<A HREF="#force-arrow-cursor"><EM>force-arrow-cursor</EM></A> feature
is set (or you actually are on a slow link).
The third character is either D (Deleted),
A (Answered),
N (New), or blank.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then this token refers to all of the messages in the collapsed portion of
the thread instead of just the top message.
The first character will be a '*' if <EM>any</EM> of the messages in the thread
are marked Important, else a '+' if any of the messages are addressed
to you, else a '-' if any of the messages are cc'd to you.
The third character will be a 'D' if <EM>all</EM> of the messages
in the collapsed thread are marked deleted,
an 'A' if <EM>all</EM> of the messages
in the collapsed thread are marked answered,
it will be an 'N' if any of
the messages are undeleted and unseen, and it will be blank otherwise.
</DD>
<DT>FULLSTATUS</DT>
<DD>
This token represents a less abbreviated alternative
to the "STATUS" token.
It is six characters wide.
The first character is '+', '-', or blank, the
second blank, the third either '*' or blank, the fourth
N or blank,
the fifth A
or blank, and the sixth character is
either D or
blank.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then this token refers to all of the messages in the collapsed portion of
the thread instead of just the top message.
The first character is '+', '-', or blank depending on whether <EM>any</EM>
of the messages in the collapsed thread are addressed to you or cc'd to you.
The third character will be '*' if any of the messages are marked
Important.
The fourth character will be 'N' if all of the messages in the thread
are New, else 'n' if some of the messages in the thread are New, else blank.
The fifth character will be 'A' or 'a' or blank, and the sixth character
will be 'D' or 'd' or blank.
</DD>
<DT>IMAPSTATUS</DT>
<DD>
This token represents an even less abbreviated alternative to the
"STATUS" token.
It differs from "FULLSTATUS" in only the fourth character which is
an 'N' if the message is new to this folder since the last time
it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
new to the folder since it was last opened <EM>but</EM> has not been
viewed, or a blank if the message has been in the folder since it was
last opened and has been viewed.
<P>
If you are using a threaded view of the index and this message is at the
top of a collapsed portion of a thread,
then the fourth character will be
'N' if all of the messages in the thread are unseen and recent;
else 'n' if some of the messages in the thread are unseen and recent;
else 'U' if all of the messages in the thread are unseen and not recent;
else 'u' if some of the messages in the thread are unseen and not recent;
else 'R' if all of the messages in the thread are seen and recent;
else 'r' if some of the messages in the thread are seen and recent;
else blank.
</DD>
<DT>SHORTIMAPSTATUS</DT>
<DD>
This is the same as the last four of the six characters of IMAPSTATUS,
so the '+' To Me information will be missing.
</DD>
<DT>SIZE</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a "K" (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes (rounded to the nearest 1,000).
If an "M" (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
Commas are not used in this field.
This field is seven characters wide, including the enclosing parentheses.
Sizes are rounded when "K" or "M" is present.
The progression of sizes used looks like:
<P>
<CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
<P>
</DD>
<DT>SIZECOMMA</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a "K" (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes (rounded to the nearest 1,000).
If an "M" (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
Commas are used if the number shown is 1,000 or greater.
The SIZECOMMA field is one character wider than the SIZE field.
Sizes are rounded when "K" or "M" is present.
The progression of sizes used looks like:
<P>
<CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
<P>
</DD>
<DT>KSIZE</DT>
<DD>
This token represents the total size of the message, expressed in
kilobytes or megabytes, as most appropriate.
These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
The progression of sizes used looks like:
<P>
<CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
<P>
</DD>
<DT>SIZENARROW</DT>
<DD>
This token represents the total size, in bytes, of the message.
If a "K" (Kilobyte)
follows the number, the size is approximately 1,000
times that many bytes.
If an "M" (Megabyte) follows the number, the size is approximately
1,000,000 times that many bytes.
If a "G" (Gigabyte) follows the number, the size is approximately
1,000,000,000 times that many bytes.
This field uses only five characters of screen width, including the enclosing
parentheses.
The progression of sizes used looks like:
<P>
<CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
<P>
</DD>
<DT>DESCRIPSIZE</DT>
<DD>
This token is intended to represent a more useful description of the
message than just its size, but it isn't very useful at this point.
The plus sign in this view means there are attachments.
Note that including this token in
the "Index-Format" could slow down the
display a little while <EM>Alpine</EM> collects the necessary information.
</DD>
<DT>SUBJKEY</DT>
<DD>
This token is the same as the SUBJECT token unless keywords are set for
the message.
In that case, a list of keywords enclosed in braces will be prepended to
the subject of the message.
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
Having this set in the Index-Format will also cause the keywords to be
prepended to the subject in the MESSAGE TEXT screen.
If you have given a keyword a nickname
(<A HREF="#keywords"><EM>keywords</EM></A>), that nickname is displayed
instead of the actual keyword.
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>
option may be used to modify this token slightly.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
</DD>
<DT>SUBJKEYINIT</DT>
<DD>
This token is the same as the SUBJKEY token except that instead of
prepending a list of keywords to the subject, a list of first initials
of keywords will be prepended instead.
For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
set (or Work and Now are the <EM>Alpine</EM> nicknames of keywords which are set)
then the SUBJKEY token would cause a result like
<P>
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
<P>
whereas the SUBJKEYINIT token would give
<P>
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
<P>
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A>
option may be used to modify this token slightly.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
</DD>
<DT>SUBJECTTEXT</DT>
<DD>
Same as SUBJECT but if there is room in the Subject field for more text,
the opening part of the text of the message is displayed after the subject.
The time needed to fetch the text may cause a performance problem
which can, of course, be avoided by using the SUBJECT version of
the Subject instead.
You may color this opening text differently by using the
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from
the Setup Kolor screen.
You may adjust the characters that are displayed between the Subject and the
opening text with the option
<A HREF="#opening-text-separator-chars"><EM>Opening-Text-Separator-Chars</EM></A>.
</DD>
<DT>SUBJKEYTEXT</DT>
<DD>
Same as SUBJKEY but with the opening message text.
</DD>
<DT>SUBJKEYINITTEXT</DT>
<DD>
Same as SUBJKEYINIT but with the opening message text.
</DD>
<DT>OPENINGTEXT</DT>
<DD>
This is similar to SUBJECTTEXT.
Instead of combining the Subject and the opening text in a single
field in the index screen this token allows you to allocate a
separate column just for the opening text of the message.
The time needed to fetch this text may cause a performance problem.
You may color this opening text differently by using the
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from
the Setup Kolor screen.
</DD>
<DT>OPENINGTEXTNQ</DT>
<DD>
This is very similar to OPENINGTEXT.
The NQ stands for No Quotes.
The only difference is that quoted text (lines beginning with >) is deleted.
For some messages this may be confusing.
For example, a message might have a line preceding some quoted
text that reads something like "On May 8th person A said."
That no longer makes sense after the quoted text is deleted and it
will appear that person A said whatever the text after the quote
is, even though that is really person B talking.
</DD>
<DT>KEY</DT>
<DD>
This is a space-delimited list of keywords that are set for the message.
Only those keywords that you have defined in your
<A HREF="#keywords">Keywords</A> option
in Setup/Config are considered in the list.
In other words, keywords that have been set by some other means, perhaps
by another email program, won't show up unless included in
<A HREF="#keywords">Keywords</A>.
If you have given a keyword a nickname
that nickname is displayed
instead of the actual keyword.
It is also possible to color keywords in the index using the
Setup/Kolor screen.
This token defaults to an arbitrary width of 5.
You should set it to whatever width suits you using something
like KEY(17) in the Index-Format.
</DD>
<DT>KEYINIT</DT>
<DD>
This is a list of keyword initials that are set for the message.
If you have given a keyword a nickname
the initial of that nickname
is displayed instead of the initial of the actual keyword.
It is also possible to color keyword initials in the index using the
Setup/Kolor screen.
This token defaults to an arbitrary width of 2.
You should set it to whatever width suits you using something
like KEYINIT(3) in the Index-Format.
</DD>
<DT>PRIORITY</DT>
<DD>
The X-Priority header is a non-standard header that is used in a
somewhat standard way by many mail programs.
<EM>Alpine</EM> expects the value of this header to be a digit with a value
from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
Since this priority is something that the sender sets it is only an indication
of the priority that the sender attaches to the mail and it is therefore almost
totally unreliable for use as a filtering criterion.
This token will display the numeric value of the priority if it is between
1 and 5.
It will be suppressed (blank) if the value is 3, which is normal priority.
It is also possible to set the color of the PRIORITY field.
By default the token is colored the same
as the index line it is part of.
You may set it to be another color with the
<A HREF="#index-pri-color">Index Priority Colors</A> options available from
the Setup Kolor screen.
</DD>
<DT>PRIORITYALPHA</DT>
<DD>
This is a more verbose interpretation of the X-Priority field.
Once again nothing is displayed unless the value of the field
is 1, 2, 4, or 5.
The values displayed for those values are:
<P>
<TABLE>
<TR> <TD>1</TD> <TD>Highest</TD> </TR>
<TR> <TD>2</TD> <TD>High</TD> </TR>
<TR> <TD>4</TD> <TD>Low</TD> </TR>
<TR> <TD>5</TD> <TD>Lowest</TD> </TR>
</TABLE>
<P>
You may color this token with the
<A HREF="#index-pri-color">Index Priority Colors</A> options.
</DD>
<DT>PRIORITY!</DT>
<DD>
This is a one character, non-numeric version of the X-Priority field.
If the value of the X-Priority header is 1 or 2 an exclamation
point is displayed.
If the value is 4 or 5 a "v" (think down arrow) is displayed.
You may color this token with the
<A HREF="#index-pri-color">Index Priority Colors</A> options.
</DD>
<DT>ATT</DT>
<DD>
This is a one column wide field which represents the number of attachments
a message has. It will be blank if there are no attachments, a single
digit for one to nine attachments, or an asterisk for more than nine.
Note that including this token in
the "Index-Format" could slow down the
display a little while <EM>Alpine</EM> collects the necessary information.
</DD>
<DT>FROMORTO</DT>
<DD>
This token represents <EM>either</EM> the personal name (or email address) of
the person listed in the message's "From:" header
field, <EM>or</EM>, if that address is yours or one of your
<A HREF="#alt-addresses">alternate addresses</A>,
the first person specified in the
message's "To:" header field
with the prefix "To: " prepended.
If the from address is yours and there is also no "To" address,
<EM>Alpine</EM> will use the address on the "Cc" line.
If there is no address there, either, <EM>Alpine</EM> will look for a newsgroup name
from the "Newsgroups" header field and put
that after the "To: " prefix.
</DD>
<DT>FROMORTONOTNEWS</DT>
<DD>
This is almost the same as <EM>FROMORTO</EM>.
The difference is that newsgroups aren't considered.
When a message is from you, doesn't have a To or Cc, and does have
a Newsgroups header; this token will be your name instead of the name
of the newsgroup (like it would be with FROMORTO).
</DD>
<DT>TEXT</DT>
<DD>
This is a different sort of token.
It allows you to display a label within each index line.
It will be the same fixed text for each line.
It is different from all the other tokens in that there is no space column
displayed after this token.
Instead, it is butted up against the following field.
It also has a different syntax.
The text to display is given following a colon after the
word "TEXT".
For example,
<P>
<CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
<P>
would insert the literal text "abc=" (without the quotes)
into the index display line.
You must quote the text if it includes space characters, like
<P>
<CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
<P>
</DD>
<DT>HEADER</DT>
<DD>
This allows you to display the text from a particular header line in the
message.
The syntax for this token is substantially different from all the others
in order that you might be able to display a portion of the text following
a particular header.
The header name you are interested in is given following a colon
after the word "HEADER".
For example,
<P>
<CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
<P>
would display the text of the X-Spam header, if any.
Like for other index tokens a width field may (and probably should)
follow this.
<P>
<CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
<P>
displays the first ten characters of the X-Spam header.
Unlike other index tokens, the syntax for HEADER is more flexible.
An optional second argument comes after a comma inside the parentheses.
It specifies the "field" number.
By default, the field separator is a space character.
No extra space characters are allowed in the argument list.
<P>
<CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
<P>
would display the second field, left-justified, in a 10 character
wide field.
The second field would consist of all the text after the first space
up to the next space or the end of the header.
The default field number is zero, which stands for the entire line.
There is also an optional third argument which is a list of field
separators. It defaults to a space character.
The example
<P>
<CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
<P>
would cause the field separators to be any of colon, percent,
or space (there is a space character between the percent and the
right parenthesis).
The first field runs from the start of the header value up to the first
colon, percent, or space; the second goes from there to the next; and so on.
In order to use a comma character as a field separator you must escape
it by preceding it with a backslash (\).
The same is true of the backslash character itself.
There is one further optional argument.
It is an R or an L to specify right or left adjustment of the text
within the field.
The default is to left justify, however if you are displaying numbers
you might prefer to right justify.
<P>
Here's an example of a SpamAssassin header.
The exact look of the header will vary, but if your incoming mail
contains headers that look like the following
<P>
<CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
<P>
you might want to display the hits value.
The first field starts with the Y in Yes.
To get what you're interested in you might use "=" and
space as the field separators and display the third field, like
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
<P>
or maybe you would break at the dot instead
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
<P>
Another example we've seen has headers that look like
<P>
<CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
<P>
Because there are two equals and a comma before the 7% and a comma
after it, the token
<P>
<CENTER><SAMP>HEADER:X-Spam-Status(3,4,=\,,R)</SAMP></CENTER>
<P>
should display the probability (for example 7% or 83%) right justified
in a 3-wide field.
</DD>
<DT>ARROW</DT>
<DD>
This gives an alternative way to display the current message in the
MESSAGE INDEX screen.
Usually the current message is indicated by the line being shown in
reverse video.
Instead, if the ARROW token is included in your Index-Format,
the current line will include an "arrow" that
looks like
<P>
<CENTER><SAMP>-></SAMP></CENTER>
<P>
in the ARROW token's field.
For all of the non-current messages, the ARROW field will be filled
with blanks.
If you use the fixed-field width feature the length of the "arrow"
may be adjusted.
The arrow will be drawn as width-1 dashes followed by a greater than sign.
For example, if you use ARROW(3) you will get
<P>
<CENTER><SAMP>--></SAMP></CENTER>
<P>
and ARROW(1) will give you just
<P>
<CENTER><SAMP>></SAMP></CENTER>
<P>
It is also possible to set the color of the ARROW field.
By default (and for non-current messages) the arrow is colored the same
as the index line it is part of.
You may set it to be another color with the
<A HREF="#index-arrow-color">Index Arrow Color</A> option available from
the Setup Kolor screen.
</DD>
<DT>SCORE</DT>
<DD>
This gives the
score
of each message.
This will be six columns wide to accommodate the widest possible score.
You will probably want to use the Index-Format fixed-field width feature
to limit the width of the field to the widest score that
you use (e.g. SCORE(3) if your scores are always between 0 and 999).
If you have not defined any score rules the scores will all be zero.
If any of your score rules contain AllText or BodyText patterns
then including SCORE in the Index-Format
may slow down the display of the MESSAGE INDEX screen.
</DD>
</DL>
<P>
<H3><EM>Tokens Available for all but Index-Format</EM></H3>
<DL>
<DT>CURNEWS</DT>
<DD>
This token represents the current newsgroup if there is one.
For example, "comp.mail.pine".
</DD>
<DT>MSGID</DT>
<DD>
This token represents the message ID of the message.
This token does not work with Filter Rule folder names.
</DD>
<DT>CURDATE</DT>
<DD>
This token represents the current date.
It has the format MMM DD. For example, "Oct 23".
</DD>
<DT>CURDATEISO</DT>
<DD>
This token represents the current date.
It has the format YYYY-MM-DD. For example, "1998-10-23".
</DD>
<DT>CURDATEISOS</DT>
<DD>
This token represents the current date.
It has the format YY-MM-DD. For example, "98-10-23".
</DD>
<DT>CURPREFDATE</DT>
<DD>
This token represents the current date.
It is your operating system's idea of the preferred date representation for the current locale.
Internally it uses the %x version of the date from the strftime routine.
</DD>
<DT>CURPREFTIME</DT>
<DD>
This token represents the current time.
It is the preferred time representation for the current locale.
Internally it uses the %X version of the time from the strftime routine.
</DD>
<DT>CURPREFDATETIME</DT>
<DD>
This token represents the current date and time.
It is the preferred date and time representation for the current locale.
Internally it uses the %c version of the time from the strftime routine.
</DD>
<DT>CURTIME24</DT>
<DD>
This token represents the current time.
It has the format HH:MM. For example, "17:28".
</DD>
<DT>CURTIME12</DT>
<DD>
This token represents the current time.
This time is for a 12 hour clock.
It has the format HH:MMpm.
For example, "5:28pm" or "11:13am".
</DD>
<DT>CURDAY</DT>
<DD>
This token represents the current day of the month.
For example, "23" or "9".
</DD>
<DT>CURDAY2DIGIT</DT>
<DD>
This token represents the current day of the month.
For example, "23" or "09".
It is always 2 digits.
</DD>
<DT>CURDAYOFWEEK</DT>
<DD>
This token represents the current day of the week.
For example, "Sunday" or "Wednesday".
</DD>
<DT>CURDAYOFWEEKABBREV</DT>
<DD>
This token represents the current day of the week.
For example, "Sun" or "Wed".
</DD>
<DT>CURMONTH</DT>
<DD>
This token represents the current month.
For example, "10" or "9".
</DD>
<DT>CURMONTH2DIGIT</DT>
<DD>
This token represents the current month.
For example, "10" or "09".
It is always 2 digits.
</DD>
<DT>CURMONTHLONG</DT>
<DD>
This token represents the current month.
For example, "October".
</DD>
<DT>CURMONTHABBREV</DT>
<DD>
This token represents the current month.
For example, "Oct".
</DD>
<DT>CURYEAR</DT>
<DD>
This token represents the current year.
For example, "1998" or "2001".
</DD>
<DT>CURYEAR2DIGIT</DT>
<DD>
This token represents the current year.
For example, "98" or "01".
It is always 2 digits.
</DD>
<DT>LASTMONTH</DT>
<DD>
This token represents last month.
For example, if this is November (the 11th month),
it is equal to "10" or if this is October (the 10th month),
it is "9".
It is possible that this and the other tokens beginning with LASTMONTH
below could be useful when used with a Filtering Rule that
has the "Beginning of Month" option set.
</DD>
<DT>LASTMONTH2DIGIT</DT>
<DD>
This token represents last month.
For example, if this is November (the 11th month),
it is equal to "10" or if this is October (the 10th month),
it is "09".
It is always 2 digits.
</DD>
<DT>LASTMONTHLONG</DT>
<DD>
This token represents last month.
For example, if this is November the value is "October".
</DD>
<DT>LASTMONTHABBREV</DT>
<DD>
This token represents last month.
For example, if this is November the value is "Oct".
</DD>
<DT>LASTMONTHYEAR</DT>
<DD>
This token represents what the year was a month ago.
For example, if this is October, 1998, it is "1998".
If this is January, 1998, it is "1997".
</DD>
<DT>LASTMONTHYEAR2DIGIT</DT>
<DD>
This token represents what the year was a month ago.
For example, if this is October, 1998, it is "98".
If this is January, 1998, it is "97".
</DD>
<DT>LASTYEAR</DT>
<DD>
This token represents last year.
For example, if this is 1998, it equals "1997".
It is possible that this
could be useful when used with a Filtering Rule that
has the "Beginning of Year" option set.
</DD>
<DT>LASTYEAR2DIGIT</DT>
<DD>
This token represents last year.
For example, if this is 1998, it equals "97".
It is always 2 digits.
</DD>
<DT>ROLENICK</DT>
<DD>
This token represents the nickname of the
role currently being used. If no role is being used,
then no text will be printed for this token.
This token does not work with Filter Rule folder names.
</DD>
</DL>
<P>
<H3><EM>Token Available Only for Reply-Leadin</EM></H3>
See the help for the
<A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option,
to see why you might want to use this.
Since the <EM>Reply-Leadin</EM> contains free text this token
must be surrounded by underscores when used.
<DL>
<DT>NEWLINE</DT>
<DD>
This is an end of line marker.
</DD>
</DL>
<P>
<H3><EM>Token Available Only for Templates and Signatures</EM></H3>
<DL>
<DT>CURSORPOS</DT>
<DD>
This token is different from the others.
When it is replaced it is replaced with nothing, but it sets a <EM>Alpine</EM>
internal variable which tells the composer to start with the cursor
positioned at the position where this token was.
If both the template file and the signature file contain
a "CURSORPOS" token, then the position in the template file
is used.
If there is a template file and neither it nor the signature file contains
a "CURSORPOS" token, then the cursor is positioned
after the end of the contents of the
template file when the composer starts up.
</DD>
</DL>
<H2><A NAME="reply-token-conditionals"></A>Conditional Inclusion of Text for Reply-Leadin, Signatures, and Templates</H2>
Conditional text inclusion may be used with
the <A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option,
in signature files, and in template files used in
roles.
It may <EM>not</EM> be used with the
<EM>Index-Format</EM> option.
<P>
There is a limited if-else capability for including text.
The if-else condition is based
on whether or not a given token would result in replacement text you
specify.
The syntax of this conditional inclusion is
<P>
<CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
<P>
The left parenthesis must follow the underscore immediately, with no
intervening space.
It means the token is expanded and the results of that expansion are
compared against the "match_this" argument.
If there is an exact match, then the "if_matched" text is used
as the replacement text.
Otherwise, the "if_not_matched" text is used.
One of the most useful values for the "match_this" argument is
the empty string, "".
In that case the expansion is compared against the empty string.
<P>
Here's an example to make it clearer.
This text could be included in one of your template files:
<P>
<CENTER><SAMP>_NEWS_("", "I'm replying to email","I'm replying to news")</SAMP></CENTER>
<P>
If that is included in a template file which you are using while replying
to a message (because you chose to use the role it was part of),
and that message has a newsgroup header and a newsgroup in that header,
then the text
<P>
<CENTER><SAMP>I'm replying to news</SAMP></CENTER>
<P>
will be included in the message you are about to compose.
On the other hand, if the message you are replying to does not have
a newsgroup, then the text
<P>
<CENTER><SAMP>I'm replying to email</SAMP></CENTER>
<P>
would be included instead.
This would also work in signature files and in
the "Reply-Leadin" option.
If the "match_this", "if_matched",
or "if_not_matched" arguments contain
spaces, parentheses, or commas;
they have to be quoted with double quotation marks (like in the example
above).
If you want to include a literal quote in the text you must escape the
quote by preceding it with a backslash character.
If you want to include a literal backslash character you must escape it
by preceding it with another backslash.
<P>
The comma followed by "if_not_matched" is optional.
If there is no "if_not_matched"
present then no text is included if the not_matched case is true.
Here's another example:
<P>
<CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
<P>
Here you can see that tokens may appear in the arguments.
The same is true for tokens with the conditional parentheses.
They may appear in arguments,
though you do have to be careful to get the quoting and escaping of
nested double quotes correct.
If this was in the signature file being used and you were replying to a message
sent to comp.mail.pine the resulting text would be:
<P>
<CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
<P>
If you were replying to a message which wasn't sent to any newsgroup the
resulting text would be a single blank line.
The reason you'd get a blank line is because the end of the line is
outside of the conditional, so is always included.
If you wanted to get rid of that blank line you could do so by moving
the end of line inside the conditional.
In other words, it's ok to have multi-line
"if_matched" or "if_not_matched" arguments.
The text just continues until the next double quotation, even if it's not
on the same line.
<P>
Here's one more (contrived) example illustrating a matching argument
which is not the empty string.
<P>
<CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
<P>
If this was the value of your "Reply-Leadin" option and you
were replying to
a message which was sent today, then the value of the "Reply-Leadin"
would be
<P>
<CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
<P>
But if you were replying to a message sent on Oct. 27 (and that wasn't
today) you would get
<P>
<CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
<P>
<H2><A NAME="per-server-ldap-config"></A>Per Server Directory Configuration</H2>
This is only available if <EM>Alpine</EM> was built with LDAP support.
If that's the case, there will be a Directory option underneath the Setup
command on the Main Menu.
Each server that is defined there has several configuration variables
which control the behavior when using it.
<DL COMPACT>
<DT> <A NAME="ldap-server"><EM>ldap-server</EM></A>
<DD> This is the name of the host where an LDAP server is running.
<P>
To find out whether your organization has its own LDAP server,
contact its computing support staff.
<P>
<DT> <A NAME="search-base"><EM>search-base</EM></A>
<DD> This is the search base to be used on this server.
It functions as a filter
by restricting your searches in the LDAP server database
to the specified contents of the specified fields.
Without it, searches submitted to this directory server may fail.
It might be something like:
<PRE>
O = <Your Organization Name>, C = US
</PRE>
or it might be blank.
(Some LDAP servers actually ignore anything specified here.)
<P>
If in doubt what parameters you should specify here,
contact the maintainers of the LDAP server.
<P>
<DT> <A NAME="port"><EM>port</EM></A>
<DD> This is the TCP port number to be used with this LDAP server.
If you leave this blank port <CODE>389</CODE> will be used.
<P>
<DT> <A NAME="ldap-nickname"><EM>nickname</EM></A>
<DD> This is a nickname to be used in displays.
If you don't supply a nickname the server name from
"ldap-server" will be used instead.
This option is strictly for your convenience.
<P>
<DT> <A NAME="use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>
<DD> Set this feature to have lookups done to this server implicitly from
the composer.
If an address doesn't look like a fully-qualified address, it will be looked
up in your address books, and if it doesn't match a nickname there, then it
will be looked up on the LDAP servers which have this feature set.
The lookups will also be done when using the address completion feature
(TAB command) in the composer if any of the serves have this feature set.
Also see the LDAP feature
<A HREF="#lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A>
and the Setup/Config feature
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>.
<P>
<DT> <A NAME="lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A>
<DD> Normally implicit LDAP lookups from the composer are done only for the
strings you type in from the composer screen. In other words, you type in
something in the To or CC field and press return, then the string is looked up.
First that string is looked up in your address books. If a match is found
there, then the results of that match are looked up again. If you place
a string in your address book that you want to have looked up on the LDAP
directory server, you need to turn on this feature. If you set this feature
for a server, you almost always will also want to set the
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A>
feature.
An example might serve to best illustrate this feature.
<P>
If an LDAP lookup of "William Clinton" normally returns an
entry with an
address of pres@whitehouse.gov, then you might put an entry in your address
book that looks like:
<PRE>
Nickname Address
bill "William Clinton"
</PRE>
Now, when you type "bill" into an
address field in the composer <EM>Alpine</EM> will
find the "bill" entry in your address book.
It will replace "bill" with
"William Clinton".
It will then search for an entry with that nickname
in your address book and not find one. If this feature
is set, <EM>Alpine</EM> will then attempt to lookup
"William Clinton" on the LDAP server and find the entry with address
pres@whitehouse.gov.
<P>
A better way to accomplish the same thing is probably to use the feature
<A HREF="#save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A>.
<P>
<DT> <A NAME="save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A>
<DD> Normally when you save the results of an LDAP directory lookup to your
address book the <EM>results</EM> of the lookup are saved.
If this feature is set
and the entry being saved was found on this directory server, then the
search <EM>criteria</EM> is saved instead of the <EM>results</EM> of the search.
When this address book entry is used in the future, instead of copying
the results from the address book the directory lookup will be done again.
This could be useful if the copied result might become stale because the data on
the directory server changes (for example, the entry's email address changes).
You probably don't want to set this feature if the server is at all slow or
unreliable.
<P>
The way this actually works is that instead of saving the email address
in your address book, <EM>Alpine</EM> saves enough
information to look up the same directory entry again.
In particular, it saves the server name and the
distinguished name of the entry.
It's possible that the server administrators
might change the format of distinguished names on the server, or that the
entry might be removed from the server. If <EM>Alpine</EM> notices this, you will be warned
and a backup copy of the email address will be used. You may want to create
a new entry in this case, since you will get the annoying warning every
time you use the old entry. You may do that by Saving the entry to a new
nickname in the same address book. You will be asked whether or not you
want to use the backup email address.
<P>
A related feature in the Setup/Config screen is
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>.
<P>
<DT> <A NAME="disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>
<DD> Spaces in your input are normally handled specially.
Each space character is replaced
by
<PRE>
* <SPACE>
</PRE>
in the search query (but not by "* <SPACE> *").
The reason this is done is so the input string
<PRE>
Greg Donald
</PRE>
(which is converted to "Greg* Donald") will match
the names "Greg Donald",
"Gregory Donald", "Greg F. Donald", and
"Gregory F Donald"; but it won't match "Greg McDonald".
If the "Search-Rule" you were using was "begins-with",
then it would also match the name "Greg Donaldson".
<P>
Turning on this feature will disable this substitution.
<P>
<DT> <A NAME="search-type"><EM>search-type</EM></A>
<DD> This affects the way that LDAP searches are done.
In particular, this tells the server where to look for the string to be matched.
If set to "name" then the string that is being searched for will
be compared with the string in the
"Name" field on the server
(technically, it is the "commonname" field on the server).
"Surname" means we're looking for a
match in the "Surname" field on the
server (actually the "sn" field).
"Givenname" really is "givenname"
and "email" is the electronic mail address (this is actually the field
called "mail" or "electronicmail" on the server).
The other three types are combinations of
the types listed so far. "Name-or-email"
means the string should appear
in either the "name" field OR the "email" field.
Likewise, "surname-or-givenname"
means "surname" OR "givenname"
and "sur-or-given-or-name-or-email" means the obvious thing.
<P>
This search <EM>type</EM> is combined with the
search <A HREF="#search-rule"><EM>rule</EM></A>
to form the actual search query.
<P>
The usual default value for this
option is "sur-or-given-or-name-or-email".
This type of search may be slow on some servers.
Try "name-or-email", which is often
faster, or just "name" if the performance seems to be a problem.
<P>
Some servers have been configured with different attribute names for
these four fields.
In other words, instead of using the attribute name "mail"
for the email address field, the server might be configured to use something
else, for example, "rfc822mail" or "internetemailaddress".
<EM>Alpine</EM> can be configured to use these different attribute names by using
the four per-server configuration options:
<P><UL>
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A>
</UL>
<P>
<DT> <A NAME="search-rule"><EM>search-rule</EM></A>
<DD> This affects the way that LDAP searches are done.
If set to "equals" then
only exact matches count.
"Contains" means that the string you type in
is a substring of what you are matching against.
"Begins-with" and "ends-with"
mean that the string starts or ends with the string you type in.
<P>
Spaces in your input are normally handled specially, but you can turn that
special handling off with the
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>
feature.
<P>
The usual default value for this option is <EM>begins-with</EM>.
<P>
<DT> <A NAME="email-attribute"><EM>email-attribute</EM></A>
<DD> This is the name of the attribute which is searched for when looking for
an email address. The default value for this option is "mail" or
"electronicmail".
If the server you are using uses a different attribute name for the email
address, put that attribute name here.
<P>
This will affect the search filter used if your Search-Type is one that
contains a search for "email".
It will also cause the attribute value matching this attribute name to be used
as the email address when you look up an entry from the composer.
<P>
<DT> <A NAME="name-attribute"><EM>name-attribute</EM></A>
<DD> This is the name of the attribute which is searched for when looking for
the name of the entry. The default value for this option is "cn", which
stands for common name.
If the server you are using uses a different attribute name for the name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for "name".
<P>
<DT> <A NAME="surname-attribute"><EM>surname-attribute</EM></A>
<DD> This is the name of the attribute which is searched for when looking for
the surname of the entry. The default value for this option is "sn".
If the server you are using uses a different attribute name for the surname,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for "surname".
<P>
<DT> <A NAME="givenname-attribute"><EM>givenname-attribute</EM></A>
<DD> This is the name of the attribute which is searched for when looking for
the given name of the entry. The default value for this option is "givenname".
If the server you are using uses a different attribute name for the given name,
put that attribute name here.
This will affect the search filter used if your Search-Type is one that
contains a search for "givenname".
<P>
<DT> <A NAME="timelimit"><EM>timelimit</EM></A>
<DD> This places a limit on the number of seconds the LDAP search will continue.
The default is 30 seconds. A value of 0 means no limit. Note that some servers
may place limits of their own on searches.
<P>
<DT> <A NAME="sizelimit"><EM>sizelimit</EM></A>
<DD> This places a limit on the number of entries returned by the LDAP server.
A value of 0 means no limit. The default is 0. Note that some servers
may place limits of their own on searches.
<P>
<DT> <A NAME="custom-search-filter"><EM>custom-search-filter</EM></A>
<DD> This one is for advanced users only! If you define this, then the
<A HREF="#search-type"><EM>search-type</EM></A>
and
<A HREF="#search-rule"><EM>search-rule</EM></A>
defined are both ignored.
However, the feature
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A>
is still in effect.
That is, the space substitution will take place even in a custom filter unless
you disable it.
<P>
If your LDAP service stops working and you suspect it might be because
of your custom filter, just delete this filter and try using the
<EM>search-type</EM> and <EM>search-rule</EM> instead.
Another option that sometimes causes trouble is the
<A HREF="#search-base"><EM>search-base</EM></A> option.
<P>
This variable may be set to the string representation of an LDAP search
filter (see RFC1960). In the places where you want the address string to be
substituted in, put a '%s' in this filter string. Here are some examples:
<P>
A "Search-Type" of "name" with "Search-Rule" of "begins-with"
is equivalent to the "custom-search-filter"
<PRE>
(cn=%s*)
</PRE>
When you try to match against the string "string" the program replaces
the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
they will all be replaced with the string. There is a limit of 10 "%s"'s.
<P>
A "Search-Type" of "name-or-email" with "Search-Rule"
of "contains" is equivalent to
<PRE>
(|(cn=*%s*)(mail=*%s*))
</PRE>
<P>
If your server uses a different attribute <EM>name</EM> than
<EM>Alpine</EM> uses by default,
(for example, it uses "rfc822mail" instead of "mail"),
then you may be able to use one or more of the four attribute configuration
options instead of defining a custom filter:
<P><UL>
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A>
</UL>
<P><UL>
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A>
</UL>
</DL>
<P>
<H2><A NAME="color-config"></A>Color Configuration</H2>
If the terminal or terminal emulator you are using is capable of using
color (see <A HREF="#color-style"><EM>color-style</EM></A> option),
or if you are using <EM>PC-Alpine</EM>, then it is possible to
set up <EM>Alpine</EM> so that various parts of the display will be
shown in colors you configure.
This is done using the Setup Color screen.
The Setup Color screen is divided into five broad sections: Options,
General Colors, Index Colors, Header Colors, and Keyword Colors.
In addition to these five categories you may also color lines in the
MESSAGE INDEX screen by configuring the
<A HREF="#index-color-config">Index Line Color</A>.
<P>
Each color is defined as a foreground color (the color of the actual text)
and a background color (the color of the area behind the text).
<P>
<H3><A NAME="color-options"></A>Color Options</H3>
<DL>
<DT> <A NAME="cur-il-style"><EM>current-indexline-style</EM></A>
<DD>
This option affects the colors used to display the current line in the
MESSAGE INDEX screen.
If you do not have
<A HREF="#index-color-config">Index Line Colors</A>
defined, then this option will have no effect in the index.
Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
<P>
If the option
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is turned on and the
<A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>
is set to something other than the default, then
this option also affects the color used to display the current folder
in the Incoming FOLDER LIST screen.
<P>
The available options include:
<P>
<DL>
<DT>flip-colors</DT>
<DD>This is the default.
If an index line is colored because it matches one of your
Index Color Rules, then its colors will be reversed when it is the currently
highlighted line.
For example, if the line is normally red text on a blue background, then
when it is the current line it will be drawn as blue text on a red background.
<P>
The rest of the option values all revert to this flip-colors behavior if
there is no Reverse Color defined.
</DD>
<DT>reverse</DT>
<DD>With this option the Reverse color is always used to highlight the
current line.
</DD>
<DT>reverse-fg</DT>
<DD>The foreground part of the Reverse Color is used to highlight
the current line.
If this would cause the text to be unreadable (because the foreground and
background colors are the same) or if it would cause no change in the
color of the index line, then the colors are flipped instead.
<P>
Some people think this works particularly well if you use different
background colors to emphasize "interesting" lines,
but always with the same Normal foreground color,
and you use a different foreground color for the Reverse Color.
</DD>
<DT>reverse-fg-no-ambiguity</DT>
<DD>With the "reverse-fg" rule above, it is possible that
the resulting color will be exactly the same as the regular Reverse
Color.
That can lead to some possible confusion because an
"interesting"
line which is the current line will be displayed exactly the same as a
non-interesting line which is current.
You can't tell whether the line is just a regular current line or if it is
an "interesting" current line by looking at the color.
Setting the option to this value removes that ambiguity.
It is the same as the "reverse-fg" setting unless the resulting
interesting current line would look just like a non-interesting current line.
In that case, the interesting line's colors are simply flipped (like in the
default behavior).
<P>
As an alternative way to preserve the line's interestingness in this case,
you may find that using both a different foreground and a different
background color for the interesting line will help.
</DD>
<DT>reverse-bg</DT>
<DD>The background part of the Reverse Color is used to highlight
the current line.
If this would cause the text to be unreadable (because the foreground and
background colors are the same) or if it would cause no change in the
color of the index line, then the colors are flipped instead.
<P>
Some people think this works particularly well if you use different
foreground colors to emphasize "interesting" lines,
but always with the same Normal background color,
and you use a different background color for the Reverse Color.
</DD>
<DT>reverse-bg-no-ambiguity</DT>
<DD>As with the "reverse-fg" case, the "reverse-bg"
rule may also result in a color which is exactly the same as the regular
Reverse Color.
Setting the option to this value removes that ambiguity.
It is the same as the "reverse-bg" setting unless the resulting
current line has the same color as the Reverse Color.
In that case, the interesting line's colors are simply flipped (like in the
default behavior).
</DD>
</DL>
<DT> <A NAME="titlebar-style"><EM>titlebar-color-style</EM></A>
<DD>
This option affects the colors used to display the titlebar (the top
line on the screen) when viewing a message.
<P>
The available options include:
<P>
<DL>
<DT>default</DT>
<DD>The color of the titlebar will be the color you set for the
<A HREF="#title-color"><EM>Title Color</EM></A>.
The Title Color may be set by using the
</DD>
<DT>indexline</DT>
<DD>The color of the titlebar will be the same as the color of the
index line corresponding to the message being viewed.
The rules which determine what color the index line will be may be set
up by going to the Setup/Rules/Indexcolor screen.
If the index line for a message is not colored explicitly by the
Indexcolor rules, then the titlebar will be colored the same as for
the "default" option above (which is not the same color that
the index line itself will have).
</DD>
<DT>reverse-indexline</DT>
<DD>This is similar to the "indexline" option except the
foreground and background colors from the corresponding index line will
be reversed.
For example, if the index line color is red letters on a white background,
then the titlebar will be white letters on a red background.
If the index line for a message is not colored explicitly by the
Indexcolor rules, then the titlebar will be colored the same as for
the "default" option above (which is not the same color that
the index line itself will have).
</DD>
</DL>
</DL>
<P>
<H3><A NAME="general-colors"></A>General Colors</H3>
<DL COMPACT>
<DT> <A NAME="normal-color"><EM>Normal Color</EM></A>
<DD> This is the color which most of the screen is painted in.
By default this color is black characters on a white background.
<P>
<DT> <A NAME="reverse-color"><EM>Reverse Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for reverse video characters.
Actually, the name is misleading. This used to be reverse video and so
the name remains. It is still used to highlight certain parts of the
screen but the color may be set to whatever you'd like.
<P>
<DT> <A NAME="title-color"><EM>Title Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the
screen).
By default, the Title Color is black characters on a yellow background.
The actual titlebar color may be different from the Title Color if
the option
<A HREF="#titlebar-color-style"><EM>titlebar-color-style</EM></A>
is set to some value other than the default.
It may also be different if the current folder is closed and the
<A HREF="#title-closed-color">Title Closed Color</A>
is set to something different from the Title Color.
<P>
<DT> <A NAME="title-closed-color"><EM>Title-closed Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the
screen) when the current folder is closed.
By default, the Title Color Closed Color is white characters on a red background.
<P>
<DT> <A NAME="status-color"><EM>Status Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for messages written to the status
message line near the bottom of the screen.
By default, the Status Color is the same as the Reverse Color.
<P>
<DT> <A NAME="keylabel-color"><EM>KeyLabel Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for the labels of the commands in the
two-line menu at the bottom of the screen.
The label is the long name, for example, "PrevMsg".
By default, the KeyLabel Color is the same as the Normal Color.
<P>
WARNING: Some terminal emulators have the property that the screen will scroll
down one line whenever a character is written to the character cell in the
lower right corner of the screen.
<EM>Alpine</EM> can usually avoid writing a character in that corner of the screen.
However, if you have defined a KeyLabel Color then <EM>Alpine</EM> does have to write
a character in that cell in order to color the cell correctly.
If you find that your display sometimes scrolls up a line this could be
the problem.
The most obvious symptom is probably that the titlebar at the top of the
screen scrolls off the screen.
Try setting KeyLabel Color to Default to see if that fixes the problem.
<P>
<DT> <A NAME="keyname-color"><EM>KeyName Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for the names of the commands in the
two-line menu at the bottom of the screen.
The KeyName is the shorter name in the menu. For example, the "W"
before the "WhereIs".
By default, the KeyName Color is the same as the Normal Color.
<P>
<DT> <A NAME="selectable-item-color"><EM>Selectable-item Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for displaying selectable items, such
as URLs.
By default, the Selectable-item Color is the same as the Normal Color, except
it is also Bold.
<P>
<DT> <A NAME="meta-message-color"><EM>Meta-message Color</EM></A>
<DD> The color <EM>Alpine</EM> uses in the MESSAGE TEXT screen for messages to you
that aren't part of the message itself.
By default, the Meta-Message Color is black characters on a yellow background.
<P>
<DT> <A NAME="quote-colors"><EM>Quote Colors</EM></A>
<DD> The colors <EM>Alpine</EM> uses for coloring quoted text in the
MESSAGE TEXT screen.
If a line begins with a > character (or space followed by >) it
is considered a quote. That line will be given the Quote1 Color (first
level quote). If there is a second level of quoting then the Quote2 Color
will be used. <EM>Alpine</EM> considers there to be a second level of quoting if
that first > is followed by another > (or space followed by >).
If there are characters other than whitespace and > signs, then it isn't
considered another level of quoting. Similarly, if there is a third level
of quoting the Quote3 Color will be used. If there are more levels after
that the Quote Colors are reused. If you define all three colors then it
would repeat like Color1, Color2, Color3, Color1, Color2, Color3, ...
If you only define the first two it would be Color1, Color2,
Color1, Color2, ...
If you define only the Quote1 Color, then the entire quote would be
that color regardless of the quoting levels.
By default, the Quote1 Color is black characters on a greenish-blue background;
the Quote2 Color is black characters on a dull yellow background; and
the Quote3 Color is black characters on a green background.
<P>
<DT> <A NAME="incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>
<DD> If the option
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A>
is turned on it is possible to highlight the folders that contain
unseen messages by coloring them with this color.
By default, this is the same as the Normal Color and no highlighting is done.
<P>
Usually the "current" folder (the folder the cursor is on)
is highlighted using reverse video.
If the current folder is colored because it contains unseen messages then
the color used to show that it is also the current folder is controlled
by the <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A>
feature at the top of the SETUP COLOR screen.
<P>
<DT> <A NAME="signature-color"><EM>Signature Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for coloring the signature in the MESSAGE TEXT
screen. According to USENET conventions, the signature is defined as the
paragraph following the "sigdashes", that is, the special line
consisting of the three characters
"-- " (i.e., dash, dash, and space). <EM>Alpine</EM> allows for one
empty line right after the sigdashes to be considered as part of the
signature.
By default, the Signature Color is blue characters on a white background.
<P>
<DT> <A NAME="prompt-color"><EM>Prompt Color</EM></A>
<DD> The color <EM>Alpine</EM> uses for confirmation prompts and questions
which appear in the status message line near the bottom of the screen.
By default, the Prompt Color is the same as the Reverse Color.
<P>
</DL>
<H3><A NAME="index-colors"></A>Index Colors</H3>
You may add color to the single character symbols which give the status
of each message in the MESSAGE INDEX.
By default the characters "+", "*", "D",
"A", and "N" show up near the left hand side of the
screen, depending on whether the message is addressed to you, and whether
the message is marked Important, is Deleted, is Answered, or is New.
You may set the color of those symbols.
By default, all of these symbols are drawn with the same color as the rest
of the index line they are a part of.
<P>
Besides coloring the message status symbols, you may also color the
entire index line.
This is done by using the
<A HREF="#index-color-config">Index Line Color</A> configuration screen.
It is also possible to color
(<A HREF="#keywords">keywords</A>
in the index using the
Setup/Kolor screen (<A HREF="#keyword-colors">Keyword Colors</A>);
the <A HREF="#index-arrow-color">ARROW</A> cursor;
the Subject using
<A HREF="#index-subject-color">Index Subject Color</A>;
the From using
<A HREF="#index-from-color">Index From Color</A>;
and the
<A HREF="#index-opening-color">Index Opening</A> text.
<P>
<DL COMPACT>
<DT> <A NAME="index-to-me-color"><EM>Index-to-me Symbol Color</EM></A>
<DD> The color used for drawing the "+" symbol which signifies a
message is addressed directly to you.
<P>
<DT> <A NAME="index-important-color"><EM>Index-important Symbol Color</EM></A>
<DD> The color used for drawing the "*" symbol which signifies a
message has been flagged Important.
<P>
<DT> <A NAME="index-deleted-color"><EM>Index-deleted Symbol Color</EM></A>
<DD> The color used for drawing the "D" symbol which signifies a
message has been marked Deleted.
<P>
<DT> <A NAME="index-answered-color"><EM>Index-answered Symbol Color</EM></A>
<DD> The color used for drawing the "A" symbol which signifies a
message has been answered.
<P>
<DT> <A NAME="index-new-color"><EM>Index-new Symbol Color</EM></A>
<DD> The color used for drawing the "N" symbol which signifies a
message is New.
<P>
<DT> <A NAME="index-recent-color"><EM>Index-recent Symbol Color</EM></A>
<DD> The color used for drawing the "R" symbol which signifies a
message is Recent (only visible if the "IMAPSTATUS" or "SHORTIMAPSTATUS" token is
part of the
<A HREF="#index-format"><EM>index-format</EM></A> option).
<P>
<DT> <A NAME="index-unseen-color"><EM>Index-unseen Symbol Color</EM></A>
<DD> The color used for drawing the "U" symbol which signifies a
message is Unseen (only visible if the "IMAPSTATUS" or "SHORTIMAPSTATUS" token is
part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option).
<P>
<DT> <A NAME="index-pri-color"><EM>Index-priority Symbol Colors</EM></A>
<DD> The colors used for drawing the tokens "PRIORITY",
"PRIORITYALPHA", and "PRIORITY!" when these are
configured as part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
You may set the color used to draw these tokens by use of the colors
Index High Priority Symbol Color and Index Low Priority Symbol Color.
This coloring takes place for all but the current index line, and the Priority
Color appears to be in front of any color from an Index Color Rule.
If the priority has a value of 1 or 2 the High Priority color will be
used,
and if the value is 4 or 5 the Low Priority color will be used.
<P>
If you don't set these colors the index line will be colored in the same color as
the bulk of the index line.
<P>
<DT> <A NAME="index-arrow-color"><EM>Index-arrow Symbol Color</EM></A>
<DD> The color used for drawing the "ARROW" token when it is
configured as part of the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
<P>
<DT> <A NAME="index-subject-color"><EM>Index-subject Symbol Color</EM></A>
<DD> You may set the color used to draw the Subject part of the index line.
This coloring takes place for all but the current index line, and the Subject
Color appears to be in front of any color from an Index Color Rule.
<P>
If you don't set this color it will be colored in the same color as
the bulk of the index line.
<P>
<DT> <A NAME="index-from-color"><EM>Index-from Symbol Color</EM></A>
<DD> You may set the color used to draw the From part of the index line.
This coloring takes place for all but the current index line, and the From
Color appears to be in front of any color from an Index Color Rule.
<P>
If you don't set this color it will be colored in the same color as
the bulk of the index line.
<P>
<DT> <A NAME="index-opening-color"><EM>Index-opening Symbol Color</EM></A>
<DD> It is possible to configure the
<A HREF="#index-format"><EM>Index-Format</EM></A> option
so that it includes the subject followed by the "opening" text of the
message if there is enough space.
This is done by using one of the tokens SUBJECTTEXT, SUBJKEYTEXT, or
SUBJKEYINITTEXT.
The color used for drawing this opening text is given by this option.
The coloring happens for all but the current index line, and this opening
color appears to be in front of any color from an Index Color Rule.
<P>
By default the Index Opening Color is gray characters on a white background.
<P>
</DL>
<P>
The default colors for these symbols are:
<TABLE>
<TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
<TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
<TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
<TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
<TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
<TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
<TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
</TABLE>
<H3><A NAME="header-colors"></A>Header Colors</H3>
You may add color to the header fields in the MESSAGE TEXT screen.
The
<P>
<DL COMPACT>
<DT> <A NAME="header-general-color"><EM>Header-general Color</EM></A>
<DD> may be used to color all of the headers of
the message.
</DL>
<P>
It is also possible to set the colors for specific header fields,
for example for the Subject or From fields, using the
<A HREF="#viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A>
option.
<P>
For Header Colors,
there is an additional line on the configuration
screen labeled "Pattern to match".
If you leave that blank, then the whole field for that header will
always be colored.
However, if you give a pattern to match, the coloring will only take place
if there is a match for that pattern in the value of the field.
For example, if you are working on a color for the Subject header and
you fill in a pattern of "important", then only Subjects which
contain the word "important" will be colored.
For address fields like From or To, a pattern match will cause only the
addresses which match the pattern to be colored.
<P>
If the pattern you enter is a comma-separated list of patterns, then coloring
happens if any of those patterns matches.
<P>
<H3><A NAME="keyword-colors"></A>Keyword Colors</H3>
Sets the colors <EM>Alpine</EM> uses for Keyword fields in the MESSAGE INDEX screen.
Keywords may be displayed as part of the Subject of a message by using
the "SUBJKEY" or "SUBJKEYINIT" tokens in the
<A HREF="#index-format">Index-Format</A> option.
Keywords may also be displayed in a column of their own in the MESSAGE INDEX
screen by using the "KEY" or "KEYINIT" tokens.
<P>
For example, you might have set up a Keyword
"Work" using the
<A HREF="#keywords">Keywords</A>
option in the Setup/Config screen.
You could cause that Keyword to show up as a special color
by setting up the Keyword Color using this option, and then including it
in the MESSAGE INDEX screen using one of the tokens listed above in the
Index-Format.
<P>
<H3><A NAME="index-line-colors"></A>Index Line Colors</H3>
You may color whole index lines by using roles.
This isn't configured in the Setup Colors screen, but is configured in
the <A HREF="#index-color-config">Setup Rules IndexColor</A> screen.
<H2><A NAME="index-color-config"></A>Index Line Color Configuration</H2>
Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
This action is only available if your terminal is capable of displaying
color and color display has been enabled with the
<A HREF="#color-style"><EM>Color-Style</EM></A> option.
(In PC-Alpine, color is always enabled so there is no option to turn on.)
<P>
Each rule has a "Pattern",
which is used to decide which of the rules is used; and the color which
is used if the Pattern matches a particular message.
<H3>Rule Patterns</H3>
In order to determine whether or not a message matches a rule the message is
compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
"<A HREF="#patterns-section">here</A>".
<H3>Index Line Color</H3>
This is the color that index lines are colored when there is a matching
Pattern.
This colors the whole index line, except possibly the status letters
which may be colored separately using
the <A HREF="#color-config">Setup Kolor</A> screen.
<H2><A NAME="role-config"></A>Role Configuration</H2>
You may play different roles depending on who you are replying to.
For example, if you are replying to a message addressed to <EM>help-desk</EM> you
may be acting as a Help Desk Worker.
That role may require that you use a different return address and/or
a different signature.
<P>
Roles are optional.
If you set up roles they work like this: Each role has a set of
"Uses", which indicate whether or not a role is eligible to be
considered for a particular use; a "Pattern",
which is used to decide which of the eligible roles is used; and a set
of "Actions", which are taken when that role is used.
When you reply to a message, the message you are replying to is compared
with the Patterns of the roles marked as eligible for use when replying.
The comparisons start with the first eligible role and keep going until there
is a match.
If a match is found, the matching role's Actions are taken.
<P>
It is also possible to set a default role and to change that role during
your <EM>Alpine</EM> session.
When you start <EM>Alpine</EM> no default role will be set.
You may set or change the current default role by using the "D"
command in the role selection screen.
You'll see that screen while composing a message and being asked to select
a role.
An easy way to get to that screen is to use the Role Command to
compose a message.
You may find a default role useful if you normally perform the duties of one
of your roles for a while, then you switch to another role and stay in the
new role for another period of time.
It may be easier than using the Role Command to select the role each time you
compose a message.
<H3>Role Uses</H3>
There are three types of use to be configured;
one for Replying, one for Forwarding, and one for Composing.
These indicate whether or not you want a role to be considered when you
type the Reply, Forward, or Compose commands.
(The Role command is an alternate form of the Compose command, and it is
not affected by these settings.)
Each of these Use types has three possible values.
The value "Never"
means that the role will never be considered as a candidate for use with
the corresponding command.
For example, if you set a role's Reply Use to Never, then when you Reply to
a message, the role won't even be considered.
(That isn't quite true. If the message you are replying to matches some other
role which requires confirmation,
then there will be a ^T command available which allows you to select a role
from all of your roles, not just the reply-eligible roles.)
<P>
The options "With confirmation" and "Without confirmation"
both mean that you do want to consider this role when using the corresponding
command.
For either of these settings the role's Pattern will
be checked to see if it matches the message.
For Reply Use, the message used to compare the Patterns with is the message
being replied to.
For Forward Use, the message used to compare the Pattern with is the message
being forwarded.
For Compose Use, there is no message, so the parts of the Pattern which depend
on a message (everything other than Current Folder Type) are ignored.
In all cases, the Current Folder is checked if defined.
If there is a match then this role will either be used without confirmation
or will be the default when confirmation is asked for, depending on
which of the two options is selected.
If confirmation is requested, you will have a chance to
choose No Role instead of the offered role, or to
change the role to any one of your other roles (with the ^T command).
<H3>Role Patterns</H3>
In order to determine whether or not a message matches a role the message is
compared with the Role Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
"<A HREF="#patterns-section">here</A>".
<P>
Since header patterns, AllText patterns, and BodyText patterns which are unset are ignored,
a role which has all header patterns unset, the AllText pattern unset,
the BodyText pattern unset,
the Score Interval unset, and the Current Folder Type set to
"Any" may be used as a default role.
It should be put last in the list of roles since the matching
starts at the beginning and proceeds until one of the roles is a match.
If no roles at all match, then <EM>Alpine</EM> will
use its regular methods of defining the role.
If you wanted to, you could define a different "default" role
for Replying, Forwarding, and Composing by setting the
"Use" fields appropriately.
<H3>Role Actions</H3>
Once a role match is found, the role's Actions are taken.
For each role there are several possible actions that may be defined.
They are actions to set the From address, the Reply-To address,
the Fcc, the Signature file, and the Template file.
<H4>Initialize Settings Using Role</H4>
This is a power user feature.
You will usually want to leave this field empty.
The value of this field is the nickname of another one of your roles.
The Action values from that other role
are used as the initial values of the Action items for this role.
If you put something in any of the action fields for this role, that will
override whatever was in the corresponding field of the initializer role.
<P>
You might use this field if the "Action" part of one of your roles
is something you want to use in more than one role.
Instead of filling in those action values again for each role, you
may give the nickname of the role where the values are filled in.
It's just a shortcut way to define Role Actions.
<P>
Here's an example to help explain how this works.
Suppose you have a role with nickname "role1" and role1 has
(among other things)
<P>
<CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
<P>
set.
If in "role2" you set "Initialize settings using role" to
"role1", then role2 will inherit the Set Reply-To value
from role1 by default (and any of the other inheritable action values
that are set).
So if role2 had
<P>
<CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
<P>
defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
However, if role2 had
<P>
<CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
<P>
defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
<P>
If you wish,
you may choose a nickname from your list of roles by using the
"T" command.
If the role you are using to initialize also has a role it initializes from,
then that initialization happens first.
That is, inheritance works as expected with the grandparent and
great-grandparent (and so on) roles having the expected effect.
<H4>Set From</H4>
This field consists of a single address which will be used as the From
address on the message you are sending.
This should be a fully-qualified address like
<P>
<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
<P>
or just
<P>
<CENTER><SAMP>user@domain</SAMP></CENTER>
<P>
If this is left blank, then the normal From address will be used.
<H4>Set Reply-To</H4>
The Reply-To address is the address used on the Reply-To line of the message
you are sending.
You don't need a Reply-To address unless it is different from the From address.
This should be a fully-qualified address like
<P>
<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
<P>
or just
<P>
<CENTER><SAMP>user@domain</SAMP></CENTER>
<P>
If this is left blank, then there won't be a Reply-To address unless
you have configured one specially with the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A>
configuration option.
<H4>Set Other-Hdrs</H4>
This field gives you a way to set values for headers besides
"From" and "Reply-To".
If you want to set either of those, use the specific
"Set From" and "Set Reply-To" settings.
<P>
This field is similar to the
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> option.
Each header you specify here must include the header tag
("To:", "Approved:", etc.)
and may optionally include a value for that header.
In order to see these headers when you compose using this role you
must use the rich header command.
Here's an example which shows how you might set the To address.
<P>
<CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
<P>
Headers set in this way are different from headers set with the
customized-hdrs option in that the value you give for a header here
will replace any value that already exists.
For example, if you are Replying to a message there will already be at
least one address in the To header (the address you are Replying to).
However, if you Reply using a role which sets the To header, that role's
To header value will be used instead.
The customized-hdrs headers are defaults.
<P>
Limitation: Because commas are used to separate the list of
Other Headers, it is not possible to have the value of a
header contain a comma;
nor is there currently an "escape" mechanism provided
to make this work.
<H4>Set Fcc</H4>
This field consists of a single folder name which will be used in
the Fcc field of the message you are sending.
You may put anything here that you would normally type into the Fcc
field from the composer.
<P>
In addition, an fcc of "" (two double quotation marks) means
no Fcc.
<P>
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding
the default value of the Fcc field.
For many roles, perhaps most, it may make more sense for you to use the
other <EM>Alpine</EM> facilities for setting the Fcc.
In particular, if you want the Fcc to depend on who you are sending the
message to then the <A HREF="#fcc-name-rule"><EM>fcc-name-rule</EM></A>
is probably more useful.
In that case, you would want to leave the Fcc field here blank.
However, if you have a role that depends on who the message you are replying
to was From, or what address that message was sent to;
then it might make sense to set the Fcc for that role here.
<H4>Set LiteralSig</H4>
This field contains the actual text for your signature, as opposed to
the name of a file containing your signature.
If this is defined it takes precedence over any value set in the
<EM>Set Signature</EM> field.
<P>
This is simply a different way to store the signature.
The signature is stored inside your Alpine configuration file instead of in
a separate signature file.
Tokens work the same way they do with <EM>Set Signature</EM>.
<P>
The two character sequence \n (backslash followed by
the character n) will be used to signify a line-break in your signature.
You don't have to enter the \n, but it will be visible in the
CHANGE THIS ROLE RULE window after you are done editing the signature.
<H4>Set Signature</H4>
The Signature is the name of a file to be used as the signature file when
this role is being used.
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.
<P>
Signature files may be stored remotely on an IMAP server.
In order to do that you just give the file a remote name.
This works just like the regular
<A HREF="#sig-file">signature-file</A>
option which is configured from the Setup/Configuration screen.
A remote signature file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/sig3</SAMP></CENTER>
<P>
Once you have named the remote signature file you create its
contents by using the "F" "editFile" command when the
cursor is on the "Set Signature"
line of the role editor.
<P>
Besides containing regular text, a signature file may also
contain (or a signature program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the signature file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a signature file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a signature file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="#index-tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals">here</A>.
<P>
In the very unlikely event that you want to include a literal token in
a signature file, you must precede it with a backslash character.
For example, to include the literal text _DATE_ you must actually use
\_DATE_.
It is not possible to have a literal backslash followed by an expanded token.
<P>
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding
which file (if any) to use for the signature file.
<H4>Set Template</H4>
A Template is the name of a file to be included in the message when this
role is being used.
The template file is a file which is included at the top of the message you
are composing.
<P>
If the filename is followed by a vertical bar (|) then instead
of reading the contents of the file the file is assumed to be a
program which will produce the text to be used on its standard output.
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>,
but the rest of the processing works as if the contents came from a file.
<P>
Template files may be stored remotely on an IMAP server.
In order to do that you just give the file a remote name.
This works just like the regular
<A HREF="#sig-file">signature-file</A>
option which is configured from the Setup/Configuration screen.
A remote template file name might look like:
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
<P>
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try
<P>
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/templ3</SAMP></CENTER>
<P>
Once you have named the remote template file you create its
contents by using the "F" "editFile" command when the
cursor is on the "Set Template"
line of the role editor.
<P>
Besides containing regular text, a template file may also
contain (or a template file program may produce) tokens which are replaced with text
which depends on the message you are replying to or forwarding.
The tokens all look like _word_ (a word surrounded by underscores).
For example, if the token
<P>
<CENTER><SAMP>_DATE_</SAMP></CENTER>
<P>
is included in the text of the template file, then when you reply to
or forward a message, the token will be replaced with the actual date
the message you are replying to or forwarding was sent.
<P>
If you use a role which has a template file for a plain composition
(that is, not a reply or forward) then there is no original message, so
any tokens which depend on the message will be replaced with nothing.
So if you want a template file to be useful for new compositions it
shouldn't include any of the tokens which depend on the message being
replied to or forwarded.
<P>
The list of available tokens is
<A HREF="#index-tokens">here</A>.
<P>
Actually, for the adventurous, there is a way to conditionally include text based
on whether or not a token would result in specific replacement text.
For example, you could include some text based on whether or not
the _NEWS_ token would result in any newsgroups if it was used.
It's explained in detail
<A HREF="#reply-token-conditionals">here</A>.
<P>
In the very unlikely event that you want to include a literal token in
a template file, you must precede it with a backslash character.
For example, to include the literal text _DATE_ you must actually use
\_DATE_.
It is not possible to have a literal backslash followed by an expanded token.
<P>
A blank field here means that <EM>Alpine</EM> will not use a template file when
this role is being used.
<H4>Use SMTP Server</H4>
If this field has a value, then it will be used as the SMTP server
to send mail when this role is being used (unless the SMTP server variable
is set in the system-wide fixed configuration file).
It has the same semantics as the
<A HREF="#smtp-server"><EM>smtp-server</EM></A>
variable in the Setup/Config screen.
When you postpone the composition this SMTP server list will be saved
with the postponed composition and it cannot be changed later.
Because of that, you may want to make this a list of SMTP servers
with the preferred server at the front of the list and alternate servers
later in the list.
<P>
If any of the actions are left unset, then the action depends on what
is present in the "Initialize settings using role" field.
If you've listed the nickname of another one of your roles there, then the
corresponding action from that role will be used here.
If that action is also blank, or if there is no nickname specified,
then <EM>Alpine</EM> will do whatever it normally does to set these actions.
This depends on other configuration options and features you've set.
<H2><A NAME="filter-config"></A>Filtering Configuration</H2>
The software which actually delivers mail (the stuff that happens
before <EM>Alpine</EM> is involved) for you is in a better position to do mail filtering
than <EM>Alpine</EM> itself.
If possible, you may want to look into using that sort of mail filtering to
deliver mail to different folders, delete it, or forward it.
However, if you'd like <EM>Alpine</EM> to help with this, <EM>Alpine</EM>'s filtering is for you.
<P>
Filtering is a way to automatically move certain messages from one folder
to another or to delete messages.
It can also be used to set message status bits (Important, Deleted, New,
Answered).
<EM>Alpine</EM> doesn't have the ability to forward mail to another address.
<P>
Each filtering rule has a "Pattern" and a "Filter Action".
When a folder is opened, when new mail arrives in an open folder, or
when mail is Expunged from a folder; each
message is compared with the Patterns of your filtering rules.
The comparisons start with the first rule and keep going until there
is a match.
If a match is found, the message may be deleted or moved, depending on
the setting of the Filter Action.
If the message is not deleted, it may have its status altered.
<P>
For efficiency, each message is usually only checked once.
When new mail arrives, the new messages are checked but not the old.
There are some exceptions to this rule.
The expunge command will cause all messages to be rechecked, as will
editing of the filtering rules.
<P>
<EM>NOTE:</EM>
When setting up a Pattern used to delete messages,
it is recommended that you test the Pattern first with a "Move"
folder specified in
case unintended matches occur. Messages that are deleted will be removed
from the folder and <EM>unrecoverable</EM> from within <EM>Alpine</EM> after the
next Expunge command or once the folder being filtered has been closed.
<H3>Filter Patterns</H3>
In order to determine whether or not a message matches a filter the message is
compared with the Filter's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
"<A HREF="#patterns-section">here</A>".
<P>
Since filtering is a potentially destructive action, if you have a filtering
Pattern with nothing other than Current Folder Type set, that filtering
rule is ignored.
<H3>Filter Actions</H3>
Once a filter match is found for a particular message, there are some actions
which may be taken.
First, the message may have its status changed.
This is the same message status that you can manipulate manually using the
Flag Command.
There are four elements of message status that you can control.
You can set or clear the Important status, the New status, the Deleted
status, and the Answered status.
Of course, if the filter is going to delete the message,
then there is no point in setting message status.
You may also set or clear user-defined
<A HREF="#keywords">keywords</A> for a message.
<P>
Second, the filter may delete or move the message.
Deleting the message marks it Deleted and removes it from view.
It is effectively gone forever (though it technically is still there until
the next expunge command, which may happen implicitly).
Moving the message moves it from the open folder into the folder
listed on the "Folder List" line of the filter configuration.
If you list more than one folder name (separated by commas) then the message
will be copied to each of those folders.
In any case, if "Delete" or "Move" is set then the
message is removed from the current folder.
If you just want to set the messages status without deleting it from
the folder, then set the filter action to
"Just Set Message Status".
<P>
(There is no way to do a Copy instead of a Move, due to the difficulties
involved in keeping track of whether or not a message has
already been copied by a previous <EM>Alpine</EM> session.)
<H4><A NAME="move-only-if-not-deleted"></A>Move-only-if-not-deleted option</H4>
If you have specified a Move to Folder to filter messages into, then this
option has an effect.
If this option is set then messages will only be moved into the specified folder
if they aren't already marked deleted.
This might be useful if you have more than one <EM>Alpine</EM> session running
simultaneously and you don't want messages to be filtered into a folder
more than once.
This method is not foolproof.
There may be cases where a message gets marked deleted and so it is never
filtered into the folder.
For example, if you deleted it in another <EM>Alpine</EM> or
another mail program that didn't know about the filtering rule.
<P>
This option has no effect if the Filter Action is not set to Move.
<H4><A NAME="dont-quit-even-if-rule-matches"></A>Dont-quit-even-if-rule-matches option</H4>
If this option is set then this is a non-terminating rule.
Usually, for each message, <EM>Alpine</EM> searches through the filter rules until
a match is found and then it performs the action associated with that rule.
Rules following the match are not considered.
If this option is set then the search for matches will continue at the next
rule.
<P>
If a non-terminating rule matches then the actions associated with
that rule, except for any implied deletion of the message, are performed
before the match for the next rule is checked.
For example, if the non-terminating rule sets the Important status, then that
status will be set when the next rule is considered.
However, if the non-terminating rule Moves the message, the message will
actually be copied instead of copied and deleted so that it is still there
for the next rule.
A moved message is deleted after all the relevant rules have been checked.
The name of the "Move" action is confusing in this case because
a single message can be moved to more than one folder.
It turns the Move into a Copy instead, but it is still followed by a deletion
at the end.
<P>
This option may be useful if you want to have a single message filtered to
two different folders because it matches two different Patterns.
For example, suppose you normally filter messages to a particular mailing
list into one folder, and messages addressed directly to you into a second
folder.
If a message is sent to both you and the list (and you can tell that by
looking at the headers of the message) this option may give you a convenient
way to capture a copy to each folder.
(It may also cause you to capture two copies to each folder,
depending on whether your mail system delivers one or two copies of the
message to you and on how the list works.)
<H2><A NAME="scoring-config"></A>Scoring Configuration</H2>
Most people will not use scores at all, but if you do use them, here's how
they work in Alpine.
Using this screen, you may define Scoring rules.
The score for a message is calculated by looking at every Score rule defined
and adding up the Score Values for the ones which match the message.
If there are no matches for a message, it has a score of zero.
Message scores may be used a couple of ways in Alpine.
<H3>Sorting by Score</H3>
One of the methods you may use to sort message indexes is to sort by
score.
The scores of all the messages in a folder will be calculated and then
the index will be ordered by placing the messages in order of ascending or
descending score.
<H3>Scores for use in Patterns</H3>
The Patterns used for Roles, Index Line Coloring, and Filtering have a
category labeled "Score Interval".
When a message is being compared with a Pattern to check for a match, if
the Score Interval is set only messages which have a score somewhere in
the interval are a match.
<H3>Scoring Rule Patterns</H3>
In order to determine whether or not a message matches a scoring rule
the message is compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
"<A HREF="#patterns-section">here</A>".
<P>
Actually, Scoring rule Patterns are slightly different from the other types of
Patterns because Scoring rule Patterns don't contain a Score Interval.
In other words, when calculating the score for a message, which is done
by looking at the Scoring rule Patterns, scores aren't used.
<H3>Score Value</H3>
This is the value that will be added to the score for a message if the
rule's Pattern is a match.
Each individual Score Value is an integer between -100 and 100, and the
values from matching rules are added together to get a message's score.
There is also a way to extract the value from a particular header of each
message. See the help text for Score Value for further information.
<H2><A NAME="other-config"></A>Other Rules Configuration</H2>
Using this screen, you may define configuration Rules which don't fit
nicely into the other Rules categories.
<H3>Other Rule Patterns</H3>
Other Rules are a little different from the rest of the Rules because
they depend only on the current folder, and not on a particular message.
In order to determine whether or not a rule's actions should be applied
the current folder is compared with the rule's Pattern, which consists
of only the Current Folder Type.
Current Folder Type works the same for Other Rules as it does for Roles,
Filtering, Index Coloring, and Scoring.
Keep in mind that the only part of the Pattern which applies to Other
Rules is the Current Folder Type when looking at the description of
Patterns given
"<A HREF="#patterns-section">here</A>".
<H3>Other Rule Actions</H3>
Once a pattern match is found, the rule's Actions are taken.
Neither of the following two rule's depends on a message for its match.
That means that all the parts of the Pattern which depend on matching an
attribute of a message are ignored.
So the only part of the Pattern that matters for these Actions is
the Current Folder Type.
<H4>Set Sort Order</H3>
When you enter a new folder, these rules will be checked to see if you
have set a sort order which is different from your default sort order.
The default is set in the Setup/Config screen with
the <A HREF="#sort-key">Sort-Key</A> option.
If the Sort Order action is set, then the folder will be displayed sorted in
that sort order instead of in the default order.
<P>
A possible point of confusion arises when you change the configuration
of the Sort Order for the currently open folder.
The folder will normally be re-sorted when you go back to viewing the
index.
However, if you have manually sorted the folder with the
Sort command, it will not be re-sorted.
<H4>Set Index Format</H3>
When you enter a new folder, these rules will be checked to see if you
have set an Index Format which is different from your default Index Format,
which is set with the
<A HREF="#index-format"><EM>Index-Format</EM></A> option.
If so, the index will be displayed with this format instead of the default.
<H4>Set Startup Rule</H4>
When you enter a new folder, these rules will be checked to see if you
have set a startup rule which is different from the default startup rule.
The default for incoming folders is set in the Setup/Config screen with
the "incoming-startup-rule" option.
The default for folders other than INBOX that are not part of your
incoming collection
(see <A HREF="#enable-incoming-folders">enable-incoming-folders</A> feature)
is to start with the last message in the folder.
If the Startup Rule is set to something other than "default",
then the rule will determine which message will be the current message when
the folder is first opened.
<P>
The various startup rule possibilities work the same here as they do in
the incoming collection, except that the folder can be any specific
folder or any folder type.
<H2><A NAME="search-rules-config"></A>Search Rules Configuration</H2>
One of the commands that becomes available when that feature is turned on
is the "; Select" command, which is used in the MESSAGE INDEX
screen to select a set of messages.
One way of selecting messages is to use a Rule.
All of the messages which match (or don't match if you wish)
a Rule's Pattern will be selected.
<P>
Any of your Rules may be used for this purpose.
You might already have Rules set up for filtering, index line color, scores, or roles;
and you may use any of those Rules with the Select command.
However, you might find it more convenient to set up a separate set of Rules
just for this purpose without having to worry about what other effects
they may cause.
That is the purpose of these Select Rules.
<H3>Rule Patterns</H3>
In order to determine whether or not a message is selected by a rule the
message is
compared with the rule's Pattern.
These Patterns are the same for use with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules, so are described in only one place,
"<A HREF="#patterns-section">here</A>".
<P>
There is no action associated with these Search Rules.
Only their Patterns are used.
<H2><A NAME="patterns-section"></A>Patterns</H2>
Patterns are used with Roles, Filtering, Index Coloring,
Scoring, Other Rules, and Search Rules.
Patterns are compared with a message to see if there is a match.
For Filtering, the messages being checked are all the messages in the
folder, one at a time.
For Index Line Coloring, each message that is visible on the screen is
checked for matches with the Index Coloring Patterns.
Roles are used with the Reply, Forward, and Compose commands.
For Reply, the message used to compare the Pattern with is the message
being replied to;
for Forward, the message used to compare the Pattern with is the message
being forwarded;
and for Compose, there is no message, so the parts of the Pattern which depend
on a message (everything other than Current Folder Type and the
Beginning of Month and Year)
are not used.
Only the Current Folder Type matters for Compose (plus the Beginning of
Month or Year, which you wouldn't usually use for a Role).
For Scoring, the message being scored is compared with all of the Score
Patterns, and the Score Values from the ones that match are added together to
get the message's score.
For Other Rules, there is no message. Only the Current Folder Type is checked
for Other Rules.
<P>
Each Pattern has several possible parts, all of which are optional.
In order for there to be a match, <EM>ALL</EM> of the
<EM>defined</EM> parts of the Pattern must match the message.
If a part is not defined it is considered a match.
For example, if the To pattern is not defined it will be
displayed as
<P>
<CENTER>To pattern = <No Value Set></CENTER>
<P>
That is considered a match because it is not defined.
This means that the Pattern with nothing defined is a match if the
Current Folder Type matches, but there is an exception.
Because filtering is a potentially destructive action, filtering Patterns
with nothing other than Current Folder Type defined are ignored.
If you really want a filtering Pattern to match all messages (subject to
Current Folder Type) the best way to do it is to define a Score interval
which includes all possible scores.
This would be the score interval <SAMP>(-INF,INF)</SAMP>.
This can be used even if you haven't defined any rules to Set Scores.
<P>
There are six predefined header patterns called the To, From, Sender, Cc, News,
and Subject patterns.
Besides those six predefined header patterns, you may add
additional header patterns with header fieldnames of your choosing.
You add an extra header pattern by placing the cursor on one of the
patterns while in the role editor and using the "eXtraHdr" command.
The Recip pattern is a header pattern which stands for Recipient (To OR Cc)
and the Partic pattern is a header pattern which stands for
Participant (From OR To OR Cc).
(Defining the Recip pattern does not have the same effect as defining both
the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
Similar to the header patterns are the AllText pattern and the BodyText pattern.
Instead of comparing this pattern's text against only the contents of
a particular header field, the text for the AllText pattern is compared
with text anywhere in the message's header or body, and the text for the
BodyText pattern is compared with text anywhere in the message's body.
<P>
Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
"!" "toggle NOT" command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
"!" at the beginning of the pattern line.
When the "!" is present, it reverses the meaning of the match.
That is, if the pattern matches then it is considered to NOT be a match, and
if it does not match it is considered to be a match.
<P>
Don't make the mistake of putting the "!" in the data field for
a pattern.
For example, if you type the characters "!urgent" into the Subject
pattern, the pattern will look like:
<P>
<PRE>
Subject pattern = !urgent
</PRE>
<P>
This means you want to match the 7 character sequence "!urgent".
In order to match messages which do not have "urgent" in
their Subject field, first type the characters "urgent" followed
by carriage return for the value of the Subject pattern, then negate it
by typing the "!" command.
It should look like
<P>
<PRE>
! Subject pattern = urgent
</PRE>
<P>
The contents of each of these header patterns (or the AllText or BodyText patterns) may
be a complete email address, part of an address, or a random set of
characters to match against.
It may also be a list of such patterns, which means you
are looking for a match against the first pattern in the list <EM>OR</EM>
the second pattern <EM>OR</EM> the third and so on.
For example, a Subject pattern equal to
<P>
<PRE>
Subject pattern = urgent
emergency
alert
</PRE>
<P>
would match all messages with a subject which contained at least one
of those words.
It would also match subjects containing the words "alerts" or
"Urgently".
<P>
The same example with "NOT" turned on would be
<P>
<PRE>
! Subject pattern = urgent
emergency
alert
</PRE>
<P>
which would match all messages with a subject which did NOT contain any of
those words.
You can use the "Add Value" command to add new words to the list,
or you can enter them as a comma-separated list.
<P>
(It is not possible to specify two patterns which must <EM>BOTH</EM> be
present for a match.
It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
pattern2 must be present,
and that is exactly what using a list does.)
<P>
The "Current Folder Type" and the "Score Interval" are
also part of the Pattern, although the "Score Interval" is not used
when checking for matches for Scoring.
There are five similar settings which relate to the status of the message.
These settings rely on the message being New or not, Deleted or not,
Answered or not, Important or not, and Recent or not.
There are also some other miscellaneous settings.
The first is the Age of the message in days.
Another is the Size of the message in bytes.
The third is a setting which detects whether or not the Subject of a
message contains raw 8-bit characters (unencoded characters with the most
significant bit set).
There is a setting which detects whether or not this is the first time
<EM>Alpine</EM> has been run this month (doesn't depend on individual messages),
and another which detects whether or not this is the first time <EM>Alpine</EM> has
been run this year.
Other parts of the Pattern detect whether or not the From address of a
message appears in your address book, whether or not certain keywords
are set for a message, and whether or not certain character sets are
used in a message.
<H3>Parts of a Pattern</H3>
<H4>Header patterns</H4>
A header pattern is simply text which is searched for in the corresponding
header field.
For example, if a Pattern has a From header pattern with the value
"@company.com", then only messages which have a From header
which contains the text "@company.com" will be possible
matches.
Matches don't have to be exact.
For example, if the relevant field of a message contains the text
"mailbox@domain" somewhere
in it, then header patterns of "box", or "x@d", or
"mailbox@domain" are all matches.
<P>
All parts of the Pattern must match so, for example,
if a message matches a defined
From pattern, it still must be checked against the other parts of the
Pattern which have been defined.
The To header pattern is a slightly special case.
If the message being checked has a Resent-To header
and the feature <A HREF="#use-resent-to-in-rules">Use-Resent-To-in-Rules</A> is turned on, the addresses
there are used in place of the addresses in the To header.
This is only true for the To header.
Resent-cc and Resent-From headers are never used unless you add them
with the eXtraHdrs command.
<P>
The meaning of a header pattern may be negated with the
"!" "toggle NOT" command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
"!" at the beginning of the pattern line.
It would look something like
<P>
<PRE>
! From pattern = susan@example.com
</PRE>
<P>
When the "!" is present, it reverses the meaning of the match.
<P>
If you want to check for the presence of a header field but don't care
about its value, then
the empty pattern which you get by entering a pair of
double quotes ("") should match any message which
has the corresponding header field.
<H4><A NAME="pattern_alltext">AllText patterns</A></H4>
AllText patterns are just like header patterns except that the text is
searched for anywhere in the message's headers or body, not just in the
contents of a particular header field.
<P>
<H4><A NAME="pattern_bodytext">BodyText patterns</A></H3>
BodyText patterns are just like header patterns except that the text is
searched for anywhere in the message's body, not just in the
contents of a particular header field.
<P>
If there is more than one header pattern or AllText pattern or BodyText pattern
for which you want to take the
same action there is a shorthand notation which may be used.
Any of these patterns may be a list of patterns instead of
just a single pattern.
If any one of the patterns in the list matches the message
then it is considered a match.
For example, if "company1" and "company2" both required
you to use the same role when replying to messages, you might have
a To pattern which looks like
<P>
<PRE>
To pattern = company1.com
company2.com
</PRE>
<P>
This means that if the mail you are replying to was addressed to
either "anything@company1.com" or "anything@company2.com",
then this Pattern is a match and the same actions will be taken.
<P>
The meaning of an AllText or BodyText pattern may be negated with the
"!" "toggle NOT" command.
You can tell that <EM>NOT</EM> has been turned on by looking for the character
"!" at the beginning of the pattern line.
When the "!" is present, it reverses the meaning of the match.
<P>
A technicality: Since comma is the character used to separate multiple values
in any of the fields which may have multiple values (such as header patterns,
AllText patterns, BodyText patterns, keywords, folder lists, and so on),
you must escape comma with a
backslash (\) if you want to include a literal comma in one of those fields.
In other words, if you type a backslash followed by a comma it will
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between
pattern values.
All other backslashes (those not followed by a comma) are literal
backslashes and should not be escaped.
It's unlikely you'll ever need to enter a literal comma or backslash in
any of the patterns.
<H4>Current Folder Type</H4>
The "Current Folder Type" may be set to one of four different
values: "Any", "News", "Email", or
"Specific".
If the value is set to "News", then the
Pattern will only match if the currently open folder is a newsgroup.
The value "Email" only matches if the current folder is not news and
the value "Any" causes any folder to match.
If the value of "Current Folder Type" is set to "Specific",
then you must fill in a value for "Folder", which is on the line
below the "Specific" line.
In this case you will only get a match if the currently open folder is
the specific folder you list.
You may give a list of folders instead of just a single
folder name, in which case the Pattern will match if the open folder is
any one of the folders in the list.
The name of each folder in the list may be either "INBOX",
the technical specification
of the folder (like what appears in your configuration file) or, if the
folder is one of your incoming folders, it may be the nickname you've given
the folder.
Here are some samples of specific folder names:
<P>
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
<P>
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
<P>
<CENTER><SAMP>mail/local-folder</SAMP></CENTER>
<P>
The easiest way to fill in the "Folder" field is to use
the "T" command which is available when the "Folder" line is
highlighted, or to use the "Take" command with the configuration
feature
<A HREF="#enable-rules-under-take">"enable-rules-under-take"</A>
turned on.
<P>
When reading a newsgroup, there may be a performance penalty
incurred when collecting the information necessary to check whether
or not a Pattern matches a message.
For this reason, the default Current Folder Type is set to "Email".
If you have Patterns with a Current Folder Type of either
"Any" or "News" and those Patterns are used for
Index Line Coloring or Scoring, you may experience
slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
<H4>Age Interval</H4>
The "Age Interval" may be set to an interval of message
ages which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Age Interval looks like
<P>
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
<P>
where "min_age" and "max_age" are integers greater
than or equal to zero.
The special value "INF" may be used for
the max value. It represents infinity.
<P>
Actually, this option may be defined as a list of intervals instead
of just a single interval.
The list is separated by commas.
It can look like
<P>
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
<P>
When there is an Age Interval defined, it is a match if the age, in days, of
the message is contained in any of the intervals.
The intervals include both endpoints.
<P>
Even though this option is called Age, it isn't actually
the <EM>age</EM> of the message.
Instead, it is how many days ago the message arrived in one of your folders.
If the current time is a little past midnight, then a message that arrived
just before midnight arrived yesterday, even though the message is only
a few minutes old.
By default, the date being used is not the date in the Date
header of the message.
It is the date that the message arrived in one of your folders.
When you Save a message from one folder to another that arrival date
is preserved.
If you would like to use the date in the Date header that is possible.
Turn on the option
<EM>use-date-header-for-age</EM>
near the bottom of the rule definition.
<P>
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
<H4><A NAME="pattern_size_interval">Size Interval</A></H3>
The "Size Interval" may be set to an interval of message
sizes which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Size Interval looks like
<P>
<CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
<P>
where "min_size" and "max_size" are integers greater
than or equal to zero.
The special value "INF" may be used for
the max value. It represents infinity.
<P>
Actually, this option may be defined as a list of intervals instead
of just a single interval.
The list is separated by commas.
It can look like
<P>
<CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
<P>
When there is a Size Interval defined, it is a match if the size, in bytes, of
the message is contained in any of the intervals.
The intervals include both endpoints.
<H4>Score Interval</H4>
The "Score Interval" may be set to an interval of message
scores which should be considered a match.
Like the other parts of the Pattern, if it is unset it will be ignored.
The Score Interval looks like
<P>
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
<P>
where "min_score" and "max_score" are integers between
-32000 and 32000.
The special values "-INF" and "INF" may be used for
the min and max values to represent negative and positive infinity.
<P>
Actually, a list of intervals may be used if you wish.
A list would look like
<P>
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
<P>
When there is a Score Interval defined, it is a match if the score for
the message is contained in any of the intervals in the list.
The intervals include the endpoints.
The score for a message is calculated by looking at every Score rule defined and
adding up the Score Values for the ones which match the message.
When deciding whether or not a Pattern matches a message for purposes of
calculating the score, the Score Interval is ignored.
<H4>Message Status</H4>
There are five separate message status settings.
By default, all five are set to the value "Don't care", which
will match any message.
The value "Yes" means that the particular status must be true
for a match, and the value "No" means that the particular
status must not be true for a match.
For example, one of the five Message Status settings is whether a message
is marked Important or not.
A "Yes" means that the message must be Important to be
considered a match and "No" means that the message must not be
Important to be considered a match.
The same is true of the other four message status settings which depend
on whether or not the message is New; whether the message has
been Answered or not; whether the message has been Deleted or not, and
whether the message is Recent or not.
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.
<H4>Message Keywords</H4>
Keywords are similar to Message Status, but they are chosen by the user.
Provided the mail server allows for it, you may add a set of possible keywords
to a folder and then you may set those keywords or not for each message
in the folder.
The syntax of this part of the Pattern is similar to the header patterns.
It is a list of keywords.
The Keyword part of the Pattern is a match if the message has any of
the keywords in the list set.
Like other parts of the Pattern, if this is unset it will be ignored.
<H4>Message Character Set</H4>
A message may use one or more character sets.
This part of the Pattern matches messages which make use of one or more of
the character sets specified in the pattern.
It will be considered a match if a message uses any of the character
sets in the list you give here.
The syntax of this part of the Pattern is similar to the header patterns
and the Message Keywords pattern.
It is a list of character sets.
<P>
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
GB2312) you may also use some shorthand names that <EM>Alpine</EM> provides.
These names are more understandable shorthand names for sets of
character set names.
Two examples are "Cyrillic" and "Greek".
Selecting one of these shorthand names is equivalent to selecting all of
the character sets that make up the set.
You can see all of these shorthand names and the lists of character sets
they stand for by typing the "T" command with the Character
Set pattern highlighted.
The Character Set part of the Pattern is a match if the message uses any
of the character sets in the list.
Like other parts of the Pattern, if this is unset it will be ignored.
<H4>Raw 8-bit in Subject</H4>
It seems that lots of unwanted email contains unencoded 8-bit characters
in the Subject.
Normally, characters with the 8th bit set are not allowed in the Subject
header unless they are MIME-encoded.
This option gives you a way to match messages which have Subjects which
contain unencoded 8-bit characters.
Setting this option will affect performance in large folders because the
subject of each message in the folder has to be checked.
<H4>Beginning of Month</H4>
This option gives you a way to take some action once per month.
The value "Yes" means that this must be the first time <EM>Alpine</EM> has
been run this month in order to count as a match,
<H4>Beginning of Year</H4>
This option gives you a way to take some action once per year.
The value "Yes" means that this must be the first time <EM>Alpine</EM> has
been run this year in order to count as a match,
<H4>From or Reply-To address in Address Books</H4>
This option gives you a way to match messages which have a From or
a Reply-To address
which is in one of your address books.
Only the simple entries in your address books are searched.
Address book distribution lists are ignored!
Setting this option will affect performance in large folders because the
From and Reply-To of each message in the folder have to be checked.
<H4>Categorizer Command</H4>
This is a command that is run with its standard input set to the message
being checked and its standard output discarded.
The full directory path should be specified.
The command will be run and then its exit status will be checked against
the Exit Status Interval, which defaults to just the value zero.
If the exit status of the command falls in the interval, it is considered
a match, otherwise it is not a match.
<P>
This option may actually be a list of commands.
The first one that exists and is executable is used.
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and
<EM>PC-Alpine</EM>.
<P>
If none of the commands in the list exists and is executable then the rule
is <EM>not</EM> a match.
If it is possible that the command may not exist, you should be careful
to structure your rules so that nothing destructive
happens when the command does not exist.
For example, you might have a filter that filters away spam when there is
a match but does nothing when there is not a match.
That would continue to work correctly if the command didn't exist.
However, if you have a filter which filters away spam when there is not
a match and keeps it when there is a match, that would filter everything
if the categorizer command didn't exist.
<H3><A NAME="help-for-pattern-config"></A>Help Configuring Pattern Fields</H3>
<DL COMPACT>
<DT> <A NAME="role-nickname"><EM>Nickname</EM></A>
<DD> This is a nickname to help you.
You should have a different nickname for each role you define.
The nickname will be used in the SETUP ROLE RULES screen to allow you to
pick a role to edit.
It will also be used when you send a message to let you know you are
sending with a different role than you use by default, and
it will be useful for choosing a role when composing with the Role command
or when composing with one of the Role Uses set to With Confirmation.
This field is not used in the outgoing message.
<P>
<DT> <A NAME="role-comment"><EM>Comment</EM></A>
<DD> This is a comment to help you.
This comment does not play any functional role, it is simply an optional
comment to help you remember what the rule is for.
<P>
<DT> <A NAME="to-pattern"><EM>To pattern</EM></A>
<DD> If this pattern is non-blank, then for this role to be considered a
match, at least one of the recipients from
the To line of the message being replied to or forwarded
must match this pattern.
In the case of the Compose command, this pattern and the other header
patterns are ignored.
If this pattern is a list of patterns, then at least one of the
recipients must match at least one of the patterns.
(Any other non-blank parts of the Pattern must match, too.)
If the message being replied to or forwarded has a Resent-To header line,
then that is used in place of the To line.
(Note that this special Resent rule only applies to the To header. The
Resent-From, Resent-Subject, and so on are not consulted.)
<P>
It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
"!" "toggle NOT" command.
This changes the meaning of the To pattern so that it has the opposite meaning.
It will be considered a match if there are no matches between the
addresses in the To: line and the list of To patterns.
<P>
Don't make the mistake of putting the "!" in the data field for
the pattern.
For example, if you type the characters "!frizzle" into the To
pattern, the pattern will look like:
<P>
<PRE>
To pattern = !frizzle
</PRE>
<P>
This means you want to match the 8 character sequence "!frizzle".
In order to match messages which do not have "frizzle" in
their To field, first type the characters "frizzle" followed
by carriage return for the value of the To pattern, then negate it
by typing the "!" command.
It should end up looking like
<P>
<PRE>
! To pattern = frizzle
</PRE>
<P>
<DT> <A NAME="from-pattern"><EM>From pattern</EM></A>
<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the From header of the message being replied to or forwarded instead
of the addresses from the To header.
<P>
<DT> <A NAME="sender-pattern"><EM>Sender pattern</EM></A>
<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the Sender header of the message being replied to or forwarded instead
of the addresses from the To header.
If there is no Sender header, then the From header is used instead.
<P>
<DT> <A NAME="cc-pattern"><EM>Cc pattern</EM></A>
<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the address from the CC header of the message being replied to or forwarded instead
of the addresses from the To header.
<P>
<DT> <A NAME="news-pattern"><EM>News pattern</EM></A>
<DD> If this pattern is non-blank, then for this role to be considered a
match, at least one of the newsgroups from
the Newsgroups line of the message must match this pattern.
If this pattern is a list of patterns, then at least one of the
newsgroups must match at least one of the patterns.
(Any other non-blank parts of the Pattern must match, too.)
<P>
<DT> <A NAME="subject-pattern"><EM>Subject pattern</EM></A>
<DD> This is similar to the other header patterns.
It is compared with
the contents from the Subject of the message being replied to or forwarded.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>
<DT> <A NAME="extra-header-patterns"><EM>Extra header patterns</EM></A>
<DD> There isn't actually a field called Extra header patterns, but you
may add extra header patterns by moving the cursor to one of the header
patterns and using the "eXtraHdr" command to add a new header
pattern.
You would do this if the six predefined header patterns don't cover the
header you want to use for pattern matching.
Once you've added an extra header pattern, you use it just like the
Subject pattern.
Of course, it is compared with
the contents from the particular header field of the message being replied
to or forwarded rather than the contents from the subject field.
To remove an extra header pattern from a role, use the "RemoveHdr"
command on the highlighted extra header.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>
<DT> <A NAME="recip-pattern"><EM>Recipient pattern</EM></A>
<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the addresses from both the To header and the Cc header
instead of just the addresses from the To header.
It's equivalent to having two different rules;
one with a To pattern and the other with the same Cc pattern.
<P>
<DT> <A NAME="partic-pattern"><EM>Participant pattern</EM></A>
<DD> This is just like the
<A HREF="#to-pattern"><EM>To pattern</EM></A>
except that it is compared with
the addresses from the To header, the Cc header, and the From header
instead of just the addresses from the To header.
It's equivalent to having three different rules;
one with a To pattern, another with the same Cc pattern, and another
with the same From pattern.
<P>
<DT> <A NAME="alltext-pattern"><EM>AllText pattern</EM></A>
<DD> This is similar to the header patterns.
Instead of comparing with text in a particular header field it is compared with
all of the text in the message header and body.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>
<DT> <A NAME="bodytext-pattern"><EM>BodyText pattern</EM></A>
<DD> Just like AllText, except it is compared only with the body of the
message, not the body and header.
<P>
If you enter non-ascii characters in this field then the search will be
done using the character set you have defined with the
<A HREF="#char-set">Character-Set</A>
configuration variable.
(The truly sophisticated may use an alternate character set for a search
by entering the MIME encoding of the header string here.)
<P>
<DT> <A NAME="age-interval"><EM>Age Interval</EM></A>
<DD>The Age Interval, if defined, is part of the Pattern.
If you use this, it should be set to something like:
<P>
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
<P>
where "min_age" and "max_age" are non-negative integers.
The special value "INF" may be used for the max value.
It represents infinity.
<P>
In rare cases it may be useful to use the more general form of the value,
which is a comma-separated list of intervals.
It would look something like:
<P>
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
<P>
When there is an Age Interval defined, it is a match if the age, in days, of
the message is contained in the interval.
The interval includes both endpoints.
If the option is set to a list of intervals then it is a match if the
age of the message is contained in any of the intervals.
<P>
Even though this option is called Age, it isn't actually
the <EM>age</EM> of the message.
Instead, it is how many days ago the message arrived in one of your folders.
If the current time is a little past midnight, then a message that arrived
just before midnight arrived yesterday, even though the message is only
a few minutes old.
By default, the date being used is not the date in the Date
header of the message.
It is the date that the message arrived in one of your folders.
When you Save a message from one folder to another that arrival date
is preserved.
If you would like to use the date in the Date header that is possible.
Turn on the option
<EM>use-date-header-for-age</EM>
near the bottom of the rule definition.
<P>
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
The age interval
<P>
<CENTER><SAMP>(2,2)</SAMP></CENTER>
<P>
matches all messages that arrived on the day before yesterday.
The interval
<P>
<CENTER><SAMP>(180,INF)</SAMP></CENTER>
<P>
matches all messages that arrived at least 180 days before today.
The interval
<P>
<CENTER><SAMP>(0,1)</SAMP></CENTER>
<P>
matches all messages that arrived today or yesterday.
<P>
<DT> <A NAME="score-interval"><EM>Score Interval</EM></A>
<DD> The Score Interval, if defined, is part of the Pattern.
If you use this, it should be set to something like:
<P>
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
<P>
where "min_score" and "max_score" are integers between
-32000 and 32000.
The special values "-INF" and "INF" can be used for
the min and max values.
These represent negative and positive infinity.
<P>
Actually, the value may be a list of intervals rather than just a
single interval if that is useful.
The elements of the list are separated by commas like:
<P>
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
<P>
When there is a Score Interval defined, it is a match if the score for
the message is contained in any of the intervals.
The intervals include both endpoints.
The score for a message is calculated by looking at every scoring rule
defined and adding up the Score Values for the rules which match the message.
<P>
<DT> <A NAME="keyword-pattern"><EM>Keyword pattern</EM></A>
<DD> A folder may have user-defined keywords.
These are similar to the Important flag which the user may set using the
Flag command.
The difference is that the Important flag is always present for each folder.
User-defined keywords are picked by the user.
You may add new keywords by defining them in the
<A HREF="#keywords">Keywords</A> option in the Setup/Config screen.
After you have added a potential keyword with the Keywords option,
the Flag command may be used to set or clear the keyword on individual messages.
If you have given a keyword a nickname when configuring it,
that nickname may be used instead of the actual keyword.
<P>
When filling in a value for this field, it may be easiest to use
the "T" command, which presents you with a list of the keywords
you have defined to choose from.
<P>
This part of the Pattern matches messages with certain keywords set.
It will be considered a match if a message has any of the keywords in the
list set.
<P>
It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
"!" "toggle NOT" command.
This changes the meaning of the Keyword pattern so that it has the opposite meaning.
It will be considered a match if none of the keywords in the list are set
for a message.
<P>
Don't make the mistake of putting the "!" in the data field for
the pattern.
For example, if you type the characters "!frizzle" into the Keyword
pattern, the pattern will look like:
<P>
<PRE>
Keyword pattern = !frizzle
</PRE>
<P>
This means you want to match the 8 character sequence "!frizzle".
In order to match messages which do not have the keyword "frizzle"
set, first type the characters "frizzle" followed
by carriage return for the value of the Keyword pattern, then negate it
by typing the "!" command.
It should end up looking like
<P>
<PRE>
! Keyword pattern = frizzle
</PRE>
<P>
<DT> <A NAME="charset-pattern"><EM>Character Set pattern</EM></A>
<DD> A message may use one or more character sets.
This part of the Pattern matches messages which make use of
certain specified character sets.
It will be considered a match if a message uses any of the character
sets in the list you give here.
<P>
When filling in a value for this field, you may use
the "T" command, which presents you with a large list of
possible character sets to choose from.
You may also just type in the name of a character set, and it need not
be one that Alpine knows about.
<P>
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
GB2312) you may also use some shorthand names that Alpine provides.
These names are more understandable shorthand names for sets of
character set names.
Two examples are "Cyrillic" and "Greek".
Selecting one of these shorthand names is equivalent to selecting all of
the character sets that make up the set.
You can see all of these shorthand names and the lists of character sets
they stand for by typing the "T" command.
<P>
For the purposes of this Pattern,
<EM>Alpine</EM> will search through a message for all of the text parts and
collect the character sets declared for each part.
It will also look in the Subject line for a character set used there.
<EM>Alpine</EM> does not actually look at the text of the message or the text
of the Subject to determine if a declared character set is actually
used, it looks only at the declarations themselves in the MIME part headers
and in the Subject.
<P>
It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
"!" "toggle NOT" command.
This changes the meaning of the Character Set pattern so that
it has the opposite meaning.
It will be considered a match if none of the character sets in the
list are used in a message.
<P>
Don't make the mistake of putting the "!" in the data field for
the pattern.
For example, if you type the characters "!GB2312" into the
Character Set pattern, the pattern will look like:
<P>
<PRE>
Charset pattern = !GB2312
</PRE>
<P>
This means you want to match the 7 character sequence "!GB2312".
In order to match messages which do not have the
character set "GB2312"
set, first type the characters "GB2312" followed
by carriage return for the value of the Character Set pattern, then negate it
by typing the "!" command.
It should end up looking like
<P>
<PRE>
! Charset pattern = GB2312
</PRE>
<P>
A technicality: Since comma is the character used to separate multiple
values in a pattern field, you have to escape comma with a backslash (\) if
you want to include a literal comma in the field.
In other words, if you type a backslash followed by a comma it will
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between
pattern values.
All other backslashes are literal backslashes and should not be escaped.
<P>
<DT> <A NAME="current-folder-type"><EM>Current Folder Type</EM></A>
<DD> The Current Folder Type is part of the Pattern.
It refers to the type of the currently open folder, which is the folder
you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
In order for a pattern to be considered a match, the current folder must
be of the type you set here.
The three types "Any", "News", and "Email" are
all what you might think.
<P>
If the Current Folder Type for a Pattern is set to "News", for
example, then
that will only be a match if the current folder is a newsgroup and
the rest of the Pattern matches.
The value "Specific" may be used when you want to limit the match
to a specific folder (not just a specific type of folder), or to a list of
specific folders.
In order to match a specific folder you must Select the "Specific"
button <EM>AND</EM> you must fill in
the name (or list of names) of
the folder in the "Folder" field.
If the current folder is any of the folders in the list, that is considered
a match.
The name of each folder in the list may be either "INBOX", the technical specification
of the folder (like what appears in your configuration file) or, if the
folder is one of your incoming folders, it may be the nickname you've given
the folder.
Here are a couple samples of specific folder names:
<P>
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
<P>
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
<P>
The easiest way to fill in the "Folder" field is to use
the T command which is available when the "Folder" line is
highlighted.
Note that you won't be able to edit the "Folder" line unless the
Current Folder Type is set to "Specific", and any value that
"Folder" has is ignored unless the type
is set to "Specific".
<P>
When reading a newsgroup, there may be a performance penalty
incurred when collecting the information necessary to check a Pattern.
For this reason, the default Current Folder Type is set to "Email".
For example, a role with a non-Normal Index Line Color
and a Current Folder Type of
"Any" or "News" may cause the MESSAGE INDEX
screen to draw more slowly when in a newsgroup.
<P>
<DT> <A NAME="message-status-important"><EM>Message Status Important</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the message must be
flagged "Important" in order to be a match; or "No", which
means the message must <EM>not</EM> be flagged "Important" in order
to be considered a match.
<P>
<DT> <A NAME="message-status-new"><EM>Message Status New</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the message must be
"New" in order to be a match; or "No", which
means the message must <EM>not</EM> be "New" in order
to be a match.
"New" is the same as <EM>Unseen</EM> and not "New" is the
same as <EM>Seen</EM>.
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.
<P>
<DT> <A NAME="message-status-recent"><EM>Message Status Recent</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the message must be
"Recent" in order to be a match; or "No", which
means the message must <EM>not</EM> be "Recent" in order
to be a match.
"Recent" means that the message was added to the folder since
the last time the folder was opened.
If more than one mail client has the folder opened, the message will
appear to be "Recent" to only one of the clients.
<P>
The nomenclature for New and Recent is a bit confusing:
<P>
New means that the message is Unseen.
It could have been in your mailbox for a long time but if you haven't looked
at it, it is still considered New.
That matches the default <EM>Alpine</EM> index display that shows an N for such a
message.
<P>
Recent means that the message was added to this folder since the last time
you opened the folder.
<EM>Alpine</EM> also shows an N by default for these types of messages.
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after
the other, a message would only show up as Recent in (at most) the first
<EM>Alpine</EM> session.
<P>
<DT> <A NAME="message-status-deleted"><EM>Message Status Deleted</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the message must be
marked "Deleted" in order to be a match; or "No", which
means the message must <EM>not</EM> be marked "Deleted" in order
to be a match.
<P>
If you are thinking of using this part of the Pattern as a way to prevent
messages from being filtered more than once in a Filter Pattern,
take a look at the Filter Option
<A HREF="#move-only-if-not-deleted">"move-only-if-not-deleted"</A>
instead.
It should work better than using this field since it will hide the filtered
messages even if they are already Deleted.
<P>
<DT> <A NAME="message-status-answered"><EM>Message Status Answered</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the message must be
marked "Answered" in order to be a match; or "No", which
means the message must <EM>not</EM> be marked "Answered" in order
to be a match.
<P>
<DT> <A NAME="subject-contains-raw-8bit"><EM>Subject Contains Raw 8-bit</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means the Subject of
the message must contain unencoded 8-bit characters (characters with the
most significant bit set)
in order to be a match; or "No", which
means the Subject must <EM>not</EM>
contain unencoded 8-bit characters in order to be a match.
<P>
<DT> <A NAME="beginning-of-month"><EM>Beginning of Month</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means this is the first
time <EM>Alpine</EM> has been run this month;
or "No", which
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this month.
The way that <EM>Alpine</EM> decides if it is the beginning of the month or not is
to compare today's date with the date stored in the
<A HREF="#last-time">Last-Time-Prune-Questioned</A>
variable in the config file.
If the month of today's date is later than the month stored in the variable,
then this is considered to be the first time you have run Alpine this month, and
that turns the Beginning of the Month option on.
<P>
<DT> <A NAME="beginning-of-year"><EM>Beginning of Year</EM></A>
<DD> This part of the Pattern may have one of three possible values.
The default value is "Don't care", which matches any message.
The other two values are "Yes", which means this is the first
time <EM>Alpine</EM> has been run this year;
or "No", which
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this year.
The way that <EM>Alpine</EM> decides if it is the beginning of the year or not is
to compare today's date with the date stored in the
<A HREF="#last-time">Last-Time-Prune-Questioned</A>
variable in the config file.
If the year of today's date is later than the year stored in the variable,
then this is considered to be the first time you have run Alpine this year, and
that turns the Beginning of the Year option on.
<P>
<DT> <A NAME="from-in-abook"><EM>From or Reply-To in Address Book</EM></A>
<DD> This part of the Pattern may have one of five possible values.
The default value is "Don't care", which matches any message.
The value "Yes, in any address book" means either the From address
or the Reply-To address of the message must be in at least one of your
address books in order to be a match.
The value "No, not in any address book"
means neither the From nor the Reply-To addresses may
be in any of your address books in order to be a match.
<P>
The values "Yes, in specific address books" and
"No, not in any of specific address books" are similar but instead
of depending on all address books you are allowed to give a list of address
books to look in.
Usually this would be a single address book but it may be a
list of address books as well.
For each of these "specific" address book options you Select which
of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
name (or list of names) of the address book in the
"Abook List" field.
The names to be used are those that appear in the ADDRESS BOOK LIST screen.
The easiest way to fill in the Abook List field it to use
the "T" command which is available when the "Abook List"
line is highlighted.
Note that you won't be able to edit the "Abook List" line unless the
option is set to one of the two "Specific", values.
<P>
<DT> <A NAME="categorizer-cmd-explained"><EM>Categorizer Command</EM></A>
<DD> This is a command that is run with its standard input set to the message
being checked and its standard output discarded.
The full directory path should be specified.
The command will be run and then its exit status will be checked against
the <EM>Exit Status Interval</EM>, which defaults to just the value zero.
If the exit status of the command falls in the interval, it is considered
a match, otherwise it is not a match.
<P>
This option may actually be a list of commands.
The first one that exists and is executable is used.
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and
<EM>PC-Alpine</EM>.
<P>
If none of the commands in the list exists and is executable then the rule
is <EM>not</EM> a match.
If it is possible that the command may not exist, you should be careful
to structure your rules so that nothing destructive
happens when the command does not exist.
For example, you might have a filter that filters away spam when there is
a match but does nothing when there is not a match.
That would continue to work correctly if the command didn't exist.
However, if you have a filter which filters away spam when there is not
a match and keeps it when there is a match, that would filter everything
if the categorizer command didn't exist.
<P>
The categorizer command is run and the result is the exit status of
that command.
If that exit status falls in the <EM>Exit Status Interval</EM>
then it is considered a match, otherwise it is not a match.
Of course for the entire rule to match, it must also be checked against
the other defined parts of the Pattern.
<P>
The <EM>Exit Status Interval</EM> defaults to the single value 0 (zero).
If you define it, it should be set to something like:
<P>
<CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
<P>
where "min_exit_value" and "max_exit_value" are integers.
The special values "INF" and "-INF" may be used for large
positive and negative integers.
<P>
Actually, a list of intervals may be used if you wish.
A list would look like
<P>
<CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
<P>
When there is an <EM>Exit Status Interval</EM> defined, it is a match if the exit status
of the categorizer command is contained in any of the intervals.
The intervals include both endpoints.
<P>
The default interval is
<P>
<CENTER><SAMP>(0,0)</SAMP></CENTER>
<P>
and it matches only if the command exits with exit status equal to zero.
<P>
It is also possible to set a <EM>Character Limit</EM> for the categorizer command.
Setting this option makes it possible to limit how much of the message
is made available to the categorizer command as input.
The default value (-1) means that the entire message is fed to the
command.
A value of 0 (zero) means that only the headers of the message are
made available.
A positive integer means that the headers plus that many characters from
the body of the message are passed to the categorizer.
<P>
</DL>
<H2><A NAME="configuring-news"></A>Configuring News</H2>
<EM>Alpine</EM> can access news folders in any one of three different ways:
<DL>
<DT>REMOTE NNTP</DT>
<DD>Using the Network News Transport Protocol (NNTP) to
access news on a remote news server. In this case the newsrc file is
stored on the machine where <EM>Alpine</EM> is running.
<P>
To specify a remote news-collection accessed via NNTP use the
SETUP/collectionList screen's "Add" command. Set the
Server: value to the NNTP server's hostname appended with the
communication method "/service=NNTP", and set the Path:
value to the "#news." namespace (without the quotes).
<P>
Instead of specifying a news-collection, you may simply set the
<A HREF="#nntp-server">nntp-server</A>
option, which will cause <EM>Alpine</EM> to create a default news-collection for you.
Another NNTP option which may be of interest is
<A HREF="#nntp-range">nntp-range</A>.
<DT>REMOTE IMAP</DT>
<DD>Using the Internet Message Access Protocol (IMAP) to
access news on a remote news server. In this case, your newsrc file is
stored on the news server, in your home directory, so you must have an
account on the news server, but you would be running <EM>Alpine</EM> on a different
machine. The news server must be running an IMAPd server process.
<P>
To specify a remote news-collection accessed via IMAP use the
SETUP/collectionList screen's "Add" command. Set the
Server: value to the IMAP server's hostname, and set the Path: value
to the "#news." namespace (without the quotes).
</DD>
<DT>LOCAL</DT>
<DD>Using local file access to the news database. In this
case, your newsrc file is stored on the news server, in your home
directory, so you must have an account on the news server, and you would
be running <EM>Alpine</EM> on the same machine.
<P>
To specify a local news-collection use the SETUP/collectionList
screen's "Add" command. Leave the Server: value blank, and
set the Path: value to the "#news." namespace (without the
quotes).
</DD>
</DL>
<P>
NOTE: Should no news-collection be defined as above, <EM>Alpine</EM> will
automatically create one using the Setup/Config screen's
"nntp-server" variable's value if defined. The collection
will be created as a "Remote NNTP" as described above.
<P>
If you are a <EM>PC-Alpine</EM> user, either option 1 (NNTP) or option 2 (IMAP) is
possible. If you don't have an account on the news server, or if the news
server is not running an IMAP daemon, then you must use NNTP. (If you are not
sure, ask your service provider, university, or company for help.) In
this case, your Unix .newsrc file can be transferred to your PC. A good
place to put it would be in the same directory as your PINERC file, under
the name NEWSRC, but you can
<A HREF="#newsrc-path">specify a different location</A>.
<P>
Other configuration features related to news are
<A HREF="#enable-8bit-nntp-posting">Enable-8bit-Nntp-Posting</A>.
<A HREF="#compose-sets-newsgroup-without-confirm">Compose-Sets-Newsgroup-Without-Confirm</A>,
<A HREF="#news-approximates-new-status">News-Approximates-New-Status</A>,
<A HREF="#news-deletes-across-groups">News-Deletes-Across-Groups</A>,
<A HREF="#news-offers-catchup-on-close">News-Offers-Catchup-On-Close</A>,
<A HREF="#news-post-without-validation">News-Post-Without-Validation</A>,
<A HREF="#news-read-in-newsrc-order">News-Read-in-Newsrc-Order</A>, and
<A HREF="#quell-extra-post-prompt">Quell-Extra-Post-Prompt</A>.
<HR>
<!-- pnuts -->
</BODY>
</HTML>
|
