| 1 |
<HTML><HEAD><TITLE>Alpine Technical Notes: Configuration and Preferences</TITLE></HEAD><BODY> |
| 2 |
<H1>Configuration and Preferences</H1> |
| 3 |
|
| 4 |
<H2><A NAME="pine-conf">Alpine Configuration</A></H2> |
| 5 |
|
| 6 |
There is very little in <EM>Alpine</EM> which <STRONG>requires</STRONG> compile-time |
| 7 |
configuration. In most cases, the compiled-in preferences will suit users |
| 8 |
and administrators just fine. When running <EM>Alpine</EM> on a UNIX system, the |
| 9 |
default built-in configuration can be changed by setting variables in the |
| 10 |
system configuration files, <CODE>/usr/local/lib/pine.conf</CODE> |
| 11 |
or <CODE>/usr/local/lib/pine.conf.fixed</CODE>. |
| 12 |
(Actually, these files can be changed using the configure arguments |
| 13 |
--with-system-pinerc=VALUE or --with-system-fixed-pinerc=VALUE.) |
| 14 |
The location of the pine.conf file can be changed with the -P command line |
| 15 |
argument. |
| 16 |
Both <EM>Alpine</EM> |
| 17 |
and <EM>PC-Alpine</EM> also use personal (user-based) configuration files. |
| 18 |
On UNIX machines, the personal configuration file is the |
| 19 |
file <CODE>~/.pinerc</CODE>. |
| 20 |
For <EM>PC-Alpine</EM> systems, the personal configuration file is in |
| 21 |
<CODE>$PINERC</CODE> or <CODE><PineRC registry value></CODE> or |
| 22 |
<CODE>${HOME}\ALPINE\PINERC</CODE> or |
| 23 |
<CODE><ALPINE.EXE </CODE>dir<CODE>>\PINERC</CODE>. |
| 24 |
Or the personal configuration file can be specified with the -p command |
| 25 |
line argument. |
| 26 |
<P> |
| 27 |
All of these configuration files, other than the fixed system |
| 28 |
config <CODE>pine.conf.fixed</CODE> on UNIX systems, may optionally |
| 29 |
be remote configuration files instead of local files. |
| 30 |
This is discussed further in the following section and in |
| 31 |
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>. |
| 32 |
|
| 33 |
<P> |
| 34 |
After the personal configuration, <EM>Alpine</EM> may optionally use |
| 35 |
a personal exceptions configuration file which is specified with the |
| 36 |
command line option "-x exceptions_config". |
| 37 |
"Exceptions_config" may also be either a local file or a remote |
| 38 |
configuration folder. |
| 39 |
For Unix <EM>Alpine</EM>, if you don't have a "-x" command line option, |
| 40 |
<EM>Alpine</EM> will look for the file "<CODE>.pinercex</CODE>" |
| 41 |
in the same local directory that the regular config file is located in. |
| 42 |
If the regular config file is remote then Unix <EM>Alpine</EM> looks in the home |
| 43 |
directory for "<CODE>.pinercex</CODE>". |
| 44 |
<P> |
| 45 |
For <EM>PC-Alpine</EM>, if you don't have a "-x" command line option, |
| 46 |
<EM>PC-Alpine</EM> will use the value of the |
| 47 |
environment variable <CODE>$PINERCEX</CODE>. |
| 48 |
If that is not set, <EM>PC-Alpine</EM> will look for |
| 49 |
the local file "<CODE>PINERCEX</CODE>" |
| 50 |
in the same local directory that the regular config file is located in. |
| 51 |
If the regular config file is remote then <EM>PC-Alpine</EM> looks in the |
| 52 |
local directory specified by the "-aux local_directory" command |
| 53 |
line argument, or the directory <CODE>${HOME}\ALPINE</CODE>, or |
| 54 |
in <CODE><ALPINE.EXE </CODE>directory<CODE>></CODE>. |
| 55 |
<P> |
| 56 |
|
| 57 |
The syntax of a non-list configuration variable is this: |
| 58 |
|
| 59 |
<BLOCKQUOTE> |
| 60 |
<variable> = <value><BR> |
| 61 |
</BLOCKQUOTE> |
| 62 |
|
| 63 |
If the value is absent then the variable is unset. To set a variable to |
| 64 |
the empty value two double quotes (""). This is equivalent to an absent value |
| 65 |
except that it overrides any system-wide default value that may be set. Quotes |
| 66 |
may be used around any value. All values are strings and end at the end |
| 67 |
of the line or the closing quote. Leading and trailing space is ignored |
| 68 |
unless it is included in the quotes. There is one variable, |
| 69 |
<EM>use-only-domain-name</EM>, for which the only |
| 70 |
appropriate values are <EM>yes</EM> and <EM>no</EM>. That's because it is |
| 71 |
a variable from the early days of <EM>Alpine</EM> before features existed. |
| 72 |
<P> |
| 73 |
|
| 74 |
There is also a |
| 75 |
second type of variable, lists. A list is a comma-separated list of |
| 76 |
values. The syntax for a list is: |
| 77 |
|
| 78 |
<BLOCKQUOTE> |
| 79 |
<variable> = <value> [, <value> , ... ]<BR> |
| 80 |
</BLOCKQUOTE> |
| 81 |
|
| 82 |
A list can be continued on subsequent lines by beginning the line with |
| 83 |
white-space. Both the per-user and global configuration files may contain |
| 84 |
comments which are lines beginning with a <CODE>#</CODE>. <P> |
| 85 |
|
| 86 |
For UNIX <EM>Alpine</EM>, there are five ways in which each variable can be set. |
| 87 |
In decreasing order of precedence they are: |
| 88 |
|
| 89 |
<OL> |
| 90 |
|
| 91 |
<LI> the system-wide <EM>fixed</EM> configuration file |
| 92 |
|
| 93 |
<LI> a command line argument |
| 94 |
|
| 95 |
<LI> the personal exceptions file |
| 96 |
|
| 97 |
<LI> the personal configuration file |
| 98 |
|
| 99 |
<LI> the system-wide configuration file. |
| 100 |
|
| 101 |
</OL><P> |
| 102 |
|
| 103 |
If the variable is not set in any of those places, there is a default |
| 104 |
setting in the source code. |
| 105 |
<P> |
| 106 |
So, system-wide fixed settings always take precedence over command line |
| 107 |
flags, which take precedence over per-user exception settings, which take precedence over per-user settings, which take precedence |
| 108 |
over system-wide configuration settings. |
| 109 |
<EM>PC-Alpine</EM> has the same list, except that it |
| 110 |
does not use a system-wide <EM>fixed</EM> configuration file. |
| 111 |
This can be modified slightly by using inheritance, which is covered below. |
| 112 |
<P> |
| 113 |
|
| 114 |
You may get a sample/fresh copy of the system configuration file by |
| 115 |
running <EM>alpine -conf</EM>. The result will be printed on the standard |
| 116 |
output with very short comments describing each variable. (The online help in |
| 117 |
the Setup screens provides much longer comments.) If you need to fix some |
| 118 |
of the configuration variables, you would use the same template for the |
| 119 |
fixed configuration file as for the regular system-wide configuration |
| 120 |
file. (If it isn't clear, the purpose of the fixed configuration file is |
| 121 |
to allow system administrators to restrict the configurability of <EM>Alpine</EM>. |
| 122 |
It is by no means a bullet-proof method.) <EM>Alpine</EM> will automatically create |
| 123 |
the personal configuration file the first time it is run, so there is no |
| 124 |
need to generate a sample. <EM>Alpine</EM> reads and writes the personal |
| 125 |
configuration file occasionally during normal operation. Users will not |
| 126 |
normally look at their personal configuration file, but will use the |
| 127 |
Setup screens from within <EM>Alpine</EM> to set the values in this file. If a |
| 128 |
user does add additional comments to the personal configuration file they |
| 129 |
will be retained. |
| 130 |
<P> |
| 131 |
|
| 132 |
References to environment variables may be included in the <EM>Alpine</EM> |
| 133 |
configuration files. The format is <CODE>$variable</CODE> or |
| 134 |
<CODE>${variable}.</CODE> The character <CODE>~</CODE> will be expanded to the |
| 135 |
<CODE>$HOME</CODE> environment variable. |
| 136 |
For a more complete explanation of how environment variables work, see |
| 137 |
the section |
| 138 |
<A HREF="config-notes.html#env-variables">Using Environment Variables</A>.<P> |
| 139 |
|
| 140 |
When environment variables are used for <EM>Alpine</EM> settings which take lists, |
| 141 |
you must have an environment variable set for each member of the list. |
| 142 |
That is, <EM>Alpine</EM> won't properly recognize an environment variable which is |
| 143 |
set equal to a comma-delimited list. It is OK to reference unset |
| 144 |
environment variables in the <EM>Alpine</EM> configuration file, which |
| 145 |
will expand to nothing. <P> |
| 146 |
|
| 147 |
<H3>Remote and Local Configuration</H3> |
| 148 |
|
| 149 |
There are two types of storage for configuration information. |
| 150 |
<EM>Local</EM> configuration files are used by default. |
| 151 |
These are just regular files on the UNIX system or on the PC. |
| 152 |
<EM>Remote</EM> configuration folders are stored on an IMAP server. |
| 153 |
The advantage of using a remote configuration is that the same information |
| 154 |
may be accessed from multiple platforms. |
| 155 |
For example, if you use one computer at work and another at home, the same |
| 156 |
configuration could be used from both places. |
| 157 |
A configuration change from one place would be seen in both places. |
| 158 |
Technical information about remote configuration is in |
| 159 |
<A HREF="low-level.html#remote-config"><EM>Remote Configuration</EM></A>. |
| 160 |
|
| 161 |
<H3>Generic and Exceptional Configuration</H3> |
| 162 |
|
| 163 |
If you use <EM>Alpine</EM> from more than one platform it may be convenient |
| 164 |
to split your configuration information into two pieces, a generic piece |
| 165 |
and exceptions which apply to a particular platform. |
| 166 |
For example, suppose you use <EM>Alpine</EM> from home and from work. |
| 167 |
Most of your configuration settings are probably the |
| 168 |
same in both locations, so those settings belong in the generic settings |
| 169 |
configuration. |
| 170 |
However, you may use a different SMTP server and INBOX |
| 171 |
from home than you do from work. |
| 172 |
The "smtp-server" and "inbox-path" variables could be |
| 173 |
part of your exceptional configuration so that they could be different in the |
| 174 |
two places. |
| 175 |
<P> |
| 176 |
You can use the command line option "-x config" |
| 177 |
to split your configuration into generic and exceptional pieces. |
| 178 |
Config may be either local or remote. |
| 179 |
<P> |
| 180 |
For most people, splitting the configuration information into two pieces is |
| 181 |
only going to be useful if the generic information is accessed remotely. |
| 182 |
If you already have a local pinerc file with settings you like you may find |
| 183 |
that the command Setup/RemoteConfigSetup will be useful in helping you |
| 184 |
convert to a remote configuration. |
| 185 |
The command line flag |
| 186 |
<A HREF="cmd-line.html#copy_pinerc">copy_pinerc</A> |
| 187 |
may also be useful. |
| 188 |
|
| 189 |
<H3>Configuration Inheritance</H3> |
| 190 |
|
| 191 |
Configuration inheritance is a power user feature. |
| 192 |
It is confusing and not completely supported by the configuration |
| 193 |
user interface. |
| 194 |
<P> |
| 195 |
For configuration variables which are lists, like "smtp-server" or |
| 196 |
"incoming-folders", |
| 197 |
the inheritance mechanism makes it possible to <EM>combine</EM> |
| 198 |
the values of options from different configuration locations instead |
| 199 |
of <EM>replacing</EM> the value. |
| 200 |
<A HREF="config-notes.html#config-inheritance">Configuration Inheritance</A> |
| 201 |
has more information about how inheritance is used. |
| 202 |
<P> |
| 203 |
|
| 204 |
<HR> |
| 205 |
|
| 206 |
<H2><A NAME="gen-conf">General Configuration Variables</A></H2> |
| 207 |
|
| 208 |
The following is a list of all <EM>Alpine</EM> configuration variables, in |
| 209 |
alphabetical order. Note that not all variables apply to all versions of |
| 210 |
<EM>Alpine</EM> and that some variables are only applicable in a system configuration |
| 211 |
file and some are only applicable in a personal configuration file. |
| 212 |
These are configuration <EM>variables</EM>. |
| 213 |
<A HREF="#features-conf">Configuration <EM>Features</EM></A> |
| 214 |
are in a separate section. |
| 215 |
<P> |
| 216 |
|
| 217 |
<DL COMPACT> |
| 218 |
|
| 219 |
<DT> <A NAME="addrbook-sort-rule"><EM>addrbook-sort-rule</EM></A> |
| 220 |
|
| 221 |
<DD> This variable sets up the default address book sorting. Currently, |
| 222 |
<EM>Alpine</EM> will accept the values <EM>dont-sort</EM>, |
| 223 |
<EM>fullname-with-lists-last</EM>, <EM>fullname</EM>, |
| 224 |
<EM>nickname-with-lists-last</EM>, and <EM>nickname</EM>. The default is |
| 225 |
to sort by fullname with lists last. |
| 226 |
If you use an address book from more than one computer and those |
| 227 |
computers sort the address book differently then the sort order |
| 228 |
will be the order where the last change to the address book was |
| 229 |
made. |
| 230 |
There are two reasons the sorting might be different on different |
| 231 |
systems. |
| 232 |
First, the addrbook-sort-rule may be set differently in the two |
| 233 |
places. |
| 234 |
Second, the collation rules on the two computers may be different. |
| 235 |
For example, one system might ignore special characters while the other |
| 236 |
doesn't or one may sort upper and lower case letters together while |
| 237 |
the other doesn't. |
| 238 |
In any case, the order you see is the order on the system where the |
| 239 |
last change was made, for example by an address book edit or a |
| 240 |
Take Address command. |
| 241 |
<P> |
| 242 |
This option is displayed as "Addressbook Sort Rule". |
| 243 |
<P> |
| 244 |
|
| 245 |
<DT> <A NAME="pers-abook"><EM>address-book</EM></A> |
| 246 |
|
| 247 |
<DD> A list of personal address books. |
| 248 |
Each entry in the list is an |
| 249 |
optional nickname followed by a pathname or file name relative to the home |
| 250 |
directory. |
| 251 |
The nickname is separated from the rest of the line with whitespace. |
| 252 |
Instead of a local pathname or file name, a remote folder name can be given. |
| 253 |
This causes the address book to |
| 254 |
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>. |
| 255 |
Remote folder syntax is discussed in |
| 256 |
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>. |
| 257 |
This list of address books will be combined with the |
| 258 |
<A HREF="#glob-abook"><EM>global-address-book</EM></A> |
| 259 |
list to arrive at the complete set of address books. <P> |
| 260 |
|
| 261 |
<DT> <A NAME="abook-formats"><EM>addressbook-formats</EM></A> |
| 262 |
|
| 263 |
<DD> This option specifies the format that address books are displayed in. |
| 264 |
By default, address books are displayed with the nicknames in the first |
| 265 |
column, the fullnames in the second column, and addresses in the third |
| 266 |
column. The system figures out reasonable defaults for the widths of the |
| 267 |
columns. An address book may be given a different format by listing |
| 268 |
special tokens in the order you want them to display. The possible tokens |
| 269 |
are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT. More details are included |
| 270 |
in the online help for this variable. <P> |
| 271 |
|
| 272 |
<DT> <A NAME="alt-addresses"><EM>alt-addresses</EM></A> |
| 273 |
|
| 274 |
<DD> This option provides a place for you to list alternate email addresses |
| 275 |
you may have. |
| 276 |
Each address in the list should be the actual email address part of an |
| 277 |
address, without the full name field or the angle brackets. |
| 278 |
For example: |
| 279 |
|
| 280 |
<P> |
| 281 |
<CENTER><SAMP>[email protected]</SAMP></CENTER> |
| 282 |
<P> |
| 283 |
|
| 284 |
The matching is case-insensitive, so this would match any of |
| 285 |
<SAMP>[email protected]</SAMP>, <SAMP>[email protected]</SAMP>, or |
| 286 |
<SAMP>[email protected]</SAMP> as well. |
| 287 |
|
| 288 |
<P> |
| 289 |
If set, the option affects the behavior of the Reply |
| 290 |
command and the "+" symbol in the MESSAGE INDEX, which denotes that |
| 291 |
a message has been addressed specifically to you. |
| 292 |
|
| 293 |
<P> |
| 294 |
In the default INDEX display |
| 295 |
the personal name (or email address) of |
| 296 |
the person listed in the message's "From:" header |
| 297 |
field is usually displayed except when that address is yours or one of your |
| 298 |
alternate addresses. |
| 299 |
In that case you will usually see the name of |
| 300 |
the first person specified in the |
| 301 |
message's "To:" header field |
| 302 |
with the prefix "To: " prepended. |
| 303 |
|
| 304 |
<P> |
| 305 |
With respect to Reply, the reply-to-all option will exclude addresses |
| 306 |
listed here. |
| 307 |
|
| 308 |
<P> |
| 309 |
The feature |
| 310 |
<A HREF="#copy-to-to-from">copy-to-address-to-from-if-it-is-us</A> |
| 311 |
is somewhat related to this option. |
| 312 |
|
| 313 |
<P> |
| 314 |
In addition to a list of actual addresses, |
| 315 |
you may use regular expressions (as used with grep -E with the ignore case flag) |
| 316 |
to describe the addresses you want to match. |
| 317 |
<EM>Alpine</EM> will somewhat arbitrarily interpret your entry as a regular |
| 318 |
expression if it contains any of the characters |
| 319 |
*, |, +, ?, {, [, ^, $, or \. |
| 320 |
Otherwise, it will be treated literally. |
| 321 |
The feature |
| 322 |
<A HREF="#disable-regex">disable-regular-expression-matching-for-alternate-addresses</A> |
| 323 |
may be used to turn off regular expression processing regardless of whether or not |
| 324 |
special characters appear in the entry. |
| 325 |
|
| 326 |
<P> |
| 327 |
A description of how regular expressions work is beyond the |
| 328 |
scope of this help text, but some examples follow. |
| 329 |
|
| 330 |
<P> |
| 331 |
The entry |
| 332 |
|
| 333 |
<P> |
| 334 |
<CENTER><SAMP>.*@example.com</SAMP></CENTER> |
| 335 |
<P> |
| 336 |
|
| 337 |
in the alt-addresses list would mean that any |
| 338 |
address with a domain name of <SAMP>example.com</SAMP> (such as |
| 339 |
<SAMP>[email protected]</SAMP> or <SAMP>[email protected]</SAMP>) will be considered |
| 340 |
one of your alternate addresses. |
| 341 |
Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with |
| 342 |
a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought |
| 343 |
to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>. |
| 344 |
Complicating things further, the dollar sign |
| 345 |
is special in the <EM>Alpine</EM> configuration (it signifies environment variable expansion) |
| 346 |
so the dollar sign should be doubled or backslash escaped for <EM>Alpine</EM>'s sake. |
| 347 |
Quotes around the whole expression will not escape the dollar sign successfully. |
| 348 |
So this example should look like |
| 349 |
|
| 350 |
<P> |
| 351 |
<CENTER><SAMP>.*@example\.com$$</SAMP></CENTER> |
| 352 |
<P> |
| 353 |
|
| 354 |
<P> |
| 355 |
The entry |
| 356 |
|
| 357 |
<P> |
| 358 |
<CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER> |
| 359 |
<P> |
| 360 |
|
| 361 |
would match |
| 362 |
<SAMP>[email protected]</SAMP> or <SAMP>[email protected]</SAMP> as well |
| 363 |
as <SAMP>[email protected]</SAMP>. |
| 364 |
|
| 365 |
<P> |
| 366 |
You could match all addresses that look like |
| 367 |
<SAMP>[email protected]</SAMP> for any value of <SAMP>stuff</SAMP> with the |
| 368 |
entry |
| 369 |
|
| 370 |
<P> |
| 371 |
<CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER> |
| 372 |
<P> |
| 373 |
|
| 374 |
Notice that you have to escape the plus sign with a backslash because plus |
| 375 |
is a special character in regular expressions. |
| 376 |
If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP> |
| 377 |
the expression |
| 378 |
|
| 379 |
<P> |
| 380 |
<CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER> |
| 381 |
<P> |
| 382 |
|
| 383 |
would do it, but it would be easier to just add [email protected] as a |
| 384 |
separate entry. |
| 385 |
|
| 386 |
<P> |
| 387 |
One more example, a match of all first-level subdomains, is given by |
| 388 |
|
| 389 |
<P> |
| 390 |
<CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER> |
| 391 |
<P> |
| 392 |
|
| 393 |
<P> |
| 394 |
Because the regular expression matching is based on an old library |
| 395 |
(<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect, |
| 396 |
but they should be close. |
| 397 |
|
| 398 |
<P> |
| 399 |
This option is displayed as "Alternate Addresses". |
| 400 |
|
| 401 |
<DT> <A NAME="bugs-add"><EM>bugs-additional-data</EM></A> |
| 402 |
|
| 403 |
<DD> System-wide configuration files only. Program/Script used by |
| 404 |
<EM>Report Bug</EM> command. Output from the program/script is |
| 405 |
captured and attached to the bug report. <P> |
| 406 |
|
| 407 |
<DT> <A NAME="bugs"><EM>bugs-fullname</EM></A>, |
| 408 |
<EM>bugs-address</EM>, <EM>local-fullname</EM>, <EM>local-address</EM>, |
| 409 |
<EM>suggest-fullname</EM>, and <EM>suggest-address</EM> |
| 410 |
|
| 411 |
<DD> System-wide configuration files only. These are used by the bug |
| 412 |
report commands which can be accessed from some of the Help screens. |
| 413 |
<P> |
| 414 |
|
| 415 |
<DT> <A NAME="busy-cue-rate"><EM>busy-cue-rate</EM></A> |
| 416 |
|
| 417 |
<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that |
| 418 |
something is happening with a small animated display in the status |
| 419 |
message line near the bottom of the screen. |
| 420 |
This option sets how frequently the characters (for example, a spinning bar) |
| 421 |
in the active status message lines are updated. |
| 422 |
At most, it can be set to be updated 20 times per second. |
| 423 |
|
| 424 |
<P> |
| 425 |
Setting this value to zero will prevent display of the animations |
| 426 |
altogether. |
| 427 |
|
| 428 |
<P> |
| 429 |
The option |
| 430 |
<A HREF="#busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A> |
| 431 |
can be used to remove the randomness from this animated display. |
| 432 |
<P> |
| 433 |
|
| 434 |
<DT> <A NAME="char-set"><EM>character-set</EM></A> |
| 435 |
|
| 436 |
<DD> This is now obsolete, replaced by three separate variables: |
| 437 |
<EM>display-character-set</EM>, |
| 438 |
<EM>keyboard-character-set</EM>, and |
| 439 |
<EM>posting-character-set</EM>. |
| 440 |
See the section on |
| 441 |
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for more |
| 442 |
details.<P> |
| 443 |
|
| 444 |
<DT> <A NAME="color-style"><EM>color-style</EM></A> |
| 445 |
|
| 446 |
<DD> UNIX <EM>Alpine</EM> only (color is automatically on with <EM>PC-Alpine</EM>). |
| 447 |
If the terminal or terminal emulator you are using is capable of displaying |
| 448 |
colors, this variable controls whether or not |
| 449 |
color will be used in <EM>Alpine</EM>. |
| 450 |
If you turn color on and things are set up correctly, |
| 451 |
you should see color appear on the screen immediately. |
| 452 |
Modern terminal emulators are usually capable of displaying colors. |
| 453 |
<P> |
| 454 |
This variable may be set to any of the following values: |
| 455 |
<P> |
| 456 |
|
| 457 |
<DL> |
| 458 |
<DT>no-color</DT> |
| 459 |
<DD>Don't use color. |
| 460 |
</DD> |
| 461 |
|
| 462 |
<DT>use-termdef</DT> |
| 463 |
<DD>In order to decide if your terminal is capable of color, |
| 464 |
<EM>Alpine</EM> looks in |
| 465 |
the terminal capabilities database, TERMINFO or TERMCAP, depending on |
| 466 |
how <EM>Alpine</EM> was compiled. |
| 467 |
This is a good option to choose if you switch between a color and a non-color |
| 468 |
terminal with the same <EM>Alpine</EM> configuration. |
| 469 |
<EM>Alpine</EM> will know to use color on the color terminal because |
| 470 |
it is described |
| 471 |
in the termcap entry, and <EM>Alpine</EM> will know to use black and white on the |
| 472 |
non-color terminal. |
| 473 |
<A HREF="config-notes.html#color-config-notes">Color Details</A> |
| 474 |
has more information about configuring a termcap entry for color. |
| 475 |
This is usually something a system administrator does. |
| 476 |
</DD> |
| 477 |
|
| 478 |
<DT>force-ansi-8color</DT> |
| 479 |
<DD>Because setting up a termcap entry is confusing and because the |
| 480 |
terminal capabilities database is often not correctly configured for color, |
| 481 |
this choice and the next may be easier for you to use. |
| 482 |
If your terminal emulator responds to ANSI color escape sequences, which |
| 483 |
many do, this option will |
| 484 |
cause <EM>Alpine</EM> to believe your terminal will respond |
| 485 |
to the escape sequences which produce eight different foreground and background |
| 486 |
colors. |
| 487 |
The escape sequences used to set the foreground colors are |
| 488 |
|
| 489 |
<P><CENTER>ESC [ 3 <color_number> m</CENTER><P> |
| 490 |
|
| 491 |
where the color_number is an ASCII digit between 0 and 7. |
| 492 |
The numbers 0 through 7 should correspond to the colors black, red, green, |
| 493 |
yellow, blue, magenta, cyan, and white. |
| 494 |
Some terminal emulators use a pre-ANSI scheme which swaps |
| 495 |
the colors blue and red and the colors yellow and cyan. |
| 496 |
This will cause the default colors to be different, but other than that |
| 497 |
things should work fine. |
| 498 |
There is also a 9th color available, the last one shown, which is the default |
| 499 |
color from the terminal emulator. |
| 500 |
When used as a background color some people refer to this color as |
| 501 |
"transparent", which is why the letters "TRAN" are |
| 502 |
shown in the color swatch of the SETUP COLOR screen. |
| 503 |
The foreground transparent color is shown as |
| 504 |
the color of the "TRAN" text. |
| 505 |
(The transparent color will not work correctly in a PC-Alpine configuration.) |
| 506 |
The escape sequences used to set the background colors are the same |
| 507 |
as for the foreground colors except a "4" replaces the "3". |
| 508 |
<P> |
| 509 |
Note: With the Tera Term terminal emulator this setting works well. |
| 510 |
You should also have the Tera Term "Full color" option turned OFF. |
| 511 |
You may find the "Full color" option in Tera Term's "Setup" |
| 512 |
menu, in the "Window" submenu. |
| 513 |
</DD> |
| 514 |
|
| 515 |
<DT>force-ansi-16color</DT> |
| 516 |
<DD>Many terminal emulators know about the same eight colors above |
| 517 |
plus eight more. |
| 518 |
This option attempts to use all 16 colors. |
| 519 |
The same escape sequences as for the eight-color terminal are used |
| 520 |
for the first eight colors. |
| 521 |
The escape sequences used to set foreground colors 8-15 are the same as |
| 522 |
for 0-7 except the "3" is replaced with a "9". |
| 523 |
The background color sequences for colors 8-15 are the same as for 0-7 |
| 524 |
except the "4" is replaced with "10". |
| 525 |
You can tell if the 16 colors are working by turning on this option |
| 526 |
and then going into one of the color configuration screens, for example, |
| 527 |
the configuration screen for Normal Color. |
| 528 |
If you see 16 different colors to select from (plus a 17th for |
| 529 |
the transparent color), it's working. |
| 530 |
</DD> |
| 531 |
|
| 532 |
<DT>force-xterm-256color</DT> |
| 533 |
<DD>Some versions of xterm (and some other terminal emulators) |
| 534 |
have support for 256 colors. |
| 535 |
The escape sequences used to set the foreground colors are |
| 536 |
|
| 537 |
<P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P> |
| 538 |
|
| 539 |
where the color_number is an ASCII digit between 0 and 255. |
| 540 |
Background colors are the same with the 38 replaced with a 48. |
| 541 |
The numbers 0 through 15 are probably similar to the 16 color version |
| 542 |
above, then comes a 6x6x6 color cube, followed by 24 colors of gray. |
| 543 |
The terminal default (transparent) color is the 257th color at the bottom. |
| 544 |
Some terminal emulators will misinterpret these escape sequences causing |
| 545 |
the terminal to blink or overstrike characters or to do something else |
| 546 |
undesirable. |
| 547 |
<P> |
| 548 |
The PuTTY terminal emulator has an option called "Allow terminal to |
| 549 |
use xterm 256-colour mode" which allows PuTTY to work well with |
| 550 |
this 256-color setting. |
| 551 |
|
| 552 |
</DD> |
| 553 |
</DL> |
| 554 |
|
| 555 |
<P> |
| 556 |
There are two other possible color values which may be useful in some |
| 557 |
situations. |
| 558 |
In the color configuration screens there will sometimes be a color which has |
| 559 |
the label "NORM" inside its color swatch. |
| 560 |
If this is selected the corresponding foreground or background |
| 561 |
<A HREF="#normal-color"><EM>Normal Color</EM></A> |
| 562 |
will be used. |
| 563 |
Another similar color is the one that has the |
| 564 |
label "NONE" inside its color swatch. |
| 565 |
The meaning of this setting is that no color changing will be done. |
| 566 |
This NONE color is only useful in contexts where <EM>Alpine</EM> is already |
| 567 |
coloring the text some color other than the Normal Color. |
| 568 |
For example, if the |
| 569 |
<A HREF="#reverse-color"><EM>Reverse Color</EM></A> is set then the current |
| 570 |
line in the MESSAGE INDEX will be colored. |
| 571 |
If one of the index symbols (for example, the Index-to-me Symbol) has the NONE |
| 572 |
color as its background then the symbol's foreground color will be used |
| 573 |
to draw the actual text but the background color will be the same as whatever |
| 574 |
the background color already was. |
| 575 |
The color values which end up in the configuration file for these special |
| 576 |
values are the 11-character words "norm-padded", "none-padded", |
| 577 |
and "transparent". |
| 578 |
|
| 579 |
<P> |
| 580 |
The normal default is "no-color". |
| 581 |
<P> |
| 582 |
Once you've turned on color you may set the |
| 583 |
colors of many objects on the screen individually. |
| 584 |
The <A HREF="#color-config">Color Configuration</A> section has more |
| 585 |
information, or you may just try it by |
| 586 |
running the "Setup" command and typing "K" |
| 587 |
for Kolor to enter the color configuration screen (Kolor instead of Color |
| 588 |
because C means Config). |
| 589 |
Most categories of color which <EM>Alpine</EM> supports are configurable there. |
| 590 |
<A HREF="#index-color-config">Index line color</A> is configured separately. |
| 591 |
<P> |
| 592 |
|
| 593 |
<DT> <A NAME="composer-word-separators"><EM>composer-word-separators</EM></A> |
| 594 |
|
| 595 |
<DD> This option affects how a "word" is defined in the composer. |
| 596 |
The definition of a word is used when using the Forward Word and Backward |
| 597 |
Word commands in the composer, as well as when using the spell checker. |
| 598 |
Whitespace is always considered a word separator. |
| 599 |
Punctuation (like question marks, periods, commas, and so on) is always |
| 600 |
a word separator if it comes at the end of a word. |
| 601 |
By default, a punctuation character which is in the middle of a word does |
| 602 |
not break up that word as long as the character before and the character |
| 603 |
after it are both alphanumeric. |
| 604 |
If you add a character to this option it will be considered a |
| 605 |
word separator even when it occurs in the middle of an alphanumeric word. |
| 606 |
For example, if you want to skip through each part of an address instead |
| 607 |
of skipping the whole address at once you might want to include"@" |
| 608 |
and "." in this list. |
| 609 |
If you want the word-skipper to stop on each part of a UNIX filename you |
| 610 |
could add "/" to the list. |
| 611 |
The equal sign and dash are other possibilities you might find helpful. |
| 612 |
<P> |
| 613 |
|
| 614 |
<DT> <A NAME="composer-wrap-column"><EM>composer-wrap-column</EM></A> |
| 615 |
|
| 616 |
<DD> This option specifies an aspect of <EM>Alpine</EM>'s Composer. This gives the |
| 617 |
maximum width that auto-wrapped lines will have. It's also the maximum |
| 618 |
width of lines justified using the ^J Justify command. The normal default |
| 619 |
is <EM>74</EM>. The largest allowed setting is normally <EM>80</EM> in order to |
| 620 |
prevent very long lines from being sent in outgoing mail. When the mail |
| 621 |
is actually sent, trailing spaces will be stripped off of each line. |
| 622 |
<P> |
| 623 |
|
| 624 |
<DT> <A NAME="current-indexline-style"><EM>current-indexline-style</EM></A> |
| 625 |
|
| 626 |
<DD> <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A>. |
| 627 |
<P> |
| 628 |
|
| 629 |
<DT> <A NAME="cust-hdr"><EM>customized-hdrs</EM></A> |
| 630 |
|
| 631 |
<DD> You may add your own custom headers to outgoing messages. |
| 632 |
Each header you specify here must include the header tag |
| 633 |
(Reply-To:, Approved:, etc.) |
| 634 |
and may optionally include a value for that header. |
| 635 |
If you want to see these custom headers each time you compose a message, |
| 636 |
you must add them to your |
| 637 |
<A HREF="#def-comp"><EM>default-composer-hdrs</EM></A> list, |
| 638 |
otherwise they become part |
| 639 |
of the rich header set which you only see when you press the rich header |
| 640 |
command. |
| 641 |
(If you are looking for a way to change which headers are <EM>displayed</EM> |
| 642 |
when you view a message, take a look at the |
| 643 |
<A HREF="#viewer-hdrs"><EM>viewer-hdrs</EM></A> |
| 644 |
option instead.) |
| 645 |
Here's an example which shows how you might set your From address |
| 646 |
<P> |
| 647 |
<CENTER><SAMP>From: Full Name <[email protected]></SAMP></CENTER> |
| 648 |
<P> |
| 649 |
and another showing how you might set a Reply-To address |
| 650 |
<P> |
| 651 |
<CENTER><SAMP>Reply-To: [email protected]</SAMP></CENTER> |
| 652 |
<P> |
| 653 |
You may also set non-standard header values here. |
| 654 |
For example, you could add |
| 655 |
<P> |
| 656 |
<CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER> |
| 657 |
<P> |
| 658 |
or even |
| 659 |
<P> |
| 660 |
<CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER> |
| 661 |
<P> |
| 662 |
If you include a value after the colon then that header will be included |
| 663 |
in your outgoing messages unless you delete it before sending. |
| 664 |
If a header in the Customized-Headers list has only a tag but no value, then |
| 665 |
it will not be included in outgoing messages unless you edit a value |
| 666 |
in manually. |
| 667 |
For example, if |
| 668 |
<P> |
| 669 |
<CENTER><SAMP>Reply-To:</SAMP></CENTER> |
| 670 |
<P> |
| 671 |
is in the list, then the Reply-To header will be available for editing |
| 672 |
but won't be included unless a value is added while in the composer. |
| 673 |
<P> |
| 674 |
It's actually a little more complicated than that. |
| 675 |
The values of headers that you set with the Customized-Headers option are |
| 676 |
defaults. |
| 677 |
If the message you are about to compose already has a value for a header, |
| 678 |
that value is used instead of a value from your Customized-Headers. |
| 679 |
For example, if you are Replying to a message the Subject field |
| 680 |
will already be filled in. |
| 681 |
In that case, if the Customized-Headers list contains a Subject line, the |
| 682 |
custom subject will <EM>NOT</EM> be used. |
| 683 |
The subject derived from the subject of the message you are Replying |
| 684 |
to will be used instead. |
| 685 |
<P> |
| 686 |
It is also possible to make header setting even more complicated and more |
| 687 |
automatic by using |
| 688 |
<A HREF="#role-config"><EM>Roles</EM></A>, |
| 689 |
but if all you want to do is set a default value for a header, you don't |
| 690 |
need to think about Roles. |
| 691 |
<P> |
| 692 |
If you change your From address you may also find it useful to add the |
| 693 |
changed From address to the |
| 694 |
<A HREF="#alt-addresses"><EM>alt-addresses</EM></A> |
| 695 |
configuration option. |
| 696 |
<P> |
| 697 |
Limitation: Because commas are used to separate the list of |
| 698 |
Customized-Headers, it is not possible to have the value of a |
| 699 |
header contain a comma. |
| 700 |
Nor is there currently an "escape" mechanism provided |
| 701 |
to make this work. |
| 702 |
<P> |
| 703 |
This option is displayed as "Customized Headers". |
| 704 |
<P> |
| 705 |
|
| 706 |
<DT> <A NAME="dead-letter-files"><EM>dead-letter-files</EM></A> |
| 707 |
|
| 708 |
<DD> This option affects <EM>Alpine</EM>'s behavior when you cancel a message being |
| 709 |
composed. <EM>Alpine</EM>'s usual behavior is to write the canceled message to |
| 710 |
a file named |
| 711 |
"dead.letter" in your home directory, or |
| 712 |
"DEADLETR" when using <EM>PC-Alpine</EM>, |
| 713 |
overwriting any previous message. |
| 714 |
<P> |
| 715 |
If you set this option to a value higher than one, then that many copies |
| 716 |
of dead letter files will be saved. |
| 717 |
For example, if you set this option to "3" then you may have |
| 718 |
files named |
| 719 |
"DEADLETR", |
| 720 |
"DEADLETR2", and |
| 721 |
"DEADLETR3"; or |
| 722 |
"dead.letter", |
| 723 |
"dead.letter2", and |
| 724 |
"dead.letter3". |
| 725 |
In this example, the most recently cancelled message will be in |
| 726 |
"dead.letter", |
| 727 |
and the third most recently cancelled message will be in |
| 728 |
"dead.letter3". |
| 729 |
The fourth most recently cancelled message will no longer be saved. |
| 730 |
|
| 731 |
<P> |
| 732 |
If you set this option to zero, then NO record of canceled messages is |
| 733 |
maintained. |
| 734 |
<P> |
| 735 |
If the feature |
| 736 |
<A HREF="#quell-dead-letter-on-cancel">Quell-Dead-Letter-On-Cancel</A> |
| 737 |
is set, that overrides whatever you set for this option. |
| 738 |
If this option had existed at the time, then the Quell feature would not |
| 739 |
have been added, but it is still there for backwards compatibility. |
| 740 |
So, in order for this option to have the desired effect, make sure the |
| 741 |
Quell feature is turned off. |
| 742 |
<P> |
| 743 |
|
| 744 |
<DT> <A NAME="def-comp"><EM>default-composer-hdrs</EM></A> |
| 745 |
|
| 746 |
<DD> You can control which headers you want visible when composing outgoing |
| 747 |
email using this option. |
| 748 |
You can specify any of the regular set, any |
| 749 |
Rich Header, |
| 750 |
or any <A HREF="#cust-hdr"><EM>Customized-Hdrs</EM></A> |
| 751 |
which you have already defined. |
| 752 |
If you use this setting at all, you must specify all the |
| 753 |
headers you want to see, you can't just add to the regular header set. |
| 754 |
The default set is To:, Cc:, Attchmnt:, and Subject:. |
| 755 |
<P> |
| 756 |
|
| 757 |
Note that the "Newsgroups:" header will be abbreviated in the Composer |
| 758 |
display, but should be spelled out in full here. |
| 759 |
<P> |
| 760 |
This option is displayed as "Default Composer Headers". |
| 761 |
<P> |
| 762 |
|
| 763 |
<DT> <A NAME="def-fcc"><EM>default-fcc</EM></A> |
| 764 |
|
| 765 |
<DD> The name of the folder to which all outgoing mail goes is set here. |
| 766 |
The compiled-in default is <EM>sent-mail</EM> (UNIX) or <EM>sentmail</EM> |
| 767 |
(PC). It can be set to "" (two double quotes with nothing between them) |
| 768 |
to turn off saving copies of outgoing mail. If <EM>default-fcc</EM> is a |
| 769 |
relative file name, then it is relative to your default collection for |
| 770 |
saves (see <A HREF="#fold-coll"><EM>folder-collections</EM></A>). <P> |
| 771 |
This option is displayed as "Default Fcc (File carbon copy)". |
| 772 |
<P> |
| 773 |
|
| 774 |
<DT> <A NAME="def-save"><EM>default-saved-msg-folder</EM></A> |
| 775 |
|
| 776 |
<DD> This option determines the default folder name for <EM>Saves</EM>... |
| 777 |
If this is not a path name, it will be in the default collection for saves. |
| 778 |
Any valid folder specification, local or IMAP, is allowed. This default |
| 779 |
folder only applies when the |
| 780 |
<A HREF="#saved-msg-name"><EM>saved-msg-name-rule</EM></A> |
| 781 |
doesn't override it. |
| 782 |
Unix <EM>Alpine</EM> default is normally |
| 783 |
<EM>saved-messages</EM> in the default folder collection. |
| 784 |
<EM>PC-Alpine</EM> default is <EM>SAVEMAIL</EM> |
| 785 |
(normally stored as <EM>SAVEMAIL.MTX</EM>). <P> |
| 786 |
This option is displayed as "Default Saved Message Folder". |
| 787 |
<P> |
| 788 |
|
| 789 |
<DT> <A NAME="disable-these-auths"><EM>disable-these-authenticators</EM></A> |
| 790 |
|
| 791 |
<DD> This variable is a list of SASL (Simple Authentication and Security |
| 792 |
Layer) authenticators which will be disabled. |
| 793 |
SASL is a mechanism for |
| 794 |
authenticating to IMAP, POP3, SMTP, and other network servers. |
| 795 |
<P> |
| 796 |
|
| 797 |
<EM>Alpine</EM> matches its list of supported authenticators with the server to |
| 798 |
determine the most secure authenticator that is supported by both. |
| 799 |
If no matching authenticators are found, <EM>Alpine</EM> will revert to plaintext |
| 800 |
login (or, in the case of SMTP, will be unable to authenticate at all). |
| 801 |
<P> |
| 802 |
|
| 803 |
The candidates for disabling are listed below. |
| 804 |
There may be more if you compile <EM>Alpine</EM> with additional authenticators |
| 805 |
and/or a newer version of the c-client library. |
| 806 |
<P> |
| 807 |
|
| 808 |
<UL> |
| 809 |
<LI> GSSAPI |
| 810 |
<LI> CRAM-MD5 |
| 811 |
<LI> PLAIN |
| 812 |
<LI> LOGIN |
| 813 |
</UL> |
| 814 |
<P> |
| 815 |
|
| 816 |
Normally, you will not disable any authenticators. |
| 817 |
There are two exceptions: |
| 818 |
<P> |
| 819 |
|
| 820 |
<OL> |
| 821 |
<LI> You use a broken server that advertises an authenticator, |
| 822 |
but does not actually implement it. |
| 823 |
<LI> You have a Kerberos-capable version of <EM>Alpine</EM> and the server is |
| 824 |
also Kerberos-capable, but you can not obtain Kerberos |
| 825 |
credentials on the server machine, thus you desire to disable |
| 826 |
GSSAPI (which in turn disables <EM>Alpine</EM>'s Kerberos support). |
| 827 |
</OL> |
| 828 |
|
| 829 |
<P> |
| 830 |
It is never necessary to disable authenticators, since <EM>Alpine</EM> will try |
| 831 |
other authenticators before giving up. |
| 832 |
However, disabling the relevant authenticator avoids annoying error messages. |
| 833 |
<P> |
| 834 |
|
| 835 |
<DT> <A NAME="disable-these-drivers"><EM>disable-these-drivers</EM></A> |
| 836 |
|
| 837 |
<DD> This variable is a list of mail drivers which will be disabled. |
| 838 |
The candidates for disabling are listed below. |
| 839 |
There may be more in the future if you compile <EM>Alpine</EM> with |
| 840 |
a newer version of the c-client library. |
| 841 |
<P> |
| 842 |
|
| 843 |
<UL> |
| 844 |
<LI> mbox |
| 845 |
<LI> mbx |
| 846 |
<LI> mh |
| 847 |
<LI> mix |
| 848 |
<LI> mmdf |
| 849 |
<LI> mtx |
| 850 |
<LI> mx |
| 851 |
<LI> news |
| 852 |
<LI> phile |
| 853 |
<LI> tenex |
| 854 |
<LI> unix |
| 855 |
</UL> |
| 856 |
<P> |
| 857 |
|
| 858 |
The <EM>mbox</EM> driver enables the following behavior: if there is a |
| 859 |
file called <CODE>mbox</CODE> |
| 860 |
in your home directory, and if that file is either empty or in Unix mailbox |
| 861 |
format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver |
| 862 |
will automatically transfer mail from the system mail spool directory into the |
| 863 |
<CODE>mbox</CODE> file and |
| 864 |
delete it from the spool directory. If you disable the <EM>mbox</EM> driver, |
| 865 |
this will not happen. |
| 866 |
<P> |
| 867 |
|
| 868 |
It is not recommended to disable the driver which supports the system default |
| 869 |
mailbox format. On most non-SCO systems, that driver is the |
| 870 |
<EM>unix</EM> driver. |
| 871 |
On most SCO systems, it is the <EM>mmdf</EM> driver. |
| 872 |
The system default driver may be |
| 873 |
configured to something else on your system; check with your system manager |
| 874 |
for additional information. |
| 875 |
<P> |
| 876 |
|
| 877 |
It is most likely not very useful for you to disable any of the drivers other |
| 878 |
than possibly <EM>mbox</EM>. |
| 879 |
You could disable some of the others if you know for |
| 880 |
certain that you don't need them but the performance gain in doing so |
| 881 |
is very modest. |
| 882 |
<P> |
| 883 |
|
| 884 |
<DT> <A NAME="disp-char-set"><EM>display-character-set</EM></A> |
| 885 |
|
| 886 |
<DD> See the discussion in |
| 887 |
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for |
| 888 |
details.<P> |
| 889 |
|
| 890 |
<DT> <A NAME="display-filters"><EM>display-filters</EM></A> |
| 891 |
|
| 892 |
<DD> This option defines a list of text-filtering commands (programs or |
| 893 |
scripts) that may be used to filter text portions of received messages |
| 894 |
prior to their use (e.g., presentation in the "Message Text" display |
| 895 |
screen). For security reasons, the full path name of the filter command |
| 896 |
must be specified. |
| 897 |
<P> |
| 898 |
Display filters do not work with <EM>PC-Alpine</EM>. |
| 899 |
<P> |
| 900 |
|
| 901 |
The command is executed and the message is piped into its standard input. |
| 902 |
The standard output of the command is read back by <EM>Alpine</EM>. The |
| 903 |
<EM>_TMPFILE_</EM> token (see below) overrides this default behavior. |
| 904 |
|
| 905 |
<P> |
| 906 |
The filter's use is based on the configured <EM>trigger</EM> string. The |
| 907 |
format of a filter definition is: |
| 908 |
|
| 909 |
<P> |
| 910 |
<CENTER><trigger> <command> <arguments></CENTER> |
| 911 |
|
| 912 |
<P> |
| 913 |
You can specify as many filters as you wish, separating them with a comma. |
| 914 |
Each filter can have only one trigger and command. Thus, two trigger |
| 915 |
strings which invoke the same command require separate filter |
| 916 |
specifications. |
| 917 |
|
| 918 |
<P> |
| 919 |
The <EM>trigger</EM> is simply text that, if found in the message, |
| 920 |
will invoke the associated command. If the trigger contains any space |
| 921 |
characters, it must be placed within quotes. Likewise, should you |
| 922 |
wish a filter to be invoked unconditionally, define the trigger as the |
| 923 |
null string, "" (two consecutive double-quote characters). If the |
| 924 |
trigger string is found anywhere in the text of the message the filter |
| 925 |
is invoked. Placing the trigger text within the tokens defined below |
| 926 |
changes where within the text the trigger must be before considering |
| 927 |
it a match. |
| 928 |
|
| 929 |
<P> |
| 930 |
Trigger Modifying Tokens: |
| 931 |
<DL> |
| 932 |
<DT><EM>_CHARSET(<VAR>string</VAR>)_</EM> |
| 933 |
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command |
| 934 |
if the text is in a character set matching <VAR>string</VAR> |
| 935 |
(e.g., ISO-8859-2 or ISO-2022-JP). |
| 936 |
|
| 937 |
<DT><EM>_LEADING(<VAR>string</VAR>)_</EM> |
| 938 |
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command |
| 939 |
if the enclosed <VAR>string</VAR> is found to be the first |
| 940 |
non-whitespace text. |
| 941 |
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains |
| 942 |
the space character. |
| 943 |
|
| 944 |
<DT><EM>_BEGINNING(<VAR>string</VAR>)_</EM> |
| 945 |
<DD>This token tells <EM>Alpine</EM> to invoke the supplied command |
| 946 |
if the enclosed <VAR>string</VAR> is found at the beginning |
| 947 |
of any line in the text. |
| 948 |
<BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains |
| 949 |
the space character. |
| 950 |
</DL> |
| 951 |
|
| 952 |
<P> |
| 953 |
The "command" and "arguments" portion is simply |
| 954 |
the command line to be invoked if the trigger string is found. Below |
| 955 |
are tokens that <EM>Alpine</EM> will recognize and replace with special values |
| 956 |
when the command is actually invoked. |
| 957 |
|
| 958 |
<P> |
| 959 |
Command Modifying Tokens: |
| 960 |
|
| 961 |
<DL> |
| 962 |
<DT><EM>_TMPFILE_</EM> |
| 963 |
<DD>When the command is executed, this token is |
| 964 |
replaced with the path and name of the temporary |
| 965 |
file containing the text to be filtered. <EM>Alpine</EM> |
| 966 |
expects the filter to replace this data with the |
| 967 |
filter's result. |
| 968 |
|
| 969 |
NOTE: Use of this token implies that the text to |
| 970 |
be filtered is not piped into standard input of the |
| 971 |
executed command and its standard output is ignored. |
| 972 |
<EM>Alpine</EM> restores the tty modes before invoking the |
| 973 |
filter in case the filter interacts with the user |
| 974 |
via its own standard input and output. |
| 975 |
|
| 976 |
<DT><EM>_RESULTFILE_</EM> |
| 977 |
<DD>When the command is executed, this token is |
| 978 |
replaced with the path and name of a temporary |
| 979 |
file intended to contain a status message from the |
| 980 |
filter. <EM>Alpine</EM> displays this in the message status |
| 981 |
field. |
| 982 |
|
| 983 |
<DT><EM>_DATAFILE_</EM> |
| 984 |
<DD>When the command is executed, this token is |
| 985 |
replaced with the path and name of a temporary |
| 986 |
file that <EM>Alpine</EM> creates once per session and deletes |
| 987 |
upon exit. The file is intended to be used by the |
| 988 |
filter to store state information between instances |
| 989 |
of the filter. |
| 990 |
|
| 991 |
<DT><EM>_PREPENDKEY_</EM> |
| 992 |
<DD>When the command is executed, this token indicates that a random |
| 993 |
number will be passed down the input stream before the message text. |
| 994 |
This number could be used as a session key. |
| 995 |
It does not appear as a command-line argument. |
| 996 |
It is sent in this way to improve security. |
| 997 |
The number is unique to the current <EM>Alpine</EM> session |
| 998 |
and is only generated once per session. |
| 999 |
</DL> |
| 1000 |
|
| 1001 |
<P> |
| 1002 |
The feature |
| 1003 |
<A HREF="#disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A> is related. |
| 1004 |
<P> |
| 1005 |
Performance caveat/considerations: |
| 1006 |
<BR> |
| 1007 |
Testing for the trigger and invoking the filter doesn't come for free. |
| 1008 |
There is overhead associated with searching for the trigger string, testing |
| 1009 |
for the filter's existence and actually piping the text through the filter. |
| 1010 |
The impact can be reduced if the Trigger Modifying Tokens above are |
| 1011 |
employed. |
| 1012 |
<P> |
| 1013 |
Limitation: |
| 1014 |
<BR> |
| 1015 |
If Header Colors are being used, the sequences of bytes which indicate |
| 1016 |
color changes will be contained in the text which is passed to the |
| 1017 |
display-filter. |
| 1018 |
If this causes problems you'll need to turn off Header Colors. |
| 1019 |
The thirteen bytes which indicate a color change are |
| 1020 |
the character \377 followed by |
| 1021 |
\010 for a foreground color or \011 for a background color. |
| 1022 |
Then comes eleven characters of RGB data which looks something like |
| 1023 |
255, 0,255, depending on the particular color, of course. |
| 1024 |
<P> |
| 1025 |
|
| 1026 |
<DT> <A NAME="download-command"><EM>download-command</EM></A> |
| 1027 |
|
| 1028 |
<DD> This option affects the behavior of the <EM>Export</EM> command. |
| 1029 |
It specifies a Unix program name, and any necessary command line arguments, |
| 1030 |
that <EM>Alpine</EM> can use to transfer the exported message to your |
| 1031 |
personal computer's disk. |
| 1032 |
<P> |
| 1033 |
|
| 1034 |
<DT> <A NAME="download-command-prefix"><EM>download-command-prefix</EM></A> |
| 1035 |
|
| 1036 |
<DD> This option is used in conjunction with the <EM>download-command</EM> |
| 1037 |
option. |
| 1038 |
It defines text to be written to the terminal emulator (via standard |
| 1039 |
output) immediately prior to starting the download command. This is |
| 1040 |
useful for integrated serial line file transfer agents that permit command |
| 1041 |
passing (e.g., Kermit's APC method). <P> |
| 1042 |
|
| 1043 |
<DT> <A NAME="editor"><EM>editor</EM></A> |
| 1044 |
|
| 1045 |
<DD> UNIX <EM>Alpine</EM> only. Sets the name of the alternate editor for composing |
| 1046 |
mail (message text only, not headers). It will be invoked with the "^_" |
| 1047 |
command or it will be invoked automatically if the |
| 1048 |
<A HREF="#enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A> |
| 1049 |
feature is set. <P> |
| 1050 |
|
| 1051 |
<DT> <A NAME="empty-header-message"><EM>empty-header-message</EM></A> |
| 1052 |
|
| 1053 |
<DD> When sending, if both the To and Cc fields are empty and you |
| 1054 |
are sending the message to a Bcc, |
| 1055 |
<EM>Alpine</EM> will put a special address in the To line. The default value is |
| 1056 |
"undisclosed-recipients: ;". The reason for this is to avoid |
| 1057 |
embarrassment caused by some Internet mail transfer software that |
| 1058 |
interprets a "missing" To: header as an error and replaces it with an |
| 1059 |
Apparently-to: header that may contain the addresses you entered on the |
| 1060 |
Bcc: line, defeating the purpose of the Bcc. You may change the part |
| 1061 |
of this message that comes before the ": ;" by setting the |
| 1062 |
<EM>empty-header-message</EM> variable to something else. |
| 1063 |
<P> |
| 1064 |
|
| 1065 |
<DT> <A NAME="fcc-name-rule"><EM>fcc-name-rule</EM></A> |
| 1066 |
|
| 1067 |
<DD> Determines default folder name for fcc when composing. Currently, |
| 1068 |
<EM>Alpine</EM> will accept the values <EM>default-fcc</EM>, <EM>by-recipient</EM>, |
| 1069 |
or <EM>last-fcc-used</EM>. If set to <EM>default-fcc</EM>, then <EM>Alpine</EM> will |
| 1070 |
use the value defined in the <A HREF="#def-fcc"><EM>default-fcc</EM></A> |
| 1071 |
variable (which itself |
| 1072 |
has a default) for the Fcc header field. If set to <EM>by-recipient</EM>, |
| 1073 |
then <EM>Alpine</EM> will use the name of the recipient as a folder name for the fcc. |
| 1074 |
The relevant recipient is the first address in the To field. If set to |
| 1075 |
"last-fcc-used", then <EM>Alpine</EM> will offer to Fcc to whatever folder |
| 1076 |
you used previously. |
| 1077 |
In all cases, the field can still be edited after it is |
| 1078 |
initially assigned. If the fcc field in the address book is set for the |
| 1079 |
first To address, that value over-rides any value derived from this rule. |
| 1080 |
<P> |
| 1081 |
|
| 1082 |
<DT> <A NAME="feat-list"><EM>feature-list</EM></A> |
| 1083 |
|
| 1084 |
<DD> This is a list of the many features (options) which may be turned on |
| 1085 |
or off. There is a separate section titled |
| 1086 |
<A HREF="#features-conf">Configuration Features</A> which explains |
| 1087 |
each of the features. There is some additional explanation about the |
| 1088 |
<EM>feature-list</EM> variable itself |
| 1089 |
in <A HREF="config-notes.html#feature-list"><EM>Feature List Variable</EM></A>. |
| 1090 |
<P> |
| 1091 |
|
| 1092 |
<DT> <A NAME="file-directory"><EM>file-directory</EM></A> |
| 1093 |
|
| 1094 |
<DD> <EM>PC-Alpine</EM> only. |
| 1095 |
This value affects the Composer's "^J Attach" command, |
| 1096 |
the Attachment Index Screen's "S Save" command, and the |
| 1097 |
Message Index's "E Export" command. |
| 1098 |
|
| 1099 |
<P> |
| 1100 |
Normally, when a filename is supplied that lacks a leading "path" |
| 1101 |
component, <EM>Alpine</EM> assumes the file exists in the user's home directory. |
| 1102 |
Under Windows operating systems, this definition isn't always clear. This |
| 1103 |
feature allows you to explicitly set where <EM>Alpine</EM> should look for files |
| 1104 |
without a leading path. |
| 1105 |
|
| 1106 |
<P> |
| 1107 |
NOTE: this feature's value is ignored if either |
| 1108 |
<A HREF="#use-current-dir"><EM>use-current-dir</EM></A> feature |
| 1109 |
is set or the PINERC has a value for the |
| 1110 |
<A HREF="#operating-dir"><EM>operating-dir</EM></A> variable. |
| 1111 |
<P> |
| 1112 |
|
| 1113 |
<DT> <A NAME="fold-coll"><EM>folder-collections</EM></A> |
| 1114 |
|
| 1115 |
<DD> This is a list of one or more collections where saved mail is stored. |
| 1116 |
See the sections describing |
| 1117 |
<A HREF="config-notes.html#collections">folder collections and collection syntax</A> for more information. |
| 1118 |
The first collection in this list is the default |
| 1119 |
collection for <EM>Save</EM>s, |
| 1120 |
including <A HREF="#def-fcc"><EM>default-fcc</EM>'s</A>. |
| 1121 |
<P> |
| 1122 |
|
| 1123 |
<DT> <A NAME="folder-ext"><EM>folder-extension</EM></A> |
| 1124 |
|
| 1125 |
<DD> <EM>PC-Alpine</EM> only. File extension used for local folder names. This |
| 1126 |
is <CODE>.MTX</CODE> by default. |
| 1127 |
<P> |
| 1128 |
|
| 1129 |
<DT> <A NAME="reopen-rule"><EM>folder-reopen-rule</EM></A> |
| 1130 |
|
| 1131 |
<DD> <EM>Alpine</EM> normally checks for new mail in the currently open folder |
| 1132 |
and in the INBOX every few <A HREF="#mail-check"><EM>minutes</EM></A>. |
| 1133 |
|
| 1134 |
<P> |
| 1135 |
There are some situations where automatic new-mail checking does not work. |
| 1136 |
For example, if a mail folder is opened using the POP protocol or a newsgroup |
| 1137 |
is being read using the NNTP protocol, then new-mail checking is disabled. |
| 1138 |
|
| 1139 |
<P> |
| 1140 |
It may be possible to check for new mail in these cases by reopening the |
| 1141 |
folder. |
| 1142 |
<EM>Alpine</EM> does not do this for you automatically, but you may do the commands |
| 1143 |
manually to cause this to happen. |
| 1144 |
You reopen by going back to the folder list screen from the message |
| 1145 |
index screen with the "<" command, |
| 1146 |
and then going back into the message index screen with |
| 1147 |
the ">" command. |
| 1148 |
(Actually, any method you would normally use to open a folder will work the |
| 1149 |
same as the "<" followed by ">" method. |
| 1150 |
For example, the GoTo Folder command will work, or you may use L to go to the |
| 1151 |
Folder List screen and Carriage Return to reopen the folder.) |
| 1152 |
|
| 1153 |
<P> |
| 1154 |
There are some cases where <EM>Alpine</EM> knows that reopening the folder should |
| 1155 |
be useful as a way to discover new mail. |
| 1156 |
At the time of this writing, connections made using the POP protocol, |
| 1157 |
news reading using the NNTP protocol, local news reading, and local |
| 1158 |
ReadOnly folders which are in the traditional UNIX or the MMDF format all |
| 1159 |
fall into this category. |
| 1160 |
There are other cases where it <EM>may</EM> be a way to discover new mail, but <EM>Alpine</EM> |
| 1161 |
has no way of knowing, so it might also just be an exercise in futility. |
| 1162 |
All remote, ReadOnly folders other than those listed just above fall into this |
| 1163 |
category. |
| 1164 |
The setting of this option together with the type of folder |
| 1165 |
controls how <EM>Alpine</EM> will react to the apparent attempt to reopen a folder. |
| 1166 |
|
| 1167 |
<P> |
| 1168 |
If you don't reopen, then you will just be back in |
| 1169 |
the message index with no change. |
| 1170 |
You left the index and came back, but the folder remained "open" |
| 1171 |
the whole time. |
| 1172 |
However, if you do reopen the folder, the folder is closed and then reopened. |
| 1173 |
In this case, the current state of the open folder is lost. |
| 1174 |
The New status, Important and Answered flags, |
| 1175 |
selected state, Zoom state, collapsed or expanded state of threads, |
| 1176 |
current message number, |
| 1177 |
and any other temporary state is all lost when the reopen happens. |
| 1178 |
For POP folders (but not NNTP newsgroups) the Deleted flags are also lost. |
| 1179 |
|
| 1180 |
<P> |
| 1181 |
In the possibilities listed below, the text says "POP/NNTP" in |
| 1182 |
several places. |
| 1183 |
That really implies the case where <EM>Alpine</EM> knows it is a good way to discover |
| 1184 |
new mail, which is more than just POP and NNTP, but POP and NNTP are |
| 1185 |
the cases of most interest. |
| 1186 |
This option probably has more possible values than it deserves. They are: |
| 1187 |
<P> |
| 1188 |
|
| 1189 |
<DL> |
| 1190 |
<DT>Always reopen</DT> |
| 1191 |
<DD><EM>Alpine</EM> will not ask whether you want to reopen but will just do the reopen |
| 1192 |
whenever you type a command that implies a reopen, regardless of the |
| 1193 |
access method. |
| 1194 |
In other words, it is assumed you would always answer Yes if asked |
| 1195 |
about reopening. |
| 1196 |
</DD> |
| 1197 |
|
| 1198 |
<DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT> |
| 1199 |
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but |
| 1200 |
will ask you whether to reopen other remote folders, |
| 1201 |
with a default answer of Yes. |
| 1202 |
</DD> |
| 1203 |
|
| 1204 |
<DT>Yes for POP/NNTP, Ask about other remote [No]</DT> |
| 1205 |
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, but |
| 1206 |
will ask you whether to reopen other remote folders, |
| 1207 |
with a default answer of No. |
| 1208 |
</DD> |
| 1209 |
|
| 1210 |
<DT>Yes for POP/NNTP, No for other remote</DT> |
| 1211 |
<DD><EM>Alpine</EM> will assume a Yes answer if the access method is POP or NNTP, and |
| 1212 |
will assume a No answer for all other remote folders. |
| 1213 |
</DD> |
| 1214 |
|
| 1215 |
<DT>Always ask [Yes]</DT> |
| 1216 |
<DD><EM>Alpine</EM> will not differentiate based on access method. |
| 1217 |
It will always ask for all remote folders, with a default answer of Yes. |
| 1218 |
</DD> |
| 1219 |
|
| 1220 |
<DT>Always ask [No]</DT> |
| 1221 |
<DD><EM>Alpine</EM> will not differentiate based on access method. |
| 1222 |
It will always ask for all remote folders, with a default answer of No. |
| 1223 |
</DD> |
| 1224 |
|
| 1225 |
<DT>Ask about POP/NNTP [Yes], No for other remote</DT> |
| 1226 |
<DD><EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer |
| 1227 |
of Yes. |
| 1228 |
It will never attempt to reopen other remote folders. |
| 1229 |
</DD> |
| 1230 |
|
| 1231 |
<DT>Ask about POP/NNTP [No], No for other remote</DT> |
| 1232 |
<DD>This is the default. |
| 1233 |
<EM>Alpine</EM> will ask if the access method is POP or NNTP, with a default answer |
| 1234 |
of No. |
| 1235 |
It will never attempt to reopen other remote folders. |
| 1236 |
</DD> |
| 1237 |
|
| 1238 |
<DT>Never reopen</DT> |
| 1239 |
<DD><EM>Alpine</EM> will never attempt to reopen already open folders. |
| 1240 |
</DD> |
| 1241 |
</DL> |
| 1242 |
|
| 1243 |
<P> |
| 1244 |
Remember, wherever it says POP or NNTP above it really means POP or NNTP or |
| 1245 |
any of the other situations where it is likely that reopening is a good way |
| 1246 |
to discover new mail. |
| 1247 |
|
| 1248 |
<P> |
| 1249 |
There is an alternative that may be of useful in some situations. |
| 1250 |
Instead of manually checking for new mail you can set up a |
| 1251 |
<A HREF="config-notes.html#maildrop">Mail Drop</A> |
| 1252 |
and automatically check for new mail. |
| 1253 |
<P> |
| 1254 |
|
| 1255 |
<DT> <A NAME="folder-sort-rule"><EM>folder-sort-rule</EM></A> |
| 1256 |
|
| 1257 |
<DD> This option controls the order in which folder list entries will be |
| 1258 |
presented in the FOLDER LIST screen. Choose one of the following: |
| 1259 |
|
| 1260 |
<DL> |
| 1261 |
<DT> <EM>Alphabetical</EM> |
| 1262 |
|
| 1263 |
<DD> sort by alphabetical name independent of type |
| 1264 |
|
| 1265 |
<DT> <EM>Alpha-with-dirs-last</EM> |
| 1266 |
|
| 1267 |
<DD> sort by alphabetical name grouping directory entries |
| 1268 |
to the end of the list |
| 1269 |
|
| 1270 |
<DT> <EM>Alpha-with-dirs-first</EM> |
| 1271 |
|
| 1272 |
<DD> sort by alphabetical name grouping directory entries |
| 1273 |
to the start of the list |
| 1274 |
</DL> |
| 1275 |
|
| 1276 |
The normal default is <EM>Alphabetical</EM>. |
| 1277 |
<P> |
| 1278 |
|
| 1279 |
<DT> <A NAME="font-name"><EM>font-name</EM></A> |
| 1280 |
|
| 1281 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 1282 |
|
| 1283 |
<DT> <A NAME="font-size"><EM>font-size</EM></A> |
| 1284 |
|
| 1285 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 1286 |
|
| 1287 |
<DT> <A NAME="font-style"><EM>font-style</EM></A> |
| 1288 |
|
| 1289 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 1290 |
|
| 1291 |
<DT> <A NAME="forced-abook"><EM>forced-abook-entry</EM></A> |
| 1292 |
|
| 1293 |
<DD> System-wide <EM>Alpine</EM> configuration files only. |
| 1294 |
Force these address book |
| 1295 |
entries into all writable personal address books. |
| 1296 |
This is a list variable. Each item in the list has the form: |
| 1297 |
|
| 1298 |
<BLOCKQUOTE> |
| 1299 |
Nickname | Fullname | Address <BR> |
| 1300 |
</BLOCKQUOTE> |
| 1301 |
|
| 1302 |
with optional whitespace in all the obvious places. |
| 1303 |
<P> |
| 1304 |
|
| 1305 |
<DT> <A NAME="form-letter-folder"><EM>form-letter-folder</EM></A> |
| 1306 |
|
| 1307 |
<DD> A Form Letter Folder is a mail folder that is intended to |
| 1308 |
contain messages that you have composed and that are intended to be |
| 1309 |
sent in their original form repeatedly. |
| 1310 |
|
| 1311 |
<P> |
| 1312 |
Setting this variable will alter <EM>Alpine</EM>'s usual behavior when you |
| 1313 |
execute the Compose command. Normally, <EM>Alpine</EM> offers a chance to |
| 1314 |
continue a postponed or interrupted message should one or the other |
| 1315 |
exist. When this variable is set to a folder name that exists, <EM>Alpine</EM> |
| 1316 |
will also offer the chance to select a message from the folder to |
| 1317 |
insert into the composer, much like when continuing a postponed message. |
| 1318 |
The difference, however, is that <EM>Alpine</EM> will not automatically delete |
| 1319 |
the selected message from the Form Letter Folder. |
| 1320 |
<P> |
| 1321 |
Setting this variable will also affect <EM>Alpine</EM>'s behavior when you |
| 1322 |
Postpone a message from the composer. Normally, <EM>Alpine</EM> simply stashes |
| 1323 |
the message away in your |
| 1324 |
<A HREF="#postponed-folder"><EM>Postponed-Folder</EM></A>. |
| 1325 |
Regardless of the specified folder's existence, <EM>Alpine</EM> will ask which |
| 1326 |
folder you intend the message to be stored in. Choose the |
| 1327 |
"F" option to store the message in your Form Letter Folder. |
| 1328 |
This is the most common way to add a message to the folder. |
| 1329 |
|
| 1330 |
<P> |
| 1331 |
Another method of adding messages to the folder is via the <EM>Alpine</EM> |
| 1332 |
composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that |
| 1333 |
you expect to send in the same form again, you can enter the Form |
| 1334 |
Letter Folder's name in this field. <EM>Alpine</EM>, as usual, will copy the |
| 1335 |
message as it's sent. Note, when you later select this message from |
| 1336 |
your Form Letter Folder, it will have the same recipients as the original |
| 1337 |
message. |
| 1338 |
|
| 1339 |
<P> |
| 1340 |
To delete a message from the Form Letter Folder, you can either select |
| 1341 |
the folder from a suitable FOLDER LIST screen, or use the Delete |
| 1342 |
command in the MESSAGE INDEX offered when selecting from the folder as |
| 1343 |
part of the Compose command. You can delete a Form Letter Folder just |
| 1344 |
as any other folder from a suitable FOLDER LIST screen. |
| 1345 |
|
| 1346 |
<P> |
| 1347 |
You may find that the <A HREF="#role-config"><EM>Roles</EM></A> |
| 1348 |
facility can be used |
| 1349 |
to replace the Form Letter Folder. |
| 1350 |
|
| 1351 |
<P> |
| 1352 |
|
| 1353 |
<DT> <A NAME="glob-abook"><EM>global-address-book</EM></A> |
| 1354 |
|
| 1355 |
<DD> A list of shared address books. Each entry in the list is an |
| 1356 |
optional nickname followed by a pathname or file name relative to the home |
| 1357 |
directory. |
| 1358 |
A SPACE character separates the nickname from the rest of the line. |
| 1359 |
Instead of a local pathname or file name, a remote folder name can be given. |
| 1360 |
This causes the address book to |
| 1361 |
be a <A HREF="low-level.html#addrbook"><EM>Remote address book</EM></A>. |
| 1362 |
Remote folder syntax is discussed in |
| 1363 |
<A HREF="config-notes.html#remote-folders">Syntax for Remote Folders</A>. |
| 1364 |
This list will be added to the |
| 1365 |
<A HREF="#pers-abook"><EM>address-book</EM></A> list to |
| 1366 |
arrive at the complete set of address books. Global address books are |
| 1367 |
defined to be ReadOnly. <P> |
| 1368 |
|
| 1369 |
<DT> <A NAME="goto-default-rule"><EM>goto-default-rule</EM></A> |
| 1370 |
|
| 1371 |
<DD> This value affects <EM>Alpine</EM>'s behavior when using |
| 1372 |
the <EM>Goto</EM> command. |
| 1373 |
There are five possible values for this option: |
| 1374 |
<P> |
| 1375 |
|
| 1376 |
<DL> |
| 1377 |
|
| 1378 |
<DT> <EM>folder-in-first-collection</EM> |
| 1379 |
|
| 1380 |
<DD> <EM>Alpine</EM> will offer the most recently visited folder in the default |
| 1381 |
collection found in the "Collection List" screen as the default. |
| 1382 |
<P> |
| 1383 |
|
| 1384 |
<DT> <EM>inbox-or-folder-in-first-collection</EM> |
| 1385 |
|
| 1386 |
<DD> If the current folder is <EM>INBOX</EM>, |
| 1387 |
<EM>Alpine</EM> will offer the most recently visited folder in the |
| 1388 |
default collection found in the "Collection List" screen. |
| 1389 |
If the current folder is other than <EM>INBOX</EM>, |
| 1390 |
<EM>INBOX</EM> is offered as the default. |
| 1391 |
<P> |
| 1392 |
|
| 1393 |
<DT> <EM>inbox-or-folder-in-recent-collection</EM> |
| 1394 |
|
| 1395 |
<DD> This is <EM>Alpine</EM>'s default behavior. |
| 1396 |
If the current folder is <EM>INBOX</EM>, |
| 1397 |
<EM>Alpine</EM> will offer the last open |
| 1398 |
folder as the default. |
| 1399 |
If the current folder is other than <EM>INBOX</EM>, |
| 1400 |
<EM>INBOX</EM> is offered as the default. |
| 1401 |
<P> |
| 1402 |
|
| 1403 |
<DT> <EM>first-collection-with-inbox-default</EM> |
| 1404 |
|
| 1405 |
<DD> Instead of offering the most recently visited folder in the default |
| 1406 |
collection, the default collection is offered but with <EM>INBOX</EM> as |
| 1407 |
the default folder. |
| 1408 |
If you type in a folder name it will be in the default collection. |
| 1409 |
If you simply accept the default, however, your <EM>INBOX</EM> will be opened. |
| 1410 |
<P> |
| 1411 |
|
| 1412 |
<DT> <EM>most-recent-folder</EM> |
| 1413 |
|
| 1414 |
<DD> The last accepted value simply causes the most recently opened |
| 1415 |
folder to be offered as the default regardless of the currently opened |
| 1416 |
folder. |
| 1417 |
<P> |
| 1418 |
|
| 1419 |
</DL> |
| 1420 |
|
| 1421 |
NOTE: The default while a newsgroup is open remains the same; the last |
| 1422 |
open newsgroup. <P> |
| 1423 |
|
| 1424 |
<DT> <A NAME="header-general-background-color"><EM>header-general-background-color</EM></A> |
| 1425 |
<DT> <A NAME="header-general-foreground-color"><EM>header-general-foreground-color</EM></A> |
| 1426 |
|
| 1427 |
<DD> <A HREF="#header-colors"><EM>Header Colors</EM></A>. |
| 1428 |
<P> |
| 1429 |
|
| 1430 |
<DT> <A NAME="image-viewer"><EM>image-viewer</EM></A> |
| 1431 |
|
| 1432 |
<DD> This variable names the program to call for displaying parts of a |
| 1433 |
MIME message that are of type IMAGE. If your system supports the |
| 1434 |
<EM>mailcap</EM> system, you don't need to set this variable. <P> |
| 1435 |
|
| 1436 |
<DT> <A NAME="inbox-path"><EM>inbox-path</EM></A> |
| 1437 |
|
| 1438 |
<DD> This specifies the name of the folder to use for the <EM>INBOX</EM>. |
| 1439 |
By default this is unset and the system's default is used. |
| 1440 |
The most common reason for |
| 1441 |
setting this is to open an IMAP mailbox for the <EM>INBOX</EM>. For example, |
| 1442 |
<EM>{imap5.u.example.edu}inbox</EM> will open the user's standard |
| 1443 |
<EM>INBOX</EM> on the mail server, <EM>imap5</EM>. <P> |
| 1444 |
|
| 1445 |
<DT> <A NAME="incoming-archive-folders"><EM>incoming-archive-folders</EM></A> |
| 1446 |
|
| 1447 |
<DD> This is like <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A>, |
| 1448 |
only more general. This is a list |
| 1449 |
of folder pairs, with the first separated from the second in the pair by a |
| 1450 |
space. The first folder in a pair is the folder you want to archive, and |
| 1451 |
the second folder is the folder that read messages from the first should |
| 1452 |
be moved to. Depending on how you define the |
| 1453 |
<A HREF="#auto-read-msg"><EM>auto-move-read-msgs</EM></A> |
| 1454 |
feature, you may or may not be asked when you leave |
| 1455 |
the first folder if you want read messages to be moved to the second |
| 1456 |
folder. In either case, moving the messages means they will be deleted |
| 1457 |
from the first folder. <P> |
| 1458 |
|
| 1459 |
If these are not path names, they will be in the default collection for |
| 1460 |
<EM>Save</EM>s. Any valid folder specification, local or remote (via IMAP), is |
| 1461 |
allowed. There is no default. <P> |
| 1462 |
|
| 1463 |
<DT> <A NAME="incoming-check-interval"><EM>incoming-check-interval</EM></A> |
| 1464 |
|
| 1465 |
<DD> This option has no effect unless the feature |
| 1466 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 1467 |
is set, which in turn has no effect unless |
| 1468 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 1469 |
is set. |
| 1470 |
<P> |
| 1471 |
This option specifies, in seconds, how often <EM>Alpine</EM> will check |
| 1472 |
for new mail and state changes in Incoming Folders when Incoming Folders |
| 1473 |
Checking is turned on. |
| 1474 |
The default is 3 minutes (180). |
| 1475 |
This value applies only to folders that are local to the system that |
| 1476 |
<EM>Alpine</EM> is running on or that are accessed using the IMAP protocol. |
| 1477 |
The similar option |
| 1478 |
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A> |
| 1479 |
applies to all other monitored folders. |
| 1480 |
<P> |
| 1481 |
|
| 1482 |
<DT> <A NAME="incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A> |
| 1483 |
|
| 1484 |
<DD> This option has no effect unless the feature |
| 1485 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 1486 |
is set, which in turn has no effect unless |
| 1487 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 1488 |
is set. |
| 1489 |
<P> |
| 1490 |
This option together with the option |
| 1491 |
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A> |
| 1492 |
specifies, in seconds, how often <EM>Alpine</EM> will check |
| 1493 |
for new mail and state changes in Incoming Folders when Incoming Folders |
| 1494 |
Checking is turned on. |
| 1495 |
The default for this option is 3 minutes (180). |
| 1496 |
For folders that are local to this system or |
| 1497 |
that are accessed using the IMAP protocol |
| 1498 |
the value of the option |
| 1499 |
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A> |
| 1500 |
is used. |
| 1501 |
For all other monitored folders, the value of this option is used. |
| 1502 |
<P> |
| 1503 |
The reason there are two separate options is because it is usually |
| 1504 |
less expensive to check local and IMAP folders than it is to check |
| 1505 |
other types, like POP or NNTP folders. |
| 1506 |
You may want to set this secondary value to a higher number than |
| 1507 |
the primary check interval. |
| 1508 |
<P> |
| 1509 |
|
| 1510 |
<DT> <A NAME="incoming-check-list"><EM>incoming-check-list</EM></A> |
| 1511 |
|
| 1512 |
<DD> This option has no effect unless the feature |
| 1513 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 1514 |
is set, which in turn has no effect unless |
| 1515 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 1516 |
is set. |
| 1517 |
<P> |
| 1518 |
When monitoring the Incoming Message Folders for Unseen messages Alpine will |
| 1519 |
normally monitor all Incoming Folders. |
| 1520 |
You may use this option to restrict the list of monitored folders to a |
| 1521 |
subset of all Incoming Folders. |
| 1522 |
<P> |
| 1523 |
|
| 1524 |
<DT> <A NAME="incoming-check-timeout"><EM>incoming-check-timeout</EM></A> |
| 1525 |
|
| 1526 |
<DD> This option has no effect unless the feature |
| 1527 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 1528 |
is set, which in turn has no effect unless |
| 1529 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 1530 |
is set. |
| 1531 |
<P> |
| 1532 |
Sets the time in seconds that Alpine will |
| 1533 |
attempt to open a network connection used for monitoring for Unseen |
| 1534 |
messages in Incoming Folders. The default is 5. |
| 1535 |
If a connection has not completed within this many seconds Alpine will |
| 1536 |
give up and consider it a failed connection. |
| 1537 |
<P> |
| 1538 |
|
| 1539 |
<DT> <A NAME="inc-fold"><EM>incoming-folders</EM></A> |
| 1540 |
|
| 1541 |
<DD> This is a list of one or more folders other than <EM>INBOX</EM> that |
| 1542 |
may receive new messages. This list is slightly special in that it is |
| 1543 |
always expanded in the folder lister. In the future, it may become more |
| 1544 |
special. For example, it would be nice |
| 1545 |
if <EM>Alpine</EM> would monitor the folders |
| 1546 |
in this list for new mail. <P> |
| 1547 |
|
| 1548 |
<DT> <A NAME="incoming-startup-rule"><EM>incoming-startup-rule</EM></A> |
| 1549 |
|
| 1550 |
<DD> This rule affects <EM>Alpine</EM>'s behavior when opening |
| 1551 |
the <EM>INBOX</EM> or |
| 1552 |
another folder from the "INCOMING MESSAGE FOLDERS". |
| 1553 |
This rule tells <EM>Alpine</EM> |
| 1554 |
which message to make the current message when an incoming folder is opened. |
| 1555 |
There are seven possible values for this option: |
| 1556 |
<P> |
| 1557 |
|
| 1558 |
<DL> |
| 1559 |
|
| 1560 |
<DT> <EM>first-unseen</EM> |
| 1561 |
|
| 1562 |
<DD> The current message will be the first unseen message which has not been |
| 1563 |
marked deleted, or the last message if all of the messages have been seen. |
| 1564 |
This is the default setting. |
| 1565 |
<P> |
| 1566 |
|
| 1567 |
<DT> <EM>first-recent</EM> |
| 1568 |
|
| 1569 |
<DD> This is similar to <EM>first-unseen</EM>. Instead of first unseen |
| 1570 |
it is the first recent message. A message is considered to be recent if it |
| 1571 |
arrived since the last time the folder was open (by any mail client, not just |
| 1572 |
the current one). So this option causes the |
| 1573 |
current message to be set to the first undeleted-recent message, or the |
| 1574 |
last message if none is both undeleted and recent. |
| 1575 |
<P> |
| 1576 |
|
| 1577 |
<DT> <EM>first-important</EM> |
| 1578 |
|
| 1579 |
<DD> This will result in the current message being set to the first |
| 1580 |
message marked Important (but not Deleted). |
| 1581 |
If no messages are marked Important, then it will be the last message. |
| 1582 |
<P> |
| 1583 |
|
| 1584 |
<DT> <EM>first-important-or-unseen</EM> |
| 1585 |
|
| 1586 |
<DD> This selects the minimum of the first unseen and the first important |
| 1587 |
messages. |
| 1588 |
<P> |
| 1589 |
|
| 1590 |
<DT> <EM>first-important-or-recent</EM> |
| 1591 |
|
| 1592 |
<DD> This selects the first of the first recent and the first important |
| 1593 |
messages. |
| 1594 |
<P> |
| 1595 |
|
| 1596 |
<DT> <EM>first</EM> |
| 1597 |
|
| 1598 |
<DD> Set the current message to the first undeleted message unless all |
| 1599 |
are deleted. In that case set it to the last message. |
| 1600 |
<P> |
| 1601 |
|
| 1602 |
<DT> <EM>last</EM> |
| 1603 |
|
| 1604 |
<DD> Set the current message to the last undeleted message unless all |
| 1605 |
are deleted. In that case set it to the last message. |
| 1606 |
<P> |
| 1607 |
|
| 1608 |
</DL> |
| 1609 |
<P> |
| 1610 |
|
| 1611 |
<DT> <A NAME="incoming-unseen-background-color"><EM>incoming-unseen-background-color</EM></A> |
| 1612 |
<DT> <A NAME="incoming-unseen-foreground-color"><EM>incoming-unseen-foreground-color</EM></A> |
| 1613 |
|
| 1614 |
<DD> <A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A>. |
| 1615 |
<P> |
| 1616 |
|
| 1617 |
<DT> <A NAME="index-answered-background-color"><EM>index-answered-background-color</EM></A> |
| 1618 |
<DT> <A NAME="index-answered-foreground-color"><EM>index-answered-foreground-color</EM></A> |
| 1619 |
<DT> <A NAME="index-arrow-background-color"><EM>index-arrow-background-color</EM></A> |
| 1620 |
<DT> <A NAME="index-arrow-foreground-color"><EM>index-arrow-foreground-color</EM></A> |
| 1621 |
<DT> <A NAME="index-deleted-background-color"><EM>index-deleted-background-color</EM></A> |
| 1622 |
<DT> <A NAME="index-deleted-foreground-color"><EM>index-deleted-foreground-color</EM></A> |
| 1623 |
<DT> <A NAME="index-from-background-color"><EM>index-from-background-color</EM></A> |
| 1624 |
<DT> <A NAME="index-from-foreground-color"><EM>index-from-foreground-color</EM></A> |
| 1625 |
<DT> <A NAME="index-highpriority-background-color"><EM>index-highpriority-background-color</EM></A> |
| 1626 |
<DT> <A NAME="index-highpriority-foreground-color"><EM>index-highpriority-foreground-color</EM></A> |
| 1627 |
<DT> <A NAME="index-important-background-color"><EM>index-important-background-color</EM></A> |
| 1628 |
<DT> <A NAME="index-important-foreground-color"><EM>index-important-foreground-color</EM></A> |
| 1629 |
<DT> <A NAME="index-lowpriority-background-color"><EM>index-lowpriority-background-color</EM></A> |
| 1630 |
<DT> <A NAME="index-lowpriority-foreground-color"><EM>index-lowpriority-foreground-color</EM></A> |
| 1631 |
<DT> <A NAME="index-new-background-color"><EM>index-new-background-color</EM></A> |
| 1632 |
<DT> <A NAME="index-new-foreground-color"><EM>index-new-foreground-color</EM></A> |
| 1633 |
<DT> <A NAME="index-opening-background-color"><EM>index-opening-background-color</EM></A> |
| 1634 |
<DT> <A NAME="index-opening-foreground-color"><EM>index-opening-foreground-color</EM></A> |
| 1635 |
<DT> <A NAME="index-recent-background-color"><EM>index-recent-background-color</EM></A> |
| 1636 |
<DT> <A NAME="index-recent-foreground-color"><EM>index-recent-foreground-color</EM></A> |
| 1637 |
<DT> <A NAME="index-subject-background-color"><EM>index-subject-background-color</EM></A> |
| 1638 |
<DT> <A NAME="index-subject-foreground-color"><EM>index-subject-foreground-color</EM></A> |
| 1639 |
<DT> <A NAME="index-to-me-background-color"><EM>index-to-me-background-color</EM></A> |
| 1640 |
<DT> <A NAME="index-to-me-foreground-color"><EM>index-to-me-foreground-color</EM></A> |
| 1641 |
<DT> <A NAME="index-unseen-background-color"><EM>index-unseen-background-color</EM></A> |
| 1642 |
<DT> <A NAME="index-unseen-foreground-color"><EM>index-unseen-foreground-color</EM></A> |
| 1643 |
|
| 1644 |
<DD> <A HREF="#index-colors"><EM>Index Colors</EM></A>. |
| 1645 |
<P> |
| 1646 |
|
| 1647 |
<DT> <A NAME="index-format"><EM>index-format</EM></A> |
| 1648 |
|
| 1649 |
<DD> This option is used to customize the content of lines in the |
| 1650 |
MESSAGE INDEX screen. Each line is intended |
| 1651 |
to convey some amount of immediately relevant information about each |
| 1652 |
message in the current folder. |
| 1653 |
<P> |
| 1654 |
|
| 1655 |
<EM>Alpine</EM> provides a pre-defined set of informational fields with |
| 1656 |
reasonable column widths automatically computed. You can, however, |
| 1657 |
replace this default set by listing special tokens in the order you |
| 1658 |
want them displayed. |
| 1659 |
<P> |
| 1660 |
|
| 1661 |
The list of available tokens is |
| 1662 |
<A HREF="#index-tokens"><EM>here</EM></A>. |
| 1663 |
<P> |
| 1664 |
|
| 1665 |
Spaces are used to separate listed tokens. Additionally, you can |
| 1666 |
specify how much of the screen's width the taken's associated data |
| 1667 |
should occupy on the index line by appending the token with a pair of |
| 1668 |
parentheses enclosing either a number or percentage. For example, |
| 1669 |
"SUBJECT(13)" means to allocate 13 characters of space to the subject |
| 1670 |
column, and "SUBJECT(20%)" means to |
| 1671 |
allocate 20% of the available space |
| 1672 |
to the subjects column, while plain "SUBJECT" means the system will |
| 1673 |
attempt to figure out a reasonable amount of space. |
| 1674 |
<P> |
| 1675 |
|
| 1676 |
There is always one space between every pair of columns, so if you use fixed |
| 1677 |
column widths (like 13) you should remember to take that into account. |
| 1678 |
Several of the fields are virtually fixed-width, so it doesn't make |
| 1679 |
much sense to specify the width for them. The fields STATUS, |
| 1680 |
FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE, |
| 1681 |
and DESCRIPSIZE all fall into that category. |
| 1682 |
You <EM>may</EM> specify widths for those if you wish, but |
| 1683 |
you're probably better off letting the system pick those widths. <P> |
| 1684 |
|
| 1685 |
<P> |
| 1686 |
The default is equivalent to: |
| 1687 |
|
| 1688 |
<P> |
| 1689 |
<CENTER><SAMP>index-format=STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER> |
| 1690 |
|
| 1691 |
<P> |
| 1692 |
This means that the four fields without percentages will be allocated |
| 1693 |
first, and then 33% and 67% of the <EM>remaining</EM> space will go to |
| 1694 |
the from and subject fields. If one of those two fields is specified |
| 1695 |
as a percentage and the other is left for the system to choose, then |
| 1696 |
the percentage is taken as an absolute percentage of the screen, not |
| 1697 |
of the space remaining after allocating the first four columns. It |
| 1698 |
doesn't usually make sense to do it that way. If you leave off all |
| 1699 |
the widths, then the subject and from fields (if both are present) are |
| 1700 |
allocated space in a 2 to 1 ratio, which is almost exactly the same as |
| 1701 |
the default. |
| 1702 |
|
| 1703 |
<P> |
| 1704 |
What you are most likely to do with this configuration option is to |
| 1705 |
specify which fields appear at all, which order they appear in, and the |
| 1706 |
percentage of screen that is used for the from and subject fields if you |
| 1707 |
don't like the 2 to 1 default. |
| 1708 |
<P> |
| 1709 |
If you want to retain the default format that <EM>Pine</EM> 4.64 had, use |
| 1710 |
|
| 1711 |
<P> |
| 1712 |
<CENTER><SAMP>Index-Format=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER> |
| 1713 |
<P> |
| 1714 |
|
| 1715 |
<EM>and</EM> set the feature |
| 1716 |
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A>. |
| 1717 |
|
| 1718 |
<P> |
| 1719 |
|
| 1720 |
<DT> <A NAME="initial-keystroke-list"><EM>initial-keystroke-list</EM></A> |
| 1721 |
|
| 1722 |
<DD> This is a comma-separated list of keystrokes which <EM>Alpine</EM> executes on |
| 1723 |
startup. Items in the list are usually just characters, but there are |
| 1724 |
some special values. <EM>SPACE,</EM> <EM>TAB,</EM> and <EM>CR</EM> mean a |
| 1725 |
space character, tab character, and a carriage return, respectively. |
| 1726 |
<EM>F1</EM> through <EM>F12</EM> stand for the twelve function keys. |
| 1727 |
<EM>UP, DOWN, LEFT, </EM>and<EM> RIGHT </EM>stand for the arrow keys. |
| 1728 |
Control characters are represented with <EM>^<char></EM>. A |
| 1729 |
restriction is that you can't mix function keys and character keys in this |
| 1730 |
list even though you can, in some cases, mix them when running <EM>Alpine</EM>. A |
| 1731 |
user can always use only <EM>character</EM> keys in the startup list even |
| 1732 |
if he or she is using <EM>function</EM> keys normally, or vice versa. If |
| 1733 |
an element in this list is a string surrounded by double quotes (") |
| 1734 |
then it will be expanded into the individual characters in the string, |
| 1735 |
excluding the double quotes. <P> |
| 1736 |
|
| 1737 |
<DT> <A NAME="kblock-count"><EM>kblock-passwd-count</EM></A> |
| 1738 |
|
| 1739 |
<DD> System-wide <EM>Alpine</EM> configuration files only. Number of times a user |
| 1740 |
will have to enter a password when they run the keyboard lock command in |
| 1741 |
the main menu. <P> |
| 1742 |
|
| 1743 |
<DT> <A NAME="keyb-char-set"><EM>keyboard-character-set</EM></A> |
| 1744 |
|
| 1745 |
<DD> See the discussion in |
| 1746 |
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for |
| 1747 |
details.<P> |
| 1748 |
|
| 1749 |
<DT> <A NAME="keylabel-background-color"><EM>keylabel-background-color</EM></A> |
| 1750 |
<DT> <A NAME="keylabel-foreground-color"><EM>keylabel-foreground-color</EM></A> |
| 1751 |
|
| 1752 |
<DD> <A HREF="#keylabel-color"><EM>KeyLabel Color</EM></A>. |
| 1753 |
<P> |
| 1754 |
|
| 1755 |
<DT> <A NAME="keyname-background-color"><EM>keyname-background-color</EM></A> |
| 1756 |
<DT> <A NAME="keyname-foreground-color"><EM>keyname-foreground-color</EM></A> |
| 1757 |
|
| 1758 |
<DD> <A HREF="#keyname-color"><EM>KeyName Color</EM></A>. |
| 1759 |
<P> |
| 1760 |
|
| 1761 |
<DT> <A NAME="keywords"><EM>keywords</EM></A> |
| 1762 |
|
| 1763 |
<DD> You may define your own set of keywords and optionally set them on a |
| 1764 |
message by message basis. |
| 1765 |
These are similar to the "Important" flag which the user |
| 1766 |
may set using the Flag command. |
| 1767 |
The difference is that the Important flag is always present for each folder. |
| 1768 |
User-defined keywords are chosen by the user. |
| 1769 |
You may set up the list of possible keywords here, or you may add keywords |
| 1770 |
from the Flag Details screen that you |
| 1771 |
can get to after typing the |
| 1772 |
Flag (*) |
| 1773 |
command. |
| 1774 |
After the keywords have been defined, |
| 1775 |
then you use the Flag command |
| 1776 |
to set or clear the keywords in each message. |
| 1777 |
The behavior of the flag command may be modified by using the |
| 1778 |
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A> option or the |
| 1779 |
<A HREF="#enable-flag-screen-keyword-shortcut"><EM>Enable-Flag-Screen-Keyword-Shortcut</EM></A> option. |
| 1780 |
|
| 1781 |
<P> |
| 1782 |
Keywords may be used when Selecting messages (Select Keyword). |
| 1783 |
Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc). |
| 1784 |
Filter rules may be used to set keywords automatically. |
| 1785 |
Keywords may be displayed as part of the Subject of a message by using |
| 1786 |
the SUBJKEY or SUBJKEYINIT tokens in the |
| 1787 |
<A HREF="#index-format">Index-Format</A> option. |
| 1788 |
The <A HREF="#keyword-surrounding-chars"><EM>Keyword-Surrounding-Chars</EM></A> |
| 1789 |
option may be used to modify the display of keywords using |
| 1790 |
SUBJKEY and SUBJKEYINIT slightly. |
| 1791 |
Keywords may also be displayed in a column of their own in the MESSAGE INDEX |
| 1792 |
screen by using the KEY or KEYINIT tokens. |
| 1793 |
It is also possible to color keywords in the index using the |
| 1794 |
Setup/Kolor screen |
| 1795 |
(<A HREF="#keyword-colors">Keyword Colors</A>). |
| 1796 |
Keywords are not supported by all mail servers. |
| 1797 |
<P> |
| 1798 |
You may give keywords nicknames if you wish. |
| 1799 |
If the keyword definition you type in contains a SPACE character, then the |
| 1800 |
actual value of the keyword is everything after the last SPACE and the |
| 1801 |
nickname for that keyword is everything before the last SPACE. |
| 1802 |
For example, suppose you are trying to interoperate with another email program |
| 1803 |
which uses a particular keyword with an unpleasant name. |
| 1804 |
Maybe it uses a keyword called |
| 1805 |
<P> |
| 1806 |
<CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER> |
| 1807 |
<P> |
| 1808 |
but for you that keyword means that the message is work-related. |
| 1809 |
You could define a keyword to have the value |
| 1810 |
<P> |
| 1811 |
<CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER> |
| 1812 |
<P> |
| 1813 |
and then you would use the name "Work" when dealing with |
| 1814 |
that keyword in <EM>Alpine</EM>. |
| 1815 |
If you defined it as |
| 1816 |
<P> |
| 1817 |
<CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER> |
| 1818 |
<P> |
| 1819 |
the nickname would be everything before the last SPACE, that is the nickname |
| 1820 |
would be "My Work". |
| 1821 |
<P> |
| 1822 |
Some commonly used keywords begin with dollar signs. |
| 1823 |
This presents a slight complication, because the dollar sign is normally used |
| 1824 |
to signify |
| 1825 |
<A HREF="config-notes.html#env-variables">environment variable expansion</A> |
| 1826 |
in the <EM>Alpine</EM> configuration. |
| 1827 |
In order to specify a keyword which begins with a dollar sign you must |
| 1828 |
precede the dollar sign with a second dollar sign to escape its special |
| 1829 |
meaning. |
| 1830 |
For example, if you want to include the keyword |
| 1831 |
<P> |
| 1832 |
<CENTER><SAMP>$Label1</SAMP></CENTER> |
| 1833 |
<P> |
| 1834 |
as one of your possible keywords, you must enter the text |
| 1835 |
<P> |
| 1836 |
<CENTER><SAMP>$$Label1</SAMP></CENTER> |
| 1837 |
<P> |
| 1838 |
instead. |
| 1839 |
<P> |
| 1840 |
|
| 1841 |
<DT> <A NAME="keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A> |
| 1842 |
|
| 1843 |
<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX and MESSAGE |
| 1844 |
TEXT screens. |
| 1845 |
If you have modified the |
| 1846 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option |
| 1847 |
so that either the "SUBJKEY" or "SUBJKEYINIT" tokens |
| 1848 |
are used to display keywords or their initials along with the Subject; then |
| 1849 |
this option may be used to modify the resulting display slightly. |
| 1850 |
By default, the keywords or initials displayed for these tokens will be |
| 1851 |
surrounded with curly braces ({ and }) and a trailing space. |
| 1852 |
For example, if keywords "Work" and "Now" are set for |
| 1853 |
a message, the "SUBJKEY" token will normally look like |
| 1854 |
<P> |
| 1855 |
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER> |
| 1856 |
<P> |
| 1857 |
and the SUBJKEYINIT token would look like |
| 1858 |
<P> |
| 1859 |
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER> |
| 1860 |
<P> |
| 1861 |
The default character before the keywords is the left brace ({) and the |
| 1862 |
default after the keywords is the right brace followed by a space (} ). |
| 1863 |
<P> |
| 1864 |
This option allows you to change that. |
| 1865 |
You should set it to two values separated by a space. |
| 1866 |
The values may be quoted if they include space characters. |
| 1867 |
So, for example, the default value could be specified explicitly by setting this |
| 1868 |
option to |
| 1869 |
<P> |
| 1870 |
<CENTER><SAMP>Keyword-Surrounding-Chars="{" "} "</SAMP></CENTER> |
| 1871 |
<P> |
| 1872 |
The first part wouldn't need to be quoted (but it doesn't hurt). |
| 1873 |
The second part does need the quotes because it includes a space character. |
| 1874 |
If you wanted to change the braces to brackets you could use |
| 1875 |
<P> |
| 1876 |
<CENTER><SAMP>Keyword-Surrounding-Chars="[" "] "</SAMP></CENTER> |
| 1877 |
<P> |
| 1878 |
Inside the quotes you can use backslash quote to mean quote, so |
| 1879 |
<P> |
| 1880 |
<CENTER><SAMP>Keyword-Surrounding-Chars="\"" "\" "</SAMP></CENTER> |
| 1881 |
<P> |
| 1882 |
would produce |
| 1883 |
<P> |
| 1884 |
<CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER> |
| 1885 |
<P> |
| 1886 |
It is also possible to color keywords in the index using the |
| 1887 |
Setup/Kolor screen |
| 1888 |
(<A HREF="#keyword-colors">Keyword Colors</A>). |
| 1889 |
<P> |
| 1890 |
It is not possible to change the fact that a space character is used to |
| 1891 |
separate the keywords if more than one keyword is set for a message. |
| 1892 |
It is also not possible to change the fact that there are no separators |
| 1893 |
between the keyword initials if more than one keyword is set. |
| 1894 |
<P> |
| 1895 |
This option is displayed as "Keyword Surrounding Characters". |
| 1896 |
<P> |
| 1897 |
|
| 1898 |
<DT> <A NAME="last-time"><EM>last-time-prune-questioned</EM></A> |
| 1899 |
|
| 1900 |
<DD> Personal configuration file only. This variable records the month |
| 1901 |
the user was last asked if his or her <EM>sent-mail</EM> folders should |
| 1902 |
be pruned. |
| 1903 |
The format is <EM>yy.mm</EM>. |
| 1904 |
This is automatically updated by <EM>Alpine</EM> when |
| 1905 |
the the pruning is done or declined. |
| 1906 |
If a user wanted to make <EM>Alpine</EM> stop |
| 1907 |
asking this question he or she could set this time to something |
| 1908 |
far in the future. |
| 1909 |
This may not be set in the system-wide configuration files. |
| 1910 |
Note: The <EM>yy</EM> year is actually the number of years since 1900, so it |
| 1911 |
will be equal to 101 in the year 2001. |
| 1912 |
<P> |
| 1913 |
|
| 1914 |
<DT> <A NAME="last-version-used"><EM>last-version-used</EM></A> |
| 1915 |
|
| 1916 |
<DD> Personal configuration file only. |
| 1917 |
This is set automatically by <EM>Alpine</EM>. |
| 1918 |
It is used to keep track of the last version of <EM>Alpine</EM> that |
| 1919 |
was run by the user. |
| 1920 |
Whenever the version number increases, a new version message is printed out. |
| 1921 |
This may not be set in the system-wide configuration files. |
| 1922 |
<P> |
| 1923 |
|
| 1924 |
<DT> <A NAME="ldap-servers"><EM>ldap-servers</EM></A> |
| 1925 |
|
| 1926 |
<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library |
| 1927 |
when it was compiled. This variable is normally managed by <EM>Alpine</EM> though |
| 1928 |
it can be set in the system-wide configuration files as well as the personal |
| 1929 |
configuration. It is a list variable. Each item in the |
| 1930 |
list contains quite a bit of extra information besides just the server name. |
| 1931 |
To put this into a system-wide config file the easiest thing to do is to |
| 1932 |
configure a personal <EM>Alpine</EM> for the LDAP server then copy the |
| 1933 |
configuration line |
| 1934 |
into the system-wide config file. Each item in the list looks like: |
| 1935 |
|
| 1936 |
<BLOCKQUOTE> |
| 1937 |
<CODE> |
| 1938 |
server_name[:port] <SPACE> "quoted stuff" </CODE><BR> |
| 1939 |
</BLOCKQUOTE> |
| 1940 |
|
| 1941 |
The <CODE>server_name</CODE> is just a hostname and it is followed by |
| 1942 |
an optional colon and port number. The default <CODE>port</CODE> is 389. |
| 1943 |
Following the server name is a single SPACE character followed by |
| 1944 |
a bunch of characters inside double quotes. The part inside the quotes is |
| 1945 |
a set of <EM>tag</EM> = <EM>value</EM> pairs. |
| 1946 |
Each tag is preceded by a slash (/) and followed |
| 1947 |
by an equal sign. The value for that tag is the text up to the next slash. |
| 1948 |
An example of some <CODE>quoted stuff</CODE> is: |
| 1949 |
|
| 1950 |
<BLOCKQUOTE> |
| 1951 |
<CODE> |
| 1952 |
"/base=o=University of Washington, c=US/impl=0/.../nick=My Server" |
| 1953 |
</CODE><BR> |
| 1954 |
</BLOCKQUOTE> |
| 1955 |
|
| 1956 |
This would set the search base for this server to |
| 1957 |
<CODE>o=University of Washington, c=US</CODE>, set the implicit bit to zero, |
| 1958 |
and set the nickname for the server to <CODE>My Server</CODE>. |
| 1959 |
All of the tags correspond directly to items in the Setup/Directory screen |
| 1960 |
so experiment with that if you want to see what the possible tags and values |
| 1961 |
are. |
| 1962 |
<P> |
| 1963 |
|
| 1964 |
<DT> <A NAME="literal-signature"><EM>literal-signature</EM></A> |
| 1965 |
|
| 1966 |
<DD> With this option your actual signature, as opposed to |
| 1967 |
the name of a file containing your signature, |
| 1968 |
is stored in the <EM>Alpine</EM> configuration file. |
| 1969 |
If this is defined it takes precedence over the <EM>signature-file</EM> option. |
| 1970 |
<P> |
| 1971 |
|
| 1972 |
This is simply a different way to store the signature data. |
| 1973 |
The signature is stored inside your <EM>Alpine</EM> configuration file |
| 1974 |
instead of in a separate signature file. |
| 1975 |
Tokens contained in the signature work the same way they do with the regular |
| 1976 |
<A HREF="#sig-file">signature-file</A>. |
| 1977 |
<P> |
| 1978 |
|
| 1979 |
The Setup/Signature command in <EM>Alpine</EM>'s Main Menu will edit |
| 1980 |
the <EM>literal-signature</EM> by default. However, if no |
| 1981 |
<EM>literal-signature</EM> is defined and the file named in the |
| 1982 |
<EM>signature-file</EM> option exists, then the latter will be used |
| 1983 |
instead. Compose (Reply, Forward, ...) will default to using the |
| 1984 |
<EM>literal-signature</EM> if defined, otherwise it will use the contents |
| 1985 |
of the file named in <EM>signature-file</EM>. |
| 1986 |
<P> |
| 1987 |
|
| 1988 |
The <EM>Alpine</EM> composer is used to edit the literal-signature. |
| 1989 |
The result of that edit is first converted to a C-style string before it |
| 1990 |
is stored in the configuration file. |
| 1991 |
In particular, the two character sequence \n (backslash followed by |
| 1992 |
the character "n") will be used to signify a |
| 1993 |
line-break in the signature. |
| 1994 |
You don't have to enter the \n, but it will be visible in the |
| 1995 |
SETUP CONFIGURATION window after you are done editing the signature. |
| 1996 |
<P> |
| 1997 |
|
| 1998 |
<DT> <A NAME="mail-check"><EM>mail-check-interval</EM></A> |
| 1999 |
|
| 2000 |
<DD> This option specifies, in seconds, |
| 2001 |
how often <EM>Alpine</EM> will check for new mail. |
| 2002 |
If set to zero, new-mail checking is disabled. |
| 2003 |
(You can always manually force a new-mail check by typing ^L (Ctrl-L), which is also |
| 2004 |
the command to refresh the screen, or by typing the Next command when the |
| 2005 |
current message is the last message of the folder.) |
| 2006 |
There is a minimum value for this option, normally 15 seconds. |
| 2007 |
The default value is normally 150 seconds. |
| 2008 |
The higher you set this option, the easier it is on the server. |
| 2009 |
<P> |
| 2010 |
There are some situations where automatic new-mail checking does not work. |
| 2011 |
See the discussion about new-mail checking in <A HREF="#reopen-rule"><EM>folder-reopen-rule</EM></A>. |
| 2012 |
<P> |
| 2013 |
The new-mail checking will not happen exactly at the frequency that you specify. |
| 2014 |
For example, <EM>Alpine</EM> may elect to defer a non-INBOX mail check if you |
| 2015 |
are busy typing. |
| 2016 |
Or, it may check more frequently than you have specified if that is |
| 2017 |
thought to be necessary to keep the server from closing the connection |
| 2018 |
to the folder due to inactivity. |
| 2019 |
If <EM>Alpine</EM> checks for new mail as a side effect of another command, it will reset |
| 2020 |
the timer, so that new-mail checking may seem to happen irregularly instead of |
| 2021 |
every X seconds like clockwork. |
| 2022 |
<P> |
| 2023 |
If you are anxious to know about new mail as soon as possible, set the check |
| 2024 |
interval low, and you'll know about the new mail by approximately |
| 2025 |
that amount of time after it arrives. |
| 2026 |
If you aren't so worried about knowing right away, set this option to a |
| 2027 |
higher value. |
| 2028 |
That will save the server some processing time and may save you some of |
| 2029 |
the time you spend waiting for new-mail checks to happen if you are |
| 2030 |
dealing with a slow server or slow network connection. |
| 2031 |
<P> |
| 2032 |
If you suspect that new-mail checking is causing slow downs for you, |
| 2033 |
you may want to look into the options |
| 2034 |
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>, |
| 2035 |
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> and |
| 2036 |
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A>, |
| 2037 |
which refine when mail checking is done. |
| 2038 |
<P> |
| 2039 |
If the mailbox being check uses a <A HREF="config-notes.html#maildrop">Mail Drop</A> then |
| 2040 |
there is a minimum time |
| 2041 |
(<A HREF="#maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A>) |
| 2042 |
between new-mail checks. |
| 2043 |
Because of this minimum you may notice that new mail does not |
| 2044 |
appear promptly when you expect it. |
| 2045 |
The reason for this is to protect the server from over-zealous opening and |
| 2046 |
closing of the Mail Drop folder, since that is a costly operation. |
| 2047 |
<P> |
| 2048 |
A side effect of disabling mail checking is that there will be situations |
| 2049 |
in which the user's IMAP connection will be broken due to inactivity timers |
| 2050 |
on the server. Another side effect is that the |
| 2051 |
<A HREF="#user-input"><EM>user-input-timeout</EM></A> |
| 2052 |
option won't work. |
| 2053 |
<P> |
| 2054 |
|
| 2055 |
<DT> <A NAME="mail-check-noncurr"><EM>mail-check-interval-noncurrent</EM></A> |
| 2056 |
|
| 2057 |
<DD> This option is closely related to the |
| 2058 |
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> |
| 2059 |
option, as well as the |
| 2060 |
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A> and |
| 2061 |
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> options. |
| 2062 |
If the "Mail-Check-Interval" option is set to zero, then automatic |
| 2063 |
new-mail checking is disabled and this option will have no effect. |
| 2064 |
<P> |
| 2065 |
Normally this option is set to zero, which means that the value used will be |
| 2066 |
the same as the value for the "Mail-Check-Interval". |
| 2067 |
If you set this option to a value different from zero |
| 2068 |
(usually larger than the value for "Mail-Check-Interval") |
| 2069 |
then that is the check interval that will be used |
| 2070 |
for folders which are not the currently open folder or the INBOX. |
| 2071 |
You may not even have any folders that are noncurrent and not the INBOX. |
| 2072 |
If you do, it is likely that they are due to |
| 2073 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A> |
| 2074 |
you have configured. |
| 2075 |
This option also affects the rate of mail checking done on cached |
| 2076 |
connections to folders you previously had open but are no longer actively |
| 2077 |
using. |
| 2078 |
You aren't expected to understand that last sentence, but if you are interested |
| 2079 |
take a look at |
| 2080 |
<A HREF="#max-remote-connections">Max-Remote-Connections</A>, |
| 2081 |
and the related options. |
| 2082 |
<P> |
| 2083 |
|
| 2084 |
<DT> <A NAME="mail-directory"><EM>mail-directory</EM></A> |
| 2085 |
|
| 2086 |
<DD> This variable was more important in previous versions of <EM>Alpine</EM>. Now |
| 2087 |
it is used only as the default for storing personal folders (and only if |
| 2088 |
there are no <A HREF="#fold-coll"><EM>folder-collections</EM></A> defined). |
| 2089 |
The default value is |
| 2090 |
<EM>~/mail</EM> on UNIX and <EM>${HOME}\MAIL</EM> on a PC. <P> |
| 2091 |
|
| 2092 |
<DT> <A NAME="mailcap-search-path"><EM>mailcap-search-path</EM></A> |
| 2093 |
|
| 2094 |
<DD> This variable is used to replace <EM>Alpine</EM>'s default |
| 2095 |
mailcap file search path. |
| 2096 |
It takes one or more file names (full paths must be specified) in |
| 2097 |
which to look for mail capability data. <P> |
| 2098 |
|
| 2099 |
<DT> <A NAME="maildrop-check-minimum"><EM>maildrop-check-minimum</EM></A> |
| 2100 |
|
| 2101 |
<DD> New-mail checking for a |
| 2102 |
<A HREF="config-notes.html#maildrop">Mail Drop</A> |
| 2103 |
is a little different from new |
| 2104 |
mail checking for a regular folder. |
| 2105 |
One of the differences is that the connection to the Mail Drop is not |
| 2106 |
kept open and so the cost of checking |
| 2107 |
(delay for you and additional load for the server) may be significant. |
| 2108 |
Because of this additional cost we set a minimum time that |
| 2109 |
must pass between checks. |
| 2110 |
This minimum only applies to the automatic checking done by <EM>Alpine</EM>. |
| 2111 |
If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are |
| 2112 |
at the end of a folder index, then the check is done right away. |
| 2113 |
<P> |
| 2114 |
This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop |
| 2115 |
new-mail checks. |
| 2116 |
You may want to set this minimum high in order to avoid experiencing some |
| 2117 |
of the delays associated with the checks. |
| 2118 |
Note that the time between checks is still controlled by the regular |
| 2119 |
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> option. |
| 2120 |
When <EM>Alpine</EM> is about to do an automatic check for new mail (because |
| 2121 |
the Mail-Check-Interval has expired) then if the time since the last |
| 2122 |
new-mail check |
| 2123 |
of any open Mail Drops has been greater than the MailDrop-Check-Minimum, |
| 2124 |
the Mail Drop is checked for new mail as well. |
| 2125 |
Therefore, it is only useful to set this option to a value that is higher |
| 2126 |
than the Mail-Check-Interval. |
| 2127 |
<P> |
| 2128 |
If this option is set to zero, automatic Mail Drop new-mail |
| 2129 |
checking is disabled. |
| 2130 |
There is a minimum value, normally 60 seconds. |
| 2131 |
The default value is normally 60 seconds as well. |
| 2132 |
This applies to the INBOX and to the currently open folder if that is |
| 2133 |
different from the INBOX. |
| 2134 |
<P> |
| 2135 |
|
| 2136 |
<DT> <A NAME="max-remote-connections"><EM>max-remote-connections</EM></A> |
| 2137 |
|
| 2138 |
<DD> This option affects low-level behavior of <EM>Alpine</EM>. |
| 2139 |
The default value for this option is <EM>2</EM>. |
| 2140 |
If your INBOX is accessed using the IMAP protocol |
| 2141 |
from an IMAP server, that connection is kept open throughout the |
| 2142 |
duration of your <EM>Alpine</EM> session, independent of the value of this option. |
| 2143 |
The same is true of any |
| 2144 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A> |
| 2145 |
you have defined. |
| 2146 |
This option controls <EM>Alpine</EM>'s behavior when connecting to remote IMAP folders |
| 2147 |
other than your INBOX or your Stay-Open-Folders. |
| 2148 |
It specifies the maximum number of remote IMAP connections (other than |
| 2149 |
those mentioned above) that <EM>Alpine</EM> will use for accessing the rest of your |
| 2150 |
folders. |
| 2151 |
If you set this option to zero, you will turn off most remote connection |
| 2152 |
re-use. |
| 2153 |
It's difficult to understand exactly what this option does, and it is usually |
| 2154 |
fine to leave it set to its default value. |
| 2155 |
It is probably more likely that you will be interested in setting the |
| 2156 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A> option |
| 2157 |
instead of changing the value of this option. |
| 2158 |
A slightly longer explanation of what is going on with this option |
| 2159 |
is given in the next paragraphs. |
| 2160 |
|
| 2161 |
<P> |
| 2162 |
There are some time costs involved in opening and closing remote IMAP |
| 2163 |
folders, the main costs being the time you have to wait for the connection |
| 2164 |
to the server and the time for the folder to open. |
| 2165 |
Opening a folder may involve not only the time the server takes to do its |
| 2166 |
processing but time that <EM>Alpine</EM> uses to do filtering. |
| 2167 |
These times can vary widely. |
| 2168 |
They depend on how loaded the server is, how large |
| 2169 |
the folder being opened is, and how you set up filtering, among other things. |
| 2170 |
Once <EM>Alpine</EM> has opened a connection to a particular folder, it will attempt |
| 2171 |
to keep that connection open in case you use it again. |
| 2172 |
In order to do this, |
| 2173 |
<EM>Alpine</EM> will attempt to use the Max-Remote-Connections (the value of |
| 2174 |
this option) IMAP connections you have allotted for this purpose. |
| 2175 |
<P> |
| 2176 |
For example, suppose the value of this option is set to "2". |
| 2177 |
If your INBOX is accessed on a remote server using the IMAP protocol, that |
| 2178 |
doesn't count as one of the remote connections but it is always kept open. |
| 2179 |
If you then open another IMAP folder, that would be your first |
| 2180 |
remote connection counted as one of the Max-Remote-Connections connections. |
| 2181 |
If you open a third folder the second will be left open, in case you |
| 2182 |
return to it. |
| 2183 |
You won't be able to tell it has been left open. |
| 2184 |
It will appear to be closed when you leave the folder but the connection |
| 2185 |
will remain in the background. |
| 2186 |
Now suppose you go back to the second folder (the first folder after the |
| 2187 |
INBOX). |
| 2188 |
A connection to that folder is still open so you won't have to wait |
| 2189 |
for the startup time to open it. |
| 2190 |
Meanwhile, the connection to the third folder will be left behind. |
| 2191 |
Now, if you open a fourth folder, you will bump into the |
| 2192 |
Max-Remote-Connections limit, because this will be the third folder other |
| 2193 |
than INBOX and you have the option set to "2". |
| 2194 |
The connection that is being used for |
| 2195 |
the third folder will be re-used for this new fourth folder. |
| 2196 |
If you go back to the third folder after this, it is no longer already |
| 2197 |
connected when you get there. |
| 2198 |
You'll still save some time since <EM>Alpine</EM> will re-use the connection to the |
| 2199 |
fourth folder and you have already logged in on that connection, |
| 2200 |
but the folder will have to be re-opened from scratch. |
| 2201 |
<P> |
| 2202 |
If a folder is large and the startup cost is dominated by the time it takes |
| 2203 |
to open that folder or to run filters on it, then it will pay to make the |
| 2204 |
value of this option large enough to keep it open. |
| 2205 |
On the other hand, if you only revisit a handful of folders or if |
| 2206 |
the folders are small, then it might |
| 2207 |
make more sense to keep this number small so that the reconnect |
| 2208 |
time (the time to start up a new connection and authenticate) |
| 2209 |
is eliminated instead. |
| 2210 |
<P> |
| 2211 |
You may also need to consider the impact on the server. |
| 2212 |
On the surface, a larger number here may cause a larger impact on the |
| 2213 |
server, since you will have more connections open to the server. |
| 2214 |
On the other hand, not only will <EM>you</EM> be avoiding the startup costs |
| 2215 |
associated with reopening a folder, but the <EM>server</EM> will be |
| 2216 |
avoiding those costs as well. |
| 2217 |
<P> |
| 2218 |
When twenty five minutes pass without any active use of an IMAP connection |
| 2219 |
being saved for possible re-use, that connection will be shut down, |
| 2220 |
<P> |
| 2221 |
This option is displayed as "Maximum Remote Connections". |
| 2222 |
<P> |
| 2223 |
|
| 2224 |
<DT> <A NAME="meta-message-background-color"><EM>meta-message-background-color</EM></A> |
| 2225 |
<DT> <A NAME="meta-message-foreground-color"><EM>meta-message-foreground-color</EM></A> |
| 2226 |
|
| 2227 |
<DD> <A HREF="#meta-message-color"><EM>Meta-message Color</EM></A>. |
| 2228 |
<P> |
| 2229 |
|
| 2230 |
<DT> <A NAME="mimetype-search-path"><EM>mimetype-search-path</EM></A> |
| 2231 |
|
| 2232 |
<DD> This variable is used to replace <EM>Alpine</EM>'s default mime.types file |
| 2233 |
search path. It takes one or more file names (full paths must be |
| 2234 |
specified) in which to look for file-name-extension to MIME type mapping |
| 2235 |
data. See the Config Notes for details on <EM>Alpine</EM>'s usage of the <A |
| 2236 |
HREF="config-notes.html#mime.types">MIME.Types File</A>. <P> |
| 2237 |
|
| 2238 |
<DT> <A NAME="new-version-threshold"><EM>new-version-threshold</EM></A> |
| 2239 |
|
| 2240 |
<DD> When a new version of <EM>Alpine</EM> is run for the first time it offers a |
| 2241 |
special explanatory screen to the user upon startup. This option |
| 2242 |
helps control when and if that special screen appears for users that |
| 2243 |
have previously run <EM>Alpine</EM>. It takes as its value a <EM>Alpine</EM> version |
| 2244 |
number. <EM>Alpine</EM> versions less than the specified value will suppress this |
| 2245 |
special screen while versions equal to or greater than that specified |
| 2246 |
will behave normally. <P> |
| 2247 |
|
| 2248 |
<DT> <A NAME="newmail-fifo-path"><EM>newmail-fifo-path</EM></A> |
| 2249 |
|
| 2250 |
<DD> This option is only available in UNIX <EM>Alpine</EM>. |
| 2251 |
However, there is a very similar feature built in to <EM>PC-Alpine</EM>. |
| 2252 |
In <EM>PC-Alpine</EM>'s Config menu at the top of the screen |
| 2253 |
is an option called "New Mail Window". |
| 2254 |
<P> |
| 2255 |
You may have <EM>Alpine</EM> create a FIFO special file (also called a named pipe, see mkfifo(3) and fifo(4)) where |
| 2256 |
it will send a one-line message each time a new message is received in |
| 2257 |
the current folder, the INBOX, or any open |
| 2258 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A>. |
| 2259 |
To protect against two different <EM>Alpine</EM>s both writing to the same FIFO, <EM>Alpine</EM> |
| 2260 |
will only create the FIFO and write to it if it doesn't already exist. |
| 2261 |
<P> |
| 2262 |
A possible way to use this option would be to have a separate window |
| 2263 |
on your screen running the command |
| 2264 |
<P> |
| 2265 |
<CENTER><SAMP>cat filename</SAMP></CENTER> |
| 2266 |
<P> |
| 2267 |
where "filename" is the name of the file given for this option. |
| 2268 |
Because the file won't exist until after you start <EM>Alpine</EM>, you must <EM>first</EM> |
| 2269 |
start <EM>Alpine</EM> and <EM>then</EM> run the "cat" command. |
| 2270 |
You may be tempted to use "tail -f filename" to view the new |
| 2271 |
mail log. |
| 2272 |
However, the common implementations of the tail command will not do what you |
| 2273 |
are hoping. |
| 2274 |
<P> |
| 2275 |
The width of the messages produced for the FIFO may be altered with the |
| 2276 |
<A HREF="#newmail-window-width">NewMail-Window-Width</A> option. |
| 2277 |
<P> |
| 2278 |
On some systems, fifos may only be created in a local filesystem. |
| 2279 |
In other words, they may not be in NFS filesystems. |
| 2280 |
This requirement is not universal. |
| 2281 |
If the system you are using supports it, it should work. |
| 2282 |
(It is often the case that your home directory is in an NFS filesystem. |
| 2283 |
If that is the case, you might try using a file in the "/tmp" |
| 2284 |
filesystem, which is usually a local filesystem.) |
| 2285 |
Even when it is possible to use an NFS-mounted filesystem as a place to name |
| 2286 |
the fifo (for example, your home directory), it will still be the case that |
| 2287 |
the reader (probably the "cat" command) and the |
| 2288 |
writer (<EM>Alpine</EM>) of the fifo must be running on the same system. <P> |
| 2289 |
|
| 2290 |
<DT> <A NAME="newmail-window-width"><EM>newmail-window-width</EM></A> |
| 2291 |
|
| 2292 |
<DD> UNIX <EM>Alpine</EM> only. |
| 2293 |
<P> |
| 2294 |
This option is only useful if you have turned on the |
| 2295 |
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option. |
| 2296 |
That option causes new mail messages to be sent to a fifo file. |
| 2297 |
Those messages will be 80 characters wide by default. |
| 2298 |
You can change the width of the messages by changing this option. |
| 2299 |
For example, if you are reading those messages in another window you might |
| 2300 |
want to set this width to the width of that other window. <P> |
| 2301 |
For UNIX <EM>Alpine</EM>, this option is only useful if you have turned on the |
| 2302 |
<A HREF="#newmail-fifo-path">NewMail-FIFO-Path</A> option. |
| 2303 |
That option causes new mail messages to be sent to a fifo file. |
| 2304 |
Those messages will be 80 characters wide by default. |
| 2305 |
You can change the width of those messages by changing this option. |
| 2306 |
For example, if you are reading those messages in another window you might |
| 2307 |
want to set this width to the width of that other window. |
| 2308 |
<P> |
| 2309 |
If you are using <EM>PC-Alpine</EM>, it has an option in the Config menu to turn |
| 2310 |
on the "New Mail Window". |
| 2311 |
The present option also controls the width of that window. |
| 2312 |
|
| 2313 |
<DT> <A NAME="news-active"><EM>news-active-file-path</EM></A> |
| 2314 |
|
| 2315 |
<DD> This option tells <EM>Alpine</EM> where to look for the "active file" for |
| 2316 |
newsgroups when accessing news locally, rather than via NNTP. The default |
| 2317 |
path is usually <CODE>/usr/lib/news/active</CODE>. <P> |
| 2318 |
|
| 2319 |
<DT> <A NAME="news-coll"><EM>news-collections</EM></A> |
| 2320 |
|
| 2321 |
<DD> This is a list of collections where news folders are located. See |
| 2322 |
the section describing <A HREF="config-notes.html#collections">collections</A> |
| 2323 |
for more information. <P> |
| 2324 |
|
| 2325 |
<DT> <A NAME="news-spool"><EM>news-spool-directory</EM></A> |
| 2326 |
|
| 2327 |
<DD> This option tells <EM>Alpine</EM> where to look for the "news spool" for |
| 2328 |
newsgroups when accessing news locally, rather than via NNTP. The default |
| 2329 |
path is usually <CODE>/usr/spool/news</CODE>. <P> |
| 2330 |
|
| 2331 |
<DT> <A NAME="newsrc-path"><EM>newsrc-path</EM></A> |
| 2332 |
|
| 2333 |
<DD> This option overrides the default name <EM>Alpine</EM> uses for your "newsrc" |
| 2334 |
news status and subscription file. If set, <EM>Alpine</EM> will take this value as |
| 2335 |
the full pathname for the desired newsrc file. <P> |
| 2336 |
|
| 2337 |
<DT> <A NAME="nntp-range"><EM>nntp-range</EM></A> |
| 2338 |
|
| 2339 |
<DD> This option applies only to newsgroups accessed using the NNTP protocol. |
| 2340 |
It does not, for example, |
| 2341 |
apply to newsgroups accessed using an IMAP-to-NNTP proxy. |
| 2342 |
<P> |
| 2343 |
When you open a connection to a News server using the NNTP protocol, you |
| 2344 |
normally have access to all of the articles in each newsgroup. |
| 2345 |
If a server keeps a large backlog of messages it may speed performance |
| 2346 |
some to restrict attention to only the newer messages in a group. |
| 2347 |
This option allows you to set how many article numbers should be checked |
| 2348 |
when opening a newsgroup. |
| 2349 |
You can think of "nntp-range" as specifying the maximum number |
| 2350 |
of messages you ever want to see. |
| 2351 |
For example, if you only ever wanted to look at the last 500 messages in each |
| 2352 |
newsgroup you could set this option to 500. |
| 2353 |
In actuality, it isn't quite that. |
| 2354 |
Instead, for performance reasons, it specifies the range of article |
| 2355 |
numbers to be checked, beginning |
| 2356 |
with the highest numbered article and going backwards from there. |
| 2357 |
If there are messages that have been canceled or deleted |
| 2358 |
their article numbers are still counted as part of the range. |
| 2359 |
<P> |
| 2360 |
So, more precisely, setting the "nntp-range" will cause article |
| 2361 |
numbers |
| 2362 |
<P><CENTER>last_article_number - nntp-range + 1 through last_article_number</CENTER> |
| 2363 |
<P> |
| 2364 |
to be considered when reading a newsgroup. |
| 2365 |
The number of messages that show up in your index will be less than or equal |
| 2366 |
to the value of "nntp-range". |
| 2367 |
<P> |
| 2368 |
The purpose of this option is simply to speed up access when reading news. |
| 2369 |
The speedup comes because <EM>Alpine</EM> can ignore all but the last nntp-range article |
| 2370 |
numbers, and can avoid downloading any information about the ignored articles. |
| 2371 |
There is a cost you pay for this speedup. |
| 2372 |
That cost is that there is no way for you to see those ignored articles. |
| 2373 |
The articles that come before the range you specify are invisible to you and |
| 2374 |
to <EM>Alpine</EM>, as if they did not exist at all. |
| 2375 |
There is no way to see those messages using, for example, an unexclude command |
| 2376 |
or something similar. |
| 2377 |
The only way to see those articles is to set this option high enough (or |
| 2378 |
set it to zero) and then to reopen the newsgroup. |
| 2379 |
|
| 2380 |
<P> |
| 2381 |
If this option is set to 0 (which is also the default), |
| 2382 |
then the range is unlimited. |
| 2383 |
This option applies globally to all NNTP servers and to all newsgroups |
| 2384 |
on those servers. |
| 2385 |
There is no way to set different values for different newsgroups or servers. |
| 2386 |
<P> |
| 2387 |
|
| 2388 |
<DT> <A NAME="nntp-server"><EM>nntp-server</EM></A> |
| 2389 |
|
| 2390 |
<DD> One or more NNTP servers (host name or IP address) which <EM>Alpine</EM> will |
| 2391 |
use for reading and posting news. |
| 2392 |
If you read and post news to and from a single |
| 2393 |
NNTP server, you can get away with only setting the <EM>nntp-server</EM> |
| 2394 |
variable and leaving the <EM>news-collections</EM> variable unset. |
| 2395 |
<P> |
| 2396 |
When you define an NNTP server, <EM>Alpine</EM> implicitly defines a |
| 2397 |
news collection for you, assuming that server as the news server |
| 2398 |
and assuming that you will use the NNTP protocol and a local newsrc |
| 2399 |
configuration file for reading news. |
| 2400 |
See also <A HREF="#configuring-news">Configuring News</A>. |
| 2401 |
<P> |
| 2402 |
Your NNTP server may offer NNTP "AUTHINFO SASL" |
| 2403 |
or "AUTHINFO USER" authentication. |
| 2404 |
It may even require it. |
| 2405 |
If your NNTP server does offer such authentication you may specify a user name |
| 2406 |
parameter to cause <EM>Alpine</EM> to attempt to authenticate. |
| 2407 |
The same is true for the server name in a folder collection which uses NNTP. |
| 2408 |
This parameter requires an associated value, |
| 2409 |
the username identifier with which to establish the server connection. |
| 2410 |
An example might be: |
| 2411 |
|
| 2412 |
<P> |
| 2413 |
<CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER> |
| 2414 |
<P> |
| 2415 |
|
| 2416 |
If authentication is offered by the server, this will cause <EM>Alpine</EM> to |
| 2417 |
attempt to use it. |
| 2418 |
If authentication is not offered by the server, this will cause <EM>Alpine</EM> |
| 2419 |
to fail with an error similar to: |
| 2420 |
|
| 2421 |
<P> |
| 2422 |
<CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER> |
| 2423 |
<P> |
| 2424 |
For more details about the server name possibilities see |
| 2425 |
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A>. |
| 2426 |
<P> |
| 2427 |
|
| 2428 |
<DT> <A NAME="norm-back"><EM>normal-background-color</EM></A> |
| 2429 |
<DT> <A NAME="normal-foreground-color"><EM>normal-foreground-color</EM></A> |
| 2430 |
|
| 2431 |
<DD> <A HREF="#normal-color"><EM>Normal Color</EM></A>. |
| 2432 |
<P> |
| 2433 |
|
| 2434 |
<DT> <A NAME="opening-text-separator-chars"><EM>opening-text-separator-chars</EM></A> |
| 2435 |
<DD> This option controls a minor aspect of <EM>Alpine</EM>'s MESSAGE INDEX screen. |
| 2436 |
With some setups the text of the subject is followed |
| 2437 |
by the opening text of the message if there is any room available in the index line. |
| 2438 |
If you have configured your |
| 2439 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option |
| 2440 |
to include one of the Subject tokens which causes this behavior |
| 2441 |
(SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used |
| 2442 |
to modify what is displayed slightly. |
| 2443 |
By default, the Subject is separated from the opening text of the message by |
| 2444 |
the three characters space dash space; |
| 2445 |
<P> |
| 2446 |
<CENTER><SAMP>" - "</SAMP></CENTER> |
| 2447 |
<P> |
| 2448 |
Use this option to set it to something different. |
| 2449 |
The value must be quoted if it includes any space characters. |
| 2450 |
For example, the default value could be specified explicitly by setting this |
| 2451 |
option to |
| 2452 |
<P> |
| 2453 |
<CENTER><SAMP>Opening-Text-Separator-Chars=" - "</SAMP></CENTER> |
| 2454 |
<P> |
| 2455 |
This option is displayed as "Opening Text Separator Characters". |
| 2456 |
<P> |
| 2457 |
|
| 2458 |
<DT> <A NAME="operating-dir"><EM>operating-dir</EM></A> |
| 2459 |
|
| 2460 |
<DD> System-wide <EM>Alpine</EM> configuration files only. |
| 2461 |
This names the root of the |
| 2462 |
tree to which the user is restricted when reading and writing folders and |
| 2463 |
files. It is usually used in the <EM>fixed</EM> configuration file. <P> |
| 2464 |
|
| 2465 |
<DT> <A NAME="patterns-filters2"><EM>patterns-filters2</EM></A> |
| 2466 |
|
| 2467 |
<DD> Matching patterns and their corresponding actions are stored in |
| 2468 |
this variable. |
| 2469 |
These patterns are used with |
| 2470 |
<A HREF="#filter-config"><EM>Filtering</EM></A>. |
| 2471 |
This variable is normally maintained through the Setup/Rules/Filters |
| 2472 |
configuration screen. |
| 2473 |
It is a list variable. |
| 2474 |
Each member of the list is a single pattern/action pair, or it can be |
| 2475 |
a file which contains zero or more lines of pattern/action pairs. |
| 2476 |
The only way to create a filters file is to use the InsertFile command in |
| 2477 |
the Setup/Rules/Filters screen with a filename which doesn't yet exist. |
| 2478 |
Then use the Shuffle command to move existing filter patterns into the file. |
| 2479 |
This isn't very convenient but it isn't thought that many users will |
| 2480 |
need this functionality. |
| 2481 |
The purpose of filter files is for sharing filters. |
| 2482 |
<P> |
| 2483 |
This option is displayed as "Patterns Filters". |
| 2484 |
<P> |
| 2485 |
|
| 2486 |
<DT> <A NAME="patterns-indexcolors"><EM>patterns-indexcolors</EM></A> |
| 2487 |
|
| 2488 |
<DD> Matching patterns and their corresponding actions are stored in |
| 2489 |
this variable. |
| 2490 |
These patterns are used for |
| 2491 |
<A HREF="#index-color-config"><EM>Index Line Colors</EM></A>. |
| 2492 |
This variable is normally maintained through the Setup/Rules/Indexcolor |
| 2493 |
configuration screen. |
| 2494 |
It is a list variable. |
| 2495 |
Each member of the list is a single pattern/action pair, or it can be |
| 2496 |
a file which contains zero or more lines of pattern/action pairs. |
| 2497 |
The only way to create a indexcolor file is to use the InsertFile command in |
| 2498 |
the Setup/Rules/Indexcolor screen with a filename which doesn't yet exist. |
| 2499 |
Then use the Shuffle command to move existing patterns into the file. |
| 2500 |
This isn't very convenient but it isn't thought that many users will |
| 2501 |
need this functionality. |
| 2502 |
The purpose of indexcolor files is for sharing indexcolors. |
| 2503 |
<P> |
| 2504 |
|
| 2505 |
<DT> <A NAME="patterns-other"><EM>patterns-other</EM></A> |
| 2506 |
|
| 2507 |
<DD> Matching patterns and their corresponding actions are stored in |
| 2508 |
this variable. |
| 2509 |
These patterns are used with |
| 2510 |
<A HREF="#other-config"><EM>Miscellaneous Rules</EM></A> configuration. |
| 2511 |
This variable is normally maintained through the Setup/Rules/Other |
| 2512 |
configuration screen. |
| 2513 |
It is a list variable. |
| 2514 |
Each member of the list is a single pattern/action pair, or it can be |
| 2515 |
a file which contains zero or more lines of pattern/action pairs. |
| 2516 |
The only way to create a rules file is to use the InsertFile command in |
| 2517 |
the Setup/Rules/Other screen with a filename which doesn't yet exist. Then use |
| 2518 |
the Shuffle command to move existing rules into the file. |
| 2519 |
This isn't very convenient but it isn't thought that many users will |
| 2520 |
need this functionality. |
| 2521 |
<P> |
| 2522 |
|
| 2523 |
<DT> <A NAME="patterns-roles"><EM>patterns-roles</EM></A> |
| 2524 |
|
| 2525 |
<DD> Matching patterns and their corresponding actions are stored in |
| 2526 |
this variable. |
| 2527 |
These patterns are used with |
| 2528 |
<A HREF="#role-config"><EM>Roles</EM></A>. |
| 2529 |
This variable is normally maintained through the Setup/Rules/Roles |
| 2530 |
configuration screen. |
| 2531 |
It is a list variable. |
| 2532 |
Each member of the list is a single pattern/action pair, or it can be |
| 2533 |
a file which contains zero or more lines of pattern/action pairs. |
| 2534 |
The only way to create a roles file is to use the InsertFile command in |
| 2535 |
the Setup/Rules/Roles screen with a filename which doesn't yet exist. Then use |
| 2536 |
the Shuffle command to move existing roles into the file. |
| 2537 |
This isn't very convenient but it isn't thought that many users will |
| 2538 |
need this functionality. |
| 2539 |
The purpose of role files is for sharing roles. |
| 2540 |
<P> |
| 2541 |
|
| 2542 |
<DT> <A NAME="patterns-scores2"><EM>patterns-scores2</EM></A> |
| 2543 |
|
| 2544 |
<DD> Matching patterns and their corresponding actions are stored in |
| 2545 |
this variable. |
| 2546 |
These patterns are used with |
| 2547 |
<A HREF="#scoring-config"><EM>Scoring</EM></A>. |
| 2548 |
This variable is normally maintained through the Setup/Rules/SetScores |
| 2549 |
configuration screen. |
| 2550 |
It is a list variable. |
| 2551 |
Each member of the list is a single pattern/action pair, or it can be |
| 2552 |
a file which contains zero or more lines of pattern/action pairs. |
| 2553 |
The only way to create a scores file is to use the InsertFile command in |
| 2554 |
the Setup/Rules/SetScores screen with a filename which doesn't yet exist. |
| 2555 |
Then use the Shuffle command to move existing scoring patterns into the file. |
| 2556 |
This isn't very convenient but it isn't thought that many users will |
| 2557 |
need this functionality. |
| 2558 |
The purpose of scoring files is for sharing scoring rules. |
| 2559 |
<P> |
| 2560 |
This option is displayed as "Patterns Scores". |
| 2561 |
<P> |
| 2562 |
|
| 2563 |
<DT> <A NAME="patterns-search"><EM>patterns-search</EM></A> |
| 2564 |
|
| 2565 |
<DD> Matching patterns for use with the Select command are stored in |
| 2566 |
this variable. |
| 2567 |
These patterns are used with |
| 2568 |
<A HREF="#search-rules-config"><EM>Search Rules</EM></A> configuration. |
| 2569 |
This variable is normally maintained through the Setup/Rules/searCh |
| 2570 |
configuration screen. |
| 2571 |
It is a list variable. |
| 2572 |
Each member of the list is a single pattern, or it can be |
| 2573 |
a file which contains zero or more lines of patterns. |
| 2574 |
The only way to create a rules file is to use the InsertFile command in |
| 2575 |
the Setup/Rules/searCh screen with a filename which doesn't yet exist. Then use |
| 2576 |
the Shuffle command to move existing rules into the file. |
| 2577 |
This isn't very convenient but it isn't thought that many users will |
| 2578 |
need this functionality. |
| 2579 |
<P> |
| 2580 |
|
| 2581 |
<DT> <A NAME="personal-name"><EM>personal-name</EM></A> |
| 2582 |
|
| 2583 |
<DD> Personal configuration file only. |
| 2584 |
User's full personal name. On UNIX systems, the default is taken |
| 2585 |
from the accounts data base (<CODE>/etc/passwd</CODE>). |
| 2586 |
The easiest way to change the full From address is with the |
| 2587 |
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable. |
| 2588 |
<P> |
| 2589 |
|
| 2590 |
<DT> <A NAME="personal-print-category"><EM>personal-print-category</EM></A> |
| 2591 |
|
| 2592 |
<DD> Personal configuration file only. |
| 2593 |
This is the category that the default print command belongs to. There |
| 2594 |
are three categories. Category 1 is an attached printer which uses the ANSI |
| 2595 |
escape sequence, category 2 is the standard system print command, and |
| 2596 |
category 3 is the set of custom printer commands defined by the user. |
| 2597 |
This just helps <EM>Alpine</EM> figure out where to put the cursor when the user |
| 2598 |
runs the <EM>Setup/Printer</EM> command. This is not used by <EM>PC-Alpine</EM>. |
| 2599 |
<P> |
| 2600 |
|
| 2601 |
<DT> <A NAME="personal-print-command"><EM>personal-print-command</EM></A> |
| 2602 |
|
| 2603 |
<DD> Personal configuration file only. |
| 2604 |
This corresponds to the third category in the printer menu, the |
| 2605 |
personally selected print commands. This variable |
| 2606 |
contains the list of custom commands that the user has entered in the |
| 2607 |
<EM>Setup/Printer</EM> screen. This is not used by <EM>PC-Alpine</EM>. |
| 2608 |
<P> |
| 2609 |
|
| 2610 |
<DT> <A NAME="posting-char-set"><EM>posting-character-set</EM></A> |
| 2611 |
|
| 2612 |
<DD> See the discussion in |
| 2613 |
<A HREF="low-level.html#char-set">International Character Sets</EM></A> for |
| 2614 |
details.<P> |
| 2615 |
|
| 2616 |
<DT> <A NAME="postponed-folder"><EM>postponed-folder</EM></A> |
| 2617 |
|
| 2618 |
<DD> The folder where postponed messages are stored. The default is |
| 2619 |
<EM>postponed-msgs</EM> (Unix) or <EM>POSTPOND</EM> (PC). <P> |
| 2620 |
|
| 2621 |
<DT> <A NAME="print-font-name"><EM>print-font-name</EM></A> |
| 2622 |
|
| 2623 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 2624 |
|
| 2625 |
<DT> <A NAME="print-font-size"><EM>print-font-size</EM></A> |
| 2626 |
|
| 2627 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 2628 |
|
| 2629 |
<DT> <A NAME="print-font-style"><EM>print-font-style</EM></A> |
| 2630 |
|
| 2631 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. <P> |
| 2632 |
|
| 2633 |
<DT> <A NAME="printer"><EM>printer</EM></A> |
| 2634 |
|
| 2635 |
<DD> Personal configuration file only. |
| 2636 |
This is the current setting for a user's printer. |
| 2637 |
This variable is set from <EM>Alpine</EM>'s <EM>Setup/Printer</EM> screen. |
| 2638 |
<P> |
| 2639 |
|
| 2640 |
<DT> <A NAME="prompt-background-color"><EM>prompt-background-color</EM></A> |
| 2641 |
<DT> <A NAME="prompt-foreground-color"><EM>prompt-foreground-color</EM></A> |
| 2642 |
|
| 2643 |
<DD> <A HREF="#prompt-color"><EM>Prompt Color</EM></A>. |
| 2644 |
<P> |
| 2645 |
|
| 2646 |
<DT> <A NAME="pruned-folders"><EM>pruned-folders</EM></A> |
| 2647 |
|
| 2648 |
<DD> This variable allows you to define a list of one or more folders that |
| 2649 |
<EM>Alpine</EM> will offer to prune for you in the same way it automatically offers |
| 2650 |
to prune your "sent-mail" folder each month. |
| 2651 |
Each folder in this list must be a folder in your default folder collection |
| 2652 |
(the first folder collection if you have more than one), and it is just |
| 2653 |
the relative name of the folder in the collection, not the fully-qualified name. |
| 2654 |
It is similar to sent-mail. |
| 2655 |
Instead of something like |
| 2656 |
<P> |
| 2657 |
<CENTER><SAMP>pruned-folders={servername}mail/folder</SAMP></CENTER> |
| 2658 |
<P> |
| 2659 |
the correct value to use would be |
| 2660 |
<P> |
| 2661 |
<CENTER><SAMP>folder</SAMP></CENTER> |
| 2662 |
<P> |
| 2663 |
There is an assumption here that your first collection is the folders in |
| 2664 |
<P> |
| 2665 |
<CENTER><SAMP>{servername}mail</SAMP></CENTER> |
| 2666 |
<P> |
| 2667 |
|
| 2668 |
Once a month, for each folder listed, <EM>Alpine</EM> will offer to move |
| 2669 |
the contents of the folder to a new folder of the same name but with |
| 2670 |
the previous month's date appended. <EM>Alpine</EM> will then look for any such |
| 2671 |
date-appended folder names created for a previous month, and offer each |
| 2672 |
one it finds for deletion. |
| 2673 |
<P> |
| 2674 |
|
| 2675 |
If you decline the first offer, no mail is moved and no new folder is |
| 2676 |
created. |
| 2677 |
<P> |
| 2678 |
|
| 2679 |
The new folders will be created |
| 2680 |
in your default folder collection. |
| 2681 |
<P> |
| 2682 |
|
| 2683 |
<DT> <A NAME="pruning-rule"><EM>pruning-rule</EM></A> |
| 2684 |
|
| 2685 |
<DD> By default, <EM>Alpine</EM> will ask at the beginning of each month whether or not |
| 2686 |
you want to rename your sent-mail folder to a name like sent-mail-month-year. |
| 2687 |
(See the feature <A HREF="#prune-uses-yyyy-mm">prune-uses-yyyy-mm</A> to |
| 2688 |
change the format of the folder to sent-mail-yyyy-mm.) |
| 2689 |
It will also ask whether you would like to delete old sent-mail folders. |
| 2690 |
If you have defined |
| 2691 |
<A HREF="#read-msg-fold"><EM>read-message-folder</EM></A> |
| 2692 |
or |
| 2693 |
<A HREF="#pruned-folders"><EM>pruned-folders</EM></A> |
| 2694 |
<EM>Alpine</EM> will also ask about pruning those folders. |
| 2695 |
With this option you may provide an automatic answer to the rename questions |
| 2696 |
and you may tell <EM>Alpine</EM> to not ask about deleting old folders.<P> |
| 2697 |
|
| 2698 |
<DT> <A NAME="quote1-background-color"><EM>quote1-background-color</EM></A> |
| 2699 |
<DT> <A NAME="quote1-foreground-color"><EM>quote1-foreground-color</EM></A> |
| 2700 |
<DT> <A NAME="quote2-background-color"><EM>quote2-background-color</EM></A> |
| 2701 |
<DT> <A NAME="quote2-foreground-color"><EM>quote2-foreground-color</EM></A> |
| 2702 |
<DT> <A NAME="quote3-background-color"><EM>quote3-background-color</EM></A> |
| 2703 |
<DT> <A NAME="quote3-foreground-color"><EM>quote3-foreground-color</EM></A> |
| 2704 |
|
| 2705 |
<DD> <A HREF="#quote-colors"><EM>Quote Colors</EM></A>. |
| 2706 |
<P> |
| 2707 |
|
| 2708 |
<DT> <A NAME="quote-replace-string"><EM>quote-replace-string</EM></A> |
| 2709 |
|
| 2710 |
<DD> This option specifies what string to use as a quote when <b>viewing</b> a |
| 2711 |
message. The standard way of quoting messages when replying is the string |
| 2712 |
"> " (quote space). |
| 2713 |
With this variable set, viewing a message will |
| 2714 |
replace occurrences of "> " with the replacement string. |
| 2715 |
This setting works best when |
| 2716 |
<A HREF="#reply-ind-string">Reply-Indent-String</A> |
| 2717 |
or the equivalent setting in your correspondents' mail programs |
| 2718 |
is set to the default "> ", but it will also work fine with the |
| 2719 |
Reply-Indent-String set to ">". |
| 2720 |
<P> |
| 2721 |
Enable the feature |
| 2722 |
<A HREF="#quote-replace-nonflowed">Quote-Replace-Nonflowed</A> |
| 2723 |
to also have quote-replacement performed on non-flowed messages. |
| 2724 |
<P> |
| 2725 |
Setting this option will replace ">" and |
| 2726 |
"> " with the new setting. This string may include trailing |
| 2727 |
spaces. To preserve those spaces enclose the full string in double quotes. |
| 2728 |
<P> |
| 2729 |
No padding to separate the text of the message from the quote string is |
| 2730 |
added. This means that if you do not add trailing spaces to the value of |
| 2731 |
this variable, text will be displayed right next to the quote string, |
| 2732 |
which may be undesirable. This can be avoided by adding a new string |
| 2733 |
separated by a space from your selection of quote string replacement. This |
| 2734 |
last string will be used for padding. For example, setting this variable to |
| 2735 |
">" " " has the effect of setting |
| 2736 |
">" as the quote-replace-string, with the text padded by |
| 2737 |
a space from the last quote string to make it more readable. |
| 2738 |
<P> |
| 2739 |
One possible setting for this variable could be |
| 2740 |
" " (four spaces wrapped in quotes), which |
| 2741 |
would have the effect of indenting each level of quoting four spaces and |
| 2742 |
removing the ">"'s. Different levels of quoting could be made |
| 2743 |
more discernible by setting colors for quoted text. |
| 2744 |
<P> |
| 2745 |
Replying to or forwarding the viewed message will preserve the original |
| 2746 |
formatting of the message, so quote-replacement will not be performed on |
| 2747 |
messages that are being composed. |
| 2748 |
<P> |
| 2749 |
|
| 2750 |
<DT> <A NAME="quote-suppression-threshold"><EM>quote-suppression-threshold</EM></A> |
| 2751 |
|
| 2752 |
<DD> This option should be used with care. |
| 2753 |
It will cause some of the quoted text to be eliminated from the |
| 2754 |
display when viewing a message in the MESSAGE TEXT screen. |
| 2755 |
For example, if you set the Quote-Suppression-Threshold to the |
| 2756 |
value "5", |
| 2757 |
this will cause quoted text that is longer than five lines to be truncated. |
| 2758 |
Quoted text of five or fewer consecutive lines will be displayed in its entirety. |
| 2759 |
Quoted text of more than six lines will have the first five lines displayed |
| 2760 |
followed by a line that looks something like |
| 2761 |
<P> |
| 2762 |
<CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER> |
| 2763 |
<P> |
| 2764 |
As a special case, if exactly one line of quoted text would be hidden, the |
| 2765 |
entire quote will be shown instead. |
| 2766 |
So for the above example, quoted text which is exactly six lines long will |
| 2767 |
will be shown in its entirety. |
| 2768 |
(In other words, instead of hiding a single line and adding a line |
| 2769 |
that announces that one line was hidden, the line is just shown.) |
| 2770 |
<P> |
| 2771 |
If the sender of a message has carefully chosen the quotes that he or she |
| 2772 |
includes, hiding those quotes may change the meaning of the message. |
| 2773 |
For that reason, <EM>Alpine</EM> requires that when you want to set the value of this |
| 2774 |
variable to something less than four lines, you actually have to set it |
| 2775 |
to the negative of that number. |
| 2776 |
So if you want to set this option to "3", you actually have to |
| 2777 |
set it to "-3". |
| 2778 |
The only purpose of this is to get you to think about whether or not you |
| 2779 |
really want to do this! |
| 2780 |
If you want to delete all quoted text you set the value of this option |
| 2781 |
to the special value "-10". |
| 2782 |
<P> |
| 2783 |
The legal values for this option are |
| 2784 |
<P> |
| 2785 |
<TABLE> |
| 2786 |
<TR> |
| 2787 |
<TD> 0 </TD> |
| 2788 |
<TD> Default, don't hide anything </TD> |
| 2789 |
</TR> |
| 2790 |
<TR> |
| 2791 |
<TD> -1,-2,-3 </TD> |
| 2792 |
<TD> Suppress quote lines past 1, 2, or 3 lines </TD> |
| 2793 |
</TR> |
| 2794 |
<TR> |
| 2795 |
<TD> 4,5,6,... </TD> |
| 2796 |
<TD> Suppress if more than that many lines </TD> |
| 2797 |
</TR> |
| 2798 |
<TR> |
| 2799 |
<TD> -10 </TD> |
| 2800 |
<TD> Suppress all quoted lines </TD> |
| 2801 |
</TR> |
| 2802 |
</TABLE> |
| 2803 |
<P> |
| 2804 |
If you set this option to a non-default value you may sometimes wish to |
| 2805 |
view the quoted text that is not shown. |
| 2806 |
When this is the case, the HdrMode (Header Mode) command may be used to |
| 2807 |
show the hidden text. |
| 2808 |
Typing the "H" command once will show the hidden text. |
| 2809 |
Typing a second "H" will also turn on Full Header mode. |
| 2810 |
The presence or absence of the HdrMode command is determined by the |
| 2811 |
<A HREF="#enable-full-header-cmd">"Enable-Full-Header-Cmd"</A> |
| 2812 |
Feature-List option in your <EM>Alpine</EM> configuration, so you will want to |
| 2813 |
be sure that is turned on if you use quote suppression. |
| 2814 |
<P> |
| 2815 |
For the purposes of this option, a quote is a line that begins with the |
| 2816 |
character ">". |
| 2817 |
<P> |
| 2818 |
Quotes are only suppressed when displaying a message on the screen. |
| 2819 |
The entire quote will be left intact when printing or forwarding or something |
| 2820 |
similar. |
| 2821 |
<P> |
| 2822 |
|
| 2823 |
<DT> <A NAME="read-msg-fold"><EM>read-message-folder</EM></A> |
| 2824 |
|
| 2825 |
<DD> If set, mail in the <EM>INBOX</EM> that has been read but not deleted |
| 2826 |
is moved here, or rather, the user is asked whether or not he or she wants |
| 2827 |
to move it here upon quitting <EM>Alpine</EM>. <P> |
| 2828 |
|
| 2829 |
<DT> <A NAME="remote-abook-history"><EM>remote-abook-history</EM></A> |
| 2830 |
|
| 2831 |
<DD> Sets how many extra copies of |
| 2832 |
<A HREF="low-level.html#addrbook">remote address book</A> |
| 2833 |
data will be kept in each remote address book folder. |
| 2834 |
The default is three. |
| 2835 |
These extra copies are simply old versions of the data. Each time a change |
| 2836 |
is made a new copy of the address book data is appended to the folder. Old |
| 2837 |
copies are trimmed, if possible, when <EM>Alpine</EM> exits. |
| 2838 |
An old copy can be put back into use by |
| 2839 |
deleting and expunging newer versions of the data from the folder. |
| 2840 |
Don't delete the first message from the folder. It is a special header |
| 2841 |
message for the remote address book and it must be there. |
| 2842 |
This is to prevent regular folders from being used as remote address book |
| 2843 |
folders and having their data destroyed. |
| 2844 |
<P> |
| 2845 |
|
| 2846 |
<DT> <A NAME="remote-abook-metafile"><EM>remote-abook-metafile</EM></A> |
| 2847 |
|
| 2848 |
<DD> Personal configuration file only. |
| 2849 |
This is usually set by <EM>Alpine</EM> and is the name of a file |
| 2850 |
that contains data about |
| 2851 |
<A HREF="low-level.html#addrbook">remote address books</A> and |
| 2852 |
<A HREF="low-level.html#remote-config">remote configuration files</A>. |
| 2853 |
<P> |
| 2854 |
|
| 2855 |
<DT> <A NAME="remote-abook-validity"><EM>remote-abook-validity</EM></A> |
| 2856 |
|
| 2857 |
<DD> Sets the minimum number of minutes that a |
| 2858 |
remote address book will be considered up to date. |
| 2859 |
Whenever an entry contained in a remote address book is used, |
| 2860 |
if more than this many minutes have |
| 2861 |
passed since the last check the remote server will be queried to see if the |
| 2862 |
address book has changed. |
| 2863 |
If it has changed, the local copy is updated. |
| 2864 |
The default value is five minutes. |
| 2865 |
The special value of -1 means never check. |
| 2866 |
The special value of zero means only check when the address book is first |
| 2867 |
opened. |
| 2868 |
<P> |
| 2869 |
No matter what the value, the validity check is always done when the |
| 2870 |
address book is about to be changed by the user. |
| 2871 |
The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L) |
| 2872 |
while in the address book maintenance screen for the remote address book. |
| 2873 |
<P> |
| 2874 |
|
| 2875 |
<DT> <A NAME="reply-ind-str"><EM>reply-indent-string</EM></A> |
| 2876 |
|
| 2877 |
<DD> This variable specifies an aspect of <EM>Alpine</EM>'s <EM>Reply</EM> |
| 2878 |
command. |
| 2879 |
When a message is replied to and the text of the message is included, the |
| 2880 |
included text usually has the string "> " prepended |
| 2881 |
to each line indicating it is quoted text. |
| 2882 |
|
| 2883 |
<P> |
| 2884 |
This option specifies a different value for that string. |
| 2885 |
If you wish to use a string which begins or ends with a space, |
| 2886 |
enclose the string in double quotes. |
| 2887 |
|
| 2888 |
<P> |
| 2889 |
Besides simple text, the prepended string can be based |
| 2890 |
on the message being replied to. |
| 2891 |
The following tokens are substituted for the message's corresponding value: |
| 2892 |
|
| 2893 |
<DL> |
| 2894 |
<DT>_FROM_</DT> |
| 2895 |
<DD>This token gets replaced with the message sender's "username". |
| 2896 |
At most six characters are used. |
| 2897 |
</DD> |
| 2898 |
|
| 2899 |
<DT>_NICK_</DT> |
| 2900 |
<DD>This token gets replaced with the nickname of the message sender's |
| 2901 |
address as found in your addressbook. |
| 2902 |
If no addressbook entry is found, |
| 2903 |
Pine replaces the characters "_NICK_" with nothing. |
| 2904 |
At most six characters are used. |
| 2905 |
</DD> |
| 2906 |
|
| 2907 |
<DT>_INIT_</DT> |
| 2908 |
<DD>This token gets replaced with the initials of the sender of the message. |
| 2909 |
</DD> |
| 2910 |
|
| 2911 |
</DL> |
| 2912 |
|
| 2913 |
When the |
| 2914 |
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A> |
| 2915 |
feature is enabled, you are given the opportunity to edit the string, whether |
| 2916 |
it is the default or one automatically generated using the above tokens. |
| 2917 |
<P> |
| 2918 |
|
| 2919 |
<DT> <A NAME="reply-leadin"><EM>reply-leadin</EM></A> |
| 2920 |
|
| 2921 |
<DD> This option is used to customize the content of the introduction line |
| 2922 |
that is included when replying to a message and including the original |
| 2923 |
message in the reply. |
| 2924 |
The normal default (what you will get if you delete this variable) looks |
| 2925 |
something like: |
| 2926 |
<P> |
| 2927 |
<CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER> |
| 2928 |
<P> |
| 2929 |
where the day of the week is only included if it is available in the |
| 2930 |
original message. |
| 2931 |
You can replace this default with text of your own. |
| 2932 |
The text may contain tokens that are replaced with text |
| 2933 |
that depends on the message you are replying to. |
| 2934 |
For example, the default is equivalent to: |
| 2935 |
<P> |
| 2936 |
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER> |
| 2937 |
<P> |
| 2938 |
|
| 2939 |
Since this variable includes regular text mixed with special tokens |
| 2940 |
the tokens have to be surrounded by underscore characters. |
| 2941 |
For example, to use the token "<SAMP>PREFDATE</SAMP>" |
| 2942 |
you would need to use "<SAMP>_PREFDATE_</SAMP>", |
| 2943 |
not "<SAMP>PREFDATE</SAMP>". |
| 2944 |
<P> |
| 2945 |
The list of available tokens is |
| 2946 |
<A HREF="#index-tokens"><EM>here</EM></A>. |
| 2947 |
|
| 2948 |
<P> |
| 2949 |
By default, the text is all on a single line and is followed by a blank line. |
| 2950 |
If your <EM>Reply-Leadin</EM> turns out to be longer |
| 2951 |
than 80 characters when replying to a particular message, it is shortened. |
| 2952 |
However, if you use the token |
| 2953 |
<P> |
| 2954 |
<CENTER><SAMP>_NEWLINE_</SAMP></CENTER> |
| 2955 |
<P> |
| 2956 |
|
| 2957 |
anywhere in the value, no end of line or blank line is appended, and no |
| 2958 |
shortening is done. |
| 2959 |
The _NEWLINE_ token may be used to get rid of the blank line following |
| 2960 |
the text, to add more blank lines, or to form a multi-line |
| 2961 |
<EM>Reply-Leadin</EM>. |
| 2962 |
To clarify how _NEWLINE_ works recall that the default value is: |
| 2963 |
<P> |
| 2964 |
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER> |
| 2965 |
<P> |
| 2966 |
|
| 2967 |
That is equivalent to |
| 2968 |
<P> |
| 2969 |
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER> |
| 2970 |
<P> |
| 2971 |
|
| 2972 |
In the former case, two newlines are added automatically because |
| 2973 |
no _NEWLINE_ token appears in the value of the option (for backwards |
| 2974 |
compatibility). In the latter case, the newlines are explicit. |
| 2975 |
If you want to remove the blank line that follows the |
| 2976 |
<EM>Reply-Leadin</EM> text use a single |
| 2977 |
_NEWLINE_ token like |
| 2978 |
<P> |
| 2979 |
<CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER> |
| 2980 |
<P> |
| 2981 |
|
| 2982 |
Because of the backwards compatibility problem, it is not possible to |
| 2983 |
remove all of the ends of lines, because then there will be no _NEWLINE_ tokens |
| 2984 |
and that will cause the automatic adding of two newlines! |
| 2985 |
If you want, you may embed newlines in the middle of the text, as well, |
| 2986 |
producing a multi-line <EM>Reply-Leadin</EM>. |
| 2987 |
|
| 2988 |
<P> |
| 2989 |
By default, no attempt is made to localize the date. |
| 2990 |
If you prefer a localized form you may find that one of the tokens |
| 2991 |
_PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute. |
| 2992 |
If you want more control one of the many other date tokens, such as _DATEISO_, |
| 2993 |
might be better. |
| 2994 |
|
| 2995 |
<P> |
| 2996 |
For the adventurous, there is a way to conditionally include text based |
| 2997 |
on whether or not a token would result in specific replacement text. |
| 2998 |
For example, you could include some text based on whether or not |
| 2999 |
the _NEWS_ token would result in any newsgroups if it was used. |
| 3000 |
It's explained in detail |
| 3001 |
<A HREF="#reply-token-conditionals"><EM>here</EM></A>. |
| 3002 |
|
| 3003 |
<P> |
| 3004 |
In the very unlikely event that you want to include a literal token |
| 3005 |
in the introduction line you must precede it with a backslash character. |
| 3006 |
For example, |
| 3007 |
<P> |
| 3008 |
<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER> |
| 3009 |
<P> |
| 3010 |
would produce something like |
| 3011 |
<P> |
| 3012 |
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER> |
| 3013 |
<P> |
| 3014 |
It is not possible to have a literal backslash followed by an expanded token. |
| 3015 |
<P> |
| 3016 |
|
| 3017 |
<DT> <A NAME="reverse-background-color"><EM>reverse-background-color</EM></A> |
| 3018 |
<DT> <A NAME="reverse-foreground-color"><EM>reverse-foreground-color</EM></A> |
| 3019 |
|
| 3020 |
<DD> <A HREF="#reverse-color"><EM>Reverse Color</EM></A>. |
| 3021 |
<P> |
| 3022 |
|
| 3023 |
<DT> <A NAME="rsh-command"><EM>rsh-command</EM></A> |
| 3024 |
|
| 3025 |
<DD> Sets the format of the command used to |
| 3026 |
open a UNIX remote shell connection. The default is |
| 3027 |
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the |
| 3028 |
provided command. The first is for the command's pathname, the second is |
| 3029 |
for the host to connect to, the third is for the user to connect as, and |
| 3030 |
the fourth is for the connection method (typically <CODE>imap</CODE>). |
| 3031 |
<P> |
| 3032 |
|
| 3033 |
<DT> <A NAME="rsh-open-timeout"><EM>rsh-open-timeout</EM></A> |
| 3034 |
|
| 3035 |
<DD> Sets the time in seconds that <EM>Alpine</EM> will |
| 3036 |
attempt to open a UNIX remote shell connection. |
| 3037 |
The default is 15, the minimum non-zero value is 5, |
| 3038 |
and the maximum is unlimited. If this is set to zero rsh connections |
| 3039 |
will be completely disabled. |
| 3040 |
<P> |
| 3041 |
|
| 3042 |
<DT> <A NAME="rsh-path"><EM>rsh-path</EM></A> |
| 3043 |
|
| 3044 |
<DD> Sets the name of the command used to open a UNIX remote shell |
| 3045 |
connection. The default is typically <CODE>/usr/ucb/rsh</CODE>. |
| 3046 |
<P> |
| 3047 |
|
| 3048 |
<DT> <A NAME="saved-msg-name"><EM>saved-msg-name-rule</EM></A> |
| 3049 |
|
| 3050 |
<DD> Determines default folder name when <EM>Sav</EM>ing. |
| 3051 |
If set to <EM>default-folder</EM> (which is the default setting), |
| 3052 |
then <EM>Alpine</EM> will offer the folder "saved-messages" (UNIX) or "SAVEMAIL" |
| 3053 |
(PC) for <EM>Sav</EM>ing messages. The default folder offered in this way |
| 3054 |
may be changed by using the configuration variable |
| 3055 |
<A HREF="#def-save"><EM>default-saved-msg-folder</EM></A>. |
| 3056 |
<P> |
| 3057 |
|
| 3058 |
If this rule is set to <EM>last-folder-used</EM>, <EM>Alpine</EM> offers to |
| 3059 |
<EM>Save</EM> to the folder you last successfully <EM>Saved</EM> a message |
| 3060 |
to (this session). |
| 3061 |
The first time you <EM>Save</EM> a message in a session, |
| 3062 |
<EM>Alpine</EM> offers to <EM>Save</EM> the message to the default folder. |
| 3063 |
<P> |
| 3064 |
|
| 3065 |
Choosing any of the <EM>by-</EM> options causes <EM>Alpine</EM> to attempt |
| 3066 |
to get the chosen option's value for the message being <EM>Saved</EM> (or |
| 3067 |
for the first message being Saved if using an aggregate Save). |
| 3068 |
For example, if <EM>by-from</EM> is chosen, <EM>Alpine</EM> attempts to |
| 3069 |
get the value of who the message |
| 3070 |
came from (i.e. the from address). <EM>Alpine</EM> then attempts to |
| 3071 |
<EM>Save</EM> the message to a folder matching that value. |
| 3072 |
If <EM>by-from</EM> is chosen and no value is |
| 3073 |
obtained, <EM>Alpine</EM> uses <EM>by-sender</EM>. |
| 3074 |
The opposite is also true. |
| 3075 |
If <EM>by-recipient</EM> was chosen and the message was posted to a newsgroup, |
| 3076 |
<EM>Alpine</EM> will use the newsgroup name. |
| 3077 |
If <EM>by-replyto</EM> is chosen and no value is |
| 3078 |
obtained, <EM>Alpine</EM> uses <EM>by-from</EM>. |
| 3079 |
<P> |
| 3080 |
|
| 3081 |
If any of the "by-realname" options are chosen, <EM>Alpine</EM> will attempt |
| 3082 |
to use the personal name part of the address instead of the mailbox part. |
| 3083 |
If any of the "by-nick" options are chosen, the |
| 3084 |
address is looked up in your address book and if found, the |
| 3085 |
nickname for that entry is used. |
| 3086 |
Only simple address book entries are checked, not distribution lists. |
| 3087 |
Similarly, if any of the |
| 3088 |
"by-fcc" options are chosen, the fcc from the corresponding |
| 3089 |
address book entry is used. |
| 3090 |
If by-realname, or the by-nick or by-fcc lookups result in no value, |
| 3091 |
then if the chosen option ends with the "then-from", |
| 3092 |
"then-sender", "then-replyto", |
| 3093 |
or "then-recip" suffix, <EM>Alpine</EM> |
| 3094 |
reverts to the same behavior as "by-from", |
| 3095 |
"by-sender", "by-replyto", or "by-recip" |
| 3096 |
depending on which option was specified. |
| 3097 |
If the chosen option doesn't end with one of |
| 3098 |
the "then-" suffixes, then <EM>Alpine</EM> reverts to the default |
| 3099 |
folder when no match is found in the address book. |
| 3100 |
|
| 3101 |
<P> |
| 3102 |
Here is an example to make some of the options clearer. |
| 3103 |
If the message is From |
| 3104 |
<P> |
| 3105 |
<CENTER><SAMP>Fred Flintstone <[email protected]></SAMP></CENTER> |
| 3106 |
<P> |
| 3107 |
and this rule is set to "by-from", then the default folder offered |
| 3108 |
in the save dialog would be "flint". |
| 3109 |
<P> |
| 3110 |
If this rule is set to "by-realname-of-from" then the default would |
| 3111 |
be "Fred Flintstone". |
| 3112 |
<P> |
| 3113 |
If this rule is set to "by-nick-of-from" then <EM>Alpine</EM> will search |
| 3114 |
for the address "[email protected]" in your address book. |
| 3115 |
If an entry is found and it has a nickname associated with it, that nickname |
| 3116 |
will be offered as the default folder. |
| 3117 |
If not, the default saved message folder will be offered as the default. |
| 3118 |
<P> |
| 3119 |
If this rule is set to "by-fcc-of-from" then <EM>Alpine</EM> will search |
| 3120 |
for the address "[email protected]" in your address book. |
| 3121 |
If an entry is found and it has an Fcc associated with it, that Fcc |
| 3122 |
will be offered as the default folder. |
| 3123 |
If not, the default saved message folder will be offered as the default. |
| 3124 |
<P> |
| 3125 |
If this rule is set to "by-nick-of-from-then-from" then <EM>Alpine</EM> will search |
| 3126 |
for the address "[email protected]" in your address book. |
| 3127 |
If an entry is found and it has a nickname associated with it, that nickname |
| 3128 |
will be offered as the default folder. |
| 3129 |
If it is not found (or has no nickname) then the default offered will be |
| 3130 |
the same as it would be for the "by-from" rule. |
| 3131 |
That is, it would be "flint" |
| 3132 |
<P> |
| 3133 |
This option is displayed as "Saved Message Name Rule". |
| 3134 |
<P> |
| 3135 |
|
| 3136 |
<DT> <A NAME="scroll-margin"><EM>scroll-margin</EM></A> |
| 3137 |
|
| 3138 |
<DD> This option controls when <EM>Alpine</EM>'s line-by-line scrolling occurs. |
| 3139 |
Typically, when a selected item is at the top or bottom screen edge |
| 3140 |
and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are pressed, the |
| 3141 |
displayed items are scrolled down or up by a single line. |
| 3142 |
<P> |
| 3143 |
|
| 3144 |
This option allows you to tell <EM>Alpine</EM> the number of lines from the top and |
| 3145 |
bottom screen edge that line-by-line scrolling should occur. For example, |
| 3146 |
setting this value to one (1) will cause <EM>Alpine</EM> to scroll the display |
| 3147 |
when you move to select an item on the display's top or |
| 3148 |
bottom edge (instead of moving when you move off the edge of the screen). |
| 3149 |
<P> |
| 3150 |
|
| 3151 |
By default, this variable is zero (0), indicating that scrolling happens |
| 3152 |
when you move up or down to select an item immediately off the display's |
| 3153 |
top or bottom edge. |
| 3154 |
<P> |
| 3155 |
|
| 3156 |
<DT> <A NAME="selectable-item-background-color"><EM>selectable-item-background-color</EM></A> |
| 3157 |
<DT> <A NAME="selectable-item-foreground-color"><EM>selectable-item-foreground-color</EM></A> |
| 3158 |
|
| 3159 |
<DD> <A HREF="#selectable-item-color"><EM>Selectable-item Color</EM></A>. |
| 3160 |
<P> |
| 3161 |
|
| 3162 |
<DT> <A NAME="sending-filters"><EM>sending-filters</EM></A> |
| 3163 |
|
| 3164 |
<DD> This option defines a list of text-filtering commands (programs and |
| 3165 |
scripts) that may be selectively invoked to process a message just before |
| 3166 |
it is sent. If set, the Composer's <EM>^X Send</EM> command will allow you to |
| 3167 |
select which filter (or none) to apply to the message before it is sent. |
| 3168 |
For security reasons, the full path of the filter program must be |
| 3169 |
specified. |
| 3170 |
<P> |
| 3171 |
Sending filters do not work with <EM>PC-Alpine</EM> and sending filters are |
| 3172 |
not used if the feature |
| 3173 |
<A HREF="#send-without-confirm">send-without-confirm</A> is set. |
| 3174 |
<P> |
| 3175 |
Command Modifying Tokens: |
| 3176 |
|
| 3177 |
<DL> |
| 3178 |
<DT><EM>_RECIPIENTS_</EM> |
| 3179 |
<DD>When the command is executed, this token is replaced |
| 3180 |
with the space delimited list of recipients of the |
| 3181 |
message being sent. |
| 3182 |
|
| 3183 |
<DT><EM>_TMPFILE_</EM> |
| 3184 |
<DD> |
| 3185 |
When the command is executed, this token is |
| 3186 |
replaced with the path and name of the temporary |
| 3187 |
file containing the text to be filtered. <EM>Alpine</EM> |
| 3188 |
expects the filter to replace this data with the |
| 3189 |
filter's result. |
| 3190 |
|
| 3191 |
NOTE: Use of this token implies that the text to |
| 3192 |
be filtered is not piped into standard input of the |
| 3193 |
executed command and its standard output is ignored. |
| 3194 |
<EM>Alpine</EM> restores the tty modes before invoking the |
| 3195 |
filter in case the filter interacts with the user |
| 3196 |
via its own standard input and output. |
| 3197 |
|
| 3198 |
<DT><EM>_RESULTFILE_</EM> |
| 3199 |
<DD>When the command is executed, this token is |
| 3200 |
replaced with the path and name of a temporary |
| 3201 |
file intended to contain a status message from the |
| 3202 |
filter. <EM>Alpine</EM> displays this in the message status |
| 3203 |
field. |
| 3204 |
|
| 3205 |
<DT><EM>_DATAFILE_</EM> |
| 3206 |
<DD>When the command is executed, this token is replaced |
| 3207 |
in the command line with the path and name of a |
| 3208 |
temporary file that <EM>Alpine</EM> creates once per session |
| 3209 |
and deletes upon exit. The file is intended to be |
| 3210 |
used by the filter to store state information between |
| 3211 |
instances of the filter. |
| 3212 |
|
| 3213 |
<DT><EM>_PREPENDKEY_</EM> |
| 3214 |
<DD>When the command is executed, this token indicates |
| 3215 |
that a random number will be passed down the input |
| 3216 |
stream before the message text. It is not included as a command-line argument. |
| 3217 |
This number could be used as a session key. It is sent in this way |
| 3218 |
to improve security. The number is unique to the |
| 3219 |
current <EM>Alpine</EM> session and is only generated once per |
| 3220 |
session. |
| 3221 |
|
| 3222 |
<DT><EM>_INCLUDEALLHDRS_</EM> |
| 3223 |
<DD>When the command is executed, this token indicates |
| 3224 |
that the headers of the message will be passed down the input stream |
| 3225 |
before the message text. |
| 3226 |
It is not included as a command-line argument. |
| 3227 |
The filter should, of course, remove the headers before returning control |
| 3228 |
to <EM>Alpine</EM>. |
| 3229 |
|
| 3230 |
<DT><EM>_MIMETYPE_</EM> |
| 3231 |
<DD>When the command is executed, this token is replaced in the |
| 3232 |
command name with a temporary file name used to accept any new MIME |
| 3233 |
Content-Type information necessitated by the output of the filter. |
| 3234 |
Upon the filter's exit, if the file contains new MIME type |
| 3235 |
information, <EM>Alpine</EM> verifies its format and replaces the outgoing |
| 3236 |
message's MIME type information with that contained in the file. This |
| 3237 |
is basically a cheap way of sending something other than Text/Plain. |
| 3238 |
</DL> |
| 3239 |
<P> |
| 3240 |
|
| 3241 |
<DT> <A NAME="sendmail-path"><EM>sendmail-path</EM></A> |
| 3242 |
|
| 3243 |
<DD> This names the path to an |
| 3244 |
alternative program, and any necessary arguments, to be used in posting |
| 3245 |
mail messages. See the section on <A |
| 3246 |
HREF="background.html#SMTP">SMTP and Sendmail</A> for more details. |
| 3247 |
<P> |
| 3248 |
|
| 3249 |
<DT> <A NAME="sig-file"><EM>signature-file</EM></A></A> |
| 3250 |
|
| 3251 |
<DD> This is the name of a file which will be automatically inserted into |
| 3252 |
outgoing messages. |
| 3253 |
It typically contains information such as your |
| 3254 |
name, email address and organizational affiliation. |
| 3255 |
<EM>Alpine</EM> adds the |
| 3256 |
signature into the message as soon as you enter the composer so you |
| 3257 |
can choose to remove it or edit it on a message by message basis. |
| 3258 |
Signature file placement in message replies is controlled by the |
| 3259 |
<A HREF="#sig-at-bot">signature-at-bottom</A> |
| 3260 |
setting in the feature list. |
| 3261 |
<P> |
| 3262 |
|
| 3263 |
This defaults to |
| 3264 |
<CODE>~/.signature</CODE> on UNIX and <PINERC |
| 3265 |
directory><CODE>\PINE.SIG</CODE> on a PC. <P> |
| 3266 |
|
| 3267 |
To create or edit your signature file choose Setup from the Main Menu |
| 3268 |
and then select S for Signature (Main/Setup/Signature). |
| 3269 |
This puts you |
| 3270 |
into the Signature Editor where you can enter a <EM>few</EM> lines of |
| 3271 |
text containing your identity and affiliation. |
| 3272 |
|
| 3273 |
<P> |
| 3274 |
If the filename is followed by a vertical bar (|) then instead |
| 3275 |
of reading the contents of the file the file is assumed to be a |
| 3276 |
program which will produce the text to be used on its standard output. |
| 3277 |
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>, |
| 3278 |
but the rest of the processing works as if the contents came from a file. |
| 3279 |
|
| 3280 |
<P> |
| 3281 |
Instead of storing the data in a local file, the |
| 3282 |
signature data may be stored remotely in an IMAP folder. |
| 3283 |
In order to do this, |
| 3284 |
you must use a remote name for the file. |
| 3285 |
A remote signature-file name might look like: |
| 3286 |
<P> |
| 3287 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER> |
| 3288 |
<P> |
| 3289 |
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try |
| 3290 |
<P> |
| 3291 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/signature</SAMP></CENTER> |
| 3292 |
<P> |
| 3293 |
|
| 3294 |
The syntax used here is the same as the syntax used for remote configuration |
| 3295 |
files from the command line. |
| 3296 |
Note that you may not access an existing signature file remotely, |
| 3297 |
you have to create a new <EM>folder</EM> which contains the signature data. |
| 3298 |
If the name you use here for the signature file is a remote name, then when |
| 3299 |
you edit the file from the Setup/Signature command the data will be stored |
| 3300 |
remotely in the folder. |
| 3301 |
You aren't required to do anything special to create the folder, it |
| 3302 |
gets created automatically if you use a remote name. |
| 3303 |
|
| 3304 |
<P> |
| 3305 |
Besides regular text, the signature file may also contain |
| 3306 |
(or a signature program may produce) tokens which |
| 3307 |
are replaced with text which usually depends on the message you are replying |
| 3308 |
to or forwarding. |
| 3309 |
For example, if the signature file contains the token |
| 3310 |
<P> |
| 3311 |
<CENTER><SAMP>_DATE_</SAMP></CENTER> |
| 3312 |
<P> |
| 3313 |
anywhere in the text, then that token is replaced by the date |
| 3314 |
the message you are replying to or forwarding was sent. |
| 3315 |
If it contains |
| 3316 |
<P> |
| 3317 |
<CENTER><SAMP>_CURDATE_</SAMP></CENTER> |
| 3318 |
<P> |
| 3319 |
that is replaced with the current date. |
| 3320 |
The first is an example of a token which depends on the message you |
| 3321 |
are replying to (or forwarding) and the second is an example which |
| 3322 |
doesn't depend on anything other than the current date. |
| 3323 |
You have to be a little careful with this facility since tokens which |
| 3324 |
depend on the message you are replying to or forwarding will be replaced |
| 3325 |
by nothing in the case where you are composing a new message from scratch. |
| 3326 |
The use of <A HREF="#role-config"><EM>roles</EM></A> may help you |
| 3327 |
in this respect. |
| 3328 |
It allows you to use different signature files in different cases. |
| 3329 |
<P> |
| 3330 |
|
| 3331 |
The list of tokens available for use in the signature file is |
| 3332 |
<A HREF="#index-tokens"><EM>here</EM></A>. |
| 3333 |
<P> |
| 3334 |
|
| 3335 |
Instead of, or along with the use of <EM>roles</EM> to give you |
| 3336 |
different signature files in different situations, there is also |
| 3337 |
a way to conditionally include text based |
| 3338 |
on whether or not a token would result in specific replacement text. |
| 3339 |
For example, you could include some text based on whether or not |
| 3340 |
the _NEWS_ token would result in any newsgroups if it was used. |
| 3341 |
This is explained in detail |
| 3342 |
<A HREF="#reply-token-conditionals"><EM>here</EM></A>. |
| 3343 |
This isn't for the faint of heart. |
| 3344 |
<P> |
| 3345 |
In the very unlikely event that you want to include a literal token |
| 3346 |
in the signature you must precede it with a backslash character. |
| 3347 |
For example, |
| 3348 |
<P> |
| 3349 |
<CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER> |
| 3350 |
<P> |
| 3351 |
would produce something like |
| 3352 |
<P> |
| 3353 |
<CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER> |
| 3354 |
<P> |
| 3355 |
It is not possible to have a literal backslash followed by an expanded token. |
| 3356 |
<P> |
| 3357 |
|
| 3358 |
<DT> <A NAME="signature-background-color"><EM>signature-background-color</EM></A> |
| 3359 |
<DT> <A NAME="signature-foreground-color"><EM>signature-foreground-color</EM></A> |
| 3360 |
|
| 3361 |
<DD> <A HREF="#signature-color"><EM>Signature Color</EM></A>. |
| 3362 |
<P> |
| 3363 |
|
| 3364 |
<DT> <A NAME="smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A> |
| 3365 |
|
| 3366 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3367 |
<P> |
| 3368 |
If the option |
| 3369 |
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A> |
| 3370 |
is set then this option will have no effect. |
| 3371 |
<P> |
| 3372 |
Normally, Public Certificates for use with S/MIME will be stored in the directory |
| 3373 |
which is the value of this option. |
| 3374 |
Those certificates will be stored in PEM format, one certificate per file. |
| 3375 |
The name of the file for the certificate corresponding to |
| 3376 |
<P> |
| 3377 |
<CENTER><SAMP>emailaddress</SAMP></CENTER> |
| 3378 |
<P> |
| 3379 |
should be |
| 3380 |
<P> |
| 3381 |
<CENTER><SAMP>emailaddress.crt</SAMP></CENTER> |
| 3382 |
<P> |
| 3383 |
For example, a file for [email protected] would be in the file |
| 3384 |
<P> |
| 3385 |
<CENTER><SAMP>[email protected]</SAMP></CENTER> |
| 3386 |
<P> |
| 3387 |
in this directory. |
| 3388 |
<P> |
| 3389 |
Use the Setup/SMIME screen to modify this variable. |
| 3390 |
<P> |
| 3391 |
Typically, the public certificates that you have will come from S/MIME signed |
| 3392 |
messages that are sent to you. |
| 3393 |
<EM>Alpine</EM> will extract the public certificate from the signed message and store |
| 3394 |
it in the certificates directory. |
| 3395 |
These PEM format public certificates look something like: |
| 3396 |
<PRE> |
| 3397 |
-----BEGIN CERTIFICATE----- |
| 3398 |
MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB |
| 3399 |
rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug |
| 3400 |
Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho |
| 3401 |
... |
| 3402 |
2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8 |
| 3403 |
D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf |
| 3404 |
-----END CERTIFICATE----- |
| 3405 |
</PRE> |
| 3406 |
<P> |
| 3407 |
<UL> |
| 3408 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3409 |
</UL><P> |
| 3410 |
This option is displayed as "S/MIME - Public Cert Directory". |
| 3411 |
<P> |
| 3412 |
|
| 3413 |
<DT> <A NAME="smime-public-cert-container"><EM>smime-public-cert-container</EM></A> |
| 3414 |
|
| 3415 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3416 |
<P> |
| 3417 |
If this option is set it will be used instead of |
| 3418 |
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A> |
| 3419 |
<P> |
| 3420 |
This option gives you a way to store certificates remotely on an IMAP server |
| 3421 |
instead of storing the certificates one per file locally. |
| 3422 |
In order to do that you just give this option a remote folder name for a folder |
| 3423 |
which does not yet exist. |
| 3424 |
The name is similar to the name you might use for a remote configuration file. |
| 3425 |
A remote folder name might look something like: |
| 3426 |
<P> |
| 3427 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER> |
| 3428 |
<P> |
| 3429 |
Use the Setup/SMIME screen to modify this variable. |
| 3430 |
<P> |
| 3431 |
<UL> |
| 3432 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3433 |
</UL><P> |
| 3434 |
This option is displayed as "S/MIME - Public Cert Container". |
| 3435 |
<P> |
| 3436 |
|
| 3437 |
<DT> <A NAME="smime-private-key-directory"><EM>smime-private-key-directory</EM></A> |
| 3438 |
|
| 3439 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3440 |
<P> |
| 3441 |
In order to sign outgoing S/MIME messages you will need a |
| 3442 |
personal digital ID certificate. |
| 3443 |
You will usually get such a certificate from a certificate authority such as |
| 3444 |
Thawte or CAcert. |
| 3445 |
(In order to encrypt outgoing messages you don't need a personal digital ID, you |
| 3446 |
need the public certificate of the recipient instead.) |
| 3447 |
If the option |
| 3448 |
<A HREF="#smime-private-key-container"><EM>smime-private-key-container</EM></A> |
| 3449 |
is set then this option will have no effect. |
| 3450 |
<P> |
| 3451 |
Normally, Private Keys for use with S/MIME will be stored in the directory |
| 3452 |
which is the value of this option. |
| 3453 |
Those certificates will be stored in PEM format, one certificate per file. |
| 3454 |
The name of the file for the certificate corresponding to your |
| 3455 |
<P> |
| 3456 |
<CENTER><SAMP>emailaddress</SAMP></CENTER> |
| 3457 |
<P> |
| 3458 |
should be |
| 3459 |
<P> |
| 3460 |
<CENTER><SAMP>emailaddress.key</SAMP></CENTER> |
| 3461 |
<P> |
| 3462 |
For example, if your address is [email protected] the name of the file would be |
| 3463 |
<P> |
| 3464 |
<CENTER><SAMP>[email protected]</SAMP></CENTER> |
| 3465 |
<P> |
| 3466 |
in this directory. |
| 3467 |
<P> |
| 3468 |
Use the Setup/SMIME screen to modify this variable. |
| 3469 |
<P> |
| 3470 |
Typically, the private key that you have will come from a Certificate |
| 3471 |
Authority. |
| 3472 |
The private key should be stored in a PEM format file that |
| 3473 |
looks something like: |
| 3474 |
<PRE> |
| 3475 |
-----BEGIN RSA PRIVATE KEY----- |
| 3476 |
Proc-Type: 4,ENCRYPTED |
| 3477 |
DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6 |
| 3478 |
|
| 3479 |
YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI |
| 3480 |
SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k |
| 3481 |
VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA |
| 3482 |
... |
| 3483 |
oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix |
| 3484 |
m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA== |
| 3485 |
-----END RSA PRIVATE KEY----- |
| 3486 |
</PRE> |
| 3487 |
<P> |
| 3488 |
<UL> |
| 3489 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3490 |
</UL><P> |
| 3491 |
This option is displayed as "S/MIME - Private Key Directory". |
| 3492 |
<P> |
| 3493 |
|
| 3494 |
<DT> <A NAME="smime-private-key-container"><EM>smime-private-key-container</EM></A> |
| 3495 |
|
| 3496 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3497 |
<P> |
| 3498 |
If this option is set it will be used instead of |
| 3499 |
<A HREF="#smime-private-key-directory"><EM>smime-private-key-directory</EM></A>. |
| 3500 |
<P> |
| 3501 |
This option gives you a way to store keys remotely on an IMAP server |
| 3502 |
instead of storing the keys one per file locally. |
| 3503 |
In order to do that you just give this option a remote folder name for a folder |
| 3504 |
which does not yet exist. |
| 3505 |
The name is similar to the name you might use for a remote configuration file. |
| 3506 |
A remote folder name might look something like: |
| 3507 |
<P> |
| 3508 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER> |
| 3509 |
<P> |
| 3510 |
Use the Setup/SMIME screen to modify this variable. |
| 3511 |
<P> |
| 3512 |
<UL> |
| 3513 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3514 |
</UL><P> |
| 3515 |
This option is displayed as "S/MIME - Private Key Container". |
| 3516 |
<P> |
| 3517 |
|
| 3518 |
<DT> <A NAME="smime-cacert-directory"><EM>smime-cacert-directory</EM></A> |
| 3519 |
|
| 3520 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3521 |
<P> |
| 3522 |
If the option |
| 3523 |
<A HREF="#smime-cacert-container"><EM>smime-cacert-container</EM></A> |
| 3524 |
is set then this option will have no effect. |
| 3525 |
<P> |
| 3526 |
CACert is a shorthand name for certification authority certificate. |
| 3527 |
Normally <EM>Alpine</EM> will use the CACerts that are located in the standard system |
| 3528 |
location for CACerts. |
| 3529 |
It may be the case that one of your correspondents has a Digital ID which has |
| 3530 |
been signed by a certificate authority that is not in the regular set of system certificate |
| 3531 |
authorities. |
| 3532 |
You may supplement the system list by adding further certificates of your own. |
| 3533 |
These should be stored in the directory |
| 3534 |
which is the value of this option. |
| 3535 |
The certificates will be stored in PEM format, one certificate per file. |
| 3536 |
The names of the files can be anything ending in ".crt". |
| 3537 |
<P> |
| 3538 |
Use the Setup/SMIME screen to modify this variable. |
| 3539 |
<P> |
| 3540 |
These PEM format CA certificates look very similar to your public |
| 3541 |
certificates for particular email addresses |
| 3542 |
(<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A>). |
| 3543 |
<P> |
| 3544 |
<UL> |
| 3545 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3546 |
</UL><P> |
| 3547 |
This option is displayed as "S/MIME - Cert Authority Directory". |
| 3548 |
<P> |
| 3549 |
|
| 3550 |
<DT> <A NAME="smime-cacert-container"><EM>smime-cacert-container</EM></A> |
| 3551 |
|
| 3552 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3553 |
<P> |
| 3554 |
If this option is set it will be used instead of |
| 3555 |
<A HREF="#smime-cacert-directory"><EM>smime-cacert-directory</EM></A>. |
| 3556 |
<P> |
| 3557 |
This option gives you a way to store certificates remotely on an IMAP server |
| 3558 |
instead of storing the certificates one per file locally. |
| 3559 |
In order to do that you just give this option a remote folder name for a folder |
| 3560 |
which does not yet exist. |
| 3561 |
The name is similar to the name you might use for a remote configuration file. |
| 3562 |
A remote folder name might look something like: |
| 3563 |
<P> |
| 3564 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER> |
| 3565 |
<P> |
| 3566 |
Use the Setup/SMIME screen to modify this variable. |
| 3567 |
<P> |
| 3568 |
<UL> |
| 3569 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 3570 |
</UL><P> |
| 3571 |
This option is displayed as "S/MIME - Cert Authority Container". |
| 3572 |
<P> |
| 3573 |
|
| 3574 |
<DT> <A NAME="smtp-server"><EM>smtp-server</EM></A> |
| 3575 |
|
| 3576 |
<DD> One or more SMTP servers (host name or IP address) which <EM>Alpine</EM> will |
| 3577 |
use for outgoing mail. If not set, <EM>Alpine</EM> passes outgoing email to the |
| 3578 |
<EM>sendmail</EM> program on the local machine. <EM>PC-Alpine</EM> users must have |
| 3579 |
this variable set in order to send mail as they have no <EM>sendmail</EM> |
| 3580 |
program. |
| 3581 |
<P> |
| 3582 |
Your SMTP server may offer SMTP AUTH authentication. |
| 3583 |
It may even require it. |
| 3584 |
If your SMTP server offers SMTP AUTH authentication you may specify a |
| 3585 |
"user" name parameter to cause <EM>Alpine</EM> to attempt to authenticate. |
| 3586 |
This parameter requires an associated value, |
| 3587 |
the username identifier with which to establish the server |
| 3588 |
connection. |
| 3589 |
An example might be: |
| 3590 |
|
| 3591 |
<P> |
| 3592 |
<CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER> |
| 3593 |
<P> |
| 3594 |
|
| 3595 |
If AUTH authentication is offered by the server, this will cause <EM>Alpine</EM> to |
| 3596 |
attempt to use it. |
| 3597 |
If AUTH authentication is not offered by the server, this will cause <EM>Alpine</EM> |
| 3598 |
to fail sending with an error similar to: |
| 3599 |
|
| 3600 |
<P> |
| 3601 |
<CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER> |
| 3602 |
<P> |
| 3603 |
|
| 3604 |
Another type of authentication that is used by some ISPs is called |
| 3605 |
"POP before SMTP" or "IMAP before SMTP", |
| 3606 |
which means that you have to authenticate |
| 3607 |
yourself to the POP or IMAP server by opening a mailbox before you |
| 3608 |
can send mail. |
| 3609 |
To do this, you usually only have to open your INBOX. |
| 3610 |
<P> |
| 3611 |
You may tell <EM>Alpine</EM> to use the |
| 3612 |
<A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A> |
| 3613 |
port (587) instead of the SMTP port (25) by including the "submit" |
| 3614 |
parameter |
| 3615 |
in this option. |
| 3616 |
At this time "/submit" is simply equivalent to specifying |
| 3617 |
port 587, though it may imply more than that at some point in the future. |
| 3618 |
Some ISPs are blocking port 25 in order to reduce the amount of spam |
| 3619 |
being sent to their users. |
| 3620 |
You may find that the submit option allows you to get around such a block. |
| 3621 |
|
| 3622 |
<P> |
| 3623 |
<CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER> |
| 3624 |
<P> |
| 3625 |
|
| 3626 |
To specify any non-standard port number on the SMTP server you may follow |
| 3627 |
the hostname with a colon followed by the portnumber. |
| 3628 |
|
| 3629 |
<P> |
| 3630 |
<CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER> |
| 3631 |
<P> |
| 3632 |
|
| 3633 |
Normally, when a connection is made to the Smtp-Server <EM>Alpine</EM> will attempt |
| 3634 |
to negotiate a secure (encrypted) session using Transport Layer Security (TLS). |
| 3635 |
If that fails then a non-encrypted connection will be attempted instead. |
| 3636 |
You may specify that a TLS connection is required if you wish. |
| 3637 |
If you append "/tls" to the name then the connection will fail |
| 3638 |
instead of falling back to a non-secure connection. |
| 3639 |
|
| 3640 |
<P> |
| 3641 |
<CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER> |
| 3642 |
<P> |
| 3643 |
|
| 3644 |
See the |
| 3645 |
<A HREF="config-notes.html#smtp-server">SMTP Servers</A> |
| 3646 |
section or the |
| 3647 |
<A HREF="config-notes.html#server-name-syntax">Server Name Syntax</A> |
| 3648 |
section for some more details. |
| 3649 |
<P> |
| 3650 |
This option is displayed as "SMTP Server (for sending)". |
| 3651 |
<P> |
| 3652 |
|
| 3653 |
<DT> <A NAME="sort-key"><EM>sort-key</EM></A> |
| 3654 |
|
| 3655 |
<DD> This variable sets up the default Message Index sorting. |
| 3656 |
The default is to |
| 3657 |
sort by arrival order (the order the messages arrived in the folder). |
| 3658 |
It has the same functionality as the |
| 3659 |
<EM>-sort</EM> command line argument and the <EM>$</EM> command in the |
| 3660 |
"Folder Index". If a <EM>sort-key</EM> is set, then all folders open during |
| 3661 |
the session will have that as the default sort order. <P> |
| 3662 |
|
| 3663 |
<DT> <A NAME="speller"><EM>speller</EM></A> |
| 3664 |
|
| 3665 |
<DD> UNIX <EM>Alpine</EM> only. |
| 3666 |
<P> |
| 3667 |
For <EM>PC-Alpine</EM>, you must install the aspell library code that you |
| 3668 |
may get from |
| 3669 |
<A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>. |
| 3670 |
<P> |
| 3671 |
This option affects the behavior of the <EM>^T</EM> (spell check) |
| 3672 |
command in the Composer. |
| 3673 |
It specifies the program invoked by <EM>^T</EM> in the Composer. |
| 3674 |
By default, <EM>Alpine</EM> uses the system's "spell" command. |
| 3675 |
<EM>Alpine</EM> will use the |
| 3676 |
command defined by this option (if any) instead. |
| 3677 |
When invoking the spell-checking program, |
| 3678 |
<EM>Alpine</EM> appends a tempfile name (where the message is passed) |
| 3679 |
to the command line. |
| 3680 |
<EM>Alpine</EM> expects the speller to correct the |
| 3681 |
spelling in that file. When you exit from the speller |
| 3682 |
program <EM>Alpine</EM> will read the |
| 3683 |
tmpfile back into the composer. |
| 3684 |
<P> |
| 3685 |
For Unix <EM>Alpine</EM> the program <EM>ispell</EM> works well as an |
| 3686 |
alternate spell checker. |
| 3687 |
If your Unix system has <EM>ispell</EM> it is probably reasonable to make |
| 3688 |
it the default speller by configuring it as the default in the |
| 3689 |
system configuration file, <CODE>/usr/local/lib/pine.conf</CODE>. |
| 3690 |
|
| 3691 |
<P> |
| 3692 |
If this option is not set, then the system's <EM>spell</EM> command is used. |
| 3693 |
The spell command does not work the same as the alternate speller. |
| 3694 |
It produces a list of misspelled words on its standard output, instead, |
| 3695 |
and doesn't take a tempfile as an argument. |
| 3696 |
Don't set this speller option to the standard Unix spell command. |
| 3697 |
That won't work. If you want to use the standard Unix spell command, |
| 3698 |
set the speller option to nothing. |
| 3699 |
|
| 3700 |
<DT> <A NAME="ssh-command"><EM>ssh-command</EM></A> |
| 3701 |
|
| 3702 |
<DD> Sets the format of the command used to |
| 3703 |
open a UNIX secure shell connection. The default is |
| 3704 |
"%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the |
| 3705 |
provided command. The first is for the command's pathname, the second is |
| 3706 |
for the host to connect to, the third is for the user to connect as, and |
| 3707 |
the fourth is for the connection method (typically <CODE>imap</CODE>). |
| 3708 |
<P> |
| 3709 |
|
| 3710 |
<DT> <A NAME="ssh-open-timeout"><EM>ssh-open-timeout</EM></A> |
| 3711 |
|
| 3712 |
<DD> Sets the time in seconds that <EM>Alpine</EM> will |
| 3713 |
attempt to open a UNIX secure shell connection. |
| 3714 |
The default is 15, the minimum non-zero value is 5, |
| 3715 |
and the maximum is unlimited. If this is set to zero ssh connections |
| 3716 |
will be completely disabled. |
| 3717 |
<P> |
| 3718 |
|
| 3719 |
<DT> <A NAME="ssh-path"><EM>ssh-path</EM></A> |
| 3720 |
|
| 3721 |
<DD> Sets the name of the command used to open a UNIX secure shell |
| 3722 |
connection. The default is typically <CODE>/usr/bin/ssh</CODE>. |
| 3723 |
<P> |
| 3724 |
|
| 3725 |
<DT> <A NAME="standard-printer"><EM>standard-printer</EM></A> |
| 3726 |
|
| 3727 |
<DD> System-wide configuration file only. Specifies a list of commands |
| 3728 |
for category 2 of the <EM>Setup/Printer</EM> screen, the standard print command |
| 3729 |
section. This is not used by <EM>PC-Alpine</EM>. |
| 3730 |
<P> |
| 3731 |
|
| 3732 |
<DT> <A NAME="status-background-color"><EM>status-background-color</EM></A> |
| 3733 |
<DT> <A NAME="status-foreground-color"><EM>status-foreground-color</EM></A> |
| 3734 |
|
| 3735 |
<DD> <A HREF="#status-color"><EM>Status Color</EM></A>. |
| 3736 |
<P> |
| 3737 |
|
| 3738 |
<DT> <A NAME="status-message-delay"><EM>status-message-delay</EM></A> |
| 3739 |
|
| 3740 |
<DD> This option has evolved over time, causing the possible values to be |
| 3741 |
counter-intuitive. |
| 3742 |
Read carefully before you set this option. |
| 3743 |
First we explain what the option does, then there is a longer discussion |
| 3744 |
following that. |
| 3745 |
<P> |
| 3746 |
If this is set to zero, the default value, it has <EM>no</EM> effect. |
| 3747 |
Positive and negative values serve two similar, but different purposes. |
| 3748 |
<P> |
| 3749 |
If it is set to a positive number, it causes the cursor to move to the |
| 3750 |
status line whenever a status message is printed and pause there for this |
| 3751 |
many seconds. |
| 3752 |
It will probably only be useful if the |
| 3753 |
<A HREF="#show-cursor"><EM>show-cursor</EM></A> |
| 3754 |
feature is |
| 3755 |
also turned on. |
| 3756 |
Setting this option to a positive number can only be used to |
| 3757 |
<EM>increase</EM> the status message delay. |
| 3758 |
This may be useful for Braille displays, or other non-traditional displays. |
| 3759 |
<P> |
| 3760 |
If it is set to a negative number the interpretation is a bit complicated. |
| 3761 |
Negative numbers are used to <EM>decrease</EM> the amount of delay <EM>Alpine</EM> uses to |
| 3762 |
allow you to read important status messages. |
| 3763 |
Of course, this may cause you to miss some important messages. |
| 3764 |
If you see a message flash by but miss what it says you can use the |
| 3765 |
Journal command from the Main menu to read it. |
| 3766 |
If you set this option to a negative value, the delay will be |
| 3767 |
no more than one second less than the absolute value |
| 3768 |
of the value you set. |
| 3769 |
So if you set it to -1, the delay will be no more than zero seconds, no |
| 3770 |
delay at all. |
| 3771 |
If you set it to -2, the delay will be no more than 1 second. |
| 3772 |
And so on, -3 is 2 seconds, -4 is 3 seconds, ... |
| 3773 |
If the delay that <EM>Alpine</EM> would have used by default is less than this delay, |
| 3774 |
then the smaller delay set by <EM>Alpine</EM> will be used. |
| 3775 |
Setting this option to a negative value can only reduce the amount of |
| 3776 |
delay, never increase it. |
| 3777 |
<P> |
| 3778 |
Here is a more detailed explanation. |
| 3779 |
Status messages are the messages which show up spontaneously in the |
| 3780 |
status message line, the third line from the bottom of the screen. |
| 3781 |
By default, <EM>Alpine</EM> assigns each status message it produces a minimum |
| 3782 |
display time. |
| 3783 |
Some status messages have a minimum display time of zero. |
| 3784 |
You can see an example of such a message by paging up in this help text |
| 3785 |
until you reach the top of the screen. |
| 3786 |
If you try to page past the top you will see the message |
| 3787 |
<P> |
| 3788 |
<CENTER><SAMP>[Already at start of help text]</SAMP></CENTER> |
| 3789 |
<P> |
| 3790 |
in the status line. |
| 3791 |
If there is another more important use of the status message line this message |
| 3792 |
might be replaced quickly, or it even might not be shown at all. |
| 3793 |
However, if there is no reason to get rid of the message, it might stay |
| 3794 |
there for several seconds while you read the help. |
| 3795 |
An example where it is replaced immediately happens when you page up in |
| 3796 |
the help text past the top of the screen, but then type the "WhereIs" |
| 3797 |
command right after paging up. |
| 3798 |
The message will disappear immediately without causing a delay (unless you |
| 3799 |
have set this option to a positive value) to allow you to type input for |
| 3800 |
the "WhereIs" command. |
| 3801 |
Since it isn't a very important message, <EM>Alpine</EM> has set its minimum display |
| 3802 |
time to zero seconds. |
| 3803 |
<P> |
| 3804 |
Other messages have minimum display times of three or more seconds. |
| 3805 |
These are usually error messages that <EM>Alpine</EM> thinks you ought to see. |
| 3806 |
For example, it might be a message about a failed Save or a failed folder open. |
| 3807 |
It is often the case that this minimum display time won't delay you in |
| 3808 |
any way because the status message line is not needed for another reason. |
| 3809 |
However, there are times when <EM>Alpine</EM> has to delay what it is doing in |
| 3810 |
order to display a status message for the minimum display time. |
| 3811 |
This happens when a message is being displayed and <EM>Alpine</EM> wants to ask |
| 3812 |
for input from the keyboard. |
| 3813 |
For example, when you Save a message you use the status message line. |
| 3814 |
You get a prompt there asking for the name of the folder to save to. |
| 3815 |
If there is a status message being displayed that has not |
| 3816 |
yet displayed for its minimum |
| 3817 |
time <EM>Alpine</EM> will display that status message surrounded with the characters |
| 3818 |
> and < to show you that it is delaying. |
| 3819 |
That might happen, for example, if you tried to save to a folder that |
| 3820 |
caused an error, then followed that immediately with another Save command. |
| 3821 |
You might find yourself waiting for a status message like |
| 3822 |
<P> |
| 3823 |
<CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER> |
| 3824 |
<P> |
| 3825 |
to finish displaying for three seconds. |
| 3826 |
If that is something you find happening to you frequently, you may use |
| 3827 |
negative values of this option to decrease or eliminate that delay, at |
| 3828 |
the risk of missing the message. |
| 3829 |
<P> |
| 3830 |
|
| 3831 |
<DT> <A NAME="stay-open-folders"><EM>stay-open-folders</EM></A> |
| 3832 |
|
| 3833 |
<DD> This option affects low-level behavior of <EM>Alpine</EM>. |
| 3834 |
There is no default value for this option. |
| 3835 |
It is related to the options |
| 3836 |
<A HREF="#preopen-stayopen-folders">Preopen-Stayopen-Folders</A>, |
| 3837 |
<A HREF="#max-remote-connections">Max-Remote-Connections</A>, |
| 3838 |
and <A HREF="#offer-expunge-of-stayopen-folders">offer-expunge-of-Stayopen-Folders</A>. |
| 3839 |
|
| 3840 |
<P> |
| 3841 |
Note: changes made to this list take effect the next time you open a |
| 3842 |
folder in the list. |
| 3843 |
|
| 3844 |
<P> |
| 3845 |
This is a list of folders that will be permanently kept open once they |
| 3846 |
are first opened. |
| 3847 |
The names in this list may be either the nickname of an Incoming folder |
| 3848 |
or the full technical specification of a folder. |
| 3849 |
The folders in this list need not be remote IMAP folders, they could usefully |
| 3850 |
be local folders, as well. |
| 3851 |
If a folder in the list is a newsgroup or is not accessed either locally |
| 3852 |
or via IMAP, then the entry will be ignored. |
| 3853 |
For example, folders accessed via NNTP or POP3 will not be kept open, since |
| 3854 |
the way that new mail is found with those protocols involves closing and |
| 3855 |
reopening the connection. |
| 3856 |
<P> |
| 3857 |
Once a Stay Open folder has been opened, new-mail checking will continue |
| 3858 |
to happen on that folder for the rest of the <EM>Alpine</EM> session. |
| 3859 |
Your INBOX is always implicitly included in this Stay-Open list and doesn't |
| 3860 |
need to be added explicitly. |
| 3861 |
<P> |
| 3862 |
Another difference that you may notice between a Stay Open folder and a |
| 3863 |
non-Stay Open folder is which message is selected as the current message |
| 3864 |
when you enter the folder index. |
| 3865 |
Normally, the starting position for an incoming folder (which most Stay Open |
| 3866 |
folders will likely be) is controlled by the |
| 3867 |
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>. |
| 3868 |
However, if a folder is a Stay Open folder, when you re-enter the folder |
| 3869 |
after the first time the current message will be the same as it was when |
| 3870 |
you left the folder. |
| 3871 |
An exception is made if you use the TAB command to get to the folder. |
| 3872 |
In that case, the message number will be incremented by one from what it |
| 3873 |
was when you left the folder. |
| 3874 |
<P> |
| 3875 |
The above special behavior is thought to be useful. |
| 3876 |
However, it is special and different from what you might at first expect. |
| 3877 |
The feature |
| 3878 |
<A HREF="#use-reg-start-rule"><EM>Use-Regular-Startup-Rule-for-Stayopen-Folders</EM></A> |
| 3879 |
may be used to turn off this special treatment. |
| 3880 |
<P> |
| 3881 |
If the message that was current when you left the folder no longer exists, |
| 3882 |
then the regular startup rule will be used instead. |
| 3883 |
<P> |
| 3884 |
This option is displayed as "Stayopen Folders". |
| 3885 |
<P> |
| 3886 |
|
| 3887 |
<DT> <A NAME="tcp-open-timeout"><EM>tcp-open-timeout</EM></A> |
| 3888 |
|
| 3889 |
<DD> Sets the time in seconds that <EM>Alpine</EM> will |
| 3890 |
attempt to open a network connection. The default is 30, the minimum is 5, |
| 3891 |
and the maximum is system defined (typically 75). If a connection has not |
| 3892 |
completed within this many seconds <EM>Alpine</EM> will give up and consider it a |
| 3893 |
failed connection. |
| 3894 |
<P> |
| 3895 |
|
| 3896 |
<DT> <A NAME="tcp-query-timeout"><EM>tcp-query-timeout</EM></A> |
| 3897 |
|
| 3898 |
<DD> When <EM>Alpine</EM> times out a network read or write it will normally just display |
| 3899 |
a message saying "Still waiting". |
| 3900 |
However, if enough time has elapsed since it started waiting it will offer |
| 3901 |
to let you break the connection. |
| 3902 |
That amount of time is set by this option, which defaults to 60 seconds, |
| 3903 |
has a minimum of 5 seconds, and a maximum of 1000 seconds. |
| 3904 |
<P> |
| 3905 |
|
| 3906 |
<DT> <A NAME="tcp-read-warning-timeout"><EM>tcp-read-warning-timeout</EM></A> |
| 3907 |
|
| 3908 |
<DD> Sets the time in seconds that <EM>Alpine</EM> will |
| 3909 |
wait for a network read before warning you that things are moving slowly |
| 3910 |
and possibly giving you the option to break the connection. |
| 3911 |
The default is 15 seconds. The minimum is 5 seconds and the maximumn is |
| 3912 |
1000 seconds. |
| 3913 |
<P> |
| 3914 |
|
| 3915 |
<DT> <A NAME="tcp-write-warning-timeout"><EM>tcp-write-warning-timeout</EM></A> |
| 3916 |
|
| 3917 |
<DD> Sets the time in seconds that <EM>Alpine</EM> will |
| 3918 |
wait for a network write before warning you that things are moving slowly |
| 3919 |
and possibly giving you the option to break the connection. |
| 3920 |
The default is 0 which means it is unset. If set to a non-zero value, the |
| 3921 |
minimum is 5 and the maximum is 1000. |
| 3922 |
|
| 3923 |
<DT> <A NAME="threading-display-style"><EM>threading-display-style</EM></A> |
| 3924 |
|
| 3925 |
<DD> When a folder is sorted by Threads or OrderedSubject, |
| 3926 |
this option will affect the MESSAGE INDEX display. |
| 3927 |
By default, <EM>Alpine</EM> will display the MESSAGE INDEX in the |
| 3928 |
"show-thread-structure" style if a folder is sorted |
| 3929 |
by Threads or OrderedSubject. |
| 3930 |
The possible values are: |
| 3931 |
<P> |
| 3932 |
|
| 3933 |
<DL> |
| 3934 |
<DT><EM>none</EM></DT> |
| 3935 |
<DD>Regular index display. |
| 3936 |
The same index line as would be displayed without threading is used. |
| 3937 |
The only difference will be in the order of the messages. |
| 3938 |
</DD> |
| 3939 |
|
| 3940 |
<DT><EM>show-thread-structure</EM></DT> |
| 3941 |
<DD>Threaded Subjects will be indented and vertical bars and horizontal |
| 3942 |
lines will be added to make it easier to see the relationships among |
| 3943 |
the messages in a thread (a conversation). |
| 3944 |
</DD> |
| 3945 |
|
| 3946 |
<DT><EM>mutt-like</EM></DT> |
| 3947 |
<DD>This is the same as the option above except that the Subject |
| 3948 |
is suppressed (is blank) if it matches the previous Subject in the thread. |
| 3949 |
The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>. |
| 3950 |
Here is an example of what a mutt-like index might look like. |
| 3951 |
In this example, the first column represents the message number, the |
| 3952 |
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A> |
| 3953 |
is set to "regular-index-with-expanded-threads", and the |
| 3954 |
<A HREF="#threading-lastreply-character"><EM>Threading-Lastreply-Character</EM></A> |
| 3955 |
is set to a backslash: |
| 3956 |
<PRE> |
| 3957 |
1 Some topic |
| 3958 |
2 . Subject original message in thread |
| 3959 |
3 |-> reply to 2 |
| 3960 |
4 . |-> another reply to 2 |
| 3961 |
5 . | \-> reply to 4 |
| 3962 |
6 . | \-> reply to 5 |
| 3963 |
7 | \-> reply to 6 |
| 3964 |
8 |-> another reply to 2 |
| 3965 |
9 . |->New subject another reply to 2 but with a New subject |
| 3966 |
10 | |-> reply to 9 |
| 3967 |
11 | \-> another reply to 9 |
| 3968 |
12 | \-> reply to 11 |
| 3969 |
13 \-> final reply to 2 |
| 3970 |
14 Next topic |
| 3971 |
</PRE> |
| 3972 |
</DD> |
| 3973 |
|
| 3974 |
<DT><EM>indent-subject-1</EM></DT> |
| 3975 |
<DD>Threaded Subjects will be indented one space per level of the conversation. |
| 3976 |
The bars and lines that show up in the show-thread-structure display will |
| 3977 |
not be there with this style. |
| 3978 |
</DD> |
| 3979 |
|
| 3980 |
<DT><EM>indent-subject-2</EM></DT> |
| 3981 |
<DD>Same as above but indent two spaces per level instead of one space. |
| 3982 |
</DD> |
| 3983 |
|
| 3984 |
<DT><EM>indent-from-1</EM></DT> |
| 3985 |
<DD>Similar to indent-subject-1, except that instead of indenting the |
| 3986 |
Subject field one space the From field of a thread will be indented one |
| 3987 |
space per level of the conversation. |
| 3988 |
</DD> |
| 3989 |
|
| 3990 |
<DT><EM>indent-from-2</EM></DT> |
| 3991 |
<DD>Same as above but indent two spaces per level instead of one space. |
| 3992 |
</DD> |
| 3993 |
|
| 3994 |
<DT><EM>show-structure-in-from</EM></DT> |
| 3995 |
<DD>The structure of the thread is illustrated with indenting, vertical bars, |
| 3996 |
and horizontal lines just like with the show-thread-structure option, but |
| 3997 |
the From field is used to show the relationships instead of the Subject field. |
| 3998 |
</DD> |
| 3999 |
|
| 4000 |
</DL> |
| 4001 |
<P> |
| 4002 |
|
| 4003 |
<DT> <A NAME="threading-expanded-character"><EM>threading-expanded-character</EM></A> |
| 4004 |
|
| 4005 |
<DD> The Threading-Expanded-Character option has a small effect on the MESSAGE |
| 4006 |
INDEX display when using a |
| 4007 |
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A> |
| 4008 |
other than <EM>none</EM>. |
| 4009 |
The value of this option is a single character. |
| 4010 |
This character is used to indicate that part of a thread has been expanded |
| 4011 |
and could be collapsed if desired with |
| 4012 |
the "/" Collapse/Expand command. |
| 4013 |
By default, the value of this option is a dot (.). |
| 4014 |
<P> |
| 4015 |
If this option is set to the Empty Value, then the column (and the following |
| 4016 |
blank column) will be deleted from the display. |
| 4017 |
<P> |
| 4018 |
This option is closely related to the |
| 4019 |
<A HREF="#threading-indicator-character"><EM>threading-indicator-character</EM></A> |
| 4020 |
option. |
| 4021 |
Another similar option which affects the thread display is the |
| 4022 |
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option. |
| 4023 |
|
| 4024 |
<DT> <A NAME="threading-index-style"><EM>threading-index-style</EM></A> |
| 4025 |
|
| 4026 |
<DD> When a folder is sorted by Threads or OrderedSubject, |
| 4027 |
this option will affect the INDEX displays. |
| 4028 |
The possible values are: |
| 4029 |
<P> |
| 4030 |
|
| 4031 |
<DL> |
| 4032 |
<DT><EM>regular-index-with-expanded-threads</EM></DT> |
| 4033 |
<DD>This is the default display. |
| 4034 |
If the configuration option |
| 4035 |
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A> |
| 4036 |
is set to something other than "none", then this setting |
| 4037 |
will cause <EM>Alpine</EM> to start off with a MESSAGE INDEX with all of |
| 4038 |
the threads expanded. |
| 4039 |
That is, each message will have a line in the MESSAGE INDEX display. |
| 4040 |
The Collapse/Expand command (/) may be used to manually collapse or |
| 4041 |
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>). |
| 4042 |
<P> |
| 4043 |
This setting affects the display when the folder is first threaded. |
| 4044 |
The collapsed state may also be re-initialized by re-sorting the folder manually |
| 4045 |
using the SortIndex command ($). |
| 4046 |
After re-sorting the threads will once again all be expanded, even if you |
| 4047 |
have previously collapsed some of them. |
| 4048 |
<P> |
| 4049 |
If "threading-display-style" is set to "none", then |
| 4050 |
the display will be the regular default <EM>Alpine</EM> MESSAGE INDEX, but sorted |
| 4051 |
in a different order. |
| 4052 |
</DD> |
| 4053 |
|
| 4054 |
<DT><EM>regular-index-with-collapsed-threads</EM></DT> |
| 4055 |
<DD>If the configuration option |
| 4056 |
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A> |
| 4057 |
is set to something other than "none", then this setting |
| 4058 |
will cause <EM>Alpine</EM> to start out with all of the threads collapsed instead of |
| 4059 |
starting out with all of the threads expanded. |
| 4060 |
The Collapse/Expand command (/) may be used to manually collapse or |
| 4061 |
expand a thread or subthread (see also <A HREF="#slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A>). |
| 4062 |
<P> |
| 4063 |
This setting affects the display when the folder is first threaded. |
| 4064 |
The collapsed state may also be re-initialized by re-sorting the folder manually |
| 4065 |
using the SortIndex command ($). |
| 4066 |
After re-sorting the threads will once again all be collapsed, even if you |
| 4067 |
have previously expanded some of them. |
| 4068 |
</DD> |
| 4069 |
|
| 4070 |
<DT><EM>separate-index-screen-always</EM></DT> |
| 4071 |
<DD>With this setting and the next, you will see an index of threads |
| 4072 |
instead of an |
| 4073 |
index of messages, provided you have sorted by Threads or OrderedSubject. |
| 4074 |
<P> |
| 4075 |
The THREAD INDEX contains a '*' in the first column if any message in the thread |
| 4076 |
is marked Important. |
| 4077 |
If not, it contains a '+' if any message in the thread is to you. |
| 4078 |
The second column is blank. The third column contains a 'D' if all of the |
| 4079 |
messages in the thread are deleted. |
| 4080 |
Otherwise, it contains an 'N' if any of the messages in the thread are New. |
| 4081 |
<P> |
| 4082 |
When you view a particular thread from the THREAD INDEX you will be |
| 4083 |
in the MESSAGE INDEX display |
| 4084 |
but the index will only contain messages from the thread you are viewing. |
| 4085 |
</DD> |
| 4086 |
|
| 4087 |
<DT><EM>separate-index-screen-except-for-single-messages</EM></DT> |
| 4088 |
<DD>This is very similar to the option above. |
| 4089 |
When you are in the THREAD INDEX, one of the available commands |
| 4090 |
is "ViewThd". |
| 4091 |
With the setting "separate-index-screen-always" (the option above) |
| 4092 |
when you view a particular thread you will be in the |
| 4093 |
MESSAGE INDEX display and the index will only contain messages from |
| 4094 |
the thread you are viewing. |
| 4095 |
If the thread you are viewing consists of a single message, the MESSAGE INDEX |
| 4096 |
will be an index with only one message in it. |
| 4097 |
If you use this "separate-index-screen-except-for-single-messages" |
| 4098 |
setting instead, then that index which contains a single message |
| 4099 |
will be skipped and you will go directly from the THREAD INDEX into the |
| 4100 |
MESSAGE TEXT screen. |
| 4101 |
</DD> |
| 4102 |
|
| 4103 |
</DL> |
| 4104 |
|
| 4105 |
<P> |
| 4106 |
|
| 4107 |
<DT> <A NAME="threading-indicator-character"><EM>threading-indicator-character</EM></A> |
| 4108 |
|
| 4109 |
<DD> The Threading-Indicator-Character option has a small effect on the MESSAGE |
| 4110 |
INDEX display when using a |
| 4111 |
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A> |
| 4112 |
other than <EM>none</EM> and sorting by Threads or OrderedSubject. |
| 4113 |
The value of this option is a single character. |
| 4114 |
This character is used to indicate that part of a thread (a conversation) is |
| 4115 |
hidden beneath a message. |
| 4116 |
The message could be expanded |
| 4117 |
if desired with the "/" Collapse/Expand command. |
| 4118 |
By default, the value of this option is the greater than sign (>). |
| 4119 |
<P> |
| 4120 |
If this option is set to the Empty Value, then the column (and the following |
| 4121 |
blank column) will be deleted from the display. |
| 4122 |
|
| 4123 |
<P> |
| 4124 |
This option is closely related to the |
| 4125 |
<A HREF="#threading-expanded-character"><EM>threading-expanded-character</EM></A> |
| 4126 |
option. |
| 4127 |
Another similar option which affects the thread display is the |
| 4128 |
<A HREF="#threading-lastreply-character"><EM>threading-lastreply-character</EM></A> option. |
| 4129 |
<P> |
| 4130 |
|
| 4131 |
<DT> <A NAME="threading-lastreply-character"><EM>threading-lastreply-character</EM></A> |
| 4132 |
|
| 4133 |
<DD>The Threading-Lastreply-Character option has a small effect on the MESSAGE |
| 4134 |
INDEX display when using a |
| 4135 |
<A HREF="#threading-display-style"><EM>threading-display-style</EM></A> |
| 4136 |
of <EM>show-thread-structure</EM>, <EM>mutt-like</EM>, or |
| 4137 |
<EM>show-structure-in-from</EM>; and sorting by Threads or OrderedSubject. |
| 4138 |
The value of this option is a single character. |
| 4139 |
This character is used instead of the vertical line character when there are |
| 4140 |
no more replies directly to the parent of the current message. |
| 4141 |
It can be used to "round-off" the bottom of the vertical line |
| 4142 |
by setting it to a character such as a backslash (\) or |
| 4143 |
a backquote (`). |
| 4144 |
The default value of this option is the backslash character (\). |
| 4145 |
This option may not be set to the Empty Value. |
| 4146 |
In that case, the default will be used instead. |
| 4147 |
<P> |
| 4148 |
This option is displayed as "Threading Last Reply Character". |
| 4149 |
<P> |
| 4150 |
|
| 4151 |
<DT> <A NAME="title-background-color"><EM>title-background-color</EM></A> |
| 4152 |
<DT> <A NAME="title-foreground-color"><EM>title-foreground-color</EM></A> |
| 4153 |
|
| 4154 |
<DD> <A HREF="#title-color"><EM>Title Color</EM></A>. |
| 4155 |
<P> |
| 4156 |
|
| 4157 |
<DT> <A NAME="title-closed-background-color"><EM>title-closed-background-color</EM></A> |
| 4158 |
<DT> <A NAME="title-closed-foreground-color"><EM>title-closed-foreground-color</EM></A> |
| 4159 |
|
| 4160 |
<DD> <A HREF="#title-closed-color"><EM>Title-closed Color</EM></A>. |
| 4161 |
<P> |
| 4162 |
|
| 4163 |
<DT> <A NAME="titlebar-color-style"><EM>titlebar-color-style</EM></A> |
| 4164 |
|
| 4165 |
<DD> <A HREF="#titlebar-style"><EM>titlebar-color-style</EM></A>. |
| 4166 |
<P> |
| 4167 |
|
| 4168 |
<DT> <A NAME="unknown-character-set"><EM>unknown-character-set</EM></A> |
| 4169 |
|
| 4170 |
<DD> A text message should either be made up of all US-ASCII characters |
| 4171 |
or it should contain a charset label which tells the software which |
| 4172 |
character set encoding to use to interpret the message. |
| 4173 |
Sometimes a malformed message may be unlabeled but contain non-ascii text. |
| 4174 |
This message is outside of the standards so any attempt to read it could fail. |
| 4175 |
When <EM>Alpine</EM> attempts to read such a message it will try to interpret the |
| 4176 |
text in the character set you specify here. |
| 4177 |
For example, if you have correspondents who send you unlabeled messages that |
| 4178 |
are usually made up of characters from the WINDOWS-1251 character set, setting |
| 4179 |
this unknown-character-set to <CODE>WINDOWS-1251</CODE> will |
| 4180 |
allow you to read those messages. |
| 4181 |
Of course, if the unlabeled message is actually in some other character set, |
| 4182 |
then you may see garbage on your screen. |
| 4183 |
|
| 4184 |
<P> |
| 4185 |
In the Setup/Config screen you may choose from a list of all the |
| 4186 |
character sets <EM>Alpine</EM> knows about by using the "T" ToCharsets command. |
| 4187 |
<P> |
| 4188 |
|
| 4189 |
<DT> <A NAME="upload-command"><EM>upload-command</EM></A> |
| 4190 |
|
| 4191 |
<DD> This option affects the behavior of the Composer's <EM>^R</EM> (Read File) |
| 4192 |
and <EM>^J</EM> (Attach File, in the header) commands. It |
| 4193 |
specifies a Unix program name, and any necessary command line arguments, |
| 4194 |
that <EM>Alpine</EM> can use to transfer files from your personal computer into |
| 4195 |
messages that you are composing. <P> |
| 4196 |
|
| 4197 |
<DT> <A NAME="upload-command-prefix"><EM>upload-command-prefix</EM></A> |
| 4198 |
|
| 4199 |
<DD> This option is used in |
| 4200 |
conjunction with the <EM>upload-command</EM> option. |
| 4201 |
It defines text to be written to the terminal emulator (via standard |
| 4202 |
output) immediately prior to starting the upload command. This is useful for |
| 4203 |
integrated serial line file transfer agents that permit command passing |
| 4204 |
(e.g., Kermit's APC method). <P> |
| 4205 |
|
| 4206 |
<DT> <A NAME="url-viewers"><EM>url-viewers</EM></A> |
| 4207 |
|
| 4208 |
<DD> List of programs to use to open Internet URLs. |
| 4209 |
This value affects <EM>Alpine</EM>'s handling of URLs that are found in the text of |
| 4210 |
messages you read. Normally, only URLs <EM>Alpine</EM> can handle directly are |
| 4211 |
automatically offered for selection in the "Message Text" screen. When |
| 4212 |
one or more comma delimited Web browsers capable of deciphering URLs on |
| 4213 |
their command line are added here, <EM>Alpine</EM> will choose the first available |
| 4214 |
browser to display URLs it doesn't recognize. |
| 4215 |
<P> |
| 4216 |
|
| 4217 |
Additionally, to support various connection methods and browsers, each |
| 4218 |
entry in this list can begin with the special token |
| 4219 |
<CODE>_TEST(test-string)_</CODE>. |
| 4220 |
The <CODE>test-string</CODE> is a shell command that <EM>Alpine</EM> |
| 4221 |
will run and which must exit with a status of zero for <EM>Alpine</EM> to consider |
| 4222 |
that browser for use (the other criteria is that the browser must exist |
| 4223 |
as a full path or a path relative to your home directory). |
| 4224 |
<P> |
| 4225 |
|
| 4226 |
Now for an example: |
| 4227 |
|
| 4228 |
<BLOCKQUOTE> |
| 4229 |
<CODE> |
| 4230 |
url-viewers=_TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape, |
| 4231 |
/usr/local/bin/lynx, |
| 4232 |
C:\BIN\NETSCAPE.BAT </CODE><BR> |
| 4233 |
</BLOCKQUOTE> |
| 4234 |
|
| 4235 |
This example shows that for the first browser in the list to be used the |
| 4236 |
environment variable <CODE>DISPLAY</CODE> must be defined. |
| 4237 |
If it is, then the file <CODE>/usr/local/bin/netscape</CODE> must exist. |
| 4238 |
If either condition is not met, then the file |
| 4239 |
<CODE>/usr/local/bin/lynx</CODE> must exist. |
| 4240 |
If it doesn't, then the final path and file must |
| 4241 |
exist. Note that the last entry is a DOS/Windows path. This is one way |
| 4242 |
to support <EM>Alpine</EM> running on more than one architecture with the same |
| 4243 |
configuration file. |
| 4244 |
<P> |
| 4245 |
|
| 4246 |
<DT> <A NAME="use-only"><EM>use-only-domain-name</EM></A> |
| 4247 |
|
| 4248 |
<DD> Can be set to <EM>yes</EM> or <EM>no.</EM> Anything but |
| 4249 |
<EM>yes</EM> means <EM>no.</EM> If set to <EM>yes</EM> the first label in |
| 4250 |
the host name will be lopped off to get the domain name and the domain |
| 4251 |
name will be used for outgoing mail and such. That is, if the host name |
| 4252 |
is <EM>carson.u.example.edu</EM> and this variable is set to <EM>yes,</EM> |
| 4253 |
then <EM>u.example.edu</EM> will be used on outgoing mail. Only |
| 4254 |
meaningful if <A HREF="#user-domain"><EM>user-domain</EM></A> is NOT set. <P> |
| 4255 |
|
| 4256 |
<DT> <A NAME="user-domain"><EM>user-domain</EM></A> |
| 4257 |
|
| 4258 |
<DD> Sets the domain or host name for the user, overriding the system host |
| 4259 |
or domain name. See the <A HREF="config-notes.html#domain"><EM>domain name section</EM></A>. |
| 4260 |
The easiest way to change the full From address is with the |
| 4261 |
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable. |
| 4262 |
<P> |
| 4263 |
|
| 4264 |
<DT> <A NAME="user-id"><EM>user-id</EM></A> |
| 4265 |
|
| 4266 |
<DD> <EM>PC-Alpine</EM> only and personal configuration file only. |
| 4267 |
Sets the username that is placed on all outgoing |
| 4268 |
messages. The username is the part of the address that comes before the "@". |
| 4269 |
The easiest way to change the full From address is with the |
| 4270 |
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> variable. |
| 4271 |
<P> |
| 4272 |
|
| 4273 |
<DT> <A NAME="user-input"><EM>user-input-timeout</EM></A> |
| 4274 |
|
| 4275 |
<DD> If this is set to an integer greater than zero, then this is the number |
| 4276 |
of <EM>hours</EM> to wait for user input before <EM>Alpine</EM> times out. |
| 4277 |
If <EM>Alpine</EM> is |
| 4278 |
in the midst of composing a message or is waiting for user response to |
| 4279 |
a question, then it will not timeout. |
| 4280 |
However, if <EM>Alpine</EM> is sitting idle waiting for |
| 4281 |
the user to tell it what to do next and the user does not give any |
| 4282 |
input for this many hours, <EM>Alpine</EM> will exit. |
| 4283 |
No expunging or moving of read |
| 4284 |
messages will take place. |
| 4285 |
It will exit similarly to the way it would exit |
| 4286 |
if it received a hangup signal. |
| 4287 |
This may be useful for cleaning up unused <EM>Alpine</EM> sessions which have been |
| 4288 |
forgotten by their owners. |
| 4289 |
The <EM>Alpine</EM> developers envision system administrators |
| 4290 |
setting this to a value of several hours (24?) so that it won't surprise |
| 4291 |
a user who didn't want to be disconnected. |
| 4292 |
<P> |
| 4293 |
|
| 4294 |
<DT> <A NAME="viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A> |
| 4295 |
|
| 4296 |
<DD> This variable holds the optional Header Colors and patterns which |
| 4297 |
have been defined by the user. This is usually modified by using |
| 4298 |
the <A HREF="#header-colors"><EM>Header Colors</EM></A> section |
| 4299 |
of the Setup Color screen. |
| 4300 |
<P> |
| 4301 |
|
| 4302 |
<DT> <A NAME="viewer-hdrs"><EM>viewer-hdrs</EM></A> |
| 4303 |
|
| 4304 |
<DD> You may change the default list of headers that are viewed by listing |
| 4305 |
the headers you want to view here. If the headers in your <EM>viewer-hdrs</EM> |
| 4306 |
list are present in the message, then they will be shown. The order of |
| 4307 |
the headers you list will also be honored. If the special |
| 4308 |
value <EM>all-except</EM> |
| 4309 |
is included as the first header in the <EM>viewer-hdrs</EM> list, then all |
| 4310 |
headers in the message except those in the list will be shown. The values |
| 4311 |
are all case insensitive.<P> |
| 4312 |
This option is displayed as "Viewer Headers". |
| 4313 |
<P> |
| 4314 |
|
| 4315 |
<DT> <A NAME="viewer-margin-left"><EM>viewer-margin-left</EM></A> |
| 4316 |
|
| 4317 |
<DD> This variable controls the left-hand vertical margin's width in |
| 4318 |
<EM>Alpine</EM>'s Message Viewing screen. |
| 4319 |
Its value is the number of space characters preceding each displayed line. |
| 4320 |
For consistency with |
| 4321 |
<A HREF="#viewer-margin-right">Viewer-Margin-Right</A>, |
| 4322 |
you may specify the column number to start in |
| 4323 |
(column numbering begins with number 1) |
| 4324 |
instead of the width of the margin by appending a lower case letter |
| 4325 |
"c" to the number. |
| 4326 |
For example, a value of "2c" means to start the text in column two, |
| 4327 |
which is entirely equivalent to a value of "1", which means to |
| 4328 |
leave a margin of 1 space. |
| 4329 |
<P> |
| 4330 |
The default is a left margin of 0 (zero). |
| 4331 |
Misconfigurations (for example, negative values or values with starting |
| 4332 |
left columns greater than the ending right column) |
| 4333 |
are silently ignored. |
| 4334 |
If the number of columns for text between the Viewer-Margin-Left and |
| 4335 |
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used |
| 4336 |
instead. |
| 4337 |
<P> |
| 4338 |
|
| 4339 |
<DT> <A NAME="viewer-margin-right"><EM>viewer-margin-right</EM></A> |
| 4340 |
|
| 4341 |
<DD> This variable controls the right-hand vertical margin's width in |
| 4342 |
<EM>Alpine</EM>'s Message Viewing screen. |
| 4343 |
Its value is the number of space characters following each displayed line. |
| 4344 |
You may specify the column number to end the text in |
| 4345 |
(column numbering begins with number 1) |
| 4346 |
instead of the width of the margin by appending a lower case letter |
| 4347 |
"c" to the number. |
| 4348 |
For example, a value of "76c" means to end the text in column 76. |
| 4349 |
If the screen is 80 characters wide, this is equivalent to a value |
| 4350 |
of "4", which means to leave a margin of 4 spaces. |
| 4351 |
However, if you use different size screens at different times, then these |
| 4352 |
two values are not equivalent. |
| 4353 |
<P> |
| 4354 |
The default right margin is 4. |
| 4355 |
Misconfigurations (for example, negative values or values with starting |
| 4356 |
left columns greater than the ending right column) |
| 4357 |
are silently ignored. |
| 4358 |
If the number of columns for text between the |
| 4359 |
<A HREF="#viewer-margin-left">Viewer-Margin-Left</A> and |
| 4360 |
the Viewer-Margin-Right is fewer than 8, then margins of zero will be used |
| 4361 |
instead. |
| 4362 |
<P> |
| 4363 |
|
| 4364 |
<DT> <A NAME="overlap"><EM>viewer-overlap</EM></A> |
| 4365 |
|
| 4366 |
<DD> This option specifies an aspect of <EM>Alpine</EM>'s Message Viewing screen. |
| 4367 |
When the space bar is used to page forward in a message, the number of |
| 4368 |
lines specified by the <EM>viewer-overlap</EM> variable |
| 4369 |
will be repeated from the |
| 4370 |
bottom of the screen. That is, if this was set to two lines, then the |
| 4371 |
bottom two lines of the screen would be repeated on the top of the next |
| 4372 |
screen. The normal default value is "2". <P> |
| 4373 |
|
| 4374 |
<DT> <A NAME="window-position"><EM>window-position</EM></A> |
| 4375 |
|
| 4376 |
<DD> Winsock version of <EM>PC-Alpine</EM> only. Window position in the format: |
| 4377 |
CxR+X+Yn Where C and R are the window size in characters and X and Y are |
| 4378 |
the screen position of the top left corner of the window. <P> |
| 4379 |
|
| 4380 |
</DL> |
| 4381 |
|
| 4382 |
<HR> |
| 4383 |
|
| 4384 |
<H2><A NAME="features-conf">Configuration Features</A></H2> |
| 4385 |
|
| 4386 |
There are several features (options) which may be turned off or on. |
| 4387 |
The configuration variable |
| 4388 |
<A HREF="#feat-list"><EM>feature-list</EM></A> is a list of all the |
| 4389 |
features that are turned on or off. |
| 4390 |
If the name of a feature is in |
| 4391 |
the list it will be turned on. |
| 4392 |
If the name of a feature with the characters |
| 4393 |
<CODE>no-</CODE> prepended is in the list, it will turn the feature off. |
| 4394 |
This is useful for overriding system-wide defaults. |
| 4395 |
This is because, unlike all the other configuration variables, |
| 4396 |
the <EM>feature-list</EM> is additive. |
| 4397 |
That is, first the system-wide <EM>feature-list</EM> is read |
| 4398 |
and then the user's <EM>feature-list</EM> is read. This makes it possible |
| 4399 |
for the system manager to turn some of the features on by default while |
| 4400 |
still allowing the user to cancel that default. |
| 4401 |
For example, if the system manager has |
| 4402 |
turned on the <EM>allow-talk</EM> feature by default then a user may turn |
| 4403 |
it back off by including the feature <EM>no-allow-talk</EM> in his or her |
| 4404 |
personal configuration file. Of course, these details are usually handled |
| 4405 |
by <EM>Alpine</EM> when the user turns an option on or off from inside the |
| 4406 |
<EM>Setup/Config</EM> screen. |
| 4407 |
<P> |
| 4408 |
|
| 4409 |
System managers should take some care when turning on features by default. |
| 4410 |
Some of the documentation assumes that all of the features are off by |
| 4411 |
default, so it could be confusing for a user if some are on by default instead. |
| 4412 |
Feature names are case-independent. |
| 4413 |
<P> |
| 4414 |
|
| 4415 |
Here is an alphabetical list of possible features. |
| 4416 |
|
| 4417 |
<DL COMPACT> |
| 4418 |
|
| 4419 |
<DT> <A NAME="allow-from"><EM>allow-changing-from</EM></A> |
| 4420 |
|
| 4421 |
<DD> Prior to <EM>Pine</EM> 4.00 there was a <EM>compile</EM>-time option called |
| 4422 |
ALLOW_CHANGING_FROM. That has been replaced by a <EM>runtime</EM> feature. |
| 4423 |
If this feature is turned on then the From line can be changed just like |
| 4424 |
all the other header fields that can be changed. See the configuration |
| 4425 |
variables <A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> |
| 4426 |
and <A HREF="#def-comp"><EM>default-composer-hdrs</EM></A> |
| 4427 |
for more information on editing headers. |
| 4428 |
<P> |
| 4429 |
The default value for this feature |
| 4430 |
is ON, so that editing of From headers is allowed |
| 4431 |
by default. |
| 4432 |
<P> |
| 4433 |
|
| 4434 |
<DT> <A NAME="allow-talk"><EM>allow-talk</EM></A> |
| 4435 |
|
| 4436 |
<DD> Unix <EM>Alpine</EM> only. By default, permission for |
| 4437 |
others to <EM>talk</EM> to your terminal is turned |
| 4438 |
off when you are running <EM>Alpine</EM>. When this feature is set, permission is |
| 4439 |
instead turned on. |
| 4440 |
<P> |
| 4441 |
|
| 4442 |
Note: The <EM>talk</EM> program has nothing to do with <EM>Alpine</EM> or email. The |
| 4443 |
<EM>talk</EM> daemon on your system will |
| 4444 |
attempt to print a message on your screen |
| 4445 |
when someone else is trying to contact you. If you wish to see these |
| 4446 |
messages while you are running <EM>Alpine</EM>, you should enable this feature. |
| 4447 |
<P> |
| 4448 |
|
| 4449 |
If you do enable this feature and see a <EM>talk</EM> message, you must |
| 4450 |
suspend or quit <EM>Alpine</EM> before you can respond. |
| 4451 |
<P> |
| 4452 |
|
| 4453 |
<DT> <A NAME="alternate-compose-menu"><EM>alternate-compose-menu</EM></A> |
| 4454 |
|
| 4455 |
<DD>This feature controls the menu that is displayed when Compose is selected. |
| 4456 |
If set, a list of options will be presented, with each option representing |
| 4457 |
the type of composition that could be used. This feature is most useful for |
| 4458 |
users who want to avoid being prompted with each option separately, or who |
| 4459 |
want to avoid the checking of remote postponed or form letter folders. |
| 4460 |
The possible types of composition are: |
| 4461 |
|
| 4462 |
<P> |
| 4463 |
New, for starting a new composition. Note that if New is selected and roles |
| 4464 |
are set, roles are checked for matches and applied according to the setting |
| 4465 |
of the matching role. |
| 4466 |
|
| 4467 |
<P> |
| 4468 |
Interrupted, for continuing an interrupted composition. This option is only |
| 4469 |
offered if an interrupted message folder is detected. |
| 4470 |
|
| 4471 |
<P> |
| 4472 |
Postponed, for continuing postponed compositions. This option is offered |
| 4473 |
if a postponed-folder is set in the config <EM>REGARDLESS OF</EM> whether or not |
| 4474 |
the postponed folder actually exists. This option is especially handy |
| 4475 |
for avoiding having to check for the existence of a remote postponed folder. |
| 4476 |
|
| 4477 |
<P> |
| 4478 |
Form, for using form letters. This option is offered if the form-letter-folder |
| 4479 |
is set in the config, and is not checked for existence for reasons similar |
| 4480 |
to those explained by the postponed option. |
| 4481 |
|
| 4482 |
<P> |
| 4483 |
setRole, for selecting a role to apply to a composition. |
| 4484 |
|
| 4485 |
<P> |
| 4486 |
|
| 4487 |
<DT> <A NAME="alternate-role-menu"><EM>alternate-role-menu</EM></A> |
| 4488 |
|
| 4489 |
<DD> Normally the Role Command allows you to choose |
| 4490 |
a role and compose a new message using that role. |
| 4491 |
When this feature is set, the role command will first ask whether you want to |
| 4492 |
Compose a new message, Forward the current message, Reply to the |
| 4493 |
current message, or Bounce the current message. |
| 4494 |
If you are not in the MESSAGE INDEX and are not viewing a message, |
| 4495 |
then there is no current message and the question will be skipped. |
| 4496 |
After you have chosen to Compose, Forward, Reply or Bounce you will |
| 4497 |
then choose the role to be used. |
| 4498 |
<P> |
| 4499 |
When Bouncing the "Set From" address is used for the |
| 4500 |
Resent-From header, the "Set Fcc" value is used for the Fcc |
| 4501 |
provided that the option |
| 4502 |
<A HREF="#fcc-on-bounce">"Fcc-On-Bounce"</A> is turned on, |
| 4503 |
and the "Use SMTP Server" value is used for the SMTP server, if |
| 4504 |
set. |
| 4505 |
Other actions of the role are ignored when Bouncing. |
| 4506 |
<P> |
| 4507 |
This feature is displayed as "Alternate Role (#) Menu". |
| 4508 |
<P> |
| 4509 |
|
| 4510 |
|
| 4511 |
<DT> <A NAME="assume-slow-link"><EM>assume-slow-link</EM></A> |
| 4512 |
|
| 4513 |
<DD> UNIX <EM>Alpine</EM> only. |
| 4514 |
<P> |
| 4515 |
This feature affects <EM>Alpine</EM>'s display routines. If set, the normal |
| 4516 |
inverse-video cursor (used to highlight the current item in a list) will be |
| 4517 |
replaced by an <EM>arrow</EM> cursor and other screen update optimizations for |
| 4518 |
low-speed links (e.g. 2400 bps dialup connections) will be activated. |
| 4519 |
One of the optimizations is that colored index lines (set up with Indexcolor |
| 4520 |
Rules) will not be colored. |
| 4521 |
This might be useful if <I>you</I> know you have a slow speed link but for some |
| 4522 |
reason <EM>Alpine</EM> doesn't know. |
| 4523 |
<P> |
| 4524 |
|
| 4525 |
<DT> <A NAME="auto-read-msg"><EM>auto-move-read-msgs</EM></A> |
| 4526 |
|
| 4527 |
<DD> This feature controls an aspect |
| 4528 |
of <EM>Alpine</EM>'s behavior upon quitting. If set, |
| 4529 |
and the <A HREF="#read-msg-fold"><EM>read-message-folder</EM></A> |
| 4530 |
variable is also set, then <EM>Alpine</EM> will |
| 4531 |
automatically transfer all read messages from the <EM>INBOX</EM> to |
| 4532 |
the designated folder and mark |
| 4533 |
them as deleted in the <EM>INBOX</EM>. Messages in the <EM>INBOX</EM> marked |
| 4534 |
with an <EM>N</EM> (meaning New, or unseen) are not affected. |
| 4535 |
<P> |
| 4536 |
This feature is displayed as "Auto Move Read Messages". |
| 4537 |
<P> |
| 4538 |
|
| 4539 |
<DT> <A NAME="auto-open-next-unread"><EM>auto-open-next-unread</EM></A> |
| 4540 |
|
| 4541 |
<DD> This feature controls the behavior of the TAB key when traversing folders |
| 4542 |
in the optional <A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 4543 |
collection or in optional <A HREF="#news-coll"><EM>news-collections</EM></A>. |
| 4544 |
<P> |
| 4545 |
|
| 4546 |
When the TAB (Next New) key is pressed, and there are no more unseen |
| 4547 |
messages in the current (incoming message or news) folder, <EM>Alpine</EM> will |
| 4548 |
search the list of folders in the current collection for one containing |
| 4549 |
New or Recent (new since the last time the folder was opened) messages. |
| 4550 |
This behavior may be modified slightly with the |
| 4551 |
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A> |
| 4552 |
feature which causes <EM>Alpine</EM> to look for Unseen messages instead of Recent |
| 4553 |
messages. |
| 4554 |
By default, when such a folder is found, |
| 4555 |
<EM>Alpine</EM> will ask whether you wish to |
| 4556 |
open the folder. |
| 4557 |
If this feature is set, <EM>Alpine</EM> will automatically open the |
| 4558 |
folder without prompting. |
| 4559 |
<P> |
| 4560 |
|
| 4561 |
<DT> <A NAME="auto-unselect-after-apply"><EM>auto-unselect-after-apply</EM></A> |
| 4562 |
|
| 4563 |
<DD> This feature affects the behavior of the Apply command. If set, |
| 4564 |
the Apply command will do the operation you specify, but then will |
| 4565 |
implicitly do an "UnSelect All", so that you will automatically be back in |
| 4566 |
the normal Index view after the Apply. |
| 4567 |
<P> |
| 4568 |
|
| 4569 |
<DT> <A NAME="auto-unzoom-after-apply"><EM>auto-unzoom-after-apply</EM></A> |
| 4570 |
|
| 4571 |
<DD> If set, and if |
| 4572 |
you are currently looking at a Zoomed Index view of selected messages, |
| 4573 |
the <EM>Apply</EM> command will do the operation you specify, but then will |
| 4574 |
implicitly do an <EM>UnZoom</EM>, so that you will automatically be back in |
| 4575 |
the normal Index view after the <EM>Apply</EM>. |
| 4576 |
This feature is set by default. |
| 4577 |
<P> |
| 4578 |
|
| 4579 |
<DT> <A NAME="auto-zoom-after-select"><EM>auto-zoom-after-select</EM></A> |
| 4580 |
|
| 4581 |
<DD> If set, the <EM>; select</EM> command will automatically |
| 4582 |
perform a <EM>Zoom</EM> after the <EM>select</EM> is complete. |
| 4583 |
This feature is set by default. |
| 4584 |
<P> |
| 4585 |
|
| 4586 |
<DT> <A NAME="busy-cue-spinner-only"><EM>busy-cue-spinner-only</EM></A> |
| 4587 |
|
| 4588 |
<DD> When <EM>Alpine</EM> is delayed for some reason it usually shows that |
| 4589 |
something is happening with a small animated display in the status |
| 4590 |
message line near the bottom of the screen. |
| 4591 |
Setting this feature will cause that animation to be the same |
| 4592 |
each time instead of having <EM>Alpine</EM> choose a random animation. |
| 4593 |
You may turn the animation off altogether by setting the |
| 4594 |
<A HREF="#busy-cue-rate"><EM>busy-cue-rate</EM></A> |
| 4595 |
option to zero. |
| 4596 |
<P> |
| 4597 |
|
| 4598 |
<DT> <A NAME="check-newmail-when-quitting"><EM>check-newmail-when-quitting</EM></A> |
| 4599 |
|
| 4600 |
<DD> If set, <EM>Alpine</EM> will check for new mail after you give the |
| 4601 |
Quit command. |
| 4602 |
If new mail has arrived since the previous check, you will be notified |
| 4603 |
and given the choice of quitting or not quitting. |
| 4604 |
<P> |
| 4605 |
|
| 4606 |
<DT> <A NAME="combined-addrbook-display"><EM>combined-addrbook-display</EM></A> |
| 4607 |
|
| 4608 |
<DD> This feature affects the address book display screens. |
| 4609 |
Normally, expanding an address book from the ADDRESS BOOK LIST screen |
| 4610 |
will cause the remaining address books and directory servers to disappear |
| 4611 |
from the screen, leaving only the entries of the expanded address book. |
| 4612 |
If this feature is set, then the other address books will remain on the screen, |
| 4613 |
so that all of the address books can be present at once. |
| 4614 |
|
| 4615 |
<P> |
| 4616 |
The way that commands work won't be changed. |
| 4617 |
For example, the Select All command will select all of the entries in the |
| 4618 |
current address book, not all of the entries in all of the address books. |
| 4619 |
The WhereIs command will change a little. |
| 4620 |
It will search through all of the text on the screen plus all of the entries |
| 4621 |
from expanded address books. |
| 4622 |
|
| 4623 |
<P> |
| 4624 |
When this feature is set, the setting of the feature |
| 4625 |
<A HREF="#expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A> |
| 4626 |
has an effect. |
| 4627 |
<P> |
| 4628 |
This feature is displayed as "Combined Addressbook Display". |
| 4629 |
<P> |
| 4630 |
|
| 4631 |
<DT> <A NAME="combined-folder-display"><EM>combined-folder-display</EM></A> |
| 4632 |
|
| 4633 |
<DD> This feature affects the folder list display screens. |
| 4634 |
Normally, each folder list is viewed within its collection only. This |
| 4635 |
command allows folder lists to be viewed within a single screen that |
| 4636 |
combines the contents of all collections. |
| 4637 |
|
| 4638 |
<P> |
| 4639 |
The way that commands work won't be changed. |
| 4640 |
For example, the Select All command will select all of the folders in the |
| 4641 |
current collection, not all of the entries in all of the collections. |
| 4642 |
The WhereIs command will change a little. |
| 4643 |
It will search through all of the folders in the current collection as well |
| 4644 |
as all the folder in any other expanded collection. |
| 4645 |
|
| 4646 |
<P> |
| 4647 |
When this feature is set, the setting of the feature |
| 4648 |
<A HREF="#expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A> |
| 4649 |
has an effect. |
| 4650 |
<P> |
| 4651 |
|
| 4652 |
<DT> <A NAME="combined-subdirectory-display"><EM>combined-subdirectory-display</EM></A> |
| 4653 |
|
| 4654 |
<DD> This feature affects the Folder List screen when |
| 4655 |
the |
| 4656 |
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A> |
| 4657 |
feature is enabled. Normally, selecting a directory from the Folder |
| 4658 |
List takes you into a new screen displaying only the contents of |
| 4659 |
that directory. |
| 4660 |
|
| 4661 |
<P> |
| 4662 |
Enabling this feature will cause the contents of the selected |
| 4663 |
directory to be |
| 4664 |
displayed within the boundaries of the |
| 4665 |
<A HREF="background.html#collections"><EM>Collection</EM></A> |
| 4666 |
it is a part of. All previously displayed collections will remain |
| 4667 |
in the screen. |
| 4668 |
|
| 4669 |
<P> |
| 4670 |
The way that commands work won't be changed. |
| 4671 |
For example, the Select All command will select all of the folders in the |
| 4672 |
directory, as opposed to all of the entries in all of the collections. |
| 4673 |
The WhereIs command will change a little. |
| 4674 |
It will search through all of the folders in the current collection as well |
| 4675 |
as all the folder in any other expanded collection. |
| 4676 |
|
| 4677 |
<P> |
| 4678 |
|
| 4679 |
<DT> <A NAME="compose-cancel-confirm-uses-yes"><EM>compose-cancel-confirm-uses-yes</EM></A> |
| 4680 |
|
| 4681 |
<DD> This feature affects what happens when you type ^C to cancel a composition. |
| 4682 |
By default, if you attempt to cancel a composition by typing ^C, you will be |
| 4683 |
asked to confirm the cancellation by typing a "C" |
| 4684 |
for <EM>C</EM>onfirm. |
| 4685 |
It logically ought to be a "Y" for <EM>Y</EM>es, but that is |
| 4686 |
risky because the "^C Y" needed to cancel a message |
| 4687 |
is close (on the keyboard) to the "^X Y" needed to send a message. |
| 4688 |
<P> |
| 4689 |
If this feature is set the confirmation asked for |
| 4690 |
will be a "<EM>Y</EM>es" |
| 4691 |
instead of a "<EM>C</EM>onfirm" response. |
| 4692 |
<P> |
| 4693 |
|
| 4694 |
<DT> <A NAME="compose-cut-from-cursor"><EM>compose-cut-from-cursor</EM></A> |
| 4695 |
|
| 4696 |
<DD> If set, the <EM>^K</EM> command in the composer will cut from the |
| 4697 |
current cursor position to the end of the line, |
| 4698 |
rather than cutting the entire line. |
| 4699 |
<P> |
| 4700 |
This feature is displayed as "Ctrl-K Cuts From Cursor". |
| 4701 |
<P> |
| 4702 |
|
| 4703 |
<DT> <A NAME="compose-maps-delete-key-to-ctrl-d"><EM>compose-maps-delete-key-to-ctrl-d</EM></A> |
| 4704 |
|
| 4705 |
<DD> If set, Delete will be equivalent to ^D, and delete |
| 4706 |
the current character. Normally <EM>Alpine</EM> defines the Delete key |
| 4707 |
to be equivalent to ^H, which deletes the <EM>previous</EM> |
| 4708 |
character. |
| 4709 |
<P> |
| 4710 |
This feature is displayed as "Delete Key Maps to Ctrl-D". |
| 4711 |
<P> |
| 4712 |
|
| 4713 |
<DT> <A NAME="compose-rejects-unqualified-addrs"><EM>compose-rejects-unqualified-addrs</EM></A> |
| 4714 |
|
| 4715 |
<DD> If set, unqualified names entered as addresses will be treated as errors |
| 4716 |
unless they match an addressbook nickname or are looked up successfully |
| 4717 |
on an LDAP server. <EM>Alpine</EM> will not attempt to turn |
| 4718 |
them into complete addresses by adding your local domain (which <EM>Alpine</EM> normally |
| 4719 |
does by default). |
| 4720 |
<P> |
| 4721 |
|
| 4722 |
A complete (fully-qualified) address is one containing a username |
| 4723 |
followed by an <EM>@</EM> symbol, followed by a host or domain name (e.g. |
| 4724 |
<EM>[email protected]</EM>). An unqualified name is one without the |
| 4725 |
<EM>@</EM> symbol |
| 4726 |
and host or domain name (e.g. <EM>jsmith</EM>). |
| 4727 |
<P> |
| 4728 |
This feature is displayed as "Compose Rejects Unqualified Addresses". |
| 4729 |
<P> |
| 4730 |
|
| 4731 |
<DT> <A NAME="compose-send-offers-first-filter"><EM>compose-send-offers-first-filter</EM></A> |
| 4732 |
|
| 4733 |
<DD> If you have <A HREF="#sending-filters"><EM>sending-filters</EM></A> |
| 4734 |
configured, setting this feature will cause the first filter in the |
| 4735 |
<EM>sending-filters</EM> list to be offered as the default |
| 4736 |
instead of <EM>unfiltered</EM>, the usual default. |
| 4737 |
<P> |
| 4738 |
|
| 4739 |
<DT> <A NAME="compose-sets-newsgroup-without-confirm"><EM>compose-sets-newsgroup-without-confirm</EM></A> |
| 4740 |
|
| 4741 |
<DD> If you enter the |
| 4742 |
composer while reading a newsgroup, you will normally be prompted to |
| 4743 |
determine whether you intend the new message to be posted to the current |
| 4744 |
newsgroup or not. If this feature is set, <EM>Alpine</EM> will not prompt you |
| 4745 |
in this situation, and will assume that you do indeed wish to post |
| 4746 |
to the newsgroup you are reading. |
| 4747 |
<P> |
| 4748 |
This feature is displayed as "Compose Sets Newsgroup Without Confirming". |
| 4749 |
<P> |
| 4750 |
|
| 4751 |
<DT> <A NAME="confirm-role-even-for-default"><EM>confirm-role-even-for-default</EM></A> |
| 4752 |
|
| 4753 |
<DD> If you have roles, when you Reply to or Forward a message, or Compose |
| 4754 |
a new message, <EM>Alpine</EM> |
| 4755 |
will search through your roles for one which matches. |
| 4756 |
Normally, if no matches are found you will be placed into the composer |
| 4757 |
with no opportunity to select a role. |
| 4758 |
If this feature is set, then you will be asked to confirm that you don't |
| 4759 |
want a role. |
| 4760 |
This will give you the opportunity to select a role (with the ^T command). |
| 4761 |
If you confirm no role with a Return, you will be placed in |
| 4762 |
the composer with no role. |
| 4763 |
You may also confirm with either an "N" or a "Y". |
| 4764 |
These behave the same as if you pressed the Return. |
| 4765 |
(The "N" and "Y" answers are available because they |
| 4766 |
match what you might type if there was a role match.) |
| 4767 |
<P> |
| 4768 |
If you are using the alternate form of the Compose command called |
| 4769 |
"Role", then all of your roles will be available to you, |
| 4770 |
independent of the value of this feature and of the values set for all of |
| 4771 |
Reply Use, Forward Use, and Compose Use. |
| 4772 |
<P> |
| 4773 |
|
| 4774 |
<DT> <A NAME="continue-tab-without-confirm"><EM>continue-tab-without-confirm</EM></A> |
| 4775 |
|
| 4776 |
<DD> Normally, when you use the TAB NextNew |
| 4777 |
command and there is a problem checking a folder, you are asked |
| 4778 |
whether you want to continue with the search in the following folder or not. |
| 4779 |
This gives you a chance to stop the NextNew processing. |
| 4780 |
<P> |
| 4781 |
If this feature is set you will not be asked. |
| 4782 |
It will be assumed that you want to continue. |
| 4783 |
<P> |
| 4784 |
This feature is displayed as "Continue NextNew Without Confirming". |
| 4785 |
<P> |
| 4786 |
|
| 4787 |
<DT> <A NAME="convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A> |
| 4788 |
|
| 4789 |
<DD> Normally, the message dates that you see in the |
| 4790 |
MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from. |
| 4791 |
For example, if a message was sent to you from a few timezones to the east |
| 4792 |
it might appear that it was sent from the future; |
| 4793 |
or if it was sent from somewhere to the west it might appear |
| 4794 |
as if it is from yesterday even though it was sent only a few minutes ago. |
| 4795 |
If this feature is set an attempt will be made to convert the dates |
| 4796 |
to your local timezone to be displayed. |
| 4797 |
<P> |
| 4798 |
Note that this does not affect the results of Select by Date or of |
| 4799 |
anything else other than these displayed dates. |
| 4800 |
When viewing the message you may look at the original unconverted value of the Date |
| 4801 |
header by using the HdrMode Command. |
| 4802 |
<P> |
| 4803 |
|
| 4804 |
<DT> <A NAME="copy-to-to-from"><EM>copy-to-address-to-from-if-it-is-us</EM></A> |
| 4805 |
|
| 4806 |
<DD> This feature affects the From address used when Replying to a message. |
| 4807 |
It is probably only useful if you have some |
| 4808 |
<A HREF="#alt-addresses">alt-addresses</A> |
| 4809 |
defined. |
| 4810 |
When enabled, it checks to see if any of the addresses in the To or Cc |
| 4811 |
fields of the message you are replying to is one of your addresses. |
| 4812 |
If it is, and there is only one of them, then that address is used as |
| 4813 |
the From address in the message you are composing. |
| 4814 |
In other words, you will be using a From address that is the same |
| 4815 |
as the To address that was used to get the mail to you in the first place. |
| 4816 |
|
| 4817 |
<P> |
| 4818 |
If a role is being used and it has a From address defined, that From address will |
| 4819 |
be used rather than the one derived from this feature. |
| 4820 |
<P> |
| 4821 |
|
| 4822 |
<DT> <A NAME="delete-skips-deleted"><EM>delete-skips-deleted</EM></A> |
| 4823 |
|
| 4824 |
<DD> If set, this |
| 4825 |
feature will cause the <EM>Delete</EM> command to |
| 4826 |
advance past other messages that |
| 4827 |
are marked deleted. In other words, pressing <EM>D</EM> will both mark the |
| 4828 |
current message deleted and advance to the next message that is not marked |
| 4829 |
deleted. |
| 4830 |
This feature is set by default. |
| 4831 |
<P> |
| 4832 |
|
| 4833 |
<DT> <A NAME="disable-config-cmd"><EM>disable-config-cmd</EM></A> |
| 4834 |
|
| 4835 |
<DD> If set, the configuration |
| 4836 |
screen <EM>Setup/Config</EM> will not be available at all. |
| 4837 |
<P> |
| 4838 |
|
| 4839 |
<DT> <A NAME="disable-save-input-history"><EM>disable-save-input-history</EM></A> |
| 4840 |
|
| 4841 |
<DD> Many of the prompts that ask for input in the status line near the |
| 4842 |
bottom of the screen will respond to Up Arrow and Down Arrow |
| 4843 |
with the history of previous entries. |
| 4844 |
For example, in the MESSAGE INDEX screen when you use the WhereIs |
| 4845 |
command the text you entered will be remembered and can be recalled |
| 4846 |
by using the Up Arrow key. |
| 4847 |
Another example, when saving a message the folders saved to will |
| 4848 |
be remembered and can be recalled using the arrow keys. |
| 4849 |
<P> |
| 4850 |
In the Save prompt, some users prefer that the Up and Down arrow keys |
| 4851 |
be used for the Previous Collection and Next Collection commands |
| 4852 |
instead of for a history of previous saves. |
| 4853 |
If this option is set the Up and Down arrow keys will become synonyms for the |
| 4854 |
Previous Collection and Next Collection (^P and ^N) commands in the |
| 4855 |
prompt for the name of a folder to Save to or in the prompt for the |
| 4856 |
name of a folder to GoTo. |
| 4857 |
When this feature is not set (the default), ^P and ^N will change the |
| 4858 |
collection and the arrow keys will show the history. |
| 4859 |
<P> |
| 4860 |
|
| 4861 |
<DT> <A NAME="disable-kblock"><EM>disable-keyboard-lock-cmd</EM></A> |
| 4862 |
|
| 4863 |
<DD> In the Main <EM>Alpine</EM> menu there is a Keyboard locking |
| 4864 |
command (<EM>KBLock</EM>). If this feature is set, that command won't be |
| 4865 |
available to the user. |
| 4866 |
<P> |
| 4867 |
|
| 4868 |
<DT> <A NAME="disable-keymenu"><EM>disable-keymenu</EM></A> |
| 4869 |
|
| 4870 |
<DD> If set, the command key menu that normally appears on the |
| 4871 |
bottom two lines of the screen will not usually be there. Asking for |
| 4872 |
help with <EM>^G</EM> or <EM>?</EM> will cause the key menu to |
| 4873 |
appear instead of causing the help message to come up. If you want to |
| 4874 |
actually see the help text, |
| 4875 |
another <EM>^G</EM> or <EM>?</EM> will show it to you. |
| 4876 |
After the key menu has popped |
| 4877 |
up with the help key it will remain there for an <EM>O Other</EM> command but |
| 4878 |
will disappear if any other command is typed. |
| 4879 |
<P> |
| 4880 |
|
| 4881 |
<DT> <A NAME="disable-password-caching"><EM>disable-password-caching</EM></A> |
| 4882 |
<P> |
| 4883 |
|
| 4884 |
<DD> Normally, loginname/password combinations are cached in <EM>Alpine</EM> |
| 4885 |
so that the user does not have to enter the same password more than once |
| 4886 |
in a session. |
| 4887 |
A disadvantage to this approach is that the password must be stored in |
| 4888 |
the memory image of the running <EM>Alpine</EM> in order that it can be reused. |
| 4889 |
In the event that <EM>Alpine</EM> crashes and produces a core dump, and that core |
| 4890 |
dump is readable by others, the loginname and password could possibly be read |
| 4891 |
from the core dump. |
| 4892 |
<P> |
| 4893 |
If this feature is set, then the passwords will not be cached and |
| 4894 |
the user will have to retype the password whenever <EM>Alpine</EM> needs it. |
| 4895 |
Even with this feature set there is still some chance that the core |
| 4896 |
file will contain a password, so care should be taken to make the |
| 4897 |
core files unreadable. |
| 4898 |
<P> |
| 4899 |
NOTE: If PASSFILE caching is enabled, this does not disable it. |
| 4900 |
That is a separate and independent feature. |
| 4901 |
<P> |
| 4902 |
|
| 4903 |
<DT> <A NAME="disable-password-cmd"><EM>disable-password-cmd</EM></A> |
| 4904 |
|
| 4905 |
<DD> If set the <EM>Newpassword</EM> command usually available under the |
| 4906 |
<EM>Setup</EM> command will not be available. |
| 4907 |
<P> |
| 4908 |
|
| 4909 |
<DT> <A NAME="disable-pipes-in-sigs"><EM>disable-pipes-in-sigs</EM></A> |
| 4910 |
|
| 4911 |
<DD> If set it will be an error to append a vertical bar (|) to the name |
| 4912 |
of a signature file. |
| 4913 |
Appending a vertical bar normally causes the signature file to be executed |
| 4914 |
to produce the signature. |
| 4915 |
<P> |
| 4916 |
|
| 4917 |
<DT> <A NAME="disable-pipes-in-templates"><EM>disable-pipes-in-templates</EM></A> |
| 4918 |
|
| 4919 |
<DD> If set it will be an error to append a vertical bar (|) to the name |
| 4920 |
of a template file. |
| 4921 |
Appending a vertical bar normally causes the signature file to be executed |
| 4922 |
to produce the signature. |
| 4923 |
<P> |
| 4924 |
|
| 4925 |
<DT> <A NAME="disable-regex"><EM>disable-regular-expression-matching-for-alternate-addresses</EM></A> |
| 4926 |
|
| 4927 |
<DD> Normally, the |
| 4928 |
<A HREF="#alt-addresses">alt-addresses</A> |
| 4929 |
option is interpreted as a regular expression. |
| 4930 |
One type of address that might cause trouble is an address that |
| 4931 |
contains a plus sign. |
| 4932 |
If you want to have an address with a plus as one of your |
| 4933 |
alternate addresses |
| 4934 |
and you don't want to use regular expressions, then setting this |
| 4935 |
feature will cause <EM>Alpine</EM> to treat the addresses you list literally instead. |
| 4936 |
<P> |
| 4937 |
|
| 4938 |
<DT> <A NAME="disable-roles-setup-cmd"><EM>disable-roles-setup-cmd</EM></A> |
| 4939 |
|
| 4940 |
<DD> If set the <EM>Roles</EM> command usually available under the |
| 4941 |
<EM>Setup</EM> command will not be available. |
| 4942 |
<P> |
| 4943 |
|
| 4944 |
<DT> <A NAME="disable-roles-sig-edit"><EM>disable-roles-sig-edit</EM></A> |
| 4945 |
|
| 4946 |
<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow |
| 4947 |
editing of signature files with the F subcommand. |
| 4948 |
<P> |
| 4949 |
|
| 4950 |
<DT> <A NAME="disable-roles-template-edit"><EM>disable-roles-template-edit</EM></A> |
| 4951 |
|
| 4952 |
<DD> If set the roles editor in the <EM>Setup/Roles</EM> command will not allow |
| 4953 |
editing of template files with the F subcommand. |
| 4954 |
<P> |
| 4955 |
|
| 4956 |
<DT> <A NAME="disable-sender"><EM>disable-sender</EM></A> |
| 4957 |
|
| 4958 |
<DD> If set, <EM>Alpine</EM> will not generate a "Sender:" or "X-X-Sender" header. |
| 4959 |
This may be desirable on a system which is virtually hosting many domains, |
| 4960 |
and the sysadmin has other methods available for tracking a message to |
| 4961 |
its originator. |
| 4962 |
<P> |
| 4963 |
This feature is displayed as "Do Not Generate Sender Header". |
| 4964 |
<P> |
| 4965 |
|
| 4966 |
<DT> <A NAME="disable-setlocale-collate"><EM>disable-setlocale-collate</EM></A> |
| 4967 |
|
| 4968 |
<DD> This is a hard to understand feature that should only be used in rare cases. |
| 4969 |
Normally, the C function call |
| 4970 |
<P> |
| 4971 |
<CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER> |
| 4972 |
<P> |
| 4973 |
is used by <EM>Alpine</EM>. |
| 4974 |
If you want to try turning it off, |
| 4975 |
setting this feature will turn it off. |
| 4976 |
This part of the locale has to do with the sort order |
| 4977 |
of characters in your locale. |
| 4978 |
<P> |
| 4979 |
|
| 4980 |
<DT> <A NAME="disable-shared-namespaces"><EM>disable-shared-namespaces</EM></A> |
| 4981 |
|
| 4982 |
<DD> If this hidden feature is set |
| 4983 |
the automatic search for namespaces "ftp", |
| 4984 |
"imapshared", and "imappublic" by the underlying library |
| 4985 |
will be disabled. |
| 4986 |
The reason this feature exists is because there are some implementations |
| 4987 |
of system password lookup routines which are very slow when presented with |
| 4988 |
a long loginname which does not exist. |
| 4989 |
This feature could be set to prevent the delay at startup time when the |
| 4990 |
names above are searched for in the password file. |
| 4991 |
<P> |
| 4992 |
|
| 4993 |
<DT> <A NAME="disable-signature-edit-cmd"><EM>disable-signature-edit-cmd</EM></A> |
| 4994 |
|
| 4995 |
<DD> If set the <EM>Signature</EM> editing command usually available under the |
| 4996 |
<EM>Setup</EM> command will not be available. |
| 4997 |
<P> |
| 4998 |
|
| 4999 |
<DT> <A NAME="disable-take-fullname"><EM>disable-take-fullname-in-addresses</EM></A> |
| 5000 |
|
| 5001 |
<DD> Normally, when TakeAddr is used to copy an address or addresses |
| 5002 |
from a message into an address book entry, <EM>Alpine</EM> will try to preserve |
| 5003 |
the full name associated with each address in the list of addresses. |
| 5004 |
The reason for this is so that if the entry is a list or later becomes a |
| 5005 |
list, then information about the individual addresses in the list |
| 5006 |
is preserved. |
| 5007 |
If you would rather just have the simple addresses in the list of addresses, |
| 5008 |
set this feature. For example, with the default setting you might |
| 5009 |
see something like this in the ADDRESS BOOK editor after you type TakeAddr |
| 5010 |
<P> |
| 5011 |
<PRE> |
| 5012 |
Nickname : nick |
| 5013 |
Fullname : Bedrock Elders |
| 5014 |
Fcc : |
| 5015 |
Comment : |
| 5016 |
Addresses : Fred Flintstone <[email protected]>, |
| 5017 |
Barney Rubble <[email protected]> |
| 5018 |
</PRE> |
| 5019 |
<P> |
| 5020 |
but with this feature set it would look like |
| 5021 |
<P> |
| 5022 |
<PRE> |
| 5023 |
Nickname : nick |
| 5024 |
Fullname : Bedrock Elders |
| 5025 |
Fcc : |
| 5026 |
Comment : |
| 5027 |
Addresses : [email protected], |
| 5028 |
[email protected] |
| 5029 |
</PRE> |
| 5030 |
<P> |
| 5031 |
instead. Note the difference in the Addresses field. |
| 5032 |
<P> |
| 5033 |
|
| 5034 |
<DT> <A NAME="disable-take-last-comma-first"><EM>disable-take-last-comma-first</EM></A> |
| 5035 |
|
| 5036 |
<DD> Normally, when <EM>TakeAddr</EM> is used to copy an address |
| 5037 |
from a message into an address book, <EM>Alpine</EM> will attempt to rewrite the |
| 5038 |
full name of the address in the form: |
| 5039 |
|
| 5040 |
<BLOCKQUOTE> |
| 5041 |
Last, First <BR> |
| 5042 |
</BLOCKQUOTE> |
| 5043 |
|
| 5044 |
instead of |
| 5045 |
|
| 5046 |
<BLOCKQUOTE> |
| 5047 |
First Last <BR> |
| 5048 |
</BLOCKQUOTE> |
| 5049 |
|
| 5050 |
It does this because many people find it useful to sort by Last name instead |
| 5051 |
of First name. If this feature is set, then the <EM>TakeAddr</EM> command will |
| 5052 |
not attempt to reverse the name in this manner. |
| 5053 |
<P> |
| 5054 |
|
| 5055 |
<DT> <A NAME="disable-terminal-reset-for-display-filters"><EM>disable-terminal-reset-for-display-filters</EM></A> |
| 5056 |
|
| 5057 |
<DD> UNIX <EM>Alpine</EM> only. |
| 5058 |
<P> |
| 5059 |
This feature affects <EM>Alpine</EM>'s behavior when using |
| 5060 |
<A HREF="#display-filters"><EM>Display-Filters</EM></A>. |
| 5061 |
Normally, before the display filter is run, the terminal mode is reset |
| 5062 |
to what it was before you started <EM>Alpine</EM>. |
| 5063 |
This may be necessary if the filter requires the use of the terminal. |
| 5064 |
For example, it may need to interact with you. |
| 5065 |
If you set this feature, then the terminal mode will not be reset. |
| 5066 |
One thing that turning on this feature should fix is the coloring of |
| 5067 |
quoted text in the message view, which |
| 5068 |
breaks because the terminal reset resets the color state of the terminal |
| 5069 |
(<A HREF="#color-config">Color Configuration</A>). |
| 5070 |
<P> |
| 5071 |
|
| 5072 |
<DT> <A NAME="downgrade-multipart-to-text"><EM>downgrade-multipart-to-text</EM></A> |
| 5073 |
|
| 5074 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail. Internet |
| 5075 |
standards require <EM>Alpine</EM> to translate all non-ASCII characters in |
| 5076 |
messages that it sends using MIME encoding. This encoding can be |
| 5077 |
ostensibly broken for recipients if any agent between <EM>Alpine</EM> and the |
| 5078 |
recipient, such as an email list expander, appends text to the |
| 5079 |
message, such as list information or advertising. When sending such |
| 5080 |
messages <EM>Alpine</EM> attempts to protect such encoding by placing extra |
| 5081 |
MIME boundaries around the message text. |
| 5082 |
<P> |
| 5083 |
These extra boundaries are invisible to recipients that |
| 5084 |
use MIME-aware email programs (the vast majority). However, if |
| 5085 |
you correspond with users of email programs that are not MIME-aware, |
| 5086 |
or do not handle the extra boundaries gracefully, you can |
| 5087 |
use this feature to prevent <EM>Alpine</EM> from including the extra |
| 5088 |
MIME information. Of course, it will increase the likelihood |
| 5089 |
that non-ASCII text you send may appear corrupt to the recipient. |
| 5090 |
<P> |
| 5091 |
|
| 5092 |
<DT> <A NAME="enable-8bit-esmtp-negotiation"><EM>enable-8bit-esmtp-negotiation</EM></A> |
| 5093 |
|
| 5094 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when sending mail. |
| 5095 |
By default, this feature is set. |
| 5096 |
Internet standards |
| 5097 |
require that all electronic mail messages traversing the global Internet |
| 5098 |
consist of 7bit ASCII characters unless a pair of cooperating mail |
| 5099 |
transfer agents explicitly agree to allow 8bit messages. In general, |
| 5100 |
then, exchanging messages in non-ASCII characters requires MIME encoding. |
| 5101 |
<P> |
| 5102 |
|
| 5103 |
However, there are now Internet standards that allow for unencoded 8bit |
| 5104 |
exchange of messages between cooperating systems. When this feature is set |
| 5105 |
<EM>Alpine</EM> will try to negotiate unencoded 8bit transmission during the |
| 5106 |
sending process. Should the negotiation fail, <EM>Alpine</EM> will fall back to its |
| 5107 |
ordinary encoding rules. |
| 5108 |
<P> |
| 5109 |
|
| 5110 |
Note, this feature relies on your system's mail transport agent or |
| 5111 |
configured <A HREF="#smtp-server"><EM>smtp-server</EM></A> |
| 5112 |
having the negotiation mechanism introduced in |
| 5113 |
"Extended SMTP" (ESMTP) and the specific extension called <EM>8BITMIME</EM>. |
| 5114 |
<P> |
| 5115 |
|
| 5116 |
<DT> <A NAME="enable-8bit-nntp-posting"><EM>enable-8bit-nntp-posting</EM></A> |
| 5117 |
|
| 5118 |
<DD> The Internet standard for exchanging USENET news messages (RFC-1036) |
| 5119 |
specifies that USENET messages should conform to Internet mail standards |
| 5120 |
and contain only 7bit characters, but much of the news transport software |
| 5121 |
in use today is capable of successfully sending messages containing 8bit |
| 5122 |
characters. Hence, many people believe that it is appropriate to send 8bit |
| 5123 |
news messages without any MIME encoding. |
| 5124 |
<P> |
| 5125 |
|
| 5126 |
Moreover, there is no Internet standard for explicitly negotiating 8bit |
| 5127 |
transfer, as there is for Internet email. Therefore, <EM>Alpine</EM> provides the |
| 5128 |
option of posting unencoded 8bit news messages, though not as the default. |
| 5129 |
Setting this feature will turn OFF <EM>Alpine</EM>'s MIME encoding of newsgroup |
| 5130 |
postings that contain 8bit characters. |
| 5131 |
<P> |
| 5132 |
|
| 5133 |
Note, articles may cross a path or pass through news transport software |
| 5134 |
that is unsafe or even hostile to 8bit characters. At best this will only |
| 5135 |
cause the posting to become garbled. The safest way to transmit 8bit |
| 5136 |
characters is to leave <EM>Alpine</EM>'s MIME encoding turned on, but recipients |
| 5137 |
who lack MIME-aware tools are often annoyed when they receive MIME-encoded |
| 5138 |
messages. |
| 5139 |
<P> |
| 5140 |
|
| 5141 |
<DT> <A NAME="enable-aggregate-command-set"><EM>enable-aggregate-command-set</EM></A> |
| 5142 |
|
| 5143 |
<DD> When this feature is set you may use the commands and subcommands that relate to |
| 5144 |
performing operations on more than one message at a time. |
| 5145 |
We call these "aggregate operations". |
| 5146 |
In particular, the <EM>; Select</EM>, <EM>A Apply</EM>, and |
| 5147 |
<EM>Z Zoom</EM> commands are enabled by this feature. |
| 5148 |
<EM>Select</EM> is used to <EM>tag</EM> one |
| 5149 |
or more messages meeting the specified criteria. <EM>Apply</EM> can then be used |
| 5150 |
to apply any message command to all of the selected/tagged messages. |
| 5151 |
Further, the <EM>Zoom</EM> command allows you to toggle the "Folder Index" view |
| 5152 |
between just those Selected and all messages in the folder. |
| 5153 |
<P> |
| 5154 |
|
| 5155 |
This feature also enables the <EM>^X</EM> subcommand in |
| 5156 |
the "Folder Index" <EM>WhereIs</EM> |
| 5157 |
command which causes |
| 5158 |
all messages matching the <EM>WhereIs</EM> argument to become |
| 5159 |
selected. |
| 5160 |
<P> |
| 5161 |
|
| 5162 |
You may also use aggregate operations in the address book screens where |
| 5163 |
you are operating on address book entries instead of on messages. |
| 5164 |
<P> |
| 5165 |
|
| 5166 |
<DT> <A NAME="enable-alt-ed"><EM>enable-alternate-editor-cmd</EM></A> |
| 5167 |
|
| 5168 |
<DD> If this feature is set (the default), and the <A HREF="#editor"><EM>editor</EM></A> |
| 5169 |
variable is not set, entering |
| 5170 |
the <EM>^_</EM> (Control-underscore) key while |
| 5171 |
composing a message will prompt you |
| 5172 |
for the name of the editor you would like to use. |
| 5173 |
<P> |
| 5174 |
|
| 5175 |
If the environment variable <CODE>$EDITOR</CODE> is set, |
| 5176 |
this value will be offered as a default. |
| 5177 |
|
| 5178 |
If the <EM>editor</EM> variable is set, the <EM>^_</EM> key will activate |
| 5179 |
the specified editor without prompting, in which case it is not necessary to |
| 5180 |
set the <EM>enable-alternate-editor-cmd</EM> feature. |
| 5181 |
This feature is not available in <EM>PC-Alpine</EM>. |
| 5182 |
<P> |
| 5183 |
This feature is displayed as "Enable Alternate Editor Command". |
| 5184 |
<P> |
| 5185 |
|
| 5186 |
<DT> <A NAME="enable-alt-imp"><EM>enable-alternate-editor-implicitly</EM></A> |
| 5187 |
|
| 5188 |
<DD> If this feature and the <A HREF="#editor"><EM>editor</EM></A> |
| 5189 |
variable are both set, <EM>Alpine</EM> will |
| 5190 |
automatically activate the specified editor when the cursor is moved from |
| 5191 |
the header of the message being composed into the message text. For |
| 5192 |
replies, the alternate editor will be activated immediately. If this |
| 5193 |
feature is set but the <EM>editor</EM> variable is not set, |
| 5194 |
then <EM>Alpine</EM> will |
| 5195 |
automatically ask for the name of an alternate editor when the cursor |
| 5196 |
is moved out of the headers, or if a reply is being done. |
| 5197 |
This feature is not available in <EM>PC-Alpine</EM>. |
| 5198 |
<P> |
| 5199 |
|
| 5200 |
<DT> <A NAME="enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A> |
| 5201 |
|
| 5202 |
<DD> This feature controls the behavior of the left and right arrow keys. |
| 5203 |
If set, the left and right arrow keys will operate like the usual |
| 5204 |
navigation keys <EM><</EM> and <EM>></EM>. |
| 5205 |
This feature is set by default. |
| 5206 |
|
| 5207 |
<P> |
| 5208 |
If you set this feature, and do not like the changed behavior of the up/down |
| 5209 |
arrow keys when navigating through the FOLDER LIST screen -- |
| 5210 |
<B>first</B> from column to column, if more than one folder is |
| 5211 |
displayed per row, |
| 5212 |
and <B>then</B> from row to row -- you may either also wish to set the feature |
| 5213 |
<A HREF="#enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A>, |
| 5214 |
<A HREF="#single-column-folder-list"><EM>single-column-folder-list</EM></A>, |
| 5215 |
or use the ^P/^N (instead of up/down arrow) keys to move up/down the list of |
| 5216 |
folders in each column. |
| 5217 |
<P> |
| 5218 |
|
| 5219 |
<DT> <A NAME="enable-arrow-navigation-relaxed"><EM>enable-arrow-navigation-relaxed</EM></A> |
| 5220 |
|
| 5221 |
<DD> This feature controls the behavior of the left and right arrow keys |
| 5222 |
in the FOLDER LIST screen when the |
| 5223 |
<A HREF="#enable-arrow-navigation"><EM>enable-arrow-navigation</EM></A> |
| 5224 |
feature is set. |
| 5225 |
This feature is set by default. |
| 5226 |
<P> |
| 5227 |
|
| 5228 |
When this feature is set, the left and right |
| 5229 |
arrow keys in the FOLDER LIST screen |
| 5230 |
move the highlight bar to the left or right, and the up and |
| 5231 |
down arrows move it up or down. |
| 5232 |
|
| 5233 |
<P> |
| 5234 |
When the "Enable-Arrow-Navigation" feature is set and this |
| 5235 |
feature is not set; |
| 5236 |
the left and right arrow keys in the Folder List screen strictly |
| 5237 |
track the commands bound to the '<' and '>' keys, and the up |
| 5238 |
and down arrow keys move the highlight bar to the previous and next |
| 5239 |
folder or directory name. |
| 5240 |
|
| 5241 |
<P> |
| 5242 |
|
| 5243 |
<DT> <A NAME="enable-background-sending"><EM>enable-background-sending</EM></A> |
| 5244 |
|
| 5245 |
<DD> If set, this |
| 5246 |
feature enables a subcommand in the composer's <EM>Send?</EM> confirmation |
| 5247 |
prompt. The subcommand allows you to tell <EM>Alpine</EM> to handle the actual |
| 5248 |
posting in the background. While this feature usually allows posting |
| 5249 |
to appear to happen very fast, it has no affect on the actual delivery |
| 5250 |
time it takes a message to arrive at its destination. |
| 5251 |
<P> |
| 5252 |
|
| 5253 |
This feature isn't supported on all systems. All DOS and Windows, |
| 5254 |
as well as several Unix ports, do not recognize this feature. |
| 5255 |
It is not possible to use background sending if the feature |
| 5256 |
<A HREF="#send-without-confirm">send-without-confirm</A> is set. |
| 5257 |
<P> |
| 5258 |
|
| 5259 |
Error handling is significantly different when this feature is |
| 5260 |
enabled. Any message posting failure results in the message |
| 5261 |
being appended to your <EM>Interrupted</EM> mail folder. When you |
| 5262 |
type the <EM>Compose</EM> command, <EM>Alpine</EM> will notice this folder and |
| 5263 |
offer to extract any messages contained. Upon continuing a |
| 5264 |
failed message, <EM>Alpine</EM> will display the nature of the failure |
| 5265 |
in the status message line. |
| 5266 |
<P> |
| 5267 |
|
| 5268 |
Under extreme conditions, it is possible for message data to |
| 5269 |
get lost. Do not enable this feature if you typically run close |
| 5270 |
to any sort of disk-space limits or quotas. |
| 5271 |
<P> |
| 5272 |
|
| 5273 |
<DT> <A NAME="enable-bounce-cmd"><EM>enable-bounce-cmd</EM></A> |
| 5274 |
|
| 5275 |
<DD> Setting this feature enables the <EM>B Bounce</EM> command, |
| 5276 |
which will prompt |
| 5277 |
for an address and <EM>remail</EM> the message to the new recipient. |
| 5278 |
This command |
| 5279 |
is used to re-direct messages that you have received in error, or need to |
| 5280 |
be redirected for some other reason (e.g. list moderation). The final |
| 5281 |
recipient will see a header indicating that you have Resent the msg, but |
| 5282 |
the message's From: header will show the original author of the message, |
| 5283 |
and replies to it will go back to that author, and not to you. |
| 5284 |
<P> |
| 5285 |
This feature is displayed as "Enable Bounce Command". |
| 5286 |
<P> |
| 5287 |
|
| 5288 |
<DT> <A NAME="enable-cruise-mode"><EM>enable-cruise-mode</EM></A> |
| 5289 |
|
| 5290 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when you hit the "Space Bar" at |
| 5291 |
the end of a displayed message. Typically, <EM>Alpine</EM> complains that the end |
| 5292 |
of the text has already been reached. Setting this feature causes such |
| 5293 |
keystrokes to be interpreted as if the <EM>Tab</EM> key had been hit, thus |
| 5294 |
taking you to the next <EM>interesting</EM> message, or scanning ahead to the |
| 5295 |
next incoming folder with <EM>interesting</EM> messages. |
| 5296 |
<P> |
| 5297 |
|
| 5298 |
<DT> <A NAME="enable-cruise-mode-delete"><EM>enable-cruise-mode-delete</EM></A> |
| 5299 |
|
| 5300 |
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s <EM>enable-cruise-mode</EM> |
| 5301 |
feature. Setting this feature causes <EM>Alpine</EM> to implicitly delete read |
| 5302 |
messages when it moves on to display the next <EM>interesting</EM> message. |
| 5303 |
<P> |
| 5304 |
|
| 5305 |
NOTE: Beware when enabling this feature <B>and</B> the |
| 5306 |
<A HREF="#expunge-wo-confirm"><EM>expunge-without-confirm</EM></A> feature. |
| 5307 |
<P> |
| 5308 |
This feature is displayed as "Enable Cruise Mode With Deleting". |
| 5309 |
<P> |
| 5310 |
|
| 5311 |
<DT> <A NAME="enable-delivery-status-notification"><EM>enable-delivery-status-notification</EM></A> |
| 5312 |
|
| 5313 |
<DD> If set, this |
| 5314 |
feature enables a subcommand in the composer's "Send?" confirmation |
| 5315 |
prompt. The subcommand allows you to tell <EM>Alpine</EM> to request the type of |
| 5316 |
Delivery Status Notification (DSN) which you would like. Most users will |
| 5317 |
be happy with the default, and need not enable this feature. See the online |
| 5318 |
help for more details. |
| 5319 |
<P> |
| 5320 |
It is not possible to use delivery status notifications if the feature |
| 5321 |
<A HREF="#send-without-confirm">send-without-confirm</A> is set. |
| 5322 |
<P> |
| 5323 |
|
| 5324 |
Note that this is not a method to request <EM>READ</EM> receipts, which tells |
| 5325 |
the sender when the receiver has read the message. In this case we're talking |
| 5326 |
about notification of delivery to the mailbox, not notification that the |
| 5327 |
message has been seen. |
| 5328 |
<P> |
| 5329 |
|
| 5330 |
<DT> <A NAME="enable-dot-files"><EM>enable-dot-files</EM></A> |
| 5331 |
|
| 5332 |
<DD> If set, files beginning with dot (".") will be |
| 5333 |
visible in the file browser. For example, you'll be able to select them |
| 5334 |
when using the browser to add an attachment to a message. |
| 5335 |
<P> |
| 5336 |
|
| 5337 |
<DT> <A NAME="enable-dot-folders"><EM>enable-dot-folders</EM></A> |
| 5338 |
|
| 5339 |
<DD> If set, folders beginning with dot (".") may be added |
| 5340 |
and viewed. |
| 5341 |
This feature is displayed as "Enable Hidden Folders". |
| 5342 |
<P> |
| 5343 |
|
| 5344 |
<DT> <A NAME="enable-exit-via-lessthan-command"><EM>enable-exit-via-lessthan-command</EM></A> |
| 5345 |
|
| 5346 |
<DD> If set, then on screens where there is an <EM>Exit</EM> command |
| 5347 |
but no <EM><</EM> command, the <EM><</EM> key will perform |
| 5348 |
the same function as the <EM>Exit</EM> command. |
| 5349 |
This feature is set by default. |
| 5350 |
<P> |
| 5351 |
|
| 5352 |
<DT> <A NAME="enable-fast-recent-test"><EM>enable-fast-recent-test</EM></A> |
| 5353 |
|
| 5354 |
<DD> This feature controls the behavior of the TAB key when traversing folders |
| 5355 |
in the optional |
| 5356 |
<A HREF="#enable-incoming-folders">Incoming-Folders</A> |
| 5357 |
collection or in optional News-Collections. |
| 5358 |
|
| 5359 |
<P> |
| 5360 |
When the TAB |
| 5361 |
(NextNew) |
| 5362 |
key is pressed, the default behavior is to |
| 5363 |
explicitly examine the status of the folder for the number of recent |
| 5364 |
messages (messages delivered since the last time it was viewed). |
| 5365 |
Depending on the size and number of messages in the folder, this test |
| 5366 |
can be time consuming. |
| 5367 |
|
| 5368 |
<P> |
| 5369 |
Enabling this feature will cause <EM>Alpine</EM> to only test for the existence of |
| 5370 |
any recent messages rather than to obtain the count. This is much faster |
| 5371 |
in many cases. The downside is that you're not given the number of recent |
| 5372 |
messages when prompted to view the next folder. |
| 5373 |
If the feature |
| 5374 |
<A HREF="#tab-uses-unseen-for-next-folder">Tab-Uses-Unseen-For-Next-Folder</A> |
| 5375 |
is turned on, then the present feature will have no effect. |
| 5376 |
<P> |
| 5377 |
|
| 5378 |
<DT> <A NAME="enable-flag-cmd"><EM>enable-flag-cmd</EM></A> |
| 5379 |
|
| 5380 |
<DD> Setting this feature enables the <EM>* Flag</EM> command, |
| 5381 |
which allows you to |
| 5382 |
manipulate the status flags associated with a message. |
| 5383 |
By default, <EM>Flag</EM> |
| 5384 |
will set the <EM>Important</EM> flag, which results in an asterisk being |
| 5385 |
displayed in column one of the "Folder Index" for such messages. |
| 5386 |
<P> |
| 5387 |
This feature is displayed as "Enable Flag Command". |
| 5388 |
<P> |
| 5389 |
|
| 5390 |
<DT> <A NAME="enable-flag-screen-implicitly"><EM>enable-flag-screen-implicitly</EM></A> |
| 5391 |
|
| 5392 |
<DD> This feature modifies the behavior of the <EM>* Flag</EM> command |
| 5393 |
(provided it too is enabled). |
| 5394 |
By default, when the <EM>* Flag</EM> command is selected, |
| 5395 |
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the |
| 5396 |
option of entering the detailed flag manipulation screen via the <EM>^T</EM> |
| 5397 |
key. Enabling this feature causes <EM>Alpine</EM> to immediately enter the detailed |
| 5398 |
flag screen rather than first offer the simple prompt. |
| 5399 |
The |
| 5400 |
<A HREF="#enable-flag-screen-keyword-shortcut">Enable-Flag-Screen-Keyword-Shortcut</A> option offers a slightly different way of setting keywords. |
| 5401 |
<P> |
| 5402 |
|
| 5403 |
<DT> <A NAME="enable-flag-screen-keyword-shortcut"><EM>enable-flag-screen-keyword-shortcut</EM></A> |
| 5404 |
|
| 5405 |
<DD> This feature modifies the behavior of the |
| 5406 |
Flag command and the Select command. |
| 5407 |
By default, when the "* Flag" command is selected, |
| 5408 |
<EM>Alpine</EM> offers a prompt to set one of several flags and also offers the |
| 5409 |
option of entering the detailed flag manipulation screen via the "^T" |
| 5410 |
key. |
| 5411 |
If you have |
| 5412 |
<A HREF="#keywords">keywords</A> |
| 5413 |
defined, then enabling this feature adds a shortcut way to set or unset |
| 5414 |
keywords. |
| 5415 |
You use "*" followed by the first letter of a keyword (or the nickname of |
| 5416 |
a keyword if you've given it a nickname) and that will set the keyword. |
| 5417 |
<P> |
| 5418 |
An example is easier to understand than the explanation. |
| 5419 |
The flag command can always be used to set the system flags. |
| 5420 |
For example, to set the Answered flag you would type |
| 5421 |
<P> |
| 5422 |
<CENTER><SAMP>* A</SAMP></CENTER> |
| 5423 |
<P> |
| 5424 |
Now suppose you have defined a keyword "Work" using the Keywords |
| 5425 |
option in the Config screen. |
| 5426 |
By default, to set a keyword like "Work" you would usually |
| 5427 |
have to go to the Flag Details screen using |
| 5428 |
the "^T To Flag Details" command. |
| 5429 |
Instead, if you have enabled this feature, you may type |
| 5430 |
<P> |
| 5431 |
<CENTER><SAMP>* W</SAMP></CENTER> |
| 5432 |
<P> |
| 5433 |
to set the Work flag, or |
| 5434 |
<P> |
| 5435 |
<CENTER><SAMP>* ! W</SAMP></CENTER> |
| 5436 |
<P> |
| 5437 |
to unset it. |
| 5438 |
Just like for the other flag setting commands, the case of the letter does |
| 5439 |
not matter, so "w" or "W" both set the "Work" |
| 5440 |
keyword. |
| 5441 |
<P> |
| 5442 |
Notice that you can only use this trick for one keyword that begins |
| 5443 |
with "W". |
| 5444 |
If you happen to have a "Work" keyword and another keyword that is |
| 5445 |
"WIFI" the "* W" command will set the first one in |
| 5446 |
your list of keywords. |
| 5447 |
Also, there are five letters which are reserved for system |
| 5448 |
flags and the NOT command. |
| 5449 |
If you type "* A" it will always set the Answered flag, not |
| 5450 |
your "Aardvark" keyword. |
| 5451 |
In order to set the "Aardvark" keyword you'll still have to use |
| 5452 |
the Flag Details screen. |
| 5453 |
<P> |
| 5454 |
Because enabling the |
| 5455 |
<A HREF="#enable-flag-screen-implicitly">Enable-Flag-Screen-Implicitly</A> |
| 5456 |
option causes <EM>Alpine</EM> to skip directly to the Flag Details screen when the |
| 5457 |
Flag command is used, |
| 5458 |
setting it will cause this feature to have no effect at all. |
| 5459 |
<P> |
| 5460 |
Similarly, when Selecting by Keyword, setting this option will allow you |
| 5461 |
to use Keyword initials instead of full keywords. |
| 5462 |
<P> |
| 5463 |
|
| 5464 |
<DT> <A NAME="enable-full-header-cmd"><EM>enable-full-header-cmd</EM></A> |
| 5465 |
|
| 5466 |
<DD> This feature enables the <EM>H Full Headers</EM> command which |
| 5467 |
toggles between |
| 5468 |
the display of all headers in the message and the normal edited view of |
| 5469 |
headers. The <EM>Full Header</EM> command also controls |
| 5470 |
which headers are included |
| 5471 |
for <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>, |
| 5472 |
and <EM>Reply</EM> functions. (For <EM>Reply</EM>, the |
| 5473 |
<EM>Full Header</EM> mode will respect |
| 5474 |
the <EM>include-headers-in-reply</EM> feature setting.) |
| 5475 |
<P> |
| 5476 |
If Full Header mode is turned on and you Forward a message, you will |
| 5477 |
be asked if you'd like to forward the message as an attachment, as opposed |
| 5478 |
to including the text of the message in the body of your new message. |
| 5479 |
<P> |
| 5480 |
If you have also turned on the |
| 5481 |
<A HREF="#quote-suppression-threshold">"Quote Suppression"</A> |
| 5482 |
option then the Full Headers command actually rotates through three states |
| 5483 |
instead of just two. |
| 5484 |
The first is the normal view with long quotes suppressed. |
| 5485 |
The second is the normal view but with the long quotes included. |
| 5486 |
The last enables the display of all headers in the message. |
| 5487 |
When using Export, Pipe, Print, Forward, or Reply the quotes are |
| 5488 |
never suppressed, so the first two states are identical. |
| 5489 |
<P> |
| 5490 |
Normally, the Header Mode will reset |
| 5491 |
to the default behavior when moving to a new message. |
| 5492 |
The mode can be made to persist from message to message by setting the feature |
| 5493 |
<A HREF="#quell-full-header-auto-reset">Quell-Full-Header-Auto-Reset</A>. |
| 5494 |
<P> |
| 5495 |
This feature is displayed as "Enable Full Header Command". |
| 5496 |
<P> |
| 5497 |
|
| 5498 |
<DT> <A NAME="enable-full-header-and-text"><EM>enable-full-header-and-text</EM></A> |
| 5499 |
|
| 5500 |
<DD> |
| 5501 |
<P>This feature affects how the <EM>H Full Headers</EM> command displays |
| 5502 |
message text. If set, the raw message text will be displayed. This |
| 5503 |
especially affects MIME formatted email, where the entire MIME format |
| 5504 |
will be displayed. This feature similarly affects how messages are |
| 5505 |
included for the <EM>Export</EM>, <EM>Pipe</EM>, <EM>Print</EM>, <EM>Forward</EM>, |
| 5506 |
and <EM>Reply</EM> functions. |
| 5507 |
|
| 5508 |
<DT> <A NAME="enable-goto-in-file-browser"><EM>enable-goto-in-file-browser</EM></A> |
| 5509 |
|
| 5510 |
<DD> Setting this causes <EM>Alpine</EM> to offer the <EM>G Goto</EM> command in |
| 5511 |
the file browser. The Goto command allows you to explicitly type in the |
| 5512 |
desired directory. |
| 5513 |
That is the default. |
| 5514 |
<P> |
| 5515 |
|
| 5516 |
<DT> <A NAME="enable-incoming-folders"><EM>enable-incoming-folders</EM></A> |
| 5517 |
|
| 5518 |
<DD> If set, this feature defines a pseudo-folder collection called |
| 5519 |
<EM>INCOMING MESSAGE FOLDERS</EM>. |
| 5520 |
Initially, the only folder included in this collection |
| 5521 |
will be your <EM>INBOX</EM>, which will no longer show up in your default |
| 5522 |
saved-message folder collection. |
| 5523 |
<P> |
| 5524 |
This feature is displayed as "Enable Incoming Folders Collection". |
| 5525 |
<P> |
| 5526 |
|
| 5527 |
<DT> <A NAME="enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 5528 |
|
| 5529 |
<DD> This feature is only operational if you have enabled the optional |
| 5530 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 5531 |
If you do have Incoming Message Folders and you also set this feature, |
| 5532 |
then the number of Unseen messages in each folder will be displayed |
| 5533 |
in the FOLDER LIST screen for the Incoming Message Folders. |
| 5534 |
The number of Unseen messages in a folder will be displayed in parentheses |
| 5535 |
to the right of the name of each folder. |
| 5536 |
If there are no Unseen messages in a folder then only the name |
| 5537 |
is displayed, not a set of parentheses with zero inside them. |
| 5538 |
A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for |
| 5539 |
the Incoming Message Folders to cause an immediate update. |
| 5540 |
<P> |
| 5541 |
If a check for Unseen messages fails for a particular folder then Alpine |
| 5542 |
will no longer attempt to check that folder for the duration of the |
| 5543 |
session and this will be indicated by a question mark inside the |
| 5544 |
parentheses. |
| 5545 |
<P> |
| 5546 |
The features |
| 5547 |
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A>, |
| 5548 |
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>, |
| 5549 |
<A HREF="#incoming-check-list"><EM>incoming-check-list</EM></A>, |
| 5550 |
<A HREF="#incoming-check-interval"><EM>incoming-check-interval</EM></A>, |
| 5551 |
<A HREF="#incoming-check-interval-secondary"><EM>incoming-check-interval-secondary</EM></A>, and |
| 5552 |
<A HREF="#incoming-check-timeout"><EM>incoming-check-timeout</EM></A> |
| 5553 |
all affect how this feature behaves. |
| 5554 |
<P> |
| 5555 |
|
| 5556 |
<DT> <A NAME="disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> |
| 5557 |
|
| 5558 |
<DD> This feature affects the display of dates in the MESSAGE INDEX. |
| 5559 |
Normally an attempt is made to localize the dates |
| 5560 |
used in the MESSAGE INDEX display to your locale. |
| 5561 |
This is controlled with the |
| 5562 |
LC_TIME locale setting on a UNIX system. |
| 5563 |
On Windows the Regional Options control panel may be used to set the date format. |
| 5564 |
At the programming level, <EM>Alpine</EM> is using the strftime routine |
| 5565 |
to print the parts of a date. |
| 5566 |
<P> |
| 5567 |
If this feature is set, dates are displayed in English and |
| 5568 |
with the conventions of the United States. |
| 5569 |
<P> |
| 5570 |
|
| 5571 |
<DT> <A NAME="enable-jump-shortcut"><EM>enable-jump-shortcut</EM></A> |
| 5572 |
|
| 5573 |
<DD> When this feature is set you may enter a number (followed by RETURN) |
| 5574 |
and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT |
| 5575 |
screens. In other words, it obviates the need for typing the <EM>J</EM> for the |
| 5576 |
<EM>Jump</EM> command. |
| 5577 |
<P> |
| 5578 |
|
| 5579 |
<DT> <A NAME="enable-lame-list-mode"><EM>enable-lame-list-mode</EM></A> |
| 5580 |
|
| 5581 |
<DD> This feature modifies the method <EM>Alpine</EM> uses to ask your IMAP |
| 5582 |
server for folder names to display in the the FOLDER LIST screen. |
| 5583 |
It is intended to compensate for a small set of IMAP servers that |
| 5584 |
are programmed to ignore a part of the request, and thus respond |
| 5585 |
to <EM>Alpine</EM>'s query with nonsensical results. |
| 5586 |
<P> |
| 5587 |
|
| 5588 |
If you find that <EM>Alpine</EM> is erroneously displaying blank folder lists, |
| 5589 |
try enabling this feature. |
| 5590 |
<P> |
| 5591 |
|
| 5592 |
NOTE: Enabling this feature has consequences for the Goto and Save |
| 5593 |
commands. Many servers allow access to folders outside the area |
| 5594 |
reserved for your personal folders via some reserved character, |
| 5595 |
typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism |
| 5596 |
allows, at the Goto and Save prompts, quick access to folders |
| 5597 |
outside your personal folder collection without requiring a specific |
| 5598 |
collection definition. This behavior will generally not be available |
| 5599 |
when this feature is enabled. |
| 5600 |
<P> |
| 5601 |
This feature is displayed as "Compensate for Deficient IMAP servers". |
| 5602 |
<P> |
| 5603 |
|
| 5604 |
<DT> <A NAME="enable-mail-check-cue"><EM>enable-mail-check-cue</EM></A> |
| 5605 |
|
| 5606 |
<DD> If set, this will cause an asterisk to appear in the upper |
| 5607 |
left-hand corner of the screen whenever <EM>Alpine</EM> checks for new mail, and two |
| 5608 |
asterisks whenever <EM>Alpine</EM> saves (checkpoints) the state of the current |
| 5609 |
mailbox to disk. |
| 5610 |
<P> |
| 5611 |
|
| 5612 |
<DT> <A NAME="enable-mailcap-param-substitution"><EM>enable-mailcap-param-substitution</EM></A> |
| 5613 |
|
| 5614 |
<DD> If set, this will allow mailcap named parameter substitution to occur |
| 5615 |
in mailcap entries. |
| 5616 |
By default, this is turned off to prevent security problems which may occur |
| 5617 |
with some incorrect mailcap configurations. |
| 5618 |
For more information, RFC1524 and look for "named parameters" in the |
| 5619 |
text of the RFC. |
| 5620 |
<P> |
| 5621 |
This feature is displayed as "Enable Mailcap Parameter Substitution". |
| 5622 |
<P> |
| 5623 |
|
| 5624 |
<DT> <A NAME="enable-mouse-in-xterm"><EM>enable-mouse-in-xterm</EM></A> |
| 5625 |
|
| 5626 |
<DD> |
| 5627 |
This feature controls whether or not an X terminal mouse can be used with |
| 5628 |
<EM>Alpine</EM>. If set, and the $DISPLAY variable indicates that an X terminal is |
| 5629 |
being used, the left mouse button on the mouse can be used to select text |
| 5630 |
or commands. |
| 5631 |
Clicking on a command at the bottom of the screen will behave as if you had |
| 5632 |
typed that command. |
| 5633 |
Clicking on an index line will move the current message highlight to |
| 5634 |
that line. |
| 5635 |
Double-clicking on an index line will view the message. |
| 5636 |
Double-clicking on a link will view the link. |
| 5637 |
<P> |
| 5638 |
This type of mouse support will also work in some terminal emulators which are |
| 5639 |
not actually X terminals, but which have extra code to support the xterm |
| 5640 |
style mouse. |
| 5641 |
For those emulators you not only need to turn this feature on but you also |
| 5642 |
have to set the $DISPLAY environment variable even though it isn't needed |
| 5643 |
for your terminal. |
| 5644 |
That will cause <EM>Alpine</EM> to think that it is an xterm and to properly interpret the |
| 5645 |
escape sequences sent by the mouse. |
| 5646 |
<P> |
| 5647 |
Note: if this feature is set, the behavior of X terminal cut-and-paste is |
| 5648 |
also modified. It is sometimes possible to hold the shift key down while clicking |
| 5649 |
left or middle mouse buttons for the normal xterm cut/paste operations. |
| 5650 |
There is also an <EM>Alpine</EM> command to toggle this mode on or off. |
| 5651 |
The command is Ctrl-\ (Control-backslash). |
| 5652 |
<P> |
| 5653 |
|
| 5654 |
<DT> <A NAME="enable-msg-view-addresses"><EM>enable-msg-view-addresses</EM></A> |
| 5655 |
|
| 5656 |
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen. |
| 5657 |
Setting this feature causes <EM>Alpine</EM> to select possible email addresses |
| 5658 |
from the displayed text and display them in boldface for selection. |
| 5659 |
<P> |
| 5660 |
|
| 5661 |
The first available email address is displayed in inverse. This is the |
| 5662 |
"selected" address. |
| 5663 |
Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to enter the message |
| 5664 |
composition screen with the To field filled in with the selected address. |
| 5665 |
<P> |
| 5666 |
|
| 5667 |
Use the up and down arrow keys to change which of the addresses |
| 5668 |
displayed in boldface is the current selection. |
| 5669 |
<P> |
| 5670 |
This feature is displayed as "Enable Message View Address Links". |
| 5671 |
<P> |
| 5672 |
|
| 5673 |
<DT> <A NAME="enable-msg-view-attachments"><EM>enable-msg-view-attachments</EM></A> |
| 5674 |
|
| 5675 |
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen. |
| 5676 |
Setting this feature causes <EM>Alpine</EM> to present attachments in boldface. |
| 5677 |
The first available attachment is displayed in inverse. This is the |
| 5678 |
"selected" attachment. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display |
| 5679 |
the selected attachment. Use the up and down arrow keys to change which of the |
| 5680 |
attachments displayed in boldface is the current selection. |
| 5681 |
<P> |
| 5682 |
|
| 5683 |
Speaking of arrow keys, the Up and Down Arrows will select the next |
| 5684 |
and previous attachments if one is available on the screen for selection. |
| 5685 |
Otherwise, they will simply adjust the viewed text one line up or down. |
| 5686 |
<P> |
| 5687 |
|
| 5688 |
Similarly, when selectable items are present in a message, the Ctrl-F |
| 5689 |
key can be used to select the next item in the message independent |
| 5690 |
of which portion of the viewed message is currently displayed. The |
| 5691 |
Ctrl-B key can be used to select the previous item in the same way. |
| 5692 |
<P> |
| 5693 |
This feature is displayed as "Enable Message View Attachment Links". |
| 5694 |
<P> |
| 5695 |
|
| 5696 |
<DT> <A NAME="enable-msg-view-forced-arrows"><EM>enable-msg-view-forced-arrows</EM></A> |
| 5697 |
|
| 5698 |
<DD> This feature modifies Up and Down arrow key behavior in <EM>Alpine</EM>'s |
| 5699 |
"Message Text" screen when selectable Attachments, URL's, or |
| 5700 |
web-hostnames are presented. <EM>Alpine</EM>'s usual behavior is to move to |
| 5701 |
the next or previous selectable item if currently displayed or |
| 5702 |
simply to adjust the screen view by one line if the next selectable line |
| 5703 |
is off the screen. |
| 5704 |
<P> |
| 5705 |
|
| 5706 |
Setting this feature causes the Up and Down arrow keys to behave as |
| 5707 |
if no selectable items were present in the message. |
| 5708 |
<P> |
| 5709 |
|
| 5710 |
Note, the <EM>Ctrl-F</EM> (next selectable item) and |
| 5711 |
<EM>Ctrl-B</EM> (previous selectable item) functionality is unchanged. |
| 5712 |
<P> |
| 5713 |
This feature is displayed as "Enable Message View Forced Arrows". |
| 5714 |
<P> |
| 5715 |
|
| 5716 |
<DT> <A NAME="enable-msg-view-urls"><EM>enable-msg-view-urls</EM></A> |
| 5717 |
|
| 5718 |
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen. |
| 5719 |
When this feature is set (the default) <EM>Alpine</EM> will select possible URLs from the |
| 5720 |
displayed text and display them in boldface for selection. |
| 5721 |
<P> |
| 5722 |
|
| 5723 |
The first available URL is displayed in inverse. This is the |
| 5724 |
"selected" URL. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display |
| 5725 |
the selected URL via either built-in means as with <CODE>mailto:</CODE>, |
| 5726 |
<CODE>imap:</CODE>, <CODE>news:</CODE>, and <CODE>nntp:</CODE>, |
| 5727 |
or via an external application as defined |
| 5728 |
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable. |
| 5729 |
<P> |
| 5730 |
|
| 5731 |
Use the up and down arrow keys to change which of the URLs displayed in boldface |
| 5732 |
is the current selection. |
| 5733 |
<P> |
| 5734 |
This feature is displayed as "Enable Message View URL Links". |
| 5735 |
<P> |
| 5736 |
|
| 5737 |
<DT> <A NAME="enable-msg-view-web-hostnames"><EM>enable-msg-view-web-hostnames</EM></A> |
| 5738 |
|
| 5739 |
<DD> This feature modifies the behavior of <EM>Alpine</EM>'s "Message Text" screen. |
| 5740 |
When this feature is set (the default) <EM>Alpine</EM> will select possible web hostnames |
| 5741 |
from the displayed text and display them in boldface for selection. |
| 5742 |
<P> |
| 5743 |
|
| 5744 |
The first available hostname is displayed in inverse. This is the |
| 5745 |
"selected" hostname. Pressing <EM>RETURN</EM> will cause <EM>Alpine</EM> to display |
| 5746 |
the selected hostname via an external application as defined |
| 5747 |
by the <A HREF="#url-viewers"><EM>url-viewers</EM></A> variable. |
| 5748 |
<P> |
| 5749 |
|
| 5750 |
Use the up and down arrow keys to change which of the hostnames displayed in |
| 5751 |
boldface is the current selection. |
| 5752 |
<P> |
| 5753 |
This feature is displayed as "Enable Message View Web Hostname Links". |
| 5754 |
<P> |
| 5755 |
|
| 5756 |
<DT> <A NAME="enable-multiple-newsrcs"><EM>enable-multiple-newsrcs</EM></A> |
| 5757 |
|
| 5758 |
<DD> This feature makes it so <EM>Alpine</EM> can use multiple newsrcs based on |
| 5759 |
the news server being connected to, which allows for separate lists |
| 5760 |
of subscribed-to newsgroups. When this feature is not set, there is only |
| 5761 |
one list of newsgroups. |
| 5762 |
<P> |
| 5763 |
Under this feature, the name of a newsrc is based on the news server. |
| 5764 |
For example, if your <a href="#newsrc-path">newsrc-path</a> |
| 5765 |
is set to ".newsrc", and the news server you are connecting to is |
| 5766 |
news.example.com, then the newsrc to be used is .newsrc-news.example.com. |
| 5767 |
Setting this feature for the first time will allow for the option of using |
| 5768 |
your old newsrc the next time you read news. |
| 5769 |
<P> |
| 5770 |
If this feature is set, then the feature |
| 5771 |
<A HREF="#mult-newsrc-hostnames-as-typed">Mult-Newsrc-Hostnames-As-Typed</A> |
| 5772 |
also may affect the name of the newsrc file that is used. |
| 5773 |
|
| 5774 |
<P> |
| 5775 |
|
| 5776 |
<DT> <A NAME="enable-newmail-in-xterm-icon"><EM>enable-newmail-in-xterm-icon</EM></A> |
| 5777 |
|
| 5778 |
<DD> This feature controls whether or not <EM>Alpine</EM> will attempt to announce new |
| 5779 |
mail arrival when it is running in an X terminal window and that window |
| 5780 |
is iconified. |
| 5781 |
If set, and the <CODE>$DISPLAY</CODE> variable indicates that an X |
| 5782 |
terminal is being used, <EM>Alpine</EM> will send appropriate escape sequences to |
| 5783 |
the X terminal to modify the label on <EM>Alpine</EM>'s icon to indicate that new |
| 5784 |
mail has arrived. <EM>Alpine</EM> will also modify the <EM>Alpine</EM> window's title to |
| 5785 |
indicate new mail. |
| 5786 |
See also <A HREF="#enable-newmail-short-text-in-icon">Enable-Newmail-Short-Text-in-Icon</A>. |
| 5787 |
<P> |
| 5788 |
|
| 5789 |
<DT> <A NAME="enable-newmail-short-text-in-icon"><EM>enable-newmail-short-text-in-icon</EM></A> |
| 5790 |
|
| 5791 |
<DD> This feature controls the text to be displayed in an icon in the event |
| 5792 |
of a new message arrival. Normally, the message will |
| 5793 |
be the one that is displayed on the screen. This feature shortens the |
| 5794 |
message to a count of the number of new messages in brackets. This may be |
| 5795 |
more useful for those who use the window's title bar in the task bar as a |
| 5796 |
new mail indicator. This feature is only useful if the |
| 5797 |
<A HREF="#enable-newmail-in-xterm-icon">Enable-Newmail-in-Xterm-Icon</A> |
| 5798 |
is also set. Like the Enable-Newmail-in-Xterm-Icon |
| 5799 |
feature, this feature is only relevant when run in an xterm environment. |
| 5800 |
<P> |
| 5801 |
|
| 5802 |
<DT> <A NAME="enable-partial-match-lists"><EM>enable-partial-match-lists</EM></A> |
| 5803 |
|
| 5804 |
<DD> This feature affects the subcommands available when <EM>Sav</EM>ing |
| 5805 |
or Opening a new folder. If set, the subcommand <EM>^X ListMatches</EM> will be |
| 5806 |
available. This command allows you to type in a substring of the folder |
| 5807 |
you are looking for and when you type <EM>^X</EM> it will display all folders |
| 5808 |
which contain that substring in their names. |
| 5809 |
This feature is set by default. |
| 5810 |
<P> |
| 5811 |
|
| 5812 |
<DT> <A NAME="enable-print-via-y-command"><EM>enable-print-via-y-command</EM></A> |
| 5813 |
|
| 5814 |
<DD> By default, <EM>Alpine</EM>'s print command is available by pressing the <EM>%</EM> |
| 5815 |
key. In older versions of <EM>Pine</EM>, the print command was accessed by |
| 5816 |
pressing the <EM>Y</EM> key. |
| 5817 |
<P> |
| 5818 |
|
| 5819 |
Enabling this feature will cause <EM>Alpine</EM> to recognize both the old |
| 5820 |
command, <EM>Y</EM>, and the new <EM>%</EM> method for invoking |
| 5821 |
printing. Note, key menu labels are not changed as a result of |
| 5822 |
enabling this feature. |
| 5823 |
<P> |
| 5824 |
|
| 5825 |
<DT> <A NAME="enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A> |
| 5826 |
|
| 5827 |
<DD> This feature affects the Reply command's "Include original message |
| 5828 |
in Reply?" prompt. When enabled, it causes the |
| 5829 |
"Edit Indent String" sub-command to appear which allows |
| 5830 |
you to edit the string <EM>Alpine</EM> would otherwise use to denote included |
| 5831 |
text from the message being replied to.<P> |
| 5832 |
|
| 5833 |
Thus, you can change <EM>Alpine</EM>'s default message quote character (usually |
| 5834 |
an angle bracket) on a per message basis. So you could change your quoted message to |
| 5835 |
look, for example, like this:<p> |
| 5836 |
|
| 5837 |
<pre>On Tues, 26 Jan 1999, John Q. Smith wrote: |
| 5838 |
|
| 5839 |
John: I just wanted to say hello and to congratulate you |
| 5840 |
John: on a job well done!</pre><p> |
| 5841 |
|
| 5842 |
The configuration option |
| 5843 |
<A HREF="#reply-ind-str">"reply-indent-string"</A> |
| 5844 |
may be used to change what appears as the default string to be edited. |
| 5845 |
<P> |
| 5846 |
NOTE: Edited reply-indent-strings only apply to the message |
| 5847 |
currently being replied to. |
| 5848 |
<P> |
| 5849 |
|
| 5850 |
<DT> <A NAME="enable-rules-under-take"><EM>enable-rules-under-take</EM></A> |
| 5851 |
|
| 5852 |
<DD> Normally, the Take command takes addresses from a message and helps you |
| 5853 |
put them into your Address Book. |
| 5854 |
If you use Rules for Indexcolors, Roles, Filtering, or Scoring; |
| 5855 |
you may find it useful |
| 5856 |
to be able to Take information from a message's headers and put it into |
| 5857 |
a new Rule. |
| 5858 |
When this feature is set, you will be given an extra prompt which gives |
| 5859 |
you the choice to Take into the Address Book or Take into a rule. |
| 5860 |
<P> |
| 5861 |
This feature is displayed as "Enable Take Rules". |
| 5862 |
<P> |
| 5863 |
|
| 5864 |
<DT> <A NAME="enable-search-and-replace"><EM>enable-search-and-replace</EM></A> |
| 5865 |
|
| 5866 |
<DD> If set <EM>Alpine</EM>'s composer offers the <EM>R Replace</EM> command |
| 5867 |
option inside the <EM>W WhereIs</EM> command. |
| 5868 |
<P> |
| 5869 |
|
| 5870 |
<DT> <A NAME="enable-sigdashes"><EM>enable-sigdashes</EM></A> |
| 5871 |
|
| 5872 |
<DD> If set and a <EM>signature-file</EM> exists, the line consisting of |
| 5873 |
the three characters "<CODE>-- </CODE>" (dash dash space) is included |
| 5874 |
before the signature. |
| 5875 |
This only happens if the signature doesn't already contain such a line. |
| 5876 |
<P> |
| 5877 |
In addition, when you Reply or Followup to a message containing one of |
| 5878 |
these special lines and choose to include its text, <EM>Alpine</EM> will observe |
| 5879 |
the convention of not including text beyond the special line in your |
| 5880 |
reply. |
| 5881 |
<P> |
| 5882 |
|
| 5883 |
<DT> <A NAME="enable-suspend"><EM>enable-suspend</EM></A> |
| 5884 |
|
| 5885 |
<DD> Setting this feature will allow you to type <EM>^Z</EM> |
| 5886 |
and temporarily suspend <EM>Alpine</EM>. Not available on <EM>PC-Alpine</EM>. |
| 5887 |
<P> |
| 5888 |
|
| 5889 |
<DT> <A NAME="enable-tab-completion"><EM>enable-tab-completion</EM></A> |
| 5890 |
|
| 5891 |
<DD> This feature enables the <EM>TAB</EM> key when |
| 5892 |
at a prompt for a filename. In this |
| 5893 |
case, <EM>TAB</EM> will cause the |
| 5894 |
partial name already entered to be automatically |
| 5895 |
completed, provided the partial name is unambiguous. |
| 5896 |
This feature is set by default. |
| 5897 |
<P> |
| 5898 |
Similarly, this feature also enables TAB completion of address book |
| 5899 |
nicknames when at a prompt for a nickname, |
| 5900 |
or when typing in an address field in the composer. |
| 5901 |
<P> |
| 5902 |
|
| 5903 |
<DT> <A NAME="enable-take-export"><EM>enable-take-export</EM></A> |
| 5904 |
|
| 5905 |
<DD> Normally, the Take command takes addresses from a message and helps you |
| 5906 |
put them into your Address Book. |
| 5907 |
When this feature is set, you will be given an extra prompt which gives you |
| 5908 |
the choice to Take addresses into a file instead of your Address |
| 5909 |
Book. |
| 5910 |
Only the user@domain_name part of the address is put in the file. |
| 5911 |
<P> |
| 5912 |
|
| 5913 |
<DT> <A NAME="enable-tray-icon"><EM>enable-tray-icon</EM></A> |
| 5914 |
|
| 5915 |
<DD> <EM>PC-Alpine</EM> only. This option restores a behavior of |
| 5916 |
previous versions of PC-Alpine. These |
| 5917 |
versions, when started, installed a PC-Alpine icon in the notification |
| 5918 |
tray of Window's Taskbar. The primary use of this icon was to indicate |
| 5919 |
new mail arrival by turning red (while the Taskbar icon remained green). |
| 5920 |
Additionally, the icon now changes to yellow to signify that a mail folder |
| 5921 |
has been closed unexpectedly. |
| 5922 |
<P> |
| 5923 |
Rather than add another icon to the Taskbar, this version of PC-Alpine will |
| 5924 |
color its Taskbar entry's icon red (as well as the icon in the Window |
| 5925 |
Title). This feature is only provided for backwards compatibility. |
| 5926 |
<P> |
| 5927 |
|
| 5928 |
<DT> <A NAME="enable-unix-pipe-cmd"><EM>enable-unix-pipe-cmd</EM></A> |
| 5929 |
|
| 5930 |
<DD> This feature enables the <EM>| Pipe</EM> command |
| 5931 |
that sends the current message |
| 5932 |
to the specified Unix command for external processing. |
| 5933 |
<P> |
| 5934 |
This feature is displayed as "Enable Unix Pipe Command". |
| 5935 |
<P> |
| 5936 |
|
| 5937 |
<DT> <A NAME="enable-verbose-smtp-posting"><EM>enable-verbose-smtp-posting</EM></A> |
| 5938 |
|
| 5939 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s message sending. When enabled, |
| 5940 |
<EM>Alpine</EM> will send a <CODE>VERB</CODE> (i.e., VERBose) command |
| 5941 |
early in the posting process |
| 5942 |
intended to cause the server SMTP to provide a more detailed account of |
| 5943 |
the transaction. This feature is typically only useful to system |
| 5944 |
administrators and other support personnel as an aid in troubleshooting |
| 5945 |
problems. |
| 5946 |
|
| 5947 |
Note, this feature relies on a specific capability of the system's mail |
| 5948 |
transport agent or configured <A HREF="#smtp-server"><EM>smtp-server</EM></A>. |
| 5949 |
<P> |
| 5950 |
|
| 5951 |
<DT> <A NAME="expanded-view-of-addressbooks"><EM>expanded-view-of-addressbooks</EM></A> |
| 5952 |
|
| 5953 |
<DD> If multiple address books (either personal or global) are defined, and you |
| 5954 |
wish to have them all expanded implicitly upon entering the ADDRESS BOOK |
| 5955 |
screen, then set this feature. This feature will have no effect unless the |
| 5956 |
feature |
| 5957 |
<A HREF="#combined-addrbook-display"><EM>combined-addrbook-display</EM></A> |
| 5958 |
is also set. |
| 5959 |
<P> |
| 5960 |
|
| 5961 |
<DT> <A NAME="expanded-view-of-distribution-lists"><EM>expanded-view-of-distribution-lists</EM></A> |
| 5962 |
|
| 5963 |
<DD> If this feature is set, then distribution lists in the address book |
| 5964 |
screen will always be expanded automatically. |
| 5965 |
<P> |
| 5966 |
|
| 5967 |
<DT> <A NAME="expanded-view-of-folders"><EM>expanded-view-of-folders</EM></A> |
| 5968 |
|
| 5969 |
<DD> If multiple folder collections are defined, and you |
| 5970 |
wish to have them all expanded implicitly upon entering the FOLDER LIST |
| 5971 |
screen, then set this feature. This feature will have no effect unless the |
| 5972 |
feature |
| 5973 |
<A HREF="#combined-folder-display"><EM>combined-folder-display</EM></A> |
| 5974 |
is also set. |
| 5975 |
<P> |
| 5976 |
|
| 5977 |
<DT> <A NAME="expose-hidden-config"><EM>expose-hidden-config</EM></A> |
| 5978 |
|
| 5979 |
<DD> The purpose of this feature is to allow you to change configuration |
| 5980 |
features and variables which are normally hidden. |
| 5981 |
This is particularly useful if you are using a remote configuration file, |
| 5982 |
where it is difficult to edit the file manually, but it may also be used |
| 5983 |
on a local pinerc configuration file. |
| 5984 |
<P> |
| 5985 |
If set, most configuration variables and features which are normally |
| 5986 |
hidden from view will show up in the Setup/Configuration screen. |
| 5987 |
They will be at the bottom of the configuration screen. |
| 5988 |
You can find them by searching for the word "hidden". |
| 5989 |
<P> |
| 5990 |
|
| 5991 |
Note that this is an advanced feature which should be used with care. |
| 5992 |
The reason that this part of the configuration is normally hidden is because |
| 5993 |
there is a significant potential for causing problems if you change these |
| 5994 |
variables. |
| 5995 |
If something breaks after a change try changing it back to see if that is |
| 5996 |
what is causing the problem. |
| 5997 |
There are also some variables which are normally hidden because they are |
| 5998 |
manipulated through <EM>Alpine</EM> in other ways. |
| 5999 |
For example, the "address-book" variable is normally set using |
| 6000 |
the Setup/AddressBooks screen, so there is little reason to edit it directly. |
| 6001 |
The "incoming-folders" variable is normally changed by using |
| 6002 |
the Add, Delete, and Rename commands in the FOLDER LIST screen, |
| 6003 |
and the "last-time-prune-questioned" variable is normally used |
| 6004 |
internally by <EM>Alpine</EM> and not set directly by the user. |
| 6005 |
<P> |
| 6006 |
|
| 6007 |
<DT> <A NAME="expunge-only-manually"><EM>expunge-only-manually</EM></A> |
| 6008 |
|
| 6009 |
<DD> Normally, when you close a folder which contains deleted messages you are |
| 6010 |
asked if you want to expunge those messages from the folder permanently. |
| 6011 |
If this feature is set, you won't be asked and the deleted messages will |
| 6012 |
remain in the folder. |
| 6013 |
If you choose to set this feature you will have to expunge the |
| 6014 |
messages manually using the eXpunge command, which you can use while |
| 6015 |
in the MESSAGE INDEX screen. |
| 6016 |
If you do not expunge deleted messages the size of your |
| 6017 |
folder will continue to increase until you are out of disk space. |
| 6018 |
<P> |
| 6019 |
|
| 6020 |
<DT> <A NAME="expunge-wo-confirm"><EM>expunge-without-confirm</EM></A> |
| 6021 |
|
| 6022 |
<DD> If set, you will not be prompted to confirm your intent before |
| 6023 |
the expunge takes place. Actually, you will still be prompted for confirmation |
| 6024 |
if the folder is not the <EM>INBOX</EM> folder or another folder in the |
| 6025 |
Incoming Folders collection. See the <EM>expunge-without-confirm-everywhere</EM> |
| 6026 |
feature which follows. |
| 6027 |
<P> |
| 6028 |
This feature is displayed as "Expunge Without Confirming". |
| 6029 |
<P> |
| 6030 |
|
| 6031 |
<DT> <A NAME="expunge-without-confirm-everywhere"><EM>expunge-without-confirm-everywhere</EM></A> |
| 6032 |
|
| 6033 |
<DD> The regular <EM>expunge-without-confirm</EM> feature actually only |
| 6034 |
works for the <EM>INBOX</EM> folder and for other folders in the "Incoming |
| 6035 |
Folders" collection. If this feature is set then you also won't be prompted |
| 6036 |
to confirm expunges for all other folders. |
| 6037 |
<P> |
| 6038 |
This feature is displayed as "Expunge Without Confirming Everywhere". |
| 6039 |
<P> |
| 6040 |
|
| 6041 |
<DT> <A NAME="fcc-on-bounce"><EM>fcc-on-bounce</EM></A> |
| 6042 |
|
| 6043 |
<DD> If set, normal Fcc (File Carbon Copy) processing will be |
| 6044 |
done for bounced messages, |
| 6045 |
just as if you had composed a message to the address you are |
| 6046 |
bouncing to. If not set, no Fcc of the message will be saved. |
| 6047 |
<P> |
| 6048 |
This feature is displayed as "Include Fcc When Bouncing Messages". |
| 6049 |
<P> |
| 6050 |
|
| 6051 |
<DT> <A NAME="fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A> |
| 6052 |
|
| 6053 |
<DD> This features controls an aspect of <EM>Alpine</EM>'s composer. |
| 6054 |
The only time this feature will be used is if you attempt to send mail |
| 6055 |
which has no recipients but does have an Fcc. |
| 6056 |
Normally, <EM>Alpine</EM> will ask if you really mean to copy the message only to |
| 6057 |
the Fcc. |
| 6058 |
That is, it asks if you really meant to have no recipients. |
| 6059 |
If this feature is set, you |
| 6060 |
will <B>not</B> be prompted to confirm your intent to make only a copy |
| 6061 |
of a message with no recipients. |
| 6062 |
<P> |
| 6063 |
This feature is closely related to |
| 6064 |
<A HREF="#warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A>. |
| 6065 |
The difference between this feature and that feature is that this feature |
| 6066 |
considers a Bcc to be a recipient while that feature will ask for confirmation |
| 6067 |
even if there is a Bcc when there is no To, Cc, or Newsgroup. |
| 6068 |
The default values also differ. This feature defaults to asking the question |
| 6069 |
and you have to turn it off. |
| 6070 |
The warn-if-blank-to-and-cc-and-newsgroups feature defaults to not asking |
| 6071 |
unless you turn it on. |
| 6072 |
<P> |
| 6073 |
This feature is displayed as "Send to Fcc Only Without Confirming". |
| 6074 |
<P> |
| 6075 |
|
| 6076 |
<DT> <A NAME="fcc-without-attachments"><EM>fcc-without-attachments</EM></A> |
| 6077 |
|
| 6078 |
<DD> This features controls the way FCC's (File Carbon Copies) are |
| 6079 |
made of the messages you send. |
| 6080 |
|
| 6081 |
<P> |
| 6082 |
Normally, <EM>Alpine</EM> saves an exact copy of your message as it was sent. |
| 6083 |
When this feature is enabled, the "body" of the message |
| 6084 |
you send (the text you type in the composer) is preserved in the |
| 6085 |
copy as before, however all attachments are replaced with text |
| 6086 |
explaining what had been sent rather than the attachments themselves. |
| 6087 |
|
| 6088 |
<P> |
| 6089 |
This feature also affects <EM>Alpine</EM>'s "Send ?" confirmation prompt |
| 6090 |
in that a new "^F Fcc Attchmnts" option becomes available which |
| 6091 |
allows you to interactively set whether or not attachments are saved |
| 6092 |
to the Fcc'd copy. |
| 6093 |
<P> |
| 6094 |
This feature is displayed as "Fcc Does Not Include Attachments". |
| 6095 |
<P> |
| 6096 |
|
| 6097 |
<DT> <A NAME="force-arrow-cursor"><EM>force-arrow-cursor</EM></A> |
| 6098 |
|
| 6099 |
<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display routine. |
| 6100 |
If set, the normal inverse-video cursor will be |
| 6101 |
replaced by a simple "arrow" cursor, which normally occupies the |
| 6102 |
second column of the index display. |
| 6103 |
<P> |
| 6104 |
This is the same index cursor you get if you turn on |
| 6105 |
<A HREF="#assume-slow-link">Assume-Slow-Link</A>, but the index |
| 6106 |
line coloring will still be present if this feature is turned on and |
| 6107 |
Assume-Slow-Link is off. |
| 6108 |
<P> |
| 6109 |
An alternative version of the Arrow cursor is available by including the |
| 6110 |
ARROW |
| 6111 |
token in the |
| 6112 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option. |
| 6113 |
<P> |
| 6114 |
It ought to be the case that this feature also affects the ATTACHMENT INDEX, |
| 6115 |
but that is not implemented. |
| 6116 |
<P> |
| 6117 |
|
| 6118 |
<DT> <A NAME="hide-nntp-path"><EM>hide-nntp-path</EM></A> |
| 6119 |
|
| 6120 |
<DD> Normally the Path header that <EM>Alpine</EM> generates when posting to a newsgroup |
| 6121 |
contains the name of the computer from which the message is being sent and |
| 6122 |
the user name. |
| 6123 |
Some believe that this information is used by spammers. |
| 6124 |
If this feature is set, that information will be replaced with the text |
| 6125 |
<P> |
| 6126 |
<CENTER><SAMP>not-for-mail</SAMP></CENTER> |
| 6127 |
<P> |
| 6128 |
instead. |
| 6129 |
<P> |
| 6130 |
It should be noted that many servers being connected to will still reveal |
| 6131 |
the information that this feature attempts to protect. |
| 6132 |
<P> |
| 6133 |
<DT> <A NAME="include-attachments-in-reply"><EM>include-attachments-in-reply</EM></A> |
| 6134 |
|
| 6135 |
<DD> If set, any MIME |
| 6136 |
attachments that were part of the original message will automatically be |
| 6137 |
included in a <EM>Reply</EM>. |
| 6138 |
<P> |
| 6139 |
|
| 6140 |
<DT> <A NAME="include-header-in-reply"><EM>include-header-in-reply</EM></A> |
| 6141 |
|
| 6142 |
<DD> If set, and a |
| 6143 |
message being replied to is included in the <EM>Reply</EM>, |
| 6144 |
then headers from that |
| 6145 |
message will also be part of the reply. |
| 6146 |
<P> |
| 6147 |
|
| 6148 |
<DT> <A NAME="include-text-in-reply"><EM>include-text-in-reply</EM></A> |
| 6149 |
|
| 6150 |
<DD> Normally, <EM>Alpine</EM> will ask whether you |
| 6151 |
wish to include the original message in your <EM>Reply</EM>. |
| 6152 |
If this feature is set and the feature |
| 6153 |
<A HREF="#enable-reply-indent-string-editing"><EM>enable-reply-indent-string-editing</EM></A> |
| 6154 |
is <EM>not</EM> set, then the original message will be included in the reply |
| 6155 |
automatically, without prompting. |
| 6156 |
<P> |
| 6157 |
|
| 6158 |
<DT> <A NAME="incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A> |
| 6159 |
|
| 6160 |
<DD> This option has no effect unless the feature |
| 6161 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 6162 |
is set, which in turn has no effect unless |
| 6163 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 6164 |
is set. |
| 6165 |
<P> |
| 6166 |
When incoming folder checking is turned on the default is to display |
| 6167 |
the number of unseen messages in each folder. |
| 6168 |
More precisely, it is the number of undeleted unseen messages. |
| 6169 |
Using this option you may also display the total number of messages |
| 6170 |
in each folder. |
| 6171 |
Instead of a single number representing the number of unseen messages |
| 6172 |
you will get two numbers separated by a slash character. |
| 6173 |
The first is the number of unseen messages and the second is the |
| 6174 |
total number of messages. |
| 6175 |
<P> |
| 6176 |
You may also use the recent message count instead of the unseen message |
| 6177 |
count by turning on the feature |
| 6178 |
<A HREF="#incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A>. |
| 6179 |
<P> |
| 6180 |
|
| 6181 |
<DT> <A NAME="incoming-checking-uses-recent"><EM>incoming-checking-uses-recent</EM></A> |
| 6182 |
|
| 6183 |
<DD> This option has no effect unless the feature |
| 6184 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 6185 |
is set, which in turn has no effect unless |
| 6186 |
<A HREF="#inc-fold"><EM>incoming-folders</EM></A> |
| 6187 |
is set. |
| 6188 |
<P> |
| 6189 |
When incoming folder checking is turned on the default is to display |
| 6190 |
the number of unseen messages in each folder. |
| 6191 |
More precisely, it is the number of undeleted unseen messages. |
| 6192 |
Using this option you may display the number of recent messages instead |
| 6193 |
of the number of unseen messages. |
| 6194 |
A message is only counted as recent if this is the first session to |
| 6195 |
see it, so the recent count might be less than the unseen count. |
| 6196 |
The difference between the two would be accounted for by the unseen messages |
| 6197 |
in the folder which were there previously but have not been looked at yet. |
| 6198 |
<P> |
| 6199 |
If you simultaneously run more than one email client at a time |
| 6200 |
(for example, you run more than one <EM>Alpine</EM> in parallel) then turning |
| 6201 |
this feature on can cause some confusion. |
| 6202 |
The confusion stems from the fact that each message is only considered to be |
| 6203 |
recent in one session. |
| 6204 |
That means that the counts of new messages may be different in the two |
| 6205 |
<EM>Alpine</EM>s running side by side, because each incoming message will only be |
| 6206 |
counted as recent in one of the two sessions. |
| 6207 |
<P> |
| 6208 |
You may also display the total number of messages |
| 6209 |
in each folder by using the |
| 6210 |
<A HREF="#incoming-checking-includes-total"><EM>incoming-checking-includes-total</EM></A> |
| 6211 |
option. |
| 6212 |
<P> |
| 6213 |
|
| 6214 |
<DT> <A NAME="ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A> |
| 6215 |
|
| 6216 |
<DD> This is only available if <EM>Alpine</EM> was linked with an LDAP library |
| 6217 |
when it was compiled. |
| 6218 |
If both the per-directory-server option |
| 6219 |
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A> |
| 6220 |
and this feature are set, |
| 6221 |
then when an implicit directory lookup is done from the |
| 6222 |
composer you will automatically be prompted to add the result of the |
| 6223 |
directory lookup to your address book. |
| 6224 |
<P> |
| 6225 |
This feature is displayed as "LDAP Result to Addressbook Add". |
| 6226 |
<P> |
| 6227 |
|
| 6228 |
<DT> <A NAME="maildrops-preserve-state"><EM>maildrops-preserve-state</EM></A> |
| 6229 |
|
| 6230 |
<DD> |
| 6231 |
This feature affects the way |
| 6232 |
<A HREF="config-notes.html#maildrop">Mail Drops</A> work. |
| 6233 |
Normally, when mail is moved from a Mail Drop folder to a destination |
| 6234 |
folder, the state changes that have taken place since the mail was originally |
| 6235 |
delivered are lost. |
| 6236 |
Any Seen/New, Answered, Important/Flagged state that has changed will be |
| 6237 |
ignored. |
| 6238 |
All of the mail will be considered unSeen, unAnswered, and unImportant after |
| 6239 |
it is moved. |
| 6240 |
<P> |
| 6241 |
If this feature is set, then the state changes will not be lost. |
| 6242 |
<P> |
| 6243 |
In any case, messages which are already marked Deleted when the |
| 6244 |
mail is to be copied from the Mail Drop will be ignored. |
| 6245 |
<P> |
| 6246 |
|
| 6247 |
<DT> <A NAME="mark-fcc-seen"><EM>mark-fcc-seen</EM></A> |
| 6248 |
|
| 6249 |
<DD> This features controls the way FCCs (File Carbon Copies) are |
| 6250 |
made of the messages you send. |
| 6251 |
Normally, when <EM>Alpine</EM> saves a copy of a message you sent as an Fcc, that |
| 6252 |
copy will be marked as Unseen. |
| 6253 |
When you look at the folder it was saved in the message will appear to |
| 6254 |
be a New message until you read it. |
| 6255 |
When this feature is enabled, the message will be marked as having |
| 6256 |
been Seen. |
| 6257 |
<P> |
| 6258 |
|
| 6259 |
<DT> <A NAME="mark-for-cc"><EM>mark-for-cc</EM></A> |
| 6260 |
|
| 6261 |
<DD> This feature affects <EM>Alpine</EM>'s MESSAGE INDEX display. |
| 6262 |
By default, a '+' is displayed in the first column if the |
| 6263 |
message is addressed directly to you. |
| 6264 |
When this feature is set and the message is not addressed to you, then a |
| 6265 |
'-' character is displayed if the message is instead Cc'd directly |
| 6266 |
to you. |
| 6267 |
<P> |
| 6268 |
|
| 6269 |
<DT> <A NAME="mult-newsrc-hostnames-as-typed"><EM>mult-newsrc-hostnames-as-typed</EM></A> |
| 6270 |
|
| 6271 |
<DD> This feature will be of little use to most users. |
| 6272 |
It has no effect unless the feature |
| 6273 |
<A HREF="#enable-multiple-newsrcs">Enable-Multiple-Newsrcs</A> |
| 6274 |
is set. |
| 6275 |
|
| 6276 |
When the Enable-Multiple-Newsrcs feature is set |
| 6277 |
then the setting of this feature may have an effect on the names of the |
| 6278 |
newsrc files used. |
| 6279 |
Normally, the name of the news server will be canonicalized before it is |
| 6280 |
used in the newsrc file name. |
| 6281 |
For example, if you type the news server name |
| 6282 |
|
| 6283 |
<P> |
| 6284 |
<CENTER><SAMP>servername</SAMP></CENTER> |
| 6285 |
<P> |
| 6286 |
|
| 6287 |
it is likely that the canonical name will be something like |
| 6288 |
|
| 6289 |
<P> |
| 6290 |
<CENTER><SAMP>servername.example.com</SAMP></CENTER> |
| 6291 |
<P> |
| 6292 |
|
| 6293 |
Or it may be the case that |
| 6294 |
|
| 6295 |
<P> |
| 6296 |
<CENTER><SAMP>servername.example.com</SAMP></CENTER> |
| 6297 |
<P> |
| 6298 |
|
| 6299 |
is really an alias (a DNS CNAME) for |
| 6300 |
|
| 6301 |
<P> |
| 6302 |
<CENTER><SAMP>othername.example.com</SAMP></CENTER> |
| 6303 |
<P> |
| 6304 |
|
| 6305 |
If this feature is not set, then the canonicalized names will be used. |
| 6306 |
If this feature is set, then the name you typed in (or put in your |
| 6307 |
configuration) will be used. |
| 6308 |
<P> |
| 6309 |
This feature is displayed as "Multiple Newsrc Hostnames as Typed". |
| 6310 |
<P> |
| 6311 |
|
| 6312 |
<DT> <A NAME="news-approximates-new-status"><EM>news-approximates-new-status</EM></A> |
| 6313 |
|
| 6314 |
<DD> This feature causes certain messages to be marked as <EM>New</EM> in the |
| 6315 |
MESSAGE INDEX of newsgroups. |
| 6316 |
This feature is set by default. |
| 6317 |
<P> |
| 6318 |
|
| 6319 |
When opening a newsgroup, <EM>Alpine</EM> will consult |
| 6320 |
your <EM>newsrc</EM> file and |
| 6321 |
determine the last message you have previously disposed of via the <EM>D</EM> |
| 6322 |
key. If this feature is set, any subsequent messages will be shown in the |
| 6323 |
Index with an <EM>N</EM>, and the first of these messages will be highlighted. |
| 6324 |
Although this is only an approximation of true <EM>New</EM> or <EM>Unseen</EM> |
| 6325 |
status, it provides a useful cue to distinguish more-or-less recent |
| 6326 |
messages from those you have seen previously, but are not yet ready to |
| 6327 |
mark deleted. |
| 6328 |
<P> |
| 6329 |
|
| 6330 |
Background: your <EM>newsrc</EM> file (used to store message status information |
| 6331 |
for newsgroups) is only capable of storing a single flag, and <EM>Alpine</EM> uses |
| 6332 |
this to record whether or not you are "done with" a message, as |
| 6333 |
indicated by marking the message as <EM>Deleted</EM>. Unfortunately, this |
| 6334 |
means that <EM>Alpine</EM> has no way to record exactly which messages you have |
| 6335 |
previously seen, so it normally does not show the <EM>N</EM> status flag for |
| 6336 |
any messages in a newsgroup. This feature enables a starting |
| 6337 |
<I>approximation</I> of seen/unseen status that may be useful. |
| 6338 |
<P> |
| 6339 |
|
| 6340 |
<DT> <A NAME="news-deletes-across-groups"><EM>news-deletes-across-groups</EM></A> |
| 6341 |
|
| 6342 |
<DD> This feature controls what <EM>Alpine</EM> does when you delete a |
| 6343 |
message in a newsgroup that appears in more than one newsgroup. |
| 6344 |
Such a message is sometimes termed a "crossposting" |
| 6345 |
in that it was posted across several newsgroups. |
| 6346 |
|
| 6347 |
<P> |
| 6348 |
<EM>Alpine</EM>'s default behavior when you delete such a message is to remove |
| 6349 |
only the copy in the current newsgroup from view when you use the |
| 6350 |
"Exclude" command or the next time you visit the newsgroup. |
| 6351 |
|
| 6352 |
<P> |
| 6353 |
Enabling this feature causes <EM>Alpine</EM> to remove every occurrence of the |
| 6354 |
message from all newsgroups it appears in and to which you are |
| 6355 |
subscribed. |
| 6356 |
|
| 6357 |
<P> |
| 6358 |
NOTE: As currently implemented, enabling this feature may increase the |
| 6359 |
time it takes the Expunge command and newsgroup closing to complete. |
| 6360 |
<P> |
| 6361 |
|
| 6362 |
<DT> <A NAME="news-offers-catchup-on-close"><EM>news-offers-catchup-on-close</EM></A> |
| 6363 |
|
| 6364 |
<DD> This feature controls what <EM>Alpine</EM> does as it closes a newsgroup. |
| 6365 |
When set, <EM>Alpine</EM> will offer to delete all messages from the newsgroup |
| 6366 |
as you are quitting <EM>Alpine</EM> or opening a new folder. |
| 6367 |
|
| 6368 |
<P> |
| 6369 |
This feature is useful if you typically read all the interesting messages |
| 6370 |
in a newsgroup each time you open it. This feature saves you from |
| 6371 |
having to delete each message in a newsgroup as you read it or from |
| 6372 |
selecting all the messages and doing an |
| 6373 |
aggregate delete before you move on to the next folder or newsgroup. |
| 6374 |
<P> |
| 6375 |
|
| 6376 |
<DT> <A NAME="news-post-without-validation"><EM>news-post-without-validation</EM></A> |
| 6377 |
|
| 6378 |
<DD> This feature controls whether the NNTP server is queried as newsgroups |
| 6379 |
are entered for posting. Validation over slow links (e.g. dialup using |
| 6380 |
SLIP or PPP) can cause delays. Set this feature to eliminate such delays. |
| 6381 |
<P> |
| 6382 |
|
| 6383 |
<DT> <A NAME="news-read-in-newsrc-order"><EM>news-read-in-newsrc-order</EM></A> |
| 6384 |
|
| 6385 |
<DD> This feature controls the order that newsgroups will be presented. If |
| 6386 |
set, they will be presented in the same order as they occur in |
| 6387 |
your <EM>newsrc</EM> file. |
| 6388 |
If not set, the newsgroups |
| 6389 |
will be presented in alphabetical order. |
| 6390 |
<P> |
| 6391 |
|
| 6392 |
<DT> <A NAME="next-thread-without-confirm"><EM>next-thread-without-confirm</EM></A> |
| 6393 |
|
| 6394 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s Next and Prev commands in |
| 6395 |
the case where you are using one of the |
| 6396 |
"separate-index-screen" styles for the configuration option |
| 6397 |
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A> |
| 6398 |
and currently have the folder sorted by a Threaded or OrderedSubject sort. |
| 6399 |
When you are Viewing a particular thread you have a |
| 6400 |
MESSAGE INDEX of only the messages in that thread. |
| 6401 |
If you press the Next command with the last message in the thread highlighted |
| 6402 |
you will normally be asked if you want to "View next thread?", |
| 6403 |
assuming there is a next thread to view. |
| 6404 |
If this feature is set it will be assumed that you always want to view the |
| 6405 |
next thread and you won't be asked to confirm that. |
| 6406 |
Similarly, if the first message of the thread is highlighted and you |
| 6407 |
press the Prev command, this feature will prevent the question |
| 6408 |
"View previous thread". |
| 6409 |
<P> |
| 6410 |
This feature only has an effect in the MESSAGE INDEX screen. |
| 6411 |
If you then view a particular message from that screen and press the |
| 6412 |
Next command, you will be sent to the next thread without being asked, |
| 6413 |
independent of the setting of this feature. |
| 6414 |
<P> |
| 6415 |
The feature |
| 6416 |
<A HREF="#auto-open-next-unread">auto-open-next-unread</A>, |
| 6417 |
also has some similar effects. |
| 6418 |
<P> |
| 6419 |
This feature is displayed as "Read Next Thread Without Confirming". |
| 6420 |
<P> |
| 6421 |
|
| 6422 |
<DT> <A NAME="offer-expunge-of-inbox"><EM>offer-expunge-of-inbox</EM></A> |
| 6423 |
|
| 6424 |
<DD> The INBOX is normally treated differently from regular folders in several |
| 6425 |
ways. |
| 6426 |
One of the differences is that the normal "close" sequence of |
| 6427 |
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you |
| 6428 |
leave the INBOX to view another folder. |
| 6429 |
The "close" sequence normally includes the Expunging |
| 6430 |
of deleted messages |
| 6431 |
(either automatically or after a prompt, controlled by the features |
| 6432 |
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>, |
| 6433 |
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and |
| 6434 |
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the |
| 6435 |
handling of the |
| 6436 |
<A HREF="#read-msg-fold">Read-Message-Folder</A>. |
| 6437 |
|
| 6438 |
<P> |
| 6439 |
If this feature is set the "close" sequence handling will take |
| 6440 |
place every time you leave the INBOX. |
| 6441 |
The INBOX will still be kept open, but the offer to Expunge and the archiving |
| 6442 |
to the Read-Message-Folder |
| 6443 |
will take place each time you leave the INBOX instead of only once at the |
| 6444 |
end of the session. |
| 6445 |
<P> |
| 6446 |
|
| 6447 |
<DT> <A NAME="offer-expunge-of-stayopen-folders"><EM>offer-expunge-of-stayopen-folders</EM></A> |
| 6448 |
|
| 6449 |
<DD> This feature is related to the option |
| 6450 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A>. |
| 6451 |
Stay Open folders are treated differently from regular folders in several |
| 6452 |
ways. |
| 6453 |
One of the differences is that the normal "close" sequence of |
| 6454 |
events is deferred until <EM>Alpine</EM> is exited, instead of happening when you |
| 6455 |
leave the folder to view another folder. |
| 6456 |
The "close" sequence normally includes the Expunging |
| 6457 |
of deleted messages |
| 6458 |
(either automatically or after a prompt, controlled by the features |
| 6459 |
<A HREF="#expunge-wo-confirm">Expunge-Without-Confirm</A>, |
| 6460 |
<A HREF="#expunge-without-confirm-everywhere">Expunge-Without-Confirm-Everywhere</A>, and |
| 6461 |
<A HREF="#expunge-only-manually">Expunge-Only-Manually</A>), and the |
| 6462 |
handling of |
| 6463 |
<A HREF="#incoming-archive-folders">Incoming-Archive-Folders</A>. |
| 6464 |
|
| 6465 |
<P> |
| 6466 |
If this feature is set the "close" sequence handling will take |
| 6467 |
place when you leave the Stay Open folder. |
| 6468 |
The folder will still be kept open, but the offer to Expunge and the archiving |
| 6469 |
will take place each time you leave the folder instead of only once at the |
| 6470 |
end of the session. |
| 6471 |
This feature does not affect the INBOX, which will still only be processed |
| 6472 |
when you exit <EM>Alpine</EM>. |
| 6473 |
<P> |
| 6474 |
|
| 6475 |
<DT> <A NAME="pass-c1-control-characters-as-is"><EM>pass-c1-control-characters-as-is</EM></A> |
| 6476 |
|
| 6477 |
<DD> It is probably not useful to set this option. |
| 6478 |
This is a legacy option left behind "just in case". |
| 6479 |
Multi-byte characters which have an octet which has the same |
| 6480 |
value as a control character are permitted through whether or not |
| 6481 |
this option is turned on. |
| 6482 |
<P> |
| 6483 |
If the feature <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A> |
| 6484 |
is set, then this feature has no effect. |
| 6485 |
However, if you wish to filter out regular control characters but pass the |
| 6486 |
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then |
| 6487 |
you may leave <A HREF="#pass-control-characters-as-is">pass-control-characters-as-is</A> |
| 6488 |
unset and set this feature. |
| 6489 |
<P> |
| 6490 |
|
| 6491 |
<DT> <A NAME="pass-control-characters-as-is"><EM>pass-control-characters-as-is</EM></A> |
| 6492 |
|
| 6493 |
<DD> It is probably not useful to set this option. |
| 6494 |
This is a legacy option left behind "just in case". |
| 6495 |
Multi-byte characters which have an octet which has the same |
| 6496 |
value as a control character are permitted through whether or not |
| 6497 |
this option is turned on. |
| 6498 |
<P> |
| 6499 |
If set, all characters in a message will be sent to the |
| 6500 |
screen. Normally, control characters are automatically suppressed in |
| 6501 |
order to avoid inadvertently changing terminal setup parameters. |
| 6502 |
Control characters are usually displayed as two character sequences like |
| 6503 |
<P><CENTER><SAMP> ^C </SAMP></CENTER><P> |
| 6504 |
for Control-C, |
| 6505 |
<P><CENTER><SAMP> ^[ </SAMP></CENTER><P> |
| 6506 |
for ESCAPE, |
| 6507 |
<P><CENTER><SAMP> ^? </SAMP></CENTER><P> |
| 6508 |
for DELETE, and |
| 6509 |
<P><CENTER><SAMP> ~E </SAMP></CENTER><P> |
| 6510 |
for the character with value 133 (0x85). |
| 6511 |
(The DEL character is displayed as ^?, regular control characters are displayed |
| 6512 |
as the character ^ followed by the character obtained by adding the |
| 6513 |
five low-order bits of the character to 0x40, and the C1 |
| 6514 |
control characters 0x80 - 0x9F are displayed as the character ~ followed by the |
| 6515 |
character obtained by adding the |
| 6516 |
five low-order bits of the character to 0x40.) |
| 6517 |
Sometimes, in cases where changing a single control character into a |
| 6518 |
two-character sequence would confuse <EM>Alpine</EM>'s display routines, |
| 6519 |
a question mark is substituted for the control character. |
| 6520 |
<P> |
| 6521 |
If you wish to filter out regular control characters but pass the |
| 6522 |
so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then |
| 6523 |
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. |
| 6524 |
<P> |
| 6525 |
|
| 6526 |
<DT> <A NAME="predict-nntp-server"><EM>predict-nntp-server</EM></A> |
| 6527 |
|
| 6528 |
<DD> This feature allows <EM>Alpine</EM> to assume that the open NNTP server at the |
| 6529 |
time of composition is the NNTP server to which the message should be |
| 6530 |
posted. This is especially recommended when there are multiple News |
| 6531 |
collections. If this feature is not set, <EM>Alpine</EM> will try to post to the first server in |
| 6532 |
the <a href="#nntp-server">nntp-server</a> variable. Setting |
| 6533 |
this feature also negates the need to add News collection servers to |
| 6534 |
the nntp-server variable. |
| 6535 |
<P> |
| 6536 |
This feature can be especially handy when used in conjunction with |
| 6537 |
<a href="#enable-multiple-newsrcs">enable-multiple-newsrcs</a>. |
| 6538 |
<P> |
| 6539 |
This option is displayed as "NNTP Server (for news)". |
| 6540 |
<P> |
| 6541 |
|
| 6542 |
<DT> <A NAME="prefer-plain-text"><EM>prefer-plain-text</EM></A> |
| 6543 |
|
| 6544 |
<DD> A message being viewed may contain alternate versions of the same content. |
| 6545 |
Those alternate versions are ordered by the sending software such that the |
| 6546 |
first alternative is the least preferred and the last alternative is the |
| 6547 |
most preferred. <EM>Alpine</EM> will normally display the most-preferred version that |
| 6548 |
it knows how to display. This is most often encountered where the two |
| 6549 |
alternate versions are a plain text version and an HTML version, with the |
| 6550 |
HTML version listed last as the most preferred. |
| 6551 |
<P> |
| 6552 |
|
| 6553 |
If this option is set, then any plain text version will be preferred to |
| 6554 |
all other versions. |
| 6555 |
<P> |
| 6556 |
|
| 6557 |
<DT> <A NAME="preopen-stayopen-folders"><EM>preopen-stayopen-folders</EM></A> |
| 6558 |
|
| 6559 |
<DD> This feature is related to the option |
| 6560 |
<A HREF="#stay-open-folders">Stay-Open-Folders</A>. |
| 6561 |
Normally, Stay Open folders are only opened on demand, when the user |
| 6562 |
asks to open them. |
| 6563 |
From then on they are kept open for the duration of the session. |
| 6564 |
However, if this feature is set, then the Stay Open folders will all be |
| 6565 |
opened at startup, at the same time that the INBOX is opened. |
| 6566 |
<P> |
| 6567 |
|
| 6568 |
<DT> <A NAME="preserve-start-stop-characters"><EM>preserve-start-stop-characters</EM></A> |
| 6569 |
|
| 6570 |
<DD> This feature controls how special control key characters, typically |
| 6571 |
<EM>^S</EM> and <EM>^Q</EM>, are interpreted when input to <EM>Alpine</EM>. |
| 6572 |
These characters |
| 6573 |
are known as the "start" and "stop" characters and are sometimes used in |
| 6574 |
communications paths to control data flow between devices that operate at |
| 6575 |
different speeds. |
| 6576 |
<P> |
| 6577 |
|
| 6578 |
By default, <EM>Alpine</EM> turns the system's handling of these special characters |
| 6579 |
off except during printing. However, if you see <EM>Alpine</EM> reporting input errors |
| 6580 |
such as: |
| 6581 |
|
| 6582 |
<BLOCKQUOTE> |
| 6583 |
[ Command "^Q" not defined for this screen. ] <BR> |
| 6584 |
</BLOCKQUOTE> |
| 6585 |
|
| 6586 |
and, at the same time, see your display become garbled, then it is likely |
| 6587 |
that setting this option will solve the problem. Be aware, though, that |
| 6588 |
enabling this feature will also cause <EM>Alpine</EM> to ostensibly "hang" |
| 6589 |
whenever the <EM>Ctrl-S</EM> key combination is entered as the system is now |
| 6590 |
interpreting such input as a "stop output" command. To "start |
| 6591 |
output" again, simply type <EM>Ctrl-Q</EM>. |
| 6592 |
<P> |
| 6593 |
This feature is displayed as "Preserve Start/Stop Characters". |
| 6594 |
<P> |
| 6595 |
|
| 6596 |
<DT> <A NAME="print-formfeed-between-messages"><EM>print-formfeed-between-messages</EM></A> |
| 6597 |
|
| 6598 |
<DD> Setting this feature causes a formfeed to be printed between messages when |
| 6599 |
printing multiple messages with the <EM>Apply Print</EM> command. |
| 6600 |
<P> |
| 6601 |
|
| 6602 |
<DT> <A NAME="print-includes-from-line"><EM>print-includes-from-line</EM></A> |
| 6603 |
|
| 6604 |
<DD> If this feature is set, then the Unix mail style From line is included |
| 6605 |
at the start of each message that is printed. This line looks something |
| 6606 |
like the following, with the address replaced by the address from the |
| 6607 |
From line of the message being printed: |
| 6608 |
|
| 6609 |
<BLOCKQUOTE> |
| 6610 |
From [email protected] Mon May 13 14:11:06 1996 <BR> |
| 6611 |
</BLOCKQUOTE> |
| 6612 |
<P> |
| 6613 |
|
| 6614 |
<DT> <A NAME="print-index-enabled"><EM>print-index-enabled</EM></A> |
| 6615 |
|
| 6616 |
<DD> This feature controls the behavior of the <EM>Print</EM> command |
| 6617 |
when in the |
| 6618 |
"Folder Index" screen. |
| 6619 |
If set, the <EM>Print</EM> command will give you a prompt |
| 6620 |
asking if you wish to print the message index, or the currently highlighted |
| 6621 |
message. If not set, the message will be printed. |
| 6622 |
<P> |
| 6623 |
|
| 6624 |
<DT> <A NAME="print-offers-custom-cmd-prompt"><EM>print-offers-custom-cmd-prompt</EM></A> |
| 6625 |
|
| 6626 |
<DD> When this feature is set, the <EM>Print</EM> command |
| 6627 |
will have an additional |
| 6628 |
subcommand called <EM>C CustomPrint</EM>. |
| 6629 |
If selected, you will have |
| 6630 |
the opportunity to enter any system print command, instead of being |
| 6631 |
restricted to using those that have been previously configured in the |
| 6632 |
<EM>Setup/Printer</EM> screen. |
| 6633 |
<P> |
| 6634 |
This feature is displayed as "Print Offers Custom Command Prompt". |
| 6635 |
<P> |
| 6636 |
|
| 6637 |
<DT> <A NAME="prune-uses-yyyy-mm"><EM>prune-uses-yyyy-mm</EM></A> |
| 6638 |
|
| 6639 |
<DD> By default, <EM>Alpine</EM> asks monthly whether or not you would like to rename |
| 6640 |
some folders to a new name containing the date. |
| 6641 |
It also asks whether or not you would like to delete some old folders. |
| 6642 |
See the <A HREF="#pruning-rule">pruning-rule</A> option for an |
| 6643 |
explanation. |
| 6644 |
|
| 6645 |
<P> |
| 6646 |
By default, the name used when renaming a folder looks like |
| 6647 |
<P> |
| 6648 |
<CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER> |
| 6649 |
<P> |
| 6650 |
For example, the first time you run <EM>Alpine</EM> in May of 2004, |
| 6651 |
the folder "sent-mail" might be renamed to |
| 6652 |
<P> |
| 6653 |
<CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER> |
| 6654 |
<P> |
| 6655 |
If this feature is set, the name used will be of the form |
| 6656 |
<P> |
| 6657 |
<CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER> |
| 6658 |
<P> |
| 6659 |
where "yyyy" is the year and "mm" is the two-digit |
| 6660 |
month (01, 02, ..., 12). |
| 6661 |
For the April, 2004 example above, it would instead be |
| 6662 |
<P> |
| 6663 |
<CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER> |
| 6664 |
<P> |
| 6665 |
because April is the 4th month of the year. |
| 6666 |
A reason you might want to set this feature is so that the folders |
| 6667 |
will sort in chronological order. |
| 6668 |
<P> |
| 6669 |
|
| 6670 |
<DT> <A NAME="publiccerts-in-keychain"><EM>publiccerts-in-keychain</EM></A> |
| 6671 |
|
| 6672 |
<DD> Mac OS X <EM>Alpine</EM> only. |
| 6673 |
<P> |
| 6674 |
If this feature is set the Mac OS X default keychain will be used as the place |
| 6675 |
to store public certificates instead of a |
| 6676 |
<A HREF="#smime-public-cert-directory"><EM>smime-public-cert-directory</EM></A> |
| 6677 |
or a |
| 6678 |
<A HREF="#smime-public-cert-container"><EM>smime-public-cert-container</EM></A>. |
| 6679 |
<P> |
| 6680 |
This feature is displayed as "S/MIME -- Public Certs in MacOS Keychain". |
| 6681 |
<P> |
| 6682 |
|
| 6683 |
<DT> <A NAME="quell-attachment-extension-warn"><EM>quell-attachment-extension-warn</EM></A> |
| 6684 |
<DD> This feature suppresses the extra warning you can get when trying |
| 6685 |
to view an attachment for which there is no mime-type match. Turning |
| 6686 |
on this feature will just run the program according to extension |
| 6687 |
instead of first warning the user that it will run according to the |
| 6688 |
file's extension. |
| 6689 |
<P> |
| 6690 |
This feature can be used along side |
| 6691 |
<A HREF="#quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A> |
| 6692 |
to preserve the behavior exhibited in <EM>Pine</EM> versions prior to <EM>Pine</EM> 4.50. |
| 6693 |
<P> |
| 6694 |
This feature is displayed as "Suppress Attachment Extension Warning". |
| 6695 |
<P> |
| 6696 |
|
| 6697 |
<DT> <A NAME="quell-attachment-extra-prompt"><EM>quell-attachment-extra-prompt</EM></A> |
| 6698 |
<DD> By default, when you attempt to view an attachment externally |
| 6699 |
from the "Attachment View" screen, you are asked if you |
| 6700 |
really want to view the selected attachment. |
| 6701 |
<P> |
| 6702 |
If this feature is set, you will <B>not</B> be prompted to confirm |
| 6703 |
your selection. Prior to <EM>Pine</EM> 4.50, the default behavior was to not |
| 6704 |
prompt. This feature was added for those wanting to preserve that |
| 6705 |
behavior. |
| 6706 |
<P> |
| 6707 |
This feature is displayed as "Suppress Attachment Extra Prompt". |
| 6708 |
<P> |
| 6709 |
|
| 6710 |
<DT> <A NAME="quell-berkeley-format-timezone"><EM>quell-berkeley-format-timezone</EM></A> |
| 6711 |
|
| 6712 |
<DD> POSIX mandates a timezone in UNIX mailbox format folder delimiters |
| 6713 |
(the line which begins with From <SPACE>). |
| 6714 |
Some versions of Berkeley mail have trouble with this, and don't recognize |
| 6715 |
the line as a message delimiter. |
| 6716 |
If this feature is set, the timezone will be left off the delimiter line. |
| 6717 |
<P> |
| 6718 |
This feature is displayed as "Suppress Berkeley Format Timezone". |
| 6719 |
<P> |
| 6720 |
|
| 6721 |
<DT> <A NAME="quell-charset-warning"><EM>quell-charset-warning</EM></A> |
| 6722 |
|
| 6723 |
<DD> By default, if the message you are viewing contains characters that are |
| 6724 |
not representable in your |
| 6725 |
<A HREF="#disp-char-set"><EM>display-character-set</EM></A> |
| 6726 |
then <EM>Alpine</EM> will |
| 6727 |
add a warning to the start of the displayed text. |
| 6728 |
If this option is set, then that editorial message will be suppressed. |
| 6729 |
<P> |
| 6730 |
Setting this feature also suppresses the comment about the character set |
| 6731 |
in header lines. |
| 6732 |
For example, when viewing a message you might see |
| 6733 |
<P> |
| 6734 |
<CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER> |
| 6735 |
<P> |
| 6736 |
in the From header if your Character-Set is something other than ISO-8859-2. |
| 6737 |
If you set this feature, the comment about the character set will |
| 6738 |
no longer be there. |
| 6739 |
<P> |
| 6740 |
This feature is displayed as "Suppress Character Set Warning". |
| 6741 |
<P> |
| 6742 |
|
| 6743 |
<DT> <A NAME="quell-content-id"><EM>quell-content-id</EM></A> |
| 6744 |
|
| 6745 |
<DD> This feature changes the behavior of <EM>Alpine</EM> when sending messages. |
| 6746 |
It is intended to work around a bug in Microsoft's Outlook XP mail user |
| 6747 |
agent. |
| 6748 |
As of this writing, Microsoft has acknowledged the bug but |
| 6749 |
has not added it to the Knowledge Base. |
| 6750 |
We have been told that there will be a post-SP1 hotfix for Outlook XP. |
| 6751 |
This particular bug has bug fix number OfficeQFE:4781. |
| 6752 |
The nature of the bug is that messages with attachments which |
| 6753 |
contain a Content-ID header (which standard <EM>Alpine</EM> attachments do) |
| 6754 |
do not show the attachment indicator (a paperclip) when viewed with |
| 6755 |
Outlook XP. |
| 6756 |
So the user has no indication that the message contains an attachment. |
| 6757 |
|
| 6758 |
<P> |
| 6759 |
If this feature is set then <EM>Alpine</EM> will remove most Content-ID headers |
| 6760 |
before sending a message. |
| 6761 |
If an attachment is of type MESSAGE, then the existing Content-ID headers |
| 6762 |
inside the message will be left intact. |
| 6763 |
This would only happen with <EM>Alpine</EM> if a message was forwarded as an attachment |
| 6764 |
or if a message with a message attached was forwarded. |
| 6765 |
Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded, |
| 6766 |
the Content-ID headers of the alternative parts will not be removed. |
| 6767 |
|
| 6768 |
<P> |
| 6769 |
Because the Content-ID header is a standard part of MIME it is possible |
| 6770 |
that setting this feature will break something. |
| 6771 |
For example, if an attachment has a Content-ID header which is necessary |
| 6772 |
for the correct functioning of that attachment, it is possible that <EM>Alpine</EM> |
| 6773 |
may remove that header when the attachment is forwarded. |
| 6774 |
However, it seems fairly safe at this time. |
| 6775 |
<P> |
| 6776 |
This feature is displayed as "Suppress Content-ID". |
| 6777 |
<P> |
| 6778 |
|
| 6779 |
<DT> <A NAME="quell-dead-letter-on-cancel"><EM>quell-dead-letter-on-cancel</EM></A> |
| 6780 |
|
| 6781 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when you cancel a message being |
| 6782 |
composed. <EM>Alpine</EM>'s usual behavior is to write the canceled message to |
| 6783 |
a file named <CODE>dead.letter</CODE> in your home directory (under UNIX; |
| 6784 |
<CODE>DEADLETR</CODE> under WINDOWS/DOS) overwriting any previous message. |
| 6785 |
Under some conditions (some routine), this can introduce a noticeable delay. |
| 6786 |
<P> |
| 6787 |
|
| 6788 |
Setting this feature will cause <EM>Alpine</EM> NOT to write canceled compositions |
| 6789 |
into the file called <CODE>dead.letter</CODE>. |
| 6790 |
<P> |
| 6791 |
This feature affects the newer option |
| 6792 |
<A HREF="#dead-letter-files"><EM>Dead-Letter-Files</EM></A>, which specifies the |
| 6793 |
number of dead letter files to keep around. |
| 6794 |
If this feature is set, then the Dead-Letter-Files option has no effect. |
| 6795 |
<P> |
| 6796 |
This feature is displayed as "Do Not Save to Deadletter on Cancel". |
| 6797 |
<P> |
| 6798 |
|
| 6799 |
<DT> <A NAME="quell-empty-directories"><EM>quell-empty-directories</EM></A> |
| 6800 |
|
| 6801 |
<DD> This feature causes <EM>Alpine</EM> to remove from the display any directories |
| 6802 |
that do not contain at least one file or directory. This can be useful |
| 6803 |
to prevent overly cluttered folder lists when a collection is stored on |
| 6804 |
a server that treats all names as both a folder and a directory. |
| 6805 |
|
| 6806 |
<P> |
| 6807 |
Note, enabling this feature can cause surprising behavior! For example, |
| 6808 |
you can still use Add to create a directory, but unless you immediately |
| 6809 |
enter that directory and create a folder, that newly created directory |
| 6810 |
may not be displayed next time you enter the folder list. |
| 6811 |
|
| 6812 |
<P> |
| 6813 |
This feature is displayed as "Hide Empty Directories". |
| 6814 |
<P> |
| 6815 |
|
| 6816 |
<DT> <A NAME="quell-extra-post-prompt"><EM>quell-extra-post-prompt</EM></A> |
| 6817 |
|
| 6818 |
<DD> This feature causes <EM>Alpine</EM> to skip the extra question about |
| 6819 |
posting a message which may go to thousands of readers when you |
| 6820 |
are about to post to a newsgroup. |
| 6821 |
|
| 6822 |
<P> |
| 6823 |
This feature is displayed as "Suppress Extra Posting Prompt". |
| 6824 |
<P> |
| 6825 |
|
| 6826 |
<DT> <A NAME="quell-filtering-done-message"><EM>quell-filtering-done-message</EM></A> |
| 6827 |
|
| 6828 |
<DD> This feature causes <EM>Alpine</EM> to suppress the "filtering done" message. |
| 6829 |
|
| 6830 |
<P> |
| 6831 |
This feature is displayed as "Suppress Filtering Done Message". |
| 6832 |
<P> |
| 6833 |
|
| 6834 |
<DT> <A NAME="quell-filtering-messages"><EM>quell-filtering-messages</EM></A> |
| 6835 |
|
| 6836 |
<DD> This feature causes <EM>Alpine</EM> to suppress the messages about |
| 6837 |
moving filtered messages and setting flags in messages, due to Filter Rules. |
| 6838 |
|
| 6839 |
<P> |
| 6840 |
This feature is displayed as "Suppress Filtering Messages". |
| 6841 |
<P> |
| 6842 |
|
| 6843 |
<DT> <A NAME="quell-flowed-text"><EM>quell-flowed-text</EM></A> |
| 6844 |
|
| 6845 |
<DD> <EM>Alpine</EM> generates flowed text where possible. |
| 6846 |
The method for generating flowed text is defined by |
| 6847 |
<A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>, |
| 6848 |
the benefit of doing so is |
| 6849 |
to send message text that can properly be viewed both on normal width displays |
| 6850 |
and on displays with smaller or larger than normal screen widths. |
| 6851 |
With flowed text, a space at the end of a line tells the receiving mail |
| 6852 |
client that the following line belongs to the same paragraph. |
| 6853 |
Quoted text will also be affected, with only the innermost |
| 6854 |
level of ">" quoting being followed by a space. |
| 6855 |
However, if you have changed the |
| 6856 |
<A HREF="#reply-ind-str">"Reply-Indent-String"</A> |
| 6857 |
so that it is not equal to the default value of "> ", then |
| 6858 |
quoted text will not be flowed. |
| 6859 |
For this reason, we recommend that you leave your |
| 6860 |
"Reply-Indent-String" set to the default. |
| 6861 |
<P> |
| 6862 |
This feature turns off the generation of flowed text, as it might be |
| 6863 |
desired to more tightly control how a message is displayed on the receiving end. |
| 6864 |
<P> |
| 6865 |
If this feature is <EM>not</EM> set, you can control on a message by message |
| 6866 |
basis whether or not flowed text is generated. |
| 6867 |
You do this by typing ^V at the Send confirmation prompt that you get |
| 6868 |
after typing ^X to send a message. |
| 6869 |
^V is a toggle which turns flowing off and back on if typed again. |
| 6870 |
If for some reason flowing cannot be done on a particular message, then the |
| 6871 |
^V command will not be available. |
| 6872 |
This would be the case, for example, if this feature was set, or if your |
| 6873 |
"Reply-Indent-String" was set to a non-default value. |
| 6874 |
If the feature |
| 6875 |
<A HREF="#send-without-confirm">Send-Without-Confirm</A> is set, |
| 6876 |
then the opportunity to control on a message by message basis |
| 6877 |
whether or not flowed text is generated is lost. |
| 6878 |
<P> |
| 6879 |
When this feature is not set and you have typed ^V to turn off flowing, |
| 6880 |
the Send confirmation prompt will change to look like |
| 6881 |
<P> |
| 6882 |
<CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER> |
| 6883 |
<P> |
| 6884 |
<A HREF="#strip-whitespace-before-send">Strip-Whitespace-Before-Send</A> will |
| 6885 |
also turn off the sending of flowed text messages, but it differs in that |
| 6886 |
it also trims all trailing white space from a message before sending it. |
| 6887 |
<P> |
| 6888 |
If alternate editors are used extensively, be aware that a message will still |
| 6889 |
be sent flowed if this feature is unset. In most cases this will be fine, |
| 6890 |
but if the editor has a "flowed text" mode, it would be best to |
| 6891 |
use that. |
| 6892 |
<P> |
| 6893 |
This feature is displayed as "Do Not Send Flowed Text". |
| 6894 |
<P> |
| 6895 |
|
| 6896 |
<DT> <A NAME="quell-folder-internal-msg"><EM>quell-folder-internal-msg</EM></A> |
| 6897 |
|
| 6898 |
<DD> This feature determines whether or not <EM>Alpine</EM> will create |
| 6899 |
"pseudo messages" in folders that are in standard Unix or |
| 6900 |
MMDF format. |
| 6901 |
<P> |
| 6902 |
|
| 6903 |
<EM>Alpine</EM> will normally create these |
| 6904 |
pseudo messages when they are not already |
| 6905 |
present in a standard Unix or MMDF folder. |
| 6906 |
Their purpose is to record |
| 6907 |
certain mailbox state data needed for correct IMAP and POP server operation, |
| 6908 |
and also for <EM>Alpine</EM> to be able to mark messages as Answered when |
| 6909 |
the Reply has been postponed. |
| 6910 |
<P> |
| 6911 |
|
| 6912 |
Sites which do not use IMAP/POP for remote mail access, and which need to |
| 6913 |
support mail tools that are adversely affected by the presence of the |
| 6914 |
pseudo-messages (e.g. some mail notification tools) may enable this |
| 6915 |
feature to tell <EM>Alpine</EM> not to create them. |
| 6916 |
Note that <EM>Alpine</EM>'s "Answered" flag |
| 6917 |
capability will be adversely affected if this is done. |
| 6918 |
<P> |
| 6919 |
|
| 6920 |
Note too that, even if this feature is enabled, <EM>Alpine</EM> will not remove |
| 6921 |
pseudo-messages when it encounters them (e.g. those created by UW's imapd |
| 6922 |
or ipopd servers.) |
| 6923 |
This feature has no effect on folders that are not in |
| 6924 |
standard Unix or MMDF format, as pseudo-messages are not needed in the |
| 6925 |
other formats to record mailbox state information. |
| 6926 |
<P> |
| 6927 |
This feature is displayed as "Prevent Folder Internal Message". |
| 6928 |
<P> |
| 6929 |
|
| 6930 |
<DT> <A NAME="quell-full-header-auto-reset"><EM>quell-full-header-auto-reset</EM></A> |
| 6931 |
|
| 6932 |
<DD> The HdrMode Command |
| 6933 |
normally resets to the default state when switching to a new message. |
| 6934 |
For example, if you've used the "H" command to turn on Full |
| 6935 |
Headers for a message you are viewing, and then you type the Next command |
| 6936 |
to look at the next message, the full headers will no longer be shown. |
| 6937 |
Setting this feature disables that reset. |
| 6938 |
Instead, the Header Mode remains the same from message to message. |
| 6939 |
|
| 6940 |
<P> |
| 6941 |
The presence or absence of the HdrMode command is determined by the |
| 6942 |
<A HREF="#enable-full-header-cmd">"Enable-Full-Header-Cmd"</A> |
| 6943 |
Feature-List option. |
| 6944 |
<P> |
| 6945 |
This feature is displayed as "Suppress Full Header Auto Reset". |
| 6946 |
<P> |
| 6947 |
|
| 6948 |
<DT> <A NAME="quell-imap-envelope-update"><EM>quell-imap-envelope-update</EM></A> |
| 6949 |
|
| 6950 |
<DD> In the MESSAGE INDEX screen, if the open folder is being accessed |
| 6951 |
using IMAP, <EM>Alpine</EM> normally tries to paint the index lines on the screen |
| 6952 |
as soon as the information arrives from the IMAP server. |
| 6953 |
This means that the index information makes it onto the screen more quickly |
| 6954 |
than it otherwise would. |
| 6955 |
This sometimes results in behavior that bothers some users. |
| 6956 |
For example, when paging to a new page of the index, it may be possible for |
| 6957 |
the lines to be painted on the screen in a random order, rather than from |
| 6958 |
top to bottom. |
| 6959 |
<P> |
| 6960 |
|
| 6961 |
Setting this feature causes <EM>Alpine</EM> to wait for all of the information |
| 6962 |
to be gathered before it paints the index screen. |
| 6963 |
Once it collects all of the information, the screen will be painted quickly |
| 6964 |
from top to bottom. |
| 6965 |
<P> |
| 6966 |
This feature is displayed as "Suppress IMAP Envelope Update". |
| 6967 |
<P> |
| 6968 |
|
| 6969 |
<DT> <A NAME="quell-lock-failure-warnings"><EM>quell-lock-failure-warnings</EM></A> |
| 6970 |
|
| 6971 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when it encounters a problem |
| 6972 |
acquiring a mail folder lock. Typically, a secondary file associated |
| 6973 |
with the mail folder being opened is created as part of the locking |
| 6974 |
process. On some systems, such file creation has been administratively |
| 6975 |
precluded by the system configuration. |
| 6976 |
<P> |
| 6977 |
|
| 6978 |
<EM>Alpine</EM> issues a warning when such failures occur, which can become bothersome |
| 6979 |
if the system is configured to disallow such actions. Setting this |
| 6980 |
feature causes <EM>Alpine</EM> to remain silent when this part of lock creation fails. |
| 6981 |
<P> |
| 6982 |
|
| 6983 |
WARNING: systems that have been configured in a way that precludes locking |
| 6984 |
introduce some risk of mail folder corruption when more than one program |
| 6985 |
attempts to modify the mail folder. This is most likely to occur to one's |
| 6986 |
<EM>INBOX</EM> or other "Incoming Message Folder". |
| 6987 |
<P> |
| 6988 |
This feature is displayed as "Suppress Lock Failure Warnings". |
| 6989 |
<P> |
| 6990 |
|
| 6991 |
<DT> <A NAME="quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A> |
| 6992 |
|
| 6993 |
<DD> This option is closely related to the |
| 6994 |
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> |
| 6995 |
option, the |
| 6996 |
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and |
| 6997 |
<A HREF="#quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A>. |
| 6998 |
<P> |
| 6999 |
If this option is set, then the normal new-mail checking which happens |
| 7000 |
while you are composing will not happen for folders other than your |
| 7001 |
INBOX (which depends on the setting |
| 7002 |
of "Quell-Mailchecks-Composing-Inbox"). |
| 7003 |
<P> |
| 7004 |
You might want to set this option if you are experiencing delays while |
| 7005 |
composing which you think might be related to the speed of the new-mail |
| 7006 |
checks. |
| 7007 |
<P> |
| 7008 |
Even with this option turned on, an occasional new-mail check may be done |
| 7009 |
in order to keep the server from killing the connection to the folder. |
| 7010 |
For example, IMAP servers may remove a connection to a folder if there |
| 7011 |
has been no activity on the connection for 30 minutes or more. |
| 7012 |
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the |
| 7013 |
30 minutes is up even though you have turned on this feature to quell |
| 7014 |
those checks. |
| 7015 |
<P> |
| 7016 |
Besides new-mail checks, checkpoint operations on the folders |
| 7017 |
will also be quelled when you set this option. |
| 7018 |
The purpose of checkpointing is to write the changes to a folder out to |
| 7019 |
disk periodically in order to avoid losing those changes when system or |
| 7020 |
software problems occur. |
| 7021 |
New-mail checking and checkpointing while you are not composing are not |
| 7022 |
affected by this option. |
| 7023 |
<P> |
| 7024 |
This feature is displayed as "Prevent Mailchecks While Composing Except for INBOX". |
| 7025 |
<P> |
| 7026 |
|
| 7027 |
<DT> <A NAME="quell-mailchecks-composing-inbox"><EM>Quell-Mailchecks-Composing-Inbox</EM></A> |
| 7028 |
|
| 7029 |
<DD> This option is closely related to the |
| 7030 |
<A HREF="#mail-check"><EM>Mail-Check-Interval</EM></A> |
| 7031 |
option, the |
| 7032 |
<A HREF="#mail-check-noncurr"><EM>Mail-Check-Interval-Noncurrent</EM></A> option, and |
| 7033 |
<A HREF="#quell-mailchecks-composing-except"><EM>Quell-Mailchecks-Composing-Except-Inbox</EM></A>. |
| 7034 |
<P> |
| 7035 |
If this option is set, then the normal new-mail checking which happens |
| 7036 |
while you are composing will not happen for your INBOX. |
| 7037 |
Checking of other folders is controlled in a similar way with the |
| 7038 |
"Quell-Mailchecks-Composing-Except-Inbox" option. |
| 7039 |
<P> |
| 7040 |
You might want to set this option if you are experiencing delays while |
| 7041 |
composing which you think might be related to the speed of the new-mail |
| 7042 |
checks. |
| 7043 |
<P> |
| 7044 |
Even with this option turned on, an occasional new-mail check may be done |
| 7045 |
in order to keep the server from killing the connection to the folder. |
| 7046 |
For example, IMAP servers may remove a connection to a folder if there |
| 7047 |
has been no activity on the connection for 30 minutes or more. |
| 7048 |
Instead of letting that happen, <EM>Alpine</EM> will check for new mail before the |
| 7049 |
30 minutes is up even though you have turned on this feature to quell |
| 7050 |
those checks. |
| 7051 |
<P> |
| 7052 |
Besides new-mail checks, checkpoint operations on the INBOX |
| 7053 |
will also be quelled when you set this option. |
| 7054 |
The purpose of checkpointing is to write the changes to a folder out to |
| 7055 |
disk periodically in order to avoid losing those changes when system or |
| 7056 |
software problems occur. |
| 7057 |
New-mail checking and checkpointing while you are not composing are not |
| 7058 |
affected by this option. |
| 7059 |
<P> |
| 7060 |
This feature is displayed as "Prevent Mailchecks While Composing for INBOX". |
| 7061 |
<P> |
| 7062 |
|
| 7063 |
<DT> <A NAME="quell-maildomain-warning"><EM>quell-maildomain-warning</EM></A> |
| 7064 |
|
| 7065 |
<DD> When your configuration is set up so that your domain name contains no dots, |
| 7066 |
it is usually a configuration error. |
| 7067 |
By default, <EM>Alpine</EM> will warn you about this when you start it up. |
| 7068 |
You will see a warning message that looks like |
| 7069 |
<P> |
| 7070 |
<CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER> |
| 7071 |
|
| 7072 |
<P> |
| 7073 |
If this feature is set, the warning is turned off. |
| 7074 |
This feature is displayed as "Suppress Maildomain Warning". |
| 7075 |
<P> |
| 7076 |
|
| 7077 |
<DT> <A NAME="quell-news-envelope-update"><EM>quell-news-envelope-update</EM></A> |
| 7078 |
|
| 7079 |
<DD> In the MESSAGE INDEX screen, if the open folder is being accessed |
| 7080 |
using NNTP (News), <EM>Alpine</EM> normally tries to paint the index lines on the screen |
| 7081 |
as soon as the information arrives from the NNTP server. |
| 7082 |
This means that the index information makes it onto the screen more quickly |
| 7083 |
than it otherwise would. |
| 7084 |
This sometimes results in behavior that bothers some users. |
| 7085 |
For example, when paging to a new page of the index, it may be possible for |
| 7086 |
the lines to be painted on the screen in a random order, rather than from |
| 7087 |
top to bottom. |
| 7088 |
<P> |
| 7089 |
|
| 7090 |
Setting this feature causes <EM>Alpine</EM> to wait for all of the information |
| 7091 |
to be gathered before it paints the index screen. |
| 7092 |
Once it collects all of the information, the screen will be painted quickly |
| 7093 |
from top to bottom. |
| 7094 |
<P> |
| 7095 |
This feature is displayed as "Suppress News Envelope Update". |
| 7096 |
<P> |
| 7097 |
|
| 7098 |
<DT> <A NAME="quell-partial-fetching"><EM>quell-partial-fetching</EM></A> |
| 7099 |
|
| 7100 |
<DD> Partial fetching is a feature of the IMAP protocol. |
| 7101 |
By default, <EM>Alpine</EM> |
| 7102 |
will use partial fetching when copying the contents of a message or attachment |
| 7103 |
from the IMAP server to <EM>Alpine</EM>. |
| 7104 |
This means that the fetch will be done in many |
| 7105 |
small chunks instead of one big chunk. The main benefit of this approach is |
| 7106 |
that the fetch becomes interruptible. That is, the user can type <EM>^C</EM> |
| 7107 |
to stop the fetch early. In some cases partial fetching may cause a performance |
| 7108 |
problem so that the fetching of data takes significantly longer when partial |
| 7109 |
fetching is used. Turning on this feature will turn off partial fetching. |
| 7110 |
<P> |
| 7111 |
This feature is displayed as "Prevent Partial Fetching". |
| 7112 |
<P> |
| 7113 |
|
| 7114 |
<DT> <A NAME="quell-personal-name-prompt"><EM>quell-personal-name-prompt</EM></A> |
| 7115 |
|
| 7116 |
<DD> <EM>PC-Alpine</EM> only. This feature quells the prompting for a |
| 7117 |
<A HREF="#personal-name">personal-name</A>. This prompt normally happens |
| 7118 |
before composing a message, and only happens when there is no personal name |
| 7119 |
already set. |
| 7120 |
<P> |
| 7121 |
|
| 7122 |
<DT> <A NAME="quell-server-after-link-in-html"><EM>quell-server-after-link-in-html</EM></A> |
| 7123 |
|
| 7124 |
<DD> By default, links in HTML text are displayed with the host the link |
| 7125 |
references appended, within square brackets, to the link text. <EM>Alpine</EM> |
| 7126 |
does this to help indicate where a link will take you, particularly when |
| 7127 |
the link text might suggest a different destination. |
| 7128 |
|
| 7129 |
<P> |
| 7130 |
Setting this feature will prevent the server name from being appended |
| 7131 |
to the displayed text. |
| 7132 |
<P> |
| 7133 |
This feature is displayed as "Suppress Server After Link in HTML". |
| 7134 |
<P> |
| 7135 |
|
| 7136 |
<DT> <A NAME="quell-ssl-largeblocks"><EM>quell-ssl-largeblocks</EM></A> |
| 7137 |
|
| 7138 |
<DD> This feature (<EM>PC-Alpine</EM> only) changes the behavior of fetching messages |
| 7139 |
and attachments so that the message data is fetched in chunks no larger |
| 7140 |
than 12K bytes. |
| 7141 |
This works around a bug in Microsoft's SSL/TLS support. |
| 7142 |
Some versions of Microsoft SSL are not able to read full-sized (16K) |
| 7143 |
SSL/TLS packets. |
| 7144 |
Some servers will send such packets and this will |
| 7145 |
cause <EM>PC-Alpine</EM> to crash with the error |
| 7146 |
|
| 7147 |
<P> |
| 7148 |
<CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER> |
| 7149 |
|
| 7150 |
<P> |
| 7151 |
Microsoft is aware of the problem and has developed a hotfix for it, but as of |
| 7152 |
this writing the hotfix has not yet been added to the Knowledge Base. |
| 7153 |
<P> |
| 7154 |
This feature is displayed as "Prevent SSL Largeblocks". |
| 7155 |
<P> |
| 7156 |
|
| 7157 |
<DT> <A NAME="quell-status-message-beeping"><EM>quell-status-message-beeping</EM></A> |
| 7158 |
|
| 7159 |
<DD> If set status messages will never emit a beep. |
| 7160 |
<P> |
| 7161 |
This feature is displayed as "Suppress Status Message Beeping". |
| 7162 |
<P> |
| 7163 |
|
| 7164 |
<DT> <A NAME="quell-timezone-comment-when-sending"><EM>quell-timezone-comment-when-sending</EM></A> |
| 7165 |
|
| 7166 |
<DD> Normally, when <EM>Alpine</EM> generates a Date header for outgoing mail, |
| 7167 |
it will try to include the symbolic timezone at the end of the |
| 7168 |
header inside parentheses. |
| 7169 |
The symbolic timezone is often three characters long, but on |
| 7170 |
some operating systems, it may be longer. |
| 7171 |
Apparently there are some SMTP servers in the world which will reject an |
| 7172 |
incoming message if it has a Date header longer than about 80 characters. |
| 7173 |
If this feature is set, the symbolic timezone normally generated by |
| 7174 |
<EM>Alpine</EM> will not be included. |
| 7175 |
You probably don't need to worry about this feature unless you run into |
| 7176 |
the problem described above. |
| 7177 |
<P> |
| 7178 |
This feature is displayed as "Suppress Timezone Comment When Sending". |
| 7179 |
<P> |
| 7180 |
|
| 7181 |
<DT> <A NAME="quell-user-id-prompt"><EM>quell-user-id-prompt</EM></A> |
| 7182 |
|
| 7183 |
<DD> <EM>PC-Alpine</EM> only. This feature quells the prompting for a |
| 7184 |
<A HREF="#user-id">user-id</A> |
| 7185 |
if the information can be obtained from the login name used |
| 7186 |
to open the INBOX. Normally, this prompt happens before composing |
| 7187 |
a message, and only happens when there is no user-id already set |
| 7188 |
in the configuration. |
| 7189 |
<P> |
| 7190 |
With this feature set, composing a message is only possible after |
| 7191 |
establishing a connection to the INBOX. |
| 7192 |
<P> |
| 7193 |
|
| 7194 |
<DT> <A NAME="quell-user-lookup-in-passwd-file"><EM>quell-user-lookup-in-passwd-file</EM></A> |
| 7195 |
|
| 7196 |
<DD> This feature controls an aspect of |
| 7197 |
<EM>Alpine</EM>'s Composer, and if needed, will usually be set by the |
| 7198 |
system manager in <EM>Alpine</EM>'s system-wide configuration file. |
| 7199 |
Specifically, if this feature is set, <EM>Alpine</EM> will not attempt to look |
| 7200 |
in the system password file to find a Full Name for the entered address. |
| 7201 |
<P> |
| 7202 |
|
| 7203 |
Normally, names you enter into address fields (e.g. To: or Cc:) are |
| 7204 |
checked against your address book(s) to see if they match an address book |
| 7205 |
nickname. |
| 7206 |
Failing that, (in Unix <EM>Alpine</EM>) the name is then checked against |
| 7207 |
the Unix password file. If the entered name matches a username in the |
| 7208 |
system password file, <EM>Alpine</EM> extracts the corresponding Full Name information |
| 7209 |
for that individual, and adds that to the address being entered. |
| 7210 |
<P> |
| 7211 |
|
| 7212 |
However, password file matching can have surprising (incorrect) results if |
| 7213 |
other users of the system do not receive mail at the domain you are using. |
| 7214 |
That is, if either the <A HREF="#user-domain"><EM>user-domain</EM></A> |
| 7215 |
or <A HREF="#use-only"><EM>use-only-domain-name</EM></A> option |
| 7216 |
is set such that the administrative domain of other users on the system |
| 7217 |
isn't accurately reflected, <EM>Alpine</EM> should be told that a password |
| 7218 |
file match is coincidental, |
| 7219 |
and Full Name info will be incorrect. |
| 7220 |
For example, a |
| 7221 |
personal name from the password file could get falsely paired with the |
| 7222 |
entered name as it is turned into an address in the configured domain. |
| 7223 |
<P> |
| 7224 |
|
| 7225 |
If you are seeing this behavior, enabling this feature will prevent Unix |
| 7226 |
<EM>Alpine</EM> from looking up names in the password file to find the Full Name |
| 7227 |
for incomplete addresses you enter. |
| 7228 |
<P> |
| 7229 |
This feature is displayed as "Prevent User Lookup in Password File". |
| 7230 |
<P> |
| 7231 |
|
| 7232 |
<DT> <A NAME="quit-without-confirm"><EM>quit-without-confirm</EM></A> |
| 7233 |
|
| 7234 |
<DD> This feature controls whether or not <EM>Alpine</EM> will ask for confirmation when a |
| 7235 |
<EM>Quit</EM> command is received. |
| 7236 |
<P> |
| 7237 |
This feature is displayed as "Quit Without Confirming". |
| 7238 |
<P> |
| 7239 |
|
| 7240 |
<DT> <A NAME="quote-replace-nonflowed"><EM>quote-replace-nonflowed</EM></A> |
| 7241 |
|
| 7242 |
<DD> This feature, which is only active when |
| 7243 |
<A HREF="#quote-replace-string">Quote-Replace-String</A> is |
| 7244 |
also set, |
| 7245 |
enables quote-replacement on non-flowed messages. It is off |
| 7246 |
by default because a non-flowed message is more dependent on its format, |
| 7247 |
and thus quote-replacement may cause less-than-pleasing results. |
| 7248 |
Setting this feature will cause quote-replacement similar to that of flowed |
| 7249 |
messages, but with the added possibility of long lines being wrapped |
| 7250 |
into new lines if the Quote-Replacement-String is longer than the string |
| 7251 |
it is replacing, which is "> ". |
| 7252 |
|
| 7253 |
<P> |
| 7254 |
|
| 7255 |
<DT> <A NAME="reply-always-uses-reply-to"><EM>reply-always-uses-reply-to</EM></A> |
| 7256 |
|
| 7257 |
<DD> If set, <EM>Alpine</EM> |
| 7258 |
will not prompt when a message being replied to contains a <EM>Reply-To:</EM> |
| 7259 |
header value, but will simply use its value (as opposed to using the |
| 7260 |
<EM>From:</EM> field's value). |
| 7261 |
<P> |
| 7262 |
|
| 7263 |
<DT> <A NAME="return-to-inbox-without-confirm"><EM>return-to-inbox-without-confirm</EM></A> |
| 7264 |
|
| 7265 |
<DD> |
| 7266 |
Normally, when you use the TAB |
| 7267 |
command and there are no more folders or newsgroups to visit, you are asked |
| 7268 |
if you want to return to the INBOX. |
| 7269 |
If this feature is set you will not be asked. |
| 7270 |
It will be assumed that you do want to return to the INBOX. |
| 7271 |
<P> |
| 7272 |
This feature is displayed as "Return to INBOX Without Confirming". |
| 7273 |
<P> |
| 7274 |
|
| 7275 |
<DT> <A NAME="save-aggregates-copy-sequence"><EM>save-aggregates-copy-sequence</EM></A> |
| 7276 |
|
| 7277 |
<DD> This feature will optimize an aggregate copy operation, if |
| 7278 |
possible, by issuing a single IMAP <EM>COPY</EM> command with a |
| 7279 |
list of the messages to be copied. |
| 7280 |
This feature is set by default. |
| 7281 |
This may reduce network traffic and elapsed time for the Save. |
| 7282 |
<EM>However, many IMAP servers (including the UW IMAP server) do |
| 7283 |
not preserve the order of messages when this optimization is applied.</EM> |
| 7284 |
If this feature is not set, |
| 7285 |
<EM>Alpine</EM> will copy each message individually and the order of the |
| 7286 |
messages will be preserved. |
| 7287 |
<P> |
| 7288 |
This feature is displayed as "Save Combines Copies (may be out of order)". |
| 7289 |
<P> |
| 7290 |
|
| 7291 |
<DT> <A NAME="save-partial-wo-confirm"><EM>save-partial-msg-without-confirm</EM></A> |
| 7292 |
|
| 7293 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s Save command. |
| 7294 |
By default, when you Save a message that has some deleted parts, you will |
| 7295 |
be asked to confirm that you want to Save with a prompt that looks like: |
| 7296 |
<P> |
| 7297 |
<CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER> |
| 7298 |
<P> |
| 7299 |
If this feature is set, you will not be asked. |
| 7300 |
<P> |
| 7301 |
This feature is displayed as "Save Partial Message Without Confirming". |
| 7302 |
<P> |
| 7303 |
|
| 7304 |
<DT> <A NAME="save-will-advance"><EM>save-will-advance</EM></A> |
| 7305 |
|
| 7306 |
<DD> If set, <EM>Save</EM> will |
| 7307 |
(in addition to copying the current message to the designated folder) also |
| 7308 |
advance to the next message. |
| 7309 |
<P> |
| 7310 |
|
| 7311 |
<DT> <A NAME="save-will-not-delete"><EM>save-will-not-delete</EM></A> |
| 7312 |
|
| 7313 |
<DD> If set, <EM>Save</EM> will |
| 7314 |
not mark the message Deleted (its default behavior) after it has been |
| 7315 |
copied to the designated folder. |
| 7316 |
<P> |
| 7317 |
|
| 7318 |
<DT> <A NAME="save-will-quote"><EM>save-will-quote-leading-froms</EM></A> |
| 7319 |
|
| 7320 |
<DD> This feature controls an aspect of the <EM>Save</EM> command |
| 7321 |
(and also the way |
| 7322 |
outgoing messages are saved to an FCC folder). If set, <EM>Alpine</EM> will add |
| 7323 |
a leading <CODE>></CODE> character in front of message |
| 7324 |
lines beginning with "From" when they are |
| 7325 |
saved to another folder, including lines syntactically |
| 7326 |
distinguishable from the type of message separator line commonly used on |
| 7327 |
Unix systems. |
| 7328 |
<P> |
| 7329 |
|
| 7330 |
The default behavior is that a <CODE>></CODE> will be prepended only to lines |
| 7331 |
beginning with "From " that might otherwise be confused with a message |
| 7332 |
separator line on Unix systems. If <EM>Alpine</EM> is the only mail program you use, |
| 7333 |
this default is reasonable. If another program you use has trouble |
| 7334 |
displaying a message with an unquoted From saved by <EM>Alpine</EM>, you should |
| 7335 |
enable this feature. This feature only applies to the common Unix mailbox |
| 7336 |
format that uses message separator lines beginning with "From ". If |
| 7337 |
<EM>Alpine</EM> has been configured to use a different mailbox format (possibly |
| 7338 |
incompatible with other mail programs), then this issue does not arise, |
| 7339 |
and the feature is irrelevant. |
| 7340 |
<P> |
| 7341 |
|
| 7342 |
<DT> <A NAME="scramble-message-id"><EM>scramble-message-id</EM></A> |
| 7343 |
|
| 7344 |
<DD> Normally the Message-ID header that <EM>Alpine</EM> generates when sending a message |
| 7345 |
contains the name of the computer from which the message is being sent. |
| 7346 |
Some believe that this hostname could be used by spammers or could |
| 7347 |
be used by others for nefarious purposes. |
| 7348 |
If this feature is set, that name will be transformed with a simple |
| 7349 |
Rot13 transformation. |
| 7350 |
The result will still have the correct syntax for a Message-ID but the |
| 7351 |
part of the MessageID that is often a domain name will not be an actual |
| 7352 |
domain name because the letters will be scrambled. |
| 7353 |
<P> |
| 7354 |
It is possible (but unlikely?) that some spam detection |
| 7355 |
software will use that as a reason to reject the mail as spam. |
| 7356 |
It has also been reported that some spam detection software uses the |
| 7357 |
fact that there are no dots after the "@" as a reason to reject |
| 7358 |
messages. |
| 7359 |
If your <EM>PC-Alpine</EM> Message-ID is using a name without a dot that is because |
| 7360 |
that is what Windows thinks is your "Full computer name". |
| 7361 |
The method used to set this varies from one type of Windows to another but |
| 7362 |
check under Settings -> Control Panel -> System and |
| 7363 |
look for Network Identification or Computer Name or something similar. |
| 7364 |
How to set it is beyond the scope of <EM>Alpine</EM>. |
| 7365 |
<P> |
| 7366 |
This feature is displayed as "Scramble the Message-ID When Sending". |
| 7367 |
<P> |
| 7368 |
|
| 7369 |
<DT> <A NAME="select-without-confirm"><EM>select-without-confirm</EM></A> |
| 7370 |
|
| 7371 |
<DD> This feature controls an aspect of |
| 7372 |
<EM>Alpine</EM>'s <EM>Save</EM>, <EM>Export</EM>, and <EM>Goto</EM> commands. |
| 7373 |
These commands all take text input to specify the name of the folder or |
| 7374 |
file to be used, but allow you to press <EM>^T</EM> for a |
| 7375 |
list of possible names. |
| 7376 |
If set, the selected name will be used immediately, without further |
| 7377 |
opportunity to confirm or edit the name. |
| 7378 |
<P> |
| 7379 |
This feature is displayed as "Select Ctrl-T Foldername Without Confirming". |
| 7380 |
<P> |
| 7381 |
|
| 7382 |
<DT> <A NAME="send-without-confirm"><EM>send-without-confirm</EM></A> |
| 7383 |
|
| 7384 |
<DD> By default, when you send or post a message you will be asked to confirm |
| 7385 |
with a question that looks something like: |
| 7386 |
|
| 7387 |
<P> |
| 7388 |
<CENTER><SAMP>Send message?</SAMP></CENTER> |
| 7389 |
<P> |
| 7390 |
|
| 7391 |
If this feature is set, you |
| 7392 |
will <B>not</B> be prompted to confirm your intent to send |
| 7393 |
and your message will be sent. |
| 7394 |
<P> |
| 7395 |
If this feature is set it disables some possibilities and renders some |
| 7396 |
other features meaningless. |
| 7397 |
You will not be able to use |
| 7398 |
<A HREF="#sending-filters">Sending Filters</A>, |
| 7399 |
Verbose sending mode, |
| 7400 |
<A HREF="#enable-background-sending">Background Sending</A>, |
| 7401 |
<A HREF="#enable-delivery-status-notification">Delivery Status Notifications</A>, |
| 7402 |
or ^V to turn off the generation of flowed text for this message. |
| 7403 |
These options are normally available as suboptions in the Send prompt, but |
| 7404 |
with no Send prompt the options are gone. |
| 7405 |
|
| 7406 |
<P> |
| 7407 |
A somewhat related feature is |
| 7408 |
<A HREF="#quell-extra-post-prompt">quell-extra-post-prompt</A>. |
| 7409 |
which may be used to eliminate the extra confirmation |
| 7410 |
question when posting to a newsgroup. |
| 7411 |
<P> |
| 7412 |
This feature is displayed as "Send Without Confirming". |
| 7413 |
<P> |
| 7414 |
|
| 7415 |
<DT> <A NAME="separate-folder-and-directory-display"><EM>separate-folder-and-directory-display</EM></A> |
| 7416 |
|
| 7417 |
<DD> This feature affects folder collections wherein a folder |
| 7418 |
and directory can have the same name. By default, <EM>Alpine</EM> displays them |
| 7419 |
only once, denoting that it is both a folder and directory by appending |
| 7420 |
the folder name with the hierarchy character enclosed |
| 7421 |
in square brackets. |
| 7422 |
<P> |
| 7423 |
|
| 7424 |
Enabling this feature will cause <EM>Alpine</EM> to display such names |
| 7425 |
separately marking the name representing a directory with a trailing |
| 7426 |
hierarchy delimiter (typically the slash, "/", character). |
| 7427 |
<P> |
| 7428 |
|
| 7429 |
The feature also alters the command set slightly. By default, the |
| 7430 |
right-arrow descends into the directory, while hitting the Return key will |
| 7431 |
cause the folder by that name to be opened. |
| 7432 |
<P> |
| 7433 |
|
| 7434 |
With this feature set, the Return key will open the highlighted folder, or |
| 7435 |
enter the highlighted directory. |
| 7436 |
<P> |
| 7437 |
|
| 7438 |
<DT> <A NAME="show-cursor"><EM>show-cursor</EM></A> |
| 7439 |
|
| 7440 |
<DD> If set, the system |
| 7441 |
cursor will move to convenient locations in the displays. For example, |
| 7442 |
to the beginning of the status field of the highlighted index line, or |
| 7443 |
to the highlighted word after a successful <EM>WhereIs</EM> command. |
| 7444 |
It is intended to draw your attention to the <EM>interesting</EM> |
| 7445 |
spot on the screen. |
| 7446 |
<P> |
| 7447 |
|
| 7448 |
<DT> <A NAME="show-plain-text-internally"><EM>show-plain-text-internally</EM></A> |
| 7449 |
|
| 7450 |
<DD> This feature modifies the method <EM>Alpine</EM> uses to display Text/Plain |
| 7451 |
MIME attachments from the Attachment Index screen. Normally, the |
| 7452 |
"View" command searches for any externally defined (usually |
| 7453 |
via the Mailcap file) viewer, |
| 7454 |
and displays the selected text within that viewer. |
| 7455 |
|
| 7456 |
<P> |
| 7457 |
Enabling this feature causes <EM>Alpine</EM> to ignore any external viewer |
| 7458 |
settings and always display text with <EM>Alpine</EM>'s internal viewer. |
| 7459 |
|
| 7460 |
<P> |
| 7461 |
|
| 7462 |
<DT> <A NAME="show-selected-in-boldface"><EM>show-selected-in-boldface</EM></A> |
| 7463 |
|
| 7464 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s aggregate operation commands; |
| 7465 |
in particular, the <EM>Select</EM> and <EM>WhereIs</EM> commands. |
| 7466 |
<EM>Select</EM> and <EM>WhereIs</EM> (with |
| 7467 |
the <EM>^X</EM> subcommand) will search the current folder |
| 7468 |
for messages meeting a |
| 7469 |
specified criteria, and <EM>tag</EM> the resulting |
| 7470 |
messages with an <EM>X</EM> in the |
| 7471 |
first column of the applicable lines in the "Folder Index". If this feature |
| 7472 |
is set, instead of using the <EM>X</EM> to denote a selected message, |
| 7473 |
<EM>Alpine</EM> will attempt to display those index lines in boldface. |
| 7474 |
Whether this is preferable to the <EM>X</EM> will depend on personal |
| 7475 |
taste and the type of terminal being used. |
| 7476 |
<P> |
| 7477 |
|
| 7478 |
<DT> <A NAME="show-sort"><EM>show-sort</EM></A> |
| 7479 |
|
| 7480 |
<DD> If this feature is set and there is sufficient space on the screen, |
| 7481 |
a short indication of the current sort order will be |
| 7482 |
added in the titlebar (the top line on the screen), before the name |
| 7483 |
of the folder. |
| 7484 |
For example, with the default Arrival sort in effect, |
| 7485 |
the display would have the characters |
| 7486 |
|
| 7487 |
<P><CENTER>[A]</CENTER><P> |
| 7488 |
|
| 7489 |
added between the title of the screen and the folder name. |
| 7490 |
The letters are the same as the letters you may type to manually |
| 7491 |
sort a folder with the SortIndex command ($). |
| 7492 |
The letters in the table below are the ones that may show |
| 7493 |
up in the titlebar line. |
| 7494 |
<P> |
| 7495 |
<TABLE> |
| 7496 |
<TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR> |
| 7497 |
<TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR> |
| 7498 |
<TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR> |
| 7499 |
<TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR> |
| 7500 |
<TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR> |
| 7501 |
<TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR> |
| 7502 |
<TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR> |
| 7503 |
<TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR> |
| 7504 |
<TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR> |
| 7505 |
<TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR> |
| 7506 |
</TABLE> |
| 7507 |
<P> |
| 7508 |
If the sort order is Reversed, the letter above will be preceded by the letter |
| 7509 |
"R", for example |
| 7510 |
|
| 7511 |
<P><CENTER>[RS]</CENTER><P> |
| 7512 |
|
| 7513 |
means that a Reverse Subject sort is in effect. |
| 7514 |
For the case where the sort is in Reverse Arrival order, the "A" is |
| 7515 |
left out, and just an "R" is shown. |
| 7516 |
|
| 7517 |
<P><CENTER>[R]</CENTER> |
| 7518 |
<P> |
| 7519 |
This feature is displayed as "Show Sort in Titlebar". |
| 7520 |
<P> |
| 7521 |
|
| 7522 |
<DT> <A NAME="sig-at-bot"><EM>signature-at-bottom</EM></A> |
| 7523 |
|
| 7524 |
<DD> If this feature |
| 7525 |
is set, and a message being <EM>Repl</EM>ied to is being included in |
| 7526 |
the reply, then the |
| 7527 |
contents of the signature file (if any) will be inserted after the included |
| 7528 |
message. |
| 7529 |
This feature does not affect the results of a <EM>Forward</EM> command. |
| 7530 |
<P> |
| 7531 |
|
| 7532 |
<DT> <A NAME="single-column-folder-list"><EM>single-column-folder-list</EM></A> |
| 7533 |
|
| 7534 |
<DD> If set, the "Folder List" screen will list one folder per line |
| 7535 |
instead of several per line. |
| 7536 |
<P> |
| 7537 |
|
| 7538 |
<DT> <A NAME="slash-collapses-entire-thread"><EM>slash-collapses-entire-thread</EM></A> |
| 7539 |
|
| 7540 |
<DD> Normally, the Collapse/Expand Thread command Collapses or Expands the subthread which |
| 7541 |
starts at the currently highlighted message, if any. |
| 7542 |
If this feature is set, then the slash command Collapses or Expands the |
| 7543 |
<EM>entire</EM> current thread instead of just the subthread. |
| 7544 |
<P> |
| 7545 |
|
| 7546 |
<DT> <A NAME="smime-dont-do-smime"><EM>smime-dont-do-smime</EM></A> |
| 7547 |
|
| 7548 |
<DD> UNIX <EM>Alpine</EM> only. |
| 7549 |
<P> |
| 7550 |
Setting this feature turns off all of <EM>Alpine</EM>'s S/MIME support. |
| 7551 |
You might want to set this if you are having trouble due to the S/MIME support. |
| 7552 |
<P> |
| 7553 |
<UL> |
| 7554 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 7555 |
</UL><P> |
| 7556 |
This feature is displayed as "S/MIME -- Turn off S/MIME". |
| 7557 |
<P> |
| 7558 |
|
| 7559 |
<DT> <A NAME="smime-encrypt-by-default"><EM>smime-encrypt-by-default</EM></A> |
| 7560 |
|
| 7561 |
<DD> UNIX <EM>Alpine</EM> only. |
| 7562 |
<P> |
| 7563 |
This feature only has an effect if your version of <EM>Alpine</EM> includes |
| 7564 |
support for S/MIME. |
| 7565 |
It affects <EM>Alpine</EM>'s behavior when you send a message. |
| 7566 |
If this option is set, the "Encrypt" option will default to ON when sending messages. |
| 7567 |
<P> |
| 7568 |
Only the default value is affected. |
| 7569 |
In any case, you may still toggle the Encrypt option on or off before sending |
| 7570 |
with the "E Encrypt" command (provided you have a the public digital ID |
| 7571 |
for the recipient). |
| 7572 |
<P> |
| 7573 |
<UL> |
| 7574 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 7575 |
</UL><P> |
| 7576 |
This feature is displayed as "S/MIME -- Encrypt by Default". |
| 7577 |
<P> |
| 7578 |
|
| 7579 |
<DT> <A NAME="smime-remember-passphrase"><EM>smime-remember-passphrase</EM></A> |
| 7580 |
|
| 7581 |
<DD> UNIX <EM>Alpine</EM> only. |
| 7582 |
<P> |
| 7583 |
This feature only has an effect if your version of <EM>Alpine</EM> includes |
| 7584 |
support for S/MIME. |
| 7585 |
If this option is set, you will only have to enter your passphrase for your private key |
| 7586 |
once during an <EM>Alpine</EM> session. |
| 7587 |
<P> |
| 7588 |
<UL> |
| 7589 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 7590 |
</UL><P> |
| 7591 |
This feature is displayed as "S/MIME -- Remember S/MIME Passphrase". |
| 7592 |
<P> |
| 7593 |
|
| 7594 |
<DT> <A NAME="smime-sign-by-default"><EM>smime-sign-by-default</EM></A> |
| 7595 |
|
| 7596 |
<DD> UNIX <EM>Alpine</EM> only. |
| 7597 |
<P> |
| 7598 |
This feature only has an effect if your version of <EM>Alpine</EM> includes |
| 7599 |
support for S/MIME. |
| 7600 |
It affects <EM>Alpine</EM>'s behavior when you send a message. |
| 7601 |
If this option is set, the "Sign" option will default to ON when sending messages. |
| 7602 |
<P> |
| 7603 |
Only the default value is affected. |
| 7604 |
In any case, you may still toggle the Signing option on or off before sending |
| 7605 |
with the "G Sign" command (provided you have a personal digital ID |
| 7606 |
certificate). |
| 7607 |
<P> |
| 7608 |
<UL> |
| 7609 |
<LI><A HREF="config-notes.html#smime-general">General S/MIME Overview</A> |
| 7610 |
</UL><P> |
| 7611 |
This feature is displayed as "S/MIME -- Sign by Default". |
| 7612 |
<P> |
| 7613 |
|
| 7614 |
<DT> <A NAME="sort-default-fcc-alpha"><EM>sort-default-fcc-alpha</EM></A> |
| 7615 |
|
| 7616 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen. |
| 7617 |
If set, the default FCC folder will be sorted alphabetically with the other |
| 7618 |
folders instead of appearing right after the INBOX. |
| 7619 |
<P> |
| 7620 |
This feature is displayed as "Sort Default Fcc Folder Alphabetically". |
| 7621 |
<P> |
| 7622 |
|
| 7623 |
<DT> <A NAME="sort-default-save-alpha"><EM>sort-default-save-alpha</EM></A> |
| 7624 |
|
| 7625 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen. |
| 7626 |
If set, the default save folder will be sorted alphabetically with the other |
| 7627 |
folders instead of appearing right after the INBOX (and default FCC folder). |
| 7628 |
<P> |
| 7629 |
This feature is displayed as "Sort Default Save Folder Alphabetically". |
| 7630 |
<P> |
| 7631 |
|
| 7632 |
<DT> <A NAME="spell-check-before-sending"><EM>spell-check-before-sending</EM></A> |
| 7633 |
|
| 7634 |
<DD> When this feature is set, every composed message will be spell-checked before |
| 7635 |
being sent. |
| 7636 |
|
| 7637 |
<P> |
| 7638 |
|
| 7639 |
<DT> <A NAME="store-window-position-in-config"><EM>store-window-position-in-config</EM></A> |
| 7640 |
|
| 7641 |
<DD> Normally, <EM>PC-Alpine</EM> will store its window size and position in the |
| 7642 |
Windows Registry. |
| 7643 |
This is convenient if you want to use the same remote |
| 7644 |
configuration from more than one PC. |
| 7645 |
If you use multiple configuration files to start <EM>PC-Alpine</EM>, you may want |
| 7646 |
to store the window size and position in the configuration file instead |
| 7647 |
of in the Registry. |
| 7648 |
Setting this feature causes that to happen. |
| 7649 |
|
| 7650 |
<P> |
| 7651 |
|
| 7652 |
<DT> <A NAME="strip-from-sigdashes-on-reply"><EM>strip-from-sigdashes-on-reply</EM></A> |
| 7653 |
|
| 7654 |
<DD> This feature doesn't do anything if the feature |
| 7655 |
<A HREF="#enable-sigdashes"><EM>enable-sigdashes</EM></A> is turned on. |
| 7656 |
However, if the <EM>enable-sigdashes</EM> feature is not turned on, |
| 7657 |
then turning on this feature enables support for the convention |
| 7658 |
of not including text beyond the sigdashes line when Replying or Following |
| 7659 |
up to a message and including the text of that message. |
| 7660 |
<P> |
| 7661 |
In other words, this is a way to turn on the signature stripping behavior |
| 7662 |
without also turning on the dashes-adding behavior. |
| 7663 |
<P> |
| 7664 |
|
| 7665 |
<DT> <A NAME="strip-whitespace-before-send"><EM>strip-whitespace-before=send</EM></A> |
| 7666 |
|
| 7667 |
<DD> Trailing whitespace is not stripped from |
| 7668 |
a message before sending. Trailing whitespace should have no effect on an |
| 7669 |
email message, and in flowed text can aid in delimiting paragraphs. |
| 7670 |
However, the old behavior of stripping trailing whitespace was in place |
| 7671 |
to better deal with older clients that couldn't handle certain types of |
| 7672 |
text encodings. This feature restores the old behavior |
| 7673 |
<P> |
| 7674 |
Trailing whitespace is of aid to flowed-text-formatted messages, which are |
| 7675 |
generated by default but can be turned off via the |
| 7676 |
<A HREF="#quell-flowed-text">quell-flowed-text</A> feature. |
| 7677 |
strip-whitespace-before-send also has the effect of turning off sending |
| 7678 |
of flowed text. |
| 7679 |
<P> |
| 7680 |
This feature is displayed as "Strip Whitespace Before Sending". |
| 7681 |
<P> |
| 7682 |
|
| 7683 |
<DT> <A NAME="suppress-asterisks-in-password-prompt"><EM>suppress-asterisks-in-password-prompt</EM></A> |
| 7684 |
|
| 7685 |
<DD> When you are running <EM>Alpine</EM> you will sometimes be asked for a password |
| 7686 |
in a prompt on the third line from the bottom of the screen. |
| 7687 |
Normally each password character you type will cause an asterisk to echo |
| 7688 |
on the screen. That gives you some feedback to know that your typing is |
| 7689 |
being recognized. |
| 7690 |
There is a very slight security risk in doing it this way because someone |
| 7691 |
watching over your shoulder might be able to see how many characters there |
| 7692 |
are in your password. |
| 7693 |
If you'd like to suppress the echoing of the asterisks set this feature. |
| 7694 |
<P> |
| 7695 |
|
| 7696 |
<DT> <A NAME="suppress-user-agent-when-sending"><EM>suppress-user-agent-when-sending</EM></A> |
| 7697 |
<DD> If this feature is set then <EM>Alpine</EM> will not generate a |
| 7698 |
<CODE>User-Agent</CODE> header in outgoing messages. |
| 7699 |
<P> |
| 7700 |
|
| 7701 |
<DT> <A NAME="tab-checks-recent"><EM>tab-checks-recent</EM></A> |
| 7702 |
|
| 7703 |
<DD> In a FOLDER LIST screen, the TAB key usually just changes which |
| 7704 |
folder is highlighted. |
| 7705 |
If this feature is set, then the TAB key will cause the number of |
| 7706 |
recent messages and the total number of messages in the highlighted folder |
| 7707 |
to be displayed instead. |
| 7708 |
<P> |
| 7709 |
This feature is displayed as "Tab Checks for Recent Messages". |
| 7710 |
<P> |
| 7711 |
|
| 7712 |
<DT> <A NAME="tab-uses-unseen-for-next-folder"><EM>tab-uses-unseen-for-next-folder</EM></A> |
| 7713 |
|
| 7714 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when using the TAB |
| 7715 |
NextNew Command |
| 7716 |
to move from one folder to the next. |
| 7717 |
<EM>Alpine</EM>'s usual behavior is to search for folders |
| 7718 |
with <EM>Recent</EM> messages in them. |
| 7719 |
Recent messages are messages which have arrived since the last time the |
| 7720 |
folder was opened. |
| 7721 |
|
| 7722 |
<P> |
| 7723 |
Setting this feature causes <EM>Alpine</EM> to search for <EM>Unseen</EM> |
| 7724 |
messages instead of Recent messages. |
| 7725 |
Unseen messages remain Unseen until you view them (or flag then as Seen with |
| 7726 |
the Flag Command). |
| 7727 |
Setting this feature allows you to locate messages you have not read |
| 7728 |
instead of only recently received messages. |
| 7729 |
When this feature is set, the feature |
| 7730 |
<A HREF="#enable-fast-recent-test">Enable-Fast-Recent-Test</A> |
| 7731 |
will have no effect, so the checking may be slower. |
| 7732 |
|
| 7733 |
<P> |
| 7734 |
Another reason why you might want to use this feature is that <EM>Alpine</EM> sometimes |
| 7735 |
opens folders implicitly behind the scenes, and this clears the |
| 7736 |
Recent status of all messages in the folder. |
| 7737 |
One example where this happens is when Saving or filtering a |
| 7738 |
message to another folder. |
| 7739 |
If that message has some <A HREF="#keywords">keywords</A> |
| 7740 |
set, then because of some shortcomings |
| 7741 |
in the IMAP specification, the best way to ensure that those keywords are |
| 7742 |
still set in the saved copy of the message is to open the folder and |
| 7743 |
set the keywords explicitly. |
| 7744 |
Because this clears the Recent status of all messages in that folder the |
| 7745 |
folder will not be found by the NextNew command unless this feature is set. |
| 7746 |
<P> |
| 7747 |
|
| 7748 |
<DT> <A NAME="tab-visits-next-new-message-only"><EM>tab-visits-next-new-message-only</EM></A> |
| 7749 |
|
| 7750 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when using the <EM>TAB</EM> |
| 7751 |
key to move from one message to the next. |
| 7752 |
<EM>Alpine</EM>'s usual behavior is to select the next |
| 7753 |
<EM>Unread</EM> message or message flagged as <EM>Important</EM>. |
| 7754 |
<P> |
| 7755 |
|
| 7756 |
Setting this feature causes <EM>Alpine</EM> to skip the |
| 7757 |
messages flagged as <EM>Important</EM>, |
| 7758 |
and select <EM>Unread</EM> messages exclusively. |
| 7759 |
Tab behavior when there are no |
| 7760 |
new messages left to select remains unchanged. |
| 7761 |
<P> |
| 7762 |
|
| 7763 |
<DT> <A NAME="termdef-takes-precedence"><EM>termdef-takes-precedence</EM></A> |
| 7764 |
|
| 7765 |
<DD> This feature may affect <EM>Alpine</EM>'s low-level input routines. Termcap (or |
| 7766 |
terminfo, depending on how your copy of <EM>Alpine</EM> was compiled and linked) |
| 7767 |
is the name of the database which describes terminal capabilities. In |
| 7768 |
particular, it describes the sequences of characters that various keys |
| 7769 |
will emit. |
| 7770 |
|
| 7771 |
<P> |
| 7772 |
An example would be the Up Arrow key on the keyboard. Up |
| 7773 |
Arrow is not a distinct character on most Unix systems. When you press |
| 7774 |
the Up Arrow key a short sequence of characters are produced. This |
| 7775 |
sequence is supposed to be described in the termcap database by the |
| 7776 |
"ku" capability (or by the "kcuu1" capability if you |
| 7777 |
are using terminfo instead of termcap). |
| 7778 |
|
| 7779 |
<P> |
| 7780 |
By default, <EM>Alpine</EM> defines some terminal |
| 7781 |
escape sequences that are commonly used. For example, the sequence |
| 7782 |
"ESC O A" is recognized as an Up Arrow key. The sequence |
| 7783 |
"ESC [ A" |
| 7784 |
is also recognized as an Up Arrow key. These are chosen because common |
| 7785 |
terminals like VT100's or ANSI standard terminals produce these |
| 7786 |
sequences when you press the Up Arrow key. |
| 7787 |
|
| 7788 |
<P> |
| 7789 |
If your system's termcap |
| 7790 |
(terminfo) database assigns some other function to the sequence |
| 7791 |
"ESC O A" |
| 7792 |
it is usually ignored by <EM>Alpine</EM>. Also, if your termcap (terminfo) |
| 7793 |
database assigns a sequence which doesn't begin with an escape |
| 7794 |
character (<SAMP>ESC</SAMP>) it is usually ignored by <EM>Alpine</EM>. |
| 7795 |
This usually works fine |
| 7796 |
because most terminals emit the escape sequences that <EM>Alpine</EM> has defined |
| 7797 |
by default. We have also found that it is usually better to have these |
| 7798 |
defaults take precedence over the definitions contained in the database |
| 7799 |
because the defaults are more likely to be correct than the database. |
| 7800 |
|
| 7801 |
<P> |
| 7802 |
There are some terminals where this breaks down. If you want <EM>Alpine</EM> to |
| 7803 |
believe the definitions given in your termcap (terminfo) database in |
| 7804 |
preference to the defaults the <EM>Alpine</EM> itself sets up, then you may turn |
| 7805 |
this feature on. Then, sequences of characters which are defined in |
| 7806 |
both termcap (terminfo) and in <EM>Alpine</EM>'s set of defaults will be |
| 7807 |
interpreted the way that termcap (terminfo) says they should be |
| 7808 |
interpreted. Also, if your terminal capabilities database assigns a |
| 7809 |
sequence which doesn't begin with escape, it will not be ignored. |
| 7810 |
<P> |
| 7811 |
|
| 7812 |
<DT> <A NAME="thread-index-shows-important-color"><EM>thread-index-shows-important-color</EM></A> |
| 7813 |
|
| 7814 |
<DD> This option affects only the THREAD INDEX screen. |
| 7815 |
Whether or not you ever see a THREAD INDEX screen depends on the setting |
| 7816 |
of the configuration option |
| 7817 |
<A HREF="#threading-index-style"><EM>threading-index-style</EM></A> |
| 7818 |
and on the sort order of the index. |
| 7819 |
If a message within a thread is flagged as Important |
| 7820 |
and this option is set, then |
| 7821 |
the entire line in the THREAD INDEX will be colored the color of the |
| 7822 |
Index-important Symbol, which can be set using the |
| 7823 |
Setup Kolor screen. |
| 7824 |
<P> |
| 7825 |
|
| 7826 |
<DT> <A NAME="try-alternative-authentication-driver-first"><EM>try-alternative-authentication-driver-first</EM></A> |
| 7827 |
|
| 7828 |
<DD> This feature affects how <EM>Alpine</EM> connects to IMAP servers. |
| 7829 |
It's utility has largely been overtaken by events, |
| 7830 |
but it may still be useful in some circumstances. |
| 7831 |
If you only connect to modern IMAP servers that support |
| 7832 |
"TLS" you can ignore this feature. |
| 7833 |
|
| 7834 |
<P> |
| 7835 |
Details: |
| 7836 |
|
| 7837 |
<P> |
| 7838 |
By default, <EM>Alpine</EM> will attempt to connect to an IMAP server on the |
| 7839 |
normal IMAP service port (143), and if the server offers "Transport Layer |
| 7840 |
Security" (TLS) and <EM>Alpine</EM> has been compiled with encryption capability, |
| 7841 |
then a secure (encrypted) session will be negotiated. |
| 7842 |
|
| 7843 |
<P> |
| 7844 |
With this feature enabled, before connecting on the normal IMAP port, <EM>Alpine</EM> |
| 7845 |
will first attempt to connect to an alternate IMAP service port (993) used |
| 7846 |
specifically for encrypted IMAP sessions via the Secure Sockets Layer |
| 7847 |
(SSL) method. |
| 7848 |
If the SSL attempt fails, <EM>Alpine</EM> will then try the default |
| 7849 |
behavior described in the previous paragraph. |
| 7850 |
|
| 7851 |
<P> |
| 7852 |
TLS negotiation on the normal port is preferred, and supersedes the use of |
| 7853 |
SSL on port 993, but older servers may not provide TLS support. |
| 7854 |
This feature may be convenient when accessing IMAP servers that do not support |
| 7855 |
TLS, but do support SSL connections on port 993. |
| 7856 |
However, it is important to understand that with this feature enabled, |
| 7857 |
<EM>Alpine</EM> will <EM>attempt</EM> to make a secure connection if that is possible, |
| 7858 |
but it will proceed to make an insecure connection if that is the only |
| 7859 |
option offered by the server, or if the <EM>Alpine</EM> in question has been built |
| 7860 |
without encryption capability. |
| 7861 |
|
| 7862 |
<P> |
| 7863 |
Note that this feature specifies a per-user (or system-wide) default |
| 7864 |
behavior, but host/folder specification flags may be used to control the |
| 7865 |
behavior of any specific connection. |
| 7866 |
This feature interacts with some of |
| 7867 |
the possible host/folder path specification flags as follows: |
| 7868 |
|
| 7869 |
<P> |
| 7870 |
The <SAMP>/tls</SAMP> host flag, for example, |
| 7871 |
|
| 7872 |
<P> |
| 7873 |
<CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER> |
| 7874 |
<P> |
| 7875 |
will over-ride this feature for the specified host by bypassing the |
| 7876 |
SSL connection attempt. |
| 7877 |
Moreover, with <SAMP>/tls</SAMP> specified, |
| 7878 |
the connection attempt will fail if the |
| 7879 |
service on port 143 does not offer TLS support. |
| 7880 |
|
| 7881 |
<P> |
| 7882 |
The <SAMP>/ssl</SAMP> host flag, for example, |
| 7883 |
|
| 7884 |
<P> |
| 7885 |
<CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER> |
| 7886 |
<P> |
| 7887 |
will insist on an SSL connection for the specified host, |
| 7888 |
and will fail if the SSL service on port 993 is not available. |
| 7889 |
<EM>Alpine</EM> will not subsequently retry a connection |
| 7890 |
on port 143 if <SAMP>/ssl</SAMP> is specified. |
| 7891 |
<P> |
| 7892 |
|
| 7893 |
<DT> <A NAME="unselect-will-not-advance"><EM>unselect-will-not-advance</EM></A> |
| 7894 |
|
| 7895 |
<DD> Normally, when the Unselect current message command (:) is typed when the |
| 7896 |
current message is selected, the message will be unselected and the next |
| 7897 |
message will become the current message. |
| 7898 |
If this feature is set, the cursor will not advance to the next message. |
| 7899 |
Instead, the current message will remain the current message after |
| 7900 |
unselecting. |
| 7901 |
<P> |
| 7902 |
|
| 7903 |
<DT> <A NAME="use-current-dir"><EM>use-current-dir</EM></A> |
| 7904 |
|
| 7905 |
<DD> This feature controls an aspect of several commands. If set, your |
| 7906 |
"current working directory" will be used instead of your home directory |
| 7907 |
for all of the following operations: |
| 7908 |
|
| 7909 |
<UL> |
| 7910 |
<LI> <EM>Export</EM> in the "Folder Index" and "Message Text" screens |
| 7911 |
<LI> Attachment <EM>Save</EM> in the "Message Text" and "Attachment Text" screens |
| 7912 |
<LI> <EM>^R</EM> file inclusion in the Composer |
| 7913 |
<LI> <EM>^J</EM> file attachment in the Composer |
| 7914 |
</UL> |
| 7915 |
<P> |
| 7916 |
This feature is displayed as "Use Current Directory". |
| 7917 |
<P> |
| 7918 |
|
| 7919 |
<DT> <A NAME="use-function-keys"><EM>use-function-keys</EM></A> |
| 7920 |
|
| 7921 |
<DD> This feature specifies that <EM>Alpine</EM> will |
| 7922 |
respond to function keys instead of |
| 7923 |
the normal single-letter commands. In this mode, the key menus at the |
| 7924 |
bottom of each screen will show function key designations instead of the |
| 7925 |
normal mnemonic key. |
| 7926 |
<P> |
| 7927 |
|
| 7928 |
<DT> <A NAME="use-reg-start-rule"><EM>use-regular-startup-rule-for-stayopen-folders</EM></A> |
| 7929 |
|
| 7930 |
<DD> This feature affects which message is selected as the current message |
| 7931 |
when you enter a |
| 7932 |
<A HREF="#stay-open-folders">Stay Open</A> folder. |
| 7933 |
<P> |
| 7934 |
Normally, the starting position for an incoming folder (which most Stay Open |
| 7935 |
folders will likely be) is controlled by the |
| 7936 |
<A HREF="#incoming-startup-rule"><EM>Incoming-Startup-Rule</EM></A>. |
| 7937 |
However, if a folder is a Stay Open folder, when you re-enter the folder |
| 7938 |
after the first time the current message will be the same as it was when |
| 7939 |
you left the folder. |
| 7940 |
An exception is made if you use the TAB command to get to the folder. |
| 7941 |
In that case, the message number will be incremented by one from what it |
| 7942 |
was when you left the folder. |
| 7943 |
<P> |
| 7944 |
The above special behavior is thought to be useful. |
| 7945 |
However, it is special and different from what you might at first expect. |
| 7946 |
If this feature is set, then Stay Open folders will not be treated specially |
| 7947 |
as far as the startup rule is concerned. |
| 7948 |
<P> |
| 7949 |
|
| 7950 |
<DT> <A NAME="use-resent-to-in-rules"><EM>use-resent-to-in-rules</EM></A> |
| 7951 |
|
| 7952 |
<DD> This feature is turned off by default because turning it on causes problems |
| 7953 |
with some deficient IMAP servers. |
| 7954 |
In <EM>Alpine</EM> Filters and other types of Rules, if the |
| 7955 |
Pattern |
| 7956 |
contains a To header pattern and this feature is turned on, |
| 7957 |
then a check is made in the message to see |
| 7958 |
if a Resent-To header is present, and that is used instead of the To header. |
| 7959 |
If this feature is not turned on, then the regular To header will always |
| 7960 |
be used. |
| 7961 |
<P> |
| 7962 |
|
| 7963 |
<DT> <A NAME="use-sender-not-x-sender"><EM>use-sender-not-x-sender</EM></A> |
| 7964 |
|
| 7965 |
<DD> Normally <EM>Alpine</EM> on Unix adds a header line labeled <EM>X-X-Sender</EM>, |
| 7966 |
if the sender is different from the <EM>From:</EM> line. |
| 7967 |
|
| 7968 |
<P> |
| 7969 |
The standard specifies that this header |
| 7970 |
line should be labeled <EM>Sender</EM>, not <EM>X-X-Sender</EM>. |
| 7971 |
Setting this feature causes |
| 7972 |
<EM>Sender</EM> to be used instead of <EM>X-X-Sender</EM>. The standard also states |
| 7973 |
that the data associated with this header field should not be used as a Reply address. |
| 7974 |
Unfortunately, certain implementations of mail list management servers will use the |
| 7975 |
Sender address for such purposes. These implementations often even recognize the |
| 7976 |
<EM>X-Sender</EM> fields as being equivalent to the <EM>Sender</EM> field, and use it |
| 7977 |
if present. This is why <EM>Alpine</EM> defaults to <EM>X-X-Sender</EM>. |
| 7978 |
<P> |
| 7979 |
Note, <EM>PC-Alpine</EM> always adds |
| 7980 |
either an <EM>X-X-Sender</EM> line if there is an open, remote mailbox, or an |
| 7981 |
<EM>X-Warning: UNAuthenticated User</EM> otherwise |
| 7982 |
|
| 7983 |
<P> |
| 7984 |
This feature is displayed as "Use Sender Instead of X-X-Sender". |
| 7985 |
<P> |
| 7986 |
|
| 7987 |
<DT> <A NAME="use-subshell-for-suspend"><EM>use-subshell-for-suspend</EM></A> |
| 7988 |
|
| 7989 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when process suspension |
| 7990 |
is enabled and then activated via the <EM>^Z</EM> key. |
| 7991 |
<EM>Alpine</EM> suspension allows one to |
| 7992 |
temporarily interact with the operating system command "shell" without |
| 7993 |
quitting <EM>Alpine</EM>, |
| 7994 |
and then subsequently resume the still-active <EM>Alpine</EM> session. |
| 7995 |
<P> |
| 7996 |
|
| 7997 |
When the <EM>enable-suspend</EM> feature is set and subsequently the |
| 7998 |
<EM>^Z</EM> key is pressed, |
| 7999 |
<EM>Alpine</EM> will normally suspend itself and return temporary |
| 8000 |
control to <EM>Alpine</EM>'s parent shell process. |
| 8001 |
However, if this feature is set, <EM>Alpine</EM> will instead create an |
| 8002 |
inferior subshell process. |
| 8003 |
This is useful when the parent process is not intended to be used |
| 8004 |
interactively. |
| 8005 |
Examples include invoking <EM>Alpine</EM> via the <CODE>-e</CODE> argument |
| 8006 |
of the Unix <EM>xterm</EM> program, or via a menu system. |
| 8007 |
<P> |
| 8008 |
|
| 8009 |
Note that one typically resumes a suspended <EM>Alpine</EM> by entering the Unix |
| 8010 |
<EM>fg</EM> command, but if this feature is set, it will be necessary to enter |
| 8011 |
the <EM>exit</EM> command instead. |
| 8012 |
<P> |
| 8013 |
|
| 8014 |
<DT> <A NAME="use-system-translation"><EM>use-system-translation</EM></A> |
| 8015 |
|
| 8016 |
<DD> UNIX <EM>Alpine</EM> only. <EM>Alpine</EM> normally uses its own internal software to convert between the multi-byte |
| 8017 |
representation of characters and the Unicode representation of those |
| 8018 |
same characters |
| 8019 |
( see the section on <A HREF="low-level.html#char-set">International Character Sets</EM></A>). |
| 8020 |
It converts from the multi-byte characters your keyboard produces to Unicode, |
| 8021 |
and from Unicode to the multi-byte characters your display expects. |
| 8022 |
Alpine also uses its own internal software to decide how much space on |
| 8023 |
the screen a particular Unicode character will occupy. |
| 8024 |
|
| 8025 |
<P> |
| 8026 |
Setting this feature tells <EM>Alpine</EM> to use the system-supplied routines to |
| 8027 |
perform these tasks instead. |
| 8028 |
In particular there are three tasks and three system routines that will |
| 8029 |
be used for these tasks. |
| 8030 |
|
| 8031 |
<P> |
| 8032 |
To convert from multi-byte to Unicode the routine |
| 8033 |
|
| 8034 |
<P> |
| 8035 |
<CENTER><SAMP>mbstowcs</SAMP></CENTER> |
| 8036 |
<P> |
| 8037 |
|
| 8038 |
is used. |
| 8039 |
To convert from Unicode to multi-byte the routine |
| 8040 |
|
| 8041 |
<P> |
| 8042 |
<CENTER><SAMP>wcrtomb</SAMP></CENTER> |
| 8043 |
<P> |
| 8044 |
|
| 8045 |
is used. |
| 8046 |
And to find the screen width a particular Unicode character will |
| 8047 |
occupy the routine used is |
| 8048 |
|
| 8049 |
<P> |
| 8050 |
<CENTER><SAMP>wcwidth</SAMP></CENTER> |
| 8051 |
<P> |
| 8052 |
|
| 8053 |
This feature has been only lightly tested. |
| 8054 |
The internal routines should normally be used unless you run into |
| 8055 |
a problem that you think may be solved by using the system routines. |
| 8056 |
Note that your environment needs to be set up for these |
| 8057 |
routines to work correctly. |
| 8058 |
In particular, the LANG or LC_CTYPE variable in your environment will |
| 8059 |
need to be set. |
| 8060 |
<P> |
| 8061 |
|
| 8062 |
<DT> <A NAME="vertical-folder-list"><EM>vertical-folder-list</EM></A> |
| 8063 |
|
| 8064 |
<DD> This feature controls an aspect of <EM>Alpine</EM>'s FOLDER LIST screen. If set, |
| 8065 |
the folders will be listed alphabetically down the columns rather |
| 8066 |
than across the columns as is the default. |
| 8067 |
|
| 8068 |
<P> |
| 8069 |
This feature is displayed as "Use Vertical Folder List". |
| 8070 |
<P> |
| 8071 |
|
| 8072 |
<DT> <A NAME="warn-if-blank-subject"><EM>warn-if-blank-subject</EM></A> |
| 8073 |
|
| 8074 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being |
| 8075 |
composed. |
| 8076 |
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent |
| 8077 |
has a subject or not. |
| 8078 |
If not, you will be asked if you want to send the message anyway. |
| 8079 |
<P> |
| 8080 |
|
| 8081 |
<DT> <A NAME="warn-if-blank-to-and-cc-and-newsgroups"><EM>warn-if-blank-to-and-cc-and-newsgroups</EM></A> |
| 8082 |
|
| 8083 |
<DD> This feature affects <EM>Alpine</EM>'s behavior when you send a message being |
| 8084 |
composed. |
| 8085 |
If this option is set, <EM>Alpine</EM> will check to see if the message about to be sent |
| 8086 |
has either a To address, a Cc address, or a Newsgroup. |
| 8087 |
If none of these is set, |
| 8088 |
you will be asked if you want to send the message anyway. |
| 8089 |
<P> |
| 8090 |
This feature is closely related to |
| 8091 |
<A HREF="#fcc-only-without-confirm"><EM>fcc-only-without-confirm</EM></A>. |
| 8092 |
<EM>Alpine</EM> will normally ask if you want to copy a message only to the Fcc. |
| 8093 |
This feature also applies to cases where there is a Bcc but still no To, Cc, |
| 8094 |
or Newsgroup. |
| 8095 |
If the Fcc-Only-Without-Confirm feature is set and you are sending a |
| 8096 |
message with only an Fcc, then you won't be asked about sending with |
| 8097 |
a blank To and Cc and Newsgroups header even if this feature is set. |
| 8098 |
Similarly, if you have already been asked if you want to send to the Fcc |
| 8099 |
only and you have answered Yes, then you won't be asked again about sending with |
| 8100 |
blank To, Cc, and Newsgroups headers even if this feature is set. |
| 8101 |
|
| 8102 |
<P> |
| 8103 |
|
| 8104 |
</DL> |
| 8105 |
<P> |
| 8106 |
|
| 8107 |
<H2><A NAME="hidden-config">Hidden Config Variables and Features</A></H2> |
| 8108 |
|
| 8109 |
There are several configuration variables and features which are normally hidden |
| 8110 |
from the user. That is, they don't appear on any of the configuration |
| 8111 |
screens. Some of these are suppressed because they are intended to be used |
| 8112 |
by system administrators, and in fact may only be set in system-wide |
| 8113 |
configuration files. Others are available to users but are thought to be |
| 8114 |
of such little value to most users that their presence on the Config |
| 8115 |
screens would cause more confusion than help. |
| 8116 |
Others are hidden in the Setup/Config screen because they are normally |
| 8117 |
configured in one of the other configuration screens. For example, all |
| 8118 |
of the colors are hidden because the normal way to configure colors is |
| 8119 |
through Setup/Colors not Setup/Config. |
| 8120 |
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A> |
| 8121 |
to cause most of these hidden variables and features to show up at the bottom |
| 8122 |
of the Setup/Config screen. |
| 8123 |
|
| 8124 |
<H3>Hidden Variables Not Settable by Users</H3> |
| 8125 |
|
| 8126 |
These variables are settable only in system-wide configuration files. |
| 8127 |
|
| 8128 |
<UL> |
| 8129 |
<LI> <A HREF="#bugs-add">bugs-additional-data</A> |
| 8130 |
<LI> <A HREF="#bugs">bugs-address</A> |
| 8131 |
<LI> <A HREF="#bugs">bugs-fullname</A> |
| 8132 |
<LI> <A HREF="#forced-abook">forced-abook-entry</A> |
| 8133 |
<LI> <A HREF="#kblock-count">kblock-passwd-count</A> |
| 8134 |
<LI> <A HREF="#bugs">local-address</A> |
| 8135 |
<LI> <A HREF="#bugs">local-fullname</A> |
| 8136 |
<LI> <A HREF="#mail-directory">mail-directory</A> |
| 8137 |
<LI> <A HREF="#standard-printer">standard-printer</A> |
| 8138 |
<LI> <A HREF="#bugs">suggest-address</A> |
| 8139 |
<LI> <A HREF="#bugs">suggest-fullname</A> |
| 8140 |
</UL> |
| 8141 |
|
| 8142 |
<H3>Hidden Variables Which are Settable by Users</H3> |
| 8143 |
|
| 8144 |
These variables are not shown to users but are settable by means |
| 8145 |
of hand editing the personal configuration file. This first group |
| 8146 |
is usually maintained by <EM>Alpine</EM> and there will usually |
| 8147 |
be no reason to edit them by hand. |
| 8148 |
|
| 8149 |
<UL> |
| 8150 |
<LI> <A HREF="#last-version-used">last-version-used</A> |
| 8151 |
<LI> <A HREF="#patterns-filters2">patterns-filters2</A> |
| 8152 |
<LI> <A HREF="#patterns-indexcolors">patterns-indexcolors</A> |
| 8153 |
<LI> <A HREF="#patterns-roles">patterns-roles</A> |
| 8154 |
<LI> <A HREF="#patterns-scores2">patterns-scores2</A> |
| 8155 |
<LI> <A HREF="#remote-abook-metafile">remote-abook-metafile</A> |
| 8156 |
</UL> |
| 8157 |
<P> |
| 8158 |
|
| 8159 |
This group is usually correct but may be changed by system managers or |
| 8160 |
users in special cases. |
| 8161 |
|
| 8162 |
<UL> |
| 8163 |
<LI> <A HREF="#disable-these-auths">disable-these-authenticators</A> |
| 8164 |
<LI> <A HREF="#disable-these-drivers">disable-these-drivers</A> |
| 8165 |
<LI> <A HREF="#last-time">last-time-prune-questioned</A> |
| 8166 |
<LI> <A HREF="#new-version-threshold">new-version-threshold</A> |
| 8167 |
<LI> <A HREF="#remote-abook-history">remote-abook-history</A> |
| 8168 |
<LI> <A HREF="#remote-abook-validity">remote-abook-validity</A> |
| 8169 |
<LI> <A HREF="#rsh-command">rsh-command</A> |
| 8170 |
<LI> <A HREF="#rsh-open-timeout">rsh-open-timeout</A> |
| 8171 |
<LI> <A HREF="#rsh-path">rsh-path</A> |
| 8172 |
<LI> <A HREF="#sendmail-path">sendmail-path</A> |
| 8173 |
<LI> <A HREF="#ssh-command">ssh-command</A> |
| 8174 |
<LI> <A HREF="#ssh-open-timeout">ssh-open-timeout</A> |
| 8175 |
<LI> <A HREF="#ssh-path">ssh-path</A> |
| 8176 |
<LI> <A HREF="#tcp-open-timeout">tcp-open-timeout</A> |
| 8177 |
<LI> <A HREF="#tcp-query-timeout">tcp-query-timeout</A> |
| 8178 |
<LI> <A HREF="#tcp-read-warning-timeout">tcp-read-warning-timeout</A> |
| 8179 |
<LI> <A HREF="#tcp-write-warning-timeout">tcp-write-warning-timeout</A> |
| 8180 |
<LI> <A HREF="#use-function-keys">use-function-keys</A> |
| 8181 |
</UL> |
| 8182 |
<P> |
| 8183 |
|
| 8184 |
System managers are usually interested in setting these in the system-wide |
| 8185 |
configuration files, though users may set them if they wish. |
| 8186 |
|
| 8187 |
<UL> |
| 8188 |
<LI> <A HREF="#operating-dir">operating-dir</A> |
| 8189 |
<LI> <A HREF="#user-input">user-input-timeout</A> |
| 8190 |
</UL> |
| 8191 |
<P> |
| 8192 |
|
| 8193 |
<H3>Hidden Features Which are Settable by Users</H3> |
| 8194 |
|
| 8195 |
These are <EM>features</EM> (as opposed to variables) which users or system |
| 8196 |
administrators may set. Some of them only make sense for administrators. |
| 8197 |
To turn these on manually, the configuration file should be edited and the |
| 8198 |
feature added to the <EM>feature-list</EM> variable. |
| 8199 |
You may set the feature <A HREF="#expose-hidden-config">expose-hidden-config</A> |
| 8200 |
to cause these hidden features to show up in the Setup/Config screen. |
| 8201 |
They will be at the bottom of the screen. |
| 8202 |
|
| 8203 |
<UL> |
| 8204 |
<LI> <A HREF="#disable-config-cmd">disable-config-cmd</A> |
| 8205 |
<LI> <A HREF="#disable-kblock">disable-keyboard-lock-cmd</A> |
| 8206 |
<LI> <A HREF="#disable-password-cmd">disable-password-cmd</A> |
| 8207 |
<LI> <A HREF="#disable-pipes-in-sigs">disable-pipes-in-sigs</A> |
| 8208 |
<LI> <A HREF="#disable-pipes-in-templates">disable-pipes-in-templates</A> |
| 8209 |
<LI> <A HREF="#disable-roles-setup-cmd">disable-roles-setup-cmd</A> |
| 8210 |
<LI> <A HREF="#disable-roles-sig-edit">disable-roles-sig-edit</A> |
| 8211 |
<LI> <A HREF="#disable-roles-template-edit">disable-roles-template-edit</A> |
| 8212 |
<LI> <A HREF="#disable-setlocale-collate">disable-setlocale-collate</A> |
| 8213 |
<LI> <A HREF="#disable-shared-namespaces">disable-shared-namespaces</A> |
| 8214 |
<LI> <A HREF="#disable-signature-edit-cmd">disable-signature-edit-cmd</A> |
| 8215 |
</UL> |
| 8216 |
<P> |
| 8217 |
|
| 8218 |
<H2><A NAME="ret-var">Retired Variables and Features</A></H2> |
| 8219 |
|
| 8220 |
Variables and features that are no longer used by the current <EM>Alpine</EM> version. |
| 8221 |
When an obsolete variable is encountered, its value is applied to any new |
| 8222 |
corresponding setting. |
| 8223 |
The replaced values include: |
| 8224 |
<P> |
| 8225 |
|
| 8226 |
<DL COMPACT> |
| 8227 |
|
| 8228 |
<DT> <EM>character-set</EM> |
| 8229 |
|
| 8230 |
<DD> Replaced by three separate variables: |
| 8231 |
<EM>display-character-set</EM>, |
| 8232 |
<EM>keyboard-character-set</EM>, and |
| 8233 |
<EM>posting-character-set</EM>. |
| 8234 |
|
| 8235 |
<DT> <EM>compose-mime</EM> |
| 8236 |
|
| 8237 |
<DT> <EM>elm-style-save</EM> |
| 8238 |
|
| 8239 |
<DD> Replaced by <EM>saved-msg-name-rule</EM> |
| 8240 |
|
| 8241 |
<DT> <EM>feature-level</EM> |
| 8242 |
|
| 8243 |
<DD> Replaced by <EM>feature-list.</EM> |
| 8244 |
|
| 8245 |
<DT> <EM>header-in-reply</EM> |
| 8246 |
|
| 8247 |
<DD> Replaced by <EM>include-header-in-reply</EM> in the |
| 8248 |
<EM>feature-list.</EM> |
| 8249 |
|
| 8250 |
<DT> <EM>old-style-reply</EM> |
| 8251 |
|
| 8252 |
<DD> Replaced by <EM>signature-at-bottom</EM> in the |
| 8253 |
<EM>feature-list.</EM> |
| 8254 |
|
| 8255 |
<DT> <EM>use-old-unix-format-write</EM> |
| 8256 |
|
| 8257 |
<DD> No replacement. |
| 8258 |
|
| 8259 |
<DT> <EM>patterns</EM> |
| 8260 |
|
| 8261 |
<DD> Replaced by four separate patterns variables: |
| 8262 |
<EM>patterns-roles</EM>, |
| 8263 |
<EM>patterns-filters</EM>, |
| 8264 |
<EM>patterns-scores</EM>, and |
| 8265 |
<EM>patterns-indexcolors</EM>. |
| 8266 |
Since then, <EM>patterns-filters</EM> has also become obsolete and is replaced |
| 8267 |
by <EM>patterns-filters2</EM>; <EM>patterns-scores</EM> is replaced by |
| 8268 |
<EM>patterns-scores2</EM>. |
| 8269 |
|
| 8270 |
<DT> <EM>save-by-sender</EM> |
| 8271 |
|
| 8272 |
<DD> Replaced by <EM>saved-msg-name-rule.</EM> |
| 8273 |
|
| 8274 |
<DT> <EM>show-all-characters</EM> |
| 8275 |
|
| 8276 |
<DD> No replacement, it always works this way now. |
| 8277 |
|
| 8278 |
</DL> |
| 8279 |
|
| 8280 |
<P> |
| 8281 |
|
| 8282 |
<H2><A NAME="index-tokens"></A>Tokens for Index and Replying</H2> |
| 8283 |
|
| 8284 |
This set of special tokens may be used in the |
| 8285 |
<A HREF="#index-format"><EM>index-format</EM></A> option, |
| 8286 |
in the <A HREF="#reply-leadin"><EM>reply-leadin</EM></A> option, |
| 8287 |
in signature files, |
| 8288 |
in template files used in |
| 8289 |
<A HREF="#role-config"><EM>roles</EM></A>, |
| 8290 |
and in the folder name that is the target of a Filter Rule. |
| 8291 |
Some of them aren't available in all situations. |
| 8292 |
<P> |
| 8293 |
The tokens are used as they appear below for the <EM>Index-Format</EM> |
| 8294 |
option, but they must be surrounded by underscores for the |
| 8295 |
<EM>Reply-Leadin</EM> option, in signature and template files, |
| 8296 |
and in the target of Filter Rules. |
| 8297 |
<P> |
| 8298 |
|
| 8299 |
<H3><EM>Tokens Available for all Cases (except Filter Rules)</EM></H3> |
| 8300 |
|
| 8301 |
<DL> |
| 8302 |
<DT>SUBJECT</DT> |
| 8303 |
<DD> |
| 8304 |
This token represents the Subject the sender gave the message. |
| 8305 |
Alternatives for use in the index screen are |
| 8306 |
SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT. |
| 8307 |
You may color the subject text in the MESSAGE INDEX screen differently by using the |
| 8308 |
<A HREF="#index-subject-color">Index Subject Color</A> |
| 8309 |
and the |
| 8310 |
<A HREF="#index-opening-color">Index Opening Color</A>. |
| 8311 |
options available from |
| 8312 |
the Setup Kolor screen. |
| 8313 |
</DD> |
| 8314 |
|
| 8315 |
<DT>FROM</DT> |
| 8316 |
<DD> |
| 8317 |
This token represents the personal name (or email address if the name |
| 8318 |
is unavailable) of the person specified in the message's "From:" |
| 8319 |
header field. |
| 8320 |
You may color the from text in the MESSAGE INDEX screen differently by using the |
| 8321 |
<A HREF="#index-from-color">Index From Color</A> |
| 8322 |
option available from the Setup Kolor screen. |
| 8323 |
</DD> |
| 8324 |
|
| 8325 |
<DT>ADDRESS</DT> |
| 8326 |
<DD> |
| 8327 |
This is similar to the "FROM" token, only it is always the |
| 8328 |
email address, never the personal name. |
| 8329 |
For example, "mailbox@domain". |
| 8330 |
</DD> |
| 8331 |
|
| 8332 |
<DT>MAILBOX</DT> |
| 8333 |
<DD> |
| 8334 |
This is the same as the "ADDRESS" except that the |
| 8335 |
domain part of the address is left off. |
| 8336 |
For example, "mailbox". |
| 8337 |
</DD> |
| 8338 |
|
| 8339 |
<DT>SENDER</DT> |
| 8340 |
<DD> |
| 8341 |
This token represents the personal name (or email address) of the person |
| 8342 |
listed in the message's "Sender:" header field. |
| 8343 |
</DD> |
| 8344 |
|
| 8345 |
<DT>TO</DT> |
| 8346 |
<DD> |
| 8347 |
This token represents the personal names (or email addresses if the names |
| 8348 |
are unavailable) of the persons specified in the |
| 8349 |
message's "To:" header field. |
| 8350 |
</DD> |
| 8351 |
|
| 8352 |
<DT>NEWSANDTO</DT> |
| 8353 |
<DD> |
| 8354 |
This token represents the newsgroups from the |
| 8355 |
message's "Newsgroups:" header field <EM>and</EM> |
| 8356 |
the personal names (or email addresses if the names |
| 8357 |
are unavailable) of the persons specified in the |
| 8358 |
message's "To:" header field. |
| 8359 |
</DD> |
| 8360 |
|
| 8361 |
<DT>TOANDNEWS</DT> |
| 8362 |
<DD> |
| 8363 |
Same as "NEWSANDTO" except in the opposite order. |
| 8364 |
</DD> |
| 8365 |
|
| 8366 |
<DT>NEWS</DT> |
| 8367 |
<DD> |
| 8368 |
This token represents the newsgroups from the |
| 8369 |
message's "Newsgroups:" header field. |
| 8370 |
</DD> |
| 8371 |
|
| 8372 |
<DT>CC</DT> |
| 8373 |
<DD> |
| 8374 |
This token represents the personal names (or email addresses if the names |
| 8375 |
are unavailable) of the persons specified in the |
| 8376 |
message's "Cc:" header field. |
| 8377 |
</DD> |
| 8378 |
|
| 8379 |
<DT>RECIPS</DT> |
| 8380 |
<DD> |
| 8381 |
This token represents the personal names (or email addresses if the names |
| 8382 |
are unavailable) of the persons specified in both the |
| 8383 |
message's "To:" header field and |
| 8384 |
the message's "Cc:" header field. |
| 8385 |
</DD> |
| 8386 |
|
| 8387 |
<DT>NEWSANDRECIPS</DT> |
| 8388 |
<DD> |
| 8389 |
This token represents the newsgroups from the |
| 8390 |
message's "Newsgroups:" header field <EM>and</EM> |
| 8391 |
the personal names (or email addresses if the names |
| 8392 |
are unavailable) of the persons specified in the |
| 8393 |
message's "To:" and "Cc:" header fields. |
| 8394 |
</DD> |
| 8395 |
|
| 8396 |
<DT>RECIPSANDNEWS</DT> |
| 8397 |
<DD> |
| 8398 |
Same as "NEWSANDRECIPS" except in the opposite order. |
| 8399 |
</DD> |
| 8400 |
|
| 8401 |
<DT>INIT</DT> |
| 8402 |
<DD> |
| 8403 |
This token represents the initials from the personal name |
| 8404 |
of the person specified in the message's "From:" |
| 8405 |
header field. |
| 8406 |
If there is no personal name, it is blank. |
| 8407 |
</DD> |
| 8408 |
|
| 8409 |
<DT>DATE</DT> |
| 8410 |
<DD> |
| 8411 |
This token represents the date on which the message was sent, according |
| 8412 |
to the "Date" header field. |
| 8413 |
It has the format MMM DD. For example, "Oct 23". |
| 8414 |
The feature |
| 8415 |
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A>, |
| 8416 |
which adjusts for the timezone the message was sent from, |
| 8417 |
may have an affect on the value of this token as well as the values of |
| 8418 |
all of the other DATE or TIME tokens. |
| 8419 |
Some of the DATE and TIME tokens are displayed in a locale-specific |
| 8420 |
way unless the option |
| 8421 |
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is set. |
| 8422 |
</DD> |
| 8423 |
|
| 8424 |
<DT>SMARTDATE</DT> |
| 8425 |
<DD> |
| 8426 |
This token represents the date on which the message was sent, according |
| 8427 |
to the "Date" header field. |
| 8428 |
It is "Today" if the message was sent today, |
| 8429 |
"Yesterday" for yesterday, |
| 8430 |
"Wednesday" if it was last Wednesday, and so on. If the |
| 8431 |
message is from last year and is more than six months old it includes the year, as well. |
| 8432 |
There is no adjustment made for different time zones, so you'll get |
| 8433 |
the day the message was sent according to the time zone the sender |
| 8434 |
was in. |
| 8435 |
See the SMARTDATE alternatives below, as well. |
| 8436 |
</DD> |
| 8437 |
|
| 8438 |
<DT>SMARTTIME</DT> |
| 8439 |
<DD> |
| 8440 |
This token represents the most relevant elements of the date on which |
| 8441 |
the message was sent (according to the "Date" header field), |
| 8442 |
in a compact form. If the message was sent today, only the time is used |
| 8443 |
(e.g. "9:22am", "10:07pm"); if it was sent during |
| 8444 |
the past week, the day of the week and the hour are used |
| 8445 |
(e.g. "Wed09am", "Thu10pm"); other dates are |
| 8446 |
given as date, month, and year (e.g. "23Aug00", |
| 8447 |
"9Apr98"). |
| 8448 |
There is no adjustment made for different time zones, so you'll get |
| 8449 |
the day/time the message was sent according to the time zone the sender |
| 8450 |
was in. |
| 8451 |
</DD> |
| 8452 |
|
| 8453 |
<DT>SMARTDATETIME</DT> |
| 8454 |
<DD> |
| 8455 |
This is a combination of SMARTDATE and SMARTTIME. |
| 8456 |
It is SMARTDATE unless the SMARTDATE value is "Today", in which |
| 8457 |
case it is SMARTTIME. |
| 8458 |
See the SMARTDATETIME alternatives below, as well. |
| 8459 |
</DD> |
| 8460 |
|
| 8461 |
<DT>DATEISO</DT> |
| 8462 |
<DD> |
| 8463 |
This token represents the date on which the message was sent, according |
| 8464 |
to the "Date" header field. |
| 8465 |
It has the format YYYY-MM-DD. For example, "1998-10-23". |
| 8466 |
</DD> |
| 8467 |
|
| 8468 |
<DT>SHORTDATEISO</DT> |
| 8469 |
<DD> |
| 8470 |
This token represents the date on which the message was sent, according |
| 8471 |
to the "Date" header field. |
| 8472 |
It has the format YY-MM-DD. For example, "98-10-23". |
| 8473 |
</DD> |
| 8474 |
|
| 8475 |
<DT>SHORTDATE1</DT> |
| 8476 |
<DD> |
| 8477 |
This token represents the date on which the message was sent, according |
| 8478 |
to the "Date" header field. |
| 8479 |
It has the format MM/DD/YY. For example, "10/23/98". |
| 8480 |
</DD> |
| 8481 |
|
| 8482 |
<DT>SHORTDATE2</DT> |
| 8483 |
<DD> |
| 8484 |
This token represents the date on which the message was sent, according |
| 8485 |
to the "Date" header field. |
| 8486 |
It has the format DD/MM/YY. For example, "23/10/98". |
| 8487 |
</DD> |
| 8488 |
|
| 8489 |
<DT>SHORTDATE3</DT> |
| 8490 |
<DD> |
| 8491 |
This token represents the date on which the message was sent, according |
| 8492 |
to the "Date" header field. |
| 8493 |
It has the format DD.MM.YY. For example, "23.10.98". |
| 8494 |
</DD> |
| 8495 |
|
| 8496 |
<DT>SHORTDATE4</DT> |
| 8497 |
<DD> |
| 8498 |
This token represents the date on which the message was sent, according |
| 8499 |
to the "Date" header field. |
| 8500 |
It has the format YY.MM.DD. For example, "98.10.23". |
| 8501 |
</DD> |
| 8502 |
|
| 8503 |
<DT>LONGDATE</DT> |
| 8504 |
<DD> |
| 8505 |
This token represents the date on which the message was sent, according |
| 8506 |
to the "Date" header field. |
| 8507 |
It has the format MMM DD, YYYY. For example, "Oct 23, 1998". |
| 8508 |
</DD> |
| 8509 |
|
| 8510 |
<DT>SMARTDATE alternatives</DT> |
| 8511 |
<DD> |
| 8512 |
There are several versions of SMARTDATE which are all the same except |
| 8513 |
for the way they format dates far in the past. |
| 8514 |
SMARTDATE formats the date using the information from your locale settings |
| 8515 |
to format the date string. It may end up formatting dates so that they look |
| 8516 |
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely. |
| 8517 |
The feature |
| 8518 |
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A> |
| 8519 |
may have an affect on the values of these tokens. |
| 8520 |
If you want more control you may use one of the following. |
| 8521 |
<DL> |
| 8522 |
<DT>SMARTDATE</DT> <DD>If the option |
| 8523 |
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set |
| 8524 |
then this will be locale specific. Control this with the |
| 8525 |
LC_TIME locale setting on a UNIX system. On Windows |
| 8526 |
the Regional Options control panel may be used to set the Short date |
| 8527 |
format. At the programming level, the strftime routine is what <EM>Alpine</EM> |
| 8528 |
uses to print the date. |
| 8529 |
If the Disable-Index-Locale-Dates option is set then this is equivalent |
| 8530 |
to SMARTDATES1.</DD> |
| 8531 |
<DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD> |
| 8532 |
<DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD> |
| 8533 |
<DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD> |
| 8534 |
<DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD> |
| 8535 |
<DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD> |
| 8536 |
<DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD> |
| 8537 |
</DL> |
| 8538 |
</DD> |
| 8539 |
|
| 8540 |
<DT>SMARTDATETIME alternatives</DT> |
| 8541 |
<DD> |
| 8542 |
There are several versions of SMARTDATETIME which are all very similar. |
| 8543 |
The ones which end in 24 use a 24-hour clock for Today's messages instead |
| 8544 |
of a 12-hour clock. |
| 8545 |
The other variation is |
| 8546 |
for the way they format dates far in the past. |
| 8547 |
SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings |
| 8548 |
to format the date string. It may end up formatting dates so that they look |
| 8549 |
like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely. |
| 8550 |
The feature |
| 8551 |
<A HREF="#convert-dates-to-localtime"><EM>convert-dates-to-localtime</EM></A> |
| 8552 |
may have an affect on the values of these tokens. |
| 8553 |
The possible choices are: |
| 8554 |
<DL> |
| 8555 |
<DT>SMARTDATETIME</DT> <DD>Locale specific. Control this with the |
| 8556 |
LC_TIME locale setting on a UNIX system. On Windows |
| 8557 |
the Regional Options control panel may be used to set the Short date |
| 8558 |
format. At the programming level, the strftime routine is what <EM>Alpine</EM> |
| 8559 |
uses to print the date.</DD> |
| 8560 |
<DT>SMARTDATETIME</DT> <DD>If the option |
| 8561 |
<A HREF="#disable-index-locale-dates"><EM>Disable-Index-Locale-Dates</EM></A> is not set |
| 8562 |
then this will be locale specific. Control this with the |
| 8563 |
LC_TIME locale setting on a UNIX system. On Windows |
| 8564 |
the Regional Options control panel may be used to set the Short date |
| 8565 |
format. At the programming level, the strftime routine is what <EM>Alpine</EM> |
| 8566 |
uses to print the date. |
| 8567 |
If the Disable-Index-Locale-Dates option is set then this is equivalent |
| 8568 |
to SMARTDATETIMES1.</DD> |
| 8569 |
<DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD> |
| 8570 |
<DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD> |
| 8571 |
<DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD> |
| 8572 |
<DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD> |
| 8573 |
<DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD> |
| 8574 |
<DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD> |
| 8575 |
<DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD> |
| 8576 |
<DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD> |
| 8577 |
<DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD> |
| 8578 |
<DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD> |
| 8579 |
<DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD> |
| 8580 |
<DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD> |
| 8581 |
<DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD> |
| 8582 |
</DL> |
| 8583 |
</DD> |
| 8584 |
|
| 8585 |
<DT>DAYDATE</DT> |
| 8586 |
<DD> |
| 8587 |
This token represents the date on which the message was sent, according |
| 8588 |
to the "Date" header field. |
| 8589 |
It looks like "Sat, 23 Oct 1998". |
| 8590 |
This token is never converted in any locale-specific way. |
| 8591 |
</DD> |
| 8592 |
|
| 8593 |
<DT>PREFDATE</DT> |
| 8594 |
<DD> |
| 8595 |
This token represents the date on which the message was sent, according |
| 8596 |
to the "Date" header field. |
| 8597 |
It is your operating system's idea of the preferred date representation for the current locale. |
| 8598 |
Internally it uses the %x version of the date from the strftime routine. |
| 8599 |
</DD> |
| 8600 |
|
| 8601 |
<DT>PREFTIME</DT> |
| 8602 |
<DD> |
| 8603 |
This token represents the time at which the message was sent, according |
| 8604 |
to the "Date" header field. |
| 8605 |
It is the preferred time representation for the current locale. |
| 8606 |
Internally it uses the %X version of the time from the strftime routine. |
| 8607 |
</DD> |
| 8608 |
|
| 8609 |
<DT>PREFDATETIME</DT> |
| 8610 |
<DD> |
| 8611 |
This token represents the date and time at which the message was sent, according |
| 8612 |
to the "Date" header field. |
| 8613 |
It is the preferred date and time representation for the current locale. |
| 8614 |
Internally it uses the %c version of the time from the strftime routine. |
| 8615 |
</DD> |
| 8616 |
|
| 8617 |
<DT>DAY</DT> |
| 8618 |
<DD> |
| 8619 |
This token represents the day of the month on which the message was sent, |
| 8620 |
according to the "Date" header field. |
| 8621 |
For example, "23" or "9". |
| 8622 |
</DD> |
| 8623 |
|
| 8624 |
<DT>DAY2DIGIT</DT> |
| 8625 |
<DD> |
| 8626 |
This token represents the day of the month on which the message was sent, |
| 8627 |
according to the "Date" header field. |
| 8628 |
For example, "23" or "09". |
| 8629 |
It is always 2 digits. |
| 8630 |
</DD> |
| 8631 |
|
| 8632 |
<DT>DAYORDINAL</DT> |
| 8633 |
<DD> |
| 8634 |
This token represents the ordinal number which is the day of |
| 8635 |
the month on which the message was sent, |
| 8636 |
according to the "Date" header field. |
| 8637 |
For example, "23rd" or "9th". |
| 8638 |
</DD> |
| 8639 |
|
| 8640 |
<DT>DAYOFWEEK</DT> |
| 8641 |
<DD> |
| 8642 |
This token represents the day of the week on which the message was sent, |
| 8643 |
according to the "Date" header field. |
| 8644 |
For example, "Sunday" or "Wednesday". |
| 8645 |
</DD> |
| 8646 |
|
| 8647 |
<DT>DAYOFWEEKABBREV</DT> |
| 8648 |
<DD> |
| 8649 |
This token represents the day of the week on which the message was sent, |
| 8650 |
according to the "Date" header field. |
| 8651 |
For example, "Sun" or "Wed". |
| 8652 |
</DD> |
| 8653 |
|
| 8654 |
<DT>MONTHABBREV</DT> |
| 8655 |
<DD> |
| 8656 |
This token represents the month the message was sent, according |
| 8657 |
to the "Date" header field. |
| 8658 |
For example, "Oct". |
| 8659 |
</DD> |
| 8660 |
|
| 8661 |
<DT>MONTHLONG</DT> |
| 8662 |
<DD> |
| 8663 |
This token represents the month in which the message was sent, according |
| 8664 |
to the "Date" header field. |
| 8665 |
For example, "October". |
| 8666 |
</DD> |
| 8667 |
|
| 8668 |
<DT>MONTH</DT> |
| 8669 |
<DD> |
| 8670 |
This token represents the month in which the message was sent, according |
| 8671 |
to the "Date" header field. |
| 8672 |
For example, "10" or "9". |
| 8673 |
</DD> |
| 8674 |
|
| 8675 |
<DT>MONTH2DIGIT</DT> |
| 8676 |
<DD> |
| 8677 |
This token represents the month in which the message was sent, according |
| 8678 |
to the "Date" header field. |
| 8679 |
For example, "10" or "09". |
| 8680 |
It is always 2 digits. |
| 8681 |
</DD> |
| 8682 |
|
| 8683 |
<DT>YEAR</DT> |
| 8684 |
<DD> |
| 8685 |
This token represents the year the message was sent, according |
| 8686 |
to the "Date" header field. |
| 8687 |
For example, "1998" or "2001". |
| 8688 |
</DD> |
| 8689 |
|
| 8690 |
<DT>YEAR2DIGIT</DT> |
| 8691 |
<DD> |
| 8692 |
This token represents the year the message was sent, according |
| 8693 |
to the "Date" header field. |
| 8694 |
For example, "98" or "01". |
| 8695 |
It is always 2 digits. |
| 8696 |
</DD> |
| 8697 |
|
| 8698 |
<DT>TIME24</DT> |
| 8699 |
<DD> |
| 8700 |
This token represents the time at which the message was sent, according |
| 8701 |
to the "Date" header field. |
| 8702 |
There is no adjustment made for different time zones, so you'll get |
| 8703 |
the time the message was sent according to the time zone the sender |
| 8704 |
was in. |
| 8705 |
It has the format HH:MM. For example, "17:28". |
| 8706 |
</DD> |
| 8707 |
|
| 8708 |
<DT>TIME12</DT> |
| 8709 |
<DD> |
| 8710 |
This token represents the time at which the message was sent, according |
| 8711 |
to the "Date" header field. |
| 8712 |
This time is for a 12 hour clock. |
| 8713 |
It has the format HH:MMpm. |
| 8714 |
For example, "5:28pm" or "11:13am". |
| 8715 |
</DD> |
| 8716 |
|
| 8717 |
<DT>TIMEZONE</DT> |
| 8718 |
<DD> |
| 8719 |
This token represents the numeric timezone from |
| 8720 |
the "Date" header field. |
| 8721 |
It has the format [+-]HHMM. For example, "-0800". |
| 8722 |
</DD> |
| 8723 |
|
| 8724 |
</DL> |
| 8725 |
|
| 8726 |
<P> |
| 8727 |
<H3><EM>Tokens Available Only for Index-Format</EM></H3> |
| 8728 |
|
| 8729 |
<DL> |
| 8730 |
<DT>MSGNO</DT> |
| 8731 |
<DD> |
| 8732 |
This token represents the message's current position in the folder which, |
| 8733 |
of course, may change as the folder is sorted or new mail arrives. |
| 8734 |
</DD> |
| 8735 |
|
| 8736 |
<DT>STATUS</DT> |
| 8737 |
<DD> |
| 8738 |
This token represents a three character wide field displaying various |
| 8739 |
aspects of the message's state. |
| 8740 |
The first character is either blank, |
| 8741 |
a '*' for message marked Important, or a '+' indicating a message |
| 8742 |
addressed directly to you (as opposed to your having received it via a |
| 8743 |
mailing list, for example). |
| 8744 |
When the feature |
| 8745 |
<A HREF="#mark-for-cc"><EM>mark-for-cc</EM></A> |
| 8746 |
is set, if the first character would have been |
| 8747 |
blank then it will instead be a '-' if the message is cc'd to you. |
| 8748 |
The second character is typically blank, |
| 8749 |
though the arrow cursor may occupy it if either the |
| 8750 |
<A HREF="#assume-slow-link"><EM>assume-slow-link</EM></A> |
| 8751 |
or the |
| 8752 |
<A HREF="#force-arrow-cursor"><EM>force-arrow-cursor</EM></A> feature |
| 8753 |
is set (or you actually are on a slow link). |
| 8754 |
The third character is either D (Deleted), |
| 8755 |
A (Answered), |
| 8756 |
N (New), or blank. |
| 8757 |
<P> |
| 8758 |
If you are using a threaded view of the index and this message is at the |
| 8759 |
top of a collapsed portion of a thread, |
| 8760 |
then this token refers to all of the messages in the collapsed portion of |
| 8761 |
the thread instead of just the top message. |
| 8762 |
The first character will be a '*' if <EM>any</EM> of the messages in the thread |
| 8763 |
are marked Important, else a '+' if any of the messages are addressed |
| 8764 |
to you, else a '-' if any of the messages are cc'd to you. |
| 8765 |
The third character will be a 'D' if <EM>all</EM> of the messages |
| 8766 |
in the collapsed thread are marked deleted, |
| 8767 |
an 'A' if <EM>all</EM> of the messages |
| 8768 |
in the collapsed thread are marked answered, |
| 8769 |
it will be an 'N' if any of |
| 8770 |
the messages are undeleted and unseen, and it will be blank otherwise. |
| 8771 |
</DD> |
| 8772 |
|
| 8773 |
<DT>FULLSTATUS</DT> |
| 8774 |
<DD> |
| 8775 |
This token represents a less abbreviated alternative |
| 8776 |
to the "STATUS" token. |
| 8777 |
It is six characters wide. |
| 8778 |
The first character is '+', '-', or blank, the |
| 8779 |
second blank, the third either '*' or blank, the fourth |
| 8780 |
N or blank, |
| 8781 |
the fifth A |
| 8782 |
or blank, and the sixth character is |
| 8783 |
either D or |
| 8784 |
blank. |
| 8785 |
<P> |
| 8786 |
If you are using a threaded view of the index and this message is at the |
| 8787 |
top of a collapsed portion of a thread, |
| 8788 |
then this token refers to all of the messages in the collapsed portion of |
| 8789 |
the thread instead of just the top message. |
| 8790 |
The first character is '+', '-', or blank depending on whether <EM>any</EM> |
| 8791 |
of the messages in the collapsed thread are addressed to you or cc'd to you. |
| 8792 |
The third character will be '*' if any of the messages are marked |
| 8793 |
Important. |
| 8794 |
The fourth character will be 'N' if all of the messages in the thread |
| 8795 |
are New, else 'n' if some of the messages in the thread are New, else blank. |
| 8796 |
The fifth character will be 'A' or 'a' or blank, and the sixth character |
| 8797 |
will be 'D' or 'd' or blank. |
| 8798 |
</DD> |
| 8799 |
|
| 8800 |
<DT>IMAPSTATUS</DT> |
| 8801 |
<DD> |
| 8802 |
This token represents an even less abbreviated alternative to the |
| 8803 |
"STATUS" token. |
| 8804 |
It differs from "FULLSTATUS" in only the fourth character which is |
| 8805 |
an 'N' if the message is new to this folder since the last time |
| 8806 |
it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message |
| 8807 |
is new to the folder and has been viewed, a 'U' (Unseen) if the message is not |
| 8808 |
new to the folder since it was last opened <EM>but</EM> has not been |
| 8809 |
viewed, or a blank if the message has been in the folder since it was |
| 8810 |
last opened and has been viewed. |
| 8811 |
<P> |
| 8812 |
If you are using a threaded view of the index and this message is at the |
| 8813 |
top of a collapsed portion of a thread, |
| 8814 |
then the fourth character will be |
| 8815 |
'N' if all of the messages in the thread are unseen and recent; |
| 8816 |
else 'n' if some of the messages in the thread are unseen and recent; |
| 8817 |
else 'U' if all of the messages in the thread are unseen and not recent; |
| 8818 |
else 'u' if some of the messages in the thread are unseen and not recent; |
| 8819 |
else 'R' if all of the messages in the thread are seen and recent; |
| 8820 |
else 'r' if some of the messages in the thread are seen and recent; |
| 8821 |
else blank. |
| 8822 |
</DD> |
| 8823 |
|
| 8824 |
<DT>SHORTIMAPSTATUS</DT> |
| 8825 |
<DD> |
| 8826 |
This is the same as the last four of the six characters of IMAPSTATUS, |
| 8827 |
so the '+' To Me information will be missing. |
| 8828 |
</DD> |
| 8829 |
|
| 8830 |
<DT>SIZE</DT> |
| 8831 |
<DD> |
| 8832 |
This token represents the total size, in bytes, of the message. |
| 8833 |
If a "K" (Kilobyte) |
| 8834 |
follows the number, the size is approximately 1,000 |
| 8835 |
times that many bytes (rounded to the nearest 1,000). |
| 8836 |
If an "M" (Megabyte) follows the number, the size is approximately |
| 8837 |
1,000,000 times that many bytes. |
| 8838 |
Commas are not used in this field. |
| 8839 |
This field is seven characters wide, including the enclosing parentheses. |
| 8840 |
Sizes are rounded when "K" or "M" is present. |
| 8841 |
The progression of sizes used looks like: |
| 8842 |
|
| 8843 |
<P> |
| 8844 |
<CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER> |
| 8845 |
<P> |
| 8846 |
</DD> |
| 8847 |
|
| 8848 |
<DT>SIZECOMMA</DT> |
| 8849 |
<DD> |
| 8850 |
This token represents the total size, in bytes, of the message. |
| 8851 |
If a "K" (Kilobyte) |
| 8852 |
follows the number, the size is approximately 1,000 |
| 8853 |
times that many bytes (rounded to the nearest 1,000). |
| 8854 |
If an "M" (Megabyte) follows the number, the size is approximately |
| 8855 |
1,000,000 times that many bytes. |
| 8856 |
Commas are used if the number shown is 1,000 or greater. |
| 8857 |
The SIZECOMMA field is one character wider than the SIZE field. |
| 8858 |
Sizes are rounded when "K" or "M" is present. |
| 8859 |
The progression of sizes used looks like: |
| 8860 |
|
| 8861 |
<P> |
| 8862 |
<CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER> |
| 8863 |
<P> |
| 8864 |
</DD> |
| 8865 |
|
| 8866 |
<DT>KSIZE</DT> |
| 8867 |
<DD> |
| 8868 |
This token represents the total size of the message, expressed in |
| 8869 |
kilobytes or megabytes, as most appropriate. |
| 8870 |
These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes. |
| 8871 |
The progression of sizes used looks like: |
| 8872 |
|
| 8873 |
<P> |
| 8874 |
<CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER> |
| 8875 |
<P> |
| 8876 |
</DD> |
| 8877 |
|
| 8878 |
<DT>SIZENARROW</DT> |
| 8879 |
<DD> |
| 8880 |
This token represents the total size, in bytes, of the message. |
| 8881 |
If a "K" (Kilobyte) |
| 8882 |
follows the number, the size is approximately 1,000 |
| 8883 |
times that many bytes. |
| 8884 |
If an "M" (Megabyte) follows the number, the size is approximately |
| 8885 |
1,000,000 times that many bytes. |
| 8886 |
If a "G" (Gigabyte) follows the number, the size is approximately |
| 8887 |
1,000,000,000 times that many bytes. |
| 8888 |
This field uses only five characters of screen width, including the enclosing |
| 8889 |
parentheses. |
| 8890 |
The progression of sizes used looks like: |
| 8891 |
|
| 8892 |
<P> |
| 8893 |
<CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER> |
| 8894 |
<P> |
| 8895 |
</DD> |
| 8896 |
|
| 8897 |
<DT>DESCRIPSIZE</DT> |
| 8898 |
<DD> |
| 8899 |
This token is intended to represent a more useful description of the |
| 8900 |
message than just its size, but it isn't very useful at this point. |
| 8901 |
The plus sign in this view means there are attachments. |
| 8902 |
Note that including this token in |
| 8903 |
the "Index-Format" could slow down the |
| 8904 |
display a little while <EM>Alpine</EM> collects the necessary information. |
| 8905 |
</DD> |
| 8906 |
|
| 8907 |
<DT>SUBJKEY</DT> |
| 8908 |
<DD> |
| 8909 |
This token is the same as the SUBJECT token unless keywords are set for |
| 8910 |
the message. |
| 8911 |
In that case, a list of keywords enclosed in braces will be prepended to |
| 8912 |
the subject of the message. |
| 8913 |
Only those keywords that you have defined in your |
| 8914 |
<A HREF="#keywords">Keywords</A> option |
| 8915 |
in Setup/Config are considered in the list. |
| 8916 |
In other words, keywords that have been set by some other means, perhaps |
| 8917 |
by another email program, won't show up unless included in |
| 8918 |
<A HREF="#keywords">Keywords</A>. |
| 8919 |
Having this set in the Index-Format will also cause the keywords to be |
| 8920 |
prepended to the subject in the MESSAGE TEXT screen. |
| 8921 |
If you have given a keyword a nickname |
| 8922 |
(<A HREF="#keywords"><EM>keywords</EM></A>), that nickname is displayed |
| 8923 |
instead of the actual keyword. |
| 8924 |
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A> |
| 8925 |
option may be used to modify this token slightly. |
| 8926 |
It is also possible to color keywords in the index using the |
| 8927 |
Setup/Kolor screen. |
| 8928 |
</DD> |
| 8929 |
|
| 8930 |
<DT>SUBJKEYINIT</DT> |
| 8931 |
<DD> |
| 8932 |
This token is the same as the SUBJKEY token except that instead of |
| 8933 |
prepending a list of keywords to the subject, a list of first initials |
| 8934 |
of keywords will be prepended instead. |
| 8935 |
For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM> |
| 8936 |
set (or Work and Now are the <EM>Alpine</EM> nicknames of keywords which are set) |
| 8937 |
then the SUBJKEY token would cause a result like |
| 8938 |
<P> |
| 8939 |
<CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER> |
| 8940 |
<P> |
| 8941 |
whereas the SUBJKEYINIT token would give |
| 8942 |
<P> |
| 8943 |
<CENTER><SAMP>{WN} actual subject</SAMP></CENTER> |
| 8944 |
<P> |
| 8945 |
Only those keywords that you have defined in your |
| 8946 |
<A HREF="#keywords">Keywords</A> option |
| 8947 |
in Setup/Config are considered in the list. |
| 8948 |
In other words, keywords that have been set by some other means, perhaps |
| 8949 |
by another email program, won't show up unless included in |
| 8950 |
<A HREF="#keywords">Keywords</A>. |
| 8951 |
The <A HREF="#keyword-surrounding-chars"><EM>keyword-surrounding-chars</EM></A> |
| 8952 |
option may be used to modify this token slightly. |
| 8953 |
It is also possible to color keywords in the index using the |
| 8954 |
Setup/Kolor screen. |
| 8955 |
</DD> |
| 8956 |
|
| 8957 |
<DT>SUBJECTTEXT</DT> |
| 8958 |
<DD> |
| 8959 |
Same as SUBJECT but if there is room in the Subject field for more text, |
| 8960 |
the opening part of the text of the message is displayed after the subject. |
| 8961 |
The time needed to fetch the text may cause a performance problem |
| 8962 |
which can, of course, be avoided by using the SUBJECT version of |
| 8963 |
the Subject instead. |
| 8964 |
You may color this opening text differently by using the |
| 8965 |
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from |
| 8966 |
the Setup Kolor screen. |
| 8967 |
You may adjust the characters that are displayed between the Subject and the |
| 8968 |
opening text with the option |
| 8969 |
<A HREF="#opening-text-separator-chars"><EM>Opening-Text-Separator-Chars</EM></A>. |
| 8970 |
</DD> |
| 8971 |
|
| 8972 |
<DT>SUBJKEYTEXT</DT> |
| 8973 |
<DD> |
| 8974 |
Same as SUBJKEY but with the opening message text. |
| 8975 |
</DD> |
| 8976 |
|
| 8977 |
<DT>SUBJKEYINITTEXT</DT> |
| 8978 |
<DD> |
| 8979 |
Same as SUBJKEYINIT but with the opening message text. |
| 8980 |
</DD> |
| 8981 |
|
| 8982 |
<DT>OPENINGTEXT</DT> |
| 8983 |
<DD> |
| 8984 |
This is similar to SUBJECTTEXT. |
| 8985 |
Instead of combining the Subject and the opening text in a single |
| 8986 |
field in the index screen this token allows you to allocate a |
| 8987 |
separate column just for the opening text of the message. |
| 8988 |
The time needed to fetch this text may cause a performance problem. |
| 8989 |
You may color this opening text differently by using the |
| 8990 |
<A HREF="#index-opening-color"><EM>Index Opening Color</EM></A> option available from |
| 8991 |
the Setup Kolor screen. |
| 8992 |
</DD> |
| 8993 |
|
| 8994 |
<DT>OPENINGTEXTNQ</DT> |
| 8995 |
<DD> |
| 8996 |
This is very similar to OPENINGTEXT. |
| 8997 |
The NQ stands for No Quotes. |
| 8998 |
The only difference is that quoted text (lines beginning with >) is deleted. |
| 8999 |
For some messages this may be confusing. |
| 9000 |
For example, a message might have a line preceding some quoted |
| 9001 |
text that reads something like "On May 8th person A said." |
| 9002 |
That no longer makes sense after the quoted text is deleted and it |
| 9003 |
will appear that person A said whatever the text after the quote |
| 9004 |
is, even though that is really person B talking. |
| 9005 |
</DD> |
| 9006 |
|
| 9007 |
<DT>KEY</DT> |
| 9008 |
<DD> |
| 9009 |
This is a space-delimited list of keywords that are set for the message. |
| 9010 |
Only those keywords that you have defined in your |
| 9011 |
<A HREF="#keywords">Keywords</A> option |
| 9012 |
in Setup/Config are considered in the list. |
| 9013 |
In other words, keywords that have been set by some other means, perhaps |
| 9014 |
by another email program, won't show up unless included in |
| 9015 |
<A HREF="#keywords">Keywords</A>. |
| 9016 |
If you have given a keyword a nickname |
| 9017 |
that nickname is displayed |
| 9018 |
instead of the actual keyword. |
| 9019 |
It is also possible to color keywords in the index using the |
| 9020 |
Setup/Kolor screen. |
| 9021 |
This token defaults to an arbitrary width of 5. |
| 9022 |
You should set it to whatever width suits you using something |
| 9023 |
like KEY(17) in the Index-Format. |
| 9024 |
</DD> |
| 9025 |
|
| 9026 |
<DT>KEYINIT</DT> |
| 9027 |
<DD> |
| 9028 |
This is a list of keyword initials that are set for the message. |
| 9029 |
If you have given a keyword a nickname |
| 9030 |
the initial of that nickname |
| 9031 |
is displayed instead of the initial of the actual keyword. |
| 9032 |
It is also possible to color keyword initials in the index using the |
| 9033 |
Setup/Kolor screen. |
| 9034 |
This token defaults to an arbitrary width of 2. |
| 9035 |
You should set it to whatever width suits you using something |
| 9036 |
like KEYINIT(3) in the Index-Format. |
| 9037 |
</DD> |
| 9038 |
|
| 9039 |
<DT>PRIORITY</DT> |
| 9040 |
<DD> |
| 9041 |
The X-Priority header is a non-standard header that is used in a |
| 9042 |
somewhat standard way by many mail programs. |
| 9043 |
<EM>Alpine</EM> expects the value of this header to be a digit with a value |
| 9044 |
from 1 to 5, with 1 being the highest priority and 5 the lowest priority. |
| 9045 |
Since this priority is something that the sender sets it is only an indication |
| 9046 |
of the priority that the sender attaches to the mail and it is therefore almost |
| 9047 |
totally unreliable for use as a filtering criterion. |
| 9048 |
This token will display the numeric value of the priority if it is between |
| 9049 |
1 and 5. |
| 9050 |
It will be suppressed (blank) if the value is 3, which is normal priority. |
| 9051 |
It is also possible to set the color of the PRIORITY field. |
| 9052 |
By default the token is colored the same |
| 9053 |
as the index line it is part of. |
| 9054 |
You may set it to be another color with the |
| 9055 |
<A HREF="#index-pri-color">Index Priority Colors</A> options available from |
| 9056 |
the Setup Kolor screen. |
| 9057 |
</DD> |
| 9058 |
|
| 9059 |
<DT>PRIORITYALPHA</DT> |
| 9060 |
<DD> |
| 9061 |
This is a more verbose interpretation of the X-Priority field. |
| 9062 |
Once again nothing is displayed unless the value of the field |
| 9063 |
is 1, 2, 4, or 5. |
| 9064 |
The values displayed for those values are: |
| 9065 |
<P> |
| 9066 |
<TABLE> |
| 9067 |
<TR> <TD>1</TD> <TD>Highest</TD> </TR> |
| 9068 |
<TR> <TD>2</TD> <TD>High</TD> </TR> |
| 9069 |
<TR> <TD>4</TD> <TD>Low</TD> </TR> |
| 9070 |
<TR> <TD>5</TD> <TD>Lowest</TD> </TR> |
| 9071 |
</TABLE> |
| 9072 |
<P> |
| 9073 |
You may color this token with the |
| 9074 |
<A HREF="#index-pri-color">Index Priority Colors</A> options. |
| 9075 |
</DD> |
| 9076 |
|
| 9077 |
<DT>PRIORITY!</DT> |
| 9078 |
<DD> |
| 9079 |
This is a one character, non-numeric version of the X-Priority field. |
| 9080 |
If the value of the X-Priority header is 1 or 2 an exclamation |
| 9081 |
point is displayed. |
| 9082 |
If the value is 4 or 5 a "v" (think down arrow) is displayed. |
| 9083 |
You may color this token with the |
| 9084 |
<A HREF="#index-pri-color">Index Priority Colors</A> options. |
| 9085 |
</DD> |
| 9086 |
|
| 9087 |
<DT>ATT</DT> |
| 9088 |
<DD> |
| 9089 |
This is a one column wide field which represents the number of attachments |
| 9090 |
a message has. It will be blank if there are no attachments, a single |
| 9091 |
digit for one to nine attachments, or an asterisk for more than nine. |
| 9092 |
Note that including this token in |
| 9093 |
the "Index-Format" could slow down the |
| 9094 |
display a little while <EM>Alpine</EM> collects the necessary information. |
| 9095 |
</DD> |
| 9096 |
|
| 9097 |
<DT>FROMORTO</DT> |
| 9098 |
<DD> |
| 9099 |
This token represents <EM>either</EM> the personal name (or email address) of |
| 9100 |
the person listed in the message's "From:" header |
| 9101 |
field, <EM>or</EM>, if that address is yours or one of your |
| 9102 |
<A HREF="#alt-addresses">alternate addresses</A>, |
| 9103 |
the first person specified in the |
| 9104 |
message's "To:" header field |
| 9105 |
with the prefix "To: " prepended. |
| 9106 |
If the from address is yours and there is also no "To" address, |
| 9107 |
<EM>Alpine</EM> will use the address on the "Cc" line. |
| 9108 |
If there is no address there, either, <EM>Alpine</EM> will look for a newsgroup name |
| 9109 |
from the "Newsgroups" header field and put |
| 9110 |
that after the "To: " prefix. |
| 9111 |
</DD> |
| 9112 |
|
| 9113 |
<DT>FROMORTONOTNEWS</DT> |
| 9114 |
<DD> |
| 9115 |
This is almost the same as <EM>FROMORTO</EM>. |
| 9116 |
The difference is that newsgroups aren't considered. |
| 9117 |
When a message is from you, doesn't have a To or Cc, and does have |
| 9118 |
a Newsgroups header; this token will be your name instead of the name |
| 9119 |
of the newsgroup (like it would be with FROMORTO). |
| 9120 |
</DD> |
| 9121 |
|
| 9122 |
<DT>TEXT</DT> |
| 9123 |
<DD> |
| 9124 |
This is a different sort of token. |
| 9125 |
It allows you to display a label within each index line. |
| 9126 |
It will be the same fixed text for each line. |
| 9127 |
It is different from all the other tokens in that there is no space column |
| 9128 |
displayed after this token. |
| 9129 |
Instead, it is butted up against the following field. |
| 9130 |
It also has a different syntax. |
| 9131 |
The text to display is given following a colon after the |
| 9132 |
word "TEXT". |
| 9133 |
For example, |
| 9134 |
<P> |
| 9135 |
<CENTER><SAMP>TEXT:abc=</SAMP></CENTER> |
| 9136 |
<P> |
| 9137 |
would insert the literal text "abc=" (without the quotes) |
| 9138 |
into the index display line. |
| 9139 |
You must quote the text if it includes space characters, like |
| 9140 |
<P> |
| 9141 |
<CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER> |
| 9142 |
<P> |
| 9143 |
</DD> |
| 9144 |
|
| 9145 |
<DT>HEADER</DT> |
| 9146 |
<DD> |
| 9147 |
This allows you to display the text from a particular header line in the |
| 9148 |
message. |
| 9149 |
The syntax for this token is substantially different from all the others |
| 9150 |
in order that you might be able to display a portion of the text following |
| 9151 |
a particular header. |
| 9152 |
The header name you are interested in is given following a colon |
| 9153 |
after the word "HEADER". |
| 9154 |
For example, |
| 9155 |
<P> |
| 9156 |
<CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER> |
| 9157 |
<P> |
| 9158 |
would display the text of the X-Spam header, if any. |
| 9159 |
Like for other index tokens a width field may (and probably should) |
| 9160 |
follow this. |
| 9161 |
<P> |
| 9162 |
<CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER> |
| 9163 |
<P> |
| 9164 |
displays the first ten characters of the X-Spam header. |
| 9165 |
Unlike other index tokens, the syntax for HEADER is more flexible. |
| 9166 |
An optional second argument comes after a comma inside the parentheses. |
| 9167 |
It specifies the "field" number. |
| 9168 |
By default, the field separator is a space character. |
| 9169 |
No extra space characters are allowed in the argument list. |
| 9170 |
<P> |
| 9171 |
<CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER> |
| 9172 |
<P> |
| 9173 |
would display the second field, left-justified, in a 10 character |
| 9174 |
wide field. |
| 9175 |
The second field would consist of all the text after the first space |
| 9176 |
up to the next space or the end of the header. |
| 9177 |
The default field number is zero, which stands for the entire line. |
| 9178 |
There is also an optional third argument which is a list of field |
| 9179 |
separators. It defaults to a space character. |
| 9180 |
The example |
| 9181 |
<P> |
| 9182 |
<CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER> |
| 9183 |
<P> |
| 9184 |
would cause the field separators to be any of colon, percent, |
| 9185 |
or space (there is a space character between the percent and the |
| 9186 |
right parenthesis). |
| 9187 |
The first field runs from the start of the header value up to the first |
| 9188 |
colon, percent, or space; the second goes from there to the next; and so on. |
| 9189 |
In order to use a comma character as a field separator you must escape |
| 9190 |
it by preceding it with a backslash (\). |
| 9191 |
The same is true of the backslash character itself. |
| 9192 |
There is one further optional argument. |
| 9193 |
It is an R or an L to specify right or left adjustment of the text |
| 9194 |
within the field. |
| 9195 |
The default is to left justify, however if you are displaying numbers |
| 9196 |
you might prefer to right justify. |
| 9197 |
<P> |
| 9198 |
Here's an example of a SpamAssassin header. |
| 9199 |
The exact look of the header will vary, but if your incoming mail |
| 9200 |
contains headers that look like the following |
| 9201 |
<P> |
| 9202 |
<CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER> |
| 9203 |
<P> |
| 9204 |
you might want to display the hits value. |
| 9205 |
The first field starts with the Y in Yes. |
| 9206 |
To get what you're interested in you might use "=" and |
| 9207 |
space as the field separators and display the third field, like |
| 9208 |
<P> |
| 9209 |
<CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER> |
| 9210 |
<P> |
| 9211 |
or maybe you would break at the dot instead |
| 9212 |
<P> |
| 9213 |
<CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER> |
| 9214 |
<P> |
| 9215 |
Another example we've seen has headers that look like |
| 9216 |
<P> |
| 9217 |
<CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER> |
| 9218 |
<P> |
| 9219 |
Because there are two equals and a comma before the 7% and a comma |
| 9220 |
after it, the token |
| 9221 |
<P> |
| 9222 |
<CENTER><SAMP>HEADER:X-Spam-Status(3,4,=\,,R)</SAMP></CENTER> |
| 9223 |
<P> |
| 9224 |
should display the probability (for example 7% or 83%) right justified |
| 9225 |
in a 3-wide field. |
| 9226 |
</DD> |
| 9227 |
|
| 9228 |
|
| 9229 |
<DT>ARROW</DT> |
| 9230 |
<DD> |
| 9231 |
This gives an alternative way to display the current message in the |
| 9232 |
MESSAGE INDEX screen. |
| 9233 |
Usually the current message is indicated by the line being shown in |
| 9234 |
reverse video. |
| 9235 |
Instead, if the ARROW token is included in your Index-Format, |
| 9236 |
the current line will include an "arrow" that |
| 9237 |
looks like |
| 9238 |
<P> |
| 9239 |
<CENTER><SAMP>-></SAMP></CENTER> |
| 9240 |
<P> |
| 9241 |
in the ARROW token's field. |
| 9242 |
For all of the non-current messages, the ARROW field will be filled |
| 9243 |
with blanks. |
| 9244 |
If you use the fixed-field width feature the length of the "arrow" |
| 9245 |
may be adjusted. |
| 9246 |
The arrow will be drawn as width-1 dashes followed by a greater than sign. |
| 9247 |
For example, if you use ARROW(3) you will get |
| 9248 |
<P> |
| 9249 |
<CENTER><SAMP>--></SAMP></CENTER> |
| 9250 |
<P> |
| 9251 |
and ARROW(1) will give you just |
| 9252 |
<P> |
| 9253 |
<CENTER><SAMP>></SAMP></CENTER> |
| 9254 |
<P> |
| 9255 |
It is also possible to set the color of the ARROW field. |
| 9256 |
By default (and for non-current messages) the arrow is colored the same |
| 9257 |
as the index line it is part of. |
| 9258 |
You may set it to be another color with the |
| 9259 |
<A HREF="#index-arrow-color">Index Arrow Color</A> option available from |
| 9260 |
the Setup Kolor screen. |
| 9261 |
</DD> |
| 9262 |
|
| 9263 |
<DT>SCORE</DT> |
| 9264 |
<DD> |
| 9265 |
This gives the |
| 9266 |
score |
| 9267 |
of each message. |
| 9268 |
This will be six columns wide to accommodate the widest possible score. |
| 9269 |
You will probably want to use the Index-Format fixed-field width feature |
| 9270 |
to limit the width of the field to the widest score that |
| 9271 |
you use (e.g. SCORE(3) if your scores are always between 0 and 999). |
| 9272 |
If you have not defined any score rules the scores will all be zero. |
| 9273 |
If any of your score rules contain AllText or BodyText patterns |
| 9274 |
then including SCORE in the Index-Format |
| 9275 |
may slow down the display of the MESSAGE INDEX screen. |
| 9276 |
</DD> |
| 9277 |
</DL> |
| 9278 |
|
| 9279 |
<P> |
| 9280 |
<H3><EM>Tokens Available for all but Index-Format</EM></H3> |
| 9281 |
|
| 9282 |
<DL> |
| 9283 |
<DT>CURNEWS</DT> |
| 9284 |
<DD> |
| 9285 |
This token represents the current newsgroup if there is one. |
| 9286 |
For example, "comp.mail.pine". |
| 9287 |
</DD> |
| 9288 |
|
| 9289 |
<DT>MSGID</DT> |
| 9290 |
<DD> |
| 9291 |
This token represents the message ID of the message. |
| 9292 |
This token does not work with Filter Rule folder names. |
| 9293 |
</DD> |
| 9294 |
|
| 9295 |
<DT>CURDATE</DT> |
| 9296 |
<DD> |
| 9297 |
This token represents the current date. |
| 9298 |
It has the format MMM DD. For example, "Oct 23". |
| 9299 |
</DD> |
| 9300 |
|
| 9301 |
<DT>CURDATEISO</DT> |
| 9302 |
<DD> |
| 9303 |
This token represents the current date. |
| 9304 |
It has the format YYYY-MM-DD. For example, "1998-10-23". |
| 9305 |
</DD> |
| 9306 |
|
| 9307 |
<DT>CURDATEISOS</DT> |
| 9308 |
<DD> |
| 9309 |
This token represents the current date. |
| 9310 |
It has the format YY-MM-DD. For example, "98-10-23". |
| 9311 |
</DD> |
| 9312 |
|
| 9313 |
<DT>CURPREFDATE</DT> |
| 9314 |
<DD> |
| 9315 |
This token represents the current date. |
| 9316 |
It is your operating system's idea of the preferred date representation for the current locale. |
| 9317 |
Internally it uses the %x version of the date from the strftime routine. |
| 9318 |
</DD> |
| 9319 |
|
| 9320 |
<DT>CURPREFTIME</DT> |
| 9321 |
<DD> |
| 9322 |
This token represents the current time. |
| 9323 |
It is the preferred time representation for the current locale. |
| 9324 |
Internally it uses the %X version of the time from the strftime routine. |
| 9325 |
</DD> |
| 9326 |
|
| 9327 |
<DT>CURPREFDATETIME</DT> |
| 9328 |
<DD> |
| 9329 |
This token represents the current date and time. |
| 9330 |
It is the preferred date and time representation for the current locale. |
| 9331 |
Internally it uses the %c version of the time from the strftime routine. |
| 9332 |
</DD> |
| 9333 |
|
| 9334 |
<DT>CURTIME24</DT> |
| 9335 |
<DD> |
| 9336 |
This token represents the current time. |
| 9337 |
It has the format HH:MM. For example, "17:28". |
| 9338 |
</DD> |
| 9339 |
|
| 9340 |
<DT>CURTIME12</DT> |
| 9341 |
<DD> |
| 9342 |
This token represents the current time. |
| 9343 |
This time is for a 12 hour clock. |
| 9344 |
It has the format HH:MMpm. |
| 9345 |
For example, "5:28pm" or "11:13am". |
| 9346 |
</DD> |
| 9347 |
|
| 9348 |
<DT>CURDAY</DT> |
| 9349 |
<DD> |
| 9350 |
This token represents the current day of the month. |
| 9351 |
For example, "23" or "9". |
| 9352 |
</DD> |
| 9353 |
|
| 9354 |
<DT>CURDAY2DIGIT</DT> |
| 9355 |
<DD> |
| 9356 |
This token represents the current day of the month. |
| 9357 |
For example, "23" or "09". |
| 9358 |
It is always 2 digits. |
| 9359 |
</DD> |
| 9360 |
|
| 9361 |
<DT>CURDAYOFWEEK</DT> |
| 9362 |
<DD> |
| 9363 |
This token represents the current day of the week. |
| 9364 |
For example, "Sunday" or "Wednesday". |
| 9365 |
</DD> |
| 9366 |
|
| 9367 |
<DT>CURDAYOFWEEKABBREV</DT> |
| 9368 |
<DD> |
| 9369 |
This token represents the current day of the week. |
| 9370 |
For example, "Sun" or "Wed". |
| 9371 |
</DD> |
| 9372 |
|
| 9373 |
<DT>CURMONTH</DT> |
| 9374 |
<DD> |
| 9375 |
This token represents the current month. |
| 9376 |
For example, "10" or "9". |
| 9377 |
</DD> |
| 9378 |
|
| 9379 |
<DT>CURMONTH2DIGIT</DT> |
| 9380 |
<DD> |
| 9381 |
This token represents the current month. |
| 9382 |
For example, "10" or "09". |
| 9383 |
It is always 2 digits. |
| 9384 |
</DD> |
| 9385 |
|
| 9386 |
<DT>CURMONTHLONG</DT> |
| 9387 |
<DD> |
| 9388 |
This token represents the current month. |
| 9389 |
For example, "October". |
| 9390 |
</DD> |
| 9391 |
|
| 9392 |
<DT>CURMONTHABBREV</DT> |
| 9393 |
<DD> |
| 9394 |
This token represents the current month. |
| 9395 |
For example, "Oct". |
| 9396 |
</DD> |
| 9397 |
|
| 9398 |
<DT>CURYEAR</DT> |
| 9399 |
<DD> |
| 9400 |
This token represents the current year. |
| 9401 |
For example, "1998" or "2001". |
| 9402 |
</DD> |
| 9403 |
|
| 9404 |
<DT>CURYEAR2DIGIT</DT> |
| 9405 |
<DD> |
| 9406 |
This token represents the current year. |
| 9407 |
For example, "98" or "01". |
| 9408 |
It is always 2 digits. |
| 9409 |
</DD> |
| 9410 |
|
| 9411 |
<DT>LASTMONTH</DT> |
| 9412 |
<DD> |
| 9413 |
This token represents last month. |
| 9414 |
For example, if this is November (the 11th month), |
| 9415 |
it is equal to "10" or if this is October (the 10th month), |
| 9416 |
it is "9". |
| 9417 |
It is possible that this and the other tokens beginning with LASTMONTH |
| 9418 |
below could be useful when used with a Filtering Rule that |
| 9419 |
has the "Beginning of Month" option set. |
| 9420 |
</DD> |
| 9421 |
|
| 9422 |
<DT>LASTMONTH2DIGIT</DT> |
| 9423 |
<DD> |
| 9424 |
This token represents last month. |
| 9425 |
For example, if this is November (the 11th month), |
| 9426 |
it is equal to "10" or if this is October (the 10th month), |
| 9427 |
it is "09". |
| 9428 |
It is always 2 digits. |
| 9429 |
</DD> |
| 9430 |
|
| 9431 |
<DT>LASTMONTHLONG</DT> |
| 9432 |
<DD> |
| 9433 |
This token represents last month. |
| 9434 |
For example, if this is November the value is "October". |
| 9435 |
</DD> |
| 9436 |
|
| 9437 |
<DT>LASTMONTHABBREV</DT> |
| 9438 |
<DD> |
| 9439 |
This token represents last month. |
| 9440 |
For example, if this is November the value is "Oct". |
| 9441 |
</DD> |
| 9442 |
|
| 9443 |
<DT>LASTMONTHYEAR</DT> |
| 9444 |
<DD> |
| 9445 |
This token represents what the year was a month ago. |
| 9446 |
For example, if this is October, 1998, it is "1998". |
| 9447 |
If this is January, 1998, it is "1997". |
| 9448 |
</DD> |
| 9449 |
|
| 9450 |
<DT>LASTMONTHYEAR2DIGIT</DT> |
| 9451 |
<DD> |
| 9452 |
This token represents what the year was a month ago. |
| 9453 |
For example, if this is October, 1998, it is "98". |
| 9454 |
If this is January, 1998, it is "97". |
| 9455 |
</DD> |
| 9456 |
|
| 9457 |
<DT>LASTYEAR</DT> |
| 9458 |
<DD> |
| 9459 |
This token represents last year. |
| 9460 |
For example, if this is 1998, it equals "1997". |
| 9461 |
It is possible that this |
| 9462 |
could be useful when used with a Filtering Rule that |
| 9463 |
has the "Beginning of Year" option set. |
| 9464 |
</DD> |
| 9465 |
|
| 9466 |
<DT>LASTYEAR2DIGIT</DT> |
| 9467 |
<DD> |
| 9468 |
This token represents last year. |
| 9469 |
For example, if this is 1998, it equals "97". |
| 9470 |
It is always 2 digits. |
| 9471 |
</DD> |
| 9472 |
|
| 9473 |
<DT>ROLENICK</DT> |
| 9474 |
<DD> |
| 9475 |
This token represents the nickname of the |
| 9476 |
role currently being used. If no role is being used, |
| 9477 |
then no text will be printed for this token. |
| 9478 |
This token does not work with Filter Rule folder names. |
| 9479 |
</DD> |
| 9480 |
</DL> |
| 9481 |
|
| 9482 |
<P> |
| 9483 |
<H3><EM>Token Available Only for Reply-Leadin</EM></H3> |
| 9484 |
See the help for the |
| 9485 |
<A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option, |
| 9486 |
to see why you might want to use this. |
| 9487 |
Since the <EM>Reply-Leadin</EM> contains free text this token |
| 9488 |
must be surrounded by underscores when used. |
| 9489 |
|
| 9490 |
<DL> |
| 9491 |
<DT>NEWLINE</DT> |
| 9492 |
<DD> |
| 9493 |
This is an end of line marker. |
| 9494 |
</DD> |
| 9495 |
</DL> |
| 9496 |
<P> |
| 9497 |
<H3><EM>Token Available Only for Templates and Signatures</EM></H3> |
| 9498 |
|
| 9499 |
<DL> |
| 9500 |
<DT>CURSORPOS</DT> |
| 9501 |
<DD> |
| 9502 |
This token is different from the others. |
| 9503 |
When it is replaced it is replaced with nothing, but it sets a <EM>Alpine</EM> |
| 9504 |
internal variable which tells the composer to start with the cursor |
| 9505 |
positioned at the position where this token was. |
| 9506 |
If both the template file and the signature file contain |
| 9507 |
a "CURSORPOS" token, then the position in the template file |
| 9508 |
is used. |
| 9509 |
If there is a template file and neither it nor the signature file contains |
| 9510 |
a "CURSORPOS" token, then the cursor is positioned |
| 9511 |
after the end of the contents of the |
| 9512 |
template file when the composer starts up. |
| 9513 |
</DD> |
| 9514 |
</DL> |
| 9515 |
|
| 9516 |
<H2><A NAME="reply-token-conditionals"></A>Conditional Inclusion of Text for Reply-Leadin, Signatures, and Templates</H2> |
| 9517 |
|
| 9518 |
Conditional text inclusion may be used with |
| 9519 |
the <A HREF="#reply-leadin"><EM>Reply-Leadin</EM></A> option, |
| 9520 |
in signature files, and in template files used in |
| 9521 |
roles. |
| 9522 |
It may <EM>not</EM> be used with the |
| 9523 |
<EM>Index-Format</EM> option. |
| 9524 |
|
| 9525 |
<P> |
| 9526 |
There is a limited if-else capability for including text. |
| 9527 |
The if-else condition is based |
| 9528 |
on whether or not a given token would result in replacement text you |
| 9529 |
specify. |
| 9530 |
The syntax of this conditional inclusion is |
| 9531 |
<P> |
| 9532 |
<CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER> |
| 9533 |
<P> |
| 9534 |
The left parenthesis must follow the underscore immediately, with no |
| 9535 |
intervening space. |
| 9536 |
It means the token is expanded and the results of that expansion are |
| 9537 |
compared against the "match_this" argument. |
| 9538 |
If there is an exact match, then the "if_matched" text is used |
| 9539 |
as the replacement text. |
| 9540 |
Otherwise, the "if_not_matched" text is used. |
| 9541 |
One of the most useful values for the "match_this" argument is |
| 9542 |
the empty string, "". |
| 9543 |
In that case the expansion is compared against the empty string. |
| 9544 |
<P> |
| 9545 |
Here's an example to make it clearer. |
| 9546 |
This text could be included in one of your template files: |
| 9547 |
<P> |
| 9548 |
<CENTER><SAMP>_NEWS_("", "I'm replying to email","I'm replying to news")</SAMP></CENTER> |
| 9549 |
<P> |
| 9550 |
If that is included in a template file which you are using while replying |
| 9551 |
to a message (because you chose to use the role it was part of), |
| 9552 |
and that message has a newsgroup header and a newsgroup in that header, |
| 9553 |
then the text |
| 9554 |
<P> |
| 9555 |
<CENTER><SAMP>I'm replying to news</SAMP></CENTER> |
| 9556 |
<P> |
| 9557 |
will be included in the message you are about to compose. |
| 9558 |
On the other hand, if the message you are replying to does not have |
| 9559 |
a newsgroup, then the text |
| 9560 |
<P> |
| 9561 |
<CENTER><SAMP>I'm replying to email</SAMP></CENTER> |
| 9562 |
<P> |
| 9563 |
would be included instead. |
| 9564 |
This would also work in signature files and in |
| 9565 |
the "Reply-Leadin" option. |
| 9566 |
If the "match_this", "if_matched", |
| 9567 |
or "if_not_matched" arguments contain |
| 9568 |
spaces, parentheses, or commas; |
| 9569 |
they have to be quoted with double quotation marks (like in the example |
| 9570 |
above). |
| 9571 |
If you want to include a literal quote in the text you must escape the |
| 9572 |
quote by preceding it with a backslash character. |
| 9573 |
If you want to include a literal backslash character you must escape it |
| 9574 |
by preceding it with another backslash. |
| 9575 |
<P> |
| 9576 |
The comma followed by "if_not_matched" is optional. |
| 9577 |
If there is no "if_not_matched" |
| 9578 |
present then no text is included if the not_matched case is true. |
| 9579 |
Here's another example: |
| 9580 |
<P> |
| 9581 |
<CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER> |
| 9582 |
<P> |
| 9583 |
Here you can see that tokens may appear in the arguments. |
| 9584 |
The same is true for tokens with the conditional parentheses. |
| 9585 |
They may appear in arguments, |
| 9586 |
though you do have to be careful to get the quoting and escaping of |
| 9587 |
nested double quotes correct. |
| 9588 |
If this was in the signature file being used and you were replying to a message |
| 9589 |
sent to comp.mail.pine the resulting text would be: |
| 9590 |
<P> |
| 9591 |
<CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER> |
| 9592 |
<P> |
| 9593 |
If you were replying to a message which wasn't sent to any newsgroup the |
| 9594 |
resulting text would be a single blank line. |
| 9595 |
The reason you'd get a blank line is because the end of the line is |
| 9596 |
outside of the conditional, so is always included. |
| 9597 |
If you wanted to get rid of that blank line you could do so by moving |
| 9598 |
the end of line inside the conditional. |
| 9599 |
In other words, it's ok to have multi-line |
| 9600 |
"if_matched" or "if_not_matched" arguments. |
| 9601 |
The text just continues until the next double quotation, even if it's not |
| 9602 |
on the same line. |
| 9603 |
<P> |
| 9604 |
Here's one more (contrived) example illustrating a matching argument |
| 9605 |
which is not the empty string. |
| 9606 |
<P> |
| 9607 |
<CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER> |
| 9608 |
<P> |
| 9609 |
If this was the value of your "Reply-Leadin" option and you |
| 9610 |
were replying to |
| 9611 |
a message which was sent today, then the value of the "Reply-Leadin" |
| 9612 |
would be |
| 9613 |
<P> |
| 9614 |
<CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER> |
| 9615 |
<P> |
| 9616 |
But if you were replying to a message sent on Oct. 27 (and that wasn't |
| 9617 |
today) you would get |
| 9618 |
<P> |
| 9619 |
<CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER> |
| 9620 |
<P> |
| 9621 |
|
| 9622 |
<H2><A NAME="per-server-ldap-config"></A>Per Server Directory Configuration</H2> |
| 9623 |
|
| 9624 |
This is only available if <EM>Alpine</EM> was built with LDAP support. |
| 9625 |
If that's the case, there will be a Directory option underneath the Setup |
| 9626 |
command on the Main Menu. |
| 9627 |
Each server that is defined there has several configuration variables |
| 9628 |
which control the behavior when using it. |
| 9629 |
|
| 9630 |
<DL COMPACT> |
| 9631 |
|
| 9632 |
<DT> <A NAME="ldap-server"><EM>ldap-server</EM></A> |
| 9633 |
|
| 9634 |
<DD> This is the name of the host where an LDAP server is running. |
| 9635 |
<P> |
| 9636 |
To find out whether your organization has its own LDAP server, |
| 9637 |
contact its computing support staff. |
| 9638 |
<P> |
| 9639 |
|
| 9640 |
<DT> <A NAME="search-base"><EM>search-base</EM></A> |
| 9641 |
|
| 9642 |
<DD> This is the search base to be used on this server. |
| 9643 |
It functions as a filter |
| 9644 |
by restricting your searches in the LDAP server database |
| 9645 |
to the specified contents of the specified fields. |
| 9646 |
Without it, searches submitted to this directory server may fail. |
| 9647 |
It might be something like: |
| 9648 |
|
| 9649 |
<PRE> |
| 9650 |
O = <Your Organization Name>, C = US |
| 9651 |
</PRE> |
| 9652 |
|
| 9653 |
or it might be blank. |
| 9654 |
(Some LDAP servers actually ignore anything specified here.) |
| 9655 |
<P> |
| 9656 |
|
| 9657 |
If in doubt what parameters you should specify here, |
| 9658 |
contact the maintainers of the LDAP server. |
| 9659 |
<P> |
| 9660 |
|
| 9661 |
<DT> <A NAME="port"><EM>port</EM></A> |
| 9662 |
|
| 9663 |
<DD> This is the TCP port number to be used with this LDAP server. |
| 9664 |
If you leave this blank port <CODE>389</CODE> will be used. |
| 9665 |
<P> |
| 9666 |
|
| 9667 |
<DT> <A NAME="ldap-nickname"><EM>nickname</EM></A> |
| 9668 |
|
| 9669 |
<DD> This is a nickname to be used in displays. |
| 9670 |
If you don't supply a nickname the server name from |
| 9671 |
"ldap-server" will be used instead. |
| 9672 |
This option is strictly for your convenience. |
| 9673 |
<P> |
| 9674 |
|
| 9675 |
<DT> <A NAME="use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A> |
| 9676 |
|
| 9677 |
<DD> Set this feature to have lookups done to this server implicitly from |
| 9678 |
the composer. |
| 9679 |
If an address doesn't look like a fully-qualified address, it will be looked |
| 9680 |
up in your address books, and if it doesn't match a nickname there, then it |
| 9681 |
will be looked up on the LDAP servers which have this feature set. |
| 9682 |
The lookups will also be done when using the address completion feature |
| 9683 |
(TAB command) in the composer if any of the serves have this feature set. |
| 9684 |
Also see the LDAP feature |
| 9685 |
<A HREF="#lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A> |
| 9686 |
and the Setup/Config feature |
| 9687 |
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>. |
| 9688 |
<P> |
| 9689 |
|
| 9690 |
<DT> <A NAME="lookup-addrbook-contents"><EM>lookup-addrbook-contents</EM></A> |
| 9691 |
|
| 9692 |
<DD> Normally implicit LDAP lookups from the composer are done only for the |
| 9693 |
strings you type in from the composer screen. In other words, you type in |
| 9694 |
something in the To or CC field and press return, then the string is looked up. |
| 9695 |
First that string is looked up in your address books. If a match is found |
| 9696 |
there, then the results of that match are looked up again. If you place |
| 9697 |
a string in your address book that you want to have looked up on the LDAP |
| 9698 |
directory server, you need to turn on this feature. If you set this feature |
| 9699 |
for a server, you almost always will also want to set the |
| 9700 |
<A HREF="#use-implicitly-from-composer"><EM>use-implicitly-from-composer</EM></A> |
| 9701 |
feature. |
| 9702 |
An example might serve to best illustrate this feature. |
| 9703 |
<P> |
| 9704 |
If an LDAP lookup of "William Clinton" normally returns an |
| 9705 |
entry with an |
| 9706 |
address of [email protected], then you might put an entry in your address |
| 9707 |
book that looks like: |
| 9708 |
<PRE> |
| 9709 |
Nickname Address |
| 9710 |
bill "William Clinton" |
| 9711 |
</PRE> |
| 9712 |
Now, when you type "bill" into an |
| 9713 |
address field in the composer <EM>Alpine</EM> will |
| 9714 |
find the "bill" entry in your address book. |
| 9715 |
It will replace "bill" with |
| 9716 |
"William Clinton". |
| 9717 |
It will then search for an entry with that nickname |
| 9718 |
in your address book and not find one. If this feature |
| 9719 |
is set, <EM>Alpine</EM> will then attempt to lookup |
| 9720 |
"William Clinton" on the LDAP server and find the entry with address |
| 9721 |
[email protected]. |
| 9722 |
<P> |
| 9723 |
A better way to accomplish the same thing is probably to use the feature |
| 9724 |
<A HREF="#save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A>. |
| 9725 |
<P> |
| 9726 |
|
| 9727 |
<DT> <A NAME="save-search-criteria-not-result"><EM>save-search-criteria-not-result</EM></A> |
| 9728 |
|
| 9729 |
<DD> Normally when you save the results of an LDAP directory lookup to your |
| 9730 |
address book the <EM>results</EM> of the lookup are saved. |
| 9731 |
If this feature is set |
| 9732 |
and the entry being saved was found on this directory server, then the |
| 9733 |
search <EM>criteria</EM> is saved instead of the <EM>results</EM> of the search. |
| 9734 |
When this address book entry is used in the future, instead of copying |
| 9735 |
the results from the address book the directory lookup will be done again. |
| 9736 |
This could be useful if the copied result might become stale because the data on |
| 9737 |
the directory server changes (for example, the entry's email address changes). |
| 9738 |
You probably don't want to set this feature if the server is at all slow or |
| 9739 |
unreliable. |
| 9740 |
<P> |
| 9741 |
The way this actually works is that instead of saving the email address |
| 9742 |
in your address book, <EM>Alpine</EM> saves enough |
| 9743 |
information to look up the same directory entry again. |
| 9744 |
In particular, it saves the server name and the |
| 9745 |
distinguished name of the entry. |
| 9746 |
It's possible that the server administrators |
| 9747 |
might change the format of distinguished names on the server, or that the |
| 9748 |
entry might be removed from the server. If <EM>Alpine</EM> notices this, you will be warned |
| 9749 |
and a backup copy of the email address will be used. You may want to create |
| 9750 |
a new entry in this case, since you will get the annoying warning every |
| 9751 |
time you use the old entry. You may do that by Saving the entry to a new |
| 9752 |
nickname in the same address book. You will be asked whether or not you |
| 9753 |
want to use the backup email address. |
| 9754 |
<P> |
| 9755 |
A related feature in the Setup/Config screen is |
| 9756 |
<A HREF="#ldap-result-to-addrbook-add"><EM>ldap-result-to-addrbook-add</EM></A>. |
| 9757 |
<P> |
| 9758 |
|
| 9759 |
<DT> <A NAME="disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A> |
| 9760 |
|
| 9761 |
<DD> Spaces in your input are normally handled specially. |
| 9762 |
Each space character is replaced |
| 9763 |
by |
| 9764 |
<PRE> |
| 9765 |
* <SPACE> |
| 9766 |
</PRE> |
| 9767 |
in the search query (but not by "* <SPACE> *"). |
| 9768 |
The reason this is done is so the input string |
| 9769 |
<PRE> |
| 9770 |
Greg Donald |
| 9771 |
</PRE> |
| 9772 |
(which is converted to "Greg* Donald") will match |
| 9773 |
the names "Greg Donald", |
| 9774 |
"Gregory Donald", "Greg F. Donald", and |
| 9775 |
"Gregory F Donald"; but it won't match "Greg McDonald". |
| 9776 |
If the "Search-Rule" you were using was "begins-with", |
| 9777 |
then it would also match the name "Greg Donaldson". |
| 9778 |
<P> |
| 9779 |
Turning on this feature will disable this substitution. |
| 9780 |
<P> |
| 9781 |
|
| 9782 |
<DT> <A NAME="search-type"><EM>search-type</EM></A> |
| 9783 |
|
| 9784 |
<DD> This affects the way that LDAP searches are done. |
| 9785 |
In particular, this tells the server where to look for the string to be matched. |
| 9786 |
If set to "name" then the string that is being searched for will |
| 9787 |
be compared with the string in the |
| 9788 |
"Name" field on the server |
| 9789 |
(technically, it is the "commonname" field on the server). |
| 9790 |
"Surname" means we're looking for a |
| 9791 |
match in the "Surname" field on the |
| 9792 |
server (actually the "sn" field). |
| 9793 |
"Givenname" really is "givenname" |
| 9794 |
and "email" is the electronic mail address (this is actually the field |
| 9795 |
called "mail" or "electronicmail" on the server). |
| 9796 |
The other three types are combinations of |
| 9797 |
the types listed so far. "Name-or-email" |
| 9798 |
means the string should appear |
| 9799 |
in either the "name" field OR the "email" field. |
| 9800 |
Likewise, "surname-or-givenname" |
| 9801 |
means "surname" OR "givenname" |
| 9802 |
and "sur-or-given-or-name-or-email" means the obvious thing. |
| 9803 |
<P> |
| 9804 |
This search <EM>type</EM> is combined with the |
| 9805 |
search <A HREF="#search-rule"><EM>rule</EM></A> |
| 9806 |
to form the actual search query. |
| 9807 |
<P> |
| 9808 |
The usual default value for this |
| 9809 |
option is "sur-or-given-or-name-or-email". |
| 9810 |
This type of search may be slow on some servers. |
| 9811 |
Try "name-or-email", which is often |
| 9812 |
faster, or just "name" if the performance seems to be a problem. |
| 9813 |
<P> |
| 9814 |
Some servers have been configured with different attribute names for |
| 9815 |
these four fields. |
| 9816 |
In other words, instead of using the attribute name "mail" |
| 9817 |
for the email address field, the server might be configured to use something |
| 9818 |
else, for example, "rfc822mail" or "internetemailaddress". |
| 9819 |
<EM>Alpine</EM> can be configured to use these different attribute names by using |
| 9820 |
the four per-server configuration options: |
| 9821 |
<P><UL> |
| 9822 |
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A> |
| 9823 |
</UL> |
| 9824 |
<P><UL> |
| 9825 |
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A> |
| 9826 |
</UL> |
| 9827 |
<P><UL> |
| 9828 |
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A> |
| 9829 |
</UL> |
| 9830 |
<P><UL> |
| 9831 |
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A> |
| 9832 |
</UL> |
| 9833 |
<P> |
| 9834 |
|
| 9835 |
<DT> <A NAME="search-rule"><EM>search-rule</EM></A> |
| 9836 |
|
| 9837 |
<DD> This affects the way that LDAP searches are done. |
| 9838 |
If set to "equals" then |
| 9839 |
only exact matches count. |
| 9840 |
"Contains" means that the string you type in |
| 9841 |
is a substring of what you are matching against. |
| 9842 |
"Begins-with" and "ends-with" |
| 9843 |
mean that the string starts or ends with the string you type in. |
| 9844 |
<P> |
| 9845 |
Spaces in your input are normally handled specially, but you can turn that |
| 9846 |
special handling off with the |
| 9847 |
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A> |
| 9848 |
feature. |
| 9849 |
<P> |
| 9850 |
The usual default value for this option is <EM>begins-with</EM>. |
| 9851 |
<P> |
| 9852 |
|
| 9853 |
<DT> <A NAME="email-attribute"><EM>email-attribute</EM></A> |
| 9854 |
|
| 9855 |
<DD> This is the name of the attribute which is searched for when looking for |
| 9856 |
an email address. The default value for this option is "mail" or |
| 9857 |
"electronicmail". |
| 9858 |
If the server you are using uses a different attribute name for the email |
| 9859 |
address, put that attribute name here. |
| 9860 |
<P> |
| 9861 |
This will affect the search filter used if your Search-Type is one that |
| 9862 |
contains a search for "email". |
| 9863 |
It will also cause the attribute value matching this attribute name to be used |
| 9864 |
as the email address when you look up an entry from the composer. |
| 9865 |
<P> |
| 9866 |
|
| 9867 |
<DT> <A NAME="name-attribute"><EM>name-attribute</EM></A> |
| 9868 |
|
| 9869 |
<DD> This is the name of the attribute which is searched for when looking for |
| 9870 |
the name of the entry. The default value for this option is "cn", which |
| 9871 |
stands for common name. |
| 9872 |
If the server you are using uses a different attribute name for the name, |
| 9873 |
put that attribute name here. |
| 9874 |
This will affect the search filter used if your Search-Type is one that |
| 9875 |
contains a search for "name". |
| 9876 |
<P> |
| 9877 |
|
| 9878 |
<DT> <A NAME="surname-attribute"><EM>surname-attribute</EM></A> |
| 9879 |
|
| 9880 |
<DD> This is the name of the attribute which is searched for when looking for |
| 9881 |
the surname of the entry. The default value for this option is "sn". |
| 9882 |
If the server you are using uses a different attribute name for the surname, |
| 9883 |
put that attribute name here. |
| 9884 |
This will affect the search filter used if your Search-Type is one that |
| 9885 |
contains a search for "surname". |
| 9886 |
<P> |
| 9887 |
|
| 9888 |
<DT> <A NAME="givenname-attribute"><EM>givenname-attribute</EM></A> |
| 9889 |
|
| 9890 |
<DD> This is the name of the attribute which is searched for when looking for |
| 9891 |
the given name of the entry. The default value for this option is "givenname". |
| 9892 |
If the server you are using uses a different attribute name for the given name, |
| 9893 |
put that attribute name here. |
| 9894 |
This will affect the search filter used if your Search-Type is one that |
| 9895 |
contains a search for "givenname". |
| 9896 |
<P> |
| 9897 |
|
| 9898 |
<DT> <A NAME="timelimit"><EM>timelimit</EM></A> |
| 9899 |
|
| 9900 |
<DD> This places a limit on the number of seconds the LDAP search will continue. |
| 9901 |
The default is 30 seconds. A value of 0 means no limit. Note that some servers |
| 9902 |
may place limits of their own on searches. |
| 9903 |
<P> |
| 9904 |
|
| 9905 |
<DT> <A NAME="sizelimit"><EM>sizelimit</EM></A> |
| 9906 |
|
| 9907 |
<DD> This places a limit on the number of entries returned by the LDAP server. |
| 9908 |
A value of 0 means no limit. The default is 0. Note that some servers |
| 9909 |
may place limits of their own on searches. |
| 9910 |
<P> |
| 9911 |
|
| 9912 |
<DT> <A NAME="custom-search-filter"><EM>custom-search-filter</EM></A> |
| 9913 |
|
| 9914 |
<DD> This one is for advanced users only! If you define this, then the |
| 9915 |
<A HREF="#search-type"><EM>search-type</EM></A> |
| 9916 |
and |
| 9917 |
<A HREF="#search-rule"><EM>search-rule</EM></A> |
| 9918 |
defined are both ignored. |
| 9919 |
However, the feature |
| 9920 |
<A HREF="#disable-ad-hoc-space-substitution"><EM>disable-ad-hoc-space-substitution</EM></A> |
| 9921 |
is still in effect. |
| 9922 |
That is, the space substitution will take place even in a custom filter unless |
| 9923 |
you disable it. |
| 9924 |
<P> |
| 9925 |
If your LDAP service stops working and you suspect it might be because |
| 9926 |
of your custom filter, just delete this filter and try using the |
| 9927 |
<EM>search-type</EM> and <EM>search-rule</EM> instead. |
| 9928 |
Another option that sometimes causes trouble is the |
| 9929 |
<A HREF="#search-base"><EM>search-base</EM></A> option. |
| 9930 |
<P> |
| 9931 |
This variable may be set to the string representation of an LDAP search |
| 9932 |
filter (see RFC1960). In the places where you want the address string to be |
| 9933 |
substituted in, put a '%s' in this filter string. Here are some examples: |
| 9934 |
<P> |
| 9935 |
A "Search-Type" of "name" with "Search-Rule" of "begins-with" |
| 9936 |
is equivalent to the "custom-search-filter" |
| 9937 |
<PRE> |
| 9938 |
(cn=%s*) |
| 9939 |
</PRE> |
| 9940 |
When you try to match against the string "string" the program replaces |
| 9941 |
the "%s" with "string" (without the quotes). You may have multiple "%s"'s and |
| 9942 |
they will all be replaced with the string. There is a limit of 10 "%s"'s. |
| 9943 |
<P> |
| 9944 |
A "Search-Type" of "name-or-email" with "Search-Rule" |
| 9945 |
of "contains" is equivalent to |
| 9946 |
<PRE> |
| 9947 |
(|(cn=*%s*)(mail=*%s*)) |
| 9948 |
</PRE> |
| 9949 |
<P> |
| 9950 |
If your server uses a different attribute <EM>name</EM> than |
| 9951 |
<EM>Alpine</EM> uses by default, |
| 9952 |
(for example, it uses "rfc822mail" instead of "mail"), |
| 9953 |
then you may be able to use one or more of the four attribute configuration |
| 9954 |
options instead of defining a custom filter: |
| 9955 |
<P><UL> |
| 9956 |
<LI><A HREF="#email-attribute"><EM>email-attribute</EM></A> |
| 9957 |
</UL> |
| 9958 |
<P><UL> |
| 9959 |
<LI><A HREF="#name-attribute"><EM>name-attribute</EM></A> |
| 9960 |
</UL> |
| 9961 |
<P><UL> |
| 9962 |
<LI><A HREF="#surname-attribute"><EM>surname-attribute</EM></A> |
| 9963 |
</UL> |
| 9964 |
<P><UL> |
| 9965 |
<LI><A HREF="#givenname-attribute"><EM>givenname-attribute</EM></A> |
| 9966 |
</UL> |
| 9967 |
|
| 9968 |
</DL> |
| 9969 |
<P> |
| 9970 |
|
| 9971 |
<H2><A NAME="color-config"></A>Color Configuration</H2> |
| 9972 |
|
| 9973 |
If the terminal or terminal emulator you are using is capable of using |
| 9974 |
color (see <A HREF="#color-style"><EM>color-style</EM></A> option), |
| 9975 |
or if you are using <EM>PC-Alpine</EM>, then it is possible to |
| 9976 |
set up <EM>Alpine</EM> so that various parts of the display will be |
| 9977 |
shown in colors you configure. |
| 9978 |
This is done using the Setup Color screen. |
| 9979 |
The Setup Color screen is divided into five broad sections: Options, |
| 9980 |
General Colors, Index Colors, Header Colors, and Keyword Colors. |
| 9981 |
In addition to these five categories you may also color lines in the |
| 9982 |
MESSAGE INDEX screen by configuring the |
| 9983 |
<A HREF="#index-color-config">Index Line Color</A>. |
| 9984 |
<P> |
| 9985 |
Each color is defined as a foreground color (the color of the actual text) |
| 9986 |
and a background color (the color of the area behind the text). |
| 9987 |
<P> |
| 9988 |
<H3><A NAME="color-options"></A>Color Options</H3> |
| 9989 |
|
| 9990 |
<DL> |
| 9991 |
|
| 9992 |
<DT> <A NAME="cur-il-style"><EM>current-indexline-style</EM></A> |
| 9993 |
<DD> |
| 9994 |
This option affects the colors used to display the current line in the |
| 9995 |
MESSAGE INDEX screen. |
| 9996 |
If you do not have |
| 9997 |
<A HREF="#index-color-config">Index Line Colors</A> |
| 9998 |
defined, then this option will have no effect in the index. |
| 9999 |
Those Rules may be defined by going to the Setup/Rules/Indexcolor screen. |
| 10000 |
<P> |
| 10001 |
If the option |
| 10002 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 10003 |
is turned on and the |
| 10004 |
<A HREF="#incoming-unseen-color"><EM>Incoming Unseen Color</EM></A> |
| 10005 |
is set to something other than the default, then |
| 10006 |
this option also affects the color used to display the current folder |
| 10007 |
in the Incoming FOLDER LIST screen. |
| 10008 |
|
| 10009 |
<P> |
| 10010 |
The available options include: |
| 10011 |
<P> |
| 10012 |
|
| 10013 |
<DL> |
| 10014 |
<DT>flip-colors</DT> |
| 10015 |
<DD>This is the default. |
| 10016 |
If an index line is colored because it matches one of your |
| 10017 |
Index Color Rules, then its colors will be reversed when it is the currently |
| 10018 |
highlighted line. |
| 10019 |
For example, if the line is normally red text on a blue background, then |
| 10020 |
when it is the current line it will be drawn as blue text on a red background. |
| 10021 |
<P> |
| 10022 |
The rest of the option values all revert to this flip-colors behavior if |
| 10023 |
there is no Reverse Color defined. |
| 10024 |
</DD> |
| 10025 |
|
| 10026 |
<DT>reverse</DT> |
| 10027 |
<DD>With this option the Reverse color is always used to highlight the |
| 10028 |
current line. |
| 10029 |
</DD> |
| 10030 |
|
| 10031 |
<DT>reverse-fg</DT> |
| 10032 |
<DD>The foreground part of the Reverse Color is used to highlight |
| 10033 |
the current line. |
| 10034 |
If this would cause the text to be unreadable (because the foreground and |
| 10035 |
background colors are the same) or if it would cause no change in the |
| 10036 |
color of the index line, then the colors are flipped instead. |
| 10037 |
<P> |
| 10038 |
Some people think this works particularly well if you use different |
| 10039 |
background colors to emphasize "interesting" lines, |
| 10040 |
but always with the same Normal foreground color, |
| 10041 |
and you use a different foreground color for the Reverse Color. |
| 10042 |
</DD> |
| 10043 |
|
| 10044 |
<DT>reverse-fg-no-ambiguity</DT> |
| 10045 |
<DD>With the "reverse-fg" rule above, it is possible that |
| 10046 |
the resulting color will be exactly the same as the regular Reverse |
| 10047 |
Color. |
| 10048 |
That can lead to some possible confusion because an |
| 10049 |
"interesting" |
| 10050 |
line which is the current line will be displayed exactly the same as a |
| 10051 |
non-interesting line which is current. |
| 10052 |
You can't tell whether the line is just a regular current line or if it is |
| 10053 |
an "interesting" current line by looking at the color. |
| 10054 |
Setting the option to this value removes that ambiguity. |
| 10055 |
It is the same as the "reverse-fg" setting unless the resulting |
| 10056 |
interesting current line would look just like a non-interesting current line. |
| 10057 |
In that case, the interesting line's colors are simply flipped (like in the |
| 10058 |
default behavior). |
| 10059 |
<P> |
| 10060 |
As an alternative way to preserve the line's interestingness in this case, |
| 10061 |
you may find that using both a different foreground and a different |
| 10062 |
background color for the interesting line will help. |
| 10063 |
</DD> |
| 10064 |
|
| 10065 |
<DT>reverse-bg</DT> |
| 10066 |
<DD>The background part of the Reverse Color is used to highlight |
| 10067 |
the current line. |
| 10068 |
If this would cause the text to be unreadable (because the foreground and |
| 10069 |
background colors are the same) or if it would cause no change in the |
| 10070 |
color of the index line, then the colors are flipped instead. |
| 10071 |
<P> |
| 10072 |
Some people think this works particularly well if you use different |
| 10073 |
foreground colors to emphasize "interesting" lines, |
| 10074 |
but always with the same Normal background color, |
| 10075 |
and you use a different background color for the Reverse Color. |
| 10076 |
</DD> |
| 10077 |
|
| 10078 |
<DT>reverse-bg-no-ambiguity</DT> |
| 10079 |
<DD>As with the "reverse-fg" case, the "reverse-bg" |
| 10080 |
rule may also result in a color which is exactly the same as the regular |
| 10081 |
Reverse Color. |
| 10082 |
Setting the option to this value removes that ambiguity. |
| 10083 |
It is the same as the "reverse-bg" setting unless the resulting |
| 10084 |
current line has the same color as the Reverse Color. |
| 10085 |
In that case, the interesting line's colors are simply flipped (like in the |
| 10086 |
default behavior). |
| 10087 |
</DD> |
| 10088 |
</DL> |
| 10089 |
|
| 10090 |
<DT> <A NAME="titlebar-style"><EM>titlebar-color-style</EM></A> |
| 10091 |
<DD> |
| 10092 |
This option affects the colors used to display the titlebar (the top |
| 10093 |
line on the screen) when viewing a message. |
| 10094 |
|
| 10095 |
<P> |
| 10096 |
The available options include: |
| 10097 |
<P> |
| 10098 |
|
| 10099 |
<DL> |
| 10100 |
<DT>default</DT> |
| 10101 |
<DD>The color of the titlebar will be the color you set for the |
| 10102 |
<A HREF="#title-color"><EM>Title Color</EM></A>. |
| 10103 |
The Title Color may be set by using the |
| 10104 |
</DD> |
| 10105 |
|
| 10106 |
<DT>indexline</DT> |
| 10107 |
<DD>The color of the titlebar will be the same as the color of the |
| 10108 |
index line corresponding to the message being viewed. |
| 10109 |
The rules which determine what color the index line will be may be set |
| 10110 |
up by going to the Setup/Rules/Indexcolor screen. |
| 10111 |
If the index line for a message is not colored explicitly by the |
| 10112 |
Indexcolor rules, then the titlebar will be colored the same as for |
| 10113 |
the "default" option above (which is not the same color that |
| 10114 |
the index line itself will have). |
| 10115 |
</DD> |
| 10116 |
|
| 10117 |
<DT>reverse-indexline</DT> |
| 10118 |
<DD>This is similar to the "indexline" option except the |
| 10119 |
foreground and background colors from the corresponding index line will |
| 10120 |
be reversed. |
| 10121 |
For example, if the index line color is red letters on a white background, |
| 10122 |
then the titlebar will be white letters on a red background. |
| 10123 |
If the index line for a message is not colored explicitly by the |
| 10124 |
Indexcolor rules, then the titlebar will be colored the same as for |
| 10125 |
the "default" option above (which is not the same color that |
| 10126 |
the index line itself will have). |
| 10127 |
</DD> |
| 10128 |
</DL> |
| 10129 |
|
| 10130 |
</DL> |
| 10131 |
|
| 10132 |
<P> |
| 10133 |
<H3><A NAME="general-colors"></A>General Colors</H3> |
| 10134 |
|
| 10135 |
<DL COMPACT> |
| 10136 |
|
| 10137 |
<DT> <A NAME="normal-color"><EM>Normal Color</EM></A> |
| 10138 |
|
| 10139 |
<DD> This is the color which most of the screen is painted in. |
| 10140 |
By default this color is black characters on a white background. |
| 10141 |
<P> |
| 10142 |
|
| 10143 |
<DT> <A NAME="reverse-color"><EM>Reverse Color</EM></A> |
| 10144 |
|
| 10145 |
<DD> The color <EM>Alpine</EM> uses for reverse video characters. |
| 10146 |
Actually, the name is misleading. This used to be reverse video and so |
| 10147 |
the name remains. It is still used to highlight certain parts of the |
| 10148 |
screen but the color may be set to whatever you'd like. |
| 10149 |
<P> |
| 10150 |
|
| 10151 |
<DT> <A NAME="title-color"><EM>Title Color</EM></A> |
| 10152 |
|
| 10153 |
<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the |
| 10154 |
screen). |
| 10155 |
By default, the Title Color is black characters on a yellow background. |
| 10156 |
The actual titlebar color may be different from the Title Color if |
| 10157 |
the option |
| 10158 |
<A HREF="#titlebar-color-style"><EM>titlebar-color-style</EM></A> |
| 10159 |
is set to some value other than the default. |
| 10160 |
It may also be different if the current folder is closed and the |
| 10161 |
<A HREF="#title-closed-color">Title Closed Color</A> |
| 10162 |
is set to something different from the Title Color. |
| 10163 |
<P> |
| 10164 |
|
| 10165 |
<DT> <A NAME="title-closed-color"><EM>Title-closed Color</EM></A> |
| 10166 |
|
| 10167 |
<DD> The color <EM>Alpine</EM> uses for the titlebar (the top line on the |
| 10168 |
screen) when the current folder is closed. |
| 10169 |
By default, the Title Color Closed Color is white characters on a red background. |
| 10170 |
<P> |
| 10171 |
|
| 10172 |
<DT> <A NAME="status-color"><EM>Status Color</EM></A> |
| 10173 |
|
| 10174 |
<DD> The color <EM>Alpine</EM> uses for messages written to the status |
| 10175 |
message line near the bottom of the screen. |
| 10176 |
By default, the Status Color is the same as the Reverse Color. |
| 10177 |
<P> |
| 10178 |
|
| 10179 |
<DT> <A NAME="keylabel-color"><EM>KeyLabel Color</EM></A> |
| 10180 |
|
| 10181 |
<DD> The color <EM>Alpine</EM> uses for the labels of the commands in the |
| 10182 |
two-line menu at the bottom of the screen. |
| 10183 |
The label is the long name, for example, "PrevMsg". |
| 10184 |
By default, the KeyLabel Color is the same as the Normal Color. |
| 10185 |
<P> |
| 10186 |
WARNING: Some terminal emulators have the property that the screen will scroll |
| 10187 |
down one line whenever a character is written to the character cell in the |
| 10188 |
lower right corner of the screen. |
| 10189 |
<EM>Alpine</EM> can usually avoid writing a character in that corner of the screen. |
| 10190 |
However, if you have defined a KeyLabel Color then <EM>Alpine</EM> does have to write |
| 10191 |
a character in that cell in order to color the cell correctly. |
| 10192 |
If you find that your display sometimes scrolls up a line this could be |
| 10193 |
the problem. |
| 10194 |
The most obvious symptom is probably that the titlebar at the top of the |
| 10195 |
screen scrolls off the screen. |
| 10196 |
Try setting KeyLabel Color to Default to see if that fixes the problem. |
| 10197 |
<P> |
| 10198 |
|
| 10199 |
<DT> <A NAME="keyname-color"><EM>KeyName Color</EM></A> |
| 10200 |
|
| 10201 |
<DD> The color <EM>Alpine</EM> uses for the names of the commands in the |
| 10202 |
two-line menu at the bottom of the screen. |
| 10203 |
The KeyName is the shorter name in the menu. For example, the "W" |
| 10204 |
before the "WhereIs". |
| 10205 |
By default, the KeyName Color is the same as the Normal Color. |
| 10206 |
<P> |
| 10207 |
|
| 10208 |
<DT> <A NAME="selectable-item-color"><EM>Selectable-item Color</EM></A> |
| 10209 |
|
| 10210 |
<DD> The color <EM>Alpine</EM> uses for displaying selectable items, such |
| 10211 |
as URLs. |
| 10212 |
By default, the Selectable-item Color is the same as the Normal Color, except |
| 10213 |
it is also Bold. |
| 10214 |
<P> |
| 10215 |
|
| 10216 |
<DT> <A NAME="meta-message-color"><EM>Meta-message Color</EM></A> |
| 10217 |
|
| 10218 |
<DD> The color <EM>Alpine</EM> uses in the MESSAGE TEXT screen for messages to you |
| 10219 |
that aren't part of the message itself. |
| 10220 |
By default, the Meta-Message Color is black characters on a yellow background. |
| 10221 |
<P> |
| 10222 |
|
| 10223 |
<DT> <A NAME="quote-colors"><EM>Quote Colors</EM></A> |
| 10224 |
|
| 10225 |
<DD> The colors <EM>Alpine</EM> uses for coloring quoted text in the |
| 10226 |
MESSAGE TEXT screen. |
| 10227 |
If a line begins with a > character (or space followed by >) it |
| 10228 |
is considered a quote. That line will be given the Quote1 Color (first |
| 10229 |
level quote). If there is a second level of quoting then the Quote2 Color |
| 10230 |
will be used. <EM>Alpine</EM> considers there to be a second level of quoting if |
| 10231 |
that first > is followed by another > (or space followed by >). |
| 10232 |
If there are characters other than whitespace and > signs, then it isn't |
| 10233 |
considered another level of quoting. Similarly, if there is a third level |
| 10234 |
of quoting the Quote3 Color will be used. If there are more levels after |
| 10235 |
that the Quote Colors are reused. If you define all three colors then it |
| 10236 |
would repeat like Color1, Color2, Color3, Color1, Color2, Color3, ... |
| 10237 |
If you only define the first two it would be Color1, Color2, |
| 10238 |
Color1, Color2, ... |
| 10239 |
If you define only the Quote1 Color, then the entire quote would be |
| 10240 |
that color regardless of the quoting levels. |
| 10241 |
By default, the Quote1 Color is black characters on a greenish-blue background; |
| 10242 |
the Quote2 Color is black characters on a dull yellow background; and |
| 10243 |
the Quote3 Color is black characters on a green background. |
| 10244 |
<P> |
| 10245 |
|
| 10246 |
<DT> <A NAME="incoming-unseen-color"><EM>Incoming Unseen Color</EM></A> |
| 10247 |
|
| 10248 |
<DD> If the option |
| 10249 |
<A HREF="#enable-incoming-folders-checking"><EM>enable-incoming-folders-checking</EM></A> |
| 10250 |
is turned on it is possible to highlight the folders that contain |
| 10251 |
unseen messages by coloring them with this color. |
| 10252 |
By default, this is the same as the Normal Color and no highlighting is done. |
| 10253 |
<P> |
| 10254 |
Usually the "current" folder (the folder the cursor is on) |
| 10255 |
is highlighted using reverse video. |
| 10256 |
If the current folder is colored because it contains unseen messages then |
| 10257 |
the color used to show that it is also the current folder is controlled |
| 10258 |
by the <A HREF="#cur-il-style"><EM>current-indexline-style</EM></A> |
| 10259 |
feature at the top of the SETUP COLOR screen. |
| 10260 |
<P> |
| 10261 |
|
| 10262 |
<DT> <A NAME="signature-color"><EM>Signature Color</EM></A> |
| 10263 |
|
| 10264 |
<DD> The color <EM>Alpine</EM> uses for coloring the signature in the MESSAGE TEXT |
| 10265 |
screen. According to USENET conventions, the signature is defined as the |
| 10266 |
paragraph following the "sigdashes", that is, the special line |
| 10267 |
consisting of the three characters |
| 10268 |
"-- " (i.e., dash, dash, and space). <EM>Alpine</EM> allows for one |
| 10269 |
empty line right after the sigdashes to be considered as part of the |
| 10270 |
signature. |
| 10271 |
By default, the Signature Color is blue characters on a white background. |
| 10272 |
<P> |
| 10273 |
|
| 10274 |
<DT> <A NAME="prompt-color"><EM>Prompt Color</EM></A> |
| 10275 |
|
| 10276 |
<DD> The color <EM>Alpine</EM> uses for confirmation prompts and questions |
| 10277 |
which appear in the status message line near the bottom of the screen. |
| 10278 |
By default, the Prompt Color is the same as the Reverse Color. |
| 10279 |
<P> |
| 10280 |
|
| 10281 |
</DL> |
| 10282 |
|
| 10283 |
<H3><A NAME="index-colors"></A>Index Colors</H3> |
| 10284 |
|
| 10285 |
You may add color to the single character symbols which give the status |
| 10286 |
of each message in the MESSAGE INDEX. |
| 10287 |
By default the characters "+", "*", "D", |
| 10288 |
"A", and "N" show up near the left hand side of the |
| 10289 |
screen, depending on whether the message is addressed to you, and whether |
| 10290 |
the message is marked Important, is Deleted, is Answered, or is New. |
| 10291 |
You may set the color of those symbols. |
| 10292 |
By default, all of these symbols are drawn with the same color as the rest |
| 10293 |
of the index line they are a part of. |
| 10294 |
<P> |
| 10295 |
Besides coloring the message status symbols, you may also color the |
| 10296 |
entire index line. |
| 10297 |
This is done by using the |
| 10298 |
<A HREF="#index-color-config">Index Line Color</A> configuration screen. |
| 10299 |
It is also possible to color |
| 10300 |
(<A HREF="#keywords">keywords</A> |
| 10301 |
in the index using the |
| 10302 |
Setup/Kolor screen (<A HREF="#keyword-colors">Keyword Colors</A>); |
| 10303 |
the <A HREF="#index-arrow-color">ARROW</A> cursor; |
| 10304 |
the Subject using |
| 10305 |
<A HREF="#index-subject-color">Index Subject Color</A>; |
| 10306 |
the From using |
| 10307 |
<A HREF="#index-from-color">Index From Color</A>; |
| 10308 |
and the |
| 10309 |
<A HREF="#index-opening-color">Index Opening</A> text. |
| 10310 |
<P> |
| 10311 |
|
| 10312 |
<DL COMPACT> |
| 10313 |
|
| 10314 |
<DT> <A NAME="index-to-me-color"><EM>Index-to-me Symbol Color</EM></A> |
| 10315 |
|
| 10316 |
<DD> The color used for drawing the "+" symbol which signifies a |
| 10317 |
message is addressed directly to you. |
| 10318 |
<P> |
| 10319 |
|
| 10320 |
<DT> <A NAME="index-important-color"><EM>Index-important Symbol Color</EM></A> |
| 10321 |
|
| 10322 |
<DD> The color used for drawing the "*" symbol which signifies a |
| 10323 |
message has been flagged Important. |
| 10324 |
<P> |
| 10325 |
|
| 10326 |
<DT> <A NAME="index-deleted-color"><EM>Index-deleted Symbol Color</EM></A> |
| 10327 |
|
| 10328 |
<DD> The color used for drawing the "D" symbol which signifies a |
| 10329 |
message has been marked Deleted. |
| 10330 |
<P> |
| 10331 |
|
| 10332 |
<DT> <A NAME="index-answered-color"><EM>Index-answered Symbol Color</EM></A> |
| 10333 |
|
| 10334 |
<DD> The color used for drawing the "A" symbol which signifies a |
| 10335 |
message has been answered. |
| 10336 |
<P> |
| 10337 |
|
| 10338 |
<DT> <A NAME="index-new-color"><EM>Index-new Symbol Color</EM></A> |
| 10339 |
|
| 10340 |
<DD> The color used for drawing the "N" symbol which signifies a |
| 10341 |
message is New. |
| 10342 |
<P> |
| 10343 |
|
| 10344 |
<DT> <A NAME="index-recent-color"><EM>Index-recent Symbol Color</EM></A> |
| 10345 |
|
| 10346 |
<DD> The color used for drawing the "R" symbol which signifies a |
| 10347 |
message is Recent (only visible if the "IMAPSTATUS" or "SHORTIMAPSTATUS" token is |
| 10348 |
part of the |
| 10349 |
<A HREF="#index-format"><EM>index-format</EM></A> option). |
| 10350 |
<P> |
| 10351 |
|
| 10352 |
<DT> <A NAME="index-unseen-color"><EM>Index-unseen Symbol Color</EM></A> |
| 10353 |
|
| 10354 |
<DD> The color used for drawing the "U" symbol which signifies a |
| 10355 |
message is Unseen (only visible if the "IMAPSTATUS" or "SHORTIMAPSTATUS" token is |
| 10356 |
part of the |
| 10357 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option). |
| 10358 |
<P> |
| 10359 |
|
| 10360 |
<DT> <A NAME="index-pri-color"><EM>Index-priority Symbol Colors</EM></A> |
| 10361 |
|
| 10362 |
<DD> The colors used for drawing the tokens "PRIORITY", |
| 10363 |
"PRIORITYALPHA", and "PRIORITY!" when these are |
| 10364 |
configured as part of the |
| 10365 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option. |
| 10366 |
You may set the color used to draw these tokens by use of the colors |
| 10367 |
Index High Priority Symbol Color and Index Low Priority Symbol Color. |
| 10368 |
This coloring takes place for all but the current index line, and the Priority |
| 10369 |
Color appears to be in front of any color from an Index Color Rule. |
| 10370 |
If the priority has a value of 1 or 2 the High Priority color will be |
| 10371 |
used, |
| 10372 |
and if the value is 4 or 5 the Low Priority color will be used. |
| 10373 |
<P> |
| 10374 |
If you don't set these colors the index line will be colored in the same color as |
| 10375 |
the bulk of the index line. |
| 10376 |
<P> |
| 10377 |
|
| 10378 |
<DT> <A NAME="index-arrow-color"><EM>Index-arrow Symbol Color</EM></A> |
| 10379 |
|
| 10380 |
<DD> The color used for drawing the "ARROW" token when it is |
| 10381 |
configured as part of the |
| 10382 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option. |
| 10383 |
<P> |
| 10384 |
|
| 10385 |
<DT> <A NAME="index-subject-color"><EM>Index-subject Symbol Color</EM></A> |
| 10386 |
|
| 10387 |
<DD> You may set the color used to draw the Subject part of the index line. |
| 10388 |
This coloring takes place for all but the current index line, and the Subject |
| 10389 |
Color appears to be in front of any color from an Index Color Rule. |
| 10390 |
<P> |
| 10391 |
If you don't set this color it will be colored in the same color as |
| 10392 |
the bulk of the index line. |
| 10393 |
<P> |
| 10394 |
|
| 10395 |
<DT> <A NAME="index-from-color"><EM>Index-from Symbol Color</EM></A> |
| 10396 |
|
| 10397 |
<DD> You may set the color used to draw the From part of the index line. |
| 10398 |
This coloring takes place for all but the current index line, and the From |
| 10399 |
Color appears to be in front of any color from an Index Color Rule. |
| 10400 |
<P> |
| 10401 |
If you don't set this color it will be colored in the same color as |
| 10402 |
the bulk of the index line. |
| 10403 |
<P> |
| 10404 |
|
| 10405 |
<DT> <A NAME="index-opening-color"><EM>Index-opening Symbol Color</EM></A> |
| 10406 |
|
| 10407 |
<DD> It is possible to configure the |
| 10408 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option |
| 10409 |
so that it includes the subject followed by the "opening" text of the |
| 10410 |
message if there is enough space. |
| 10411 |
This is done by using one of the tokens SUBJECTTEXT, SUBJKEYTEXT, or |
| 10412 |
SUBJKEYINITTEXT. |
| 10413 |
The color used for drawing this opening text is given by this option. |
| 10414 |
The coloring happens for all but the current index line, and this opening |
| 10415 |
color appears to be in front of any color from an Index Color Rule. |
| 10416 |
<P> |
| 10417 |
By default the Index Opening Color is gray characters on a white background. |
| 10418 |
<P> |
| 10419 |
|
| 10420 |
</DL> |
| 10421 |
<P> |
| 10422 |
The default colors for these symbols are: |
| 10423 |
<TABLE> |
| 10424 |
<TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR> |
| 10425 |
<TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR> |
| 10426 |
<TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR> |
| 10427 |
<TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR> |
| 10428 |
<TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR> |
| 10429 |
<TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR> |
| 10430 |
<TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR> |
| 10431 |
</TABLE> |
| 10432 |
|
| 10433 |
<H3><A NAME="header-colors"></A>Header Colors</H3> |
| 10434 |
|
| 10435 |
You may add color to the header fields in the MESSAGE TEXT screen. |
| 10436 |
The |
| 10437 |
<P> |
| 10438 |
<DL COMPACT> |
| 10439 |
<DT> <A NAME="header-general-color"><EM>Header-general Color</EM></A> |
| 10440 |
|
| 10441 |
<DD> may be used to color all of the headers of |
| 10442 |
the message. |
| 10443 |
</DL> |
| 10444 |
<P> |
| 10445 |
It is also possible to set the colors for specific header fields, |
| 10446 |
for example for the Subject or From fields, using the |
| 10447 |
<A HREF="#viewer-hdr-colors"><EM>viewer-hdr-colors</EM></A> |
| 10448 |
option. |
| 10449 |
<P> |
| 10450 |
For Header Colors, |
| 10451 |
there is an additional line on the configuration |
| 10452 |
screen labeled "Pattern to match". |
| 10453 |
If you leave that blank, then the whole field for that header will |
| 10454 |
always be colored. |
| 10455 |
However, if you give a pattern to match, the coloring will only take place |
| 10456 |
if there is a match for that pattern in the value of the field. |
| 10457 |
For example, if you are working on a color for the Subject header and |
| 10458 |
you fill in a pattern of "important", then only Subjects which |
| 10459 |
contain the word "important" will be colored. |
| 10460 |
For address fields like From or To, a pattern match will cause only the |
| 10461 |
addresses which match the pattern to be colored. |
| 10462 |
<P> |
| 10463 |
If the pattern you enter is a comma-separated list of patterns, then coloring |
| 10464 |
happens if any of those patterns matches. |
| 10465 |
<P> |
| 10466 |
|
| 10467 |
<H3><A NAME="keyword-colors"></A>Keyword Colors</H3> |
| 10468 |
|
| 10469 |
Sets the colors <EM>Alpine</EM> uses for Keyword fields in the MESSAGE INDEX screen. |
| 10470 |
Keywords may be displayed as part of the Subject of a message by using |
| 10471 |
the "SUBJKEY" or "SUBJKEYINIT" tokens in the |
| 10472 |
<A HREF="#index-format">Index-Format</A> option. |
| 10473 |
Keywords may also be displayed in a column of their own in the MESSAGE INDEX |
| 10474 |
screen by using the "KEY" or "KEYINIT" tokens. |
| 10475 |
<P> |
| 10476 |
For example, you might have set up a Keyword |
| 10477 |
"Work" using the |
| 10478 |
<A HREF="#keywords">Keywords</A> |
| 10479 |
option in the Setup/Config screen. |
| 10480 |
You could cause that Keyword to show up as a special color |
| 10481 |
by setting up the Keyword Color using this option, and then including it |
| 10482 |
in the MESSAGE INDEX screen using one of the tokens listed above in the |
| 10483 |
Index-Format. |
| 10484 |
<P> |
| 10485 |
|
| 10486 |
<H3><A NAME="index-line-colors"></A>Index Line Colors</H3> |
| 10487 |
|
| 10488 |
You may color whole index lines by using roles. |
| 10489 |
This isn't configured in the Setup Colors screen, but is configured in |
| 10490 |
the <A HREF="#index-color-config">Setup Rules IndexColor</A> screen. |
| 10491 |
|
| 10492 |
<H2><A NAME="index-color-config"></A>Index Line Color Configuration</H2> |
| 10493 |
|
| 10494 |
Index Line Color causes lines in the MESSAGE INDEX screen to be colored. |
| 10495 |
This action is only available if your terminal is capable of displaying |
| 10496 |
color and color display has been enabled with the |
| 10497 |
<A HREF="#color-style"><EM>Color-Style</EM></A> option. |
| 10498 |
(In PC-Alpine, color is always enabled so there is no option to turn on.) |
| 10499 |
<P> |
| 10500 |
Each rule has a "Pattern", |
| 10501 |
which is used to decide which of the rules is used; and the color which |
| 10502 |
is used if the Pattern matches a particular message. |
| 10503 |
|
| 10504 |
<H3>Rule Patterns</H3> |
| 10505 |
|
| 10506 |
In order to determine whether or not a message matches a rule the message is |
| 10507 |
compared with the rule's Pattern. |
| 10508 |
These Patterns are the same for use with Roles, Filtering, Index Coloring, |
| 10509 |
Scoring, Other Rules, and Search Rules, so are described in only one place, |
| 10510 |
"<A HREF="#patterns-section">here</A>". |
| 10511 |
|
| 10512 |
<H3>Index Line Color</H3> |
| 10513 |
|
| 10514 |
This is the color that index lines are colored when there is a matching |
| 10515 |
Pattern. |
| 10516 |
This colors the whole index line, except possibly the status letters |
| 10517 |
which may be colored separately using |
| 10518 |
the <A HREF="#color-config">Setup Kolor</A> screen. |
| 10519 |
|
| 10520 |
<H2><A NAME="role-config"></A>Role Configuration</H2> |
| 10521 |
|
| 10522 |
You may play different roles depending on who you are replying to. |
| 10523 |
For example, if you are replying to a message addressed to <EM>help-desk</EM> you |
| 10524 |
may be acting as a Help Desk Worker. |
| 10525 |
That role may require that you use a different return address and/or |
| 10526 |
a different signature. |
| 10527 |
<P> |
| 10528 |
Roles are optional. |
| 10529 |
If you set up roles they work like this: Each role has a set of |
| 10530 |
"Uses", which indicate whether or not a role is eligible to be |
| 10531 |
considered for a particular use; a "Pattern", |
| 10532 |
which is used to decide which of the eligible roles is used; and a set |
| 10533 |
of "Actions", which are taken when that role is used. |
| 10534 |
When you reply to a message, the message you are replying to is compared |
| 10535 |
with the Patterns of the roles marked as eligible for use when replying. |
| 10536 |
The comparisons start with the first eligible role and keep going until there |
| 10537 |
is a match. |
| 10538 |
If a match is found, the matching role's Actions are taken. |
| 10539 |
<P> |
| 10540 |
It is also possible to set a default role and to change that role during |
| 10541 |
your <EM>Alpine</EM> session. |
| 10542 |
When you start <EM>Alpine</EM> no default role will be set. |
| 10543 |
You may set or change the current default role by using the "D" |
| 10544 |
command in the role selection screen. |
| 10545 |
You'll see that screen while composing a message and being asked to select |
| 10546 |
a role. |
| 10547 |
An easy way to get to that screen is to use the Role Command to |
| 10548 |
compose a message. |
| 10549 |
You may find a default role useful if you normally perform the duties of one |
| 10550 |
of your roles for a while, then you switch to another role and stay in the |
| 10551 |
new role for another period of time. |
| 10552 |
It may be easier than using the Role Command to select the role each time you |
| 10553 |
compose a message. |
| 10554 |
|
| 10555 |
<H3>Role Uses</H3> |
| 10556 |
|
| 10557 |
There are three types of use to be configured; |
| 10558 |
one for Replying, one for Forwarding, and one for Composing. |
| 10559 |
These indicate whether or not you want a role to be considered when you |
| 10560 |
type the Reply, Forward, or Compose commands. |
| 10561 |
(The Role command is an alternate form of the Compose command, and it is |
| 10562 |
not affected by these settings.) |
| 10563 |
Each of these Use types has three possible values. |
| 10564 |
The value "Never" |
| 10565 |
means that the role will never be considered as a candidate for use with |
| 10566 |
the corresponding command. |
| 10567 |
For example, if you set a role's Reply Use to Never, then when you Reply to |
| 10568 |
a message, the role won't even be considered. |
| 10569 |
(That isn't quite true. If the message you are replying to matches some other |
| 10570 |
role which requires confirmation, |
| 10571 |
then there will be a ^T command available which allows you to select a role |
| 10572 |
from all of your roles, not just the reply-eligible roles.) |
| 10573 |
<P> |
| 10574 |
|
| 10575 |
The options "With confirmation" and "Without confirmation" |
| 10576 |
both mean that you do want to consider this role when using the corresponding |
| 10577 |
command. |
| 10578 |
For either of these settings the role's Pattern will |
| 10579 |
be checked to see if it matches the message. |
| 10580 |
For Reply Use, the message used to compare the Patterns with is the message |
| 10581 |
being replied to. |
| 10582 |
For Forward Use, the message used to compare the Pattern with is the message |
| 10583 |
being forwarded. |
| 10584 |
For Compose Use, there is no message, so the parts of the Pattern which depend |
| 10585 |
on a message (everything other than Current Folder Type) are ignored. |
| 10586 |
In all cases, the Current Folder is checked if defined. |
| 10587 |
If there is a match then this role will either be used without confirmation |
| 10588 |
or will be the default when confirmation is asked for, depending on |
| 10589 |
which of the two options is selected. |
| 10590 |
If confirmation is requested, you will have a chance to |
| 10591 |
choose No Role instead of the offered role, or to |
| 10592 |
change the role to any one of your other roles (with the ^T command). |
| 10593 |
|
| 10594 |
<H3>Role Patterns</H3> |
| 10595 |
|
| 10596 |
In order to determine whether or not a message matches a role the message is |
| 10597 |
compared with the Role Pattern. |
| 10598 |
These Patterns are the same for use with Roles, Filtering, Index Coloring, |
| 10599 |
Scoring, Other Rules, and Search Rules, so are described in only one place, |
| 10600 |
"<A HREF="#patterns-section">here</A>". |
| 10601 |
<P> |
| 10602 |
Since header patterns, AllText patterns, and BodyText patterns which are unset are ignored, |
| 10603 |
a role which has all header patterns unset, the AllText pattern unset, |
| 10604 |
the BodyText pattern unset, |
| 10605 |
the Score Interval unset, and the Current Folder Type set to |
| 10606 |
"Any" may be used as a default role. |
| 10607 |
It should be put last in the list of roles since the matching |
| 10608 |
starts at the beginning and proceeds until one of the roles is a match. |
| 10609 |
If no roles at all match, then <EM>Alpine</EM> will |
| 10610 |
use its regular methods of defining the role. |
| 10611 |
If you wanted to, you could define a different "default" role |
| 10612 |
for Replying, Forwarding, and Composing by setting the |
| 10613 |
"Use" fields appropriately. |
| 10614 |
|
| 10615 |
<H3>Role Actions</H3> |
| 10616 |
|
| 10617 |
Once a role match is found, the role's Actions are taken. |
| 10618 |
For each role there are several possible actions that may be defined. |
| 10619 |
They are actions to set the From address, the Reply-To address, |
| 10620 |
the Fcc, the Signature file, and the Template file. |
| 10621 |
|
| 10622 |
<H4>Initialize Settings Using Role</H4> |
| 10623 |
|
| 10624 |
This is a power user feature. |
| 10625 |
You will usually want to leave this field empty. |
| 10626 |
The value of this field is the nickname of another one of your roles. |
| 10627 |
The Action values from that other role |
| 10628 |
are used as the initial values of the Action items for this role. |
| 10629 |
If you put something in any of the action fields for this role, that will |
| 10630 |
override whatever was in the corresponding field of the initializer role. |
| 10631 |
<P> |
| 10632 |
You might use this field if the "Action" part of one of your roles |
| 10633 |
is something you want to use in more than one role. |
| 10634 |
Instead of filling in those action values again for each role, you |
| 10635 |
may give the nickname of the role where the values are filled in. |
| 10636 |
It's just a shortcut way to define Role Actions. |
| 10637 |
<P> |
| 10638 |
Here's an example to help explain how this works. |
| 10639 |
Suppose you have a role with nickname "role1" and role1 has |
| 10640 |
(among other things) |
| 10641 |
<P> |
| 10642 |
<CENTER><SAMP>Set Reply-To = The Pres <[email protected]></SAMP></CENTER> |
| 10643 |
<P> |
| 10644 |
set. |
| 10645 |
If in "role2" you set "Initialize settings using role" to |
| 10646 |
"role1", then role2 will inherit the Set Reply-To value |
| 10647 |
from role1 by default (and any of the other inheritable action values |
| 10648 |
that are set). |
| 10649 |
So if role2 had |
| 10650 |
<P> |
| 10651 |
<CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER> |
| 10652 |
<P> |
| 10653 |
defined, the Reply-To used with role2 would be "The Pres <[email protected]>" |
| 10654 |
However, if role2 had |
| 10655 |
<P> |
| 10656 |
<CENTER><SAMP>Set Reply-To = VP <[email protected]></SAMP></CENTER> |
| 10657 |
<P> |
| 10658 |
defined, then the Reply-To used with role2 would be "VP <[email protected]>" instead. |
| 10659 |
<P> |
| 10660 |
If you wish, |
| 10661 |
you may choose a nickname from your list of roles by using the |
| 10662 |
"T" command. |
| 10663 |
If the role you are using to initialize also has a role it initializes from, |
| 10664 |
then that initialization happens first. |
| 10665 |
That is, inheritance works as expected with the grandparent and |
| 10666 |
great-grandparent (and so on) roles having the expected effect. |
| 10667 |
|
| 10668 |
<H4>Set From</H4> |
| 10669 |
|
| 10670 |
This field consists of a single address which will be used as the From |
| 10671 |
address on the message you are sending. |
| 10672 |
This should be a fully-qualified address like |
| 10673 |
<P> |
| 10674 |
<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER> |
| 10675 |
<P> |
| 10676 |
or just |
| 10677 |
<P> |
| 10678 |
<CENTER><SAMP>user@domain</SAMP></CENTER> |
| 10679 |
<P> |
| 10680 |
If this is left blank, then the normal From address will be used. |
| 10681 |
|
| 10682 |
<H4>Set Reply-To</H4> |
| 10683 |
|
| 10684 |
The Reply-To address is the address used on the Reply-To line of the message |
| 10685 |
you are sending. |
| 10686 |
You don't need a Reply-To address unless it is different from the From address. |
| 10687 |
This should be a fully-qualified address like |
| 10688 |
<P> |
| 10689 |
<CENTER><SAMP>Full Name <user@domain></SAMP></CENTER> |
| 10690 |
<P> |
| 10691 |
or just |
| 10692 |
<P> |
| 10693 |
<CENTER><SAMP>user@domain</SAMP></CENTER> |
| 10694 |
<P> |
| 10695 |
If this is left blank, then there won't be a Reply-To address unless |
| 10696 |
you have configured one specially with the |
| 10697 |
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> |
| 10698 |
configuration option. |
| 10699 |
|
| 10700 |
<H4>Set Other-Hdrs</H4> |
| 10701 |
|
| 10702 |
This field gives you a way to set values for headers besides |
| 10703 |
"From" and "Reply-To". |
| 10704 |
If you want to set either of those, use the specific |
| 10705 |
"Set From" and "Set Reply-To" settings. |
| 10706 |
<P> |
| 10707 |
This field is similar to the |
| 10708 |
<A HREF="#cust-hdr"><EM>customized-hdrs</EM></A> option. |
| 10709 |
Each header you specify here must include the header tag |
| 10710 |
("To:", "Approved:", etc.) |
| 10711 |
and may optionally include a value for that header. |
| 10712 |
In order to see these headers when you compose using this role you |
| 10713 |
must use the rich header command. |
| 10714 |
Here's an example which shows how you might set the To address. |
| 10715 |
<P> |
| 10716 |
<CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER> |
| 10717 |
<P> |
| 10718 |
Headers set in this way are different from headers set with the |
| 10719 |
customized-hdrs option in that the value you give for a header here |
| 10720 |
will replace any value that already exists. |
| 10721 |
For example, if you are Replying to a message there will already be at |
| 10722 |
least one address in the To header (the address you are Replying to). |
| 10723 |
However, if you Reply using a role which sets the To header, that role's |
| 10724 |
To header value will be used instead. |
| 10725 |
The customized-hdrs headers are defaults. |
| 10726 |
<P> |
| 10727 |
Limitation: Because commas are used to separate the list of |
| 10728 |
Other Headers, it is not possible to have the value of a |
| 10729 |
header contain a comma; |
| 10730 |
nor is there currently an "escape" mechanism provided |
| 10731 |
to make this work. |
| 10732 |
|
| 10733 |
<H4>Set Fcc</H4> |
| 10734 |
|
| 10735 |
This field consists of a single folder name which will be used in |
| 10736 |
the Fcc field of the message you are sending. |
| 10737 |
You may put anything here that you would normally type into the Fcc |
| 10738 |
field from the composer. |
| 10739 |
<P> |
| 10740 |
In addition, an fcc of "" (two double quotation marks) means |
| 10741 |
no Fcc. |
| 10742 |
<P> |
| 10743 |
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding |
| 10744 |
the default value of the Fcc field. |
| 10745 |
For many roles, perhaps most, it may make more sense for you to use the |
| 10746 |
other <EM>Alpine</EM> facilities for setting the Fcc. |
| 10747 |
In particular, if you want the Fcc to depend on who you are sending the |
| 10748 |
message to then the <A HREF="#fcc-name-rule"><EM>fcc-name-rule</EM></A> |
| 10749 |
is probably more useful. |
| 10750 |
In that case, you would want to leave the Fcc field here blank. |
| 10751 |
However, if you have a role that depends on who the message you are replying |
| 10752 |
to was From, or what address that message was sent to; |
| 10753 |
then it might make sense to set the Fcc for that role here. |
| 10754 |
|
| 10755 |
<H4>Set LiteralSig</H4> |
| 10756 |
|
| 10757 |
This field contains the actual text for your signature, as opposed to |
| 10758 |
the name of a file containing your signature. |
| 10759 |
If this is defined it takes precedence over any value set in the |
| 10760 |
<EM>Set Signature</EM> field. |
| 10761 |
<P> |
| 10762 |
This is simply a different way to store the signature. |
| 10763 |
The signature is stored inside your Alpine configuration file instead of in |
| 10764 |
a separate signature file. |
| 10765 |
Tokens work the same way they do with <EM>Set Signature</EM>. |
| 10766 |
<P> |
| 10767 |
|
| 10768 |
The two character sequence \n (backslash followed by |
| 10769 |
the character n) will be used to signify a line-break in your signature. |
| 10770 |
You don't have to enter the \n, but it will be visible in the |
| 10771 |
CHANGE THIS ROLE RULE window after you are done editing the signature. |
| 10772 |
|
| 10773 |
<H4>Set Signature</H4> |
| 10774 |
|
| 10775 |
The Signature is the name of a file to be used as the signature file when |
| 10776 |
this role is being used. |
| 10777 |
If the filename is followed by a vertical bar (|) then instead |
| 10778 |
of reading the contents of the file the file is assumed to be a |
| 10779 |
program which will produce the text to be used on its standard output. |
| 10780 |
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>, |
| 10781 |
but the rest of the processing works as if the contents came from a file. |
| 10782 |
|
| 10783 |
<P> |
| 10784 |
Signature files may be stored remotely on an IMAP server. |
| 10785 |
In order to do that you just give the file a remote name. |
| 10786 |
This works just like the regular |
| 10787 |
<A HREF="#sig-file">signature-file</A> |
| 10788 |
option which is configured from the Setup/Configuration screen. |
| 10789 |
A remote signature file name might look like: |
| 10790 |
<P> |
| 10791 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER> |
| 10792 |
<P> |
| 10793 |
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try |
| 10794 |
<P> |
| 10795 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/sig3</SAMP></CENTER> |
| 10796 |
<P> |
| 10797 |
Once you have named the remote signature file you create its |
| 10798 |
contents by using the "F" "editFile" command when the |
| 10799 |
cursor is on the "Set Signature" |
| 10800 |
line of the role editor. |
| 10801 |
|
| 10802 |
<P> |
| 10803 |
Besides containing regular text, a signature file may also |
| 10804 |
contain (or a signature program may produce) tokens which are replaced with text |
| 10805 |
which depends on the message you are replying to or forwarding. |
| 10806 |
The tokens all look like _word_ (a word surrounded by underscores). |
| 10807 |
For example, if the token |
| 10808 |
<P> |
| 10809 |
<CENTER><SAMP>_DATE_</SAMP></CENTER> |
| 10810 |
<P> |
| 10811 |
is included in the text of the signature file, then when you reply to |
| 10812 |
or forward a message, the token will be replaced with the actual date |
| 10813 |
the message you are replying to or forwarding was sent. |
| 10814 |
<P> |
| 10815 |
If you use a role which has a signature file for a plain composition |
| 10816 |
(that is, not a reply or forward) then there is no original message, so |
| 10817 |
any tokens which depend on the message will be replaced with nothing. |
| 10818 |
So if you want a signature file to be useful for new compositions it |
| 10819 |
shouldn't include any of the tokens which depend on the message being |
| 10820 |
replied to or forwarded. |
| 10821 |
<P> |
| 10822 |
The list of available tokens is |
| 10823 |
<A HREF="#index-tokens">here</A>. |
| 10824 |
<P> |
| 10825 |
Actually, for the adventurous, there is a way to conditionally include text based |
| 10826 |
on whether or not a token would result in specific replacement text. |
| 10827 |
For example, you could include some text based on whether or not |
| 10828 |
the _NEWS_ token would result in any newsgroups if it was used. |
| 10829 |
It's explained in detail |
| 10830 |
<A HREF="#reply-token-conditionals">here</A>. |
| 10831 |
<P> |
| 10832 |
In the very unlikely event that you want to include a literal token in |
| 10833 |
a signature file, you must precede it with a backslash character. |
| 10834 |
For example, to include the literal text _DATE_ you must actually use |
| 10835 |
\_DATE_. |
| 10836 |
It is not possible to have a literal backslash followed by an expanded token. |
| 10837 |
<P> |
| 10838 |
A blank field here means that <EM>Alpine</EM> will use its normal rules for deciding |
| 10839 |
which file (if any) to use for the signature file. |
| 10840 |
|
| 10841 |
<H4>Set Template</H4> |
| 10842 |
|
| 10843 |
A Template is the name of a file to be included in the message when this |
| 10844 |
role is being used. |
| 10845 |
The template file is a file which is included at the top of the message you |
| 10846 |
are composing. |
| 10847 |
<P> |
| 10848 |
If the filename is followed by a vertical bar (|) then instead |
| 10849 |
of reading the contents of the file the file is assumed to be a |
| 10850 |
program which will produce the text to be used on its standard output. |
| 10851 |
The program can't have any arguments and doesn't receive any input from <EM>Alpine</EM>, |
| 10852 |
but the rest of the processing works as if the contents came from a file. |
| 10853 |
<P> |
| 10854 |
Template files may be stored remotely on an IMAP server. |
| 10855 |
In order to do that you just give the file a remote name. |
| 10856 |
This works just like the regular |
| 10857 |
<A HREF="#sig-file">signature-file</A> |
| 10858 |
option which is configured from the Setup/Configuration screen. |
| 10859 |
A remote template file name might look like: |
| 10860 |
<P> |
| 10861 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER> |
| 10862 |
<P> |
| 10863 |
or, if you have an SSL-capable version of <EM>Alpine</EM>, you might try |
| 10864 |
<P> |
| 10865 |
<CENTER><SAMP>{myimaphost.myschool.k12.wa.us/user=loginname/ssl}mail/templ3</SAMP></CENTER> |
| 10866 |
<P> |
| 10867 |
Once you have named the remote template file you create its |
| 10868 |
contents by using the "F" "editFile" command when the |
| 10869 |
cursor is on the "Set Template" |
| 10870 |
line of the role editor. |
| 10871 |
<P> |
| 10872 |
Besides containing regular text, a template file may also |
| 10873 |
contain (or a template file program may produce) tokens which are replaced with text |
| 10874 |
which depends on the message you are replying to or forwarding. |
| 10875 |
The tokens all look like _word_ (a word surrounded by underscores). |
| 10876 |
For example, if the token |
| 10877 |
<P> |
| 10878 |
<CENTER><SAMP>_DATE_</SAMP></CENTER> |
| 10879 |
<P> |
| 10880 |
is included in the text of the template file, then when you reply to |
| 10881 |
or forward a message, the token will be replaced with the actual date |
| 10882 |
the message you are replying to or forwarding was sent. |
| 10883 |
<P> |
| 10884 |
If you use a role which has a template file for a plain composition |
| 10885 |
(that is, not a reply or forward) then there is no original message, so |
| 10886 |
any tokens which depend on the message will be replaced with nothing. |
| 10887 |
So if you want a template file to be useful for new compositions it |
| 10888 |
shouldn't include any of the tokens which depend on the message being |
| 10889 |
replied to or forwarded. |
| 10890 |
<P> |
| 10891 |
The list of available tokens is |
| 10892 |
<A HREF="#index-tokens">here</A>. |
| 10893 |
<P> |
| 10894 |
Actually, for the adventurous, there is a way to conditionally include text based |
| 10895 |
on whether or not a token would result in specific replacement text. |
| 10896 |
For example, you could include some text based on whether or not |
| 10897 |
the _NEWS_ token would result in any newsgroups if it was used. |
| 10898 |
It's explained in detail |
| 10899 |
<A HREF="#reply-token-conditionals">here</A>. |
| 10900 |
<P> |
| 10901 |
In the very unlikely event that you want to include a literal token in |
| 10902 |
a template file, you must precede it with a backslash character. |
| 10903 |
For example, to include the literal text _DATE_ you must actually use |
| 10904 |
\_DATE_. |
| 10905 |
It is not possible to have a literal backslash followed by an expanded token. |
| 10906 |
<P> |
| 10907 |
A blank field here means that <EM>Alpine</EM> will not use a template file when |
| 10908 |
this role is being used. |
| 10909 |
|
| 10910 |
<H4>Use SMTP Server</H4> |
| 10911 |
|
| 10912 |
If this field has a value, then it will be used as the SMTP server |
| 10913 |
to send mail when this role is being used (unless the SMTP server variable |
| 10914 |
is set in the system-wide fixed configuration file). |
| 10915 |
It has the same semantics as the |
| 10916 |
<A HREF="#smtp-server"><EM>smtp-server</EM></A> |
| 10917 |
variable in the Setup/Config screen. |
| 10918 |
When you postpone the composition this SMTP server list will be saved |
| 10919 |
with the postponed composition and it cannot be changed later. |
| 10920 |
Because of that, you may want to make this a list of SMTP servers |
| 10921 |
with the preferred server at the front of the list and alternate servers |
| 10922 |
later in the list. |
| 10923 |
|
| 10924 |
<P> |
| 10925 |
If any of the actions are left unset, then the action depends on what |
| 10926 |
is present in the "Initialize settings using role" field. |
| 10927 |
If you've listed the nickname of another one of your roles there, then the |
| 10928 |
corresponding action from that role will be used here. |
| 10929 |
If that action is also blank, or if there is no nickname specified, |
| 10930 |
then <EM>Alpine</EM> will do whatever it normally does to set these actions. |
| 10931 |
This depends on other configuration options and features you've set. |
| 10932 |
|
| 10933 |
<H2><A NAME="filter-config"></A>Filtering Configuration</H2> |
| 10934 |
|
| 10935 |
The software which actually delivers mail (the stuff that happens |
| 10936 |
before <EM>Alpine</EM> is involved) for you is in a better position to do mail filtering |
| 10937 |
than <EM>Alpine</EM> itself. |
| 10938 |
If possible, you may want to look into using that sort of mail filtering to |
| 10939 |
deliver mail to different folders, delete it, or forward it. |
| 10940 |
However, if you'd like <EM>Alpine</EM> to help with this, <EM>Alpine</EM>'s filtering is for you. |
| 10941 |
<P> |
| 10942 |
Filtering is a way to automatically move certain messages from one folder |
| 10943 |
to another or to delete messages. |
| 10944 |
It can also be used to set message status bits (Important, Deleted, New, |
| 10945 |
Answered). |
| 10946 |
<EM>Alpine</EM> doesn't have the ability to forward mail to another address. |
| 10947 |
<P> |
| 10948 |
Each filtering rule has a "Pattern" and a "Filter Action". |
| 10949 |
When a folder is opened, when new mail arrives in an open folder, or |
| 10950 |
when mail is Expunged from a folder; each |
| 10951 |
message is compared with the Patterns of your filtering rules. |
| 10952 |
The comparisons start with the first rule and keep going until there |
| 10953 |
is a match. |
| 10954 |
If a match is found, the message may be deleted or moved, depending on |
| 10955 |
the setting of the Filter Action. |
| 10956 |
If the message is not deleted, it may have its status altered. |
| 10957 |
<P> |
| 10958 |
For efficiency, each message is usually only checked once. |
| 10959 |
When new mail arrives, the new messages are checked but not the old. |
| 10960 |
There are some exceptions to this rule. |
| 10961 |
The expunge command will cause all messages to be rechecked, as will |
| 10962 |
editing of the filtering rules. |
| 10963 |
|
| 10964 |
<P> |
| 10965 |
<EM>NOTE:</EM> |
| 10966 |
When setting up a Pattern used to delete messages, |
| 10967 |
it is recommended that you test the Pattern first with a "Move" |
| 10968 |
folder specified in |
| 10969 |
case unintended matches occur. Messages that are deleted will be removed |
| 10970 |
from the folder and <EM>unrecoverable</EM> from within <EM>Alpine</EM> after the |
| 10971 |
next Expunge command or once the folder being filtered has been closed. |
| 10972 |
|
| 10973 |
<H3>Filter Patterns</H3> |
| 10974 |
|
| 10975 |
In order to determine whether or not a message matches a filter the message is |
| 10976 |
compared with the Filter's Pattern. |
| 10977 |
These Patterns are the same for use with Roles, Filtering, Index Coloring, |
| 10978 |
Scoring, Other Rules, and Search Rules, so are described in only one place, |
| 10979 |
"<A HREF="#patterns-section">here</A>". |
| 10980 |
<P> |
| 10981 |
Since filtering is a potentially destructive action, if you have a filtering |
| 10982 |
Pattern with nothing other than Current Folder Type set, that filtering |
| 10983 |
rule is ignored. |
| 10984 |
|
| 10985 |
<H3>Filter Actions</H3> |
| 10986 |
|
| 10987 |
Once a filter match is found for a particular message, there are some actions |
| 10988 |
which may be taken. |
| 10989 |
First, the message may have its status changed. |
| 10990 |
This is the same message status that you can manipulate manually using the |
| 10991 |
Flag Command. |
| 10992 |
There are four elements of message status that you can control. |
| 10993 |
You can set or clear the Important status, the New status, the Deleted |
| 10994 |
status, and the Answered status. |
| 10995 |
Of course, if the filter is going to delete the message, |
| 10996 |
then there is no point in setting message status. |
| 10997 |
You may also set or clear user-defined |
| 10998 |
<A HREF="#keywords">keywords</A> for a message. |
| 10999 |
<P> |
| 11000 |
Second, the filter may delete or move the message. |
| 11001 |
Deleting the message marks it Deleted and removes it from view. |
| 11002 |
It is effectively gone forever (though it technically is still there until |
| 11003 |
the next expunge command, which may happen implicitly). |
| 11004 |
Moving the message moves it from the open folder into the folder |
| 11005 |
listed on the "Folder List" line of the filter configuration. |
| 11006 |
If you list more than one folder name (separated by commas) then the message |
| 11007 |
will be copied to each of those folders. |
| 11008 |
In any case, if "Delete" or "Move" is set then the |
| 11009 |
message is removed from the current folder. |
| 11010 |
If you just want to set the messages status without deleting it from |
| 11011 |
the folder, then set the filter action to |
| 11012 |
"Just Set Message Status". |
| 11013 |
<P> |
| 11014 |
(There is no way to do a Copy instead of a Move, due to the difficulties |
| 11015 |
involved in keeping track of whether or not a message has |
| 11016 |
already been copied by a previous <EM>Alpine</EM> session.) |
| 11017 |
|
| 11018 |
<H4><A NAME="move-only-if-not-deleted"></A>Move-only-if-not-deleted option</H4> |
| 11019 |
|
| 11020 |
If you have specified a Move to Folder to filter messages into, then this |
| 11021 |
option has an effect. |
| 11022 |
If this option is set then messages will only be moved into the specified folder |
| 11023 |
if they aren't already marked deleted. |
| 11024 |
This might be useful if you have more than one <EM>Alpine</EM> session running |
| 11025 |
simultaneously and you don't want messages to be filtered into a folder |
| 11026 |
more than once. |
| 11027 |
This method is not foolproof. |
| 11028 |
There may be cases where a message gets marked deleted and so it is never |
| 11029 |
filtered into the folder. |
| 11030 |
For example, if you deleted it in another <EM>Alpine</EM> or |
| 11031 |
another mail program that didn't know about the filtering rule. |
| 11032 |
<P> |
| 11033 |
This option has no effect if the Filter Action is not set to Move. |
| 11034 |
|
| 11035 |
<H4><A NAME="dont-quit-even-if-rule-matches"></A>Dont-quit-even-if-rule-matches option</H4> |
| 11036 |
|
| 11037 |
If this option is set then this is a non-terminating rule. |
| 11038 |
Usually, for each message, <EM>Alpine</EM> searches through the filter rules until |
| 11039 |
a match is found and then it performs the action associated with that rule. |
| 11040 |
Rules following the match are not considered. |
| 11041 |
If this option is set then the search for matches will continue at the next |
| 11042 |
rule. |
| 11043 |
<P> |
| 11044 |
If a non-terminating rule matches then the actions associated with |
| 11045 |
that rule, except for any implied deletion of the message, are performed |
| 11046 |
before the match for the next rule is checked. |
| 11047 |
For example, if the non-terminating rule sets the Important status, then that |
| 11048 |
status will be set when the next rule is considered. |
| 11049 |
However, if the non-terminating rule Moves the message, the message will |
| 11050 |
actually be copied instead of copied and deleted so that it is still there |
| 11051 |
for the next rule. |
| 11052 |
A moved message is deleted after all the relevant rules have been checked. |
| 11053 |
The name of the "Move" action is confusing in this case because |
| 11054 |
a single message can be moved to more than one folder. |
| 11055 |
It turns the Move into a Copy instead, but it is still followed by a deletion |
| 11056 |
at the end. |
| 11057 |
<P> |
| 11058 |
This option may be useful if you want to have a single message filtered to |
| 11059 |
two different folders because it matches two different Patterns. |
| 11060 |
For example, suppose you normally filter messages to a particular mailing |
| 11061 |
list into one folder, and messages addressed directly to you into a second |
| 11062 |
folder. |
| 11063 |
If a message is sent to both you and the list (and you can tell that by |
| 11064 |
looking at the headers of the message) this option may give you a convenient |
| 11065 |
way to capture a copy to each folder. |
| 11066 |
(It may also cause you to capture two copies to each folder, |
| 11067 |
depending on whether your mail system delivers one or two copies of the |
| 11068 |
message to you and on how the list works.) |
| 11069 |
|
| 11070 |
<H2><A NAME="scoring-config"></A>Scoring Configuration</H2> |
| 11071 |
|
| 11072 |
Most people will not use scores at all, but if you do use them, here's how |
| 11073 |
they work in Alpine. |
| 11074 |
Using this screen, you may define Scoring rules. |
| 11075 |
The score for a message is calculated by looking at every Score rule defined |
| 11076 |
and adding up the Score Values for the ones which match the message. |
| 11077 |
If there are no matches for a message, it has a score of zero. |
| 11078 |
Message scores may be used a couple of ways in Alpine. |
| 11079 |
|
| 11080 |
<H3>Sorting by Score</H3> |
| 11081 |
|
| 11082 |
One of the methods you may use to sort message indexes is to sort by |
| 11083 |
score. |
| 11084 |
The scores of all the messages in a folder will be calculated and then |
| 11085 |
the index will be ordered by placing the messages in order of ascending or |
| 11086 |
descending score. |
| 11087 |
|
| 11088 |
<H3>Scores for use in Patterns</H3> |
| 11089 |
|
| 11090 |
The Patterns used for Roles, Index Line Coloring, and Filtering have a |
| 11091 |
category labeled "Score Interval". |
| 11092 |
When a message is being compared with a Pattern to check for a match, if |
| 11093 |
the Score Interval is set only messages which have a score somewhere in |
| 11094 |
the interval are a match. |
| 11095 |
|
| 11096 |
<H3>Scoring Rule Patterns</H3> |
| 11097 |
|
| 11098 |
In order to determine whether or not a message matches a scoring rule |
| 11099 |
the message is compared with the rule's Pattern. |
| 11100 |
These Patterns are the same for use with Roles, Filtering, Index Coloring, |
| 11101 |
Scoring, Other Rules, and Search Rules, so are described in only one place, |
| 11102 |
"<A HREF="#patterns-section">here</A>". |
| 11103 |
|
| 11104 |
<P> |
| 11105 |
Actually, Scoring rule Patterns are slightly different from the other types of |
| 11106 |
Patterns because Scoring rule Patterns don't contain a Score Interval. |
| 11107 |
In other words, when calculating the score for a message, which is done |
| 11108 |
by looking at the Scoring rule Patterns, scores aren't used. |
| 11109 |
|
| 11110 |
<H3>Score Value</H3> |
| 11111 |
|
| 11112 |
This is the value that will be added to the score for a message if the |
| 11113 |
rule's Pattern is a match. |
| 11114 |
Each individual Score Value is an integer between -100 and 100, and the |
| 11115 |
values from matching rules are added together to get a message's score. |
| 11116 |
There is also a way to extract the value from a particular header of each |
| 11117 |
message. See the help text for Score Value for further information. |
| 11118 |
|
| 11119 |
<H2><A NAME="other-config"></A>Other Rules Configuration</H2> |
| 11120 |
|
| 11121 |
Using this screen, you may define configuration Rules which don't fit |
| 11122 |
nicely into the other Rules categories. |
| 11123 |
|
| 11124 |
<H3>Other Rule Patterns</H3> |
| 11125 |
|
| 11126 |
Other Rules are a little different from the rest of the Rules because |
| 11127 |
they depend only on the current folder, and not on a particular message. |
| 11128 |
In order to determine whether or not a rule's actions should be applied |
| 11129 |
the current folder is compared with the rule's Pattern, which consists |
| 11130 |
of only the Current Folder Type. |
| 11131 |
Current Folder Type works the same for Other Rules as it does for Roles, |
| 11132 |
Filtering, Index Coloring, and Scoring. |
| 11133 |
Keep in mind that the only part of the Pattern which applies to Other |
| 11134 |
Rules is the Current Folder Type when looking at the description of |
| 11135 |
Patterns given |
| 11136 |
"<A HREF="#patterns-section">here</A>". |
| 11137 |
|
| 11138 |
<H3>Other Rule Actions</H3> |
| 11139 |
|
| 11140 |
Once a pattern match is found, the rule's Actions are taken. |
| 11141 |
Neither of the following two rule's depends on a message for its match. |
| 11142 |
That means that all the parts of the Pattern which depend on matching an |
| 11143 |
attribute of a message are ignored. |
| 11144 |
So the only part of the Pattern that matters for these Actions is |
| 11145 |
the Current Folder Type. |
| 11146 |
|
| 11147 |
<H4>Set Sort Order</H3> |
| 11148 |
|
| 11149 |
When you enter a new folder, these rules will be checked to see if you |
| 11150 |
have set a sort order which is different from your default sort order. |
| 11151 |
The default is set in the Setup/Config screen with |
| 11152 |
the <A HREF="#sort-key">Sort-Key</A> option. |
| 11153 |
If the Sort Order action is set, then the folder will be displayed sorted in |
| 11154 |
that sort order instead of in the default order. |
| 11155 |
<P> |
| 11156 |
A possible point of confusion arises when you change the configuration |
| 11157 |
of the Sort Order for the currently open folder. |
| 11158 |
The folder will normally be re-sorted when you go back to viewing the |
| 11159 |
index. |
| 11160 |
However, if you have manually sorted the folder with the |
| 11161 |
Sort command, it will not be re-sorted. |
| 11162 |
|
| 11163 |
<H4>Set Index Format</H3> |
| 11164 |
|
| 11165 |
When you enter a new folder, these rules will be checked to see if you |
| 11166 |
have set an Index Format which is different from your default Index Format, |
| 11167 |
which is set with the |
| 11168 |
<A HREF="#index-format"><EM>Index-Format</EM></A> option. |
| 11169 |
If so, the index will be displayed with this format instead of the default. |
| 11170 |
|
| 11171 |
<H4>Set Startup Rule</H4> |
| 11172 |
|
| 11173 |
When you enter a new folder, these rules will be checked to see if you |
| 11174 |
have set a startup rule which is different from the default startup rule. |
| 11175 |
The default for incoming folders is set in the Setup/Config screen with |
| 11176 |
the "incoming-startup-rule" option. |
| 11177 |
The default for folders other than INBOX that are not part of your |
| 11178 |
incoming collection |
| 11179 |
(see <A HREF="#enable-incoming-folders">enable-incoming-folders</A> feature) |
| 11180 |
is to start with the last message in the folder. |
| 11181 |
If the Startup Rule is set to something other than "default", |
| 11182 |
then the rule will determine which message will be the current message when |
| 11183 |
the folder is first opened. |
| 11184 |
<P> |
| 11185 |
The various startup rule possibilities work the same here as they do in |
| 11186 |
the incoming collection, except that the folder can be any specific |
| 11187 |
folder or any folder type. |
| 11188 |
|
| 11189 |
<H2><A NAME="search-rules-config"></A>Search Rules Configuration</H2> |
| 11190 |
|
| 11191 |
One of the commands that becomes available when that feature is turned on |
| 11192 |
is the "; Select" command, which is used in the MESSAGE INDEX |
| 11193 |
screen to select a set of messages. |
| 11194 |
One way of selecting messages is to use a Rule. |
| 11195 |
All of the messages which match (or don't match if you wish) |
| 11196 |
a Rule's Pattern will be selected. |
| 11197 |
<P> |
| 11198 |
Any of your Rules may be used for this purpose. |
| 11199 |
You might already have Rules set up for filtering, index line color, scores, or roles; |
| 11200 |
and you may use any of those Rules with the Select command. |
| 11201 |
However, you might find it more convenient to set up a separate set of Rules |
| 11202 |
just for this purpose without having to worry about what other effects |
| 11203 |
they may cause. |
| 11204 |
That is the purpose of these Select Rules. |
| 11205 |
|
| 11206 |
<H3>Rule Patterns</H3> |
| 11207 |
|
| 11208 |
In order to determine whether or not a message is selected by a rule the |
| 11209 |
message is |
| 11210 |
compared with the rule's Pattern. |
| 11211 |
These Patterns are the same for use with Roles, Filtering, Index Coloring, |
| 11212 |
Scoring, Other Rules, and Search Rules, so are described in only one place, |
| 11213 |
"<A HREF="#patterns-section">here</A>". |
| 11214 |
<P> |
| 11215 |
There is no action associated with these Search Rules. |
| 11216 |
Only their Patterns are used. |
| 11217 |
|
| 11218 |
<H2><A NAME="patterns-section"></A>Patterns</H2> |
| 11219 |
|
| 11220 |
Patterns are used with Roles, Filtering, Index Coloring, |
| 11221 |
Scoring, Other Rules, and Search Rules. |
| 11222 |
Patterns are compared with a message to see if there is a match. |
| 11223 |
For Filtering, the messages being checked are all the messages in the |
| 11224 |
folder, one at a time. |
| 11225 |
For Index Line Coloring, each message that is visible on the screen is |
| 11226 |
checked for matches with the Index Coloring Patterns. |
| 11227 |
Roles are used with the Reply, Forward, and Compose commands. |
| 11228 |
For Reply, the message used to compare the Pattern with is the message |
| 11229 |
being replied to; |
| 11230 |
for Forward, the message used to compare the Pattern with is the message |
| 11231 |
being forwarded; |
| 11232 |
and for Compose, there is no message, so the parts of the Pattern which depend |
| 11233 |
on a message (everything other than Current Folder Type and the |
| 11234 |
Beginning of Month and Year) |
| 11235 |
are not used. |
| 11236 |
Only the Current Folder Type matters for Compose (plus the Beginning of |
| 11237 |
Month or Year, which you wouldn't usually use for a Role). |
| 11238 |
For Scoring, the message being scored is compared with all of the Score |
| 11239 |
Patterns, and the Score Values from the ones that match are added together to |
| 11240 |
get the message's score. |
| 11241 |
For Other Rules, there is no message. Only the Current Folder Type is checked |
| 11242 |
for Other Rules. |
| 11243 |
<P> |
| 11244 |
Each Pattern has several possible parts, all of which are optional. |
| 11245 |
In order for there to be a match, <EM>ALL</EM> of the |
| 11246 |
<EM>defined</EM> parts of the Pattern must match the message. |
| 11247 |
If a part is not defined it is considered a match. |
| 11248 |
For example, if the To pattern is not defined it will be |
| 11249 |
displayed as |
| 11250 |
<P> |
| 11251 |
<CENTER>To pattern = <No Value Set></CENTER> |
| 11252 |
<P> |
| 11253 |
That is considered a match because it is not defined. |
| 11254 |
This means that the Pattern with nothing defined is a match if the |
| 11255 |
Current Folder Type matches, but there is an exception. |
| 11256 |
Because filtering is a potentially destructive action, filtering Patterns |
| 11257 |
with nothing other than Current Folder Type defined are ignored. |
| 11258 |
If you really want a filtering Pattern to match all messages (subject to |
| 11259 |
Current Folder Type) the best way to do it is to define a Score interval |
| 11260 |
which includes all possible scores. |
| 11261 |
This would be the score interval <SAMP>(-INF,INF)</SAMP>. |
| 11262 |
This can be used even if you haven't defined any rules to Set Scores. |
| 11263 |
<P> |
| 11264 |
There are six predefined header patterns called the To, From, Sender, Cc, News, |
| 11265 |
and Subject patterns. |
| 11266 |
Besides those six predefined header patterns, you may add |
| 11267 |
additional header patterns with header fieldnames of your choosing. |
| 11268 |
You add an extra header pattern by placing the cursor on one of the |
| 11269 |
patterns while in the role editor and using the "eXtraHdr" command. |
| 11270 |
The Recip pattern is a header pattern which stands for Recipient (To OR Cc) |
| 11271 |
and the Partic pattern is a header pattern which stands for |
| 11272 |
Participant (From OR To OR Cc). |
| 11273 |
(Defining the Recip pattern does not have the same effect as defining both |
| 11274 |
the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.) |
| 11275 |
Similar to the header patterns are the AllText pattern and the BodyText pattern. |
| 11276 |
Instead of comparing this pattern's text against only the contents of |
| 11277 |
a particular header field, the text for the AllText pattern is compared |
| 11278 |
with text anywhere in the message's header or body, and the text for the |
| 11279 |
BodyText pattern is compared with text anywhere in the message's body. |
| 11280 |
<P> |
| 11281 |
Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the |
| 11282 |
"!" "toggle NOT" command. |
| 11283 |
You can tell that <EM>NOT</EM> has been turned on by looking for the character |
| 11284 |
"!" at the beginning of the pattern line. |
| 11285 |
When the "!" is present, it reverses the meaning of the match. |
| 11286 |
That is, if the pattern matches then it is considered to NOT be a match, and |
| 11287 |
if it does not match it is considered to be a match. |
| 11288 |
<P> |
| 11289 |
Don't make the mistake of putting the "!" in the data field for |
| 11290 |
a pattern. |
| 11291 |
For example, if you type the characters "!urgent" into the Subject |
| 11292 |
pattern, the pattern will look like: |
| 11293 |
<P> |
| 11294 |
<PRE> |
| 11295 |
Subject pattern = !urgent |
| 11296 |
</PRE> |
| 11297 |
<P> |
| 11298 |
This means you want to match the 7 character sequence "!urgent". |
| 11299 |
In order to match messages which do not have "urgent" in |
| 11300 |
their Subject field, first type the characters "urgent" followed |
| 11301 |
by carriage return for the value of the Subject pattern, then negate it |
| 11302 |
by typing the "!" command. |
| 11303 |
It should look like |
| 11304 |
<P> |
| 11305 |
<PRE> |
| 11306 |
! Subject pattern = urgent |
| 11307 |
</PRE> |
| 11308 |
<P> |
| 11309 |
The contents of each of these header patterns (or the AllText or BodyText patterns) may |
| 11310 |
be a complete email address, part of an address, or a random set of |
| 11311 |
characters to match against. |
| 11312 |
It may also be a list of such patterns, which means you |
| 11313 |
are looking for a match against the first pattern in the list <EM>OR</EM> |
| 11314 |
the second pattern <EM>OR</EM> the third and so on. |
| 11315 |
For example, a Subject pattern equal to |
| 11316 |
<P> |
| 11317 |
<PRE> |
| 11318 |
Subject pattern = urgent |
| 11319 |
emergency |
| 11320 |
alert |
| 11321 |
</PRE> |
| 11322 |
<P> |
| 11323 |
would match all messages with a subject which contained at least one |
| 11324 |
of those words. |
| 11325 |
It would also match subjects containing the words "alerts" or |
| 11326 |
"Urgently". |
| 11327 |
<P> |
| 11328 |
The same example with "NOT" turned on would be |
| 11329 |
<P> |
| 11330 |
<PRE> |
| 11331 |
! Subject pattern = urgent |
| 11332 |
emergency |
| 11333 |
alert |
| 11334 |
</PRE> |
| 11335 |
<P> |
| 11336 |
which would match all messages with a subject which did NOT contain any of |
| 11337 |
those words. |
| 11338 |
You can use the "Add Value" command to add new words to the list, |
| 11339 |
or you can enter them as a comma-separated list. |
| 11340 |
<P> |
| 11341 |
(It is not possible to specify two patterns which must <EM>BOTH</EM> be |
| 11342 |
present for a match. |
| 11343 |
It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM> |
| 11344 |
pattern2 must be present, |
| 11345 |
and that is exactly what using a list does.) |
| 11346 |
<P> |
| 11347 |
The "Current Folder Type" and the "Score Interval" are |
| 11348 |
also part of the Pattern, although the "Score Interval" is not used |
| 11349 |
when checking for matches for Scoring. |
| 11350 |
There are five similar settings which relate to the status of the message. |
| 11351 |
These settings rely on the message being New or not, Deleted or not, |
| 11352 |
Answered or not, Important or not, and Recent or not. |
| 11353 |
There are also some other miscellaneous settings. |
| 11354 |
The first is the Age of the message in days. |
| 11355 |
Another is the Size of the message in bytes. |
| 11356 |
The third is a setting which detects whether or not the Subject of a |
| 11357 |
message contains raw 8-bit characters (unencoded characters with the most |
| 11358 |
significant bit set). |
| 11359 |
There is a setting which detects whether or not this is the first time |
| 11360 |
<EM>Alpine</EM> has been run this month (doesn't depend on individual messages), |
| 11361 |
and another which detects whether or not this is the first time <EM>Alpine</EM> has |
| 11362 |
been run this year. |
| 11363 |
Other parts of the Pattern detect whether or not the From address of a |
| 11364 |
message appears in your address book, whether or not certain keywords |
| 11365 |
are set for a message, and whether or not certain character sets are |
| 11366 |
used in a message. |
| 11367 |
|
| 11368 |
<H3>Parts of a Pattern</H3> |
| 11369 |
|
| 11370 |
<H4>Header patterns</H4> |
| 11371 |
|
| 11372 |
A header pattern is simply text which is searched for in the corresponding |
| 11373 |
header field. |
| 11374 |
For example, if a Pattern has a From header pattern with the value |
| 11375 |
"@company.com", then only messages which have a From header |
| 11376 |
which contains the text "@company.com" will be possible |
| 11377 |
matches. |
| 11378 |
Matches don't have to be exact. |
| 11379 |
For example, if the relevant field of a message contains the text |
| 11380 |
"mailbox@domain" somewhere |
| 11381 |
in it, then header patterns of "box", or "x@d", or |
| 11382 |
"mailbox@domain" are all matches. |
| 11383 |
<P> |
| 11384 |
All parts of the Pattern must match so, for example, |
| 11385 |
if a message matches a defined |
| 11386 |
From pattern, it still must be checked against the other parts of the |
| 11387 |
Pattern which have been defined. |
| 11388 |
The To header pattern is a slightly special case. |
| 11389 |
If the message being checked has a Resent-To header |
| 11390 |
and the feature <A HREF="#use-resent-to-in-rules">Use-Resent-To-in-Rules</A> is turned on, the addresses |
| 11391 |
there are used in place of the addresses in the To header. |
| 11392 |
This is only true for the To header. |
| 11393 |
Resent-cc and Resent-From headers are never used unless you add them |
| 11394 |
with the eXtraHdrs command. |
| 11395 |
<P> |
| 11396 |
The meaning of a header pattern may be negated with the |
| 11397 |
"!" "toggle NOT" command. |
| 11398 |
You can tell that <EM>NOT</EM> has been turned on by looking for the character |
| 11399 |
"!" at the beginning of the pattern line. |
| 11400 |
It would look something like |
| 11401 |
<P> |
| 11402 |
<PRE> |
| 11403 |
! From pattern = [email protected] |
| 11404 |
</PRE> |
| 11405 |
<P> |
| 11406 |
When the "!" is present, it reverses the meaning of the match. |
| 11407 |
<P> |
| 11408 |
If you want to check for the presence of a header field but don't care |
| 11409 |
about its value, then |
| 11410 |
the empty pattern which you get by entering a pair of |
| 11411 |
double quotes ("") should match any message which |
| 11412 |
has the corresponding header field. |
| 11413 |
|
| 11414 |
<H4><A NAME="pattern_alltext">AllText patterns</A></H4> |
| 11415 |
|
| 11416 |
AllText patterns are just like header patterns except that the text is |
| 11417 |
searched for anywhere in the message's headers or body, not just in the |
| 11418 |
contents of a particular header field. |
| 11419 |
<P> |
| 11420 |
|
| 11421 |
<H4><A NAME="pattern_bodytext">BodyText patterns</A></H3> |
| 11422 |
|
| 11423 |
BodyText patterns are just like header patterns except that the text is |
| 11424 |
searched for anywhere in the message's body, not just in the |
| 11425 |
contents of a particular header field. |
| 11426 |
<P> |
| 11427 |
|
| 11428 |
If there is more than one header pattern or AllText pattern or BodyText pattern |
| 11429 |
for which you want to take the |
| 11430 |
same action there is a shorthand notation which may be used. |
| 11431 |
Any of these patterns may be a list of patterns instead of |
| 11432 |
just a single pattern. |
| 11433 |
If any one of the patterns in the list matches the message |
| 11434 |
then it is considered a match. |
| 11435 |
For example, if "company1" and "company2" both required |
| 11436 |
you to use the same role when replying to messages, you might have |
| 11437 |
a To pattern which looks like |
| 11438 |
<P> |
| 11439 |
<PRE> |
| 11440 |
To pattern = company1.com |
| 11441 |
company2.com |
| 11442 |
</PRE> |
| 11443 |
<P> |
| 11444 |
This means that if the mail you are replying to was addressed to |
| 11445 |
either "[email protected]" or "[email protected]", |
| 11446 |
then this Pattern is a match and the same actions will be taken. |
| 11447 |
<P> |
| 11448 |
The meaning of an AllText or BodyText pattern may be negated with the |
| 11449 |
"!" "toggle NOT" command. |
| 11450 |
You can tell that <EM>NOT</EM> has been turned on by looking for the character |
| 11451 |
"!" at the beginning of the pattern line. |
| 11452 |
When the "!" is present, it reverses the meaning of the match. |
| 11453 |
<P> |
| 11454 |
A technicality: Since comma is the character used to separate multiple values |
| 11455 |
in any of the fields which may have multiple values (such as header patterns, |
| 11456 |
AllText patterns, BodyText patterns, keywords, folder lists, and so on), |
| 11457 |
you must escape comma with a |
| 11458 |
backslash (\) if you want to include a literal comma in one of those fields. |
| 11459 |
In other words, if you type a backslash followed by a comma it will |
| 11460 |
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between |
| 11461 |
pattern values. |
| 11462 |
All other backslashes (those not followed by a comma) are literal |
| 11463 |
backslashes and should not be escaped. |
| 11464 |
It's unlikely you'll ever need to enter a literal comma or backslash in |
| 11465 |
any of the patterns. |
| 11466 |
|
| 11467 |
<H4>Current Folder Type</H4> |
| 11468 |
|
| 11469 |
The "Current Folder Type" may be set to one of four different |
| 11470 |
values: "Any", "News", "Email", or |
| 11471 |
"Specific". |
| 11472 |
If the value is set to "News", then the |
| 11473 |
Pattern will only match if the currently open folder is a newsgroup. |
| 11474 |
The value "Email" only matches if the current folder is not news and |
| 11475 |
the value "Any" causes any folder to match. |
| 11476 |
If the value of "Current Folder Type" is set to "Specific", |
| 11477 |
then you must fill in a value for "Folder", which is on the line |
| 11478 |
below the "Specific" line. |
| 11479 |
In this case you will only get a match if the currently open folder is |
| 11480 |
the specific folder you list. |
| 11481 |
You may give a list of folders instead of just a single |
| 11482 |
folder name, in which case the Pattern will match if the open folder is |
| 11483 |
any one of the folders in the list. |
| 11484 |
The name of each folder in the list may be either "INBOX", |
| 11485 |
the technical specification |
| 11486 |
of the folder (like what appears in your configuration file) or, if the |
| 11487 |
folder is one of your incoming folders, it may be the nickname you've given |
| 11488 |
the folder. |
| 11489 |
Here are some samples of specific folder names: |
| 11490 |
<P> |
| 11491 |
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> |
| 11492 |
<P> |
| 11493 |
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> |
| 11494 |
<P> |
| 11495 |
<CENTER><SAMP>mail/local-folder</SAMP></CENTER> |
| 11496 |
<P> |
| 11497 |
The easiest way to fill in the "Folder" field is to use |
| 11498 |
the "T" command which is available when the "Folder" line is |
| 11499 |
highlighted, or to use the "Take" command with the configuration |
| 11500 |
feature |
| 11501 |
<A HREF="#enable-rules-under-take">"enable-rules-under-take"</A> |
| 11502 |
turned on. |
| 11503 |
<P> |
| 11504 |
When reading a newsgroup, there may be a performance penalty |
| 11505 |
incurred when collecting the information necessary to check whether |
| 11506 |
or not a Pattern matches a message. |
| 11507 |
For this reason, the default Current Folder Type is set to "Email". |
| 11508 |
If you have Patterns with a Current Folder Type of either |
| 11509 |
"Any" or "News" and those Patterns are used for |
| 11510 |
Index Line Coloring or Scoring, you may experience |
| 11511 |
slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup. |
| 11512 |
|
| 11513 |
<H4>Age Interval</H4> |
| 11514 |
|
| 11515 |
The "Age Interval" may be set to an interval of message |
| 11516 |
ages which should be considered a match. |
| 11517 |
Like the other parts of the Pattern, if it is unset it will be ignored. |
| 11518 |
The Age Interval looks like |
| 11519 |
<P> |
| 11520 |
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER> |
| 11521 |
<P> |
| 11522 |
where "min_age" and "max_age" are integers greater |
| 11523 |
than or equal to zero. |
| 11524 |
The special value "INF" may be used for |
| 11525 |
the max value. It represents infinity. |
| 11526 |
<P> |
| 11527 |
Actually, this option may be defined as a list of intervals instead |
| 11528 |
of just a single interval. |
| 11529 |
The list is separated by commas. |
| 11530 |
It can look like |
| 11531 |
<P> |
| 11532 |
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER> |
| 11533 |
<P> |
| 11534 |
When there is an Age Interval defined, it is a match if the age, in days, of |
| 11535 |
the message is contained in any of the intervals. |
| 11536 |
The intervals include both endpoints. |
| 11537 |
<P> |
| 11538 |
Even though this option is called Age, it isn't actually |
| 11539 |
the <EM>age</EM> of the message. |
| 11540 |
Instead, it is how many days ago the message arrived in one of your folders. |
| 11541 |
If the current time is a little past midnight, then a message that arrived |
| 11542 |
just before midnight arrived yesterday, even though the message is only |
| 11543 |
a few minutes old. |
| 11544 |
By default, the date being used is not the date in the Date |
| 11545 |
header of the message. |
| 11546 |
It is the date that the message arrived in one of your folders. |
| 11547 |
When you Save a message from one folder to another that arrival date |
| 11548 |
is preserved. |
| 11549 |
If you would like to use the date in the Date header that is possible. |
| 11550 |
Turn on the option |
| 11551 |
<EM>use-date-header-for-age</EM> |
| 11552 |
near the bottom of the rule definition. |
| 11553 |
<P> |
| 11554 |
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on. |
| 11555 |
|
| 11556 |
<H4><A NAME="pattern_size_interval">Size Interval</A></H3> |
| 11557 |
|
| 11558 |
The "Size Interval" may be set to an interval of message |
| 11559 |
sizes which should be considered a match. |
| 11560 |
Like the other parts of the Pattern, if it is unset it will be ignored. |
| 11561 |
The Size Interval looks like |
| 11562 |
<P> |
| 11563 |
<CENTER><SAMP>(min_size,max_size)</SAMP></CENTER> |
| 11564 |
<P> |
| 11565 |
where "min_size" and "max_size" are integers greater |
| 11566 |
than or equal to zero. |
| 11567 |
The special value "INF" may be used for |
| 11568 |
the max value. It represents infinity. |
| 11569 |
<P> |
| 11570 |
Actually, this option may be defined as a list of intervals instead |
| 11571 |
of just a single interval. |
| 11572 |
The list is separated by commas. |
| 11573 |
It can look like |
| 11574 |
<P> |
| 11575 |
<CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER> |
| 11576 |
<P> |
| 11577 |
When there is a Size Interval defined, it is a match if the size, in bytes, of |
| 11578 |
the message is contained in any of the intervals. |
| 11579 |
The intervals include both endpoints. |
| 11580 |
|
| 11581 |
<H4>Score Interval</H4> |
| 11582 |
|
| 11583 |
The "Score Interval" may be set to an interval of message |
| 11584 |
scores which should be considered a match. |
| 11585 |
Like the other parts of the Pattern, if it is unset it will be ignored. |
| 11586 |
The Score Interval looks like |
| 11587 |
<P> |
| 11588 |
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER> |
| 11589 |
<P> |
| 11590 |
where "min_score" and "max_score" are integers between |
| 11591 |
-32000 and 32000. |
| 11592 |
The special values "-INF" and "INF" may be used for |
| 11593 |
the min and max values to represent negative and positive infinity. |
| 11594 |
<P> |
| 11595 |
Actually, a list of intervals may be used if you wish. |
| 11596 |
A list would look like |
| 11597 |
<P> |
| 11598 |
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER> |
| 11599 |
<P> |
| 11600 |
When there is a Score Interval defined, it is a match if the score for |
| 11601 |
the message is contained in any of the intervals in the list. |
| 11602 |
The intervals include the endpoints. |
| 11603 |
The score for a message is calculated by looking at every Score rule defined and |
| 11604 |
adding up the Score Values for the ones which match the message. |
| 11605 |
When deciding whether or not a Pattern matches a message for purposes of |
| 11606 |
calculating the score, the Score Interval is ignored. |
| 11607 |
|
| 11608 |
<H4>Message Status</H4> |
| 11609 |
|
| 11610 |
There are five separate message status settings. |
| 11611 |
By default, all five are set to the value "Don't care", which |
| 11612 |
will match any message. |
| 11613 |
The value "Yes" means that the particular status must be true |
| 11614 |
for a match, and the value "No" means that the particular |
| 11615 |
status must not be true for a match. |
| 11616 |
For example, one of the five Message Status settings is whether a message |
| 11617 |
is marked Important or not. |
| 11618 |
A "Yes" means that the message must be Important to be |
| 11619 |
considered a match and "No" means that the message must not be |
| 11620 |
Important to be considered a match. |
| 11621 |
The same is true of the other four message status settings which depend |
| 11622 |
on whether or not the message is New; whether the message has |
| 11623 |
been Answered or not; whether the message has been Deleted or not, and |
| 11624 |
whether the message is Recent or not. |
| 11625 |
<P> |
| 11626 |
The nomenclature for New and Recent is a bit confusing: |
| 11627 |
<P> |
| 11628 |
New means that the message is Unseen. |
| 11629 |
It could have been in your mailbox for a long time but if you haven't looked |
| 11630 |
at it, it is still considered New. |
| 11631 |
That matches the default <EM>Alpine</EM> index display that shows an N for such a |
| 11632 |
message. |
| 11633 |
<P> |
| 11634 |
Recent means that the message was added to this folder since the last time |
| 11635 |
you opened the folder. |
| 11636 |
<EM>Alpine</EM> also shows an N by default for these types of messages. |
| 11637 |
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after |
| 11638 |
the other, a message would only show up as Recent in (at most) the first |
| 11639 |
<EM>Alpine</EM> session. |
| 11640 |
|
| 11641 |
<H4>Message Keywords</H4> |
| 11642 |
|
| 11643 |
Keywords are similar to Message Status, but they are chosen by the user. |
| 11644 |
Provided the mail server allows for it, you may add a set of possible keywords |
| 11645 |
to a folder and then you may set those keywords or not for each message |
| 11646 |
in the folder. |
| 11647 |
The syntax of this part of the Pattern is similar to the header patterns. |
| 11648 |
It is a list of keywords. |
| 11649 |
The Keyword part of the Pattern is a match if the message has any of |
| 11650 |
the keywords in the list set. |
| 11651 |
Like other parts of the Pattern, if this is unset it will be ignored. |
| 11652 |
|
| 11653 |
<H4>Message Character Set</H4> |
| 11654 |
|
| 11655 |
A message may use one or more character sets. |
| 11656 |
This part of the Pattern matches messages which make use of one or more of |
| 11657 |
the character sets specified in the pattern. |
| 11658 |
It will be considered a match if a message uses any of the character |
| 11659 |
sets in the list you give here. |
| 11660 |
The syntax of this part of the Pattern is similar to the header patterns |
| 11661 |
and the Message Keywords pattern. |
| 11662 |
It is a list of character sets. |
| 11663 |
|
| 11664 |
<P> |
| 11665 |
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or |
| 11666 |
GB2312) you may also use some shorthand names that <EM>Alpine</EM> provides. |
| 11667 |
These names are more understandable shorthand names for sets of |
| 11668 |
character set names. |
| 11669 |
Two examples are "Cyrillic" and "Greek". |
| 11670 |
Selecting one of these shorthand names is equivalent to selecting all of |
| 11671 |
the character sets that make up the set. |
| 11672 |
You can see all of these shorthand names and the lists of character sets |
| 11673 |
they stand for by typing the "T" command with the Character |
| 11674 |
Set pattern highlighted. |
| 11675 |
The Character Set part of the Pattern is a match if the message uses any |
| 11676 |
of the character sets in the list. |
| 11677 |
Like other parts of the Pattern, if this is unset it will be ignored. |
| 11678 |
|
| 11679 |
<H4>Raw 8-bit in Subject</H4> |
| 11680 |
|
| 11681 |
It seems that lots of unwanted email contains unencoded 8-bit characters |
| 11682 |
in the Subject. |
| 11683 |
Normally, characters with the 8th bit set are not allowed in the Subject |
| 11684 |
header unless they are MIME-encoded. |
| 11685 |
This option gives you a way to match messages which have Subjects which |
| 11686 |
contain unencoded 8-bit characters. |
| 11687 |
Setting this option will affect performance in large folders because the |
| 11688 |
subject of each message in the folder has to be checked. |
| 11689 |
|
| 11690 |
<H4>Beginning of Month</H4> |
| 11691 |
|
| 11692 |
This option gives you a way to take some action once per month. |
| 11693 |
The value "Yes" means that this must be the first time <EM>Alpine</EM> has |
| 11694 |
been run this month in order to count as a match, |
| 11695 |
|
| 11696 |
<H4>Beginning of Year</H4> |
| 11697 |
|
| 11698 |
This option gives you a way to take some action once per year. |
| 11699 |
The value "Yes" means that this must be the first time <EM>Alpine</EM> has |
| 11700 |
been run this year in order to count as a match, |
| 11701 |
|
| 11702 |
<H4>From or Reply-To address in Address Books</H4> |
| 11703 |
|
| 11704 |
This option gives you a way to match messages which have a From or |
| 11705 |
a Reply-To address |
| 11706 |
which is in one of your address books. |
| 11707 |
Only the simple entries in your address books are searched. |
| 11708 |
Address book distribution lists are ignored! |
| 11709 |
Setting this option will affect performance in large folders because the |
| 11710 |
From and Reply-To of each message in the folder have to be checked. |
| 11711 |
|
| 11712 |
<H4>Categorizer Command</H4> |
| 11713 |
|
| 11714 |
This is a command that is run with its standard input set to the message |
| 11715 |
being checked and its standard output discarded. |
| 11716 |
The full directory path should be specified. |
| 11717 |
The command will be run and then its exit status will be checked against |
| 11718 |
the Exit Status Interval, which defaults to just the value zero. |
| 11719 |
If the exit status of the command falls in the interval, it is considered |
| 11720 |
a match, otherwise it is not a match. |
| 11721 |
<P> |
| 11722 |
|
| 11723 |
This option may actually be a list of commands. |
| 11724 |
The first one that exists and is executable is used. |
| 11725 |
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and |
| 11726 |
<EM>PC-Alpine</EM>. |
| 11727 |
<P> |
| 11728 |
|
| 11729 |
If none of the commands in the list exists and is executable then the rule |
| 11730 |
is <EM>not</EM> a match. |
| 11731 |
If it is possible that the command may not exist, you should be careful |
| 11732 |
to structure your rules so that nothing destructive |
| 11733 |
happens when the command does not exist. |
| 11734 |
For example, you might have a filter that filters away spam when there is |
| 11735 |
a match but does nothing when there is not a match. |
| 11736 |
That would continue to work correctly if the command didn't exist. |
| 11737 |
However, if you have a filter which filters away spam when there is not |
| 11738 |
a match and keeps it when there is a match, that would filter everything |
| 11739 |
if the categorizer command didn't exist. |
| 11740 |
|
| 11741 |
<H3><A NAME="help-for-pattern-config"></A>Help Configuring Pattern Fields</H3> |
| 11742 |
|
| 11743 |
<DL COMPACT> |
| 11744 |
|
| 11745 |
<DT> <A NAME="role-nickname"><EM>Nickname</EM></A> |
| 11746 |
|
| 11747 |
<DD> This is a nickname to help you. |
| 11748 |
You should have a different nickname for each role you define. |
| 11749 |
The nickname will be used in the SETUP ROLE RULES screen to allow you to |
| 11750 |
pick a role to edit. |
| 11751 |
It will also be used when you send a message to let you know you are |
| 11752 |
sending with a different role than you use by default, and |
| 11753 |
it will be useful for choosing a role when composing with the Role command |
| 11754 |
or when composing with one of the Role Uses set to With Confirmation. |
| 11755 |
This field is not used in the outgoing message. |
| 11756 |
<P> |
| 11757 |
|
| 11758 |
<DT> <A NAME="role-comment"><EM>Comment</EM></A> |
| 11759 |
|
| 11760 |
<DD> This is a comment to help you. |
| 11761 |
This comment does not play any functional role, it is simply an optional |
| 11762 |
comment to help you remember what the rule is for. |
| 11763 |
<P> |
| 11764 |
|
| 11765 |
<DT> <A NAME="to-pattern"><EM>To pattern</EM></A> |
| 11766 |
|
| 11767 |
<DD> If this pattern is non-blank, then for this role to be considered a |
| 11768 |
match, at least one of the recipients from |
| 11769 |
the To line of the message being replied to or forwarded |
| 11770 |
must match this pattern. |
| 11771 |
In the case of the Compose command, this pattern and the other header |
| 11772 |
patterns are ignored. |
| 11773 |
If this pattern is a list of patterns, then at least one of the |
| 11774 |
recipients must match at least one of the patterns. |
| 11775 |
(Any other non-blank parts of the Pattern must match, too.) |
| 11776 |
If the message being replied to or forwarded has a Resent-To header line, |
| 11777 |
then that is used in place of the To line. |
| 11778 |
(Note that this special Resent rule only applies to the To header. The |
| 11779 |
Resent-From, Resent-Subject, and so on are not consulted.) |
| 11780 |
<P> |
| 11781 |
It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the |
| 11782 |
"!" "toggle NOT" command. |
| 11783 |
This changes the meaning of the To pattern so that it has the opposite meaning. |
| 11784 |
It will be considered a match if there are no matches between the |
| 11785 |
addresses in the To: line and the list of To patterns. |
| 11786 |
<P> |
| 11787 |
Don't make the mistake of putting the "!" in the data field for |
| 11788 |
the pattern. |
| 11789 |
For example, if you type the characters "!frizzle" into the To |
| 11790 |
pattern, the pattern will look like: |
| 11791 |
<P> |
| 11792 |
<PRE> |
| 11793 |
To pattern = !frizzle |
| 11794 |
</PRE> |
| 11795 |
<P> |
| 11796 |
This means you want to match the 8 character sequence "!frizzle". |
| 11797 |
In order to match messages which do not have "frizzle" in |
| 11798 |
their To field, first type the characters "frizzle" followed |
| 11799 |
by carriage return for the value of the To pattern, then negate it |
| 11800 |
by typing the "!" command. |
| 11801 |
It should end up looking like |
| 11802 |
<P> |
| 11803 |
<PRE> |
| 11804 |
! To pattern = frizzle |
| 11805 |
</PRE> |
| 11806 |
<P> |
| 11807 |
|
| 11808 |
<DT> <A NAME="from-pattern"><EM>From pattern</EM></A> |
| 11809 |
|
| 11810 |
<DD> This is just like the |
| 11811 |
<A HREF="#to-pattern"><EM>To pattern</EM></A> |
| 11812 |
except that it is compared with |
| 11813 |
the address from the From header of the message being replied to or forwarded instead |
| 11814 |
of the addresses from the To header. |
| 11815 |
<P> |
| 11816 |
|
| 11817 |
<DT> <A NAME="sender-pattern"><EM>Sender pattern</EM></A> |
| 11818 |
|
| 11819 |
<DD> This is just like the |
| 11820 |
<A HREF="#to-pattern"><EM>To pattern</EM></A> |
| 11821 |
except that it is compared with |
| 11822 |
the address from the Sender header of the message being replied to or forwarded instead |
| 11823 |
of the addresses from the To header. |
| 11824 |
If there is no Sender header, then the From header is used instead. |
| 11825 |
<P> |
| 11826 |
|
| 11827 |
<DT> <A NAME="cc-pattern"><EM>Cc pattern</EM></A> |
| 11828 |
|
| 11829 |
<DD> This is just like the |
| 11830 |
<A HREF="#to-pattern"><EM>To pattern</EM></A> |
| 11831 |
except that it is compared with |
| 11832 |
the address from the CC header of the message being replied to or forwarded instead |
| 11833 |
of the addresses from the To header. |
| 11834 |
<P> |
| 11835 |
|
| 11836 |
<DT> <A NAME="news-pattern"><EM>News pattern</EM></A> |
| 11837 |
|
| 11838 |
<DD> If this pattern is non-blank, then for this role to be considered a |
| 11839 |
match, at least one of the newsgroups from |
| 11840 |
the Newsgroups line of the message must match this pattern. |
| 11841 |
If this pattern is a list of patterns, then at least one of the |
| 11842 |
newsgroups must match at least one of the patterns. |
| 11843 |
(Any other non-blank parts of the Pattern must match, too.) |
| 11844 |
<P> |
| 11845 |
|
| 11846 |
<DT> <A NAME="subject-pattern"><EM>Subject pattern</EM></A> |
| 11847 |
|
| 11848 |
<DD> This is similar to the other header patterns. |
| 11849 |
It is compared with |
| 11850 |
the contents from the Subject of the message being replied to or forwarded. |
| 11851 |
<P> |
| 11852 |
If you enter non-ascii characters in this field then the search will be |
| 11853 |
done using the character set you have defined with the |
| 11854 |
<A HREF="#char-set">Character-Set</A> |
| 11855 |
configuration variable. |
| 11856 |
(The truly sophisticated may use an alternate character set for a search |
| 11857 |
by entering the MIME encoding of the header string here.) |
| 11858 |
<P> |
| 11859 |
|
| 11860 |
<DT> <A NAME="extra-header-patterns"><EM>Extra header patterns</EM></A> |
| 11861 |
|
| 11862 |
<DD> There isn't actually a field called Extra header patterns, but you |
| 11863 |
may add extra header patterns by moving the cursor to one of the header |
| 11864 |
patterns and using the "eXtraHdr" command to add a new header |
| 11865 |
pattern. |
| 11866 |
You would do this if the six predefined header patterns don't cover the |
| 11867 |
header you want to use for pattern matching. |
| 11868 |
Once you've added an extra header pattern, you use it just like the |
| 11869 |
Subject pattern. |
| 11870 |
Of course, it is compared with |
| 11871 |
the contents from the particular header field of the message being replied |
| 11872 |
to or forwarded rather than the contents from the subject field. |
| 11873 |
To remove an extra header pattern from a role, use the "RemoveHdr" |
| 11874 |
command on the highlighted extra header. |
| 11875 |
<P> |
| 11876 |
If you enter non-ascii characters in this field then the search will be |
| 11877 |
done using the character set you have defined with the |
| 11878 |
<A HREF="#char-set">Character-Set</A> |
| 11879 |
configuration variable. |
| 11880 |
(The truly sophisticated may use an alternate character set for a search |
| 11881 |
by entering the MIME encoding of the header string here.) |
| 11882 |
<P> |
| 11883 |
|
| 11884 |
<DT> <A NAME="recip-pattern"><EM>Recipient pattern</EM></A> |
| 11885 |
|
| 11886 |
<DD> This is just like the |
| 11887 |
<A HREF="#to-pattern"><EM>To pattern</EM></A> |
| 11888 |
except that it is compared with |
| 11889 |
the addresses from both the To header and the Cc header |
| 11890 |
instead of just the addresses from the To header. |
| 11891 |
It's equivalent to having two different rules; |
| 11892 |
one with a To pattern and the other with the same Cc pattern. |
| 11893 |
<P> |
| 11894 |
|
| 11895 |
<DT> <A NAME="partic-pattern"><EM>Participant pattern</EM></A> |
| 11896 |
|
| 11897 |
<DD> This is just like the |
| 11898 |
<A HREF="#to-pattern"><EM>To pattern</EM></A> |
| 11899 |
except that it is compared with |
| 11900 |
the addresses from the To header, the Cc header, and the From header |
| 11901 |
instead of just the addresses from the To header. |
| 11902 |
It's equivalent to having three different rules; |
| 11903 |
one with a To pattern, another with the same Cc pattern, and another |
| 11904 |
with the same From pattern. |
| 11905 |
<P> |
| 11906 |
|
| 11907 |
<DT> <A NAME="alltext-pattern"><EM>AllText pattern</EM></A> |
| 11908 |
|
| 11909 |
<DD> This is similar to the header patterns. |
| 11910 |
Instead of comparing with text in a particular header field it is compared with |
| 11911 |
all of the text in the message header and body. |
| 11912 |
<P> |
| 11913 |
If you enter non-ascii characters in this field then the search will be |
| 11914 |
done using the character set you have defined with the |
| 11915 |
<A HREF="#char-set">Character-Set</A> |
| 11916 |
configuration variable. |
| 11917 |
(The truly sophisticated may use an alternate character set for a search |
| 11918 |
by entering the MIME encoding of the header string here.) |
| 11919 |
<P> |
| 11920 |
|
| 11921 |
<DT> <A NAME="bodytext-pattern"><EM>BodyText pattern</EM></A> |
| 11922 |
|
| 11923 |
<DD> Just like AllText, except it is compared only with the body of the |
| 11924 |
message, not the body and header. |
| 11925 |
|
| 11926 |
<P> |
| 11927 |
If you enter non-ascii characters in this field then the search will be |
| 11928 |
done using the character set you have defined with the |
| 11929 |
<A HREF="#char-set">Character-Set</A> |
| 11930 |
configuration variable. |
| 11931 |
(The truly sophisticated may use an alternate character set for a search |
| 11932 |
by entering the MIME encoding of the header string here.) |
| 11933 |
<P> |
| 11934 |
|
| 11935 |
<DT> <A NAME="age-interval"><EM>Age Interval</EM></A> |
| 11936 |
|
| 11937 |
<DD>The Age Interval, if defined, is part of the Pattern. |
| 11938 |
If you use this, it should be set to something like: |
| 11939 |
<P> |
| 11940 |
<CENTER><SAMP>(min_age,max_age)</SAMP></CENTER> |
| 11941 |
<P> |
| 11942 |
where "min_age" and "max_age" are non-negative integers. |
| 11943 |
The special value "INF" may be used for the max value. |
| 11944 |
It represents infinity. |
| 11945 |
<P> |
| 11946 |
In rare cases it may be useful to use the more general form of the value, |
| 11947 |
which is a comma-separated list of intervals. |
| 11948 |
It would look something like: |
| 11949 |
<P> |
| 11950 |
<CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER> |
| 11951 |
<P> |
| 11952 |
When there is an Age Interval defined, it is a match if the age, in days, of |
| 11953 |
the message is contained in the interval. |
| 11954 |
The interval includes both endpoints. |
| 11955 |
If the option is set to a list of intervals then it is a match if the |
| 11956 |
age of the message is contained in any of the intervals. |
| 11957 |
<P> |
| 11958 |
Even though this option is called Age, it isn't actually |
| 11959 |
the <EM>age</EM> of the message. |
| 11960 |
Instead, it is how many days ago the message arrived in one of your folders. |
| 11961 |
If the current time is a little past midnight, then a message that arrived |
| 11962 |
just before midnight arrived yesterday, even though the message is only |
| 11963 |
a few minutes old. |
| 11964 |
By default, the date being used is not the date in the Date |
| 11965 |
header of the message. |
| 11966 |
It is the date that the message arrived in one of your folders. |
| 11967 |
When you Save a message from one folder to another that arrival date |
| 11968 |
is preserved. |
| 11969 |
If you would like to use the date in the Date header that is possible. |
| 11970 |
Turn on the option |
| 11971 |
<EM>use-date-header-for-age</EM> |
| 11972 |
near the bottom of the rule definition. |
| 11973 |
<P> |
| 11974 |
A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on. |
| 11975 |
The age interval |
| 11976 |
<P> |
| 11977 |
<CENTER><SAMP>(2,2)</SAMP></CENTER> |
| 11978 |
<P> |
| 11979 |
matches all messages that arrived on the day before yesterday. |
| 11980 |
The interval |
| 11981 |
<P> |
| 11982 |
<CENTER><SAMP>(180,INF)</SAMP></CENTER> |
| 11983 |
<P> |
| 11984 |
matches all messages that arrived at least 180 days before today. |
| 11985 |
The interval |
| 11986 |
<P> |
| 11987 |
<CENTER><SAMP>(0,1)</SAMP></CENTER> |
| 11988 |
<P> |
| 11989 |
matches all messages that arrived today or yesterday. |
| 11990 |
<P> |
| 11991 |
|
| 11992 |
<DT> <A NAME="score-interval"><EM>Score Interval</EM></A> |
| 11993 |
|
| 11994 |
<DD> The Score Interval, if defined, is part of the Pattern. |
| 11995 |
If you use this, it should be set to something like: |
| 11996 |
<P> |
| 11997 |
<CENTER><SAMP>(min_score,max_score)</SAMP></CENTER> |
| 11998 |
<P> |
| 11999 |
where "min_score" and "max_score" are integers between |
| 12000 |
-32000 and 32000. |
| 12001 |
The special values "-INF" and "INF" can be used for |
| 12002 |
the min and max values. |
| 12003 |
These represent negative and positive infinity. |
| 12004 |
<P> |
| 12005 |
Actually, the value may be a list of intervals rather than just a |
| 12006 |
single interval if that is useful. |
| 12007 |
The elements of the list are separated by commas like: |
| 12008 |
<P> |
| 12009 |
<CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER> |
| 12010 |
<P> |
| 12011 |
When there is a Score Interval defined, it is a match if the score for |
| 12012 |
the message is contained in any of the intervals. |
| 12013 |
The intervals include both endpoints. |
| 12014 |
The score for a message is calculated by looking at every scoring rule |
| 12015 |
defined and adding up the Score Values for the rules which match the message. |
| 12016 |
<P> |
| 12017 |
|
| 12018 |
<DT> <A NAME="keyword-pattern"><EM>Keyword pattern</EM></A> |
| 12019 |
|
| 12020 |
<DD> A folder may have user-defined keywords. |
| 12021 |
These are similar to the Important flag which the user may set using the |
| 12022 |
Flag command. |
| 12023 |
The difference is that the Important flag is always present for each folder. |
| 12024 |
User-defined keywords are picked by the user. |
| 12025 |
You may add new keywords by defining them in the |
| 12026 |
<A HREF="#keywords">Keywords</A> option in the Setup/Config screen. |
| 12027 |
After you have added a potential keyword with the Keywords option, |
| 12028 |
the Flag command may be used to set or clear the keyword on individual messages. |
| 12029 |
If you have given a keyword a nickname when configuring it, |
| 12030 |
that nickname may be used instead of the actual keyword. |
| 12031 |
|
| 12032 |
<P> |
| 12033 |
When filling in a value for this field, it may be easiest to use |
| 12034 |
the "T" command, which presents you with a list of the keywords |
| 12035 |
you have defined to choose from. |
| 12036 |
|
| 12037 |
<P> |
| 12038 |
This part of the Pattern matches messages with certain keywords set. |
| 12039 |
It will be considered a match if a message has any of the keywords in the |
| 12040 |
list set. |
| 12041 |
|
| 12042 |
<P> |
| 12043 |
It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the |
| 12044 |
"!" "toggle NOT" command. |
| 12045 |
This changes the meaning of the Keyword pattern so that it has the opposite meaning. |
| 12046 |
It will be considered a match if none of the keywords in the list are set |
| 12047 |
for a message. |
| 12048 |
<P> |
| 12049 |
Don't make the mistake of putting the "!" in the data field for |
| 12050 |
the pattern. |
| 12051 |
For example, if you type the characters "!frizzle" into the Keyword |
| 12052 |
pattern, the pattern will look like: |
| 12053 |
<P> |
| 12054 |
<PRE> |
| 12055 |
Keyword pattern = !frizzle |
| 12056 |
</PRE> |
| 12057 |
<P> |
| 12058 |
This means you want to match the 8 character sequence "!frizzle". |
| 12059 |
In order to match messages which do not have the keyword "frizzle" |
| 12060 |
set, first type the characters "frizzle" followed |
| 12061 |
by carriage return for the value of the Keyword pattern, then negate it |
| 12062 |
by typing the "!" command. |
| 12063 |
It should end up looking like |
| 12064 |
<P> |
| 12065 |
<PRE> |
| 12066 |
! Keyword pattern = frizzle |
| 12067 |
</PRE> |
| 12068 |
<P> |
| 12069 |
|
| 12070 |
<DT> <A NAME="charset-pattern"><EM>Character Set pattern</EM></A> |
| 12071 |
|
| 12072 |
<DD> A message may use one or more character sets. |
| 12073 |
This part of the Pattern matches messages which make use of |
| 12074 |
certain specified character sets. |
| 12075 |
It will be considered a match if a message uses any of the character |
| 12076 |
sets in the list you give here. |
| 12077 |
|
| 12078 |
<P> |
| 12079 |
When filling in a value for this field, you may use |
| 12080 |
the "T" command, which presents you with a large list of |
| 12081 |
possible character sets to choose from. |
| 12082 |
You may also just type in the name of a character set, and it need not |
| 12083 |
be one that Alpine knows about. |
| 12084 |
|
| 12085 |
<P> |
| 12086 |
Besides actual character set names (for example, ISO-8859-7, KOI8-R, or |
| 12087 |
GB2312) you may also use some shorthand names that Alpine provides. |
| 12088 |
These names are more understandable shorthand names for sets of |
| 12089 |
character set names. |
| 12090 |
Two examples are "Cyrillic" and "Greek". |
| 12091 |
Selecting one of these shorthand names is equivalent to selecting all of |
| 12092 |
the character sets that make up the set. |
| 12093 |
You can see all of these shorthand names and the lists of character sets |
| 12094 |
they stand for by typing the "T" command. |
| 12095 |
|
| 12096 |
<P> |
| 12097 |
For the purposes of this Pattern, |
| 12098 |
<EM>Alpine</EM> will search through a message for all of the text parts and |
| 12099 |
collect the character sets declared for each part. |
| 12100 |
It will also look in the Subject line for a character set used there. |
| 12101 |
<EM>Alpine</EM> does not actually look at the text of the message or the text |
| 12102 |
of the Subject to determine if a declared character set is actually |
| 12103 |
used, it looks only at the declarations themselves in the MIME part headers |
| 12104 |
and in the Subject. |
| 12105 |
|
| 12106 |
<P> |
| 12107 |
It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the |
| 12108 |
"!" "toggle NOT" command. |
| 12109 |
This changes the meaning of the Character Set pattern so that |
| 12110 |
it has the opposite meaning. |
| 12111 |
It will be considered a match if none of the character sets in the |
| 12112 |
list are used in a message. |
| 12113 |
<P> |
| 12114 |
Don't make the mistake of putting the "!" in the data field for |
| 12115 |
the pattern. |
| 12116 |
For example, if you type the characters "!GB2312" into the |
| 12117 |
Character Set pattern, the pattern will look like: |
| 12118 |
<P> |
| 12119 |
<PRE> |
| 12120 |
Charset pattern = !GB2312 |
| 12121 |
</PRE> |
| 12122 |
<P> |
| 12123 |
This means you want to match the 7 character sequence "!GB2312". |
| 12124 |
In order to match messages which do not have the |
| 12125 |
character set "GB2312" |
| 12126 |
set, first type the characters "GB2312" followed |
| 12127 |
by carriage return for the value of the Character Set pattern, then negate it |
| 12128 |
by typing the "!" command. |
| 12129 |
It should end up looking like |
| 12130 |
<P> |
| 12131 |
<PRE> |
| 12132 |
! Charset pattern = GB2312 |
| 12133 |
</PRE> |
| 12134 |
<P> |
| 12135 |
A technicality: Since comma is the character used to separate multiple |
| 12136 |
values in a pattern field, you have to escape comma with a backslash (\) if |
| 12137 |
you want to include a literal comma in the field. |
| 12138 |
In other words, if you type a backslash followed by a comma it will |
| 12139 |
be interpreted as a comma by <EM>Alpine</EM>, instead of as a separator between |
| 12140 |
pattern values. |
| 12141 |
All other backslashes are literal backslashes and should not be escaped. |
| 12142 |
<P> |
| 12143 |
|
| 12144 |
<DT> <A NAME="current-folder-type"><EM>Current Folder Type</EM></A> |
| 12145 |
|
| 12146 |
<DD> The Current Folder Type is part of the Pattern. |
| 12147 |
It refers to the type of the currently open folder, which is the folder |
| 12148 |
you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen. |
| 12149 |
In order for a pattern to be considered a match, the current folder must |
| 12150 |
be of the type you set here. |
| 12151 |
The three types "Any", "News", and "Email" are |
| 12152 |
all what you might think. |
| 12153 |
<P> |
| 12154 |
If the Current Folder Type for a Pattern is set to "News", for |
| 12155 |
example, then |
| 12156 |
that will only be a match if the current folder is a newsgroup and |
| 12157 |
the rest of the Pattern matches. |
| 12158 |
The value "Specific" may be used when you want to limit the match |
| 12159 |
to a specific folder (not just a specific type of folder), or to a list of |
| 12160 |
specific folders. |
| 12161 |
In order to match a specific folder you must Select the "Specific" |
| 12162 |
button <EM>AND</EM> you must fill in |
| 12163 |
the name (or list of names) of |
| 12164 |
the folder in the "Folder" field. |
| 12165 |
If the current folder is any of the folders in the list, that is considered |
| 12166 |
a match. |
| 12167 |
The name of each folder in the list may be either "INBOX", the technical specification |
| 12168 |
of the folder (like what appears in your configuration file) or, if the |
| 12169 |
folder is one of your incoming folders, it may be the nickname you've given |
| 12170 |
the folder. |
| 12171 |
Here are a couple samples of specific folder names: |
| 12172 |
<P> |
| 12173 |
<CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER> |
| 12174 |
<P> |
| 12175 |
<CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER> |
| 12176 |
<P> |
| 12177 |
The easiest way to fill in the "Folder" field is to use |
| 12178 |
the T command which is available when the "Folder" line is |
| 12179 |
highlighted. |
| 12180 |
Note that you won't be able to edit the "Folder" line unless the |
| 12181 |
Current Folder Type is set to "Specific", and any value that |
| 12182 |
"Folder" has is ignored unless the type |
| 12183 |
is set to "Specific". |
| 12184 |
<P> |
| 12185 |
When reading a newsgroup, there may be a performance penalty |
| 12186 |
incurred when collecting the information necessary to check a Pattern. |
| 12187 |
For this reason, the default Current Folder Type is set to "Email". |
| 12188 |
For example, a role with a non-Normal Index Line Color |
| 12189 |
and a Current Folder Type of |
| 12190 |
"Any" or "News" may cause the MESSAGE INDEX |
| 12191 |
screen to draw more slowly when in a newsgroup. |
| 12192 |
<P> |
| 12193 |
|
| 12194 |
<DT> <A NAME="message-status-important"><EM>Message Status Important</EM></A> |
| 12195 |
|
| 12196 |
<DD> This part of the Pattern may have one of three possible values. |
| 12197 |
The default value is "Don't care", which matches any message. |
| 12198 |
The other two values are "Yes", which means the message must be |
| 12199 |
flagged "Important" in order to be a match; or "No", which |
| 12200 |
means the message must <EM>not</EM> be flagged "Important" in order |
| 12201 |
to be considered a match. |
| 12202 |
<P> |
| 12203 |
|
| 12204 |
<DT> <A NAME="message-status-new"><EM>Message Status New</EM></A> |
| 12205 |
|
| 12206 |
<DD> This part of the Pattern may have one of three possible values. |
| 12207 |
The default value is "Don't care", which matches any message. |
| 12208 |
The other two values are "Yes", which means the message must be |
| 12209 |
"New" in order to be a match; or "No", which |
| 12210 |
means the message must <EM>not</EM> be "New" in order |
| 12211 |
to be a match. |
| 12212 |
"New" is the same as <EM>Unseen</EM> and not "New" is the |
| 12213 |
same as <EM>Seen</EM>. |
| 12214 |
<P> |
| 12215 |
The nomenclature for New and Recent is a bit confusing: |
| 12216 |
<P> |
| 12217 |
New means that the message is Unseen. |
| 12218 |
It could have been in your mailbox for a long time but if you haven't looked |
| 12219 |
at it, it is still considered New. |
| 12220 |
That matches the default <EM>Alpine</EM> index display that shows an N for such a |
| 12221 |
message. |
| 12222 |
<P> |
| 12223 |
Recent means that the message was added to this folder since the last time |
| 12224 |
you opened the folder. |
| 12225 |
<EM>Alpine</EM> also shows an N by default for these types of messages. |
| 12226 |
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after |
| 12227 |
the other, a message would only show up as Recent in (at most) the first |
| 12228 |
<EM>Alpine</EM> session. |
| 12229 |
<P> |
| 12230 |
|
| 12231 |
<DT> <A NAME="message-status-recent"><EM>Message Status Recent</EM></A> |
| 12232 |
|
| 12233 |
<DD> This part of the Pattern may have one of three possible values. |
| 12234 |
The default value is "Don't care", which matches any message. |
| 12235 |
The other two values are "Yes", which means the message must be |
| 12236 |
"Recent" in order to be a match; or "No", which |
| 12237 |
means the message must <EM>not</EM> be "Recent" in order |
| 12238 |
to be a match. |
| 12239 |
"Recent" means that the message was added to the folder since |
| 12240 |
the last time the folder was opened. |
| 12241 |
If more than one mail client has the folder opened, the message will |
| 12242 |
appear to be "Recent" to only one of the clients. |
| 12243 |
<P> |
| 12244 |
The nomenclature for New and Recent is a bit confusing: |
| 12245 |
<P> |
| 12246 |
New means that the message is Unseen. |
| 12247 |
It could have been in your mailbox for a long time but if you haven't looked |
| 12248 |
at it, it is still considered New. |
| 12249 |
That matches the default <EM>Alpine</EM> index display that shows an N for such a |
| 12250 |
message. |
| 12251 |
<P> |
| 12252 |
Recent means that the message was added to this folder since the last time |
| 12253 |
you opened the folder. |
| 12254 |
<EM>Alpine</EM> also shows an N by default for these types of messages. |
| 12255 |
If you were to run two copies of <EM>Alpine</EM> that opened a folder one right after |
| 12256 |
the other, a message would only show up as Recent in (at most) the first |
| 12257 |
<EM>Alpine</EM> session. |
| 12258 |
<P> |
| 12259 |
|
| 12260 |
<DT> <A NAME="message-status-deleted"><EM>Message Status Deleted</EM></A> |
| 12261 |
|
| 12262 |
<DD> This part of the Pattern may have one of three possible values. |
| 12263 |
The default value is "Don't care", which matches any message. |
| 12264 |
The other two values are "Yes", which means the message must be |
| 12265 |
marked "Deleted" in order to be a match; or "No", which |
| 12266 |
means the message must <EM>not</EM> be marked "Deleted" in order |
| 12267 |
to be a match. |
| 12268 |
<P> |
| 12269 |
If you are thinking of using this part of the Pattern as a way to prevent |
| 12270 |
messages from being filtered more than once in a Filter Pattern, |
| 12271 |
take a look at the Filter Option |
| 12272 |
<A HREF="#move-only-if-not-deleted">"move-only-if-not-deleted"</A> |
| 12273 |
instead. |
| 12274 |
It should work better than using this field since it will hide the filtered |
| 12275 |
messages even if they are already Deleted. |
| 12276 |
<P> |
| 12277 |
|
| 12278 |
<DT> <A NAME="message-status-answered"><EM>Message Status Answered</EM></A> |
| 12279 |
|
| 12280 |
<DD> This part of the Pattern may have one of three possible values. |
| 12281 |
The default value is "Don't care", which matches any message. |
| 12282 |
The other two values are "Yes", which means the message must be |
| 12283 |
marked "Answered" in order to be a match; or "No", which |
| 12284 |
means the message must <EM>not</EM> be marked "Answered" in order |
| 12285 |
to be a match. |
| 12286 |
<P> |
| 12287 |
|
| 12288 |
<DT> <A NAME="subject-contains-raw-8bit"><EM>Subject Contains Raw 8-bit</EM></A> |
| 12289 |
|
| 12290 |
<DD> This part of the Pattern may have one of three possible values. |
| 12291 |
The default value is "Don't care", which matches any message. |
| 12292 |
The other two values are "Yes", which means the Subject of |
| 12293 |
the message must contain unencoded 8-bit characters (characters with the |
| 12294 |
most significant bit set) |
| 12295 |
in order to be a match; or "No", which |
| 12296 |
means the Subject must <EM>not</EM> |
| 12297 |
contain unencoded 8-bit characters in order to be a match. |
| 12298 |
<P> |
| 12299 |
|
| 12300 |
<DT> <A NAME="beginning-of-month"><EM>Beginning of Month</EM></A> |
| 12301 |
|
| 12302 |
<DD> This part of the Pattern may have one of three possible values. |
| 12303 |
The default value is "Don't care", which matches any message. |
| 12304 |
The other two values are "Yes", which means this is the first |
| 12305 |
time <EM>Alpine</EM> has been run this month; |
| 12306 |
or "No", which |
| 12307 |
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this month. |
| 12308 |
The way that <EM>Alpine</EM> decides if it is the beginning of the month or not is |
| 12309 |
to compare today's date with the date stored in the |
| 12310 |
<A HREF="#last-time">Last-Time-Prune-Questioned</A> |
| 12311 |
variable in the config file. |
| 12312 |
If the month of today's date is later than the month stored in the variable, |
| 12313 |
then this is considered to be the first time you have run Alpine this month, and |
| 12314 |
that turns the Beginning of the Month option on. |
| 12315 |
<P> |
| 12316 |
|
| 12317 |
<DT> <A NAME="beginning-of-year"><EM>Beginning of Year</EM></A> |
| 12318 |
|
| 12319 |
<DD> This part of the Pattern may have one of three possible values. |
| 12320 |
The default value is "Don't care", which matches any message. |
| 12321 |
The other two values are "Yes", which means this is the first |
| 12322 |
time <EM>Alpine</EM> has been run this year; |
| 12323 |
or "No", which |
| 12324 |
means this is <EM>not</EM> the first time <EM>Alpine</EM> has been run this year. |
| 12325 |
The way that <EM>Alpine</EM> decides if it is the beginning of the year or not is |
| 12326 |
to compare today's date with the date stored in the |
| 12327 |
<A HREF="#last-time">Last-Time-Prune-Questioned</A> |
| 12328 |
variable in the config file. |
| 12329 |
If the year of today's date is later than the year stored in the variable, |
| 12330 |
then this is considered to be the first time you have run Alpine this year, and |
| 12331 |
that turns the Beginning of the Year option on. |
| 12332 |
<P> |
| 12333 |
|
| 12334 |
<DT> <A NAME="from-in-abook"><EM>From or Reply-To in Address Book</EM></A> |
| 12335 |
|
| 12336 |
<DD> This part of the Pattern may have one of five possible values. |
| 12337 |
The default value is "Don't care", which matches any message. |
| 12338 |
The value "Yes, in any address book" means either the From address |
| 12339 |
or the Reply-To address of the message must be in at least one of your |
| 12340 |
address books in order to be a match. |
| 12341 |
The value "No, not in any address book" |
| 12342 |
means neither the From nor the Reply-To addresses may |
| 12343 |
be in any of your address books in order to be a match. |
| 12344 |
<P> |
| 12345 |
The values "Yes, in specific address books" and |
| 12346 |
"No, not in any of specific address books" are similar but instead |
| 12347 |
of depending on all address books you are allowed to give a list of address |
| 12348 |
books to look in. |
| 12349 |
Usually this would be a single address book but it may be a |
| 12350 |
list of address books as well. |
| 12351 |
For each of these "specific" address book options you Select which |
| 12352 |
of the Specific options you want (Yes or No) <EM>AND</EM> fill in the |
| 12353 |
name (or list of names) of the address book in the |
| 12354 |
"Abook List" field. |
| 12355 |
The names to be used are those that appear in the ADDRESS BOOK LIST screen. |
| 12356 |
The easiest way to fill in the Abook List field it to use |
| 12357 |
the "T" command which is available when the "Abook List" |
| 12358 |
line is highlighted. |
| 12359 |
Note that you won't be able to edit the "Abook List" line unless the |
| 12360 |
option is set to one of the two "Specific", values. |
| 12361 |
<P> |
| 12362 |
|
| 12363 |
<DT> <A NAME="categorizer-cmd-explained"><EM>Categorizer Command</EM></A> |
| 12364 |
|
| 12365 |
<DD> This is a command that is run with its standard input set to the message |
| 12366 |
being checked and its standard output discarded. |
| 12367 |
The full directory path should be specified. |
| 12368 |
The command will be run and then its exit status will be checked against |
| 12369 |
the <EM>Exit Status Interval</EM>, which defaults to just the value zero. |
| 12370 |
If the exit status of the command falls in the interval, it is considered |
| 12371 |
a match, otherwise it is not a match. |
| 12372 |
<P> |
| 12373 |
|
| 12374 |
This option may actually be a list of commands. |
| 12375 |
The first one that exists and is executable is used. |
| 12376 |
That makes it possible to use the same configuration with Unix <EM>Alpine</EM> and |
| 12377 |
<EM>PC-Alpine</EM>. |
| 12378 |
<P> |
| 12379 |
|
| 12380 |
If none of the commands in the list exists and is executable then the rule |
| 12381 |
is <EM>not</EM> a match. |
| 12382 |
If it is possible that the command may not exist, you should be careful |
| 12383 |
to structure your rules so that nothing destructive |
| 12384 |
happens when the command does not exist. |
| 12385 |
For example, you might have a filter that filters away spam when there is |
| 12386 |
a match but does nothing when there is not a match. |
| 12387 |
That would continue to work correctly if the command didn't exist. |
| 12388 |
However, if you have a filter which filters away spam when there is not |
| 12389 |
a match and keeps it when there is a match, that would filter everything |
| 12390 |
if the categorizer command didn't exist. |
| 12391 |
<P> |
| 12392 |
|
| 12393 |
The categorizer command is run and the result is the exit status of |
| 12394 |
that command. |
| 12395 |
If that exit status falls in the <EM>Exit Status Interval</EM> |
| 12396 |
then it is considered a match, otherwise it is not a match. |
| 12397 |
Of course for the entire rule to match, it must also be checked against |
| 12398 |
the other defined parts of the Pattern. |
| 12399 |
<P> |
| 12400 |
The <EM>Exit Status Interval</EM> defaults to the single value 0 (zero). |
| 12401 |
If you define it, it should be set to something like: |
| 12402 |
<P> |
| 12403 |
<CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER> |
| 12404 |
<P> |
| 12405 |
where "min_exit_value" and "max_exit_value" are integers. |
| 12406 |
The special values "INF" and "-INF" may be used for large |
| 12407 |
positive and negative integers. |
| 12408 |
<P> |
| 12409 |
Actually, a list of intervals may be used if you wish. |
| 12410 |
A list would look like |
| 12411 |
<P> |
| 12412 |
<CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER> |
| 12413 |
<P> |
| 12414 |
When there is an <EM>Exit Status Interval</EM> defined, it is a match if the exit status |
| 12415 |
of the categorizer command is contained in any of the intervals. |
| 12416 |
The intervals include both endpoints. |
| 12417 |
<P> |
| 12418 |
The default interval is |
| 12419 |
<P> |
| 12420 |
<CENTER><SAMP>(0,0)</SAMP></CENTER> |
| 12421 |
<P> |
| 12422 |
and it matches only if the command exits with exit status equal to zero. |
| 12423 |
<P> |
| 12424 |
It is also possible to set a <EM>Character Limit</EM> for the categorizer command. |
| 12425 |
Setting this option makes it possible to limit how much of the message |
| 12426 |
is made available to the categorizer command as input. |
| 12427 |
The default value (-1) means that the entire message is fed to the |
| 12428 |
command. |
| 12429 |
A value of 0 (zero) means that only the headers of the message are |
| 12430 |
made available. |
| 12431 |
A positive integer means that the headers plus that many characters from |
| 12432 |
the body of the message are passed to the categorizer. |
| 12433 |
<P> |
| 12434 |
|
| 12435 |
</DL> |
| 12436 |
|
| 12437 |
<H2><A NAME="configuring-news"></A>Configuring News</H2> |
| 12438 |
|
| 12439 |
<EM>Alpine</EM> can access news folders in any one of three different ways: |
| 12440 |
<DL> |
| 12441 |
<DT>REMOTE NNTP</DT> |
| 12442 |
<DD>Using the Network News Transport Protocol (NNTP) to |
| 12443 |
access news on a remote news server. In this case the newsrc file is |
| 12444 |
stored on the machine where <EM>Alpine</EM> is running. |
| 12445 |
|
| 12446 |
<P> |
| 12447 |
To specify a remote news-collection accessed via NNTP use the |
| 12448 |
SETUP/collectionList screen's "Add" command. Set the |
| 12449 |
Server: value to the NNTP server's hostname appended with the |
| 12450 |
communication method "/service=NNTP", and set the Path: |
| 12451 |
value to the "#news." namespace (without the quotes). |
| 12452 |
<P> |
| 12453 |
Instead of specifying a news-collection, you may simply set the |
| 12454 |
<A HREF="#nntp-server">nntp-server</A> |
| 12455 |
option, which will cause <EM>Alpine</EM> to create a default news-collection for you. |
| 12456 |
Another NNTP option which may be of interest is |
| 12457 |
<A HREF="#nntp-range">nntp-range</A>. |
| 12458 |
|
| 12459 |
<DT>REMOTE IMAP</DT> |
| 12460 |
<DD>Using the Internet Message Access Protocol (IMAP) to |
| 12461 |
access news on a remote news server. In this case, your newsrc file is |
| 12462 |
stored on the news server, in your home directory, so you must have an |
| 12463 |
account on the news server, but you would be running <EM>Alpine</EM> on a different |
| 12464 |
machine. The news server must be running an IMAPd server process. |
| 12465 |
|
| 12466 |
<P> |
| 12467 |
To specify a remote news-collection accessed via IMAP use the |
| 12468 |
SETUP/collectionList screen's "Add" command. Set the |
| 12469 |
Server: value to the IMAP server's hostname, and set the Path: value |
| 12470 |
to the "#news." namespace (without the quotes). |
| 12471 |
|
| 12472 |
</DD> |
| 12473 |
|
| 12474 |
<DT>LOCAL</DT> |
| 12475 |
<DD>Using local file access to the news database. In this |
| 12476 |
case, your newsrc file is stored on the news server, in your home |
| 12477 |
directory, so you must have an account on the news server, and you would |
| 12478 |
be running <EM>Alpine</EM> on the same machine. |
| 12479 |
|
| 12480 |
<P> |
| 12481 |
To specify a local news-collection use the SETUP/collectionList |
| 12482 |
screen's "Add" command. Leave the Server: value blank, and |
| 12483 |
set the Path: value to the "#news." namespace (without the |
| 12484 |
quotes). |
| 12485 |
|
| 12486 |
</DD> |
| 12487 |
</DL> |
| 12488 |
|
| 12489 |
<P> |
| 12490 |
|
| 12491 |
NOTE: Should no news-collection be defined as above, <EM>Alpine</EM> will |
| 12492 |
automatically create one using the Setup/Config screen's |
| 12493 |
"nntp-server" variable's value if defined. The collection |
| 12494 |
will be created as a "Remote NNTP" as described above. |
| 12495 |
|
| 12496 |
<P> |
| 12497 |
|
| 12498 |
If you are a <EM>PC-Alpine</EM> user, either option 1 (NNTP) or option 2 (IMAP) is |
| 12499 |
possible. If you don't have an account on the news server, or if the news |
| 12500 |
server is not running an IMAP daemon, then you must use NNTP. (If you are not |
| 12501 |
sure, ask your service provider, university, or company for help.) In |
| 12502 |
this case, your Unix .newsrc file can be transferred to your PC. A good |
| 12503 |
place to put it would be in the same directory as your PINERC file, under |
| 12504 |
the name NEWSRC, but you can |
| 12505 |
<A HREF="#newsrc-path">specify a different location</A>. |
| 12506 |
|
| 12507 |
<P> |
| 12508 |
Other configuration features related to news are |
| 12509 |
<A HREF="#enable-8bit-nntp-posting">Enable-8bit-Nntp-Posting</A>. |
| 12510 |
<A HREF="#compose-sets-newsgroup-without-confirm">Compose-Sets-Newsgroup-Without-Confirm</A>, |
| 12511 |
<A HREF="#news-approximates-new-status">News-Approximates-New-Status</A>, |
| 12512 |
<A HREF="#news-deletes-across-groups">News-Deletes-Across-Groups</A>, |
| 12513 |
<A HREF="#news-offers-catchup-on-close">News-Offers-Catchup-On-Close</A>, |
| 12514 |
<A HREF="#news-post-without-validation">News-Post-Without-Validation</A>, |
| 12515 |
<A HREF="#news-read-in-newsrc-order">News-Read-in-Newsrc-Order</A>, and |
| 12516 |
<A HREF="#quell-extra-post-prompt">Quell-Extra-Post-Prompt</A>. |
| 12517 |
|
| 12518 |
<HR> |
| 12519 |
|
| 12520 |
<!-- pnuts --> |
| 12521 |
|
| 12522 |
</BODY> |
| 12523 |
</HTML> |