| blob | 1ec429fed4e16a2371f617d623e741957478025c |
1 # $Id: pine.hlp 1266 2009-07-14 18:39:12Z hubert@u.washington.edu $
2 #
3 # T H E A L P I N E M E S S A G E S Y S T E M
4 #
5 #/* ========================================================================
6 # * Copyright 2013-2015 Eduardo Chappa
7 # * Copyright 2006-2008 University of Washington
8 # *
9 # * Licensed under the Apache License, Version 2.0 (the "License");
10 # * you may not use this file except in compliance with the License.
11 # * You may obtain a copy of the License at
12 # *
13 # * http://www.apache.org/licenses/LICENSE-2.0
14 # *
15 # * ========================================================================
16 # */
17 #
18 Help text for the Alpine mailer
20 This file is in a format created to be turned into text strings in a C
21 program.
23 There are two shell scripts that run on this. Cmplhelp.sh is the
24 first and turns this into a C file (helptext.c) of text strings that
25 are compiled and linked. The other program, cmplhlp2.sh, turns this
26 into a .h file (helptext.h) with extern string definitions of the
27 strings in the .c file. The code that actually processes these files
28 while alpine is running is in help.c
30 The lines with "===== xxxx ====" divide the different help screens. The
31 xxx is the name of the variable that strings will be put in, which are
32 also declared in helptext.h.
34 # is a comment
36 Help text screen text can be either plain text OR HTML. The latter is
37 denoted by the first line starting with "<HTML>". The former is simply
38 displayed as it's formatted here.
40 HTML is limited to simple formatting ala HTML 2.0. No forms, or tables.
41 In addition a small set of tools are are available to customize the HTML
42 screen's text:
44 1a) Default and function key bindings are separated like this:
46 <!--chtml if pinemode="function_key"-->
47 Function key bindings here
48 <!--chtml else-->
49 Default key bindings here
50 <!--chtml endif-->
53 1b) A way to distinguish HTML text that is to be displayed when
54 pine is running vs. when the text is served up outside Alpine
55 (someday) can be done via:
57 <!--chtml if pinemode="running"-->
58 Text displayed when viewed within a running pine session
59 <!--chtml else-->
60 Text displayed when HTML viewed outside pine (using chtml aware server)
61 <!--chtml endif-->
63 1c) A way to distinguish HTML text that is to be displayed under
64 PC-Alpine vs. not is available via:
66 <!--chtml if pinemode="os_windows"-->
67 Text displayed under PC-Alpine
68 <!--chtml else-->
69 Text displayed otherwise
70 <!--chtml endif-->
72 WARNING ABOUT CHTML "if-else-endif" CLAUSES: They don't nest.
74 2a) Several "server side include" commented elements are supported:
76 <!--#include file="textfile"-->
78 The file "textfile" will be inserted into the HTML text directly.
79 Alpine does no formatting of the text. At some point we might want to
80 look at the first line for <HTML> but not today.
82 2b) Various bits of Alpine's running state can be inserted into the
83 HTML text as well using the special comment:
85 <!--#echo var="variable"-->
87 Where "variable" is one of either:
89 ALPINE_VERSION
90 ALPINE_REVISION
91 ALPINE_COMPILE_DATE
92 ALPINE_TODAYS_DATE
93 C_CLIENT_VERSION
94 _LOCAL_FULLNAME_
95 _LOCAL_ADDRESS_
96 _BUGS_FULLNAME_
97 _BUGS_ADDRESS_
98 CURRENT_DIR
99 HOME_DIR
100 PINE_CONF_PATH
101 PINE_CONF_FIXED_PATH
102 PINE_INFO_PATH
103 MAIL_SPOOL_PATH
104 MAIL_SPOOL_LOCK_PATH
105 VAR_<VARNAME> - where <VARNAME> is config variable name
106 FEAT_<FEATURENAME> - where <FEATURENAME> is config feature name
108 3) The URL scheme "X-Alpine-Gripe:" is available to insert links to
109 pine's composer such that various debugging data can be attached to the
110 message. Aside from normal email addresses, this can be set to
111 either "_LOCAL_ADDRESS_" for the configured local help address, or
112 "_BUGS_ADDRESS_" for the configured local bug reporting address.
113 Aside from the special tokens above, the default behavior only differs
114 from "mailto:" by the insertion of a special Subject: prefix that
115 consists of a randomly-generated token for tracking purposes.
116 Several optional parameters can be included to control what is
117 attached or offered for attachment to the message:
119 ?config -- Automatically attaches the user's configuration
120 information to the trouble report
121 ?keys -- Automatically attaches the user's most recent
122 keystrokes
123 ?curmsg -- Causes the user to get an offer to attach the
124 current message to the trouble report
125 ?local -- Automatically attaches the result of the script
126 defined by VAR_BUGS_EXTRAS
128 For HTML-format sections, the help screen dividers "===== xxxx ====" must
129 contain one and only one space after the first and before the second set of
130 equal signs.
132 Note to authors of this file: to mark sections that need further revision,
133 please use the text string on the following line consistently so that it is
134 easy to find those places again in this file:
135 *revision needed*
137 NOTE: Several sections of help text which weren't being used were removed
138 at RCS version number 4.122. In particular, there were some placeholders
139 with help text for the config screen and the composer that didn't have any
140 reasonable place to be called from.
141 Dummy change to get revision in pine.hlp
142 ============= h_revision =================
143 Alpine Commit 115 2015-12-07 00:01:48
144 ============= h_news =================
145 <HTML>
146 <HEAD>
147 <TITLE>RELEASE NOTES for Alpine</TITLE>
148 </HEAD>
149 <BODY>
150 <H1>Alpine Release Notes</H1>
151 <DIV ALIGN=CENTER>
152 Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)
153 <BR>
154 <!--chtml if pinemode="running"-->
155 (built <!--#echo var=ALPINE_COMPILE_DATE-->)
156 <!--chtml endif-->
158 <BR>
159 <BR>Copyright 2013-2015 Eduardo Chappa
160 <BR>Copyright 2006-2008 University of Washington
161 </DIV>
163 <P>
164 Alpine is an "Alternatively Licensed Program for Internet
165 News and Email" produced until 2009 by the University of Washington.
166 It is intended to be an easy-to-use program for
167 sending, receiving, and filing Internet electronic mail messages and
168 bulletin board (Netnews) messages. Alpine is designed to run on a wide
169 variety of Unix® operating systems. A version for Microsoft Windows®
170 is available as is a world wide web based version designed to run under the
171 Apache web server.
174 <H2>New in Alpine <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)</H2>
176 Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)
177 addresses bugs found in previous releases and has a few additions as well.
179 <P>
180 Additions include:
181 <UL>
182 <LI> PC-Alpine: New configuration option "Aspell Dictionaries" allows a
183 user to choose the dictionary used to spell, in case the user
184 communicates in more than one language. Examples of values for the
185 variable are "en_US" or "de_DE", etc. Only the first 10
186 dictionaries are offered.
188 <LI> Ignore message from smtp server after a successful authentication
189 challenge.
191 <LI> If SSLDIR is defined somehow, do not disable S/MIME if the
192 SSLCERTSDIR is not found.
194 <LI> When Alpine sends an attachment, it will set the boundary attribute
195 in lower case, as some SMTP servers, such as those of libero.it
196 reject messages if the boundary attribute is in uppercase.
198 <LI> SMIME: The ^E command that gives infromation on the certificate
199 is only available for messages that have a signed or encrypted
200 part.
202 <LI> SMIME: If a message contains a RFC822 atachment that is
203 signed/decrypted add the ability to view its SMIME information.
205 <LI> SMIME: Certificate information in the S/MIME screen is available
206 for certificates stored in a container.
208 <LI> SMIME: Offer the common name of the person, instead of the name of
209 file containing the certificate, as the name to be displayed in the
210 certificate management screen for certificate authorities.
211 Suggested by Matthias Rieber.
213 <LI> SMIME: Management of several alternate name (SAN) certificates is
214 improved. When importing a SAN certificate, also import a certificate
215 for the filename, besides for the e-mail addresses in the
216 certificate. Suggested by Matthias Rieber.
218 <LI> SMIME: add full year when displaying information about a certificate
219 in the certificate management screen. Suggested by Matthias Rieber.
221 <LI> SMIME: sort certificates by some type of alphabetical order in the
222 displayed name.
224 <LI> SMIME: Alpine will ask users if they wish to save S/MIME
225 certificates included in signatures, when the option "Validate
226 Using Certificate Store Only" is enabled. If the user does not wish
227 to save it, validation will fail.
229 <LI> HTML: Add support for decoding entities in hexadecimal notation.
230 Suggested by Tulipánt Gergely.
232 <LI> If the charset of a message can not be determined, use the value set
233 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value.
235 <LI> Resizing setup screen will redraw screen.
237 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
238 in the width ambiguous zone, it will use other means to determine
239 the width, such as call wcwidth.
241 <LI> Pico: Code reorganization in the search command to make it easier to
242 add subcommands of the search command.
244 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^
245 subcommand of the search command to bring this choice into view.
247 <LI> Pico: Add the ability to search for strings in the beginning or end
248 of a line. Use the Ctrl-^ subcommand of the search command to bring
249 this choice into view.
251 <LI> For a multipart/alternative message, the Take Address command will
252 work on the part that is being read.
254 <LI> When sending a message, allow for 512 characters of consecutive
255 non-white space before folding the subject line.
257 <LI> Make sure titlebar (the line at the top of the screen) always
258 contains the name of the folder/newsgroup that is open, if this
259 fits in the title.
261 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
262 will also scramble the name, version and operative system in the message-id header.
263 Based on a contribution by Dennis Davis, which is itself based on a contribution by
264 Mark Hills.
266 <LI> Change in logic in imap_set_password function to make Alpine ask if
267 a user wants to save a password before reading the password file.
269 <LI> Add the Control-R subcommand to the save command for attachments.
270 This subcommand toggles if the saving will be done in binary mode
271 for text attachments. When a user saves an attachment using binary
272 mode it will be saved as it was sent, otherwise the attachment will
273 be transformed to UTF-8 for further transformation through internal
274 and user defined filters for saving.
276 <LI> Add command line argument -smimedir, which allows to specify
277 the default path for a directory that contains the public, private,
278 and ca directories. This is useful in case a user has a backup of
279 old certificates that cannot be installed in the ~/.alpine-smime
280 dir.
282 <LI> Reimplementation of the code that allows the .pinerc file to be a
283 symbolic link by Kyle George from tcpsoft.com to use realpath.
285 <LI> When saving an attachment, the "^T" command leads to a screen where the
286 "A" command can be used to add a file. A directory can be added by
287 pressing "^X" after the "A" command. Added after a suggestion by
288 Stefan Goessling.
290 <LI> When saving an attachment, the ^Y and ^V commands allow a user to
291 scroll through the history of directories used to save attachments,
292 while preserving the given name of the file. Suggested by Peter
293 Koellner.
295 <LI> SMIME: Turn off automatic signing and encrypting of a message when
296 bouncing. Suggested after a discussion with Matthias Rieber.
297 </UL>
300 <P>
301 Bugs that have been addressed include:
302 <UL>
303 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also
304 Alpine will use the function ASN1_TIME_print to determine the date
305 of validity. Reported by Ben Stienstra.
307 <LI> SMIME: Crash when atempting to unlock the password file and an
308 incorrect password is entered.
310 <LI> SMIME: Crash when checking the signature of a message that contains
311 a RFC822 attached message. Reported by Holger Trapp and Björn
312 Krellner.
314 <LI> SMIME: Cancelling entering password to unlock key will not reprompt.
316 <LI> SMIME: fix a bug that did not allow users to transfer certificates to
317 remote containers. Reported by Matthias Rieber.
319 <LI> SMIME: certificates included in messages were not being transferred
320 to a remote container.
322 <LI> SMIME: Crash if public certificates are located in an inaccessible
323 remote server and the private key is not available.
325 <LI> SMIME: Alpine does not remove remporary files created when adding a
326 CA certificate to a container. Reported by Holger Trapp.
328 <LI> Pico: Searching for a string that is too long causes Pico to crash
329 in the next search.
331 <LI> Fix vulnerability in regex library. This only affects those who use
332 this library, such as the windows version of Alpine. See
333 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A>
334 for more details.
336 <LI> Alpine would not set include and lib paths for OpenSSL if this was
337 installed in /usr/local/ssl.
339 <LI> If the .pinerc file is a symbolic link, Alpine might not write its
340 contents when saving its configuration.
342 <LI> The _INIT_ token does not skip over non-alpha numeric characters in
343 the name. Reported by Andreas Fehr.
345 <LI> Mismatch in size of UCS and CELL caused a corruption in the
346 content of a pointer, which made the speller in PC-Alpine get the
347 content of a word incorrectly.
349 <LI> Skip testing openssl compatibility version when cross-compilation
350 is detected. Fix contributed by Antti Seppälä
352 <LI> Alpine fails to remove temporary files used during a display or sending
353 filter. Fix contributed by Phil Brooke.
355 <LI> When the index is in zoomed state, adding new messages to the
356 selection would not show those messages if those messages are on
357 top of the current message in the top of the screen. Reported by
358 Ulf-Dietrich Braumann. In addition, when the user scrolls through
359 the index, this scroll smoothly, without jumping pages. Reported
360 by Holger Trapp.
362 <LI> Crash when reviewing history of saving attachments.
364 <LI> Crash in Pico when forwarding messages that contain a direction mark
365 at the end of a line. Reported by James Mingo.
367 <LI> Solve compilation errors when Alpine is built with Visual Studio 2015.
368 </UL>
371 <P>
372 Version 2.20 addresses bugs found in previous releases and has several
373 additions as well.
375 <P>
376 Additions include:
377 <P>
379 <UL>
380 <LI> Upgrade UW-IMAP to Panda IMAP from
381 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
382 <LI> S/MIME: Add screen to manage certificates.
383 <LI> S/MIME: Signatures are validated using the user's certificates instead
384 of the ones included in the message. Behavior can be disabled by
385 disabling the option <A href="h_config_smime_use_cert_store">
386 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled
387 by default.
388 <LI> S/MIME: sign messages using intermediate certificates when needed
389 and possible.
390 <LI> S/MIME: validation of certificates for servers that modify signed
391 content.
392 <LI> S/MIME: signed and encrypted messages will be signed first and
393 encrypted second, so that they can be decoded by other clients.
394 <LI> S/MIME: add the sender certificate to the list of certificates in
395 encrypted messages to make it possible for the sender to decrypt
396 the message they sent.
397 <LI> S/MIME: When transferring certificates to a local container, create
398 container with default names PublicContainer, PrivateContainer and
399 CAContainer, as appropriate for these files, unless the user has
400 provided some other names.
401 <LI> S/MIME: Forwarding a message will include the signed part as part
402 of the text and not as a multipart message, just as the reply
403 command does.
404 <LI> HTML: Style tag in body of html message causes Alpine to not write
405 its content until a new </style>
406 <LI> HTML: <BR>, <BR />, and <BR/> are considered
407 the same inline tag; the same is valid for the <HR> tag.
408 <LI> Add support to selective expunge through a subcommand of the
409 select-apply commands. Read more in the <A
410 HREF="h_index_cmd_expunge">help</A> for the expunge command.
411 <LI> Pico: New subcommand of the search command, allows to reverse the
412 direction of search.
413 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled,
414 the key and certificate used to encrypt the password file are saved
415 in the ~/.alpine-smime/.pwd directory, or in the directory specified
416 by the -pwdcertdir command line option.
417 <A HREF="h_password_file_support">Learn more</A>.
418 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
419 server to use different ways to connect using ssl, for
420 example {server.com/tls1} will attempt to connect to
421 server.com at the ssl imap port (port 993) and establish a
422 connection using TLSv1. These flags can be used in
423 conjunction with the /ssl flag, the ssl flag is redundant.
424 Conversely, however, the /ssl flag does not imply any of
425 these flags; the /ssl flag means SSLv3 or, if not available,
426 SSLv2 in the SSL port.
427 <LI> Alpine does not attempt to automatically reopen a collection
428 that was not opened due to cancellation by the user.
429 Instead, the user must try to open it explicitly.
430 <LI> Alpine searches for a certificate that matches an email address in
431 all addresses in a certificate (instead of just the first
432 one) but when it tries to unlock the certificate, it asks
433 for the password for the first email address in that
434 certificate.
435 <LI> Style tag in body of html message causes Alpine to not write its content
436 until a new </style>
437 <LI> Experimental: Write the content-type of a message in
438 lowercase, as some non-compliant servers do not understand
439 uppercase content-type, such as those of GMX.de.
440 <LI> Experimental: Do not send the RSET command before attempting
441 to send a message, as this causes a delay in some evily managed
442 servers.
443 <LI> Opening a folder updates recent count in maildrops (this
444 already works for other types of folders)
445 <LI> Automatically redraw screen after opening an attachment
446 instead of simply clearing it.
447 <LI> Pico: Justification works without need of a predefined quote
448 string. This allows justification of blocks of text that are
449 indented with spaces.
450 <LI> Decode the name of attachment names, so they can be written as part
451 of the description of the part.
452 <LI> Check bounds and tie strings off to improve security. Contributed
453 by James Jerkins.
454 <LI> Replace tabs by spaces in From and Subject fields to control for
455 size in screen of these fields. Change only in index screen display.
456 <LI> Aggregate operations allows bouncing a list of messages using a role.
457 Suggested by Ulf-Dietrich Braumann.
458 <LI> Disable saving new passwords to the password file. Implemented
459 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A>
460 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload,
461 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by
462 Charles M. Register.
463 </UL>
466 <P>
467 Bugs that have been addressed include:
468 <UL>
469 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
470 in personal names. Reported by Lev Gorenstein.
471 <LI> When writing the .pinerc file, lines were truncated if they were longer
472 than 10,000 characters. This could cause data corruption, so now lines
473 are allowed to be of any length.
474 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
475 remove attachments before they were open by a mailcap viewer. It
476 requires that the user has an equivalent to a command such as "ps
477 auxww" to list the list of processes, and check if there is any
478 program using the attachment. The default is "/bin/ps auxww", but
479 it can be changed at compile time with the option --with-ps-cmd.
480 See the help of the variable
481 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
482 for more information.
483 <LI> S/MIME: signed messages that contained an attachment would not validate.
484 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
485 validate. Thanks to Andreas Schamanek for testing, debugging and
486 advising during the process of fixing this problem.
487 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
488 with "Error writing pipe" message. Reported by Andreas Schamanek
489 and Stefan Mueller.
490 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
491 home directory.
492 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize
493 SMIME making it not possible to sign or encrypt messages.
494 <LI> S/MIME: Forwarding a signed message might make the body contain mime
495 information that is not part of the body, and hence making the body
496 of the message seem wrong.
497 <LI> S/MIME Alpine would compute incorrectly the signature of a message
498 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is
499 enabled, the message contains 8bit characters and the smtp server
500 supports 8bit sending.
501 <LI> When replying to several messages, subject will be decoded first,
502 and then stripped from re/fwd before they are compared to determine
503 the subject of the replied message.
504 <LI> Crash when tcp connection to NNTP server was lost after connection
505 had been established, but lost immediately afterwards.
506 <LI> Crash with message "lock when already locked", when painting
507 an index was based on scores that needed information from a remote
508 addressbook in the same server as the folder opened. Reported by
509 Peter Koellner.
510 <LI> Crash in message/rfc822 attachments encoded in base64.
511 <LI> Postponed messages whose content-type is text/html, text/enriched and
512 text/richtext are sent with that content-type, even though, after
513 resuming composition, Alpine had changed its type to text/plain.
514 <LI> Alpine cannot handle correctly some characters in the Windows-1256
515 character set, which might lead to a crash or a corruption in the
516 screen. Work was done to contain the bug. A more complete fix will
517 be done in a future release. Reported by Professor Robert Funnell.
518 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
519 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway.
520 <LI> Save command did not warn of existence of a message with a deleted
521 attachment in an aggregate save, unless cursor was positioned on a message
522 with a deleted attachment. Reported by Florian Herzig.
523 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
524 in an IMAP server.
525 <LI> DATE tokens were not internally transformed to UTF-8, which made their
526 values not appear complete in the screen. Reported by Werner Scheinast.
527 <LI> Fixes to configure script so that it will not require PAM for every system.
528 <LI> Fix to configure script so that it will use CPPFLAGS instead of
529 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
530 during the build. Fix by Ulf-Dietrich Braumann.
531 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
532 needs to use tcl_getstringresult() instead. Reported by
533 Ulf-Dietrich Braumann.
534 <LI> Quoted string in URL Viewers configuration variable were not
535 unquoted before passing to viewer.
536 <LI> Fix in configure script to detect location of tcl library; add
537 /usr/local in FreeBSD and fix a bug in configure script that used
538 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
539 by Werner Scheinast.
540 <LI> Move SSL configurations from UW-IMAP to configure script, and
541 update OpenSSL configuration for Mac OS X.
542 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
543 <LI> When the download of an attachment is interrumpted, Alpine stills
544 caches what was downloaded, making the download incomplete for
545 subsequent calls of Alpine attempting to open the attachment. In the
546 future, Alpine will not cache any downloaded part of the attachment
547 when it is interrupted.
548 </UL>
549 <P>
552 <P>
553 Version 2.11 addresses bugs found in previous releases and has a few
554 additions as well.
556 <P>
557 Additions include:
558 <P>
560 <UL>
561 <LI> Alpine requires version 1.0.0c of Openssl to build.
562 <LI> Increase encryption of S/MIME encrypted messages.
563 <LI> Pico: Improvements in justification of paragraphs: lines that begin
564 with a quote string, followed by a space were considered individual paragraphs,
565 now they are considered part of a paragraph. Based on earlier joint work
566 with Jeff Franklin.
567 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
568 <LI> Experimental extended support of recognition of UTF-8 in urls based on
569 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
570 <LI> Added recognition of ws and wss URIs.
571 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
572 <A HREF="h_config_directory_color">directory names</A>,
573 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
574 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
575 used in the display of the INDEX SCREEN.
576 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
577 that adds the ability to preserve To: and Cc: fields when replying to a
578 message, as specified by original sender.
579 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
580 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
581 <LI> Quota command includes subcommands for printing, forwarding, etc.
582 </UL>
584 <P>
585 Bugs that have been addressed include:
586 <P>
587 <UL>
588 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
589 <LI> Crash when resizing the screen in a configuration screen.
590 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
591 <LI> Do not use a shell to open a browser.
592 <LI> Configure script did not test for crypto or pam libraries.
593 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
594 <LI> Change Cygwin directory separator to "/".
595 <LI> Alpine could set List- headers, contrary to RFC 2369.
596 </UL>
598 <P>
599 Version 2.10 addresses bugs found in previous releases and has a few
600 additions as well.
602 <P>
603 Additions include:
604 <P>
606 <UL>
607 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
608 <LI> Search a folder for the content of any header with the ";" command.
609 <LI> Foreign characters are decoded correctly in IMAP folder names.
610 <LI> Question about breaking connection to slow servers includes their name.
611 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
612 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
613 <LI> Cygwin: Alpine builds without need of patch.
614 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
615 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
616 <LI> Add support for strong encryption of password file when S/MIME is built in.
617 </UL>
619 <P>
620 Bugs that have been addressed include:
621 <P>
623 <UL>
624 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
625 <LI> Double allocation of memory in Pico.
626 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
627 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
628 <LI> Not recognition of environment variables in some options.
629 <LI> Not display of login prompt during initial keystrokes.
630 <LI> justification of long urls breaks them.
631 <LI> Incorrect New Mail message when envelope is not available.
632 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
633 <LI> Crash when resizing the screen after display of LDAP search.
634 <LI> Crash when redrawing screen while opening a remote folder collection.
635 <LI> Infinite loop in scrolltool function during notification of new mail.
636 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
637 <LI> No display of signed and encrypted S/MIME messages.
638 <LI> Alpine will not build with OpenSSL.
639 <LI> Crash for double locking in calls to c-client.
640 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
641 <LI> Ignore the references header when threading messages
642 <LI> No update of colors in index screen after update to addressbook.
643 </UL>
645 <P>
646 Version 2.01 addresses bugs found in previous releases and has a few
647 additions as well.
649 <P>
650 Additions include:
651 <P>
653 <UL>
654 <LI> Fixed non-ASCII web alpine handling
655 <LI> Added web alpine help.
656 <LI> Allow web alpine inbox on second IMAP server.
657 <LI> Allow web alpine config reset after bad inbox-path gets set.
658 <LI> Added web alpine ability to create group contact from contact list members.
659 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
660 <LI> Tidied up web alpine script layout.
661 <LI> Fixed web alpine status message ordering
662 <LI> Added web alpine Fcc setting via Contacts in Compose
663 <LI> Fixed web alpine autodraft attachment issues
664 <LI> Fixed web alpine problems with recent count maintenance
665 <LI> Fixed web alpine newmail arrival display in message list
666 <LI> Added web alpine confirmation to folder create for Move/Copy
667 <LI> Added web alpine user-domain support
668 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
669 </UL>
671 <P>
672 Bugs that have been addressed include:
673 <P>
675 <UL>
676 <LI> In web alpine fixed delete all selected within a search result to reorient
677 correctly to whole-mailbox message list.
678 <LI> Fixed web alpine delete in view page to be sensitive to sort
679 <LI> Fixed web alpine open of folder within directory from folder manager page.
680 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
681 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
682 <LI> Fixed web alpine adding contacts from message list and view
683 <LI> Fixed web alpine create of non-existent fcc
684 <LI> Remove mistakenly left debugger statement in web alpine javascript.
685 <LI> Some UNIX alpine build problems fixed
686 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
687 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
688 by locale charmap call on some Solaris 8 systems.
689 <LI> MacOS Keychain logins were not working correctly with generic host names, like
690 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
691 new password requests when not needed
692 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
693 last folder in the list
694 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
695 looked for along with the email address
696 <LI> Changes to configure to get spellcheck options with work with arguments.
697 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
698 returned by gethostname (iPhone can do this)
699 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
700 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
701 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
702 Jake Scott of marganstanley.com.
703 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
704 is not used in alpine.
705 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
706 Apparently this causes RIM Blackberry BIS service problems. This is not
707 used in alpine.
708 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
709 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
710 Fix from Ludwig Nussel of SUSE and from Crispin.
711 <LI> Include whole filename in export filename history
712 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
713 </UL>
715 <P>
716 Version 2.00
717 addressed bugs found in previous releases and had a few additions as well.
718 <P>
719 Additions included:
720 <P>
722 <UL>
723 <LI> Redesigned Web Alpine interface
724 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
725 in UNIX versions of Alpine
726 <LI> Attempt to include the attachment filename as part of the name of the
727 temporary file used when viewing an attachment with an external program.
728 Add some randomness to that filename to make it hard to predict the filename.
729 Add a filename extension, usually derived from the type/subtype, to the
730 temporary filename. This was previously done only on Windows and MacOS X.
731 <LI> Enhance address completion in the composer (TAB command) so that it looks
732 through nicknames, fullnames, and addresses from the address book; addresses
733 from the message being viewed, if any; and the results from
734 <A HREF="h_direct_config">LDAP Directory Server</A>
735 lookups for all of the defined directory servers that have the
736 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
737 feature set.
738 <LI> Make the default character set setting more liberal in what it will accept
739 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
740 <LI> Remove the Alpine revision number from the titlebar in released versions
741 while leaving it there in snapshot versions
742 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
743 display of asterisks when you type a password for Alpine
744 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
745 <LI> When the
746 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
747 feature is turned on convert not only the dates in the index screen but also
748 the dates in the MESSAGE VIEW
749 </UL>
751 <P>
752 Bugs addressed in the 2.00 release included:
753 <P>
755 <UL>
756 <LI> Crash when using tab-completion for selecting a Save filename
757 <LI> Make Web Alpine help text images relative for more portability
758 <LI> Fixed attach save of html parts in Web Alpine
759 <LI> Viewing, printing, exporting, replying, and bouncing of message
760 digests was broken. Replying and bouncing should not have been
761 allowed at all for digests. It would be nice to have a more standard
762 index-like view of a message digest but that has not been addressed
763 with this minor bug fix.
764 <LI> Adjust wrapping of HTML messages so that the margins specified by
765 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
766 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
767 are observed correctly
768 <LI> Interrupt of WhereIs command in index was broken
769 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
770 option did not work correctly interpreting unknown characters in message headers
771 <LI> Long address lines could cause blank continuation lines
772 <LI> Save to a local default INBOX failed if the primary collection was also local,
773 which it is by default. The save went to ~/mail/inbox instead.
774 <LI> Make a default save folder of "inbox" always mean the real
775 inbox, not the inbox in the primary collection
776 <LI> Address book entries with lots of addresses would be truncated when
777 entered in the composer with a screen size wider than 270 or so charcters
778 <LI> Some fields in the index screen were truncated when the screen width was
779 wider than 256 characters
780 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
781 folder, and there is a more than 10 minute pause between typing the TAB
782 and typing the Yes
783 </UL>
785 <P>
786 Version 1.10(962)
787 addressed bugs found in previous releases and had a few additions as well.
788 <P>
789 Additions included:
790 <P>
792 <UL>
793 <LI> Add the possibility of setting a default role
794 (see <A HREF="h_role_select">Roles Screen</A>)
795 which may be convenient if your work flow involves acting in one
796 role for a while then switching to another role and staying in the
797 new role for another period of time
798 <LI> When Saving and the IMAP server problem "Message to save shrank!"
799 is encountered, ask the user if he or she wants to continue with the
800 risky Save anyway instead of aborting. This may be helpful if your
801 IMAP server is broken in this way but be aware that it is possible there
802 was a real error instead of just a broken server implementation.
803 <LI> Some configure adjustments for Kerberos detection and
804 for SCO OpenServer 5 support
805 <LI> Hide INBOX in a collection if it also appears as an
806 <A HREF="h_config_enable_incoming">Incoming Folder</A>
807 <LI> Show asterisks for feedback when the user is typing a password
808 <LI> Performance improvement for threading of large folders
809 <LI> Previously, the search used to find
810 Pattern matches containing To patterns searched for both To
811 and Resent-To headers. The relatively complicated search this
812 produces causes problems when using some deficient IMAP servers.
813 Now the default is to look only for To headers and ignore the
814 presence of Resent-To. The previous behavior may be restored
815 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
816 <LI> Add an
817 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
818 to help with reading malformed unlabeled messages
819 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
820 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
821 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
822 </UL>
824 <P>
825 Bugs addressed in the 1.10(962) release included:
826 <P>
828 <UL>
829 <LI> Crash when encountering certain errors from an SMTP server
830 <LI> Crash in composer caused by overflow in replace_pat()
831 <LI> Hang when authenticating to an SMTP server that fails with a
832 "connection disconnected" error
833 <LI> Bug in handling of trailing tab character in flowed text
834 <LI> Security enhancement for mailcap parameter substitution
835 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
836 did not work if the message being replied to was not flowed text
837 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
838 was not turned on
839 <LI> Don't allow printer to be changed through hidden config screen
840 if system administrator didn't want it to be allowed
841 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
842 should know that it won't work, causing error messages to appear
843 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
844 of double-quote double-quote didn't work right
845 <LI> Quoting wasn't being done to protect special characters from the
846 MacOS X shell when
847 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
848 was not defined
849 <LI> On MacOS X message attachments should be shown internally instead of
850 being shown using the Mail application
851 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
852 sometimes set the outgoing charset to X-UNKNOWN, making the result
853 unreadable
854 <LI> When the sending of a message failed lines with leading spaces had one
855 additional space inserted in each of those lines when the user
856 was returned to the composer
857 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
858 that contained non-ascii characters because it was truncating the
859 line being searched so that it was shorter than what was visible on
860 the screen
861 <LI> When composing, an attachment with a long name that causes wrapping in
862 just the wrong place would generate an error and cause the send
863 of the attachment to fail
864 <LI> After calling the file browser to attach a file in the composer, a resize
865 of the window when back in the composer would redraw the last screen that
866 had been shown in the browser instead of the current composer screen
867 <LI> Possible crash in index screen when encountering unparseable addresses
868 or when using one of the PRIORITY tokens or the HEADER token in the
869 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
870 <LI> Problems with Header Color editing if the configuration option
871 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
872 was inadvertently changed to the Empty Value in the hidden config screen
873 <LI> When resuming the final postponed message from an Exchange server the user
874 could get a certificate validation failure because alpine was trying
875 to validate the canonical name of the folder instead of the name the
876 user used
877 <LI> Windows line endings in a mimetypes file on a Unix system cause a
878 failure to find a match
879 <LI> Make matching of extension names case independent in mimetypes files
880 <LI> Windows dialog boxes for entering text were not working correctly
881 <LI> Replying to or Forwarding multipart/alternative messages which had a
882 single text/html part did not work well
883 <LI> Printing the print confirmation page caused a crash
884 <LI> A To line with a long, quoted personal name could display incorrectly
885 if it was close to the same width as the screen
886 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
887 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
888 are turned on hide (0/0) when the folder is empty
889 <LI> Folder completion while Saving didn't work if the collection being
890 saved to was the local home directory
891 </UL>
893 <P>
894 Version 1.00
895 was an evolutionary release based on
896 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
897 developed at the University of Washington.
898 It is upwards-compatible for existing Pine users.
900 <P>
901 Changes included:
902 <P>
903 <UL>
904 <LI> Ground-up reorganization of source code around addition
905 of "pith/" core routine library.
906 <LI> Fundamental improvement in Alpine's internal text handling, which
907 is now based exclusively on Unicode. This allows displaying incoming
908 messages and producing outgoing messages in many different languages.
909 <LI> Ground-up reorganization of build and install procedures
910 based on GNU Build System's autotools. NOTE, the included IMAP library
911 build is not based on autotools, so some features will not work. However,
912 it should get built automatically during the Alpine build process.
913 <LI> Web-based version included built on TCL designed to run under
914 a suitable CGI-supporting web server such as Apache.
915 </UL>
917 <P>
919 Details on changes in previous (prerelease) versions of Alpine
920 may be found at the following URL:
921 <P>
922 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP></CENTER>
923 <P>
925 <HR WIDTH="75%"><P>
927 <H2>Getting Help</H2>
928 <DL>
929 <DT>Online Help</DT>
930 <DD>
931 Every Alpine screen and command has associated help text
932 accessible via the "?" key (or Ctrl-G in text-input contexts).
933 </DD>
935 <DT>Web Help</DT>
936 <DD>
937 The most current source of information about Alpine,
938 including new version availability, is the web page at
939 <P>
940 <CENTER><SAMP><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></SAMP></CENTER>
941 </DD>
942 </DL>
944 Frequently Asked Questions (and answers) may be found at the following
945 URL:
946 <P>
947 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
948 <P>
950 <HR WIDTH="75%"><P>
952 <H2>Additional Information</H2>
954 General Alpine configuration information can be found
955 <A HREF="h_news_config">here</A>.
956 <P>
957 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
958 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
959 access is provided by the IMAP Toolkit Environment (c-client library)
960 version <!--#echo var="C_CLIENT_VERSION"-->.
961 <P>
962 Alpine was developed until 2009 by the Office of Computing
963 & Communications at the University of Washington in Seattle.
964 Since then, the effort of developing Alpine has been continued by
965 a community of volunteers who make good software even better!
967 <P>
968 Alpine Copyright 2013-2015 Eduardo Chappa,
969 <BR> Copyright 2006-2008 University of Washington.
971 <P>
972 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
973 or instead you can find the Apache License, version 2.0 at the web URL:
975 <P>
976 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
978 <P>
979 <End of Release Notes>
980 </BODY>
981 </HTML>
982 ====== h_password_file_support ======
983 <HTML>
984 <HEAD>
985 <TITLE>Encryption for Password File Support Explained</TITLE>
986 </HEAD>
987 <BODY>
988 <H1>Encryption for Password File Support Explained</H1>
990 Index<BR>
991 <OL>
992 <LI><A HREF="#content">Explanation</A>
993 <LI><A HREF="#example">Example</A>
994 </OL>
996 <P><A NAME="content">Unix Alpine Only.</A>
998 <P> If your version of Alpine has been built with password file support
999 then you can use a special file to save your passwords, and avoid typing
1000 them every time you open a connection to a remote server.
1002 <P> If your version of Alpine was built with SMIME support, and you have a
1003 public certificate/private key pair, then Alpine will use such pair to
1004 encrypt your password file. If you have more than one key/certificate
1005 pair, Alpine will pick the first pair that it finds that works. You can also
1006 select a pair, and the way to do this is explained below.
1008 <P> Once a pair has been chosen, it will be copied to the directory
1009 ~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in
1010 that directory. The first time this process is done, this directory will
1011 be created, a key/certificate pair will be copied to it, and this pair
1012 will be used in the future to encrypt and decrypt your password file. You
1013 can create this directory and copy any key/certificate pair there. You
1014 can add a self-signed certificate there, if you like, and you can let
1015 this certificate expire. This will not affect the encryption and decryption
1016 of the password file.
1018 <P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save
1019 your key/certificate pair, you can specify a different one with the
1020 -pwdcertdir command line option in Alpine. If the directory specified by
1021 this option is not found or there is no valid key/certificate pair there,
1022 Alpine will fail to encrypt and decrypt your password file. In other words,
1023 Alpine will not initialize this directory for you.
1025 <P> Alpine does not care about the names of the key and certificates in
1026 this directory, but the private key must have ".key" extension
1027 and your public certificate must have the ".crt" extension. The
1028 name of the private key will be used in the prompt when you are asked
1029 to unlock your key to decrypt your password.
1031 <P><A NAME="example">An example follows</A>
1033 <P>Assume you have a private key called peter@address.com.key in your,
1034 ~/.alpine-smime/private directory, and a public certificate called
1035 peter@address.com.crt in your ~/.alpine-smime/public directory, and these
1036 are your only key/certificate pair.
1038 <P> When Alpine starts for the first time, without command line options,
1039 it will check if the directory ~/.alpine-smime/.pwd exists, and if not,
1040 it will create it. Then it will go through your keys and certificates and
1041 find a pair that it can use, and copy the files peter@address.com.key,
1042 and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively
1043 you can do the same by copying these files by yourself. This can be done
1044 with the sequence of commands
1046 <PRE>
1047 mkdir ~/.alpine-smime/.pwd
1048 cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd
1049 cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd
1050 </PRE>
1052 <P> When Alpine starts, you will be asked the password to unlock your
1053 private key with the prompt.
1055 <PRE>
1056 Enter password of key <peter@address.com> to unlock password file:
1057 </PRE>
1059 <P> If you prefer to use different names for your private and public keys
1060 in the ~/.alpine-smime/.pwd directory, you can do so, but you must
1061 preserve the extension of the files. For example, you can use the names
1062 private_key.key and public_cert.crt instead. In this case, the prompt you
1063 will see when you are asked to unlock your private key will read
1065 <PRE>
1066 Enter password of key <private_key> to unlock password file:
1067 </PRE>
1069 <P>Observe that you do not need to use an existing key/certificate pair,
1070 and that you can create a new private key/public certificate pair to
1071 encrypt and decrypt your password. However, once one is used, Alpine does
1072 not provide a mechanism to switch the encryption and decryption files to
1073 another key/certificate pair. This will be implemented in a future
1074 release of Alpine.
1076 <P>
1077 <End of help>
1078 </BODY>
1079 </HTML>
1080 ====== h_tls_failure_details ======
1081 <HTML>
1082 <HEAD>
1083 <TITLE>Certificate Validation Details</TITLE>
1084 </HEAD>
1085 <BODY>
1086 <H1>Certificate Validation Details</H1>
1088 This screen gives details as to why the certificate validation failed: the
1089 name of the desired server system; the reason for failure; and the name on
1090 the certificate. This is primarily of interest to experts.
1092 <P>
1093 <End of help>
1094 </BODY>
1095 </HTML>
1096 ====== h_tls_failure ======
1097 <HTML>
1098 <HEAD>
1099 <TITLE>TLS or SSL Failure</TITLE>
1100 </HEAD>
1101 <BODY>
1102 <H1>TLS or SSL Failure</H1>
1104 An attempt was made to establish a secure, encrypted connection to the
1105 server system using either Transport Layer Security (TLS) or the older
1106 Secure Sockets Layer (SSL). This attempt failed.
1108 <P>
1109 You should contact your server system management for more assistance.
1110 The problem is probably at the server system and not in Alpine or your local
1111 system. The text in this screen may be helpful for the server system
1112 management in debugging the problem,
1114 <P>
1115 <End of help>
1116 </BODY>
1117 </HTML>
1118 ====== h_tls_validation_failure ======
1119 <HTML>
1120 <HEAD>
1121 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
1122 </HEAD>
1123 <BODY>
1124 <H1>TLS and SSL Certificate Validation Failures</H1>
1126 An attempt was made to establish a secure, encrypted connection to the
1127 server system using either Transport Layer Security (TLS) or the older
1128 Secure Sockets Layer (SSL).
1130 <P>
1131 An important part of this procedure is server certificate validation. A
1132 server certificate is an "electronic identification card" for the server
1133 system that is signed by a well-known certificate authority (CA). Alpine
1134 compares the server system identity in the server certificate with the
1135 name of the server system to which it is trying to connect. Alpine also
1136 verifies that the CA signature is authentic.
1138 <P>
1139 Some common failure conditions are:
1140 <P>
1142 <UL>
1143 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
1144 signed its own certificate. This does not necessarily indicate anything
1145 bad; the server operators may simply have elected to not purchase a
1146 signed certificate from a certificate authority.
1148 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
1149 the signature on the server system is from an unknown certificate authority.
1150 It can also mean that no certificate authority certificates have been
1151 installed on the local UNIX system.
1153 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
1154 the same as either of the above two conditions in UNIX Alpine. Note that
1155 Windows systems typically have a full set of certificate authority
1156 certificates installed, so it is more likely to be a self-signed
1157 certificate than an unknown certificate authority.
1159 <LI> Server name does not match certificate. This means that the server
1160 presented a proper signed certificate for a name other than the desired
1161 name.
1162 </UL>
1164 <P>
1165 Any of these conditions can indicate that you are being attacked and have
1166 been directed to an imposter server that will record your password and
1167 your private mail messages. It can also mean something innocuous.
1169 <P>
1170 If you are certain that the problem is innocuous, you can append the
1171 option
1173 <P>
1174 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
1175 <P>
1177 to the server system name where it appears in your configuration (e.g. the
1178 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
1179 a folder-collection, or a news or SMTP server). This will
1180 disable certificate validation. On the other hand, if you are attacked,
1181 you will get no warning if you do this.
1183 <P>
1184 <End of Cert Validation Failures help>
1185 </BODY>
1186 </HTML>
1187 ====== h_release_tlscerts ======
1188 <HTML>
1189 <HEAD>
1190 <TITLE>TLS and SSL usage note</TITLE>
1191 </HEAD>
1192 <BODY>
1193 <H1>TLS and SSL usage note</H1>
1195 <P>
1196 When using Alpine from Unix or Windows 2000,
1197 server certificates must be signed by a trusted certificate authority.
1198 You may relax this requirement (at the cost of some security) by using
1199 the
1200 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
1201 modifier in the mailbox name.
1203 <P>
1204 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
1205 <P>
1207 The fully-qualified host name of the server should be used
1208 so that it matches the host name in the server certificate.
1209 <P>
1210 Here is an example of a host specification that directs Alpine to use
1211 the SSL port (993) and an encrypted data stream.
1212 <P>
1213 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
1214 <P>
1215 <End of TLS usage help>
1216 </BODY>
1217 </HTML>
1218 ====== h_news_config ======
1219 <HTML>
1220 <HEAD>
1221 <TITLE>Alpine Configuration</TITLE>
1222 </HEAD>
1223 <BODY>
1224 <H1>Alpine Configuration</H1>
1226 <H2>Using Environment Variables</H2>
1228 The values of Alpine configuration options may include environment variables
1229 that are replaced by the value of the variable at the time Alpine is run
1230 (and also at the time the config option is changed).
1231 The syntax to use environment variables is a subset of the common Unix
1232 shell dollar-syntax.
1233 For example, if
1235 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
1237 appears in the value of an Alpine configuration option it is looked up in the
1238 environent (using getenv("VAR")) and its
1239 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
1240 To include a literal dollar sign you may precede the dollar sign with another
1241 dollar sign.
1242 In other words, if the text
1244 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
1246 is the value of a configuration option, it will be expanded to
1248 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
1250 and no environment lookup will be done.
1251 For Unix Alpine it will also work to use a backslash character to
1252 escape the special meaning of the dollar sign, but $$ is preferable since
1253 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
1254 to be in a shared configuration file.
1255 <P>
1257 This all sounds more complicated than it actually is.
1258 An example may make it clearer.
1259 Unfortunately, the way in which environment variables are set is OS-dependent
1260 and command shell-dependent.
1261 In some Unix command shells you may use
1263 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
1264 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
1266 Now, if you use Alpine's Setup/Config screen to set
1268 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
1270 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
1271 so that this would be equivalent to
1273 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
1275 Note, environment variable substitution happens after configuration
1276 options that are lists are split into the separate elements of the list,
1277 so a single environment variable can't contain a list of values.
1279 <P>
1280 The environment variable doesn't have to be the only thing
1281 after the equal sign.
1282 However, if the name of the variable is not at the end of the line or
1283 followed by a space (so that you can tell where the variable name ends),
1284 it must be enclosed in curly braces like
1286 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
1288 It is always ok to use the braces even if you don't need to.
1289 <P>
1290 It is also possible to set a default value for an environment variable.
1291 This default value will be used if the environment variable is not
1292 set (that is, if getenv("VAR") returns NULL).
1293 The syntax used to set a default value is
1295 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
1297 If the config file contains
1299 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
1301 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
1302 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
1303 the value that <SAMP>VAR</SAMP> was set to, otherwise,
1304 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
1305 the default value.
1306 (Note that the variable is called "personal-name" in the config
1307 file but is displayed in the config screen as
1308 "<!--#echo var="VAR_personal-name"-->".
1309 In general, the value that goes into a config file is never exactly the
1310 same as the value you see on the screen.)
1312 <P>
1313 An example where an environment variable might be useful is the
1314 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
1315 Suppose most users used the server
1317 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
1319 but that there were some exceptions who used
1321 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
1323 In this case, the system manager might include the following line in
1324 the systemwide default Alpine configuration file
1326 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
1328 For the exceptional users adding
1330 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
1332 to their environment should work.
1333 <P>
1334 Another example might be the case where a user has to use a different
1335 SMTP server from work and from home.
1336 The setup might be something as simple as
1338 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
1340 or perhaps a default value could be given.
1341 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
1342 a list of SMTP servers.
1343 <P>
1345 <H2>Configuration precedence</H2>
1347 There are several levels of Alpine configuration. Configuration values at
1348 a given level override corresponding values at lower levels. In order of
1349 increasing precedence:
1350 <P>
1351 <UL>
1352 <LI> built-in defaults
1353 <LI> system-wide
1354 <!--chtml if pinemode="os_windows"-->
1355 config file from command line or provided
1356 by "PINECONF" environment variable
1357 <!--chtml else-->
1358 pine.conf file
1359 <!--chtml endif-->
1360 <LI> personal configuration file
1361 <LI> personal exceptions configuration file
1362 <LI> command-line options
1363 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1364 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1365 </UL>
1366 <P>
1367 The values in both the personal configuration file and the
1368 <A HREF="h_config_exceptions">exceptions</A>
1369 configuration file may be set using the Setup command.
1370 Setup/Config is the command to change most of the personal configuration
1371 options.
1372 The other Setup subcommands are also used to change the configuration,
1373 for example, Setup/AddressBook, Setup/Rules, and so on.
1374 Changing the personal exceptions configuration is very similar.
1375 To change a value in the Config screen you would use the command
1376 Setup/eXceptions/Config.
1377 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1378 <P>
1379 There are a couple exceptions to the rule that configuration values are replaced
1380 by the value of the same option in a higher-precedence file.
1381 The Feature-List variable has values that are additive, but can be
1382 negated by prepending "no-" in front of an individual feature name.
1383 So for features, each individual feature's value is replaced by the value
1384 of the same feature in a higher-precedence file.
1385 Note that this is done automatically for you when you change these values via
1386 the Setup/Config command.
1387 The other exception to the <EM>replace</EM> semantics happens when you
1388 use <A HREF="h_config_inheritance">configuration inheritance</A>
1389 for option lists.
1390 <P>
1392 <H2>File name defaults</H2>
1394 Notes:<P>
1396 <BR> <exe dir> = directory where pine.exe found.
1397 <BR> <pinerc dir> = directory where pinerc found.
1398 <BR> # = default file name is overridable in pinerc.
1399 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1400 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1401 <BR> + between the mailcap paths implies that the two files are combined.
1402 <BR> ; between other default paths implies that the first one found is used.
1403 </P>
1404 Alpine looks for most support files in the same directory it finds its
1405 personal configuration file (pinerc). The -p command-line flag may be
1406 used to specify a particular path name for the pinerc file. If a
1407 pinerc file does not exist, it will be created (if directory permissions
1408 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1409 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1410 file does not exist in either one, it will create one in the first of those
1411 two directories that is writable. In detail:
1412 <PRE>
1414 PC-Alpine:
1416 executable <DOS search path>\pine.exe
1417 help index <exe dir>\pine.ndx
1418 help text <exe dir>\pine.hlp
1420 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1421 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1422 global cfg $PINECONF
1424 debug <pinerc dir>\pinedebg.txtN
1425 crash <pinerc dir>\pinecrsh.txt
1426 signature# <pinerc dir>\pine.sig
1427 addressbook# <pinerc dir>\addrbook
1428 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1429 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1430 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1431 sentmail# $HOME\mail\sentmail.mtx
1432 postponed# $HOME\mail\postpond.mtx
1433 interrupted $HOME\mail\intruptd
1435 Unix Alpine:
1437 executable <Unix search path>/pine
1438 persnl cfg ~/.pinerc
1439 except cfg ~/.pinercex
1440 global cfg <!--#echo var="PINE_CONF_PATH"-->
1441 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1442 local help <!--#echo var="PINE_INFO_PATH"-->
1444 interrupted ~/.pine-interrupted-mail
1445 debug ~/.pine-debugN
1446 crash ~/.pine-crash
1447 newsrc# ~/.newsrc
1448 signature# <pinerc dir>/.signature
1449 addressbook# <pinerc dir>/.addressbook
1450 postponed# ~/mail/postponed-msgs
1451 sentmail# ~/mail/sent-mail
1452 mailcap# ~/.mailcap + /etc/mailcap
1453 + /usr/etc/mailcap + /usr/local/etc/mailcap
1454 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1456 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1457 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1458 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1459 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1460 password /etc/passwd
1462 Unix Alpine and PC-Alpine:
1464 .ab* remote addressbook support files
1465 a[1-9]* temporary (while Alpine is running) addressbook files
1467 </PRE>
1468 <P>
1470 <H2>Mailcap files</H2>
1472 Alpine honors the mailcap configuration system for specifying external
1473 programs for handling attachments. The mailcap file maps MIME attachment
1474 types to the external programs loaded on your system that can display
1475 and/or print the file. A sample mailcap file comes bundled with the Alpine
1476 distribution. It includes comments that explain the syntax you need to
1477 use for mailcap. With the mailcap file, any program (mail readers,
1478 newsreaders, WWW clients) can use the same configuration for handling
1479 MIME-encoded data.
1480 <P>
1482 <H2>MIME-Types files</H2>
1484 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1485 what Content-Type to use for labeling an attached file, based on
1486 the file extension. That is, this file provides a mapping between
1487 filename extensions and MIME content-types.
1488 <P>
1490 <H2>Environment variables</H2>
1492 PC-Alpine uses the following environment variables:
1493 <DL>
1494 <DT>PINERC</DT>
1495 <DD>Optional path to pinerc file.</DD>
1496 <DT>PINERCEX</DT>
1497 <DD>Optional path to personal exceptions configuration file.</DD>
1498 <DT>PINECONF</DT>
1499 <DD>Optional path to global pine config file.</DD>
1500 <DT>HOME</DT>
1501 <DT>TMPDIR, TMP, or TEMP</DT>
1502 <DT>COMSPEC</DT>
1503 <DT>MAILCAPS</DT>
1504 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1505 <DT>USER_DICTIONARY</DT>
1506 <DD>Used to specify the file to contain the user's spell check
1507 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1508 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1509 </DL>
1511 Unix Alpine uses the following environment variables:
1512 <DL>
1513 <DT>TERM</DT>
1514 <DD>Tells Alpine what kind of terminal is being used.</DD>
1515 <DT>DISPLAY</DT>
1516 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1517 <DT>SHELL</DT>
1518 <DD>If not set, default is "/bin/sh".</DD>
1519 <DT>TMPDIR, TMP, or TEMP</DT>
1520 <DT>MAILCAPS</DT>
1521 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1522 </DL>
1523 <!--chtml if pinemode="os_windows"-->
1524 <P>
1525 <H2>Common PC-Alpine Configuration Problems</H2>
1527 <H3>Configuration settings aren't being saved</H3>
1529 <P>This problem can happen if you run pine from one directory and
1530 then decide to move your pine directory to another location. PC-Alpine
1531 stores certain variables, including the configuration location, in the
1532 Windows Registry (which you shouldn't ever need to manually edit). There
1533 are a couple of ways to go about removing or resetting the values in the
1534 registry.
1536 <P>
1537 1) Run PC-Alpine's registry value deletion command. This can be done by
1538 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1539 prompt. You could create a shortcut to pine.exe and change the "Target"
1540 value to the above command.
1542 <P>
1543 2) Tell PC-Alpine where to look for the configuration file. Configuration
1544 information is stored in a file called the PINERC. With the "-p PINERC"
1545 option, you can tell PC-Alpine the location of your pinerc. An example of
1546 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1547 Again, you can use the DOS prompt or the shortcut method explained in (1).
1549 <P>
1550 Additionally, there is the "-registry set" option, which will actively
1551 set registry values to the current setting, and is therefore useful with
1552 the "-p PINERC" option.
1554 <!--chtml endif-->
1555 <P>
1556 <End of Configuration Notes>
1557 </BODY>
1558 </HTML>
1559 ====== h_news_legal ======
1560 <html>
1561 <head>
1562 <TITLE>Alpine Legal Notices</TITLE>
1563 </head>
1564 <body>
1566 <H1>Alpine Legal Notices</H1>
1568 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1571 <P>
1572 <End of Alpine Legal Notices>
1573 </BODY>
1574 </HTML>
1575 ===== h_info_on_mbox =====
1576 <HTML>
1577 <HEAD>
1578 <TITLE>Information on mbox driver</TITLE>
1579 </HEAD>
1580 <BODY>
1581 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1583 Beginning with Pine 4.00 (Pine came before Alpine)
1584 a new INBOX access method is
1585 available as part of the standard configuration. It is called the
1586 "mbox" driver and it works like this:<P>
1588 <P>
1589 <BLOCKQUOTE>
1590 If the file "mbox" exists in the user's home directory, and
1591 is in Unix mailbox format, then when INBOX is opened this file will be
1592 selected as INBOX instead of the mail spool file. Messages will be
1593 automatically transferred from the mail spool file into the mbox
1594 file.
1595 </BLOCKQUOTE>
1597 <P>
1598 The advantage of this method is that, after new mail has been copied
1599 from the system mail spool, all subsequent access is confined to the
1600 user's home directory, which is desirable on some systems. However, a
1601 possible disadvantage is that mail tools other than those from the
1602 University of Washington will not know to look for mail in the user's
1603 mbox file. For example, POP or IMAP servers other than those from the
1604 University of Washington, and many "new mail notification"
1605 programs may not work as expected with this driver enabled.<P>
1607 To disable this behavior, either remove/rename the "mbox"
1608 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1609 option in Setup/Config
1610 and add "mbox" to it:
1611 <P>
1612 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1613 <P>
1614 <End of help on this topic>
1615 </BODY>
1616 </HTML>
1617 ===== h_info_on_locking =====
1618 <HTML>
1619 <HEAD>
1620 <TITLE>FAQs on Alpine Locking</TITLE>
1621 </HEAD>
1622 <BODY>
1623 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1625 There is an extensive section on locking in the Alpine technical notes;
1626 this information is intended to provide answers to some common questions:<P>
1627 <OL>
1628 <LI> Why did locking change in Pine 4.00?<BR>
1629 The actual locking mechanisms did not change in 4.00.
1630 What changed is that when one particular locking mechanism used by Alpine
1631 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1632 failure would occur, but no warning was issued.<P>
1634 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1635 Yes. It means that Alpine was unable to create a lockfile in the
1636 spool directory, generally because of overly restrictive protections on the
1637 spool directory. The correct permissions on the spool directory for
1638 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1639 with the sticky-bit set, so only owners of a file can delete them.<P>
1641 <LI> Why does Alpine require that the mail spool directory have 1777
1642 protections?<BR>
1643 Alpine was designed to run without special privileges. This means that in
1644 order to create a lockfile in the spool directory, it is necessary to have
1645 the spool directory permissions be world-writable.<P>
1647 <LI> Can't you create the lockfile somewhere else?<BR>
1648 No. The lockfile in question must be in the mail spool directory, because
1649 that's where the mail delivery program expects to find it, and the purpose
1650 of the file is to coordinate access between the mail client (Alpine) and the
1651 mail delivery program.<P>
1653 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1654 No. Remember that the individual mail files in the spool directory are
1655 NOT world-writable, only the containing directory. Setting the "sticky
1656 bit" -- indicated by the "1" before the "777" mode
1657 -- means that only the owner of the file (or root) can delete files in the
1658 directory. So the only bad behavior that is invited by the 1777 mode is that
1659 anyone could
1660 create a random file in the spool directory. If the spool directory is
1661 under quota control along with home directories, there is little incentive
1662 for anyone to do this, and even without quotas a periodic scan for
1663 non-mail files usually takes care of the problem. <P>
1665 <LI> Why not run Alpine as setgid mail?<BR>
1666 Alpine was never designed to run with privileges, and to do so introduces a
1667 significant security vulnerability. For example, if a user suspends Alpine,
1668 the resulting shell will have group privileges. This is one example of
1669 why we strongly recommend against running Alpine as a privileged program.
1670 In addition, a "privileged mailer " paradigm would mean that normal
1671 users
1672 could not test Alpine versions or other mailers that had not been installed
1673 by the system administrators.<P>
1676 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1677 There are, but they all have different sets of tradeoffs, and not all will
1678 work on all systems. Some examples:<UL>
1679 <LI> Use lock system calls. Works fine on a few systems, provided mail
1680 spool is local. Doesn't work reliably if NFS is used.
1681 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1682 use the same calls.
1683 <LI> Deliver mail to user's home directory. An excellent solution, highly
1684 recommended -- but one which is incompatible with some "legacy"
1685 mail tools that always look in the spool directory for the mail.
1686 </UL><P>
1688 <LI> Are these spool directory lock files the only kinds of locks used by
1689 Alpine?<BR>
1690 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1691 mailbox format folders, these are used to coordinate access between
1692 multiple Alpine sessions. <P>
1694 <LI> What about the
1695 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1696 This is for people who are content to live dangerously, or who have
1697 specific knowledge that the spool directory lockfiles are superfluous on
1698 their system (because both Alpine and the mail delivery program are using
1699 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1701 <LI> Where can I find more details on how Alpine locking works?<BR>
1702 See the Alpine Technical Notes.<P>
1704 </OL>
1705 <P>
1706 <End of help on this topic>
1707 </BODY>
1708 </HTML>
1709 ===== h_finding_help ====
1710 <HTML>
1711 <HEAD>
1712 <TITLE>Finding more information and requesting help</TITLE>
1713 </HEAD>
1714 <BODY>
1715 <H1>Places to Look for More Answers</H1>
1716 If you have questions about or problems with Alpine that you cannot resolve
1717 after consulting the program's internal, context-sensitive help screens, here
1718 are additional information resources that you may find helpful:
1719 <P>
1720 <UL>
1721 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1723 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1725 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1726 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1727 since the last version, which may be useful for you to be aware of,
1728 <B>especially</B> if a "problem" you are encountering is actually
1729 a change in the way an aspect of Alpine works. There, you will also find notes
1730 on Alpine configuration.<P>
1732 <LI> The main site for Alpine contains information on configuring and solving problems
1733 with Alpine, it can be found at
1735 <CENTER><A HREF="http://patches.freeiz.com/alpine/">http://patches.freeiz.com/alpine/</A></CENTER>
1737 <LI> The Alpine Information Center (maintained by the University of
1738 Washington) World Wide Web site contains, among other things
1739 <UL>
1740 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
1741 <LI>an overview of the basics for beginning Alpine users
1742 <LI>Technical Notes for systems administrators
1743 <LI>archives (including a searchable index) of the alpine-info
1744 mailing list, on which matters of interest to systems/email administrators,
1745 developers, trainers, user support personnel, and others involved with Alpine
1746 messaging on a "technical" level are discussed.
1747 </UL>
1748 The Alpine Information Center can be accessed with a WWW browser at:<P>
1749 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
1750 </UL>
1751 <P><HR WIDTH="75%">
1752 <H1>Requesting help</H1>
1753 If the internal help, the Release Notes, the Alpine Information Center, and your
1754 local online and print resources do not help you resolve a problem, please
1755 start by contacting your local computer support staff and asking for help.
1756 <p>
1757 This is especially true if:
1758 <ul>
1759 <li>You suddenly have trouble sending or receiving mail.
1760 <li>You receive a "disk quota exceeded" message.
1761 <li>You have forgotten your password.
1762 <li>You think your account may have been compromised.
1763 <li>You need help viewing an attachment.
1764 <li>You need to know how to configure your:
1765 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
1766 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
1767 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
1768 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
1769 <li>You want to know what alternative editors or spellcheckers you may be able to use.
1770 <li>You want to block email from a particular person.
1771 <li>You're going on vacation and need to autorespond to incoming mail.
1772 <li>You want to automatically file or filter incoming messages.
1773 </ul>
1775 In all of these cases,
1776 you should contact <B>your</B> support staff, because <B>only they</B>
1777 will be able to assist you effectively. Your support staff may be, depending on who
1778 provides you with the email account you use Alpine with, for example:<UL>
1779 <LI> the computing help desk of (a department of) your university, school,
1780 employer, ... ; or
1781 <LI> the customer service center of your Internet Service Provider; or
1782 <LI> the friendly volunteer helpers of your Freenet; or
1783 <LI> the person who setup your computer and internet connection.
1784 </UL>
1786 Due to the large number of Alpine installations worldwide, and because we
1787 receive no funding for it, the University of Washington <B>cannot provide
1788 individual support services outside the University of Washington</B>.
1789 <P>
1790 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
1791 newsgroup can be a valuable source of information and assistance for Alpine
1792 user issues.
1793 <P>
1794 For systems/email administrators, developers, trainers, user support
1795 personnel, and others involved with Alpine messaging on a "technical"
1796 level, the mailing list alpine-info is available; for information on
1797 subscribing and posting to it, see
1798 <P>
1799 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
1800 <P>
1802 Regardless of whom you are asking for help with Alpine, remember
1803 to provide as much detail as you can about the
1804 nature of any problem you are encountering, such as
1805 <UL>
1806 <LI>when it first occurred;
1807 <LI>what, if anything, happened that might have brought it about;
1808 <LI>whether it still persists;
1809 <LI>whether it is reproducible, and if so, how;
1810 <LI>what, if anything, you already tried to solve it.
1811 </UL>
1812 It may also be helpful if you specify what version of Alpine you are using
1813 <!--chtml if pinemode="running"-->
1814 -- this is <!--#echo var="ALPINE_VERSION"--> --
1815 <!--chtml endif-->
1816 and on what system, and when the copy of Alpine you are using was created
1817 <!--chtml if pinemode="running"-->
1818 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
1819 <!--chtml endif-->
1821 <!--chtml if pinemode="running"-->
1822 <P>
1823 When the Alpine program you are currently using was installed, a support
1824 contact email address may have been set up; in that case, you can simply select
1825 this link now to send a message to it:<BR>
1826 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
1827 <!--chtml endif-->
1828 <!--chtml if [ -r PINE_INFO_PATH ]-->
1829 <HR WIDTH="75%">Local Support Contacts:<P>
1830 <!--#include file="PINE_INFO_PATH"-->
1831 <HR WIDTH="75%">
1832 <!--chtml endif-->
1833 <P>
1834 <End of help on this topic>
1835 </BODY>
1836 </HTML>
1837 ===== new_user_greeting ======
1838 <HTML>
1839 <HEAD>
1840 <TITLE>NEW USER GREETING</TITLE>
1841 </HEAD>
1842 <BODY>
1843 <CENTER><<<This message will appear only once>>></CENTER>
1844 <BR>
1845 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1846 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
1847 select Setup/Config to see many of the options available to you. Also note
1848 that all screens have context-sensitive help text available.<P>
1849 <!--chtml if pinemode="phone_home"-->
1850 SPECIAL REQUEST:
1851 This software was originally created and maintained as a public
1852 service by the University of Washington until 2009; updates are made
1853 available as a public service of the Alpine community. It is always
1854 helpful to have an idea of how many users are using Alpine. Are you
1855 willing to be counted as an Alpine user? Pressing
1856 <A HREF="X-Alpine-Phone-Home:">Return</A>
1857 will send an anonymous (meaning, your real email address will not be revealed)
1858 message to the Alpine developers for purposes of tallying.
1859 <P>
1860 <!--To Exit this screen and continue your Alpine session press "E".-->
1861 <!--chtml else-->
1862 To Exit this screen and continue your Alpine session press "Return".
1863 <!--chtml endif-->
1864 </BODY>
1865 </HTML>
1866 ===== new_alpine_user_greeting ======
1867 <HTML>
1868 <HEAD>
1869 <TITLE>NEW ALPINE USER GREETING</TITLE>
1870 </HEAD>
1871 <BODY>
1872 <CENTER><<<This message will appear only once>>></CENTER>
1873 <BR>
1874 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
1875 Your Alpine configuration file indicates that you may have used Pine before
1876 but not Alpine.
1877 If you are familiar with the way Pine works, you should be comfortable
1878 using Alpine.
1879 Your Pine configuration file is automatically used for Alpine.
1880 The Release Notes may be viewed by pressing
1881 "R" now or while in the MAIN MENU.
1882 <P>
1883 <!--chtml if pinemode="phone_home"-->
1884 SPECIAL REQUEST:
1885 This software was originally created and maintained as a public
1886 service by the University of Washington until 2009; updates are made
1887 available as a public service of the Alpine community. It is always
1888 helpful to have an idea of how many users are using Alpine. Are you
1889 willing to be counted as an Alpine user? Pressing
1890 <A HREF="X-Alpine-Phone-Home:">Return</A>
1891 will send an anonymous (meaning, your real email address will not be revealed)
1892 message to the Alpine developers for purposes of tallying.
1893 <P>
1894 <!--To Exit this screen and continue your Alpine session press "E".-->
1895 <!--chtml else-->
1896 To Exit this screen and continue your Alpine session press "Return".
1897 <!--chtml endif-->
1898 </BODY>
1899 </HTML>
1900 ===== new_version_greeting ======
1901 <HTML>
1902 <HEAD>
1903 <TITLE>NEW VERSION GREETING</TITLE>
1904 </HEAD>
1905 <BODY>
1906 <CENTER><<<This message will appear only once>>></CENTER>
1907 <BR>
1908 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
1909 Your Alpine configuration file indicates that you may not have used
1910 this version of Alpine before. This version's significant changes are
1911 documented in the Release Notes, which may be viewed by pressing
1912 "R" now or while in the MAIN MENU.
1913 <P>
1914 <!--chtml if pinemode="phone_home"-->
1915 SPECIAL REQUEST:
1916 This software was originally created and maintained as a public
1917 service by the University of Washington until 2009; updates are made
1918 available as a public service of the Alpine community. It is always
1919 helpful to have an idea of how many users are using Alpine. Are you
1920 willing to be counted as an Alpine user? Pressing
1921 <A HREF="X-Alpine-Phone-Home:">Return</A>
1922 will send an anonymous (meaning, your real email address will not be revealed)
1923 message to the Alpine developers for purposes of tallying.
1924 <P>
1925 <!--To Exit this screen and continue your Alpine session press "E".-->
1926 <!--chtml else-->
1927 To Exit this screen and continue your Alpine session press "Return".
1928 <!--chtml endif-->
1929 </BODY>
1930 </HTML>
1932 ===== main_menu_tx ======
1933 <HTML>
1934 <HEAD>
1935 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
1936 </HEAD>
1937 <BODY>
1938 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
1939 <DIV ALIGN=CENTER>
1940 Version <!--#echo var="ALPINE_VERSION"-->
1941 <!--chtml if pinemode="running"-->
1942 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
1943 <!--chtml endif-->
1944 </DIV>
1945 <CENTER>Copyright 2013-2015 Eduardo Chappa,
1946 <BR>Copyright 2006-2008 University of Washington.
1947 </CENTER>
1949 <P>
1950 When you are viewing a help screen, there may be links to
1951 other topics highlighted (in Reverse video) in the text.
1952 Here is an example.
1953 The word "Introduction" in the TABLE OF CONTENTS below should be
1954 highlighted.
1955 If you type carriage return (or V for View Link, see the commands at the
1956 bottom of the screen) you will be taken to a new help screen to view the
1957 Introduction.
1958 The commands at the bottom of the screen should then include
1959 "P Prev Help".
1960 If you type "P" you will end up back here.
1961 If you type "E" for Exit, you will be back out of help and returned
1962 to the place you were in Alpine when you entered Help.
1963 In this case, you would go back to the MAIN MENU.
1964 There are also other links that are highlighted in bold (or the color used
1965 by your terminal to display bold).
1966 The items after the Introduction in the TABLE OF CONTENTS are all examples
1967 of such links.
1968 In order to view those links, you first have to make the link you want
1969 to view the current link.
1970 The "NextLink" and "PrevLink" commands
1971 (see bottom of screen) can do that for you.
1972 <P>
1974 <H2>TABLE OF CONTENTS</H2>
1975 <OL>
1976 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
1977 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
1978 <!--chtml if [ -r PINE_INFO_PATH ]-->
1979 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
1980 <!--chtml endif-->
1981 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
1982 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
1983 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
1984 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
1985 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
1986 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
1987 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
1988 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
1989 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
1990 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
1991 <LI> <A HREF="h_mainhelp_folders">Folders</A>
1992 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
1993 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
1994 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
1995 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
1996 <LI> <A HREF="h_mainhelp_roles">Roles</A>
1997 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
1998 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
1999 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
2000 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
2001 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
2002 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
2003 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
2004 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
2005 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
2006 </OL>
2008 <P>
2009 <End of help on this topic>
2010 </BODY>
2011 </HTML>
2012 ===== h_mainhelp_intro ======
2013 <HTML>
2014 <HEAD>
2015 <TITLE>Introduction</TITLE>
2016 </HEAD>
2017 <BODY>
2018 <H1>Introduction</H1>
2020 Alpine is an "Alternatively Licensed Program for Internet
2021 News and Email" produced until 2009 by the University of Washington.
2022 It is intended to be an easy-to-use program for
2023 sending, receiving, and filing Internet electronic mail messages and
2024 bulletin board (Netnews/Usenet) messages. Alpine supports the following
2025 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
2026 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
2027 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
2028 Directory Access Protocol).<p>
2030 Although originally designed for inexperienced email users, Alpine has
2031 evolved to support many advanced features. There are an ever-growing
2032 number of configuration and personal-preference options, though which of
2033 them are available to you is determined by your local system managers.
2035 <H2>WHAT ALPINE DOES...</H2>
2037 Alpine is a "mail user agent" (MUA), which is a program that
2038 allows you to
2039 compose and read messages using Internet mail standards. (Whether you
2040 can correspond with others on the Internet depends on whether or not your
2041 computer is connected to the Internet.) Alpine also allows reading and
2042 posting messages on the Internet "net news" system, provided
2043 that your site operates a suitable news server.
2045 <H2>WHAT ALPINE DOES NOT DO...</H2>
2047 A "mail user agent" such as Alpine is just one part of a
2048 messaging system. Here are some things that are <B>not</B> done by Alpine,
2049 but require other programs:<P>
2050 <UL>
2051 <LI> Actual relaying of email... which is done by "message transfer
2052 agents".
2053 <LI> Vacation messages... automatically responding to incoming messages
2054 <LI> Anything to do with "talk"... which has nothing to do with
2055 email.
2056 <LI> Anything to do with "irc"... which has nothing to do with email.
2057 <LI> List processing... resending one message to a list of recipients.
2058 </UL>
2060 <P>
2061 <End of help on this topic>
2062 </BODY>
2063 </HTML>
2065 ===== h_mainhelp_pinehelp ======
2066 <HTML>
2067 <HEAD>
2068 <TITLE>Alpine Help</TITLE>
2069 </HEAD>
2070 <BODY>
2071 <H1>Alpine Help</H1>
2073 Alpine help is generally context-sensitive. In other words, each Alpine screen you
2074 use will have its own help text, explaining the choices available for that
2075 screen. This general help section, on the other hand, attempts to give an
2076 overall picture of what Alpine is capable of doing, as well as pointers to
2077 additional help sections about specific topics.<p>
2079 Much of the help text contains links to further help topics, similar to
2080 how the World Wide Web works.
2081 You may choose a link to view using the "NextLink" and
2082 "PrevLink" commands to change the link that is highlighted.
2083 The "View Link" command will then show you the highlighted link.
2084 Similar to the Back button in a web browser, the "Prev Help" command
2085 will return you to where you were before viewing the link, and "Exit Help"
2086 will return you to the location in Alpine before you asked for help.
2087 For example, if you are reading this text in Alpine you may return to the
2088 help table of contents with the "Prev Help" command or you may view the
2089 Release notes link in the next paragraph and then return here with
2090 "Prev Help".
2091 <P>
2093 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
2094 on the current Alpine version are also available from the MAIN MENU: Press
2095 <!--chtml if pinemode="function_key"-->
2096 "F9"
2097 <!--chtml else-->
2098 "R"
2099 <!--chtml endif-->
2100 to browse the release notes. These include changes since the last release,
2101 configuration information, the history of the Alpine
2102 project, credits, and legal notices.
2104 Alpine releases are available via the world wide web at
2105 <P>
2106 <CENTER><SAMP><A
2107 HREF="http://patches.freeiz.com/alpine/release/">http://patches.freeiz.com/alpine/release/</A></SAMP
2108 ></CENTER>
2109 <P>
2111 If you would like to print <EM>all</EM> of Alpine's internal help text
2112 (not recommended) for a little light bedtime reading, then press
2113 <!--chtml if pinemode="function_key"-->
2114 "F12"
2115 <!--chtml else-->
2116 "Z"
2117 <!--chtml endif-->
2118 now. (This assumes that the
2119 copy of Alpine you are using has been properly configured for printing
2120 at your site.)
2121 <P>
2122 <End of help on this topic>
2123 </BODY>
2124 </HTML>
2125 ===== h_mainhelp_localsupport ======
2126 <HTML>
2127 <HEAD>
2128 <TITLE>Local Support Contacts</TITLE>
2129 </HEAD>
2130 <BODY>
2131 <H1>Local Support Contacts</H1>
2133 <!--chtml if [ -r PINE_INFO_PATH ]-->
2134 <!--#include file="PINE_INFO_PATH"-->
2135 <!--chtml else-->
2136 No Local Support Contacts configured.
2137 <!--chtml endif-->
2139 <P>
2140 <End of help on this topic>
2141 </BODY>
2142 </HTML>
2144 ===== h_mainhelp_cmds ======
2145 <HTML>
2146 <HEAD>
2147 <TITLE>Giving Commands in Alpine</TITLE>
2148 </HEAD>
2149 <BODY>
2150 <H1>Giving Commands in Alpine</H1>
2152 Unless configured otherwise
2153 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
2154 the bottom two lines of the screen are always used to list the
2155 commands you can give. You press the keys that are highlighted to give
2156 the command. The commands for getting help and going back to the main
2157 menu are always present (except when viewing help as you are now).
2158 <!--chtml if pinemode="function_key"-->
2159 <!--chtml else-->
2160 <p>
2161 Pressing O (meaning "Other Commands") changes the keys
2162 you see at the bottom of any screen. In some cases there are 3 or
2163 even 4 different
2164 sets of keys that can be seen by using the O key. <EM>All commands are
2165 active</EM>, even if they are not currently showing at the bottom of your
2166 screen. In other words, you <EM>never</EM> need to press the O key, except to
2167 remind yourself of the proper key to press to perform an operation.
2169 <H2>Control Key Commands</H2>
2170 When composing mail, and in a few other places, in Alpine you
2171 have to use Control keys. This means pressing the Control key (usually labeled
2172 "Ctrl") and the
2173 letter indicated at the same time. Usually, this is shown with a
2174 "^" in front of the letter. On some systems, certain control
2175 characters are intercepted before they get to Alpine. As a work-around,
2176 you can press the ESCAPE key twice followed by the desired key. For
2177 example, if Ctrl-O (^O) does not work on your system, try typing
2178 "ESC ESC O".
2179 <!--chtml endif-->
2180 <H2>Paging Up and Down</H2>
2181 The "+" and "-" keys are used for
2182 moving to the next or previous page. The space bar is a synonym for
2183 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
2184 up as you do in the message composer. On screens with a WhereIs (search)
2185 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
2186 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
2187 of the message or list.
2189 <H2>Return Key</H2>
2190 The return key is usually a synonym for a frequently used
2191 command. When viewing a message, there is currently not a default
2192 command, so RETURN does nothing; when in the index, it is synonymous with
2193 "view msg". In the key menu at the bottom of the screen, whatever is
2194 enclosed in square brackets [] is the same as the return key.
2196 <H2>Control Keys Not Used By Alpine</H2>
2197 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
2198 value, but in places where Alpine is expecting text input, e.g. in the composer or
2199 at prompts for file/folder names, control keys must be used for editing and
2200 navigation functions.
2201 <P>
2203 Alpine has used nearly all the control keys available. There are, however,
2204 certain control keys that are reserved by other programs or for technical
2205 reasons. Alpine does not use any of these keys:
2206 <DL>
2207 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
2208 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
2209 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
2210 </DL>
2211 <P>
2212 Note: Ctrl-S and Ctrl-Q can be subject to
2213 <A HREF="h_special_xon_xoff">special handling</A>.
2214 <P>
2215 In addition, while the ESC key alone is not used for command input,
2216 Alpine will recognize two consecutive ESC key presses followed by a letter
2217 key as a substitute for control key input. For example, the control key
2218 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
2219 three keystrokes: <SAMP>ESC ESC x</SAMP>.
2220 This is useful if the communication program you are using
2221 (e.g. Telnet) has its own, conflicting, idea of what certain control
2222 characters mean.
2225 <H2>Repainting the Screen</H2>
2226 Sometimes what is displayed on the screen will be
2227 incorrect due to noise on the phone line or other causes and you will want
2228 to repaint the whole screen to make it correct. You can use the Ctrl-L
2229 command to do this. It never hurts to do it when in doubt.
2231 <P>
2232 <End of help on this topic>
2233 </BODY>
2234 </HTML>
2235 ===== h_mainhelp_status ======
2236 <HTML>
2237 <HEAD>
2238 <TITLE>Titlebar Line</TITLE>
2239 </HEAD>
2240 <BODY>
2241 <H1>Titlebar Line</H1>
2243 The top line of the screen is Alpine's titlebar line. It will always display
2244 the current version of Alpine and will also convey information about the
2245 status of the program. This is where you look to find out what
2246 collection, folder and message number is active and where you are in Alpine.
2247 <P>
2249 If the titlebar line says "READONLY" it means that the open folder
2250 (typically your INBOX) is "locked" by another mail session --
2251 most likely a more recent session of Alpine has taken the INBOX lock.
2252 <P>
2254 If the titlebar line says "CLOSED" it means that you are trying to
2255 access a
2256 folder on a remote mail server, and for some reason, communication with
2257 the mail server has either been lost, or never successfully established.
2258 This can be a result of trying to open a non-existent folder, or one
2259 stored on an invalid or non-operational server, or it can mean that Alpine
2260 has been suspended for more that 30 minutes while accessing a remote mail
2261 server.
2263 <P>
2264 <End of help on this topic>
2265 </BODY>
2266 </HTML>
2267 ===== h_mainhelp_mainmenu ======
2268 <HTML>
2269 <HEAD>
2270 <TITLE>Main Menu</TITLE>
2271 </HEAD>
2272 <BODY>
2273 <H1>Main Menu</H1>
2275 The Main Menu lists Alpine's main options.
2276 The key or keys you must type to enter your
2277 choice are to the left of each option or command name.
2278 You can type either uppercase or lowercase letters,
2279 and you should not press <Return> after typing the
2280 letter (unless you are specifically asking for the default,
2281 highlighted command).
2282 <P>
2284 From the Main Menu you can choose to read online help, write (compose) and
2285 send a message, look at an index of your mail messages, open or maintain
2286 your mail folders, update your address book, configure Alpine, and quit Alpine.
2287 There are additional options listed at
2288 the bottom of the screen as well.
2290 <P>
2291 The Help command usually returns context-sensitive help information.
2292 However, in the Main Menu you get the most general help, which includes
2293 a Table of Contents.
2294 The last entry in the Table of Contents is an Index of help topics,
2295 so this is a good place to go if you are having trouble finding how
2296 to do something.
2298 <H2>Main Menu Commands</H2>
2299 The Alpine main menu lists the most common Alpine functions. A <a
2300 href="h_main_menu_commands">full list of these
2301 commands</a> and what they do is available.
2302 <P>
2303 <End of help on this topic>
2304 </BODY>
2305 </HTML>
2306 ===== h_mainhelp_abooks ======
2307 <HTML>
2308 <HEAD>
2309 <TITLE>Address Books</TITLE>
2310 </HEAD>
2311 <BODY>
2312 <H1>Address Books</H1>
2315 As you use email, you can build a list of your regular email correspondents
2316 in your Alpine
2317 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
2318 screen. Your
2319 personal address book will be highlighted. Press <Return> to view it.
2320 You can use the address book to store email addresses for individuals or
2321 groups, to create easily
2322 remembered "nicknames" for these addresses, and to quickly retrieve an email
2323 address when you are composing a message.
2324 <P>
2325 There are two ways to add addresses to your address book: you can add them
2326 manually or take them from messages (by pressing T to access the Take command).
2327 With either method, you specify nicknames for your correspondents. A single
2328 address book entry (or nickname) can point to just one email address, or, it can
2329 point to more than one. When it points to more than one, it is called a
2330 distribution list. Each distribution list has a nickname, a full name, and a
2331 list of addresses. These
2332 addresses may be actual addresses, other nicknames in your address book, or
2333 other
2334 distribution lists.
2336 <P>
2337 Additional information is available in Alpine's online help:
2338 <ul>
2339 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
2340 </ul>
2341 <P>
2342 <End of help on this topic>
2343 </BODY>
2344 </HTML>
2345 ===== h_mainhelp_ldap ======
2346 <HTML>
2347 <HEAD>
2348 <TITLE>LDAP</TITLE>
2349 </HEAD>
2350 <BODY>
2351 <H1>LDAP</H1>
2353 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
2354 an organization's shared
2355 directories. Essentially, using LDAP, Alpine is able to find email addresses in
2356 large address
2357 books, rather like the White Pages provided by the phone company. As an Alpine
2358 user, it is not
2359 necessary to know much about how this works, only how to use it and how to
2360 configure
2361 it.
2362 <P>
2363 More information on configuring LDAP is available in Alpine's online help:
2364 <ul>
2365 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2366 </ul>
2367 <P>
2368 Additional help on using LDAP in Alpine is also available:
2369 <ul>
2370 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2371 </ul>
2372 <P>
2373 <End of help on this topic>
2374 </BODY>
2375 </HTML>
2376 ===== h_mainhelp_index ======
2377 <HTML>
2378 <HEAD>
2379 <TITLE>Index of Messages</TITLE>
2380 </HEAD>
2381 <BODY>
2382 <H1>Index of Messages</H1>
2384 In Alpine's message index, the selected message is highlighted. The first
2385 column on the left is blank, shows a "+" if the message was
2386 sent directly to you (i.e., it is not a
2387 copy or from a list), or a "-" if you were explicitly Cc'd.
2388 <P>
2389 The second column may be blank, or it may contain:
2390 <ul>
2391 <li>"N" if the message is new (unread), </li>
2392 <li>"A" if you have answered the message (using the Reply command), </li>
2393 <li>"D" if you have marked the message for deletion.</li>
2394 </ul>
2396 <P>
2397 Note: If you answer a message as well as mark it deleted (in either order),
2398 you will only see the "D".
2400 <P>
2401 The rest of the columns in the message line show you the message
2402 number, date sent, sender, size, and subject. For details, press ? (Help).
2403 The behavior and appearance of the Index screen is highly configurable.
2404 In the Setup/Config screen search (with the WhereIs command) for options
2405 that contain the words "index" or "thread" to see
2406 many of the configuration possibilities.
2407 In particular, the
2408 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2409 option may be used to configure the look of the standard MESSAGE INDEX lines
2410 in many different ways.
2411 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2412 read the help text there for more information.
2413 <P>
2414 Most of the commands you need to handle your messages are visible at the
2415 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2416 commands that are available.
2417 You do not need to see these "other commands"
2418 on the screen to use them. That is, you never need to press O as a prefix
2419 for any other command.
2421 <P>
2422 Additional information is available in Alpine's online help:
2423 <ul>
2424 <li><a href="h_mail_index">Message Index Commands</a></li>
2425 </ul>
2426 <P>
2427 <End of help on this topic>
2428 </BODY>
2429 </HTML>
2430 ===== h_mainhelp_reading ======
2431 <HTML>
2432 <HEAD>
2433 <TITLE>Reading Messages</TITLE>
2434 </HEAD>
2435 <BODY>
2436 <H1>Reading Messages</H1>
2438 The message text screen shows you the text of the message along with
2439 its header. If a message has attachments, those will be listed (but not
2440 displayed) also. The titlebar line displays information about the currently
2441 open message, folder and collection. You see the name of the collection
2442 (if there is one) in angle brackets, then the name of the folder, then the
2443 message number and finally the position within the current message (in
2444 percent). If the message is marked for deletion
2445 "DEL" will appear in the
2446 upper right as well.
2448 <P>
2449 As with every Alpine screen, the bottom two lines show you the commands
2450 available.
2452 <P>Additional information is available in Alpine's online help:
2453 <ul>
2454 <li><a href="h_mail_view">Message Text Screen</a></li>
2455 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2456 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2457 </ul>
2458 <P>
2459 <End of help on this topic>
2460 </BODY>
2461 </HTML>
2462 ===== h_mainhelp_composing ======
2463 <HTML>
2464 <HEAD>
2465 <TITLE>Composing Messages</TITLE>
2466 </HEAD>
2467 <BODY>
2468 <H1>Composing Messages</H1>
2470 To write a message, press C (Compose). You see the Compose Message
2471 screen, which is divided into two parts: the header area and the message
2472 text area. The header area is where information on the recipient (the To:
2473 field) and the subject line go, while the message text area contains the
2474 actual text of the email message. Different commands are available to you
2475 when your cursor is in different areas on this screen. To see additional
2476 help on commands in either the message text or header area, type
2477 <Control>G (Get help).
2479 <P>
2480 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2481 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2483 <P>The following information from Alpine's online help may prove useful:
2484 <ul>
2485 <li><a href="h_composer_to">Message Header Commands</a></li>
2486 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2487 <li><a href="h_composer">Composer Commands</a></li>
2488 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2489 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2490 <li><a href="h_compose_send">Send Command</a></li>
2491 <li><a href="h_compose_spell">Spell Check Command</a></li>
2492 </ul>
2493 <P>
2494 <End of help on this topic>
2495 </BODY>
2496 </HTML>
2497 ===== h_mainhelp_collections ======
2498 <HTML>
2499 <HEAD>
2500 <TITLE>Collection Lists</TITLE>
2501 </HEAD>
2502 <BODY>
2503 <H1>Collection Lists</H1>
2505 Collection lists are Alpine's way of organizing groups of folders. Each
2506 "collection" can reside on a different server, for example, and contain a
2507 different group of mail folders.
2509 <P>
2510 For more information on this, see:
2511 <ul>
2512 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2513 </ul>
2514 <P>
2515 Additional information relating to collection lists is also available in
2516 Alpine's online
2517 help:
2518 <ul>
2519 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2520 <li><a href="h_collection_screen">Collection List Screen</a></li>
2521 </ul>
2522 <P>
2523 <End of help on this topic>
2524 </BODY>
2525 </HTML>
2526 ===== h_mainhelp_folders ======
2527 <HTML>
2528 <HEAD>
2529 <TITLE>Folders</TITLE>
2530 </HEAD>
2531 <BODY>
2532 <H1>Folders</H1>
2534 Messages can quickly accumulate in your INBOX folder. If you use email
2535 often, you soon could have hundreds. You need to delete messages you do
2536 not want, and you can use folders to organize messages you wish to save. A
2537 folder is a collection of one or more messages that are stored (just like
2538 the messages in your INBOX) so you can access and manage them.
2540 <P>
2541 You can organize your email messages into different folders by topic,
2542 correspondent, date, or any other category that is meaningful to you. You
2543 can create your own folders, and Alpine automatically provides three:
2544 <ul>
2545 <li>The INBOX folder: messages sent to you are listed in this folder.
2546 When you first start Alpine and go to the Message Index screen, you are
2547 looking at the list of messages in your INBOX folder. Every incoming
2548 message remains in your INBOX until you delete it or save it in another
2549 folder. </li>
2550 <li>The sent-mail folder: copies of messages you send are stored in this
2551 folder. This is
2552 convenient if you cannot remember whether you actually sent a message and want
2553 to check, or
2554 if you want to send a message again.</li>
2555 <li>The saved-messages folder: copies of messages you save are stored in this
2556 folder
2557 unless you choose to save them to other folders you create yourself.</li>
2558 </ul>
2560 <P>
2561 More information about folders is available in Alpine's online help:
2562 <ul>
2563 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2564 <li><a href="h_folder_maint">Help for Folder List</a></li>
2565 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2566 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2567 Explained</a></li>
2568 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2569 </ul>
2570 <P>
2571 <End of help on this topic>
2572 </BODY>
2573 </HTML>
2574 ===== h_mainhelp_color ======
2575 <HTML>
2576 <HEAD>
2577 <TITLE>Color</TITLE>
2578 </HEAD>
2579 <BODY>
2580 <H1>Color</H1>
2582 If the terminal emulator you are using is capable of displaying color or if
2583 you are using PC-Alpine, then it is possible to set up Alpine so that various
2584 parts of the display will be shown in colors you configure. This is done
2585 using the Setup Color screen, available from the MAIN MENU by selecting
2586 the Setup command followed by "K" for Kolor (because "C"
2587 stands for Config in this context).
2589 <P>
2590 For example, you may color things like the titlebar, the current item,
2591 the keymenu, and the status messages.
2592 You may also color lines in the index, and headers and quoted text in the
2593 MESSAGE TEXT screen.
2594 You use the Color Setup screen for configuring most of this, but you must
2595 use the IndexColor setup for coloring whole index lines.
2596 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2598 <P>
2599 The following entries in Alpine's online help provide additional information
2600 about how to use color:
2601 <UL>
2602 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2603 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2604 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2605 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2606 </UL>
2607 <P>
2608 <End of help on this topic>
2609 </BODY>
2610 </HTML>
2611 ===== h_mainhelp_mouse ======
2612 <HTML>
2613 <HEAD>
2614 <TITLE>Using a Mouse</TITLE>
2615 </HEAD>
2616 <BODY>
2617 <H1>Using a Mouse</H1>
2619 If you are using PC-Alpine mouse support is turned on automatically.
2620 If you are using UNIX Alpine within an X terminal window or within
2621 a terminal emulator that supports an xterm-style mouse, then you may
2622 turn on support for the mouse with the feature
2623 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2624 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2625 <P>
2626 PC-Alpine offers considerable mouse support. You can view what is
2627 "clickable" by dragging your mouse over any screen; when the
2628 arrow cursor changes into a hand, you found something. Mouse-click
2629 possibilities include navigating between screens and folders and
2630 double-clicking on hyperlinks to open your Web browser.
2631 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2632 screen. Examples of right-click options include "copy" after
2633 selecting text to copy and "View in New Window" when you click
2634 on a particular message in the Message Index. The menu choices available
2635 to you will vary based upon what screen is open, where on the screen your
2636 cursor is located, and even what action you have already taken.
2637 Within a folder, you may set the "Important" flag on any
2638 message.
2639 <P>
2640 X terminal mouse support is more limited but still quite powerful.
2641 As with PC-Alpine, clicking on any of the commands in the keymenu at
2642 the bottom of the screen will execute that command as if you typed it.
2643 Double-clicking on a link, for example the link to the
2644 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2645 will take you to that link.
2646 Double-clicking on an index line will view the message, and so on.
2647 <P>
2648 <End of help on this topic>
2649 </BODY>
2650 </HTML>
2651 ===== h_mainhelp_keywords ======
2652 <HTML>
2653 <HEAD>
2654 <TITLE>Keywords</TITLE>
2655 </HEAD>
2656 <BODY>
2657 <H1>Keywords</H1>
2659 Within a folder, you may set the "Important" flag on any
2660 message.
2661 This doesn't have any system-defined meaning and is only called
2662 the Important flag because many users use it to signify that a message
2663 is important to them in some way.
2664 <P>
2665 You may also define your own set of keywords.
2666 You might know these as user defined flags or as labels.
2667 These are similar to the Important flag but you choose the names for yourself.
2668 <P>
2669 Alpine will only display keywords that
2670 have been added by you in the Flag Details screen or
2671 that have been configured by you using the Setup/Config option
2672 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2673 Keywords set by other means (for example, by another email client) will not
2674 show up in Alpine unless you configure Alpine to know about them.
2675 They will show up in the Flag Details screen, but will not show up, for example,
2676 in the index line.
2678 <P>
2679 The following entries in Alpine's online help provide additional information
2680 about how to use keywords:
2681 <ul>
2682 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2683 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2684 </ul>
2685 <P>
2686 <End of help on this topic>
2687 </BODY>
2688 </HTML>
2689 ===== h_mainhelp_roles ======
2690 <HTML>
2691 <HEAD>
2692 <TITLE>Roles</TITLE>
2693 </HEAD>
2694 <BODY>
2695 <H1>Roles</H1>
2697 You may play different roles depending on who you are replying to. For
2698 example, if you are replying to a message addressed to help-desk you may
2699 be acting as a Help Desk Worker. That role may require that you use a
2700 different return address and/or a different signature.
2702 <P>
2703 To configure roles, go to the MAIN MENU and use the Setup command
2704 followed by "Rules" and then "Roles".
2705 The following entries in Alpine's online help provide additional information
2706 about how to
2707 use roles:
2708 <ul>
2709 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2710 <li><a href="h_role_select">Roles Screen</a></li>
2711 </ul>
2712 <P>
2713 <End of help on this topic>
2714 </BODY>
2715 </HTML>
2716 ===== h_mainhelp_filtering ======
2717 <HTML>
2718 <HEAD>
2719 <TITLE>Filtering</TITLE>
2720 </HEAD>
2721 <BODY>
2722 <H1>Filtering</H1>
2724 The software that actually delivers mail (the stuff that happens
2725 before Alpine is involved) for you is in a better position to do mail filtering
2726 than Alpine itself.
2727 If possible, you may want to look into using that sort of mail filtering to
2728 deliver mail to different folders, delete it, or forward it.
2729 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
2731 <P>
2732 Filtering is a way to automatically move certain messages from one folder
2733 to another or to automatically delete messages.
2734 You may also automatically set the state (Important, New, Deleted, Answered) of messages
2735 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
2736 Alpine doesn't have the ability to forward mail to another address or
2737 to deliver vacation messages.
2739 <P>
2740 To configure filtering, go to the MAIN MENU and use the Setup command
2741 followed by "Rules" and then "Filters".
2742 The following entries in Alpine's online help provide additional information
2743 about how to use filtering:
2744 <UL>
2745 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
2746 </UL>
2747 <P>
2748 <End of help on this topic>
2749 </BODY>
2750 </HTML>
2751 ===== h_mainhelp_patterns ======
2752 <HTML>
2753 <HEAD>
2754 <TITLE>Patterns</TITLE>
2755 </HEAD>
2756 <BODY>
2757 <H1>Patterns</H1>
2759 Patterns are used with Roles, Filtering, Index Coloring,
2760 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
2761 The following entries in Alpine's online help provide information
2762 about using Patterns:
2763 <UL>
2764 <LI> <A HREF="h_rule_patterns">Patterns</A>
2765 </UL>
2766 <P>
2767 <End of help on this topic>
2768 </BODY>
2769 </HTML>
2770 ===== h_mainhelp_cmdlineopts ======
2771 <HTML>
2772 <HEAD>
2773 <TITLE>Command Line Options</TITLE>
2774 </HEAD>
2775 <BODY>
2776 <H1>Command Line Options</H1>
2778 Alpine accepts a number of command line arguments, allowing you, for
2779 example, to start Alpine and immediately access a particular folder.
2780 Many of these arguments overlap with options in the Alpine configuration file.
2781 If there is a difference, then an option set on the command line takes
2782 precedence.
2783 Alpine expects command line arguments (other than addresses) to be
2784 preceded by a "-" (dash) as normally used by UNIX programs.
2785 A <a href="h_command_line_options">full list</a> of command line
2786 possibilities is available.
2787 <P>
2788 <End of help on this topic>
2789 </BODY>
2790 </HTML>
2791 ===== h_mainhelp_config ======
2792 <HTML>
2793 <HEAD>
2794 <TITLE>Alpine Configuration</TITLE>
2795 </HEAD>
2796 <BODY>
2797 <H1>Alpine Configuration</H1>
2799 Unless it has been administratively disabled, the Setup command on the
2800 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
2801 The possible subcommands are for general Configuration settings,
2802 Printer settings, Changing your Password, Signature setup,
2803 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
2804 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
2805 and Color configuration.
2806 In particular, the "Config" subcommand has many features you may
2807 set or unset and many other configuration variables that may be set to change
2808 the way Alpine works.
2809 Every one of the hundreds of options available in that configuration settings
2810 screen has help text associated with it.
2811 You may read that text by moving the cursor to highlight the option and then
2812 typing the Help command.
2813 <P>
2814 These settings are stored in your personal
2815 "pinerc" configuration file (or, optionally, they may be stored
2816 <A HREF="h_config_remote_config">remotely</A>),
2817 but on shared systems these settings
2818 may be over-ridden by a system-wide control file (due to local site
2819 security or support policies). A global pine configuration file can also
2820 be used to set default values for all Alpine users on a particular system.
2821 Power users may be interested in splitting their personal configuration
2822 data into two pieces, a generic piece and
2823 <A HREF="h_config_exceptions">exceptions</A> which apply to
2824 a particular platform.
2825 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
2826 General Alpine configuration information can be found
2827 <A HREF="h_news_config">here</A>.
2828 <P>
2829 <End of help on this topic>
2830 </BODY>
2831 </HTML>
2832 ===== h_mainhelp_aggops ======
2833 <HTML>
2834 <HEAD>
2835 <TITLE>Aggregate Operations</TITLE>
2836 </HEAD>
2837 <BODY>
2838 <H1>Aggregate Operations</H1>
2840 When you are in the MESSAGE INDEX, the available commands
2841 (for example, Delete, Undelete, Save, Reply, and so on)
2842 normally act on a single message.
2843 So, for example, if you press the Delete command, the currently highlighted
2844 message is marked Deleted.
2845 These commands that normally act on a single message may be applied to
2846 several messages at once instead.
2847 <P>
2848 By default this feature is turned on, but it could be administratively turned
2849 off to reduce complexity.
2850 The feature
2851 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
2852 in the Setup/Config screen is used to turn it off or on.
2853 When this feature is turned on, the four commands "Select",
2854 "SelectCur", "ZoomMode", and "Apply"
2855 are available.
2856 The two selection commands allow you to mark a set of
2857 messages as being "selected".
2858 The "ZoomMode" command will toggle between
2859 displaying only the selected messages and displaying all the messages.
2860 The "Apply" command allows you to
2861 apply one of the regular MESSAGE INDEX commands to all of the selected
2862 messages instead of to only the highlighted message.
2863 <P>
2864 An example aggregate operation would be to catch up when reading
2865 a news group.
2866 That is, get rid of all the messages in the news group so that you can
2867 start fresh.
2868 The easiest way to do this in Alpine is to use aggregate operations.
2869 You want to Delete all of the messages in the group.
2870 You could start at the top and type "D" once for every message.
2871 A much faster method is to first Select all of the messages in the group,
2872 and then Delete all of them.
2873 This would take four keystrokes:
2874 <P>
2875 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
2876 <BR>
2877 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
2878 <P>
2879 Another use of Select is to use it for searching for a particular message
2880 or set of messages in a large folder.
2881 You may know that the message was From a certain user.
2882 You could select all messages from that user to start, and use Zoom to
2883 look at only those messages.
2884 If there were still too many messages to look at you could Narrow the
2885 set of messages further by selecting from all of those messages only
2886 the ones that were after a certain date, or contained a particular phrase
2887 in the Subject, or were too a particular address, and so on.
2888 That may be the end of what you are doing, or you may want to use Apply to
2889 Save or Forward or Print all of the selected messages.
2890 <P>
2891 Some related help topics are
2892 <UL>
2893 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
2894 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
2895 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
2896 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
2897 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
2898 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
2899 </UL>
2900 <P>
2901 <End of help on this topic>
2902 </BODY>
2903 </HTML>
2904 ===== h_mainhelp_readingnews ======
2905 <HTML>
2906 <HEAD>
2907 <TITLE>Reading News</TITLE>
2908 </HEAD>
2909 <BODY>
2910 <H1>Reading News</H1>
2912 <H2>Background</H2>
2913 Alpine can read and post to Internet (or USENET) newsgroups, using the same
2914 commands as for mail. Similar to mailing lists but existing on a larger scale,
2915 Usenet newsgroups allow groups of people with common interests to discuss
2916 particular topics. You might find newsgroups related to your career, or you
2917 might wish to check out the online discussion among the fans of your favorite
2918 television show.
2920 <H2>Configuring Alpine for Reading News</H2>
2921 Alpine often arrives
2922 pre-configured by your system administrator to automatically access the
2923 newsgroups offered by your organization, Internet Service Provider, or
2924 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
2925 need additional details on <a href="h_configuring_news">how to
2926 configure Alpine to read news</a>.
2928 <H2>Accessing Newsgroups</H2>
2929 The first step in reading news is to access the newsgroups collections
2930 screen from Alpine. If everything is configured properly, you should be able
2931 to do this by first typing L (folder List), then selecting the folder
2932 collection listed as "News." The actual name of this collection may differ
2933 from system to system.
2935 <H2>Subscribing to Newsgroups</H2>
2937 Once you have accessed the news collection, you need to subscribe to a
2938 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
2939 will keep a record of the newsgroups in which you are interested and which
2940 articles in those newsgroups have been read.
2942 <H2>Using Newsgroups</H2>
2943 Alpine uses the similar commands to read news as to read mail. For example,
2944 the D command marks messages as Deleted (or "Dismissed," if you prefer),
2945 and the R command Replies to a news posting. Basically, Alpine allows you to
2946 read news as if it were mail, so you don't need to change the way you
2947 interact with Alpine.
2948 <P>
2949 There is also additional Alpine help available on
2950 <A HREF="h_reading_news">how to use Alpine to read news</A>.
2951 <P>
2952 <End of help on this topic>
2953 </BODY>
2954 </HTML>
2955 ===== h_mainhelp_securing ======
2956 <HTML>
2957 <HEAD>
2958 <TITLE>Securing your Alpine Session</TITLE>
2959 </HEAD>
2960 <BODY>
2961 <H1>Securing your Alpine Session</H1>
2963 By default, Alpine will attempt to connect to an IMAP server on the normal
2964 IMAP service port (143).
2965 If the Alpine you are using has been built to
2966 support "Transport Layer Security" (TLS)
2967 and "Secure Sockets Layer" (SSL)
2968 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
2969 and the server offers the STARTTLS capability, then a secure (encrypted)
2970 session will be established.
2971 <P>
2972 When you are connected to a remote folder the titlebar will contain a plus sign
2973 in the far right column if the connection is encrypted using TLS or SSL.
2974 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
2975 if the connection is encrypted.
2977 <H2>More Information on Alpine with SSL and TLS</H2>
2978 <UL>
2979 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
2980 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
2981 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
2982 <LI> <A HREF="h_config_quell_ssl_largeblocks"><!--#echo var="FEAT_quell-ssl-largeblocks"--></A> PC-Alpine feature for working around OS SSL-problems</A> </LI>
2983 </UL>
2984 <H2>Here are some other security-related features and options</H2>
2985 <P>
2986 <UL>
2987 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
2988 <LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI>
2989 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
2990 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
2991 </UL>
2992 <P>
2993 <End of help on this topic>
2994 </BODY>
2995 </HTML>
2996 ===== h_mainhelp_problems ======
2997 <HTML>
2998 <HEAD>
2999 <TITLE>Reporting Problems</TITLE>
3000 </HEAD>
3001 <BODY>
3002 <H1>Reporting Problems</H1>
3004 We ask that you first read the relevant help screens and then seek
3005 assistance from your own local support staff. Once you are sure that your
3006 difficulty is not a local configuration problem, you might look at the
3007 help section explaining where to look for
3008 <A HREF="h_finding_help">more information</A> and where to
3009 get assistance.
3010 <P>
3012 <ADDRESS>
3013 Eduardo Chappa <chappa@gmx.com>
3014 </ADDRESS>
3016 <P>
3017 <End of help on this topic>
3018 </BODY>
3019 </HTML>
3020 ===== h_main_menu_commands ======
3021 <HTML>
3022 <HEAD>
3023 <TITLE>MAIN MENU COMMANDS</TITLE>
3024 </HEAD>
3025 <BODY>
3026 <H1>MAIN MENU COMMANDS</H1>
3028 <!--chtml if pinemode="function_key"-->
3029 Available Commands --
3030 Group 1 Available Commands -- Group 2<BR>
3031 ------------------------------
3032 --------------------
3033 ----------<BR>
3034 F1 Show this help text F1 Show this help text<BR>
3035 F2 Show all other available commands F2 Show other commands<BR>
3036 F3 Quit Alpine<BR>
3037 F4 Execute current MAIN MENU command F4 <A
3038 HREF="h_common_compose">Compose</A> a message<BR>
3039 F5 Select previous command up on menu F5 <A
3040 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
3041 F6 Select next command down on menu F6 <A
3042 HREF="h_common_goto">Goto</A> a specified folder<BR>
3043
3044 F7 <A
3045 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
3046
3047 F8 <A
3048 HREF="h_main_journal">Journal</A> of status messages<BR>
3049 F9 Display <A
3050 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
3051 HREF="h_main_setup">SETUP</A> menus<BR>
3052 F10 <A
3053 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
3054 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
3055
3056 F11 <A
3057 HREF="h_common_role">Compose message using a role</a><BR>
3058 <!--chtml else-->
3059 General Alpine Commands Main Menu Screen Commands<BR>
3060 --------------------- --------------------------<BR>
3061 ? Show Help Text O Show all Other available commands<BR>
3062 C <A
3063 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
3064 I <A
3065 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
3066 L <A
3067 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
3068 A <A
3069 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
3070 HREF="h_main_kblock">Lock Keyboard</A><BR>
3071 S <A
3072 HREF="h_main_setup">SETUP</A> functions G <A
3073 HREF="h_common_goto">Goto</A> a specified folder<BR>
3074 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
3075 # <A
3076 HREF="h_common_role">Compose message using a role</a><BR>
3077 <!--chtml endif-->
3079 <P>
3080 NOTE:
3081 <OL>
3082 <LI>For help on a particular command, highlight the bold text associated
3083 with it above and hit Return.
3084 <LI> The availability of certain commands (e.g. some of the options under
3085 SETUP) is determined by Alpine configuration files and system capabilities.
3086 At some sites, certain commands may not be available due to security or
3087 support concerns.
3088 </OL>
3089 <P>
3090 <End of help on this topic>
3091 </BODY>
3092 </HTML>
3094 ===== h_command_line_options ======
3095 <HTML>
3096 <HEAD>
3097 <TITLE>COMMAND LINE OPTIONS</TITLE>
3098 </HEAD>
3099 <BODY>
3100 <H1>COMMAND LINE OPTIONS</H1>
3101 Possible starting arguments for Alpine:
3103 <DL COMPACT>
3105 <DT> <EM>[addresses]</EM>
3107 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
3108 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
3109 <EM>Alpine</EM> will startup in
3110 the composer with a message started to the addresses specified.
3111 Once the message is sent, the <EM>Alpine</EM> session closes.
3112 Standard input redirection is allowed.
3113 Separate multiple addresses with a space between them.
3114 Addresses are placed in the "To" field only.
3115 <P>
3117 <DT> < <EM>file</EM>
3119 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
3120 into the body of the message.
3121 Once the message is sent, the <EM>Alpine</EM> session closes.
3122 <P>
3124 <DT> -attach <EM>file</EM>
3126 <DD> Go directly into composer with given file attached.
3127 <P>
3129 <DT> -attachlist <EM>file-list</EM>
3131 <DD> Go directly into composer with given files attached.
3132 This must be the last option on the command line.
3133 <P>
3135 <DT> -attach_and_delete <EM>file</EM>
3137 <DD> Go directly into composer with given file attached, delete when finished.
3138 <P>
3140 <DT> -aux <EM>local_directory</EM>
3142 <DD> <EM>PC-Alpine</EM> only.
3143 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
3144 files, like debug files, address books, and signature files. The pinerc may
3145 be local or remote.
3146 <P>
3148 <DT> -bail
3150 <DD> If the personal configuration file doesn't already exist, exit.
3151 This might be useful if the configuration file is accessed using some
3152 remote filesystem protocol. If the remote mount is missing this will cause
3153 <EM>Alpine</EM> to quit instead of creating a new pinerc.
3154 <P>
3156 <DT> -c <EM>n</EM>
3158 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
3159 This is used when there are multiple folder collections (contexts) and you
3160 want to open a folder not in the primary collection.
3161 <P>
3163 <DT> -conf
3165 <DD> Configuration: Prints a sample system configuration file to the
3166 screen or standard output. To generate an initial system configuration
3167 file, execute
3169 <PRE><CODE>
3170 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
3171 </CODE></PRE>
3172 <P>
3174 To generate a system configuration file using settings from an old
3175 system configuration file, execute
3177 <PRE><CODE>
3178 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
3179 </CODE></PRE>
3180 <P>
3181 A system configuration file is not required.
3182 <P>
3184 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
3186 <DD> Copy an address book file to a remote address book folder.
3187 If the remote folder doesn't exist, it will be created.
3188 If it exists but the first message in the folder isn't a remote address
3189 book header message, the copy will be aborted.
3190 This flag will not usually be used by a user.
3191 Instead, the user will create a remote address book from within <EM>Alpine</EM>
3192 and copy entries from the local address book by using aggregate Save in
3193 the address book screen.
3194 <P>
3196 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
3198 <DD> Copy a pinerc configuration file to a remote pinerc folder.
3199 If the remote folder doesn't exist, it will be created.
3200 If it exists but the first message in the folder isn't a remote pinerc
3201 header message, the copy will be aborted.
3202 This flag may be useful to users who already have a local pinerc file and
3203 would like to convert it to a remote pinerc folder and use that instead.
3204 This gives a way to bootstrap that conversion without having to manually
3205 reset all of the variables in the remote pinerc folder.
3206 <P>
3208 <DT> -d <EM>debug-level</EM>
3210 <DD> Debug Level: Sets the level of debugging information written by
3211 <EM>Alpine</EM>.
3212 <EM>debug-level</EM> can be set to any integer 0-9.
3213 A debug level of 0 turns off debugging for the session.
3214 (Actually there are some levels higher than 9, but you probably don't
3215 want to see them.)
3216 <P>
3218 <DT> -d <EM>keywords</EM>
3220 <DD> You may use a more detailed version of the debugging flag to set
3221 the debug level in separate parts of <EM>Alpine</EM>.
3222 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
3223 verbose=0..9.
3224 <EM>Flush</EM> causes debugging information to be flushed immediately to
3225 the debug file as it is written.
3226 <EM>Verbose</EM> is the general debugging verbosity level.
3227 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
3228 is useful when you are trying to figure out what is responsible for delays.
3229 <EM>Numfiles</EM> sets the number of debug files saved.
3230 <EM>Imap</EM> sets the debug level for the debugging statements related
3231 to the conversation with the IMAP server, and more generally, for the
3232 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
3233 <EM>Tcp</EM> turns on some TCP/IP debugging.
3234 <P>
3236 <DT> -f <EM>folder</EM>
3238 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
3239 of the standard INBOX.
3240 <P>
3242 <DT> -F <EM>file</EM>
3244 <DD> Open named text file for viewing and forwarding.
3245 <P>
3247 <DT> -h
3249 <DD> Help: Prints the list of available command-line arguments to the
3250 screen.
3251 <P>
3253 <DT> -i
3255 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
3256 screen instead of the MAIN MENU.
3257 <P>
3259 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
3260 <P>
3262 <DT> -I <EM>a,b,c,...</EM>
3264 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
3265 sequence of commands upon startup.
3266 This allows users to get <EM>Alpine</EM> to start in any
3267 of its menus/screens.
3268 You cannot include any input to the composer in the initial keystrokes.
3269 The key <Return> is represented by a ``CR'' in
3270 the keystroke list; the spacebar is designated by the letters ``SPACE''.
3271 Control keys are two character sequences beginning with ``^'', such as
3272 ``^I''.
3273 A tab character is ``TAB''.
3274 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
3275 ``DOWN'', ``LEFT'', and ``RIGHT''.
3276 A restriction is that you can't mix function keys and character keys in this
3277 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
3278 A user can always use only <EM>character</EM> keys in the startup list even
3279 if he or she is using <EM>function</EM> keys normally, or vice versa.
3280 If an element in this list is a string of characters surrounded by double
3281 quotes (") then it will be expanded into the individual characters in
3282 the string, excluding the double quotes.
3283 <P>
3285 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
3286 <P>
3288 <DT> -install
3290 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
3291 some basic information to help with getting properly set up.
3292 <P>
3294 <DT> -k
3296 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
3297 the input of commands to be function-keys.
3298 Otherwise, commands are linked to the regular character keys.
3299 <P>
3301 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
3302 <EM>Feature-List</EM>.
3303 <P>
3305 <DT> -n <EM>n</EM>
3307 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
3308 FOLDER INDEX screen with the current message being the specified
3309 message number.
3310 <P>
3312 <DT> -nosplash
3314 <DD> <EM>PC-Alpine</EM> only.
3315 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
3316 This may be helpful for certain troubleshooting or terminal server scenarios.
3317 <P>
3319 <DT> -o <EM>folder</EM>
3321 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
3322 <P>
3324 <DT> -p <EM>pinerc</EM>
3326 <DD> Uses the named file as the personal configuration file instead of
3327 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
3328 Alpinerc may be either a local file or a remote configuration folder.
3329 <P>
3331 <DT> -P <EM>pinerc</EM>
3333 <DD> Uses the named file as the system wide configuration file instead of
3334 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
3335 Alpinerc may be either a local file or a remote configuration folder.
3336 <P>
3338 <DT> -passfile <EM>passfile</EM>
3340 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
3341 This should be a fully-qualified filename.
3342 <P>
3344 <DT> -pinerc <EM>file</EM>
3346 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
3347 settings of variables that the user has made.
3348 Use <EM>file</EM> set to ``-'' to make output go to standard out.
3349 <P>
3351 <DT> -r
3353 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
3354 <EM>Alpine</EM> in restricted mode can only send email to itself.
3355 Save and export are limited.
3356 <P>
3358 <DT> -registry <EM>cmd</EM>
3360 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
3361 <EM>Alpine</EM>'s registry entries.
3362 Possible values for <EM>cmd</EM> are set, clear, and dump.
3363 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
3364 entries according to its current settings.
3365 <EM>Clear</EM> will clear the registry values.
3366 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3367 <EM>Dump</EM> will display the values of current registry settings.
3368 Note that the dump command is currently disabled.
3369 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3370 the registry only if there currently aren't any values set.
3371 <P>
3373 <DT> -sort <EM>key</EM>
3375 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3376 FOLDER INDEX screen.
3377 <EM>Key</EM> can have the following values:
3378 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3379 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3380 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3381 The default value is "arrival".
3382 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3383 <P>
3385 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3386 <P>
3388 <DT> -uninstall
3390 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3391 in Windows settings. The registry settings are removed and
3392 the password cache is cleared.
3393 <P>
3395 <DT> -url <EM>url</EM>
3397 <DD> Open the given URL.
3398 <P>
3400 <DT> -v
3402 <DD> Version: Print version information to the screen.
3403 <P>
3405 <DT> -x <EM>exceptions_config</EM>
3407 <DD> Configuration settings in the exceptions configuration override your normal
3408 default settings.
3409 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3410 <P>
3412 <DT> -z
3414 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3415 will suspend the <EM>Alpine</EM> session.
3416 <P>
3418 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3419 <EM>Feature-List</EM>.
3420 <P>
3422 <DT> -<EM>option</EM>=<EM>value</EM>
3424 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3425 For example, <EM>-signature-file=sig1</EM> or
3426 <EM>-Feature-List=signature-at-bottom</EM>.
3427 Note: Feature-List values are
3428 additive and features may be preceded with no- to turn them off.
3429 Also, as a special case, the "Feature-List=" part of that may be
3430 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3431 <EM>-Feature-List=signature-at-bottom</EM>.
3432 <P>
3434 </DL>
3435 <P>
3436 <End of help on this topic>
3437 </BODY>
3438 </HTML>
3439 ===== h_configuring_news ======
3440 <HTML>
3441 <HEAD>
3442 <TITLE>CONFIGURING NEWS</TITLE>
3443 </HEAD>
3444 <BODY>
3445 <H1>CONFIGURING NEWS</H1>
3446 Alpine can access news folders in any one of three different ways:
3447 <DL>
3448 <DT>REMOTE NNTP</DT>
3449 <DD>Using the Network News Transport Protocol (NNTP) to
3450 access news on a remote news server. In this case the newsrc file is
3451 stored on the machine where Alpine is running.
3453 <P>
3454 To specify a remote news-collection accessed via NNTP use the
3455 SETUP/collectionList screen's "Add" command. Set the
3456 Server: value to the NNTP server's hostname appended with the
3457 communication method "/service=NNTP", and set the Path:
3458 value to the "#news." namespace (without the quotes). See
3459 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3460 help text for a more complete explanation of access method, and the
3461 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3462 text for a more complete explanation of "namespace".
3463 <P>
3464 Instead of specifying a news-collection, you may simply set the
3465 <A HREF="h_config_nntp_server">NNTP Server</A>
3466 option, which will cause Alpine to create a default news-collection for you.
3467 Another NNTP option that may be of interest is
3468 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3470 <DT>REMOTE IMAP</DT>
3471 <DD>Using the Internet Message Access Protocol (IMAP) to
3472 access news on a remote news server. In this case, your newsrc file is
3473 stored on the news server, in your home directory, so you must have an
3474 account on the news server, but you would be running Alpine on a different
3475 machine. The news server must be running an IMAPd server process.
3477 <P>
3478 To specify a remote news-collection accessed via IMAP use the
3479 SETUP/collectionList screen's "Add" command. Set the
3480 Server: value to the IMAP server's hostname, and set the Path: value
3481 to the "#news." namespace (without the quotes). See the
3482 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3483 text for a more complete explanation of "namespace".
3485 </DD>
3487 <DT>LOCAL</DT>
3488 <DD>Using local file access to the news database. In this
3489 case, your newsrc file is stored on the news server, in your home
3490 directory, so you must have an account on the news server, and you would
3491 be running Alpine on the same machine.
3493 <P>
3494 To specify a local news-collection use the SETUP/collectionList
3495 screen's "Add" command. Leave the Server: value blank, and
3496 set the Path: value to the "#news." namespace (without the
3497 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3498 field's help text for a more complete explanation of "namespace".
3500 </DD>
3501 </DL>
3503 <P>
3505 NOTE: Should no news-collection be defined as above, Alpine will
3506 automatically create one using the Setup/Config screen's
3507 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3508 will be created as a "Remote NNTP" as described above.
3510 <P>
3512 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3513 possible. If you don't have an account on the news server, or if the news
3514 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3515 sure, ask your service provider, university, or company for help.) In
3516 this case, your Unix .newsrc file can be transferred to your PC. A good
3517 place to put it would be in the same directory as your PINERC file, under
3518 the name NEWSRC, but you can
3519 <A HREF="h_config_newsrc_path">specify a different location</A>
3520 via Alpine's Setup/Config screen.
3522 <P>
3523 Other configuration features related to news are
3524 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3525 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3526 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3527 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3528 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3529 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3530 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3531 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3533 <P>
3534 <End of help on this topic>
3535 </BODY>
3536 </HTML>
3537 ===== h_reading_news ======
3538 <HTML>
3539 <HEAD>
3540 <TITLE>READING NEWS</TITLE>
3541 </HEAD>
3542 <BODY>
3543 <H1>READING NEWS</H1>
3545 Alpine uses almost the same commands for manipulating news folders as for
3546 mail folders. This means, for example, that when you are done with a
3547 message, you would use "D" to mark it as Deleted (or Dismissed,
3548 if you prefer.) This "mail-like" behavior differs from that of
3549 most newsreaders, wherein a message is implicitly dismissed after you have
3550 looked at it once. We strongly believe that Alpine should offer as much
3551 consistency as possible between mail and news, so the mail paradigm --
3552 wherein a message does not magically disappear without explicit action by
3553 the user -- is used for news as well. <P>
3555 If you answer a message in a news folder, the index view will show the
3556 "A" flag as usual; but the industry standard file Alpine uses to
3557 keep track of what news as been read has no way of storing this flag, so
3558 it will not be preserved across sessions. The Deleted flag is the only
3559 one that is preserved when you leave and then return to a newsgroup. As an
3560 additional note on replies, when you Reply to a newsgroup message and say
3561 you want to reply to all recipients, Alpine will ask if you want to post the
3562 message to all the newsgroups listed in the original message. <P>
3564 If you would like Alpine to mark more-or-less recent news messages as
3565 "New", then set the
3566 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3567 feature (which is set by default). This will cause messages after the last one you have marked as
3568 Deleted to appear with "N" status in the MESSAGE INDEX. The
3569 "N" status often makes it easier to distinguish later news
3570 articles from those you've previously seen, but not yet disposed of via
3571 the "D" key. Note that this is an approximation, not an exact
3572 record of which messages you have not seen.
3573 <P>
3575 A frequent operation in news-reading is "catching up" -- that
3576 is, getting rid of all the messages in the newsgroup so that you can
3577 "start fresh." The easiest way to do this in Alpine is via the
3578 Select command. You would enter the following four keystrokes:
3579 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3580 dismiss) command to all of them.
3582 <P>
3583 There are also additional details on
3584 <A HREF="h_configuring_news">configuring news</a>.
3586 <P>
3587 <End of help on this topic>
3588 </BODY>
3589 </HTML>
3590 ====== h_help_index ======
3591 <HTML>
3592 <HEAD>
3593 <TITLE>Help Index</TITLE>
3594 </HEAD>
3595 <BODY>
3596 <H1>Help Index</H1>
3597 <ul>
3598 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3599 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3600 <li><a href="h_main_addrbook">Address Book Command</a>
3601 <li><a href="h_abook_view">Address Book View Explained</a>
3602 <li><a href="h_compose_addrcomplete">Address Completion</a>
3603 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3604 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3605 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3606 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3607 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3608 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3609 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3610 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3611 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3612 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3613 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3614 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3615 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3616 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3617 <li><a href="h_news_legal">Alpine Legal Notices</a>
3618 <li><a href="h_compose_alted">Alt Editor Command</a>
3619 <li><a href="h_index_cmd_apply">Apply Command</a>
3620 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3621 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3622 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3623 <li><a href="h_composer_browse">BROWSER</a>
3624 <li><a href="h_common_bounce">Bounce Command</a>
3625 <li><a href="h_compose_cancel">Cancel Command</a>
3626 <li><a href="h_config_change_your_from">Changing your From Address</a>
3627 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3628 <li><a href="h_mainhelp_color">Color</a>
3629 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3630 <li><a href="h_composer">COMPOSER COMMANDS</a>
3631 <li><a href="h_mainhelp_composing">Composing Messages</a>
3632 <li><a href="h_mainhelp_collections">Collection Lists</a>
3633 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3634 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3635 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3636 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3637 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3638 <li><a href="h_common_compose">Compose Command</a>
3639 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3640 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3641 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3642 <li><a href="h_mainhelp_config">Configuration</a>
3643 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3644 <li><a href="h_config_dflt_color">Default Color</a>
3645 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3646 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3647 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3648 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3649 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3650 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3651 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3652 <li><a href="h_ge_export">Export File Selection</a>
3653 <li><a href="h_ge_allparts">Export Message File Selection</a>
3654 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3655 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3656 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3657 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3658 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3659 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3660 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3661 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3662 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3663 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3664 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3665 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3666 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3667 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3668 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3669 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3670 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3671 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3672 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3673 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3674 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3675 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3676 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3677 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3678 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3679 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3680 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3681 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3682 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3683 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3684 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3685 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3686 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3687 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3688 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3689 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3690 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3691 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3692 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3693 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3694 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3695 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3696 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3697 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3698 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3699 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3700 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3701 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3702 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3703 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3704 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3705 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3706 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3707 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3708 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3709 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3710 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3711 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3712 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3713 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3714 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3715 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3716 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3717 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3718 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3719 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3720 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3721 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3722 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3723 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3724 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3725 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3726 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3727 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3728 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3729 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
3730 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
3731 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
3732 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
3733 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
3734 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
3735 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
3736 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
3737 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
3738 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
3739 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
3740 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
3741 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
3742 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
3743 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
3744 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
3745 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
3746 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
3747 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
3748 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
3749 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
3750 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
3751 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
3752 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
3753 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
3754 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
3755 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
3756 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
3757 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
3758 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
3759 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
3760 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
3761 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
3762 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
3763 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
3764 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
3765 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
3766 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
3767 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
3768 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
3769 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
3770 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
3771 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
3772 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
3773 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
3774 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
3775 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
3776 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
3777 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
3778 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
3779 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
3780 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
3781 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
3782 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
3783 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
3784 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
3785 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
3786 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
3787 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
3788 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
3789 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
3790 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
3791 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
3792 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
3793 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
3794 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
3795 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
3796 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
3797 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
3798 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
3799 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
3800 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
3801 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
3802 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
3803 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
3804 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
3805 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
3806 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
3807 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
3808 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
3809 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
3810 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
3811 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
3812 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
3813 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
3814 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
3815 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
3816 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
3817 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
3818 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
3819 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
3820 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
3821 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
3822 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
3823 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
3824 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
3825 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
3826 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
3827 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
3828 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
3829 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
3830 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
3831 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
3832 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
3833 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
3834 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
3835 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
3836 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
3837 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
3838 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
3839 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
3840 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
3841 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
3842 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
3843 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
3844 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
3845 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
3846 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
3847 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
3848 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
3849 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
3850 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
3851 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
3852 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
3853 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
3854 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
3855 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
3856 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
3857 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
3858 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
3859 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
3860 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
3861 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
3862 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
3863 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
3864 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
3865 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
3866 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
3867 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
3868 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
3869 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
3870 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
3871 <li><a href="h_mainhelp_filtering">Filtering</a>
3872 <li><a href="h_finding_help">Finding more information and requesting help</a>
3873 <li><a href="h_common_flag">Flag Command</a>
3874 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
3875 <li><a href="h_mainhelp_folders">Folders</a>
3876 <li><a href="h_what_are_collections">Folder Collections Explained</a>
3877 <li><a href="h_common_folders">Folder List Command</a>
3878 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
3879 <li><a href="h_folder_save">Folder Select for Save Explained</a>
3880 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
3881 <li><a href="h_config_change_your_from">From Address, Changing</a>
3882 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
3883 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
3884 <li><a href="h_common_goto">Goto Command</a>
3885 <li><a href="h_common_hdrmode">HdrMode Command</a>
3886 <li><a href="h_mainhelp_pinehelp">Help</a>
3887 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
3888 <li><a href="h_folder_maint">Help for Folder List</a>
3889 <li><a href="h_valid_folder_names">IMAP</a>
3890 <li><a href="h_ge_import">Import File Selection</a>
3891 <li><a href="h_mainhelp_index">Index of Messages</a>
3892 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
3893 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
3894 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
3895 <li><a href="h_info_on_mbox">Information on mbox driver</a>
3896 <li><a href="h_mainhelp_intro">Introduction</a>
3897 <li><a href="h_main_journal">Journal Command</a>
3898 <li><a href="h_common_jump">Jump Command</a>
3899 <li><a href="h_compose_justify">Justify Command</a>
3900 <li><a href="h_main_kblock">Keyboard Lock Command</a>
3901 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
3902 <li><a href="h_mainhelp_ldap">LDAP</a>
3903 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
3904 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
3905 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
3906 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
3907 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
3908 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
3909 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
3910 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
3911 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
3912 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
3913 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
3914 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
3915 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
3916 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
3917 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
3918 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
3919 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
3920 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
3921 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
3922 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
3923 <li><a href="h_ldap_view">LDAP Response View Explained</a>
3924 <li><a href="h_maildrop">Mail Drop: What is it?</a>
3925 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
3926 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
3927 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
3928 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
3929 <li><a href="h_common_index">Message Index Command</a>
3930 <li><a href="h_mainhelp_mouse">Mouse</a>
3931 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
3932 <li><a href="new_user_greeting">NEW USER GREETING</a>
3933 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
3934 <li><a href="h_mainhelp_readingnews">News Reading</a>
3935 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
3936 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
3937 <li><a href="h_common_nextnew">NextNew Command</a>
3938 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
3939 <li><a href="h_mainhelp_readingnews">NNTP</a>
3940 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
3941 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
3942 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
3943 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
3944 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
3945 <li><a href="h_config_color_style">OPTION: Color Style</a>
3946 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
3947 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
3948 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
3949 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
3950 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
3951 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
3952 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
3953 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
3954 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
3955 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
3956 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
3957 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
3958 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
3959 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
3960 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
3961 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
3962 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
3963 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
3964 <li><a href="h_config_file_dir">OPTION: File Directory</a>
3965 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
3966 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
3967 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
3968 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
3969 <li><a href="h_config_font_name">OPTION: Font Name</a>
3970 <li><a href="h_config_font_size">OPTION: Font Size</a>
3971 <li><a href="h_config_font_style">OPTION: Font Style</a>
3972 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
3973 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
3974 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
3975 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
3976 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
3977 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
3978 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
3979 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
3980 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
3981 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
3982 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
3983 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
3984 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
3985 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
3986 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
3987 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
3988 <li><a href="h_config_index_color">OPTION: Index Colors</a>
3989 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
3990 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
3991 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
3992 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
3993 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
3994 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
3995 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
3996 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
3997 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
3998 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
3999 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
4000 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
4001 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
4002 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
4003 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
4004 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
4005 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
4006 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
4007 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
4008 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
4009 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
4010 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
4011 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
4012 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
4013 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
4014 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
4015 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
4016 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
4017 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
4018 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
4019 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
4020 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
4021 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
4022 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
4023 <li><a href="h_config_pat_old">OPTION: Patterns</a>
4024 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
4025 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
4026 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
4027 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
4028 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
4029 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
4030 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
4031 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
4032 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
4033 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
4034 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
4035 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
4036 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
4037 <li><a href="h_config_printer">OPTION: Printer</a>
4038 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
4039 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
4040 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
4041 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
4042 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
4043 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
4044 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
4045 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
4046 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
4047 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
4048 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
4049 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
4050 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
4051 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
4052 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
4053 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
4054 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
4055 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
4056 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
4057 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
4058 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
4059 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
4060 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
4061 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
4062 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
4063 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
4064 <li><a href="h_config_aspell_dictionary">OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></a>
4065 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
4066 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
4067 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
4068 <li><a href="h_config_status_color">OPTION: Status Color</a>
4069 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
4070 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
4071 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
4072 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
4073 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
4074 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
4075 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
4076 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
4077 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
4078 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
4079 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
4080 <li><a href="h_config_title_color">OPTION: Title Color</a>
4081 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
4082 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
4083 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
4084 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
4085 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
4086 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
4087 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
4088 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
4089 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
4090 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
4091 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
4092 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
4093 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
4094 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
4095 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
4096 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
4097 <li><a href="h_config_window_position">OPTION: Window-Position</a>
4098 <li><a href="h_mainhelp_patterns">Patterns</a>
4099 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
4100 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
4101 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
4102 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
4103 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
4104 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
4105 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
4106 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
4107 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
4108 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
4109 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
4110 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
4111 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
4112 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
4113 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
4114 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
4115 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
4116 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
4117 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
4118 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
4119 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
4120 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
4121 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
4122 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
4123 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
4124 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
4125 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
4126 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
4127 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
4128 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
4129 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
4130 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
4131 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
4132 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
4133 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
4134 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
4135 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
4136 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
4137 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
4138 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
4139 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
4140 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
4141 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
4142 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
4143 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
4144 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
4145 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
4146 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
4147 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
4148 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
4149 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
4150 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
4151 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
4152 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
4153 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
4154 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
4155 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
4156 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
4157 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
4158 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
4159 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
4160 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
4161 <li><a href="h_common_pipe">Pipe Command</a>
4162 <li><a href="h_valid_folder_names">POP</a>
4163 <li><a href="h_common_postpone">Postpone Command</a>
4164 <li><a href="h_common_print">Print Command</a>
4165 <li><a href="h_mainhelp_readingnews">Reading News</a>
4166 <li><a href="h_news">RELEASE NOTES for Alpine</a>
4167 <li><a href="h_mainhelp_roles">Roles</a>
4168 <li><a href="h_role_select">ROLES SCREEN</a>
4169 <li><a href="h_compose_readfile">Read File Command</a>
4170 <li><a href="h_mainhelp_reading">Reading Messages</a>
4171 <li><a href="h_main_release_notes">Release Notes Command</a>
4172 <li><a href="h_common_reply">Reply and Forward Commands</a>
4173 <li><a href="h_compose_richhdr">Rich Header Command</a>
4174 <li><a href="h_common_role">Role Command</a>
4175 <li><a href="h_mainhelp_smime">S/MIME</a>
4176 <li><a href="h_index_cmd_select">Searching for Messages</a>
4177 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
4178 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
4179 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
4180 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
4181 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
4182 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
4183 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
4184 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
4185 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
4186 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
4187 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
4188 <li><a href="h_common_save">Save and Export Commands</a>
4189 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
4190 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
4191 <li><a href="h_compose_send">Send Command</a>
4192 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
4193 <li><a href="h_main_setup">Setup Command</a>
4194 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
4195 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
4196 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
4197 <li><a href="h_mainhelp_smime">S/MIME</a>
4198 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
4199 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
4200 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
4201 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
4202 <li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a>
4203 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
4204 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
4205 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
4206 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
4207 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
4208 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
4209 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
4210 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
4211 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
4212 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
4213 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
4214 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
4215 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
4216 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
4217 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
4218 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
4219 <li><a href="h_index_cmd_sort">Sort Command</a>
4220 <li><a href="h_compose_spell">Spell Check Command</a>
4221 <li><a href="h_common_suspend">Suspend Command</a>
4222 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
4223 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
4224 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
4225 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
4226 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
4227 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
4228 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
4229 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
4230 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
4231 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
4232 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
4233 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
4234 <li><a href="h_common_take">TakeAddr Command</a>
4235 <li><a href="h_mainhelp_status">Titlebar Line</a>
4236 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
4237 <li><a href="h_config_usenone_color">Use None Color</a>
4238 <li><a href="h_config_usenormal_color">Use Normal Color</a>
4239 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
4240 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
4241 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
4242 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
4243 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
4244 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
4245 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
4246 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
4247 </UL>
4249 <P>
4250 <End of Help Index>
4251 </BODY>
4252 </HTML>
4255 ============== h_config_remote_config =============
4256 <HTML>
4257 <HEAD>
4258 <TITLE>Remote Configuration</TITLE>
4259 </HEAD>
4260 <BODY>
4261 <H1>Remote Configuration</H1>
4263 You may use the command line argument "-p pinerc" to tell
4264 Alpine to use a non-default configuration file.
4265 There are two types of storage for configuration information.
4266 <EM>Local</EM> configuration files are used by default.
4267 These are just regular files on the UNIX system or on the PC.
4268 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
4269 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
4270 <EM>Remote</EM> configuration folders are stored on an IMAP server.
4271 The advantage of using a remote configuration is that the same information
4272 may be accessed from multiple platforms.
4273 For example, if you use one computer at work and another at home, the same
4274 configuration could be used from both places.
4275 A configuration change from one place would be seen in both places.
4276 To use a remote configuration you simply give a
4277 <A HREF="h_valid_folder_names">remote folder name</A>
4278 as the argument to the "-p" command line option.
4279 The command line might look something like:
4280 <P>
4281 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
4282 <P>
4283 If there are special characters in the command shell you use, you may need to
4284 quote the last argument (to protect the curly braces from the shell).
4285 The command might look like:
4286 <P>
4287 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
4288 <P>
4289 You should choose a folder name for a folder that does not yet exist.
4290 It will be created containing an empty configuration.
4291 Do not use a folder that you wish to store regular mail messages in.
4292 <P>
4293 The Setup/RemoteConfigSetup command will help you convert from a local
4294 configuration to a remote configuration.
4295 It will create a remote configuration for you and copy your current local
4296 configuration to it.
4297 It will also help you convert local address books into remote address books
4298 and local signature files into literal signatures contained in the
4299 remote configuration file.
4300 <P>
4301 If the Setup/RemoteConfigSetup command doesn't do what you want, you
4302 may copy a local pinerc file to a remote configuration folder by hand
4303 by using the command line option "-copy_pinerc".
4304 <P>
4305 Another command line option, which is somewhat related to remote
4306 configuration, is the option "-x exceptions_config".
4307 The configuration settings in the exceptions configuration override
4308 your default settings.
4309 It may be useful to store the default configuration (the -p argument) remotely
4310 and to have the exceptions configuration stored in a local file.
4311 You might put generic configuration information in the remote configuration
4312 and platform-specific configuration on each platform in the exceptions
4313 configuration.
4314 The arguments to the "-p" and "-x" options
4315 can be either remote folders or local files.
4316 <P>
4317 There is another command line argument that works only with PC-Alpine and
4318 which may prove useful when using a remote configuration.
4319 The option "-aux local_directory" allows you to tell PC-Alpine where
4320 to store your local auxiliary files.
4321 This only has an effect if your configuration file is remote.
4322 Some examples of auxiliary files are debug files, address book files, and
4323 signature files.
4324 <P>
4325 <End of help on this topic>
4326 </BODY>
4327 </HTML>
4328 ============== h_config_exceptions =============
4329 <HTML>
4330 <HEAD>
4331 <TITLE>Generic and Exceptional Configuration</TITLE>
4332 </HEAD>
4333 <BODY>
4334 <H1>Generic and Exceptional Configuration</H1>
4336 If you use Alpine from more than one platform it may be convenient
4337 to split your configuration information into two pieces, a generic piece
4338 and exceptions that apply to a particular platform.
4339 For example, suppose you use Alpine from home and from work.
4340 Most of your configuration settings are probably the
4341 same in both locations, so those settings belong in the generic settings
4342 configuration.
4343 However, you may use a different SMTP server and INBOX
4344 from home than you do from work.
4345 The
4346 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
4347 and
4348 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
4349 options could be
4350 part of your exceptional configuration so that they could be different in the
4351 two places.
4352 <P>
4353 The command line option "-x exceptions_config"
4354 may be used to split your configuration into generic and exceptional pieces.
4355 "Exceptions_config" may be either local or remote.
4356 The regular Alpine configuration file will contain the generic data, and
4357 "exceptions_config" will contain the exceptional data.
4358 <P>
4359 For Unix Alpine, if you don't have a "-x" command line option,
4360 Alpine will look for the file "<CODE>.pinercex</CODE>"
4361 in the same local directory that the regular config file is located in (usually
4362 the Unix home directory).
4363 If the regular config file is remote (because the command line option
4364 "-p remote_config" was used) then Unix Alpine looks in the Unix home
4365 directory for "<CODE>.pinercex</CODE>".
4366 If the file does not already exist then no exceptions will be used.
4367 You can force exceptions to be used by using the "-x" option or
4368 by creating an empty "<CODE>.pinercex</CODE>" file.
4369 <P>
4370 For PC-Alpine, if you don't have a "-x" command line option,
4371 PC-Alpine will use the value of the
4372 environment variable <CODE>$PINERCEX</CODE>.
4373 If that is not set, PC-Alpine will look for
4374 the local file "<CODE>PINERCEX</CODE>"
4375 in the same local directory that the regular config file is located in.
4376 If the regular config file is remote (because the command line option
4377 "-p remote_config" was used) then PC-Alpine looks in the
4378 local directory specified by the "-aux local_directory" command
4379 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4380 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4381 <P>
4382 When you have an exception configuration there is a new command
4383 in the Alpine Setup screen, Setup/eXceptions.
4384 It toggles between exceptions and the regular configuration.
4385 This is the usual way to make changes in your exceptional configuration data.
4386 For example, you would type "S" for Setup, "X" for
4387 eXception, then follow that with one of the Setup commands, like "C"
4388 for Config or "K" for Kolor.
4389 <P>
4390 For most people, splitting the configuration information into two pieces is
4391 going to be most useful if the generic information is accessed
4392 <A HREF="h_config_remote_config">remotely</A>).
4393 That data will be the same no matter where you access it from and if you
4394 change it that change will show up everywhere.
4395 The exceptional data will most commonly be in a local file, so that the
4396 contents may easily be different on each computing platform used.
4397 <P>
4398 If you already have a local configuration file with settings you like
4399 you may find that the command Setup/RemoteConfigSetup is useful
4400 in helping you convert to a remote configuration.
4401 The command line flag "-copy_pinerc"
4402 may also be useful.
4403 <P>
4404 <End of help on this topic>
4405 </BODY>
4406 </HTML>
4407 ============== h_config_inheritance =============
4408 <HTML>
4409 <HEAD>
4410 <TITLE>Configuration Inheritance</TITLE>
4411 </HEAD>
4412 <BODY>
4413 <H1>Configuration Inheritance</H1>
4415 Configuration inheritance is a power user feature.
4416 It is confusing and not completely supported by the configuration
4417 user interface.
4418 We start with an explanation of how configuration works in hopes of making
4419 it easier to describe how inheritance works.
4420 <P>
4421 Alpine uses a hierarchy of configuration values from different locations.
4422 There are five ways in which each configuration option (configuration
4423 variable) can be set.
4424 In increasing order of precedence they are:
4425 <P>
4426 <OL>
4427 <LI> the system-wide configuration file.
4429 <LI> the personal configuration file
4431 <LI> the personal exceptions file
4433 <LI> a command line argument
4435 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4436 </OL>
4437 <P>
4438 The fixed configuration file is normally
4439 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4440 <P>
4441 The system-wide configuration file is normally
4442 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4443 set for PC-Alpine.
4444 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4445 is used for the system-wide configuration.
4446 This location can be set or changed on the command line with the -P flag.
4447 The system-wide configuration file can be either a local file or a
4448 remote configuration folder.
4449 <P>
4450 For Unix Alpine, the personal configuration file is normally the file
4451 <CODE>.pinerc</CODE> in the user's home directory.
4452 This can be changed with the -p command line flag.
4453 For PC-Alpine, the personal configuration file is in
4454 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4455 <CODE>$HOME\PINE\PINERC</CODE> or
4456 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4457 This can be changed with the -p command line flag.
4458 If -p is used, the configuration data may be in a local file or a remote config
4459 folder.
4460 <P>
4461 For Unix Alpine, the personal exceptions configuration file is named
4462 <CODE>.pinercex</CODE> and is in the same directory as the personal
4463 configuration file, if that configuration file is not remote, and is in
4464 the home directory if the personal configuration file is remote.
4465 If the file exists, then exceptions are turned on.
4466 If it doesn't, then you are not using exceptions.
4467 Alternatively, you may change the location of the exceptions configuration
4468 by using the command line argument "-x <exceptions_config>".
4469 Like the personal configuration data, exceptions_config may be
4470 either local or remote.
4471 <P>
4472 For PC-Alpine, the personal exceptions configuration file is named
4473 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4474 configuration file unless the personal configuration file is remote.
4475 In that case, it is in the local directory specfied by the
4476 "-aux local_directory" command line argument.
4477 (In the case that the personal configuration is remote and there is no
4478 "-aux" command line argument, Alpine searches for
4479 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4480 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4481 If the file exists, then exceptions are turned on.
4482 If it doesn't, then you are not using exceptions.
4483 You may change the location of the exceptions configuration
4484 by using the command line argument "-x <exceptions_config>".
4485 or with the
4486 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4487 option).
4488 <P>
4489 To reiterate, the value of a configuration option is taken from the
4490 last location in the list above in which it is set.
4491 Or, thinking about it slightly differently, a default value for an option
4492 is established in the system-wide configuration file (or internally by Alpine
4493 if there is no value in the system-wide file).
4494 That default remains in effect until and unless it is overridden by a value in a
4495 location further down the list, in which case a new "default"
4496 value is established.
4497 As we continue down the list of locations we either retain the
4498 value at each step or establish a new value.
4499 The value that is still set after going through the whole list of
4500 configuration locations is the one that is used.
4501 <P>
4502 So, for example, if an option is set in the system-wide configuration
4503 file and in the personal configuration file, but is not set in the
4504 exceptions, on the command line, or in the fixed file; then the value
4505 from the personal configuration file is the one that is used.
4506 Or, if it is set in the system-wide config, in the personal config, not
4507 in the exceptions, but is set on the command line; then the value
4508 on the command line is used.
4509 <P>
4510 Finally we get to inheritance.
4511 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4512 "<!--#echo var="VAR_incoming-folders"-->",
4513 the inheritance mechanism makes it possible to <EM>combine</EM>
4514 the values from different locations instead of <EM>replacing</EM> the value.
4515 This is true of all configuration lists other than the "Feature-List",
4516 for which you may already set whatever you want at
4517 any configuration location (by using the "no-" prefix if
4518 necessary).
4519 <P>
4520 To use inheritance, set the first item in a configuration list to the
4521 token "INHERIT", without the quotes.
4522 If the first item is "INHERIT",
4523 then instead of replacing the default value established so far, the rest of
4524 the list is appended to the default value established so far and that is
4525 the new value.
4526 <P>
4527 Here is an example which may make it clearer. Suppose we have:
4528 <P>
4529 <PRE>
4530 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4531 Personal config : smtp-server = INHERIT, mysmtp.home
4532 Exceptions config : smtp-server = <No Value Set>
4533 Command line : smtp-server = <No Value Set>
4534 Fixed config : smtp-server = <No Value Set>
4535 </PRE>
4536 <P>
4538 This would result in an effective smtp-server option of
4539 <P>
4540 <PRE>
4541 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4542 </PRE>
4543 <P>
4544 The "INHERIT" token can be used in any of the configuration files
4545 and the effect cascades.
4546 For example, if we change the above example to:
4547 <P>
4548 <PRE>
4549 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4550 Personal config : smtp-server = INHERIT, mysmtp.home
4551 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4552 Command line : smtp-server = <No Value Set>
4553 Fixed config : smtp-server = <No Value Set>
4554 </PRE>
4555 <P>
4557 This would result in:
4558 <P>
4559 <PRE>
4560 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4561 </PRE>
4562 <P>
4563 Unset variables are skipped over (the default value is carried forward) so
4564 that, for example:
4565 <P>
4566 <PRE>
4567 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4568 Personal config : smtp-server = <No Value Set>
4569 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4570 Command line : smtp-server = <No Value Set>
4571 Fixed config : smtp-server = <No Value Set>
4572 </PRE>
4573 <P>
4575 produces:
4576 <P>
4577 <PRE>
4578 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4579 </PRE>
4580 <P>
4582 If any later configuration location has a value set (for a particular list
4583 option) which does <EM>not</EM> begin with "INHERIT",
4584 then that value replaces whatever value has been defined up to that point.
4585 In other words, that cancels out any previous inheritance.
4586 <P>
4587 <PRE>
4588 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4589 Personal config : smtp-server = INHERIT, mysmtp.org
4590 Exceptions config : smtp-server = yoursmtp.org
4591 Command line : smtp-server = <No Value Set>
4592 Fixed config : smtp-server = <No Value Set>
4593 </PRE>
4594 <P>
4596 results in:
4597 <P>
4598 <PRE>
4599 smtp-server = yoursmtp.org
4600 </PRE>
4601 <P>
4603 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4604 "<!--#echo var="VAR_patterns-roles"-->", it is
4605 difficult to insert the value "INHERIT" into the list of values
4606 for the option using the normal Setup tools.
4607 In other words, the color setting screen (for example) does not
4608 provide a way to input the text "INHERIT" as the first
4609 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4610 The way to do this is to either edit the pinerc file directly and manually
4611 insert it, or turn
4612 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4613 feature and insert it using the Setup/Config screen.
4614 <P>
4615 <End of help on this topic>
4616 </BODY>
4617 </HTML>
4618 ============== h_special_xon_xoff =============
4619 <HTML>
4620 <HEAD>
4621 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4622 </HEAD>
4623 <BODY>
4624 <H1>XOFF/XON Handling within Alpine</H1>
4626 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4627 and XON) as normal characters, even though Alpine does not use them.
4628 However, the printer, modem, or communication software you are using may
4629 be configured for "software flow control," which means that
4630 XON/XOFF must be treated as special characters by the operating system.
4631 If you see messages such as "^S not defined for this screen",
4632 then your system is probably using software flow control. In this case
4633 you will need to set the
4634 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4635 feature.
4636 <P>
4637 If you <EM>do</EM> set this
4638 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4639 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4640 and see if that puts things right. Printing via the
4641 "attached-to-ansi" or
4642 "attached-to-wyse"
4643 option will automatically enable software
4644 flow-control handling for the duration of the printing.
4645 <P>
4646 <End of help on this topic>
4647 </BODY>
4648 </HTML>
4649 ============= h_special_help_nav =============
4650 <HTML>
4651 <HEAD>
4652 <TITLE>Help Text Navigation Explained</TITLE>
4653 </HEAD>
4654 <BODY>
4655 <H1>Help Text Navigation Explained</H1>
4657 Alpine contains extensive context-sensitive help text. At any point,
4658 pressing the "?" key will bring up a page of help text
4659 explaining the options available to you. You can leave the help
4660 text screen and return to normal Alpine operation by pressing
4661 the
4662 <!--chtml if pinemode="function_key"-->
4663 F3 function
4664 <!--chtml else-->
4665 "E"
4666 <!--chtml endif-->
4667 key to Exit Help at any time.
4669 <P>
4670 Within the help screen you might find a word or phrase displayed in
4671 inverse text and others displayed in bold typeface. Such words and
4672 phrases are used to tell you Alpine has more information available on
4673 the topic they describe.
4674 The inverted text is the "selected" topic.
4675 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4676 displayed in bold type
4677 is "selected".
4678 Hit the Return key to display the information Alpine has available on that
4679 topic. While viewing such additional information, the
4680 <!--chtml if pinemode="function_key"-->
4681 F3 function
4682 <!--chtml else-->
4683 "P"
4684 <!--chtml endif-->
4685 key will return you to the previous help screen, and the
4686 <!--chtml if pinemode="function_key"-->
4687 F2 function
4688 <!--chtml else-->
4689 "E"
4690 <!--chtml endif-->
4691 key will Exit the Help system altogether.
4693 <P>
4694 The "N" command will tell you the internal name of the help text you are
4695 reading each time, so that you can send this name in the text of a message
4696 and create a direct link to that internal help using the x-pine-help URL
4697 scheme. For example, the direct link to this item is
4698 x-pine-help:h_special_help_nav. If you add this text to a message, then
4699 a person using Pine to read such message would have a direct link to this
4700 help text.
4702 <P>
4703 When you are finished reading this help text, you can press the
4704 <!--chtml if pinemode="function_key"-->
4705 F3 function
4706 <!--chtml else-->
4707 "P"
4708 <!--chtml endif-->
4709 key to return to the previously displayed help text.
4711 <P>
4712 <End of help on this topic>
4713 </BODY>
4714 </HTML>
4715 ============= h_special_list_commands =============
4716 <HTML>
4717 <HEAD>
4718 <TITLE>Email List Commands Explained</TITLE>
4719 </HEAD>
4720 <BODY>
4721 <H1>Email List Commands Explained</H1>
4723 Electonic mail lists provide a way for like-minded users to join in
4724 discussions on topics of interest. The email list itself is
4725 represented by a
4726 single address that participants send messages to when they have
4727 something of interest to share with other members of the list. The
4728 receiving computer then, either automatically or after review by the
4729 list's owner (or moderator), sends a copy of that message to each
4730 member of the list.
4732 <P>
4733 Usually, subscribing and unsubscribing is done by sending requests in
4734 an email message to a special address setup to handle managing list
4735 membership. Often this is the name of the list followed by
4736 <I>-request</I>. This address is almost <EM>never</EM> the same as
4737 the address used to send messages to the list.
4739 <P>
4740 Unfortunately, email list participation commands are more a matter
4741 of convention than standard, and thus may vary from list to list.
4742 Increasingly, list management software is adding information to
4743 the copy of the postings as they're copied to the list members that
4744 explains how to do the various list management functions.
4746 <P>
4747 Alpine will recognize this information and offer the management commands
4748 they represent in a simple display. One or more of the following
4749 operations will be made available:
4751 <DL>
4752 <DT>Help</DT>
4753 <DD>
4754 A method to get help on subscribing, unsubscribing,
4755 an explanation of what the list is about, or special instructions
4756 for participation. This may be in the form of a reply in response
4757 to an email message, or instructions on how to connect to a Web site.
4758 </DD>
4760 <DT>Unsubscribe</DT>
4761 <DD>
4762 A method to get your email addressed removed from the list of
4763 recipients of the email list.
4764 </DD>
4766 <DT>Subscribe</DT>
4767 <DD>
4768 A method to get your email address added to the list of recipients
4769 of the email list. It may be in the form of a message sent to
4770 a special address or you may be connected to a web site.
4771 <DD>
4772 </DD>
4774 <DT>Post</DT>
4775 <DD>
4776 A method used to post to the email list. However, it might also
4777 indicate that no posting is allowed directly to the list.
4778 </DD>
4780 <DT>Owner</DT>
4781 <DD>
4782 A method to contact the list owner for special questions you might
4783 have regarding the list.
4784 </DD>
4786 <DT>Archive</DT>
4787 <DD>
4788 A method to view an archive of previous messages posted to the list.
4789 This may be in the form of a mail folder on a remote computer, an
4790 IMAP mailbox or even a Web site.
4791 </DD>
4792 </DL>
4794 <P>
4795 <End of help on this topic>
4796 </BODY>
4797 </HTML>
4798 ============= h_quota_command =============
4799 <HTML>
4800 <HEAD>
4801 <TITLE>Quota Screen Explained</TITLE>
4802 </HEAD>
4803 <BODY>
4804 <H1>Quota Screen Explained</H1>
4806 <P> This screen summarizes the quota report for this mailbox in the
4807 IMAP server. For each resource that you have a quota, this reports summarizes
4808 its use and limit.
4810 <P> Your IMAP server administrator may have set a quota based either on
4811 the total size of your mailbox (STORAGE), or the number of messages in
4812 your mailbox (MESSAGES), or some other criteria. This will be reported
4813 to you indicating the type of quota, its total use and its limit.
4815 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
4816 1024 bytes. Each of the characters that you see in this help text is one
4817 byte, and this help text is about 1 kibibyte in size. Small messages sent
4818 by Alpine are normally less than 4 kibibytes in size (which includes
4819 headers and text). Other email programs may send messages with bigger
4820 sizes when they send messages, since they send plain text and an
4821 alternative part in HTML.
4823 <P> A convenient way to save space for the STORAGE type of quota is by
4824 deleting attachments. This is done on each individual message by pressing
4825 the "V" command while reading the message text, then moving the cursor
4826 to the position of the attachment that is to be deleted, then pressing
4827 "D" to delete such attachment, going back to reading the
4828 message with the "<" command and pressing "S" to
4829 save the message in the same folder you are reading from. The saved
4830 message will not have the attachment that was marked deleted. Now you
4831 can delete and expunge the message with the unwanted attachment.
4833 <P>
4834 <End of help on this topic>
4835 </BODY>
4836 </HTML>
4837 ============= h_mail_thread_index =============
4838 <HTML>
4839 <HEAD>
4840 <TITLE>THREAD INDEX COMMANDS</TITLE>
4841 </HEAD>
4842 <BODY>
4843 <H1>THREAD INDEX COMMANDS</H1>
4844 <!--chtml if pinemode="function_key"-->
4845 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4846 ------------------------------- -----------------------------<BR>
4847 F1 Show Help Text F1 Show Help Text<BR>
4848 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4849 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4850 F4 View current thread F4 Quit Alpine<BR>
4851 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4852 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4853 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
4854 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4855 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
4856 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4857 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
4858 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
4859 <BR>
4860 Available Commands -- Group 3<BR>
4861 -----------------------------<BR>
4862 F3 <A HREF="h_index_cmd_expunge">Expunge</A> F7 <A HREF="h_index_cmd_sort">Sort</A> F10 <A HREF="h_common_bounce">Bounce</A> (remail) msg<BR>
4863 F5 <A HREF="h_index_cmd_select">Select</A> F8 <A HREF="h_common_jump">Jump</A> to thread F11 <A HREF="h_common_flag">Flag</A> messages as important<BR>
4864 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
4865 <BR>
4866 Available Commands -- Group 4<BR>
4867 -----------------------------<BR>
4868 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
4869 F6 <A HREF="h_common_role">Compose using a role</A><BR>
4870 <BR>
4871 <!--chtml else-->
4872 Navigating the List of Threads Operations on the Current Thread<BR>
4873 ------------------------------- ---------------------------------<BR>
4874 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
4875 N Move to the next thread R <A HREF="h_common_reply">Reply</A> to thread F <A HREF="h_common_reply">Forward</A><BR>
4876 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
4877 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
4878 J <A HREF="h_common_jump">Jump</A> to a specific thread T <A HREF="h_common_take">Take Address</A> into Address Book<BR>
4879 W <A HREF="h_index_cmd_whereis">Whereis</A> -- search for a S <A HREF="h_common_save">Save</A> into an email folder<BR>
4880 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
4881 Tab <A HREF="h_common_nextnew">Next new</A> thread B <A HREF="h_common_bounce">Bounce</A> * <A HREF="h_common_flag">Flag</A><BR>
4882 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
4883 <BR>
4884 Miscellaneous Operations General Alpine Commands<BR>
4885 ------------------------ ---------------------<BR>
4886 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
4887 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
4888 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
4889 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
4890 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
4891 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
4892 : Select Messages in Current Thread<BR>
4893 <!--chtml endif-->
4894 <P>
4896 NOTE:
4897 <OL>
4898 <LI>For help on a particular command, highlight the bold text associated
4899 with it above and hit Return.
4900 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
4901 </OL>
4903 <H2>Description of the THREAD INDEX Screen</H2>
4905 The THREAD INDEX displays summary information from each
4906 thread (conversation) in the current folder.
4907 This is useful if you want to quickly
4908 scan new threads, or find a particular thread without having to go
4909 through the text of each message, or to quickly get rid of junk
4910 threads, etc.
4911 The current thread is always highlighted.
4912 Each line of the THREAD INDEX contains the following columns: <P>
4913 <DL>
4914 <DT>STATUS:</DT>
4915 <DD> The markings on the left side of the thread tell you about its
4916 status. You may see one or more of the following codes on any given
4917 thread:
4918 <UL>
4919 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
4920 <LI> "A" for Answered. All of the messages in this thread are marked answered.
4921 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
4922 <LI> "+" for direct-to-you. The "+" indicates that a message in the thread was sent directly to your account, your copy is not part of a cc: or a mailing list.
4923 <LI> "-" for cc-to-you. The "-" indicates that a
4924 message in the thread was sent to you as a cc:. This symbol will only show up if
4925 the feature
4926 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
4927 <LI> "X" for selected. You have selected at least one message in the thread by using the
4928 "select" command. (Some systems may optionally allow selected
4929 messages to be denoted by the index line being displayed in bold
4930 type instead.)
4931 <LI> "*" for Important. You have previously used the "Flag" command
4932 to mark at least one message in this thread as "important".
4933 </UL></DD><P>
4935 <DT>THREAD NUMBER:</DT>
4936 <DD>Threads in a folder are numbered, from one through the number
4937 of threads in the folder, to help you know where you are in the folder.
4938 </DD><P>
4940 <DT>DATE STARTED:</DT>
4941 <DD>The date the thread was started. This is actually from the Date header
4942 of the first message in the thread. It doesn't take different time zones
4943 into account.</DD><P>
4945 <DT>WHO STARTED THE THREAD:</DT>
4946 <DD>This is usually the name of the sender of the first message in the thread, taken from
4947 the From header of the message.
4948 If there is no personal name given in that
4949 address, then the email address is used instead.
4950 If the message is from you (or from one of your
4951 <A HREF="h_config_alt_addresses">alternate addresses</A>),
4952 then the recipient's name is shown here instead, with the characters
4953 "To: " inserted before the name.
4954 (The idea of this is that if you started the thread you would rather see who
4955 the mail was sent to instead of that the mail was from you.)
4956 In Newsgroups, if you are
4957 the sender and there are no email recipients, the newsgroup name will be
4958 listed after the "To: ".
4959 </DD><P>
4961 <DT>SIZE:</DT>
4962 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
4964 <DT>SUBJECT:</DT>
4965 <DD>As much of the thread's subject line as will fit on the screen.
4966 This is the subject of the first message in the thread.</DD>
4967 </DL>
4969 <P><UL>
4970 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
4971 </UL>
4972 <P>
4973 <End of help on this topic>
4974 </BODY>
4975 </HTML>
4976 ============= h_mail_index =============
4977 <HTML>
4978 <HEAD>
4979 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
4980 </HEAD>
4981 <BODY>
4982 <H1>MESSAGE INDEX COMMANDS</H1>
4983 <!--chtml if pinemode="function_key"-->
4984 Available Commands -- Group 1 Available Commands -- Group 2<BR>
4985 ------------------------------- -----------------------------<BR>
4986 F1 Show Help Text F1 Show Help Text<BR>
4987 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
4988 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
4989 F4 View current message F4 Quit Alpine<BR>
4990 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
4991 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
4992 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
4993 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
4994 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
4995 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
4996 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
4997 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
4998 <BR>
4999 Available Commands -- Group 3<BR>
5000 -----------------------------<BR>
5001 F3 <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> F7 <A HREF="h_index_cmd_sort">Sort</A> order of index F10 <A HREF="h_common_bounce">Bounce</A> (remail) msg<BR>
5002 F5 <A HREF="h_index_cmd_select">Select</A> F8 <A HREF="h_common_jump">Jump</A> to message F11 <A HREF="h_common_flag">Flag</A> message as important<BR>
5003 F6 <A HREF="h_index_cmd_apply">Apply</A> F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5004 <BR>
5005 Available Commands -- Group 4<BR>
5006 -----------------------------<BR>
5007 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
5008 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
5009 <BR>
5010 <!--chtml else-->
5011 Navigating the List of Messages Operations on the Current Message<BR>
5012 ------------------------------- ---------------------------------<BR>
5013 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
5014 N Move to the next message R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A><BR>
5015 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
5016 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
5017 J <A HREF="h_common_jump">Jump</A> to a specific message T <A HREF="h_common_take">Take Address</A> into Address Book<BR>
5018 W <A HREF="h_index_cmd_whereis">Whereis</A> -- search for a S <A HREF="h_common_save">Save</A> into an email folder<BR>
5019 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5020 Tab <A HREF="h_common_nextnew">Next new</A> message B <A HREF="h_common_bounce">Bounce</A> * <A HREF="h_common_flag">Flag</A><BR>
5021 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5022 Miscellaneous Operations<BR>
5023 ------------------------<BR>
5024 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
5025 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
5026 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
5027 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
5028 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5029 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
5030 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
5031 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
5032 <!--chtml endif-->
5033 <P>
5035 NOTE:
5036 <OL>
5037 <LI>For help on a particular command, highlight the bold text associated
5038 with it above and hit Return.
5039 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5040 </OL>
5042 <H2>Description of the MESSAGE INDEX Screen</H2>
5044 The MESSAGE INDEX displays summary information from each
5045 message in the current folder.
5046 This is useful if you want to quickly
5047 scan new messages, or find a particular message without having to go
5048 through the text of each message, or to quickly get rid of junk
5049 messages, etc.
5050 <P>
5051 The current message is always highlighted
5052 and many commands operate on the current message.
5053 For example, the Delete command will delete the current message.
5054 If the folder is sorted by either Threads or OrderedSubject, then, depending
5055 on some of your configuration settings, a single line in the index may
5056 refer to an entire thread or to a subthread.
5057 If that is the case, then the commands that normally operate on the current
5058 message will operate on the thread or subthread instead.
5059 For example, the Delete command will delete the whole collapsed thread
5060 instead of just a single message.
5061 <P>
5062 Each line of the MESSAGE INDEX contains the following columns (by default --
5063 you can change this with the
5064 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
5065 in the SETUP CONFIGURATION screen): <P>
5066 <DL>
5067 <DT>STATUS:</DT>
5068 <DD> The markings on the left side of the message tell you about its
5069 status. You may see one or more of the following codes on any given
5070 message:
5071 <UL>
5072 <LI> "D" for Deleted. You have marked this message for deletion but not
5073 yet eXpunged the folder.
5074 <LI> "N" for New. You have not looked at the text of the message yet.
5075 <LI> "A" for Answered. Any time you reply to a message it is considered
5076 to be answered.
5077 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
5078 forward a message.
5079 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
5080 directly to your account, your copy is not part of a cc: or a
5081 mailing list.
5082 <LI> "-" for cc-to-you. The "-" indicates that a
5083 message was sent to you as a cc:. This symbol will only show up if
5084 the feature
5085 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5086 <LI> "X" for selected. You have selected the message by using the
5087 "select" command. (Some systems may optionally allow selected
5088 messages to be denoted by the index line being displayed in bold
5089 type.)
5090 <LI> "*" for Important. You have previously used the "Flag" command
5091 to mark this message as "important".
5092 </UL></DD><P>
5094 <DT>MESSAGE NUMBER:</DT>
5095 <DD>Messages in a folder are numbered, from one through the number
5096 of messages in the folder, to help you know where you are in the folder.
5097 These numbers are always in increasing order, even if you sort the folder
5098 in a different way.</DD><P>
5100 <DT>DATE SENT:</DT>
5101 <DD>The date the message was sent. By default, messages are
5102 ordered by arrival time, not by date sent. Most of the time, arrival time
5103 and date sent (effectively departure time) are similar. Sometimes,
5104 however, the index will appear to be out of order because a message took a
5105 long time in delivery or because the sender is in a different time
5106 zone than you are. This date is just the date from the Date header
5107 field in the message.</DD><P>
5109 <DT>WHO SENT THE MESSAGE:</DT>
5110 <DD>This is usually the name of the sender of the message, taken from
5111 the From header of the message.
5112 If there is no personal name given in that
5113 address, then the email address is used instead.
5114 If the message is from you (or from one of your
5115 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5116 then the recipient's name is shown here instead, with the characters
5117 "To: " inserted before the name.
5118 (The idea of this is that if you sent the mail you would rather see who
5119 the mail was sent to instead of that the mail was from you.
5120 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
5121 above.
5122 In particular, use the FROM token or the FROMORTONOTNEWS token
5123 in place of the FROMORTO token.)
5124 In Newsgroups, if you are
5125 the sender and there are no email recipients, the newsgroup name will be
5126 listed after the "To: ". </DD><P>
5128 <DT>SIZE:</DT>
5129 <DD>The number in parentheses is the number of characters in the message.
5130 It may have a suffix of K, M, or G which means the number should be
5131 multiplied by one thousand, one million, or one billion to get the
5132 size of the message.</DD><P>
5134 <DT>SUBJECT:</DT>
5135 <DD>As much of the message's subject line as will fit on the screen.</DD>
5136 </DL>
5138 <P><UL>
5139 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5140 </UL>
5141 <P>
5142 <End of help on this topic>
5143 </BODY>
5144 </HTML>
5145 ============= h_mail_view ========================
5146 <HTML>
5147 <HEAD>
5148 <TITLE>MESSAGE TEXT SCREEN</TITLE>
5149 </HEAD>
5150 <BODY>
5151 <H1>MESSAGE TEXT SCREEN</H1>
5152 <!--chtml if pinemode="function_key"-->
5153 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5154 ------------------------------- ------------------------------<BR>
5155 F1 Show Help Text F1 Show Help Text<BR>
5156 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5157 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
5158 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
5159 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5160 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5161 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
5162 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
5163 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5164 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5165 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5166 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5167 <BR>
5168 Available Commands -- Group 3<BR>
5169 ------------------------------<BR>
5170 F1 Show Help Text<BR>
5171 F2 Toggle to see more commands<BR>
5172 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
5173 F4 Select current message<BR>
5174 F5 Previous selectable item<BR>
5175 F6 Next selectable item<BR>
5176 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
5177 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
5178 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
5179 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
5180 F11 <A HREF="h_common_flag">Flag</A> message<BR>
5181 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5182 Available Commands -- Group 4<BR>
5183 F5 <A HREF="h_common_role">Compose using a role</A><BR>
5184 <!--chtml else-->
5185 Operations on the Current Message<BR>
5186 ---------------------------------<BR>
5187 <BR>
5188 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
5189 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5190 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
5191 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
5192 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5193 U <A HREF="h_common_delete">Undelete</A> (remove deletion mark) ^F Select next <A HREF="h_view_cmd_hilite">hilited</A> item in message<BR>
5194 T <A HREF="h_common_take">Take Address</A> into Address Book ^B Select previous <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5195 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
5196 W <A HREF="h_view_cmd_whereis">Whereis</A>: search for text in msg | <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5197 <BR>
5198 Navigating the List of Messages Other Commands<BR>
5199 ------------------------------- ----------------------------<BR>
5200 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5201 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
5202 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
5203 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
5204 <BR>
5205 General Alpine Commands<BR>
5206 ---------------------<BR>
5207 O Show all other available commands<BR>
5208 ? Show Help text Q Quit Alpine<BR>
5209 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
5210 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
5211 # <A HREF="h_common_role">Compose using a role</A><BR>
5212 <!--chtml endif-->
5213 <P>
5215 NOTE:
5216 <OL>
5217 <LI>For help on a particular command, highlight the bold text associated
5218 with it above and hit Return.
5219 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5220 </OL>
5222 <H2>Description of the MESSAGE TEXT Screen</H2>
5224 The top line of the view message screen displays status
5225 information about the currently open collection and folder and about the
5226 current message. It shows the name of the collection in angle brackets
5227 and then the name of the folder. The line also displays the number
5228 of messages in the folder, the number of the current message and the
5229 percentage of the current message that has been displayed on the screen.
5230 If the message is marked for deletion "DEL" will appear in the upper
5231 right corner.
5232 If the message has been answered (but not deleted) "ANS" will show
5233 in the corner.
5234 <P>
5236 NOTE: to rapidly move to the end of a message, hit the
5237 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5238 (or Ctrl-W) key followed
5239 by Ctrl-V. Similarly,
5240 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5241 followed by Ctrl-Y will take you to the beginning of
5242 a message.
5244 <H2>Explanation of Alternate Character Sets</H2>
5246 Alpine attempts to stay out of the way so that it won't prevent you from
5247 viewing mail in any character set. It will simply send the message to
5248 your display device. If the device is capable of displaying the
5249 message as it was written it will do so. If not, the display may be
5250 partially or totally incorrect.
5251 If the message contains characters that are not representable in your
5252 <A HREF="h_config_char_set">"Display Character Set"</A>
5253 variable in your configuration, then a warning message will be printed
5254 to your screen at the beginning of the message display.
5255 It is probably best to use UNIX Alpine in a terminal emulator
5256 capable of displaying UTF-8 characters.
5257 See <A HREF="h_config_char_set">Display Character Set</A> for a little
5258 more information about character set settings.
5260 <P><UL>
5261 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5262 </UL>
5263 <P>
5264 <End of help on this topic>
5265 </BODY>
5266 </HTML>
5267 ======= h_index_cmd_select =======
5268 <HTML>
5269 <HEAD>
5270 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
5271 </HEAD>
5272 <BODY>
5273 <H1>Selecting: Select and WhereIs/Select</H1>
5275 Aggregate operations give you the ability to process a group of messages
5276 at once. Acting on multiple messages requires two steps: (1) selecting a
5277 set of messages and then; (2) applying a command to that set. The first
5278 part is handled by the select command. Select allows you to
5279 select messages based on their status (read, answered, etc.), contents,
5280 date, size, or keywords.
5281 You may also select based on one of your Rules or based on threads,
5282 and there are quick options to select a specific message or range of messages,
5283 to select the current message, or to select all messages.
5284 <P>
5286 We describe the various selection criteria briefly:
5287 <P>
5289 <DL>
5290 <DT>select All</DT>
5291 <DD> Marks all the messages in the folder as selected.
5292 </DD>
5294 <DT>select Cur</DT>
5295 <DD> Selects the currently highlighted message or currently highlighted
5296 set of messages if in a threaded view.
5297 </DD>
5299 <DT>select by Number</DT>
5300 <DD> Select by message number. This may be a comma-separated list instead or
5301 a single entry.
5302 Each element in the list may be either a single message number or a range
5303 of numbers with a dash between the lowest and highest member of the range.
5304 Some examples are 7 to select only message number 7; 2-5 to select messages
5305 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
5306 The word "end" may be used as a substitute for the highest numbered
5307 message in the folder.
5308 If in a separate thread index where the numbers refer to threads instead of
5309 to messages, then you will be selecting all of the messages in the
5310 referenced threads instead of selecting by message number.
5311 </DD>
5313 <DT>select by Date</DT>
5314 <DD> Select by either the date stored in the Date headers of each message,
5315 or by the date when the messages arrived.
5316 This does not adjust for different time zones, but just checks to see what
5317 day the message was sent on.
5318 You may type in a date. If you do, the date should be in the form
5319 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
5320 For example,
5321 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
5322 or
5323 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
5324 If the date you want is close to the current date, it is probably
5325 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
5326 is displayed, instead of typing in the date yourself.
5327 Or, the "^X Cur Msg" command may be used to fill in
5328 the date of the currently highlighted message.
5329 <P>
5330 There are six possible settings that are selected using the
5331 "^W Toggle When" command.
5332 Three of them select messages based on the Date headers.
5333 They are "SENT SINCE", "SENT BEFORE",
5334 and "SENT ON".
5335 SINCE is all messages with the selected date or later.
5336 BEFORE is all messages earlier than the selected date (not including the day
5337 itself).
5338 ON is all messages sent on the selected date.
5339 The other three select messages in the same way but they use the arrival
5340 times of the messages instead of the Date headers included in the messages.
5341 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
5342 and "ARRIVED ON".
5343 When you save a message from one folder to another the arrival time is
5344 preserved.
5345 </DD>
5347 <DT>select by Text</DT>
5348 <DD> Selects messages based on the message contents.
5349 This allows you to select a set of messages based on whether or not the
5350 message headers or message body contain specified text.
5351 You may look for text in the Subject, the From header,
5352 the To header, or the Cc header.
5353 You may also choose Recipient, which searches for the text in
5354 either the To or the Cc header;
5355 or Participant, which means To or Cc or From.
5356 Besides those specific header searches, you may also search the entire
5357 header and text of the message with "All Text", or just the
5358 body of the message.
5359 <P>
5360 To search for the absence of text, first type the "! Not" command
5361 before typing the specific type of text search.
5362 For example, you could type "!" followed by "S" to
5363 search for all messages that do not contain a particular word in their
5364 Subjects.
5365 <P>
5366 If you choose a Subject search, you may use the subject from the current
5367 message by typing the "^X Cur Subject" command.
5368 You may then edit it further if you wish.
5369 For example, you might select the subject of a reply and edit the
5370 "Re: " off of the front of it in order to search for
5371 the original message being replied to.
5372 All of the other header searches allow you to use addresses from the
5373 headers of the current message if you want to.
5374 You may use the "^T Cur To", "^R Cur From", or
5375 "^W Cur Cc".
5376 In each case, if there is more than one address, only the first is offered.
5377 </DD>
5379 <DT>select by Status</DT>
5380 <DD> Selects messages based on their status.
5381 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5382 messages.
5383 Or, if you first type the "! Not" command, you get not New,
5384 or not Important, and so on.
5385 If you select Deleted messages, you will get all messages with their
5386 Deleted flag set.
5387 Likewise for Important messages, all messages that you have flagged as
5388 being Important with the
5389 <A HREF="h_common_flag">Flag</A> command.
5390 The "New" and "Answered" choices are a little bit odd
5391 because they try to match what you see on the screen by default.
5392 "New" is a shorthand for messages that are Unseen, Undeleted,
5393 and Unanswered.
5394 If you have looked at the message, or deleted it, or answered it; then it
5395 is not considered "New ".
5396 "! New" is the opposite of "New".
5397 <P>
5398 "Answered" is another one that is a little different.
5399 It means that the message has been Answered <EM>and</EM> is not deleted.
5400 And to make it even more confusing, "! Answered" is not
5401 the opposite of "Answered"!
5402 Instead, "! Answered" stands for messages that are
5403 both Unanswered <EM>and</EM> not deleted.
5404 <P>
5405 The other two types were added later because the special nature of the
5406 New flag was not what was wanted by all users.
5407 New does match what you see in the index by default, but if you use
5408 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5409 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5410 be exactly what you want.
5411 "Unseen" simply selects all unseen messages, whether or not
5412 they are deleted or answered, and
5413 "Recent" selects all of the messages that have been added to
5414 the folder since you started this Alpine session.
5415 (That's not technically quite true. If there are multiple mail clients
5416 reading an IMAP mailbox, each message will be marked as Recent in only
5417 one of the client's sessions.)
5418 </DD>
5420 <DT>select by siZe</DT>
5421 <DD> Selects messages based on their size being smaller than or larger
5422 than the size you specify.
5423 The size is the number of bytes.
5424 You may use the suffix "K" or "k" to mean 1,000 times
5425 the number.
5426 For example, 7K is the same as 7000.
5427 The suffix "M" or "m" means 1,000,000 times the number,
5428 and the suffix "G" or "g" means 1,000,000,000 times.
5429 Use the "^W" command to toggle back and forth between Smaller
5430 and Larger.
5431 </DD>
5433 <DT>select by Keyword</DT>
5434 <DD> Selects messages that either have or do not have
5435 (using the "! Not" command)
5436 a particular <A HREF="h_config_keywords">Keyword</A> set.
5437 One way to select a keyword is to use the "^T To List"
5438 command to select one from your list of keywords.
5439 The
5440 <A HREF="h_config_flag_screen_kw_shortcut"><!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></A> option allows selecting by Keyword initials if set.
5441 </DD>
5443 <DT>select by Rule</DT>
5444 <DD> Selects messages that either match or don't match
5445 (using the "! Not" command)
5446 one of the Rules you have defined.
5447 The most likely method of filling in the Rule is to use the
5448 "^T To List"
5449 command to select one of your Rules.
5450 All of the Rules you have defined will be in the list, including
5451 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5452 They may not all make sense for this purpose, but they are all there for
5453 flexibility.
5454 You might find it useful to define some rules solely for the purpose
5455 of being used by the Select command.
5456 There is a special category for such Rules. They are called Search Rules.
5457 <P>
5458 Unfortunately, Alpine does not allow all possible Rules to be defined.
5459 For example, there is no logical OR operation.
5460 OR is accomplished in the Filter Rules or the other types of Rules by
5461 simply defining two rules, one that matches the first part of the OR
5462 and another that matches the second part.
5463 But you can't do that here, since you only have a single Rule to work with.
5464 Likewise, the order of Rules is usually important.
5465 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5466 a message, then that stops the search for a further match.
5467 This means that you may be confused if you try to use Select by Rule to
5468 check your Filter rules because the order is important when filtering but
5469 is not considered here.
5470 </DD>
5472 <DT>select by tHread</DT>
5473 <DD> Selects all of the messages in the current thread.
5474 </DD>
5475 </DL>
5477 After you have an initial selection, the next and subsequent selection
5478 commands modify the selection.
5479 The select command changes. It first gives
5480 you selection "alteration" options: "unselect All",
5481 "unselect Current",
5482 "Broaden selection" (implements a logical OR), and
5483 "Narrow selection" (implements a logical AND).
5484 After you choose either Broaden or Narrow, you then choose one of the
5485 selection criteria listed above (by Text or Number or ...).
5486 You may use select as many times as you wish to get the selected set right.
5487 <P>
5489 The WhereIs command has a feature (Ctrl-X) to
5490 select all the messages that match the WhereIs search. WhereIs searches
5491 through just the text that appears on the MESSAGE INDEX screen.
5492 This method is often slower than using the select command itself, unless the
5493 line you are looking for is not too far away in the index.
5494 <P>
5496 The availability of the aggregate operations commands is determined by the
5497 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5498 Feature-List option in your Alpine
5499 configuration, which defaults to set.
5500 The features
5501 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5502 and
5503 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5504 affect the behavior of the Select command.
5506 <P>
5507 <End of help on this topic>
5508 </BODY>
5509 </HTML>
5510 ======= h_select_rule =======
5511 <HTML>
5512 <HEAD>
5513 <TITLE>Select: Rule</TITLE>
5514 </HEAD>
5515 <BODY>
5516 <H1>Select: Rule</H1>
5518 You are selecting messages that either match or don't match
5519 one of the Rules you have defined.
5520 You may either type the nickname of the Rule at the prompt, or use the
5521 "^T To List"
5522 command to select one of your Rules.
5523 All of the Rules you have defined will be in the list, including
5524 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5525 They may not all make sense for this purpose, but they are all there for
5526 flexibility.
5527 Rules may be added by using the Setup/Rules screen off of the main Alpine
5528 menu.
5529 <P>
5530 Unfortunately, Alpine does not allow all possible Rules to be defined.
5531 For example, there is no logical OR operation.
5532 OR is accomplished in the Filter Rules or the other types of Rules by
5533 simply defining two rules, one that matches the first part of the OR
5534 and another that matches the second part.
5535 But you can't do that here, since you only have a single Rule to work with.
5536 Likewise, the order of Rules is usually important.
5537 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5538 a message, then that stops the search for a further match.
5539 This means that you may be confused if you try to use Select by Rule to
5540 check your Filter rules because the order is important when filtering but
5541 is not considered here.
5543 <P>
5544 <End of help on this topic>
5545 </BODY>
5546 </HTML>
5547 ======= h_select_text =======
5548 <HTML>
5549 <HEAD>
5550 <TITLE>Select: Text</TITLE>
5551 </HEAD>
5552 <BODY>
5553 <H1>Select: Text</H1>
5555 You are selecting messages based on the contents of the message.
5556 This allows you to select a set of messages based on whether or not the
5557 message headers or message body contain specified text.
5558 You may look for text in the Subject, the From header,
5559 the To header, or the Cc header.
5560 You may also choose Recipient, which searches for the text in
5561 either the To or the Cc header;
5562 or Participant, which means either the To header, or the Cc header,
5563 or the From header.
5564 Besides those specific header searches, you may also search the entire
5565 header and text of the message with "All Text", or just the
5566 body of the message with "Body".
5567 <P>
5568 To search for the absence of text, first type the "! Not" command
5569 before typing the specific type of text search.
5570 For example, you could type "!" followed by "S" to
5571 search for all messages that do not contain a particular word in their
5572 Subjects.
5573 <P>
5574 If you choose a Subject search, you may use the subject from the current
5575 message by typing the "^X Cur Subject" command.
5576 You may then edit it further if you wish.
5577 For example, you might select the subject of a reply and edit the
5578 "Re: " off of the front of it in order to search for
5579 the original message being replied to.
5580 All of the other header searches allow you to use addresses from the
5581 headers of the current message if you want to.
5582 You may use the "^T Cur To", "^R Cur From", or
5583 "^W Cur Cc".
5584 In each case, if there is more than one address, only the first is offered.
5586 <P>
5587 <End of help on this topic>
5588 </BODY>
5589 </HTML>
5590 ======= h_select_status =======
5591 <HTML>
5592 <HEAD>
5593 <TITLE>Select: Status</TITLE>
5594 </HEAD>
5595 <BODY>
5596 <H1>Select: Status</H1>
5598 You are selecting messages based on the status of the message.
5599 For example, whether or not the message has been marked Deleted or Important,
5600 or whether or not it has been Answered or is New.
5601 If you first type the "! Not" command, you will get the
5602 opposite: not Deleted, not Important, and so on.
5603 <P>
5604 If you select Deleted messages, you will get all messages with their
5605 Deleted flag set.
5606 Likewise for Important messages, all messages that you have flagged as
5607 being Important with the
5608 <A HREF="h_common_flag">Flag</A> command.
5609 The "New" and "Answered" choices are a little bit odd
5610 because they try to match what you see on the screen by default.
5611 "New" is a shorthand for messages that are Unseen, Undeleted,
5612 and Unanswered.
5613 If you have looked at the message, or deleted it, or answered it; then it
5614 is not considered "New ".
5615 "! New" is the opposite of "New".
5616 <P>
5617 "Answered" is another one that is a little different.
5618 It means that the message has been Answered <EM>and</EM> is not deleted.
5619 And to make it even more confusing, "! Answered" is not
5620 the opposite of "Answered"!
5621 Instead, "! Answered" stands for messages that are
5622 both Unanswered <EM>and</EM> not deleted.
5623 <P>
5624 (The New and Answered options may seem counter-intuitive.
5625 The reason it is done this way is
5626 because, by default, a Deleted message will show up with the "D"
5627 symbol in the MAIL INDEX screen even if it is New or Answered.
5628 The Delete symbol overrides the New and Answered symbols, because you
5629 usually don't care about the message anymore once you've deleted it.
5630 Similarly, you usually only care about whether a message is Answered or
5631 not if it is not Deleted.
5632 Once it is Deleted you've put it out of your mind.)
5633 <P>
5634 The other two options were added later because the special nature of the
5635 New flag was not what was wanted by all users.
5636 New does match what you see in the index by default, but if you use
5637 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5638 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5639 be exactly what you expect.
5640 "Unseen" simply selects all unseen messages, whether or not
5641 they are deleted or answered, and
5642 "Recent" selects all of the messages that have been added to
5643 the folder since you started this Alpine session.
5644 (That's not technically quite true. If there are multiple mail clients
5645 reading an IMAP mailbox, each message will be marked as Recent in only
5646 one of the client's sessions.
5647 That behavior can be convenienent for some purposes, like filtering, but
5648 it isn't usually what you expect when selecting.)
5650 <P>
5651 <End of help on this topic>
5652 </BODY>
5653 </HTML>
5654 ======= h_index_cmd_apply =======
5655 <HTML>
5656 <HEAD>
5657 <TITLE>Apply Command</TITLE>
5658 </HEAD>
5659 <BODY>
5660 <H1>Apply Command</H1>
5662 Apply
5663 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5664 is the second step of most aggregate operations. Apply
5665 becomes active any time there is a defined set of selected messages. The
5666 following commands can be applied to a selected message set: delete,
5667 undelete, reply, forward,
5668 <!--chtml if pinemode="os_windows"-->
5669 <!--chtml else-->
5670 pipe,
5671 <!--chtml endif-->
5672 print, take address, save, export, bounce, and flag.
5673 <P>
5675 The behavior of some of these commands in an aggregate sense is not easy to
5676 explain. Try them out to see what they do.
5677 The feature
5678 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5679 affects the behavior of the Apply command, as does the feature
5680 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5682 <P>
5683 <End of help on this topic>
5684 </BODY>
5685 </HTML>
5686 ======= h_index_cmd_zoom =======
5687 <HTML>
5688 <HEAD>
5689 <TITLE>ZoomMode Command</TITLE>
5690 </HEAD>
5691 <BODY>
5692 <H1>ZoomMode Command</H1>
5694 Another action you might want to take on a set of selected messages is to
5695 zoom in on them. Like apply, zoom only becomes active when messages have
5696 been selected.
5697 ZoomMode
5698 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5699 is a toggle command that allows you to
5700 zoom-in (and only see the selected messages) and zoom-out (to see all
5701 messages in the folder). Neither apply nor zoom removes the markings that
5702 define the selected set; you need to use a select command in order
5703 to do that.
5705 <P>
5706 <End of help on this topic>
5707 </BODY>
5708 </HTML>
5709 ======= h_index_collapse_expand =======
5710 <HTML>
5711 <HEAD>
5712 <TITLE>Collapse/Expand Command</TITLE>
5713 </HEAD>
5714 <BODY>
5715 <H1>Collapse/Expand Command</H1>
5717 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5718 the folder is sorted by either Threads or OrderedSubject, and the
5719 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5720 is set to something other than "none".
5721 By default, this command collapses or expands the subthread that starts at
5722 the currently highlighted message, if any.
5723 If the subthread is already collapsed, then this command expands it.
5724 If the subthread is expanded, then this command collapses it.
5725 If there are no more messages below the current message in the
5726 thread tree (that is, there are no replies to the current message) then
5727 this command does nothing.
5729 <P>
5730 The behavior of this command is affected by the option
5731 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
5732 Normally, this command Collapses or Expands the subthread that
5733 starts at the currently highlighted message.
5734 If the above option is set, then this command Collapses or Expands the
5735 entire current thread instead of just the subthread.
5736 The current thread is simply the top-level thread that contains the
5737 current message.
5739 <P>
5740 <End of help on this topic>
5741 </BODY>
5742 </HTML>
5743 ======= h_index_cmd_sort =======
5744 <HTML>
5745 <HEAD>
5746 <TITLE>Sort Command</TITLE>
5747 </HEAD>
5748 <BODY>
5749 <H1>Sort Command</H1>
5751 In Alpine's generic configuration, messages are presented in the order in
5752 which they arrive. This default can be changed in the SETUP CONFIGURATION
5753 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
5754 You can also re-sort the folder on demand with the sort
5755 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
5756 command.
5757 Your sorting options are:
5758 <P>
5759 <UL>
5760 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
5761 <LI> <A HREF="h_index_sort_date">D</A>ate
5762 <LI> <A HREF="h_index_sort_subj">S</A>ubject
5763 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
5764 <LI> t<A HREF="h_index_sort_thread">H</A>read
5765 <LI> <A HREF="h_index_sort_from">F</A>rom
5766 <LI> si<A HREF="h_index_sort_size">Z</A>e
5767 <LI> scor<A HREF="h_index_sort_score">E</A>,
5768 <LI> <A HREF="h_index_sort_to">T</A>o
5769 <LI> <A HREF="h_index_sort_cc">C</A>c
5770 </UL>
5772 <P>
5773 The Reverse option will toggle the order the index is currently
5774 sorted by, but will not change the relative sort order.
5776 <P>
5777 Sorting a folder does not actually rearrange the way the folder is saved,
5778 it just re-arranges how the messages are presented to you. This means
5779 that Alpine has to do the work of sorting every time you change sort order.
5780 Sometimes, especially with PC-Alpine or with large folders, this could take
5781 a while.
5783 <P>
5784 <End of help on this topic>
5785 </BODY>
5786 </HTML>
5787 ======= h_index_sort_default =======
5788 <HTML>
5789 <HEAD>
5790 <TITLE>SORT OPTION: Default</TITLE>
5791 </HEAD>
5792 <BODY>
5793 <H1>SORT OPTION: Default</H1>
5795 The <EM>Default</EM> sort option just means to use the default sort order
5796 set in the
5797 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
5798 option in Setup/Config.
5800 <P>
5801 <End of help on this topic>
5802 </BODY>
5803 </HTML>
5804 ======= h_index_sort_arrival =======
5805 <HTML>
5806 <HEAD>
5807 <TITLE>SORT OPTION: Arrival</TITLE>
5808 </HEAD>
5809 <BODY>
5810 <H1>SORT OPTION: Arrival</H1>
5812 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
5813 in the order that they exist in the folder. This is usually the same as the
5814 order in which they arrived. This option is comparable to not sorting
5815 the messages at all.
5817 <P>
5818 <End of help on this topic>
5819 </BODY>
5820 </HTML>
5821 ======= h_index_sort_date =======
5822 <HTML>
5823 <HEAD>
5824 <TITLE>SORT OPTION: Date</TITLE>
5825 </HEAD>
5826 <BODY>
5827 <H1>SORT OPTION: Date</H1>
5829 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
5830 according to the date and time they were
5831 sent.
5833 <P>
5834 On a folder like INBOX, sorting by "Date" should be almost
5835 identical to sorting by "Arrival".
5837 <P>
5838 <End of help on this topic>
5839 </BODY>
5840 </HTML>
5841 ======= h_index_sort_subj =======
5842 <HTML>
5843 <HEAD>
5844 <TITLE>SORT OPTION: Subject</TITLE>
5845 </HEAD>
5846 <BODY>
5847 <H1>SORT OPTION: Subject</H1>
5849 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
5850 by subject.
5852 <P>
5853 Messages with the same subject are
5854 first grouped together, and then the groups of like-subject messages
5855 are arranged alphabetically.
5857 <P>
5858 Alpine ignores leading "Re:" and
5859 "re:" and trailing "(fwd)" when determining the
5860 likeness and alphabetical order of subject lines.
5862 <P>
5863 <End of help on this topic>
5864 </BODY>
5865 </HTML>
5866 ======= h_index_sort_ordsubj =======
5867 <HTML>
5868 <HEAD>
5869 <TITLE>SORT OPTION: OrderedSubject</TITLE>
5870 </HEAD>
5871 <BODY>
5872 <H1>SORT OPTION: OrderedSubject</H1>
5874 The <EM>OrderedSubject</EM> sort option arranges messages in the
5875 MESSAGE INDEX by grouping all messages with the same subject
5876 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
5878 <P>
5879 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
5880 messages by the date of the oldest message in the group.
5882 <P>
5883 This sort method provides for pseudo threading of conversations within
5884 a folder.
5885 You may want to try sorting by Thread instead.
5887 <P>
5888 <End of help on this topic>
5889 </BODY>
5890 </HTML>
5891 ======= h_index_sort_thread =======
5892 <HTML>
5893 <HEAD>
5894 <TITLE>SORT OPTION: Thread</TITLE>
5895 </HEAD>
5896 <BODY>
5897 <H1>SORT OPTION: Thread</H1>
5899 The <EM>Thread</EM> sort option arranges messages in the
5900 MESSAGE INDEX by grouping all messages that indicate
5901 they are part of a conversation (discussion thread) taking
5902 place within a mailbox or newsgroup. This indication is
5903 based on information in the message's header -- specifically
5904 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
5906 <P>
5907 <End of help on this topic>
5908 </BODY>
5909 </HTML>
5910 ======= h_index_sort_from =======
5911 <HTML>
5912 <HEAD>
5913 <TITLE>SORT OPTION: From</TITLE>
5914 </HEAD>
5915 <BODY>
5916 <H1>SORT OPTION: From</H1>
5918 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
5919 by the name of the author of the message.
5921 <P>
5922 Messages with the same author are grouped together. Groups of
5923 messages are then put into alphabetical order according to message
5924 author.
5926 <P>
5927 <End of help on this topic>
5928 </BODY>
5929 </HTML>
5930 ======= h_index_sort_size =======
5931 <HTML>
5932 <HEAD>
5933 <TITLE>SORT OPTION: Size</TITLE>
5934 </HEAD>
5935 <BODY>
5936 <H1>SORT OPTION: Size</H1>
5938 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
5939 by their relative sizes.
5941 <P>
5942 <End of help on this topic>
5943 </BODY>
5944 </HTML>
5945 ======= h_index_sort_score =======
5946 <HTML>
5947 <HEAD>
5948 <TITLE>SORT OPTION: Score</TITLE>
5949 </HEAD>
5950 <BODY>
5951 <H1>SORT OPTION: Score</H1>
5953 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
5954 by their scores.
5956 <P>
5957 Messages with the same score are sorted in arrival order.
5958 Scores are something you create using the
5959 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
5961 <P>
5962 <End of help on this topic>
5963 </BODY>
5964 </HTML>
5965 ======= h_index_sort_to =======
5966 <HTML>
5967 <HEAD>
5968 <TITLE>SORT OPTION: To</TITLE>
5969 </HEAD>
5970 <BODY>
5971 <H1>SORT OPTION: To</H1>
5973 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
5974 by the names of the recipients of the message.
5976 <P>
5977 Messages with the same recipients are grouped together. Groups of
5978 messages are then put into alphabetical order according to message
5979 recipients.
5981 <P>
5982 <End of help on this topic>
5983 </BODY>
5984 </HTML>
5985 ======= h_index_sort_cc =======
5986 <HTML>
5987 <HEAD>
5988 <TITLE>SORT OPTION: Cc</TITLE>
5989 </HEAD>
5990 <BODY>
5991 <H1>SORT OPTION: Cc</H1>
5993 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
5994 the names of the carbon copy addresses of the message.
5996 <P>
5997 <End of help on this topic>
5998 </BODY>
5999 </HTML>
6000 ======= h_index_cmd_whereis =======
6001 <HTML>
6002 <HEAD>
6003 <TITLE>WhereIs Command</TITLE>
6004 </HEAD>
6005 <BODY>
6006 <H1>WhereIs Command</H1>
6008 The WhereIs
6009 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6010 command lets you search the MESSAGE INDEX for a word.
6011 It scans through whatever you see, usually the name of the author
6012 and the Subject line.
6013 WhereIs has special subcommands to let you find the beginning of the
6014 index (Ctrl-Y -- first message)
6015 or the end of the index (Ctrl-V -- last message).
6016 <P>
6017 Note that WhereIs only searches through the visible text on the screen.
6018 For example, if only part of the Subject of a message is shown because it
6019 is long, then only the visible portion of the Subject is searched.
6020 Also note that WhereIs does not "see" the
6021 "X" in column one of Index entries for selected messages
6022 so it can't be used to search for
6023 selected messages (use "Zoom" instead).
6024 <P>
6025 If the feature
6026 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
6027 is turned on,
6028 WhereIs can also be used as a quick way to select messages that match the
6029 string being searched for.
6030 Instead of typing carriage return to search for the next match, type
6031 Ctrl-X to select all matches.
6032 Once again, this only selects matches that are (or would be if the right
6033 index line was on the screen) visible.
6034 Truncated From lines or Subjects will cause matches to be missed.
6035 Although WhereIs is sometimes convenient for quick matching, the Select
6036 command is usually more powerful and usually faster.
6038 <P>
6039 <End of help on this topic>
6040 </BODY>
6041 </HTML>
6042 ======= h_view_cmd_whereis =======
6043 <HTML>
6044 <HEAD>
6045 <TITLE>WhereIs Command</TITLE>
6046 </HEAD>
6047 <BODY>
6048 <H1>WhereIs Command</H1>
6050 The WhereIs
6051 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6052 command does a "find in current message" operation. You
6053 type in text and Alpine will try to find it in the message you are
6054 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
6055 or end (Ctrl-V) of the message.
6056 That is, to rapidly move to the end of a message, hit the
6057 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6058 (or Ctrl-W) key followed
6059 by Ctrl-V. Similarly,
6060 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6061 followed by Ctrl-Y will take you to the beginning of a message.
6063 <P>
6064 <End of help on this topic>
6065 </BODY>
6066 </HTML>
6067 ======= h_view_cmd_hilite =======
6068 <HTML>
6069 <HEAD>
6070 <TITLE>View Hilite and Next item/Previous item</TITLE>
6071 </HEAD>
6072 <BODY>
6073 <H1>View Hilite and Next item/Previous item</H1>
6075 Sometimes messages may be in the form of formatted HTML text
6076 or they may contain URLs or Web server hostnames.
6077 When any of the features
6078 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
6079 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
6080 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
6081 or
6082 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
6083 are enabled, Alpine will represent such selectable items in the text
6084 in bold typeface. One of the selectable items will be displayed in
6085 inverse video (highlighted). This is the "currently selected" item.
6086 Press the Return key to view the currently selected item.
6087 <P>
6089 The Up and Down Arrows keys can be used to change the selected item
6090 (also see the feature
6091 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
6092 If there are no selectable items in the direction of the arrow you
6093 pressed, Alpine will scroll the display in that direction until one
6094 becomes visible. To "jump" forwards/backwards among selectable
6095 items in the message text, use the Previous and Next item commands,
6096 <!--chtml if pinemode="function_key"-->F5 and F6
6097 <!--chtml else-->^B and ^F<!--chtml endif-->.
6099 <P>
6100 <End of help on this topic>
6101 </BODY>
6102 </HTML>
6103 ======= h_view_cmd_viewattch =======
6104 <HTML>
6105 <HEAD>
6106 <TITLE>ViewAttch Command</TITLE>
6107 </HEAD>
6108 <BODY>
6109 <H1>ViewAttch Command</H1>
6112 The View/Save Attachment
6113 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
6114 command allows you to handle MIME attachments to a message you have
6115 received. Alpine shows you a list of the message attachments -- you just
6116 choose the attachment you want. You may either view or save the
6117 selected attachment.
6119 <P>
6120 Because many attachments require external programs for display, there
6121 is some system configuration that has to happen before you can
6122 actually display attachments. Hopefully much of that will have been
6123 done already by your system administrator. MIME configuration is
6124 handled with the "mailcap" configuration file. (See the section
6125 on configuration in the
6126 <A HREF="h_news">release notes</A> for more information.)
6128 <P>
6129 <End of help on this topic>
6130 </BODY>
6131 </HTML>
6132 ======= h_index_cmd_expunge =======
6133 <HTML>
6134 <HEAD>
6135 <TITLE>Expunge/Exclude Command</TITLE>
6136 </HEAD>
6137 <BODY>
6138 <H1>Expunge/Exclude Command</H1>
6140 Expunge/Exclude
6141 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
6142 is the command Alpine uses to actually remove all messages
6143 marked for deletion. With regular email files, expunge literally deletes
6144 the text from the current folder. With newsgroups or shared mailboxes,
6145 you don't have permission to actually remove the message, so it is an
6146 exclude -- Alpine removes the message from your view of the folder even
6147 though it is not technically gone.
6149 <P> A selective expunge command is available in IMAP folders that support
6150 the UID EXPUNGE extension in <A
6151 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
6152 other folders (local folders in all formats, POP3 inbox, and newsgroups)
6153 as a subcommand of the apply command. If some selected messages are marked
6154 deleted, then the apply command will offer the eXpunge command, which when
6155 executed will only expunge those messages that are selected and deleted.
6157 <P>
6158 Observe that the expunge command (when not used from the apply command)
6159 will expunge/exclude all deleted messages from the folder, and so all
6160 messages marked deleted will be expunged, regardless of if they are
6161 selected or not. In other words, there is no protection against
6162 potentially expunging more messages than only those that have been
6163 selected and deleted.
6164 <P>
6166 The configuration features
6167 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
6168 and
6169 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
6170 affect the behavior of the Expunge command.
6172 <P>
6173 <End of help on this topic>
6174 </BODY>
6175 </HTML>
6176 ======= h_common_compose =======
6177 <HTML>
6178 <HEAD>
6179 <TITLE>Compose Command</TITLE>
6180 </HEAD>
6181 <BODY>
6182 <H1>Compose Command</H1>
6184 The Compose command takes you into the Alpine message composer where you
6185 can start a new message for sending. This is where you type in the
6186 message's text and specify its recipient list (the "To:"
6187 address), where copies should be directed (e.g., "Fcc",
6188 "Cc:" or "Bcc:"), and which files, if any, should
6189 be attached to the message.
6191 <P>
6192 When you type this command, Alpine will also automatically check for any
6193 interrupted (i.e., a message that was being composed when your modem
6194 or network connection was broken) or previously postponed messages and
6195 offer you a chance to continue working on those.
6197 <P>
6198 <UL>
6199 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6200 </UL><P>
6201 <End of help on this topic>
6202 </BODY>
6203 </HTML>
6204 ======= h_common_index =======
6205 <HTML>
6206 <HEAD>
6207 <TITLE>Message Index Command</TITLE>
6208 </HEAD>
6209 <BODY>
6210 <H1>Message Index Command</H1>
6212 The Index command takes you to the MESSAGE INDEX screen that displays a
6213 summary caption for each message in the currently-open folder. One
6214 message will be highlighted; this is the "Current" message.
6215 The message commands available from this screen (e.g. View, Reply,
6216 Forward, Delete, Print, Save, etc) apply to the current message.
6218 <P>
6219 <End of help on this topic>
6220 </BODY>
6221 </HTML>
6222 ======= h_common_folders =======
6223 <HTML>
6224 <HEAD>
6225 <TITLE>Folder List Command</TITLE>
6226 </HEAD>
6227 <BODY>
6228 <H1>Folder List Command</H1>
6230 This Folder List command takes you to the FOLDER LIST screen that displays
6231 the names of all your message folders and allows you to view, rename,
6232 delete, and add folders. You can open (view) a different folder than the
6233 one currently open by highlighting the desired one (using the arrow keys
6234 or their control-key equivalents) and pressing RETURN.
6236 <P>
6237 If you have multiple folder collections defined (see the Help text for
6238 the FOLDER LIST screen to learn more about Collections), you may need
6239 to press Return to expand the collection and display all of the
6240 folders in it.
6242 <P>
6243 <End of help on this topic>
6244 </BODY>
6245 </HTML>
6246 ======= h_main_addrbook =======
6247 <HTML>
6248 <HEAD>
6249 <TITLE>Address Book Command</TITLE>
6250 </HEAD>
6251 <BODY>
6252 <H1>Address Book Command</H1>
6254 This command, available only from the MAIN MENU, takes you
6255 to the ADDRESS BOOK management screen. From here, your personal address
6256 book(s) may be updated.
6258 <P>
6259 <End of help on this topic>
6260 </BODY>
6261 </HTML>
6262 ======= h_main_setup =======
6263 <HTML>
6264 <HEAD>
6265 <TITLE>Setup Command</TITLE>
6266 </HEAD>
6267 <BODY>
6268 <H1>Setup Command</H1>
6270 The Setup command, available only from the MAIN MENU, prompts you for
6271 one of several configuration screens, including the SETUP CONFIGURATION
6272 screen, by which you may activate optional Alpine features.
6274 <P>
6275 <End of help on this topic>
6276 </BODY>
6277 </HTML>
6278 ======= h_main_release_notes =======
6279 <HTML>
6280 <HEAD>
6281 <TITLE>Release Notes Command</TITLE>
6282 </HEAD>
6283 <BODY>
6284 <H1>Release Notes Command</H1>
6286 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
6287 as well as pointers to further information such as history and legal notes.
6289 <P>
6290 <End of help on this topic>
6291 </BODY>
6292 </HTML>
6293 ======= h_main_kblock =======
6294 <HTML>
6295 <HEAD>
6296 <TITLE>Keyboard Lock Command</TITLE>
6297 </HEAD>
6298 <BODY>
6299 <H1>Keyboard Lock Command</H1>
6301 This command allows your Alpine session to be protected
6302 during a temporary absence from your terminal.
6304 <P>
6305 <End of help on this topic>
6306 </BODY>
6307 </HTML>
6308 ======= h_main_journal =======
6309 <HTML>
6310 <HEAD>
6311 <TITLE>Journal Command</TITLE>
6312 </HEAD>
6313 <BODY>
6314 <H1>Journal Command</H1>
6316 This command displays a list of all the status messages Alpine has
6317 displayed (on the third line from the bottom of the screen). This may
6318 be useful if a message disappeared before you had a chance to read it.
6320 <P>
6321 <End of help on this topic>
6322 </BODY>
6323 </HTML>
6324 ======= h_common_role =======
6325 <HTML>
6326 <HEAD>
6327 <TITLE>Role Command</TITLE>
6328 </HEAD>
6329 <BODY>
6330 <H1>Role Command</H1>
6332 The Role command is similar to the Compose command except that it starts
6333 off by letting you select a <A HREF="h_rules_roles">role</A>
6334 to be used for the composition.
6335 You may set up alternate roles by using Setup/Rules/Roles.
6337 <P>
6338 <End of help on this topic>
6339 </BODY>
6340 </HTML>
6341 ======= h_common_conditional_cmds =======
6342 <HTML>
6343 <HEAD>
6344 <TITLE>Conditional Commands</TITLE>
6345 </HEAD>
6346 <BODY>
6347 <H1>Conditional Commands</H1>
6349 The presence or absence of certain commands, particularly in the
6350 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
6351 whether or not specific features are set in your Alpine configuration.
6352 (You can access the SETUP CONFIGURATION screen, where they are found, from
6353 Alpine's MAIN MENU.) To see if a desired command's availability is
6354 conditioned on a feature setting, see the command's help text (highlight
6355 the phrase associated with the command and hit Return).
6357 <P>
6358 Also note that some
6359 commands may be administratively disabled by your system manager;
6360 if they don't work, please check with your local help desk.
6362 <P>
6363 <UL>
6364 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6365 </UL><P>
6366 <End of help on this topic>
6367 </BODY>
6368 </HTML>
6369 ======= h_common_pipe =======
6370 <HTML>
6371 <HEAD>
6372 <TITLE>Pipe Command</TITLE>
6373 </HEAD>
6374 <BODY>
6375 <H1>Pipe Command</H1>
6377 Pipe
6378 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6379 allows you to send a message to a specified Unix command for external
6380 processing.
6381 This command's availability is controlled by the
6382 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6383 feature.
6384 By default, the processed text of the message is sent to the command
6385 you specify and the output is captured by Alpine and shown to you.
6386 When you run the pipe command, there are some sub-commands which may be
6387 used to alter this behavior.
6388 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6390 <P>
6391 <End of help on this topic>
6392 </BODY>
6393 </HTML>
6394 ======= h_common_goto =======
6395 <HTML>
6396 <HEAD>
6397 <TITLE>Goto Command</TITLE>
6398 </HEAD>
6399 <BODY>
6400 <H1>Goto Command</H1>
6402 Goto
6403 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6404 is the command that lets you bypass Alpine's folder selection screens
6405 and jump directly to a new folder. You can select any folder in the
6406 world: one in your current collection, one in a different collection or
6407 one in a collection you've never even used before.
6408 <P>
6410 Alpine will help you as much as possible to narrow in on the folder you want.
6411 However, if the folder is outside of your defined collections, you are
6412 going to have to enter the exact folder location using the correct
6413 <A HREF="h_valid_folder_names">syntax</A>
6414 for a remote folder and/or fully-qualified path name.
6416 <P>
6417 <End of help on this topic>
6418 </BODY>
6419 </HTML>
6420 ======= h_common_nextnew =======
6421 <HTML>
6422 <HEAD>
6423 <TITLE>NextNew Command</TITLE>
6424 </HEAD>
6425 <BODY>
6426 <H1>NextNew Command</H1>
6428 When you press the TAB key, Alpine advances to the next
6429 "interesting" message.
6430 This will be the next message you have not seen before, or the next message
6431 you have flagged Important, whichever comes first.
6432 Unread messages that have been deleted are not considered interesting.
6433 (A note about reading news. Alpine expects you to "Delete" news
6434 articles after you have read them if you want to remove them from future
6435 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6436 more information.)
6438 <P>
6439 The NextNew command is affected by the feature
6440 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6441 which causes Alpine to only consider Unread messages interesting, not messages
6442 flagged Important.
6444 <P>
6445 This command behaves a little differently when it finds there are no more
6446 interesting messages left in the current folder.
6447 If the current folder is one of your Incoming Message Folders
6448 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6449 or it is a newsgroup, then Alpine will try to find the next folder or
6450 newsgroup that contains <EM>Recent</EM> messages and will ask you
6451 if you want to open that folder.
6452 This behavior may be modified by using the
6453 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6454 feature that causes Alpine to look for Unseen messages instead of Recent
6455 messages.
6456 The NextNew command's behavior is also affected by the configuration features
6457 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6458 and
6459 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6461 <P>
6462 <End of help on this topic>
6463 </BODY>
6464 </HTML>
6465 ======= h_common_jump =======
6466 <HTML>
6467 <HEAD>
6468 <TITLE>Jump Command</TITLE>
6469 </HEAD>
6470 <BODY>
6471 <H1>Jump Command</H1>
6473 This is Alpine's way of allowing you to go straight to a specific message.
6474 Just press "J" and then enter the message number. By default, Alpine is also
6475 configured such that typing in any number automatically jumps you to that
6476 message
6477 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6478 in the SETUP CONFIGURATION).
6480 <P>
6481 <End of help on this topic>
6482 </BODY>
6483 </HTML>
6484 ======= h_common_flag =======
6485 <HTML>
6486 <HEAD>
6487 <TITLE>Flag Command</TITLE>
6488 </HEAD>
6489 <BODY>
6490 <H1>Flag Command</H1>
6492 Flag
6493 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6494 is the command that allows users to manipulate the status flags that
6495 appear on the left side of the MESSAGE INDEX screen. The most common
6496 use of this is to mark a message as important. This is something of a
6497 note to yourself to get back to that message. You may also use the
6498 flag command to set (or unset) the flags that indicate that a message
6499 is new, answered, deleted, or forwarded.<P>
6501 Provided the mail server supports it,
6502 you may also manipulate user-defined keywords
6503 for a message using the flag command.
6504 These keywords will be available if you use the Flag Details screen that you
6505 can get to after typing the
6506 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6507 command.
6508 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6509 which are always present.
6510 You may add new keywords by using the Add KW command from the Flag Details screen
6511 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6513 The availability of the flag command is determined by the
6514 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6515 feature in your Alpine configuration. Also, it is possible that Flag could be
6516 administratively disabled by your system manager; if it doesn't work,
6517 please check with your local help desk before reporting a bug.
6518 The behavior of the flag command may be modified by the
6519 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6520 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6522 <P>
6523 <End of help on this topic>
6524 </BODY>
6525 </HTML>
6526 ======= h_common_hdrmode =======
6527 <HTML>
6528 <HEAD>
6529 <TITLE>HdrMode Command</TITLE>
6530 </HEAD>
6531 <BODY>
6532 <H1>HdrMode Command</H1>
6534 Every email message comes with some header lines that you normally
6535 don't see (and don't want to see).
6536 These include anywhere from 3-20 lines (or more) added by the
6537 Internet mail transport system to record the route your message took,
6538 for diagnostic purposes.
6539 These are normally of no import and simply
6540 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6541 This also includes other non-standard headers the message may contain.
6542 If you want to see these headers, there is a way to reveal them.
6543 <P>
6545 The Header Mode
6546 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6547 command is a toggle that controls Alpine's handling of these header
6548 lines. Normally, full headers is "off" and you only see a
6549 few lines about who a message is to and who it is from. When you
6550 press
6551 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6552 to turn full headers on, Alpine will show you
6553 the normal header lines as well as delivery headers, comment headers,
6554 MIME headers, and any other headers present.
6555 <P>
6557 Several different Alpine commands honor the header mode -- it affects how
6558 messages are displayed, how they appear in forward and reply email, how
6559 they are printed, how they are saved, and how they are exported.
6560 <!--chtml if pinemode="os_windows"-->
6561 <!--chtml else-->
6562 The pipe command is also affected.
6563 <!--chtml endif-->
6564 <P>
6566 The presence or absence of the Header Mode command is determined by the
6567 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6568 Feature-List option in your Alpine configuration.
6570 <P>
6571 If you have also turned on the
6572 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6573 option then the HdrMode command actually rotates through three states
6574 instead of just two.
6575 The first is the normal view with long quotes suppressed.
6576 The second is the normal view but with the long quotes included.
6577 The last enables the display of all headers in the message.
6578 When using Export, Pipe, Print, Forward, or Reply the quotes are
6579 never suppressed, so the first two states are identical.
6581 <P>
6582 The behavior of the Header Mode command may be altered slightly by
6583 turning on the
6584 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6585 Feature-List option in your Alpine configuration.
6586 In particular, it will cause the Header Mode to be persistent when moving
6587 from message to message instead of resetting to the default for each message.
6589 <P>
6590 <UL>
6591 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6592 </UL><P>
6593 <End of help on this topic>
6594 </BODY>
6595 </HTML>
6596 ======= h_common_print =======
6597 <HTML>
6598 <HEAD>
6599 <TITLE>Print Command</TITLE>
6600 </HEAD>
6601 <BODY>
6602 <H1>Print Command</H1>
6604 The Print
6605 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6606 command allows you to print a copy of a message.
6607 There are many SETUP CONFIGURATION features that affect the
6608 Print command, including
6609 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6610 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6611 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6612 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6613 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6614 You set up for printing by using the Printer option of the Setup command
6615 on the MAIN MENU.
6616 <P>
6618 <P>
6619 <End of help on this topic>
6620 </BODY>
6621 </HTML>
6622 ======= h_common_take =======
6623 <HTML>
6624 <HEAD>
6625 <TITLE>TakeAddr Command</TITLE>
6626 </HEAD>
6627 <BODY>
6628 <H1>TakeAddr Command</H1>
6631 With the Take Address
6632 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6633 command, you can extract email addresses from an
6634 incoming message and save them in an address book. This is an easy way
6635 to add to your address book and avoid having to remember the email
6636 addresses of the people who write to you.
6637 <P>
6639 If the message is just to you individually, then you will only need to
6640 provide a nickname. If the message contains more than one email address,
6641 then you will see an address
6642 selection screen that lets you choose the address you want to save into
6643 your address book, or lets you choose several of them add to a
6644 personal distribution list.
6645 <P>
6647 Once you've added an entry to your address book, you can use it from the
6648 message composer by typing the nickname of the entry into one of the
6649 header fields (for example, into the To: field), or you can use ^T from
6650 the header field to select the entry from your address book.
6651 <P>
6653 If the configuration feature
6654 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6655 is set, the behavior of the Take command is altered slightly.
6657 <P>
6658 <End of help on this topic>
6659 </BODY>
6660 </HTML>
6661 ======= h_ge_import =======
6662 <HTML>
6663 <HEAD>
6664 <TITLE>Import File Selection</TITLE>
6665 </HEAD>
6666 <BODY>
6667 <H1>Import File Selection</H1>
6669 You are importing a file that you previously
6670 exported from Alpine.
6671 You are now being asked for the name of that file.
6672 The easiest way to select a file is probably with the "^T"
6673 "To Files" command.
6674 Alternatively, you may type in a file name.
6675 It may be an absolute pathname.
6676 Otherwise, it is a file located in your home directory
6677 or current working directory
6678 <!--chtml if pinemode="running"-->
6679 (which, at least for your current Alpine "session,"
6680 is "<!--#echo var="CURRENT_DIR"-->")
6681 <!--chtml endif-->, depending on the
6682 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6683 In any case, you finish by typing a carriage return to accept the
6684 file name that is displayed.
6685 When the feature
6686 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6687 is turned on you may use TAB to complete partially typed in names.
6688 <P>
6689 You may cancel the import operation by typing "^C" after exiting
6690 this help.
6691 <P>
6692 <End of help on this topic>
6693 </BODY>
6694 </HTML>
6695 ======= h_ge_allparts =======
6696 <HTML>
6697 <HEAD>
6698 <TITLE>Export Message File Selection</TITLE>
6699 </HEAD>
6700 <BODY>
6701 <H1>Export Message File Selection</H1>
6703 You are Exporting a message from an Alpine mail folder
6704 to a plain text file.
6705 You also have the option of exporting all of the attachments associated
6706 with the message.
6707 You are now being asked for the name of the file to export <EM>to</EM>.
6708 The easiest way to select a file is probably with the "^T"
6709 "To Files" subcommand.
6710 After returning from that subcommand you will still be allowed to
6711 edit the name you have selected.
6712 Alternatively, you may type in a file name.
6713 It may be an absolute pathname.
6714 Otherwise, it is a file located in your home directory
6715 or current working directory
6716 <!--chtml if pinemode="running"-->
6717 (which, at least for your current Alpine "session,"
6718 is "<!--#echo var="CURRENT_DIR"-->")
6719 <!--chtml endif-->, depending on the
6720 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6721 In any case, you finish by typing a carriage return to accept the
6722 file name that is displayed.
6723 When the feature
6724 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6725 is turned on you may use TAB to complete partially typed in names.
6726 <P>
6727 The message you are exporting appears to have some attachments.
6728 If you wish to save <EM>all</EM> of the attachments at once,
6729 type the "^P" "AllParts" command to turn on
6730 saving of the attachments.
6731 You may turn it back off by typing "^P" again, which will now
6732 be labeled "NoAllParts" instead.
6733 If you want to save the parts the command displayed should be
6734 "NoAllParts"!
6735 When you choose to save attachments like this, the attachments will be saved
6736 in a newly created directory.
6737 That directory will have the same name as the file name you choose here,
6738 with the letters ".d" appended.
6739 If that directory already exists, then the letters ".d_1" will
6740 be tried, then ".d_2" and so on until a name that doesn't exist
6741 is found.
6742 For example, if you select the file name
6743 <P>
6744 <CENTER><SAMP>filename</SAMP></CENTER>
6745 <P>
6746 to export the message to, then the directory used for the attachments will be
6747 <P>
6748 <CENTER><SAMP>filename.d</SAMP></CENTER>
6749 <P>
6750 or perhaps
6751 <P>
6752 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
6753 <P>
6754 The attachments will then be put into files inside that directory.
6755 The names for the attachment files will be derived from the attachments
6756 if possible.
6757 This is done in the same way as the default values are derived if you
6758 save them one at a time.
6759 (The "filename" parameter from the Content-Disposition header
6760 is the first choice. If that doesn't exist, the "name"
6761 parameter from the Content-Type header is used.)
6762 If a name for a particular attachment is not available, then the
6763 part number of the attachment is used, with the characters "part_"
6764 prepended.
6765 An example of that would be
6766 <P>
6767 <CENTER><SAMP>part_2.1</SAMP></CENTER>
6768 <P>
6769 If you want to save only some of the attachments or if you want more control
6770 over the directory and filename where an attachment is saved you may
6771 cancel out of this command and View the attachment list.
6772 From there you can save each attachment individually.
6773 <P>
6774 You may cancel the Export operation by typing "^C" after exiting
6775 this help.
6776 <P>
6777 <End of help on this topic>
6778 </BODY>
6779 </HTML>
6780 ======= h_ge_export =======
6781 <HTML>
6782 <HEAD>
6783 <TITLE>Export File Selection</TITLE>
6784 </HEAD>
6785 <BODY>
6786 <H1>Export File Selection</H1>
6788 You are Exporting or Saving something from within the Alpine world
6789 (a message, an attachment, etc.)
6790 to a plain text file.
6791 You are now being asked for the name of the file to export <EM>to</EM>.
6792 The easiest way to select a file is probably with the "^T"
6793 "To Files" subcommand.
6794 After returning from that subcommand you will still be allowed to
6795 edit the name you have selected.
6796 Alternatively, you may type in a file name.
6797 It may be an absolute pathname.
6798 Otherwise, it is a file located in your home directory
6799 or current working directory
6800 <!--chtml if pinemode="running"-->
6801 (which, at least for your current Alpine "session,"
6802 is "<!--#echo var="CURRENT_DIR"-->")
6803 <!--chtml endif-->, depending on the
6804 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6805 In any case, you finish by typing a carriage return to accept the
6806 file name that is displayed.
6807 When the feature
6808 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6809 is turned on you may use TAB to complete partially typed in names.
6810 <P>
6811 If the object you are exporting is a message with some attachments,
6812 you may wish to save all of the attachments by typing the "^P"
6813 "AllParts" command to turn on saving of the attachments.
6814 This subcommand will only be visible if the message actually has attachments.
6815 You may also View the attachment list and save individual attachments from
6816 there.
6817 <P>
6818 If you are SAVING a text part (text/plain, text/html, etc.) you can use
6819 the Control-R subcommand to toggle if saving will be done in binary mode,
6820 meaning that the attachment will be decoded, but will not be transformed
6821 to UTF-8 for further processing (either in internal filters, or user
6822 supplied filters.) This is useful in case you either want to preserve
6823 the text as it was encoded originally to you, or the attachment was
6824 incorrectly attached (the attachment is not of text type) and you need
6825 the original text to process the attachment.
6826 <P>
6827 You may cancel the Export operation by typing "^C" after exiting
6828 this help.
6829 <P>
6830 <End of help on this topic>
6831 </BODY>
6832 </HTML>
6833 ======= h_common_save =======
6834 <HTML>
6835 <HEAD>
6836 <TITLE>Save and Export Commands</TITLE>
6837 </HEAD>
6838 <BODY>
6839 <H1>Save and Export Commands</H1>
6841 Save
6842 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
6843 and Export
6844 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
6845 are the two alternatives Alpine gives you to keep a copy of the message
6846 you are reading. If you want to keep the message within Alpine's email
6847 world, use "Save"; if you want to use the message in another
6848 program, use "Export".
6849 <P>
6851 When you Save a message, it is put into an existing folder or into a new
6852 folder in one of your existing folder collections. The message stays in
6853 email format and can be read by Alpine again. Alpine may use a special format
6854 for its mail folders -- never edit an Alpine folder by hand or with any
6855 program other than Alpine. The exact behavior of the Save command can be
6856 configured with the
6857 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
6858 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
6859 and
6860 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
6861 feature list settings.
6862 The name of the folder offered as a default is controlled by the option
6863 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
6864 <P>
6866 When you use Export, the message is placed in a plain text file in your
6867 home directory
6868 <!--chtml if pinemode="running"-->
6869 (which, in the present configuration of your system, is
6870 "<!--#echo var="HOME_DIR"-->")
6871 <!--chtml endif-->
6872 or current working directory
6873 <!--chtml if pinemode="running"-->
6874 (which, at least for your current Alpine "session,"
6875 is "<!--#echo var="CURRENT_DIR"-->")
6876 <!--chtml endif-->, depending on the
6877 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
6878 configuration setting. In the normal case, only minimal
6879 headers are exported with the message; however, if the full header mode
6880 (whose availability may be disabled by setting the feature
6881 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6882 in SETUP CONFIGURATION) is
6883 toggled on, then complete headers are exported along with the message
6884 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
6885 defined, they may affect the contents of the exported file.)
6887 <P>
6888 <End of help on this topic>
6889 </BODY>
6890 </HTML>
6891 ======= h_common_bounce =======
6892 <HTML>
6893 <HEAD>
6894 <TITLE>Bounce Command</TITLE>
6895 </HEAD>
6896 <BODY>
6897 <H1>Bounce Command</H1>
6899 The Bounce
6900 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
6901 command allows you to re-send, or "remail", a
6902 message, as if you were never in the loop. It is analogous to crossing
6903 out your address on a postal letter, writing a different address on the
6904 envelope, and putting it into the mailbox. Bounce is used primarily to
6905 redirect email that was sent to you in error.
6906 Also, some owners of email
6907 lists need the bounce command to handle list traffic.
6908 Bounce is not anonymous.
6909 A ReSent-From header is added to the message so that the recipient may
6910 tell that you Bounced it to them.
6911 <P>
6913 The presence or absence of the Bounce command is determined by the
6914 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
6915 feature in your Alpine configuration.
6916 The feature
6917 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
6918 affects the behavior of the Bounce command.
6919 Also, it is possible that Bounce could be
6920 administratively disabled by your system manager; if it doesn't work,
6921 please check with your local help desk before reporting a bug.
6923 <P>
6924 <End of help on this topic>
6925 </BODY>
6926 </HTML>
6927 ======= h_common_reply =======
6928 <HTML>
6929 <HEAD>
6930 <TITLE>Reply and Forward Commands</TITLE>
6931 </HEAD>
6932 <BODY>
6934 <H1>Reply and Forward Commands</H1>
6936 Replying
6937 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
6938 and Forwarding
6939 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
6940 are your two alternatives for following up on the
6941 message you are reading. You would use reply if you want to get email
6942 back to the author of the message and/or the other people who have
6943 already seen it. You use forward if you want somebody new to see the
6944 message.
6945 <P>
6947 In the normal case, the only thing that you must supply when forwarding a
6948 message is the name/email address of the new recipient.
6949 Alpine will include the text of the forwarded message.
6950 Alpine will also include any attachments to the message.
6951 There is space above the forwarded text for you to include additional comments.
6952 <P>
6954 When replying, you usually have to answer some questions.
6955 If the message is to multiple people and/or specified with a Reply-To: header,
6956 then you will have to decide who should get the reply.
6957 You also need to decide whether or not to include the previous
6958 message in your reply.
6959 Some of this is configurable.
6960 Specifically, see the
6961 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
6962 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
6963 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
6964 and
6965 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
6966 configuration features.
6967 <P>
6969 Both the Reply and Forward commands react to the full header mode toggle.
6970 If the full header mode is on, then all the header and delivery lines are
6971 included with the text of the message in your reply/forward.
6972 <P>
6974 Other configuration features that affect the Reply command are
6975 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
6976 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
6977 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
6979 <P>
6980 <End of help on this topic>
6981 </BODY>
6982 </HTML>
6983 ======= h_common_delete =======
6984 <HTML>
6985 <HEAD>
6986 <TITLE>Delete and Undelete Commands</TITLE>
6987 </HEAD>
6988 <BODY>
6989 <H1>Delete and Undelete Commands</H1>
6991 Delete
6992 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
6993 and Undelete
6994 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
6995 allow you to change the Deleted flag for the current message.
6996 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
6997 removes the mark.
6998 In the MESSAGE INDEX, deleted messages have a "D" in the status field
6999 at the left hand edge of the index line.
7000 When viewing a deleted message, the letters "DEL" will be present
7001 in the upper right hand corner of the screen.
7002 Delete simply <EM>marks</EM> a message Deleted, it does not actually
7003 get rid of the message.
7004 The eXpunge command (available from the MESSAGE INDEX screen) actually
7005 removes all of the deleted messages in a folder.
7006 Once a message is eXpunged, it can't be retrieved.
7007 <P>
7009 The Delete command is affected by the setting of the configuration feature
7010 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
7012 <P>
7013 <End of help on this topic>
7014 </BODY>
7015 </HTML>
7016 ======= h_common_postpone =======
7017 <HTML>
7018 <HEAD>
7019 <TITLE>Postpone Command</TITLE>
7020 </HEAD>
7021 <BODY>
7022 <H1>Postpone Command</H1>
7024 The postpone
7025 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
7026 command allows you to temporarily stop working on the current
7027 message so you may read
7028 other messages or compose another message. When you want to resume a
7029 message later, start to compose and answer "yes" to the
7030 "Continue postponed composition?" question. You may
7031 postpone as many messages as you like.
7033 <P>
7034 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
7035 in the Setup/Config screen, then the Postpone command will prompt you for
7036 the folder in which to store your outgoing message.
7038 <P>
7039 <End of help on this topic>
7040 </BODY>
7041 </HTML>
7042 ======= h_compose_cancel =======
7043 <HTML>
7044 <HEAD>
7045 <TITLE>Cancel Command</TITLE>
7046 </HEAD>
7047 <BODY>
7048 <H1>Cancel Command</H1>
7050 Cancel
7051 <!--chtml if pinemode="function_key"-->
7052 (F2)
7053 <!--chtml else-->
7054 (^C)
7055 <!--chtml endif-->
7057 The Cancel command returns you to Alpine's normal mail processing and
7058 causes the message currently under composition to be thrown out.
7059 The message text <EM>will be lost</EM>.
7061 <P>
7062 Note: Unless the <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A> has been set, the text of the most recent composition cancelled
7063 will be preserved in the file named
7064 <!--chtml if pinemode="os_windows"-->
7065 "DEADLETR".
7066 <!--chtml else-->
7067 "dead.letter" in your home directory.
7068 <!--chtml endif-->
7069 If you unintentionally cancel a message, look there for its text.
7071 <P>
7072 <End of help on this topic>
7073 </BODY>
7074 </HTML>
7075 ======= h_compose_addrcomplete =======
7076 <HTML>
7077 <HEAD>
7078 <TITLE>Address Completion</TITLE>
7079 </HEAD>
7080 <BODY>
7081 <H1>Address Completion</H1>
7083 When entering addresses in the address fields of the composer (To, Cc, etc.)
7084 the TAB key may be used to help complete the address.
7085 Type a partial nickname and tap the TAB key to complete the typing.
7086 The unambiguous part of the name will be filled in automatically.
7087 Typing TAB twice in succession will bring up a selection list of possibilities,
7088 making it easy to find and choose the correct address.
7090 <P>
7091 The matching algorithm is rather ad hoc.
7092 The search starts with a search of your address book.
7093 It counts as a match if the nickname, address, or fullname field of an
7094 entry begins with the text typed in so far. It is also a match if
7095 a later word in the fullname (for example, the middle name or last name)
7096 begins with the entered text.
7097 <P>
7098 Next comes an LDAP search.
7099 The search will happen for any servers that have the
7100 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
7101 feature set. You can set or unset the feature for each server independently
7102 in the Setup/Directory screen.
7103 <P>
7104 Finally, if you are replying to or forwarding a message, that message is
7105 searched for likely candidate addresses that match the typed-in text.
7107 <P>
7108 <End of help on this topic>
7109 </BODY>
7110 </HTML>
7111 ======= h_compose_richhdr =======
7112 <HTML>
7113 <HEAD>
7114 <TITLE>Rich Header Command</TITLE>
7115 </HEAD>
7116 <BODY>
7117 <H1>Rich Header Command</H1>
7119 The Rich Header command allows you to toggle between the list of
7120 all message headers available for editing and those that are most
7121 common.
7123 <P>
7124 Use this toggle to expose headers that are not normally visible by
7125 default.
7126 This set usually includes the
7127 "Bcc:",
7128 "Fcc:",
7129 "Lcc:",
7130 and "Newsgroups"
7131 headers.
7132 If you are posting to a newsgroup the set of defaults is a little different.
7133 Obviously, in that case, the Newsgroups header is of interest so is not
7134 hidden.
7135 For news posting the hidden set includes the
7136 "To:",
7137 "Cc:",
7138 "Bcc:",
7139 "Fcc:",
7140 and "Lcc:"
7141 headers.
7142 You won't normally want to edit these, which is why they are hidden,
7143 but it is sometimes useful to be able to set them manually.
7145 <P>
7146 The default sets of headers listed above can be altered.
7147 Any header that you have added to the
7148 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
7149 option, but not to the
7150 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
7151 option will appear when you use the Rich Headers command to
7152 make the Rich Headers visible.
7153 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
7154 even without toggling the Rich Headers command.)
7156 <P>
7157 <End of help on this topic>
7158 </BODY>
7159 </HTML>
7160 ======= h_compose_send =======
7161 <HTML>
7162 <HEAD>
7163 <TITLE>Send Command</TITLE>
7164 </HEAD>
7165 <BODY>
7166 <H1>Send Command</H1>
7168 The Send command
7169 <!--chtml if pinemode="function_key"-->
7170 (F3)
7171 <!--chtml else-->
7172 (^X)
7173 <!--chtml endif-->
7174 tells Alpine you are finished composing.
7175 Before actually sending it, though, Alpine will ask you to confirm
7176 your intention, and, at the same time, redisplayed the message text
7177 with the recipients at the top of the screen to give you the opportunity
7178 to review and verify that the message is addressed to the people
7179 you intended.
7180 <P>
7181 If the feature
7182 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
7183 then this confirmation prompt and any options it allows are skipped.
7185 <P>
7186 This confirmation prompt may also offer, depending
7187 on your particular Setup/Config, options allowing you to set
7188 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
7189 include attachments in the "Fcc" (if you had previously
7190 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
7191 observe details of the
7192 <A HREF="h_config_verbose_post">message submission process</A>,
7193 choose the filter through which the
7194 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
7195 or turn of flowed text generation.
7197 <P>
7198 <End of help on this topic>
7199 </BODY>
7200 </HTML>
7201 ======= h_compose_markcutpaste =======
7202 <HTML>
7203 <HEAD>
7204 <TITLE>Mark, Cut and Paste Commands</TITLE>
7205 </HEAD>
7206 <BODY>
7207 <H1>Mark, Cut and Paste Commands</H1>
7209 You can define a "block" of text, which can subsequently
7210 be deleted or
7211 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
7212 then moving the cursor to the end of the desired text block. You can then
7213 "cut" the block out
7214 <!--chtml if pinemode="function_key"-->
7215 "F9",
7216 <!--chtml else-->
7217 "Ctrl-K",
7218 <!--chtml endif-->
7219 move the cursor, and "paste" it
7220 <!--chtml if pinemode="function_key"-->
7221 "F10",
7222 <!--chtml else-->
7223 "Ctrl-U",
7224 <!--chtml endif-->
7225 in the new location. Also, you can paste more than once, allowing you
7226 to use this feature to copy a block of text.<P>
7228 If you press
7229 <!--chtml if pinemode="function_key"-->
7230 "F9"
7231 <!--chtml else-->
7232 "^K"
7233 <!--chtml endif-->
7234 without having marked anything, Alpine will delete
7235 a single line. If you delete a group of lines together, Alpine keeps them
7236 in the same buffer, so
7237 <!--chtml if pinemode="function_key"-->
7238 F10
7239 <!--chtml else-->
7240 ^U
7241 <!--chtml endif-->
7242 will restore them as a block. About
7243 terminology: Mark is shown as "^^". The first "^" means you should
7244 hold down the "Control" key on your keyboard. The second "^" means
7245 "type the character ^".
7247 <P>
7248 <End of help on this topic>
7249 </BODY>
7250 </HTML>
7251 ======= h_compose_justify =======
7252 <HTML>
7253 <HEAD>
7254 <TITLE>Justify Command</TITLE>
7255 </HEAD>
7256 <BODY>
7257 <H1>Justify Command</H1>
7259 The Justify
7260 <!--chtml if pinemode="function_key"-->
7261 (F4)
7262 <!--chtml else-->
7263 (^J)
7264 <!--chtml endif-->
7265 command reformats the text in the paragraph the cursor is in.
7266 Paragraphs are separated by one blank line or a line beginning with a space.
7267 This is useful when you have been editing a paragraph and the lines become
7268 uneven. The text is left aligned or justified and the right is ragged. If
7269 the text is already justified as typed with auto-wrap, no justification will
7270 be done.
7272 <P>
7273 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
7274 block of text, the Justify command is modified.
7275 Instead of automatically justifying the current paragraph you will be
7276 asked if you want to justify the paragraph, justify the selected region,
7277 or adjust the quote level of the selected region.
7278 Adjusting the quote level only works if you are using standard
7279 "> " or ">" quotes, which is the default if you haven't
7280 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
7282 <P>
7283 When composing a reply containing included text, the justify command
7284 will reformat text to the right of the
7285 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
7286 adding or removing indented lines as needed. Paragraphs are separated
7287 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
7288 line containing the indent string and one or more blank spaces.
7289 Included text that was previously indented (or "quoted") is
7290 not preserved.
7292 <P>
7293 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
7294 in 1999 and its wide-spread adoption since then, you will usually be better off if you
7295 use the standard
7296 "> " or ">" quotes.
7298 <P>
7299 <End of help on this topic>
7300 </BODY>
7301 </HTML>
7302 ======= h_compose_spell =======
7303 <HTML>
7304 <HEAD>
7305 <TITLE>Spell Check Command</TITLE>
7306 </HEAD>
7307 <BODY>
7308 <H1>Spell Check Command</H1>
7310 The "To Spell"
7311 <!--chtml if pinemode="function_key"-->
7312 (F12)
7313 <!--chtml else-->
7314 (^T)
7315 <!--chtml endif-->
7316 command calls an external spell checking program to look over the
7317 message you are composing. By default, Alpine uses
7318 <P>
7319 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
7320 <P>
7321 if it knows where to find "aspell".
7322 If there is no "aspell" command available but the command "ispell" is available
7323 then the command used is
7324 <P>
7325 <CENTER><SAMP>ispell -l</SAMP></CENTER>
7326 <P>
7327 Otherwise, the ancient "spell" command is used.
7328 <P>
7329 For PC-Alpine, you must install the aspell library code that you
7330 may get from
7331 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
7333 <P>
7334 <End of help on this topic>
7335 </BODY>
7336 </HTML>
7337 ======= h_compose_alted =======
7338 <HTML>
7339 <HEAD>
7340 <TITLE>Alt Editor Command</TITLE>
7341 </HEAD>
7342 <BODY>
7343 <H1>Alt Editor Command</H1>
7345 The "Alt Editor" command's availability depends on the
7346 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
7348 <P>
7349 When the variable specifies a valid editor on your system, this
7350 command will launch it with the current text of your message
7351 already filled in.
7353 <P>
7354 <End of help on this topic>
7355 </BODY>
7356 </HTML>
7357 ======= h_compose_readfile =======
7358 <HTML>
7359 <HEAD>
7360 <TITLE>Read File Command</TITLE>
7361 </HEAD>
7362 <BODY>
7363 <H1>Read File Command</H1>
7365 The "Read File"
7366 <!--chtml if pinemode="function_key"-->
7367 (F5)
7368 <!--chtml else-->
7369 (^R)
7370 <!--chtml endif-->
7371 command allows you to copy in text from an existing file. You will be
7372 prompted for the name of a file to be inserted into the message. The file
7373 name is relative to your home directory
7374 <!--chtml if pinemode="running"-->
7375 (which, in the present configuration of your system, is
7376 "<!--#echo var="HOME_DIR"-->")
7377 <!--chtml endif-->
7378 or current working directory
7379 <!--chtml if pinemode="running"-->
7380 (which, at least for your current Alpine "session,"
7381 is "<!--#echo var="CURRENT_DIR"-->")
7382 <!--chtml endif-->, depending on the
7383 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7384 configuration setting; or, the file name must be specified as a full path name
7385 <!--chtml if pinemode="os_windows"-->
7386 -- for example: "A:\PAPER.TXT"
7387 <!--chtml else-->
7388 -- for example: "/tmp/wisdom-of-the-day"
7389 <!--chtml endif-->
7390 (without the quotation marks).
7392 <P>
7393 The file will be inserted where the cursor is located. <B>The
7394 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7395 Unix machine but have files on a PC or Mac, the files must be transferred
7396 to the system Alpine is running on before they can be read. Please ask your
7397 local computer support people about the correct way to transfer a file to
7398 your Alpine system.
7400 <P>
7401 <End of help on this topic>
7402 </BODY>
7403 </HTML>
7404 ======= h_config_tray_icon =======
7405 <HTML>
7406 <HEAD>
7407 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7408 </HEAD>
7409 <BODY>
7410 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7412 PC-Alpine only.
7413 <P>
7414 This option restores a behavior of previous versions of PC-Alpine.
7415 These
7416 versions, when started, installed a PC-Alpine icon in the notification
7417 tray of Window's Taskbar. The primary use of this icon was to indicate
7418 new mail arrival by turning red (while the Taskbar icon remained green).
7419 Additionally, the icon now changes to yellow to signify that a mail folder
7420 has been closed unexpectedly.
7422 <P>
7423 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7424 color its Taskbar entry's icon red (as well as the icon in the Window
7425 Title). This feature is only provided for backwards compatibility.
7427 <P>
7428 <End of help on this topic>
7429 </BODY>
7430 </HTML>
7431 ======= h_common_suspend =======
7432 <HTML>
7433 <HEAD>
7434 <TITLE>Suspend Command</TITLE>
7435 </HEAD>
7436 <BODY>
7437 <H1>Suspend Command</H1>
7439 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7440 enabled, you can, at almost any time, temporarily halt your Alpine session,
7441 <!--chtml if pinemode="os_windows"-->
7442 minimizing it into an icon.
7443 <!--chtml else-->
7444 and return to your system prompt.
7445 <!--chtml endif-->
7447 <P>
7448 <End of help on this topic>
7449 </BODY>
7450 </HTML>
7451 ======= h_pipe_command =======
7452 <HTML>
7453 <HEAD>
7454 <TITLE>Pipe Command SubOptions</TITLE>
7455 </HEAD>
7456 <BODY>
7457 <H1>Pipe Command SubOptions</H1>
7459 By default, when you use the Pipe command, the processed text of the
7460 message is sent to the Unix command
7461 you specify and the output is captured by Alpine and shown to you.
7462 (This command is available in PC-Alpine, as well, but there aren't many
7463 Windows commands that work well with piping.)
7464 There are some sub-commands that may be used to alter this behavior.
7465 These are toggles that switch the behavior between two possibilities.
7466 They can be combined in any way you wish.
7467 <P>
7468 By default, the prompt at the bottom of the screen looks like
7469 <P>
7470 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7471 <P>
7472 or
7473 <P>
7474 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7475 <P>
7476 if you are piping more than one message.
7477 <P>
7478 The sub-command options are:
7479 <DL>
7480 <DT>Shown Text or Raw Text</DT>
7481 <DD>This option toggles between sending the shown (processed) text
7482 of the message to the Unix command, and sending the
7483 raw (unprocessed) text of the message to the Unix command.
7484 The default is to send the shown text.
7485 The raw version of the message will contain all of the headers and any
7486 MIME encoding that the message contains.
7487 If you've selected the Raw Text then the prompt will have the additional word
7488 "RAW" in it, like
7489 <P>
7490 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7491 <P>
7492 You can experiment with this option by piping to something simple like the
7493 Unix "cat" command.
7494 </DD>
7495 <DT>Captured Output or Free Output</DT>
7496 <DD>This option toggles between having Alpine capture the output of
7497 the Unix pipe command for display, and not capturing it.
7498 If the command you are piping to is a filter that will produce output
7499 you want to view, then you want to capture that output
7500 for display (the default).
7501 If the Unix command doesn't produce output or handles the display itself,
7502 then you want free output.
7503 When you've selected the Free Output option the prompt will change to
7504 <P>
7505 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7506 <P>
7507 </DD>
7508 <DT>No Delimiter or With Delimiter</DT>
7509 <DD>This option controls whether or not a Unix mailbox style delimiter
7510 will come before the text of the message.
7511 This is the delimiter used in the common Unix mailbox format.
7512 It's the single line that begins with the five characters
7513 "From" followed by a <SPACE> character.
7514 You'll usually only want to include this if the Unix command requires
7515 input in the format of a traditional Unix mailbox file.
7516 When you've selected the With Delimiter option the prompt will change to
7517 <P>
7518 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7519 <P>
7520 </DD>
7521 <DT>To Same Pipe or To Individual Pipes</DT>
7522 <DD>This option only shows up if you are running an aggregate
7523 pipe command.
7524 That is, the command was Apply Pipe, not just Pipe.
7525 You have the option of piping all of the selected messages through a
7526 single pipe to a single instance of the Unix command,
7527 or piping each individual message through a separate pipe to separate
7528 instances of the Unix command.
7529 The default is that all of the output will go through a single pipe
7530 to a single instance of the command.
7531 You can try this option with a command like "less", with Free
7532 Output enabled.
7533 When you've selected the Individual Pipes option the prompt will change to
7534 <P>
7535 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7536 <P>
7537 </DD>
7538 </DL>
7540 <P>
7541 As mentioned earlier, the options can be combined in any way you wish.
7542 You may leave them all off, turn them all on, or turn some of them on
7543 and some of them off.
7544 If you use the pipe command a second time in the same session the default
7545 options will be what you used the last time.
7547 <P>
7548 <End of help on this topic>
7549 </BODY>
7550 </HTML>
7551 ========== h_emptydir_subfolder_name =========
7552 <HTML>
7553 <HEAD>
7554 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7555 </HEAD>
7556 <BODY>
7557 <H1>Enter Subfolder Name</H1>
7559 <P>
7560 This is the name of a new subfolder in the directory you are creating.
7561 Because empty directories are hidden and therefore not useful, you must also
7562 create a subfolder in the directory you are creating in order that the
7563 directory remains visible.
7564 <P>
7565 Alternatively, you may turn off the configuration feature
7566 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7567 so that empty directories remain visible.
7568 If you do that, you will not be required to create the subfolder when you
7569 create a directory.
7571 <P>
7572 <End of help on this topic>
7573 </BODY>
7574 </HTML>
7575 ========== h_incoming_add_folder_name =========
7576 <HTML>
7577 <HEAD>
7578 <TITLE>ENTER FOLDER NAME</TITLE>
7579 </HEAD>
7580 <BODY>
7581 <H1>Enter Folder Name</H1>
7583 <P>
7584 This is the name of the folder on the previously specified server.
7585 By default the folder name is interpreted as defining a section of your personal
7586 folder area. This area and how you specify it are defined by the
7587 server, if one is specified.
7589 <P>
7590 To define a folder outside the default area, prefix
7591 the path with the namespace to use when interpreting the
7592 given path. If a namespace is specified, the folder name begins with the
7593 sharp (#) character followed by the name of the namespace
7594 and then the namespace's path-element-delimiter. Aside from the
7595 name's format, namespaces can also imply access rights, content
7596 policy, audience, location, and, occasionally, access methods.
7598 <P>
7599 Each server exports its own set (possibly of size one) of
7600 namespaces.
7601 For a more detailed explanation read about
7602 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7604 <P>
7605 To specify the default for INBOX on the server you can usually just enter
7606 "INBOX", and the server will understand the special meaning of
7607 that word.
7609 <P>
7610 <End of help on this topic>
7611 </BODY>
7612 </HTML>
7613 ========== h_incoming_add_folder_host =========
7614 <HTML>
7615 <HEAD>
7616 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7617 </HEAD>
7618 <BODY>
7619 <H1>Enter Incoming Folder Server</H1>
7621 You are being asked for the name of the server for use with this incoming
7622 folder.
7623 If the folder is on the machine where Alpine is running, then just enter
7624 RETURN without typing a server name.
7626 <P>
7627 If the folder is on an IMAP server then type the server's name followed
7628 by RETURN.
7629 You may use the ^X command if the server is the same as the server that
7630 the INBOX is on.
7632 <P>
7633 You may have to add optional extra information to the server name.
7634 For example, if the IMAP server is using a non-standard port number you
7635 would specify that by appending a colon (:) followed by the port number
7636 to the server name
7638 <P>
7639 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7640 <P>
7642 or you may need to specify a different protocol if the server is not an
7643 IMAP server. For example:
7645 <P>
7646 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7647 <P>
7649 for a POP server or
7651 <P>
7652 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7653 <P>
7655 for an NNTP news server.
7656 For an explanation of all of the possibilities, see
7657 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7658 for folders.
7660 <P>
7661 There is a special command (^W) if you want to set up a folder that gets its
7662 mail from a
7663 <A HREF="h_maildrop">Mail Drop</A>.
7664 If you type that command, you will be prompted for the information for
7665 both the Mail Drop folder and the destination folder.
7667 <P>
7668 <End of help on this topic>
7669 </BODY>
7670 </HTML>
7671 ========== h_incoming_add_inbox =========
7672 <HTML>
7673 <HEAD>
7674 <TITLE>ENTER INBOX SERVER</TITLE>
7675 </HEAD>
7676 <BODY>
7677 <H1>Enter INBOX Server</H1>
7679 You are being asked for the name of the server for use with
7680 the INBOX folder.
7681 Type the server's name followed by RETURN.
7683 <P>
7684 You may have to add optional extra information to the server name.
7685 For example, if the server is using a non-standard port number you
7686 would specify that by appending a colon (:) followed by the port number
7687 to the server name
7689 <P>
7690 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7691 <P>
7693 or you may need to specify a different protocol if the server is not an
7694 IMAP server. For example:
7696 <P>
7697 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7698 <P>
7700 for a POP server.
7701 <P>
7703 For an explanation of all of the possibilities, see
7704 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7705 for folders.
7707 <P>
7708 If the INBOX folder is on the machine where Alpine is running, then just enter
7709 RETURN without typing a server name.
7711 <P>
7712 There is a special command (^W) if you want to set up a folder that gets its
7713 mail from a
7714 <A HREF="h_maildrop">Mail Drop</A>.
7715 If you type that command, you will be prompted for the information for
7716 both the Mail Drop folder and the destination folder, which will be used
7717 as your INBOX folder.
7719 <P>
7720 <End of help on this topic>
7721 </BODY>
7722 </HTML>
7723 ========== h_incoming_add_maildrop_destn =========
7724 <HTML>
7725 <HEAD>
7726 <TITLE>ENTER DESTINATION SERVER</TITLE>
7727 </HEAD>
7728 <BODY>
7729 <H1>Enter Destination Server</H1>
7731 You are being asked for the name of the server where the destination
7732 folder is for use with this Mail Drop incoming folder.
7733 That is, you are using a Mail Drop for this incoming folder and
7734 you've already entered
7735 the server and folder name for the Mail Drop.
7736 Now you need to enter the server for the destination folder
7737 where the mail should be copied to.
7738 Mail will come from the Mail Drop and be copied to the destination folder.
7740 <P>
7741 Type the server's name followed by RETURN.
7742 If the folder is local to this computer, just type RETURN without entering
7743 a server name.
7745 <P>
7746 You may have to add optional extra information to the server name.
7747 For example, if the server is using a non-standard port number you
7748 would specify that by appending a colon (:) followed by the port number
7749 to the server name
7751 <P>
7752 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7753 <P>
7755 For an explanation of all of the possibilities, see
7756 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7757 for folders.
7759 <P>
7760 <End of help on this topic>
7761 </BODY>
7762 </HTML>
7763 ========== h_inbox_add_maildrop_destn =========
7764 <HTML>
7765 <HEAD>
7766 <TITLE>ENTER DESTINATION SERVER</TITLE>
7767 </HEAD>
7768 <BODY>
7769 <H1>Enter Destination Server</H1>
7771 You are being asked for the name of the server where the destination
7772 folder is for use with your Mail Drop INBOX.
7773 That is, you are using a Mail Drop for your INBOX and you've already entered
7774 the server and folder name for the Mail Drop.
7775 Now you need to enter the server for the destination folder
7776 where the mail should be copied to.
7777 Mail will come from the Mail Drop and be copied to the destination folder.
7779 <P>
7780 Type the server's name followed by RETURN.
7781 If the folder is local to this computer, just type RETURN without entering
7782 a server name.
7784 <P>
7785 You may have to add optional extra information to the server name.
7786 For example, if the server is using a non-standard port number you
7787 would specify that by appending a colon (:) followed by the port number
7788 to the server name
7790 <P>
7791 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7792 <P>
7794 For an explanation of all of the possibilities, see
7795 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7796 for folders.
7798 <P>
7799 <End of help on this topic>
7800 </BODY>
7801 </HTML>
7802 ========== h_inbox_add_maildrop =========
7803 <HTML>
7804 <HEAD>
7805 <TITLE>ENTER MAILDROP SERVER</TITLE>
7806 </HEAD>
7807 <BODY>
7808 <H1>Enter Mail Drop Server</H1>
7810 You are being asked for the name of the Mail Drop server for use with
7811 your INBOX.
7813 <P>
7814 Type the server's name followed by RETURN.
7816 <P>
7817 You may have to add optional extra information to the server name.
7818 For example, if the server is using a non-standard port number you
7819 would specify that by appending a colon (:) followed by the port number
7820 to the server name
7822 <P>
7823 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7824 <P>
7826 or you may need to specify a different protocol if the server is not an
7827 IMAP server. For example:
7829 <P>
7830 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7831 <P>
7833 for a POP server or
7835 <P>
7836 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7837 <P>
7839 for an NNTP news server.
7840 For an explanation of all of the possibilities, see
7841 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7842 for folders.
7844 <P>
7845 <End of help on this topic>
7846 </BODY>
7847 </HTML>
7848 ========== h_incoming_add_maildrop =========
7849 <HTML>
7850 <HEAD>
7851 <TITLE>ENTER MAILDROP SERVER</TITLE>
7852 </HEAD>
7853 <BODY>
7854 <H1>Enter Mail Drop Server</H1>
7856 You are being asked for the name of the Mail Drop server for use with
7857 this incoming folder.
7859 <P>
7860 Type the server's name followed by RETURN.
7861 You may use the ^X command if the server is the same as the server that
7862 the INBOX is on.
7864 <P>
7865 You may have to add optional extra information to the server name.
7866 For example, if the server is using a non-standard port number you
7867 would specify that by appending a colon (:) followed by the port number
7868 to the server name
7870 <P>
7871 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7872 <P>
7874 or you may need to specify a different protocol if the server is not an
7875 IMAP server. For example:
7877 <P>
7878 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7879 <P>
7881 for a POP server or
7883 <P>
7884 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7885 <P>
7887 for an NNTP news server.
7888 For an explanation of all of the possibilities, see
7889 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7890 for folders.
7892 <P>
7893 If the Mail Drop folder is on the machine where Alpine is running, then just enter
7894 RETURN without typing a server name.
7896 <P>
7897 <End of help on this topic>
7898 </BODY>
7899 </HTML>
7900 ========== h_maildrop =========
7901 <HTML>
7902 <HEAD>
7903 <TITLE>WHAT IS A MAIL DROP?</TITLE>
7904 </HEAD>
7905 <BODY>
7906 <H1>What is a Mail Drop?</H1>
7908 In some situaions it may make sense to have your mail delivered to one
7909 folder (the Mail Drop) and then when you want to read mail that has been
7910 delivered to the Mail Drop folder Alpine will move it to another
7911 destination folder.
7912 Often the Mail Drop will be a remote folder and messages will be moved from
7913 there to a local destination folder.
7915 <P>
7916 One example where this might make sense is if the Mail Drop folder is accessible
7917 only with the POP protocol.
7918 You could designate your POP inbox as the Mail Drop folder and have Alpine move
7919 mail from there to a local (on the same machine Alpine is running on)
7920 destination folder, where you'll read it.
7922 <P>
7923 A Mail Drop may only be used as your Inbox or as an
7924 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
7926 <P>
7927 There is no attempt to synchronize the contents of the destination folder
7928 with the contents of the Mail Drop folder.
7929 All that happens is that all of the messages in the Mail Drop folder are
7930 copied to the destination folder and then they are deleted and expunged (if possible)
7931 from the Mail Drop folder.
7932 The next time a check for new mail is made, any messages in the Mail
7933 Drop folder are once again copied to the destination folder and deleted
7934 and expunged from the Mail Drop folder.
7935 (If the Mail Drop folder is a news group, then the messages can't be
7936 expunged from the newsgroup. Instead, only Recent messages are copied from
7937 the newsgroup to the destination folder.)
7939 <P>
7940 Configuration of a Mail Drop is a little different from configuration of
7941 a folder that does not use a Mail Drop because you have to specify two
7942 folder names instead of one.
7943 The two folders may be any types of folders that Alpine can normally use.
7944 They don't have to be a remote folder and a local folder, that is
7945 simply the most common usage.
7946 When you use a Mail Drop folder Alpine will periodically re-open the Mail
7947 Drop to check for new mail.
7948 The new-mail checks will happen at the frequency set with the
7949 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
7950 but with a minimum time
7951 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
7952 between checks.
7953 Because of this minimum you may notice that new mail does not
7954 appear promptly when you expect it.
7955 The reason for this is to protect the server from over-zealous opening and
7956 closing of the Mail Drop folder.
7957 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
7958 the end of the folder index, then the check will happen, regardless of how
7959 long it has been since the previous check.
7960 <P>
7961 If there is new mail, that mail will be copied to the destination folder
7962 and then will be deleted from the Mail Drop.
7963 Note that using a Mail Drop with a local destination folder does not make
7964 sense if you read mail from more than one machine, because the mail is
7965 downloaded to the destination folder (which is accessible from only one
7966 machine) and deleted from the Mail Drop.
7967 <P>
7968 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
7970 <P>
7971 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
7973 <P>
7974 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
7975 <P>
7976 The brackets are not literal.
7977 <P>
7978 <CENTER><SAMP><DELIM></SAMP></CENTER>
7979 <P>
7980 is a single character that does not appear in the MailDropFolder name.
7981 If the name doesn't contain spaces then it can be a space character.
7982 The two folder names are full technical
7983 <A HREF="h_valid_folder_names">folder names</A>
7984 as used by Alpine.
7985 Here are a couple examples to give you an idea what is being talked about:
7987 <P>
7988 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
7989 <P>
7990 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
7991 <P>
7993 A #move folder may only be used as an
7994 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
7995 an Inbox.
7996 When you are in the FOLDER LIST of Incoming Message Folders (after turning
7997 on the
7998 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
7999 option)
8000 the Add command has a subcommand "Use Mail Drop"
8001 which may be helpful for defining the folder in your Alpine configuration.
8002 The same is true when you edit the
8003 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
8004 option in Setup/Config.
8005 Each of these configuration methods will also create the DestinationFolder
8006 if it doesn't already exist.
8007 If you are having problems, make sure the DestinationFolder exists.
8009 <P>
8010 <End of help on this topic>
8011 </BODY>
8012 </HTML>
8013 ========== h_save =========
8014 <HTML>
8015 <HEAD>
8016 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
8017 </HEAD>
8018 <BODY>
8019 <H1>Choose a Folder to Save Into</H1>
8021 After Exiting from this help text,
8022 type the name of the folder you want to save into and press RETURN.
8023 <P>
8024 Press ^T to get a list of your folders to choose from.
8025 Press ^C to cancel the Save.
8026 <P>
8027 If you have Folder Collections defined you may use
8028 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
8029 the collection being saved to.
8030 <P>
8031 If Tab Completion is enabled (it is enabled by default)
8032 you may type a Tab character to have Alpine complete the folder name for you.
8033 <P>
8034 If Partial Match Lists is enabled (it is enabled by default) you may type
8035 Ctrl-X to get a list of matches to the prefix you've typed in so far.
8036 <P>
8037 If the Ctrl-R subcommand is present that means you can decide to Delete or
8038 not Delete the message you are saving after you save it.
8039 The label on that key gives the action to switch to.
8040 If it says Delete and you type Ctrl-R the label displayed will change to
8041 No Delete and the source message will be deleted after the save. If it
8042 says No Delete and you type Ctrl-R the label displayed will change to
8043 Delete and the message will not be deleted.
8044 You can control the default for the Delete parameter with the
8045 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
8046 <P>
8047 Similarly, if the Ctrl-W subcommand is present that means you can decide
8048 to Preserve the order of the messages being saved or not.
8049 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
8050 will be in the same order as you see them in the source folder now.
8051 The opposite action (which is usually the default) is that you don't care
8052 about the order.
8053 The Saved messages may or may not be in the same order in the destination folder.
8054 There may be a performance penalty for choosing to save the messages in order.
8055 You can control the default for the Preserve Order parameter with the
8056 configuration feature
8057 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
8059 <P>
8060 If you haven't disabled the Save Input History and you've already done a
8061 Save earlier in this session then you may use the Up and Down arrows to retrieve
8062 a folder name used in a previous Save.
8064 <P>
8065 <End of help on this topic>
8066 </BODY>
8067 </HTML>
8068 ============= h_simple_index ========================
8069 <HTML>
8070 <HEAD>
8071 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
8072 </HEAD>
8073 <BODY>
8074 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
8075 <!--chtml if pinemode="function_key"-->
8076 <PRE>
8077 Navigating the List of Messages General Alpine Commands
8078 ------------------------------- -----------------------
8079 F5 Move to previous message F1 Show this help text
8080 F6 Move to next message
8081 F7 Show previous screen of messages
8082 F8 Show next screen of messages
8084 Message Selection Commands
8085 --------------------------
8086 F3 Exit the Message Select menu (canceling Send command)
8087 F4 Select the currently highlighted message
8088 F9 Mark the currently highlighted message as deleted
8089 F10 Undelete (remove deletion mark from) the highlighted message
8090 </PRE>
8091 <!--chtml else-->
8092 <PRE>
8093 Navigating the List of Messages General Alpine Commands
8094 ------------------------------- -----------------------
8095 P Move to previous message ? Show this help text
8096 N Move to next message
8097 - Show previous screen of messages
8098 Spc (space bar) Show next screen of messages
8100 Message Selection Commands
8101 --------------------------
8102 E Exit the Message Select menu (canceling Send command)
8103 S Select the currently highlighted message
8104 D Mark the currently highlighted message as deleted
8105 U Undelete (remove deletion mark from) the highlighted message
8106 </PRE>
8107 <!--chtml endif-->
8108 <P>
8109 <H2>Description of the Select Postponed Message Screen</H2>
8111 This screen allows you to select one of several previously postponed
8112 messages in order to continue composition. Your options are very limited
8113 -- the screen is not meant to let you manipulate these messages. However,
8114 you may now delete messages from this list. Once you choose a message,
8115 Alpine reads it in and puts you into the regular message composer.
8116 <P>
8118 Messages do not stay in this postponed state automatically. If you select
8119 a message and then want to postpone it again, use the normal postpone
8120 (Ctrl-O) command in the composer.
8121 <P>
8123 If you exit this screen without selecting a message, the Compose command
8124 that got you here is canceled. Other than messages explicitly marked
8125 "Deleted", no messages will be removed.
8127 <P>
8128 <End of help on this topic>
8129 </BODY>
8130 </HTML>
8131 ============= h_collection_screen ========================
8132 <HTML>
8133 <HEAD>
8134 <TITLE>COLLECTION LIST screen</TITLE>
8135 </HEAD>
8136 <BODY>
8137 <H1>COLLECTION LIST screen</H1>
8139 The COLLECTION LIST screen is used to select one of your
8140 collection definitions to display the folders they contain. See
8141 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
8142 detailed explanation of collections.<P>
8144 To manage your collection definitions (Add, Change, Delete, etc.), use
8145 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
8146 MAIN MENU.
8148 <P>
8149 <End of help on this topic>
8150 </BODY>
8151 </HTML>
8152 ============= h_collection_maint ========================
8153 <HTML>
8154 <HEAD>
8155 <TITLE>SETUP COLLECTION LIST screen</TITLE>
8156 </HEAD>
8157 <BODY>
8158 <H1>SETUP COLLECTION LIST screen</H1>
8160 The SETUP COLLECTION LIST screen lets you manage your collection
8161 definitions. See
8162 <A HREF="h_what_are_collections">Folder Collections Explained</A>
8163 for detailed explanation of collections.<P>
8165 Maintenance commands include:
8166 <DL>
8167 <DT>Change
8168 <!--chtml if pinemode="function_key"-->
8169 (F4)
8170 <!--chtml else-->
8171 (C)
8172 <!--chtml endif-->
8173 </DT>
8175 <DD>Modify attributes of the selected collection definition.
8177 <DT>Add Cltn
8178 <!--chtml if pinemode="function_key"-->
8179 (F9)
8180 <!--chtml else-->
8181 (A)
8182 <!--chtml endif-->
8183 </DT>
8185 <DD>Create a new collection definition.
8186 </DD>
8188 <DT>Del Cltn
8189 <!--chtml if pinemode="function_key"-->
8190 (F10)
8191 <!--chtml else-->
8192 (D)
8193 <!--chtml endif-->
8194 </DT>
8196 <DD>Delete the selected collection definition.<BR>
8197 NOTE: The folders and directories referred to by the
8198 collection definition are <EM>NOT</EM> deleted. Folders must
8199 be deleted, if that's what you wish to do, from the
8200 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
8201 individual folders in a collection.
8202 </DD>
8204 <DT>Shuffle
8205 <!--chtml if pinemode="function_key"-->
8206 (F11)
8207 <!--chtml else-->
8208 ($)
8209 <!--chtml endif-->
8210 </DT>
8212 <DD>Change the order of the displayed collections. Alpine will offer
8213 to move the currently selected collection one position UP
8214 or DOWN.
8215 </DD>
8216 </DL>
8218 <P>
8219 <End of help on this topic>
8220 </BODY>
8221 </HTML>
8222 ============ h_what_are_collections ==========
8223 <HTML>
8224 <HEAD>
8225 <TITLE>Folder Collections Explained</TITLE>
8226 </HEAD>
8227 <BODY>
8228 <H1>Folder Collections Explained</H1>
8231 Those of you with simple mail configurations will just see a list of all the
8232 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
8233 The special folders for INBOX, sent mail and saved messages
8234 will appear at the top of the list. All others are in alphabetical order.
8235 <P>
8236 If you
8237 or your system administrator have defined more than one collection or if
8238 you have a collection (for newsgroups or email folders) defined on your
8239 system, then you will see the COLLECTION LIST screen first when choosing
8240 FOLDER LIST from Alpine's MAIN MENU.
8241 <P>
8242 <H2>Why have multiple folder collections?</H2>
8243 <P>
8244 For Alpine users who only maintain email folders (and not too many) on one host,
8245 a single folder collection is probably sufficient.<P>
8247 However, people who have more than one email account - for example, one
8248 at their university, and one with their personal Internet Service Provider -
8249 will have different sets of folders on different hosts, and they may want to
8250 access them all from the same installation of Alpine, rather than use different
8251 software and/or log into other hosts to manipulate messages in different
8252 accounts. (If in doubt whether one of your email accounts can be accessed
8253 with Alpine, contact the technical support people for that account.) Even people
8254 who have only one email account on one host, but have dozens or
8255 hundreds of email folders, may want to arrange these folders together in a
8256 meaningful way.<BR>
8257 That is where multiple collections come in.
8259 <H2>Types of Collections</H2>
8260 <DL>
8261 <DT>INCOMING FOLDERS</DT>
8262 <DD>"Incoming Message Folders"
8263 is a special collection typically used to supplement your single INBOX.
8264 All the folders here are meant to be ones that receive incoming messages,
8265 which you intend to check more or less frequently.
8266 You may have multiple folders like this because you or your systems
8267 administrator have set up an external program or you may have set up
8268 Alpine to filter incoming
8269 messages into different folders, based on certain criteria such as
8270 sender, recipient, or subject; or because you have multiple accounts and
8271 wish to check their INBOXes easily. This collection is established by
8272 setting the
8273 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8274 feature in the SETUP CONFIGURATION screen, which is accessed from the
8275 MAIN MENU.
8276 </DD>
8278 <DT>NEWS</DT>
8279 <DD>You can also define a collection specifically for
8280 newsgroups. Alpine does this for you implicitly when you
8281 <A HREF="h_config_nntp_server">define an NNTP Server</A>
8282 in your Alpine configuration. The news collection appears last in the
8283 COLLECTION LIST (though you can shuffle it up in the order of presentation),
8284 and Alpine knows not to save messages there.
8285 </DD>
8287 <DT>DEFAULT COLLECTION</DT>
8288 <DD>This is the default collection for your saved and sent messages folders.
8289 </DD>
8290 </DL>
8292 <P>
8294 <H2>Defining Collections</H2>
8295 <P>
8296 In the absence of any folder-collection definitions, Alpine will assume a
8297 single default folder collection.
8298 <!--chtml if pinemode="os_windows"-->
8299 <!--chtml else-->
8300 If necessary, Alpine will create the directory
8301 "mail" in your Unix home directory
8302 to hold your folders.
8303 <!--chtml endif-->
8304 <P>
8305 You can use the
8306 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
8307 the MAIN MENU, to manage your collection list.
8308 <P>
8309 <End of help on this topic>
8310 </BODY>
8311 </HTML>
8312 ===== h_select_address_screen =====
8313 <HTML>
8314 <HEAD>
8315 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
8316 </HEAD>
8317 <BODY>
8318 <H1>SELECT AN ADDRESS SCREEN</H1>
8319 <H2>COMMANDS</H2>
8320 <!--chtml if pinemode="function_key"-->
8321 <PRE>
8322 Available Commands
8323 -------------------------------
8324 F1 Show Help Text
8325 F3 Exit without selecting anything
8326 F4 Select the highlighted address
8327 F5 Move highlight to previous address
8328 F6 Move highlight to next address
8329 F7 Previous page of addresses
8330 F8 Next page of addresses
8331 F11 Print
8332 F12 WhereIs
8333 </PRE>
8334 <!--chtml else-->
8335 <PRE>
8336 Navigation General Alpine Commands
8337 ------------------------- -----------------------
8338 P Prev Address ? Display this help text
8339 N Next Address E Exit without selecting anything
8340 - Previous page % Print
8341 Spc (space bar) Next page
8342 W WhereIs
8344 Select Command
8345 ------------------------------------------------
8346 S Select the highlighted address
8347 </PRE>
8348 <!--chtml endif-->
8350 <H2>Description of the Select Address Screen</H2>
8352 This screen gives you an easy way to select an address from all of
8353 the address book entries that match the prefix typed so far.
8355 <P><UL>
8356 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8357 </UL>
8358 <P>
8359 <End of help on this topic>
8360 </BODY>
8361 </HTML>
8362 ===== h_select_rule_screen =====
8363 <HTML>
8364 <HEAD>
8365 <TITLE>SELECT A RULE SCREEN</TITLE>
8366 </HEAD>
8367 <BODY>
8368 <H1>SELECT A RULE SCREEN</H1>
8369 <H2>COMMANDS</H2>
8370 <!--chtml if pinemode="function_key"-->
8371 <PRE>
8372 Available Commands
8373 -------------------------------
8374 F1 Show Help Text
8375 F3 Exit without selecting anything
8376 F4 Select the highlighted rule
8377 F5 Move highlight to previous rule
8378 F6 Move highlight to next rule
8379 F7 Previous page of rules
8380 F8 Next page of rules
8381 F11 Print
8382 F12 WhereIs
8383 </PRE>
8384 <!--chtml else-->
8385 <PRE>
8386 Navigation General Alpine Commands
8387 ------------------------- -----------------------
8388 P Prev Rule ? Display this help text
8389 N Next Rule E Exit without selecting anything
8390 - Previous page % Print
8391 Spc (space bar) Next page
8392 W WhereIs
8394 Select Command
8395 ------------------------------------------------
8396 S Select the highlighted rule
8397 </PRE>
8398 <!--chtml endif-->
8400 <H2>Description of the Select Rule Screen</H2>
8402 This screen just gives you an easy way to select a rule from all of your
8403 defined rules.
8404 The list of rules presented is the list of nicknames of all of the rules
8405 defined using Setup/Rules.
8406 For selecting messages, it is likely that the Indexcolor rules and possibly
8407 the Roles rules will be most useful.
8408 The others are there also, in case you find a use for them.
8409 <P>
8410 In order for this to be useful for selecting messages, the nicknames of
8411 the rules have to be different.
8412 Alpine actually just gets the nickname of the rule that you select and then
8413 looks up that rule using the nickname.
8414 So if there are duplicate nicknames, the first rule that has that
8415 nickname will be used.
8417 <P><UL>
8418 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8419 </UL>
8420 <P>
8421 <End of help on this topic>
8422 </BODY>
8423 </HTML>
8424 ===== h_select_priority_screen =====
8425 <HTML>
8426 <HEAD>
8427 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8428 </HEAD>
8429 <BODY>
8430 <H1>SELECT A PRIORITY SCREEN</H1>
8431 <H2>COMMANDS</H2>
8432 <!--chtml if pinemode="function_key"-->
8433 <PRE>
8434 Available Commands
8435 -------------------------------
8436 F1 Show Help Text
8437 F3 Exit without selecting anything
8438 F4 Select the highlighted priority
8439 F5 Move highlight to previous priority
8440 F6 Move highlight to next priority
8441 F7 Previous page of priorities
8442 F8 Next page of priorities
8443 F11 Print
8444 F12 WhereIs
8445 </PRE>
8446 <!--chtml else-->
8447 <PRE>
8448 Navigation General Alpine Commands
8449 ------------------------- -----------------------
8450 P Prev Priority ? Display this help text
8451 N Next Priority E Exit without selecting anything
8452 - Previous page % Print
8453 Spc (space bar) Next page
8454 W WhereIs
8456 Select Command
8457 ------------------------------------------------
8458 S Select the highlighted priority
8459 </PRE>
8460 <!--chtml endif-->
8462 <H2>Description of the Select Priority Screen</H2>
8464 This screen gives you a way to select a priority for the message you are sending.
8465 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8466 Some mail programs will display an indication of the priority level to
8467 the recipient of the message, some will ignore it.
8468 Even in cases where the mail programs of both the sender and the recipient
8469 agree on the meaning of this header, keep in mind that it is
8470 something that the sender sets so it is only an indication
8471 of the priority that the sender attaches to the mail.
8472 Alpine can be made to display an indication of this priority in incoming
8473 messages by use of one of the tokens
8474 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8475 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8476 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8478 <P><UL>
8479 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8480 </UL>
8481 <P>
8482 <End of help on this topic>
8483 </BODY>
8484 </HTML>
8485 ===== h_select_keyword_screen =====
8486 <HTML>
8487 <HEAD>
8488 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8489 </HEAD>
8490 <BODY>
8491 <H1>SELECT A KEYWORD SCREEN</H1>
8492 <H2>COMMANDS</H2>
8493 <!--chtml if pinemode="function_key"-->
8494 <PRE>
8495 Available Commands
8496 -------------------------------
8497 F1 Show Help Text
8498 F3 Exit without selecting anything
8499 F4 Select the highlighted keyword
8500 F5 Move highlight to previous keyword
8501 F6 Move highlight to next keyword
8502 F7 Previous page of keywords
8503 F8 Next page of keywords
8504 F11 Print
8505 F12 WhereIs
8506 </PRE>
8507 <!--chtml else-->
8508 <PRE>
8509 Navigation General Alpine Commands
8510 ------------------------- -----------------------
8511 P Prev Keyword ? Display this help text
8512 N Next Keyword E Exit without selecting anything
8513 - Previous page % Print
8514 Spc (space bar) Next page
8515 W WhereIs
8517 Select Command
8518 ------------------------------------------------
8519 S Select the highlighted keyword
8520 </PRE>
8521 <!--chtml endif-->
8523 <H2>Description of the Select Keyword Screen</H2>
8525 This screen just gives you an easy way to select a keyword.
8526 The list of keywords presented is the list of all keywords defined in your
8527 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8528 If you have given a keyword a nickname, that nickname is displayed
8529 instead of the actual keyword.
8531 <P><UL>
8532 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8533 </UL>
8534 <P>
8535 <End of help on this topic>
8536 </BODY>
8537 </HTML>
8538 ===== h_select_charset_screen =====
8539 <HTML>
8540 <HEAD>
8541 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8542 </HEAD>
8543 <BODY>
8544 <H1>SELECT A CHARACTER SET SCREEN</H1>
8545 <H2>COMMANDS</H2>
8546 <!--chtml if pinemode="function_key"-->
8547 <PRE>
8548 Available Commands
8549 -------------------------------
8550 F1 Show Help Text
8551 F3 Exit without selecting anything
8552 F4 Select the highlighted character set
8553 F5 Move highlight to previous character set
8554 F6 Move highlight to next character set
8555 F7 Previous page of character sets
8556 F8 Next page of character sets
8557 F11 Print
8558 F12 WhereIs
8559 </PRE>
8560 <!--chtml else-->
8561 <PRE>
8562 Navigation General Alpine Commands
8563 ------------------------- -----------------------
8564 P Prev Character Set ? Display this help text
8565 N Next Character Set E Exit without selecting anything
8566 - Previous page % Print
8567 Spc (space bar) Next page
8568 W WhereIs
8570 Select Command
8571 ------------------------------------------------
8572 S Select the highlighted character set
8573 </PRE>
8574 <!--chtml endif-->
8576 <H2>Description of the Select A Character Set Screen</H2>
8578 This screen just gives you an easy way to select a character set from the
8579 set of character sets Alpine knows about.
8580 The list presented will vary slightly depending on what option you are
8581 selecting the character set for.
8583 <P><UL>
8584 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8585 </UL>
8586 <P>
8587 <End of help on this topic>
8588 </BODY>
8589 </HTML>
8590 ===== h_select_multcharsets_screen =====
8591 <HTML>
8592 <HEAD>
8593 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8594 </HEAD>
8595 <BODY>
8596 <H1>SELECT CHARACTER SETS SCREEN</H1>
8597 <H2>COMMANDS</H2>
8598 <!--chtml if pinemode="function_key"-->
8599 <PRE>
8600 Available Commands
8601 -------------------------------
8602 F1 Show Help Text
8603 F3 Exit without selecting anything
8604 F4 Select the highlighted charset (or chosen charsets in ListMode)
8605 F5 Move highlight to previous charset
8606 F6 Move highlight to next charset
8607 F7 Previous page of charsets
8608 F8 Next page of charsets
8609 F9 Toggle choices when using ListMode
8610 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8611 F11 Print
8612 F12 WhereIs
8613 </PRE>
8614 <!--chtml else-->
8615 <PRE>
8616 Navigation General Alpine Commands
8617 ------------------------- -----------------------
8618 P Prev Charset ? Display this help text
8619 N Next Charset E Exit without selecting anything
8620 - Previous page % Print
8621 Spc (space bar) Next page
8622 W WhereIs
8624 Select Command
8625 ------------------------------------------------
8626 S Select the highlighted charset (or chosen charsets in ListMode)
8627 L Turn on ListMode (makes it easy to choose multiple charsets)
8628 1 Turn off ListMode
8629 X Toggle choices when using ListMode
8630 </PRE>
8631 <!--chtml endif-->
8633 <H2>Description of the Select Character Set Screen</H2>
8635 This screen just gives you an easy way to select a character set or a list of
8636 character sets.
8637 The list of character sets presented is the list of all character sets known to
8638 Alpine.
8639 You may select other character sets by typing them in directly.
8641 <P><UL>
8642 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8643 </UL>
8644 <P>
8645 <End of help on this topic>
8646 </BODY>
8647 </HTML>
8648 ===== h_select_multkeyword_screen =====
8649 <HTML>
8650 <HEAD>
8651 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8652 </HEAD>
8653 <BODY>
8654 <H1>SELECT KEYWORDS SCREEN</H1>
8655 <H2>COMMANDS</H2>
8656 <!--chtml if pinemode="function_key"-->
8657 <PRE>
8658 Available Commands
8659 -------------------------------
8660 F1 Show Help Text
8661 F3 Exit without selecting anything
8662 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8663 F5 Move highlight to previous keyword
8664 F6 Move highlight to next keyword
8665 F7 Previous page of keywords
8666 F8 Next page of keywords
8667 F9 Toggle choices when using ListMode
8668 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8669 F11 Print
8670 F12 WhereIs
8671 </PRE>
8672 <!--chtml else-->
8673 <PRE>
8674 Navigation General Alpine Commands
8675 ------------------------- -----------------------
8676 P Prev Keyword ? Display this help text
8677 N Next Keyword E Exit without selecting anything
8678 - Previous page % Print
8679 Spc (space bar) Next page
8680 W WhereIs
8682 Select Command
8683 ------------------------------------------------
8684 S Select the highlighted keyword (or chosen keywords in ListMode)
8685 L Turn on ListMode (makes it easy to choose multiple keywords)
8686 1 Turn off ListMode
8687 X Toggle choices when using ListMode
8688 </PRE>
8689 <!--chtml endif-->
8691 <H2>Description of the Select Keyword Screen</H2>
8693 This screen just gives you an easy way to select a keyword or a list of
8694 keywords.
8695 The list of keywords presented is the list of all keywords defined in your
8696 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8697 If you have given a keyword a nickname, that nickname is displayed
8698 instead of the actual keyword.
8700 <P><UL>
8701 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8702 </UL>
8703 <P>
8704 <End of help on this topic>
8705 </BODY>
8706 </HTML>
8707 ===== h_select_incoming_to_monitor =====
8708 <HTML>
8709 <HEAD>
8710 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8711 </HEAD>
8712 <BODY>
8713 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8714 <H2>COMMANDS</H2>
8715 <!--chtml if pinemode="function_key"-->
8716 <PRE>
8717 Available Commands
8718 -------------------------------
8719 F1 Show Help Text
8720 F3 Exit without selecting anything
8721 F4 Select the marked folders
8722 F5 Move highlight to previous folder
8723 F6 Move highlight to next folder
8724 F7 Previous page of folders
8725 F8 Next page of folders
8726 F9 Toggle choices on or off
8727 F11 Print
8728 F12 WhereIs
8729 </PRE>
8730 <!--chtml else-->
8731 <PRE>
8732 Navigation General Alpine Commands
8733 ------------------------- -----------------------
8734 P Prev Folder ? Display this help text
8735 N Next Folder ^C exit without changing anything
8736 - Previous page % Print
8737 Spc (space bar) Next page
8738 W WhereIs
8740 Select Command
8741 ------------------------------------------------
8742 S Select the marked folders
8743 X Toggle choices on or off
8744 </PRE>
8745 <!--chtml endif-->
8747 <H2>Description of the Select Folders to Check Screen</H2>
8749 This screen is only useful if the feature
8750 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
8751 is set.
8752 By default, when you set that feature all of your incoming folders
8753 will be checked periodically for Unseen messages.
8754 By using this screen, you may restrict the set of monitored folders to
8755 a subset of all of the incoming folders.
8756 <P>
8757 Mark the folders you want to monitor for Unseen messages with
8758 an "X".
8759 When you've finished marking all your selections use the Select
8760 command to register your choices.
8761 To return to the default of checking all incoming folders
8762 delete all folders or unmark all folders.
8764 <P><UL>
8765 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8766 </UL>
8767 <P>
8768 <End of help on this topic>
8769 </BODY>
8770 </HTML>
8771 ===== h_role_select =====
8772 <HTML>
8773 <HEAD>
8774 <TITLE>ROLES SCREEN</TITLE>
8775 </HEAD>
8776 <BODY>
8777 <H1>ROLES SCREEN</H1>
8778 <H2>ROLES COMMANDS</H2>
8779 <!--chtml if pinemode="function_key"-->
8780 <PRE>
8781 Available Commands
8782 -------------------------------
8783 F1 Show Help Text
8784 F3 Exit without a selection
8785 F4 Select a role to use in composition
8786 F5 Move to previous role
8787 F6 Move to next role
8788 F7 Previous page of roles
8789 F8 Next page of roles
8790 F11 Change Default Role
8791 F12 Whereis (search role nicknames)
8792 </PRE>
8793 <!--chtml else-->
8794 <PRE>
8795 Navigation General Alpine Commands
8796 ------------------------- -----------------------
8797 P Prev Role ? Display this help text
8798 N Next Role E Exit without a selection
8799 - Previous page
8800 Spc (space bar) Next page
8801 W WhereIs (search for word in role nicknames)
8803 Select Role Commands
8804 ------------------------------------------------
8805 [Return] Select highlighted role
8806 D Change Default Role
8807 </PRE>
8808 <!--chtml endif-->
8810 <H2>Description of the Roles Screen</H2>
8812 With this screen you select a role to be used in the composition of a
8813 message.
8814 Use the Previous and Next commands to highlight the role you wish to
8815 use.
8816 When you type carriage return you will be placed in the composer using the highlighted role.
8817 <P>
8818 You don't have any non-default <A HREF="h_rules_roles">roles</A>
8819 available unless you set them up.
8820 You may do so by using the Setup/Rules command on the MAIN MENU.
8821 <P>
8822 By using the D command, you may set a default role that will persist until
8823 you change it or until you exit Alpine.
8824 The D command toggles through three states: set the default role, unset the
8825 default role, and leave the default role as it is.
8826 <P><UL>
8827 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8828 </UL>
8829 <P>
8830 <End of help on this topic>
8831 </BODY>
8832 </HTML>
8833 ===== h_role_abook_select =====
8834 <HTML>
8835 <HEAD>
8836 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
8837 </HEAD>
8838 <BODY>
8839 <H1>SELECT ADDRESS BOOK SCREEN</H1>
8840 <H2>COMMANDS</H2>
8841 <!--chtml if pinemode="function_key"-->
8842 <PRE>
8843 Available Commands
8844 -------------------------------
8845 F1 Show Help Text
8846 F3 Exit screen without selecting anything
8847 F4 Select highlighted address book
8848 F5 Move to previous address book
8849 F6 Move to next address book
8850 F7 Previous page of address books
8851 F8 Next page of address books
8852 F12 Whereis
8853 </PRE>
8854 <!--chtml else-->
8855 <PRE>
8856 Navigation General Alpine Commands
8857 ------------------------- -----------------------
8858 P Previous addrbook ? Display this help text
8859 N Next addrbook
8860 - Previous page
8861 Spc (space bar) Next page
8862 W WhereIs
8864 Select Role Commands
8865 ------------------------------------------------
8866 S Select highlighted address book
8867 E Exit screen without selecting anything
8868 </PRE>
8869 <!--chtml endif-->
8871 <H2>Description of the Select Address Book Screen</H2>
8873 This screen helps you select one of your address books.
8874 Use the Previous and Next commands to highlight the address book you wish to
8875 select.
8876 <P><UL>
8877 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8878 </UL>
8879 <P>
8880 <End of help on this topic>
8881 </BODY>
8882 </HTML>
8883 ======== h_rule_patterns =============
8884 <HTML>
8885 <HEAD>
8886 <TITLE>PATTERNS</TITLE>
8887 </HEAD>
8888 <BODY>
8889 <H1>PATTERNS</H1>
8890 Patterns are used with Roles, Filtering, Index Coloring,
8891 Scoring, Other Rules, and Search Rules.
8892 Patterns are compared with a message to see if there is a match.
8893 For Filtering, the messages being checked are all the messages in the
8894 folder, one at a time.
8895 For Index Line Coloring, each message that is visible on the screen is
8896 checked for matches with the Index Coloring Patterns.
8897 Roles are used with the Reply, Forward, and Compose commands.
8898 For Reply, the message used to compare the Pattern with is the message
8899 being replied to;
8900 for Forward, the message used to compare the Pattern with is the message
8901 being forwarded;
8902 and for Compose, there is no message, so the parts of the Pattern that depend
8903 on a message (everything other than Current Folder Type and the
8904 Beginning of Month and Year)
8905 are not used.
8906 Only the Current Folder Type matters for Compose (plus the Beginning of
8907 Month or Year, which you wouldn't usually use for a Role).
8908 For Scoring, the message being scored is compared with all of the Score
8909 Patterns, and the Score Values from the ones that match are added together to
8910 get the message's score.
8911 For Other Rules, there is no message. Only the Current Folder Type is checked
8912 for Other Rules.
8913 <P>
8914 Each Pattern has several possible parts, all of which are optional.
8915 In order for there to be a match, <EM>ALL</EM> of the
8916 <EM>defined</EM> parts of the Pattern must match the message.
8917 If a part is not defined it is considered a match, but note that a filtering
8918 Pattern must have at least one defined part or it will be ignored.
8919 For example, if the To pattern is not defined it will be
8920 displayed as
8921 <P>
8922 <CENTER>To pattern = <No Value Set></CENTER>
8923 <P>
8924 That is considered a match because it is not defined.
8925 This means that the Pattern with nothing defined is a match if the
8926 Current Folder Type matches, but there is an exception that was mentioned
8927 in the previous paragraph.
8928 Because filtering is a potentially destructive action, filtering Patterns
8929 with nothing other than Current Folder Type defined are ignored.
8930 If you really want a filtering Pattern to match all messages (subject to
8931 Current Folder Type) the best way to do it is to define a Score interval
8932 that includes all possible scores.
8933 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
8934 This can be used even if you haven't defined any rules to Set Scores.
8935 <P>
8936 There are six predefined header patterns called the To, From, Sender, Cc, News,
8937 and Subject patterns.
8938 Besides those six predefined header patterns, you may add
8939 additional header patterns with header fieldnames of your choosing.
8940 You add an extra header pattern by placing the cursor on one of the
8941 patterns while in the role editor and using the "eXtraHdr" command.
8942 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
8943 and the Partic pattern is a header pattern that stands for
8944 Participant (From OR To OR Cc).
8945 (Defining the Recip pattern does not have the same effect as defining both
8946 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
8947 Similar to the header patterns are the AllText pattern and the BodyText pattern.
8948 Instead of comparing this pattern's text against only the contents of
8949 a particular header field, the text for the AllText pattern is compared
8950 with text anywhere in the message's header or body, and the text for the
8951 BodyText pattern is compared with text anywhere in the message's body.
8952 <P>
8953 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
8954 "!" "toggle NOT" command.
8955 You can tell that <EM>NOT</EM> has been turned on by looking for the character
8956 "!" at the beginning of the pattern line.
8957 When the "!" is present, it reverses the meaning of the match.
8958 That is, if the pattern matches then it is considered to NOT be a match, and
8959 if it does not match it is considered to be a match.
8960 <P>
8961 Don't make the mistake of putting the "!" in the data field for
8962 a pattern.
8963 For example, if you type the characters "!urgent" into the Subject
8964 pattern, the pattern will look like:
8965 <P>
8966 <PRE>
8967 Subject pattern = !urgent
8968 </PRE>
8969 <P>
8970 This means you want to match the 7 character sequence "!urgent".
8971 In order to match messages that do not have "urgent" in
8972 their Subject field, first type the characters "urgent" followed
8973 by carriage return for the value of the Subject pattern, then negate it
8974 by typing the "!" command.
8975 It should look like
8976 <P>
8977 <PRE>
8978 ! Subject pattern = urgent
8979 </PRE>
8980 <P>
8981 The contents of each of these header patterns (or the AllText or BodyText patterns) may
8982 be a complete email address, part of an address, or a random set of
8983 characters to match against.
8984 It may also be a list of such patterns, which means you
8985 are looking for a match against the first pattern in the list <EM>OR</EM>
8986 the second pattern <EM>OR</EM> the third and so on.
8987 For example, a Subject pattern equal to
8988 <P>
8989 <PRE>
8990 Subject pattern = urgent
8991 emergency
8992 alert
8993 </PRE>
8994 <P>
8995 would match all messages with a subject that contained at least one
8996 of those words.
8997 It would also match subjects containing the words "alerts" or
8998 "Urgently".
8999 <P>
9000 The same example with "NOT" turned on would be
9001 <P>
9002 <PRE>
9003 ! Subject pattern = urgent
9004 emergency
9005 alert
9006 </PRE>
9007 <P>
9008 which would match all messages with a subject that did <EM>NOT</EM> contain any of
9009 those words.
9010 You can use the "Add Value" command to add new words to the list,
9011 or you can enter them as a comma-separated list.
9012 <P>
9013 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
9014 present for a match.
9015 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
9016 pattern2 must be present,
9017 and that is exactly what using a list does.)
9018 <P>
9019 The "Current Folder Type" and the "Score Interval" are
9020 also part of the Pattern, although the "Score Interval" is not used
9021 when checking for matches for Scoring.
9022 There are five similar settings that relate to the status of the message.
9023 These settings rely on the message being New or not, Deleted or not,
9024 Answered or not, Important or not, and Recent or not.
9025 There are also some other miscellaneous settings.
9026 The first is the Age of the message in days.
9027 Another is the Size of the message, in bytes.
9028 The third is a setting that detects whether or not the Subject of a
9029 message contains raw 8-bit characters (unencoded characters with the most
9030 significant bit set).
9031 There is a setting that detects whether or not this is the first time
9032 Alpine has been run this month (doesn't depend on individual messages),
9033 and another that detects whether or not this is the first time Alpine has
9034 been run this year.
9035 Other parts of the Pattern detect whether or not the From address of a
9036 message appears in your address book, whether or not certain keywords
9037 are set for a message, and whether or not certain character sets are
9038 used in a message.
9040 <H2>Parts of a Pattern</H2>
9042 <H3>Header patterns</H3>
9044 A header pattern is simply text that is searched for in the corresponding
9045 header field.
9046 For example, if a Pattern has a From header pattern with the value
9047 "@company.com", then only messages that have a From header
9048 that contains the text "@company.com" will be possible
9049 matches.
9050 Matches don't have to be exact.
9051 For example, if the relevant field of a message contains the text
9052 "mailbox@domain" somewhere
9053 in it, then header patterns of "box", or "x@d", or
9054 "mailbox@domain" are all matches.
9055 <P>
9056 All parts of the Pattern must match so, for example,
9057 if a message matches a defined
9058 From pattern, it still must be checked against the other parts of the
9059 Pattern that have been defined.
9060 The To header pattern is a slightly special case.
9061 If the message being checked has a Resent-To header
9062 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
9063 there are used in place of the addresses in the To header.
9064 This is only true for the To header.
9065 Resent-cc and Resent-From headers are never used unless you add them
9066 with the eXtraHdrs command.
9067 <P>
9068 The meaning of a header pattern may be negated with the
9069 "!" "toggle NOT" command.
9070 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9071 "!" at the beginning of the pattern line.
9072 It would look something like
9073 <P>
9074 <PRE>
9075 ! From pattern = susan@example.com
9076 </PRE>
9077 <P>
9078 When the "!" is present, it reverses the meaning of the match.
9079 <P>
9080 If you want to check for the presence of a header field but don't care
9081 about its value, then
9082 the empty pattern that you get by entering a pair of
9083 double quotes ("") should match any message that
9084 has the corresponding header field.
9086 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
9088 AllText patterns are just like header patterns except that the text is
9089 searched for anywhere in the message's headers or body, not just in the
9090 contents of a particular header field.
9091 <P>
9093 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
9095 BodyText patterns are just like header patterns except that the text is
9096 searched for anywhere in the message's body, not just in the
9097 contents of a particular header field.
9098 <P>
9100 If there is more than one header pattern or AllText pattern or BodyText pattern
9101 for which you want to take the
9102 same action there is a shorthand notation that may be used.
9103 Any of these patterns may be a list of patterns instead of
9104 just a single pattern.
9105 If any one of the patterns in the list matches the message
9106 then it is considered a match.
9107 For example, if "company1" and "company2" both required
9108 you to use the same role when replying to messages, you might have
9109 a To pattern that looks like
9110 <P>
9111 <PRE>
9112 To pattern = company1.com
9113 company2.com
9114 </PRE>
9115 <P>
9116 This means that if the mail you are replying to was addressed to
9117 either "anything@company1.com" or "anything@company2.com",
9118 then this Pattern is a match and the same actions will be taken.
9119 <P>
9120 The meaning of an AllText or BodyText pattern may be negated with the
9121 "!" "toggle NOT" command.
9122 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9123 "!" at the beginning of the pattern line.
9124 When the "!" is present, it reverses the meaning of the match.
9125 <P>
9126 A technicality: Since comma is the character used to separate multiple values
9127 in any of the fields that may have multiple values (such as header patterns,
9128 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
9129 you must escape comma with a
9130 backslash (\) if you want to include a literal comma in one of those fields.
9131 In other words, if you type a backslash followed by a comma it will
9132 be interpreted as a comma by Alpine, instead of as a separator between
9133 pattern values.
9134 All other backslashes (those not followed by a comma) are literal
9135 backslashes and should not be escaped.
9136 It's unlikely you'll ever need to enter a literal comma or backslash in
9137 any of the patterns.
9139 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
9141 The "Current Folder Type" may be set to one of four different
9142 values: "Any", "News", "Email", or
9143 "Specific".
9144 If the value is set to "News", then the
9145 Pattern will only match if the currently open folder is a newsgroup.
9146 The value "Email" only matches if the current folder is not news and
9147 the value "Any" causes any folder to match.
9148 If the value of "Current Folder Type" is set to "Specific",
9149 then you must fill in a value for "Folder", which is on the line
9150 below the "Specific" line.
9151 In this case you will only get a match if the currently open folder is
9152 the specific folder you list.
9153 You may give a list of folders instead of just a single
9154 folder name, in which case the Pattern will match if the open folder is
9155 any one of the folders in the list.
9156 The name of each folder in the list may be either "INBOX",
9157 the technical specification
9158 of the folder (like what appears in your configuration file) or, if the
9159 folder is one of your incoming folders, it may be the nickname you've given
9160 the folder.
9161 Here are some samples of specific folder names:
9162 <P>
9163 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
9164 <P>
9165 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
9166 <P>
9167 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
9168 <P>
9169 The easiest way to fill in the "Folder" field is to use
9170 the "T" command that is available when the "Folder" line is
9171 highlighted, or to use the "Take" command with the configuration
9172 feature
9173 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
9174 turned on.
9175 <P>
9176 When reading a newsgroup, there may be a performance penalty
9177 incurred when collecting the information necessary to check whether
9178 or not a Pattern matches a message.
9179 For this reason, the default Current Folder Type is set to "Email".
9180 If you have Patterns with a Current Folder Type of either
9181 "Any" or "News" and those Patterns are used for
9182 Index Line Coloring or Scoring, you may experience
9183 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
9185 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
9187 The "Age Interval" may be set to an interval of message
9188 ages that should be considered a match.
9189 Like the other parts of the Pattern, if it is unset it will be ignored.
9190 The Age Interval looks like
9191 <P>
9192 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
9193 <P>
9194 where "min_age" and "max_age" are integers greater
9195 than or equal to zero.
9196 The special value "INF" may be used for
9197 the max value. It represents infinity.
9198 <P>
9199 Actually, this option may be defined as a list of intervals instead
9200 of just a single interval.
9201 The list is separated by commas.
9202 It can look like
9203 <P>
9204 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
9205 <P>
9206 When there is an Age Interval defined, it is a match if the age, in days, of
9207 the message is contained in any of the intervals.
9208 The intervals include both endpoints.
9209 <P>
9210 Even though this option is called Age, it isn't actually
9211 the <EM>age</EM> of the message.
9212 Instead, it is how many days ago the message arrived in one of your folders.
9213 If the current time is a little past midnight, then a message that arrived
9214 just before midnight arrived yesterday, even though the message is only
9215 a few minutes old.
9216 By default, the date being used is not the date in the Date
9217 header of the message.
9218 It is the date that the message arrived in one of your folders.
9219 When you Save a message from one folder to another that arrival date
9220 is preserved.
9221 If you would like to use the date in the Date header that is possible.
9222 Turn on the option
9223 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
9224 near the bottom of the rule definition.
9225 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
9227 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
9229 The "Size Interval" may be set to an interval of message
9230 sizes that should be considered a match.
9231 Like the other parts of the Pattern, if it is unset it will be ignored.
9232 The Size Interval looks like
9233 <P>
9234 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
9235 <P>
9236 where "min_size" and "max_size" are integers greater
9237 than or equal to zero.
9238 The special value "INF" may be used for
9239 the max value. It represents infinity.
9240 <P>
9241 Actually, this option may be defined as a list of intervals instead
9242 of just a single interval.
9243 The list is separated by commas.
9244 It can look like
9245 <P>
9246 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
9247 <P>
9248 When there is a Size Interval defined, it is a match if the size, in bytes, of
9249 the message is contained in any of the intervals.
9250 The intervals include both endpoints.
9252 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
9254 The "Score Interval" may be set to an interval of message
9255 scores that should be considered a match.
9256 Like the other parts of the Pattern, if it is unset it will be ignored.
9257 The Score Interval looks like
9258 <P>
9259 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
9260 <P>
9261 where "min_score" and "max_score" are positive or
9262 negative integers, with min_score less than or equal to max_score.
9263 The special values "-INF" and "INF" may be used for
9264 the min and max values to represent negative and positive infinity.
9265 <P>
9266 Actually, a list of intervals may be used if you wish.
9267 A list would look like
9268 <P>
9269 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
9270 <P>
9271 When there is a Score Interval defined, it is a match if the score for
9272 the message is contained in any of the intervals in the list.
9273 The intervals include the endpoints.
9274 The score for a message is calculated by looking at every Score rule defined and
9275 adding up the Score Values for the ones that match the message.
9276 When deciding whether or not a Pattern matches a message for purposes of
9277 calculating the score, the Score Interval is ignored.
9279 <H3><A NAME="pattern_message_status">Message Status</A></H3>
9281 There are five separate message status settings.
9282 By default, all five are set to the value "Don't care", which
9283 will match any message.
9284 The value "Yes" means that the particular status must be true
9285 for a match, and the value "No" means that the particular
9286 status must not be true for a match.
9287 For example, one of the five Message Status settings is whether a message
9288 is marked Important or not.
9289 A "Yes" means that the message must be Important to be
9290 considered a match and "No" means that the message must not be
9291 Important to be considered a match.
9292 The same is true of the other four message status settings that depend
9293 on whether or not the message is New; whether the message has
9294 been Answered or not; whether the message has been Deleted or not, and
9295 whether the message is Recent or not.
9296 <P>
9297 The nomenclature for New and Recent is a bit confusing:
9298 <P>
9299 New means that the message is Unseen.
9300 It could have been in your mailbox for a long time but if you haven't looked
9301 at it, it is still considered New.
9302 That matches the default Alpine index display that shows an N for such a
9303 message.
9304 <P>
9305 Recent means that the message was added to this folder since the last time
9306 you opened the folder.
9307 Alpine also shows an N by default for these types of messages.
9308 If you were to run two copies of Alpine that opened a folder one right after
9309 the other, a message would only show up as Recent in (at most) the first
9310 Alpine session.
9312 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
9314 Keywords are similar to Message Status, but they are chosen by the user.
9315 Provided the mail server allows for it, you may add a set of possible keywords
9316 to a folder and then you may set those keywords or not for each message
9317 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
9318 The syntax of this part of the Pattern is similar to the header patterns.
9319 It is a list of keywords.
9320 The Keyword part of the Pattern is a match if the message has any of
9321 the keywords in the list set.
9322 Like other parts of the Pattern, if this is unset it will be ignored.
9324 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
9326 A message may use one or more character sets.
9327 This part of the Pattern matches messages that make use of one or more of
9328 the character sets specified in the pattern.
9329 It will be considered a match if a message uses any of the character
9330 sets in the list you give here.
9332 <P>
9333 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
9334 GB2312) you may also use some shorthand names that Alpine provides.
9335 These names are more understandable shorthand names for sets of
9336 character set names.
9337 Two examples are "Cyrillic" and "Greek".
9338 Selecting one of these shorthand names is equivalent to selecting all of
9339 the character sets that make up the set.
9340 You can see all of these shorthand names and the lists of character sets
9341 they stand for by typing the "T" command with the Character
9342 Set pattern highlighted.
9343 The syntax of this part of the Pattern is similar to the header patterns
9344 and the Message Keywords pattern.
9345 It is a list of character sets (or shorthand names).
9346 The Character Set part of the Pattern is a match if the message uses any
9347 of the character sets in the list.
9348 Like other parts of the Pattern, if this is unset it will be ignored.
9350 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
9352 It seems that lots of unwanted email contains unencoded 8-bit characters
9353 in the Subject.
9354 Normally, characters with the 8th bit set are not allowed in the Subject
9355 header unless they are MIME-encoded.
9356 This option gives you a way to match messages that have Subjects that
9357 contain unencoded 8-bit characters.
9358 By default, the value of this option is "Don't care", which
9359 will match any message.
9360 The value "Yes" means that there must be raw 8-bit characters in
9361 the Subject of the message in order for there to be a match,
9362 and the value "No" is the opposite.
9363 Setting this option will affect performance in large folders because the
9364 subject of each message in the folder has to be checked.
9366 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
9368 This option gives you a way to take some action once per month.
9369 By default, the value of this option is "Don't care", which
9370 will always match.
9371 The value "Yes" means that this must be the first time Alpine has
9372 been run this month in order to count as a match,
9373 and the value "No" is the opposite.
9375 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
9377 This option gives you a way to take some action once per year.
9378 By default, the value of this option is "Don't care", which
9379 will always match.
9380 The value "Yes" means that this must be the first time Alpine has
9381 been run this year in order to count as a match,
9382 and the value "No" is the opposite.
9384 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9386 This option gives you a way to match messages that have an address
9387 that is in one of your address books.
9388 Only the simple entries in your address books are searched.
9389 Address book distribution lists are ignored!
9390 By default, the value of this option is "Don't care", which
9391 will match any message.
9392 The value "Yes, in any address book" means the address
9393 from the message must be in at least one of your
9394 address books in order to be a match.
9395 The value "No, not in any address book"
9396 means none of the addresses may
9397 be in any of your address books in order to be a match.
9398 The values "Yes, in specific address books" and
9399 "No, not in any of specific address books" are similar but instead
9400 of depending on all address books you are allowed to give a list of address
9401 books to look in.
9402 The addresses from the message that are checked for are determined by the
9403 setting you have for "Types of addresses to check for in address book".
9404 If you set this to "From" the From address from the message will
9405 be looked up in the address book.
9406 If you set it to only "To" then the To addresses will be used.
9407 If any of the To addresses are in the address book then it is considered
9408 a match for "Yes" or not a match for "No".
9409 You could set it to both From and To, in which case all of the From and To
9410 addresses are used.
9411 The "Reply-To" and "Sender" cases are a little unusual.
9412 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9413 exists or the From address if there is no Reply-To address.
9414 Same for the Sender address.
9415 Setting this option may affect performance in large folders because the
9416 From and Reply-To of each message in the folder have to be checked.
9418 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9420 This is a command that is run with its standard input set to the message
9421 being checked and its standard output discarded.
9422 The full directory path should be specified.
9423 The command will be run and then its exit status will be checked against
9424 the Exit Status Interval, which defaults to just the value zero.
9425 If the exit status of the command falls in the interval, it is considered
9426 a match, otherwise it is not a match.
9427 <P>
9429 This option may actually be a list of commands.
9430 The first one that exists and is executable is used.
9431 That makes it possible to use the same configuration with Unix Alpine and
9432 PC-Alpine.
9433 <P>
9435 If none of the commands in the list exists and is executable then the rule
9436 is <EM>not</EM> a match.
9437 If it is possible that the command may not exist, you should be careful
9438 to structure your rules so that nothing destructive
9439 happens when the command does not exist.
9440 For example, you might have a filter that filters away spam when there is
9441 a match but does nothing when there is not a match.
9442 That would continue to work correctly if the command didn't exist.
9443 However, if you have a filter that filters away spam when there is not
9444 a match and keeps it when there is a match, that would filter everything
9445 if the categorizer command didn't exist.
9446 <P>
9447 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9448 setup for the bogofilter filter.
9450 <P>
9451 <End of help on this topic>
9452 </BODY>
9453 </HTML>
9454 ===== h_rules_roles =====
9455 <HTML>
9456 <HEAD>
9457 <TITLE>SETUP ROLES SCREEN</TITLE>
9458 </HEAD>
9459 <BODY>
9460 <H1>SETUP ROLES SCREEN</H1>
9461 <H2>SETUP ROLES COMMANDS</H2>
9462 <!--chtml if pinemode="function_key"-->
9463 <PRE>
9464 Available Commands -- Group 1 Available Commands -- Group 2
9465 ------------------------------- ------------------------------
9466 F1 Show Help Text F1 Show Help Text
9467 F2 See commands in next group F2 See commands in next group
9468 F3 Back to MAIN Alpine menu
9469 F4 Change configuration for role
9470 F5 Move to previous role F5 Include file in role config
9471 F6 Move to next role F6 Exclude file from config
9472 F7 Previous page of roles
9473 F8 Next page of roles
9474 F9 Add new role F9 Replicate existing role
9475 F10 Delete existing role
9476 F11 Shuffle the order of roles
9477 F12 Whereis (search role nicknames)
9478 </PRE>
9479 <!--chtml else-->
9480 <PRE>
9481 Navigation General Alpine Commands
9482 ------------------------- -----------------------
9483 P Prev Role ? Display this help text
9484 N Next Role E Back to MAIN Alpine menu
9485 - Previous page
9486 Spc (space bar) Next page
9487 W WhereIs (search for word in role nicknames)
9489 Setup Roles Commands
9490 ------------------------------------------------
9491 A Add new role $ Shuffle the order of roles
9492 D Delete existing role C Change configuration for highlighted role
9493 R Replicate existing role
9494 I Include file in role config X Exclude file from role config
9495 </PRE>
9496 <!--chtml endif-->
9498 <H2>Description of the Setup Roles Screen</H2>
9500 This screen lets you add, delete, modify, or change the order of the rules
9501 that determine the role you are playing when composing a message.
9502 <P>
9503 You may play different roles depending on who you are replying to.
9504 For example, if you are replying to a message addressed to help-desk you
9505 may be acting as a Help Desk Worker.
9506 That role may require that you use a different return address and/or
9507 a different signature.
9508 <P>
9509 Roles are optional.
9510 If you set up roles they work like this: Each role has a set of
9511 "Uses", which indicate whether or not a role is eligible to be
9512 considered for a particular use; a "Pattern",
9513 which is used to decide which of the eligible roles is used; and a set
9514 of "Actions", which are taken when that role is used.
9515 When you reply to a message, the message you are replying to is compared
9516 with the Patterns of the roles marked as eligible for use when replying.
9517 The comparisons start with the first eligible role and keep going until there
9518 is a match.
9519 If a match is found, the matching role's Actions are taken.
9520 <P>
9521 It is also possible to set a default role and to change that role during
9522 your Alpine session.
9523 When you start Alpine no default role will be set.
9524 You may set or change the current default role by using the "D"
9525 command in the role selection screen.
9526 You'll see that screen while composing a message and being asked to select
9527 a role.
9528 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9529 compose a message.
9530 You may find a default role useful if you normally perform the duties of one
9531 of your roles for a while, then you switch to another role and stay in the
9532 new role for another period of time.
9533 It may be easier than using the Role Command to select the role each time you
9534 compose a message.
9536 <H2>Role Uses</H2>
9538 There are three types of use to be configured;
9539 one for Replying, one for Forwarding, and one for Composing.
9540 These indicate whether or not you want a role to be considered when you
9541 type the Reply, Forward, or Compose commands.
9542 (The Role command is an alternate form of the Compose command, and it is
9543 not affected by these settings.)
9544 Each of these Use types has three possible values.
9545 The value "Never"
9546 means that the role will never be considered as a candidate for use with
9547 the corresponding command.
9548 For example, if you set a role's Reply Use to Never, then when you Reply to
9549 a message, that role won't even be considered.
9550 (That isn't quite true. If the message you are replying to matches some other
9551 role that requires confirmation,
9552 then there will be a ^T command available which allows you to select a role
9553 from all of your roles, not just the reply-eligible roles.)
9554 <P>
9556 The options "With confirmation" and "Without confirmation"
9557 both mean that you do want to consider this role when using the corresponding
9558 command.
9559 For either of these settings the role's Pattern will
9560 be checked to see if it matches the message.
9561 For Reply Use, the message used to compare the Pattern with is the message
9562 being replied to.
9563 For Forward Use, the message used to compare the Pattern with is the message
9564 being forwarded.
9565 For Compose Use, there is no message, so the parts of the Pattern that depend
9566 on a message (everything other than Current Folder Type) are ignored.
9567 In all cases, the Current Folder Type is checked if defined.
9568 If there is a match then this role will either be used without confirmation
9569 or will be the default when confirmation is asked for, depending on
9570 which of the two options is selected.
9571 If confirmation is requested, you will have a chance to
9572 choose No Role instead of the offered role, or to
9573 change the role to any one of your other roles (with the ^T command).
9575 <H2>Role Patterns</H2>
9577 In order to determine whether or not a message matches a role the message is
9578 compared with the Role's Pattern.
9579 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9580 Scoring, Other Rules, and Search Rules, so are described in only one place,
9581 "<A HREF="h_rule_patterns">here</A>".
9582 <P>
9583 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9584 a role that has all header patterns unset, the AllText pattern unset,
9585 the BodyText pattern unset,
9586 the Score Interval unset, and the Current Folder Type set to
9587 "Any" may be used as a default role.
9588 It should be put last in the list of roles since the matching
9589 starts at the beginning and proceeds until one of the roles is a match.
9590 If no roles at all match, then Alpine will
9591 use its regular methods of defining the role.
9592 If you wanted to, you could define a different "default" role
9593 for Replying, Forwarding, and Composing by setting the
9594 "Use" fields appropriately.
9596 <H2>Role Actions</H2>
9598 Once a role match is found, the role's Actions are taken.
9599 For each role there are several possible actions that may be defined.
9600 They are actions to set the From address, the Reply-To address,
9601 the Fcc, the Signature, the Template file, and Other Headers.
9603 <H3>Set From</H3>
9605 The From address is the address used on the From line of the message
9606 you are sending.
9608 <H3>Set Reply-To</H3>
9610 The Reply-To address is the address used on the Reply-To line of the message
9611 you are sending.
9612 You don't need a Reply-To address unless it is different from the From address.
9614 <H3>Set Other Headers</H3>
9616 If you want to set the value of the From or Reply-To headers, use
9617 the specific fields "Set From" or "Set Reply-To".
9618 If you want to set the values of other headers, use this field.
9619 This field is similar to the
9620 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9621 Each header you specify here must include the header tag
9622 ("To:", "Approved:", etc.)
9623 and may optionally include a value for that header.
9624 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9625 for a header here will replace any value that already exists.
9626 For example, if you are Replying to a message there will be at least one
9627 address in the To header (the address you are Replying to).
9628 However, if you Reply using a role that sets the To header, that role's
9629 To header value will be used instead.
9631 <H3>Set Fcc</H3>
9633 The Fcc is used as the Fcc for the message you are sending.
9635 <H3>Set Signature or Set LiteralSig</H3>
9637 The Signature is the name of a file to be used as the signature file when
9638 this role is being used.
9639 If the name of the file has a vertical bar following it (|)
9640 then it is assumed that the file is a program that should be run to
9641 produce the signature.
9642 If the LiteralSig is set, then it is used instead of the signature file.
9643 LiteralSig is just a different way to store the signature.
9644 It is stored in the pine configuration file instead of in a separate
9645 signature file.
9646 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9647 either in the role or as the default signature in the Setup/Config screen,
9648 then the signature file is ignored.
9650 <H3>Set Template</H3>
9652 A Template is the name of a file to be included in the message when this
9653 role is being used.
9654 If the name of the file has a vertical bar following it (|)
9655 then it is assumed that the file is a program that should be run to
9656 produce the template.
9658 <P>
9659 Both signature files and template files may be stored remotely on an IMAP
9660 server.
9661 In order to do that you just give the file a remote name.
9662 This works just like the regular
9663 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9664 option that is configured from the Setup/Configuration screen.
9665 A remote signature file name might look like:
9666 <P>
9667 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9668 <P>
9669 Once you have named the remote signature or template file you create its
9670 contents by using the "F" "editFile" command when the
9671 cursor is on the "Set Signature" or "Set Template"
9672 line of the role editor.
9674 <P>
9675 Both signature files and template files (or the output of signature programs
9676 and template file programs) may contain special tokens
9677 that are replaced with contents
9678 that depend on the message being replied to or forwarded.
9679 See the help for the individual fields inside the role editor for more
9680 information on tokens.
9682 <H3>Use SMTP Server</H3>
9684 If this field has a value, then it will be used as the SMTP server
9685 to send mail when this role is being used (unless the SMTP server variable
9686 is set in the system-wide fixed configuration file).
9687 It has the same semantics as the
9688 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9689 variable in the Setup/Config screen.
9690 When you postpone the composition this SMTP server list will be saved
9691 with the postponed composition and it cannot be changed later.
9692 Because of that, you may want to make this a list of SMTP servers
9693 with the preferred server at the front of the list and alternate servers
9694 later in the list.
9696 <P>
9697 If any of the actions are left unset, then the action depends on what
9698 is present in the "Initialize settings using role" field.
9699 If you've listed the nickname of another one of your roles there, then the
9700 corresponding action from that role will be used here.
9701 If that action is also blank, or if there is no nickname specified,
9702 then Alpine will do whatever it normally does to set these actions.
9703 This depends on other configuration options and features you've set.
9705 <H2>Command Descriptions</H2>
9707 <H3>Add</H3>
9709 The Add command is used to add a new role definition to your set of
9710 roles.
9711 The new role will be added after the highlighted role.
9713 <H3>Delete</H3>
9715 The Delete command deletes the currently highlighted role.
9717 <H3>Change</H3>
9719 The Change command lets you edit the nickname, Uses, Pattern,
9720 and Actions of the currently highlighted role.
9722 <H3>Shuffle</H3>
9724 The Shuffle command allows you to change the order of the roles.
9725 You may move the currently highlighted role up or down in the list.
9726 The order of the roles is important since the roles are tested for a
9727 match starting with the first role and continuing until a match is found.
9728 You should place the roles with more specific Patterns near the beginning
9729 of the list, and those with more general Patterns near the end so that
9730 the more specific matches will happen when appropriate.
9732 <H3>Replicate</H3>
9734 The Replicate command is used to copy an existing role and modify it.
9735 The new role will be added after the highlighted role.
9737 <H3>IncludeFile</H3>
9739 The IncludeFile command allows you to add a roles file to your configuration.
9740 Usually, your roles will be contained in your Alpine configuration file.
9741 If you wish, some or all of your roles may be stored in a separate file.
9742 If a roles file already exists (maybe it was made by somebody else using
9743 Alpine), you may insert it before the currently highlighted role.
9744 You may also insert an empty file or a file that does not yet exist.
9745 Once you have an empty roles file in your configuration, you may use
9746 the Shuffle command to move roles into it.
9747 In fact, that's the only way to get the initial role into the file.
9749 <H3>eXcludeFile</H3>
9751 The eXcludeFile command removes a roles file from your roles configuration.
9752 A limitation of the program is that in order to exclude a roles file
9753 that file must have at least one role
9754 in it, otherwise you won't be able to highlight a line in the file.
9755 So you may have to add a dummy role to the file in order to exclude the file.
9756 <P><UL>
9757 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9758 </UL>
9759 <P>
9760 <End of help on this topic>
9761 </BODY>
9762 </HTML>
9763 ===== h_rules_other =====
9764 <HTML>
9765 <HEAD>
9766 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
9767 </HEAD>
9768 <BODY>
9769 <H1>SETUP OTHER RULES SCREEN</H1>
9770 <H2>SETUP OTHER RULES COMMANDS</H2>
9771 <!--chtml if pinemode="function_key"-->
9772 <PRE>
9773 Available Commands -- Group 1 Available Commands -- Group 2
9774 ------------------------------- ------------------------------
9775 F1 Show Help Text F1 Show Help Text
9776 F2 See commands in next group F2 See commands in next group
9777 F3 Back to MAIN Alpine menu
9778 F4 Change configuration for rule
9779 F5 Move to previous rule F5 Include file in rule config
9780 F6 Move to next rule F6 Exclude file from config
9781 F7 Previous page of rules
9782 F8 Next page of rules
9783 F9 Add new rule F9 Replicate existing rule
9784 F10 Delete existing rule
9785 F11 Shuffle the order of rules
9786 F12 Whereis (search rule nicknames)
9787 </PRE>
9788 <!--chtml else-->
9789 <PRE>
9790 Navigation General Alpine Commands
9791 ------------------------- -----------------------
9792 P Prev rule ? Display this help text
9793 N Next rule E Back to MAIN Alpine menu
9794 - Previous page
9795 Spc (space bar) Next page
9796 W WhereIs (search for word in rule nicknames)
9798 Setup Other Rules Commands
9799 ------------------------------------------------
9800 A Add new rule $ Shuffle the order of rules
9801 D Delete existing rule C Change configuration for highlighted rule
9802 R Replicate existing rule
9803 I Include file in rule config X Exclude file from rule config
9804 </PRE>
9805 <!--chtml endif-->
9807 <H2>Description of the Setup Other Rules Screen</H2>
9809 This is where you may set various actions that do not fit well into the
9810 other Rules categories.
9812 <H2>Patterns</H2>
9814 Other Rules are a little different from the rest of the Rules because
9815 they depend only on the current folder, and not on a particular message.
9816 In order to determine whether or not a rule's actions should be applied
9817 the current folder is compared with the rule's Pattern, which consists
9818 of only the Current Folder Type.
9819 Current Folder Type works the same for Other Rules as it does for Roles,
9820 Filtering, Index Coloring, and Scoring.
9821 Keep in mind that the only part of the Pattern that applies to Other
9822 Rules is the Current Folder Type when looking at the description of
9823 Patterns given
9824 "<A HREF="h_rule_patterns">here</A>".
9826 <H2>The Actions</H2>
9828 <H3>Set Sort Order</H3>
9830 When you enter a new folder, these rules will be checked to see if you
9831 have set a sort order that is different from your default sort order.
9832 The default is set in the Setup/Config screen with
9833 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
9834 If the Sort Order action is set, then the folder will be displayed sorted in
9835 that sort order instead of in the default order.
9836 <P>
9837 A possible point of confusion arises when you change the configuration
9838 of the Sort Order for the currently open folder.
9839 The folder will normally be re-sorted when you go back to viewing the
9840 index.
9841 However, if you have manually sorted the folder with the
9842 Sort
9843 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
9844 command, then it will not be re-sorted until the next time it is opened.
9846 <H3>Set Index Format</H3>
9848 When you enter a new folder, these rules will be checked to see if you
9849 have set an Index Format that is different from your default Index Format,
9850 which is set with the
9851 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
9852 If so, the index will be displayed with this format instead of the default.
9854 <H3>Set Startup Rule</H3>
9856 When you enter a new folder, these rules will be checked to see if you
9857 have set a startup rule that is different from the default startup rule.
9858 The default for incoming folders is set in the Setup/Config screen with
9859 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
9860 The default for folders other than INBOX that are not part of your
9861 incoming collection
9862 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
9863 is to start with the last message in the folder.
9864 If the Startup Rule is set to something other than "default",
9865 then the rule will determine which message will be the current message when
9866 the folder is first opened.
9867 <P>
9868 The various startup rule possibilities work the same here as they do in
9869 the incoming collection, so check
9870 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
9871 for more help.
9873 <H2>Command Descriptions</H2>
9875 <H3>Add</H3>
9877 The Add command is used to add a new rule definition to your set of
9878 rules.
9879 The new rule will be added after the highlighted rule.
9881 <H3>Delete</H3>
9883 The Delete command deletes the currently highlighted rule.
9885 <H3>Change</H3>
9887 The Change command lets you edit the nickname, Pattern,
9888 and Action of the currently highlighted rule.
9890 <H3>Shuffle</H3>
9892 The Shuffle command allows you to change the order of the rules.
9893 You may move the currently highlighted rule up or down in the list.
9894 The order of the rules is important since the rules are tested for a
9895 match starting with the first rule and continuing until a match is found.
9896 You should place the rules with more specific Patterns near the beginning
9897 of the list, and those with more general Patterns near the end so that
9898 the more specific matches will happen when appropriate.
9900 <H3>Replicate</H3>
9902 The Replicate command is used to copy an existing rule definition and modify it.
9903 The new rule will be added after the highlighted rule.
9905 <H3>IncludeFile</H3>
9907 The IncludeFile command allows you to add a rules file to your configuration.
9908 Usually, your rules will be contained in your Alpine configuration file.
9909 If you wish, some or all of your rules may be stored in a separate file.
9910 If a rules file already exists (maybe it was made by somebody else using
9911 Alpine), you may insert it before the currently highlighted rule.
9912 You may also insert an empty file or a file that does not yet exist.
9913 Once you have an empty rules file in your configuration, you may use
9914 the Shuffle command to move rules into it.
9915 In fact, that's the only way to get the initial rule into the file.
9917 <H3>eXcludeFile</H3>
9919 The eXcludeFile command removes a rules file from your rules configuration.
9920 A limitation of the program is that in order to exclude a rules file
9921 that file must have at least one rule
9922 in it, otherwise you won't be able to highlight a line in the file.
9923 So you may have to add a dummy rule to the file in order to exclude the file.
9924 <P><UL>
9925 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9926 </UL>
9927 <P>
9928 <End of help on this topic>
9929 </BODY>
9930 </HTML>
9931 ===== h_rules_srch =====
9932 <HTML>
9933 <HEAD>
9934 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
9935 </HEAD>
9936 <BODY>
9937 <H1>SETUP SEARCH RULES SCREEN</H1>
9938 <H2>SETUP SEARCH RULES COMMANDS</H2>
9939 <!--chtml if pinemode="function_key"-->
9940 <PRE>
9941 Available Commands -- Group 1 Available Commands -- Group 2
9942 ------------------------------- ------------------------------
9943 F1 Show Help Text F1 Show Help Text
9944 F2 See commands in next group F2 See commands in next group
9945 F3 Back to MAIN Alpine menu
9946 F4 Change configuration for rule
9947 F5 Move to previous rule F5 Include file in rule config
9948 F6 Move to next rule F6 Exclude file from config
9949 F7 Previous page of rules
9950 F8 Next page of rules
9951 F9 Add new rule F9 Replicate existing rule
9952 F10 Delete existing rule
9953 F11 Shuffle the order of rules
9954 F12 Whereis (search rule nicknames)
9955 </PRE>
9956 <!--chtml else-->
9957 <PRE>
9958 Navigation General Alpine Commands
9959 ------------------------- -----------------------
9960 P Prev rule ? Display this help text
9961 N Next rule E Back to MAIN Alpine menu
9962 - Previous page
9963 Spc (space bar) Next page
9964 W WhereIs (search for word in rule nicknames)
9966 Setup Search Rules Commands
9967 ------------------------------------------------
9968 A Add new rule $ Shuffle the order of rules
9969 D Delete existing rule C Change configuration for highlighted rule
9970 R Replicate existing rule
9971 I Include file in rule config X Exclude file from rule config
9972 </PRE>
9973 <!--chtml endif-->
9975 <H2>Description of the Setup Search Rules Screen</H2>
9977 One of the commands that becomes available when that feature is turned on
9978 is the "; Select" command, which is used in the MESSAGE INDEX
9979 screen to select a set of messages.
9980 One way of selecting messages is to use a Rule.
9981 All of the messages that match (or don't match if you wish)
9982 a Rule's Pattern will be selected.
9983 <P>
9984 Any of your Rules may be used for this purpose.
9985 You might already have Rules set up for filtering, index line color, scores, or roles;
9986 and you may use any of those Rules with the Select command.
9987 However, you might find it more convenient to set up a separate set of Rules
9988 just for this purpose without having to worry about what other effects
9989 they may cause.
9990 That is the purpose of these Select Rules.
9992 <P>
9993 Each rule has a "Pattern"
9994 that is used to decide which messages are selected when you use it with
9995 the Select command.
9997 <H2>Patterns</H2>
9999 In order to determine whether or not a message should be selected
10000 the message is compared with the rule's Pattern.
10001 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10002 Scoring, Other Rules, and Search Rules, so are described in only one place,
10003 "<A HREF="h_rule_patterns">here</A>".
10005 <H2>Command Descriptions</H2>
10007 <H3>Add</H3>
10009 The Add command is used to add a new rule definition to your set of
10010 rules.
10011 The new rule will be added after the highlighted rule.
10013 <H3>Delete</H3>
10015 The Delete command deletes the currently highlighted rule.
10017 <H3>Change</H3>
10019 The Change command lets you edit the nickname and Pattern
10020 of the currently highlighted rule.
10022 <H3>Shuffle</H3>
10024 The Shuffle command allows you to change the order of the rules.
10025 This affects only the order they are presented in when you use the
10026 ^T subcommand of the Select by Rule command.
10027 You may move the currently highlighted rule up or down in the list.
10029 <H3>Replicate</H3>
10031 The Replicate command is used to copy an existing rule definition and modify it.
10032 The new rule will be added after the highlighted rule.
10034 <H3>IncludeFile</H3>
10036 The IncludeFile command allows you to add a rules file to your configuration.
10037 Usually, your rules will be contained in your Alpine configuration file.
10038 If you wish, some or all of your rules may be stored in a separate file.
10039 If a rules file already exists (maybe it was made by somebody else using
10040 Alpine), you may insert it before the currently highlighted rule.
10041 You may also insert an empty file or a file that does not yet exist.
10042 Once you have an empty rules file in your configuration, you may use
10043 the Shuffle command to move rules into it.
10044 In fact, that's the only way to get the initial rule into the file.
10046 <H3>eXcludeFile</H3>
10048 The eXcludeFile command removes a rules file from your rules configuration.
10049 A limitation of the program is that in order to exclude a rules file
10050 that file must have at least one rule
10051 in it, otherwise you won't be able to highlight a line in the file.
10052 So you may have to add a dummy rule to the file in order to exclude the file.
10053 <P><UL>
10054 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10055 </UL>
10056 <P>
10057 <End of help on this topic>
10058 </BODY>
10059 </HTML>
10060 ===== h_rules_incols =====
10061 <HTML>
10062 <HEAD>
10063 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
10064 </HEAD>
10065 <BODY>
10066 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
10067 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
10068 <!--chtml if pinemode="function_key"-->
10069 <PRE>
10070 Available Commands -- Group 1 Available Commands -- Group 2
10071 ------------------------------- ------------------------------
10072 F1 Show Help Text F1 Show Help Text
10073 F2 See commands in next group F2 See commands in next group
10074 F3 Back to MAIN Alpine menu
10075 F4 Change configuration for rule
10076 F5 Move to previous rule F5 Include file in rule config
10077 F6 Move to next rule F6 Exclude file from config
10078 F7 Previous page of rules
10079 F8 Next page of rules
10080 F9 Add new rule F9 Replicate existing rule
10081 F10 Delete existing rule
10082 F11 Shuffle the order of rules
10083 F12 Whereis (search rule nicknames)
10084 </PRE>
10085 <!--chtml else-->
10086 <PRE>
10087 Navigation General Alpine Commands
10088 ------------------------- -----------------------
10089 P Prev rule ? Display this help text
10090 N Next rule E Back to MAIN Alpine menu
10091 - Previous page
10092 Spc (space bar) Next page
10093 W WhereIs (search for word in rule nicknames)
10095 Setup Index Color Commands
10096 ------------------------------------------------
10097 A Add new rule $ Shuffle the order of rules
10098 D Delete existing rule C Change configuration for highlighted rule
10099 R Replicate existing rule
10100 I Include file in rule config X Exclude file from rule config
10101 </PRE>
10102 <!--chtml endif-->
10104 <H2>Description of the Setup Index Line Colors Screen</H2>
10106 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
10107 This action is only available if your terminal is capable of displaying
10108 color and color display has been enabled with the
10109 <A HREF="h_config_color_style">Color Style</A> option within the
10110 Setup Color screen.
10111 (In PC-Alpine, color is always enabled so there is no option to turn on.)
10112 This screen lets you add, delete, modify, or change the order of the rules
10113 that cause the lines in the MESSAGE INDEX to be displayed in different
10114 colors.
10115 <P>
10116 Each rule has a "Pattern",
10117 which is used to decide which of the rules is used; and the color that
10118 is used if the Pattern matches a particular message.
10120 <H2>Index Color Patterns</H2>
10122 In order to determine whether or not a message matches an Index Color Rule
10123 the message is compared with the rule's Pattern.
10124 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10125 Scoring, Other Rules, and Search Rules, so are described in only one place,
10126 "<A HREF="h_rule_patterns">here</A>".
10128 <P>
10129 If none of the Index Color rules is a match for a particular index line,
10130 then the color used is set using
10131 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10133 <H2>Index Line Color</H2>
10135 This is the color that index lines are colored when there is a matching
10136 Pattern.
10137 This colors the whole index line, except possibly the status letters,
10138 which may be colored separately using
10139 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10141 <H2>Command Descriptions</H2>
10143 <H3>Add</H3>
10145 The Add command is used to add a new rule definition to your set of
10146 rules.
10147 The new rule will be added after the highlighted rule.
10149 <H3>Delete</H3>
10151 The Delete command deletes the currently highlighted rule.
10153 <H3>Change</H3>
10155 The Change command lets you edit the nickname, Pattern,
10156 and Index Line Color of the currently highlighted rule.
10158 <H3>Shuffle</H3>
10160 The Shuffle command allows you to change the order of the rules.
10161 You may move the currently highlighted rule up or down in the list.
10162 The order of the rules is important since the rules are tested for a
10163 match starting with the first rule and continuing until a match is found.
10164 You should place the rules with more specific Patterns near the beginning
10165 of the list, and those with more general Patterns near the end so that
10166 the more specific matches will happen when appropriate.
10168 <H3>Replicate</H3>
10170 The Replicate command is used to copy an existing rule definition and modify it.
10171 The new rule will be added after the highlighted rule.
10173 <H3>IncludeFile</H3>
10175 The IncludeFile command allows you to add a rules file to your configuration.
10176 Usually, your rules will be contained in your Alpine configuration file.
10177 If you wish, some or all of your rules may be stored in a separate file.
10178 If a rules file already exists (maybe it was made by somebody else using
10179 Alpine), you may insert it before the currently highlighted rule.
10180 You may also insert an empty file or a file that does not yet exist.
10181 Once you have an empty rules file in your configuration, you may use
10182 the Shuffle command to move rules into it.
10183 In fact, that's the only way to get the initial rule into the file.
10185 <H3>eXcludeFile</H3>
10187 The eXcludeFile command removes a rules file from your rules configuration.
10188 A limitation of the program is that in order to exclude a rules file
10189 that file must have at least one rule
10190 in it, otherwise you won't be able to highlight a line in the file.
10191 So you may have to add a dummy rule to the file in order to exclude the file.
10192 <P><UL>
10193 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10194 </UL>
10195 <P>
10196 <End of help on this topic>
10197 </BODY>
10198 </HTML>
10199 ===== h_rules_filter =====
10200 <HTML>
10201 <HEAD>
10202 <TITLE>SETUP FILTERING SCREEN</TITLE>
10203 </HEAD>
10204 <BODY>
10205 <H1>SETUP FILTERING SCREEN</H1>
10206 <H2>SETUP FILTERING COMMANDS</H2>
10207 <!--chtml if pinemode="function_key"-->
10208 <PRE>
10209 Available Commands -- Group 1 Available Commands -- Group 2
10210 ------------------------------- ------------------------------
10211 F1 Show Help Text F1 Show Help Text
10212 F2 See commands in next group F2 See commands in next group
10213 F3 Back to MAIN Alpine menu
10214 F4 Change configuration for filter
10215 F5 Move to previous filter F5 Include file in filter config
10216 F6 Move to next filter F6 Exclude file from config
10217 F7 Previous page of filters
10218 F8 Next page of filters
10219 F9 Add new filter F9 Replicate existing filter
10220 F10 Delete existing filter
10221 F11 Shuffle the order of filters
10222 F12 Whereis (search filter nicknames)
10223 </PRE>
10224 <!--chtml else-->
10225 <PRE>
10226 Navigation General Alpine Commands
10227 ------------------------- -----------------------
10228 P Prev Filter ? Display this help text
10229 N Next Filter E Back to MAIN Alpine menu
10230 - Previous page
10231 Spc (space bar) Next page
10232 W WhereIs (search for word in filter nicknames)
10234 Setup Filters Commands
10235 ------------------------------------------------
10236 A Add new filter $ Shuffle the order of filters
10237 D Delete existing filter C Change configuration for highlighted filter
10238 R Replicate existing filter
10239 I Include file in filter config X Exclude file from filter config
10240 </PRE>
10241 <!--chtml endif-->
10243 <H2>Description of the Setup Filtering Screen</H2>
10245 This screen lets you add, delete, modify, or change the order of the rules
10246 that determine the filtering Alpine does on folders you view.
10247 <P>
10248 The software that actually delivers mail (the stuff that happens
10249 before Alpine is involved) for you is in a better position to do mail filtering
10250 than Alpine itself.
10251 If possible, you may want to look into using that sort of mail filtering to
10252 deliver mail to different folders, delete it, or forward it.
10253 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
10254 <P>
10255 Filtering is a way to automatically move certain messages from one folder
10256 to another or to delete messages.
10257 It can also be used to set message status (Important, Deleted, New,
10258 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
10259 Alpine doesn't have the ability to forward mail to another address or
10260 to deliver vacation messages.
10261 <P>
10262 Each filtering rule has a "Pattern" and a "Filter Action".
10263 When a folder is opened, when new mail arrives in an open folder, or
10264 when mail is Expunged from a folder; each
10265 message is compared with the Patterns of your filtering rules.
10266 The comparisons start with the first rule and keep going until there
10267 is a match.
10268 If a match is found, the message may be deleted or moved, depending on
10269 the setting of the Filter Action.
10270 If the message is not deleted, it may have its status altered.
10272 <P>
10273 <EM>NOTE:</EM>
10274 When setting up a Pattern used to delete messages,
10275 it is recommended that you test the Pattern first with a "Move"
10276 folder specified in
10277 case unintended matches occur. Messages that are deleted will be removed
10278 from the folder and <EM>unrecoverable</EM> from within Alpine after the
10279 next Expunge command or once the folder being filtered has been closed.
10281 <H2>Filter Patterns</H2>
10283 In order to determine whether or not a message matches a filter the message is
10284 compared with the Filter's Pattern.
10285 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10286 Scoring, Other Rules, and Search Rules, so are described in only one place,
10287 "<A HREF="h_rule_patterns">here</A>".
10288 <P>
10289 Since filtering is a potentially destructive action, if you have a filtering
10290 Pattern with nothing other than Current Folder Type set, that filtering
10291 rule is ignored.
10293 <H2>Filter Actions</H2>
10295 Once a filter match is found for a particular message, there are some actions
10296 that may be taken.
10297 First, the message may have its status changed.
10298 This is the same message status that you can manipulate manually using the
10299 <a href="h_common_flag">Flag Command</a>.
10300 There are always four elements of message status that you can control.
10301 You can set or clear the Important status, the New status, the Deleted
10302 status, and the Answered status.
10303 Of course, if the filter is going to delete the message,
10304 then there is no point in setting message status.
10305 You may also be able to set user-defined keywords for a message.
10306 Read a little about keywords in the help text for the
10307 <A HREF="h_common_flag">Flag</A> command.
10308 <P>
10309 Second, the filter may delete or move the message.
10310 Deleting the message marks it Deleted and removes it from view.
10311 It is effectively gone forever (though it technically is still there until
10312 the next expunge command, which may happen implicitly).
10313 Moving the message moves it from the open folder into the folder
10314 listed on the "Folder List" line of the filter configuration.
10315 If you list more than one folder name (separated by commas) then the message
10316 will be copied to each of those folders.
10317 In any case, if "Delete" or "Move" is set then the
10318 message is removed from the current folder.
10319 If you just want to set the messages status without deleting it from
10320 the folder, then set the filter action to
10321 "Just Set Message Status".
10322 <P>
10323 (There is no way to do a Copy instead of a Move, due to the difficulties
10324 involved in keeping track of whether or not a message has
10325 already been copied.)
10327 <H2>Command Descriptions</H2>
10329 <H3>Add</H3>
10331 The Add command is used to add a new filter definition to your set of
10332 filters.
10333 The new filter will be added after the highlighted filter.
10335 <H3>Delete</H3>
10337 The Delete command deletes the currently highlighted filter.
10339 <H3>Change</H3>
10341 The Change command lets you edit the nickname, Pattern,
10342 and Folder of the currently highlighted filter.
10344 <H3>Shuffle</H3>
10346 The Shuffle command allows you to change the order of the filters.
10347 You may move the currently highlighted filter up or down in the list.
10348 The order of the filters is important since the filters are tested for a
10349 match starting with the first filter and continuing until a match is found.
10350 You should place the filters with more specific Patterns near the beginning
10351 of the list, and those with more general Patterns near the end so that
10352 the more specific matches will happen when appropriate.
10354 <H3>Replicate</H3>
10356 The Replicate command is used to copy an existing filter and modify it.
10357 The new filter will be added after the highlighted filter.
10359 <H3>IncludeFile</H3>
10361 The IncludeFile command allows you to add a filters file to your configuration.
10362 Usually, your filters will be contained in your Alpine configuration file.
10363 If you wish, some or all of your filters may be stored in a separate file.
10364 If a filters file already exists (maybe it was made by somebody else using
10365 Alpine), you may insert it before the currently highlighted filter.
10366 You may also insert an empty file or a file that does not yet exist.
10367 Once you have an empty filters file in your configuration, you may use
10368 the Shuffle command to move filters into it.
10369 In fact, that's the only way to get the initial filter into the file.
10371 <H3>eXcludeFile</H3>
10373 The eXcludeFile command removes a filters file from your filters configuration.
10374 A limitation of the program is that in order to exclude a filters file
10375 that file must have at least one filter
10376 in it, otherwise you won't be able to highlight a line in the file.
10377 So you may have to add a dummy filter to the file in order to exclude the file.
10378 <P><UL>
10379 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10380 </UL>
10381 <P>
10382 <H3>Performance Considerations</H3>
10383 The number and type of patterns being tested can
10384 adversely effect performance. Issues to be aware
10385 of include:
10386 <P>
10387 <UL>
10388 <LI> The more filters you have defined the longer it will take to run down
10389 the list. Deleting unused filters is a good idea.
10390 <LI> Filtering in newsgroups served by an NNTP server will be slow
10391 if your patterns include tests other than "From:"
10392 or "Subject:".
10393 </UL>
10394 <P>
10395 <End of help on this topic>
10396 </BODY>
10397 </HTML>
10398 ===== h_rules_score =====
10399 <HTML>
10400 <HEAD>
10401 <TITLE>SETUP SCORING SCREEN</TITLE>
10402 </HEAD>
10403 <BODY>
10404 <H1>SETUP SCORING SCREEN</H1>
10405 <H2>SETUP SCORING COMMANDS</H2>
10406 <!--chtml if pinemode="function_key"-->
10407 <PRE>
10408 Available Commands -- Group 1 Available Commands -- Group 2
10409 ------------------------------- ------------------------------
10410 F1 Show Help Text F1 Show Help Text
10411 F2 See commands in next group F2 See commands in next group
10412 F3 Back to MAIN Alpine menu
10413 F4 Change configuration for rule
10414 F5 Move to previous rule F5 Include file in rule config
10415 F6 Move to next rule F6 Exclude file from config
10416 F7 Previous page of rules
10417 F8 Next page of rules
10418 F9 Add new rule F9 Replicate existing rule
10419 F10 Delete existing rule
10420 F11 Shuffle the order of rules
10421 F12 Whereis (search rule nicknames)
10422 </PRE>
10423 <!--chtml else-->
10424 <PRE>
10425 Navigation General Alpine Commands
10426 ------------------------- -----------------------
10427 P Prev rule ? Display this help text
10428 N Next rule E Back to MAIN Alpine menu
10429 - Previous page
10430 Spc (space bar) Next page
10431 W WhereIs (search for word in rule nicknames)
10433 Setup Scoring Commands
10434 ------------------------------------------------
10435 A Add new rule $ Shuffle the order of rules
10436 D Delete existing rule C Change configuration for highlighted rule
10437 R Replicate existing rule
10438 I Include file in rule config X Exclude file from rule config
10439 </PRE>
10440 <!--chtml endif-->
10442 <H2>Description of the Setup Scoring Screen</H2>
10444 Most people will not use scores at all, but if you do use them, here's how
10445 they work in Alpine.
10446 Using this screen, you may define Scoring rules.
10447 The score for a message is calculated by looking at every Score rule defined
10448 and adding up the Score Values for the ones that match the message.
10449 If there are no matches for a message, it has a score of zero.
10450 Message scores may be used a couple of ways in Alpine.
10452 <H3>Sorting by Score</H3>
10454 One of the methods you may use to sort message indexes is to sort by
10455 score.
10456 The scores of all the messages in a folder will be calculated and then
10457 the index will be ordered by placing the messages in order of ascending or
10458 descending score.
10460 <H3>Scores for use in Patterns</H3>
10462 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10463 category labeled "Score Interval".
10464 When a message is being compared with a Pattern to check for a match, if
10465 the Score Interval is set only messages that have a score somewhere in
10466 the interval are a match.
10468 <H2>Scoring Rule Patterns</H2>
10470 In order to determine whether or not a message matches a scoring rule
10471 the message is compared with the rule's Pattern.
10472 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10473 Scoring, Other Rules, and Search Rules, so are described in only one place,
10474 "<A HREF="h_rule_patterns">here</A>".
10476 <P>
10477 Actually, Scoring rule Patterns are slightly different from the other types of
10478 Patterns because Scoring rule Patterns don't contain a Score Interval.
10479 In other words, when calculating the score for a message, which is done
10480 by looking at the Scoring rule Patterns, scores aren't used.
10482 <H2>Score Value</H2>
10484 This is the value that will be added to the score for a message if the
10485 rule's Pattern is a match.
10486 Each individual Score Value is an integer between -100 and 100, and the
10487 values from matching rules are added together to get a message's score.
10488 There is also a way to extract the value from a particular header of each
10489 message. See the help text for Score Value for further information.
10491 <H2>Command Descriptions</H2>
10493 <H3>Add</H3>
10495 The Add command is used to add a new scoring rule definition.
10496 The new rule will be added after the highlighted rule.
10498 <H3>Delete</H3>
10500 The Delete command deletes the currently highlighted scoring rule.
10502 <H3>Change</H3>
10504 The Change command lets you edit the nickname, Pattern,
10505 and Score Value of the currently highlighted scoring rule.
10507 <H3>Shuffle</H3>
10509 The Shuffle command allows you to change the order of the scoring rules.
10510 You may move the currently highlighted rule up or down in the list.
10511 The order of the rules is important since the rules are tested for a
10512 match starting with the first rule and continuing until a match is found.
10513 You should place the rules with more specific Patterns near the beginning
10514 of the list, and those with more general Patterns near the end so that
10515 the more specific matches will happen when appropriate.
10517 <H3>Replicate</H3>
10519 The Replicate command is used to copy an existing rule and modify it.
10520 The new rule will be added after the highlighted rule.
10522 <H3>IncludeFile</H3>
10524 The IncludeFile command allows you to add a rules file to your configuration.
10525 Usually, your rules will be contained in your Alpine configuration file.
10526 If you wish, some or all of your rules may be stored in a separate file.
10527 If a rules file already exists (maybe it was made by somebody else using
10528 Alpine), you may insert it before the currently highlighted rule.
10529 You may also insert an empty file or a file that does not yet exist.
10530 Once you have an empty rules file in your configuration, you may use
10531 the Shuffle command to move rules into it.
10532 In fact, that's the only way to get the initial rule into the file.
10534 <H3>eXcludeFile</H3>
10536 The eXcludeFile command removes a rules file from your rules configuration.
10537 A limitation of the program is that in order to exclude a rules file
10538 that file must have at least one rule
10539 in it, otherwise you won't be able to highlight a line in the file.
10540 So you may have to add a dummy rule to the file in order to exclude the file.
10541 <P><UL>
10542 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10543 </UL>
10544 <P>
10545 <End of help on this topic>
10546 </BODY>
10547 </HTML>
10548 ===== h_direct_config =====
10549 <HTML>
10550 <HEAD>
10551 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10552 </HEAD>
10553 <BODY>
10554 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10555 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10556 <!--chtml if pinemode="function_key"-->
10557 <PRE>
10558 Available Commands
10559 -------------------------------
10560 F1 Show Help Text
10561 F3 Back to MAIN Alpine menu
10562 F4 Change configuration for directory server
10563 F5 Move to previous directory server
10564 F6 Move to next directory server
10565 F7 Previous page of directory servers
10566 F8 Next page of directory servers
10567 F9 Add new directory server
10568 F10 Delete existing directory server
10569 F11 Shuffle the order of directory servers
10570 F12 Whereis (search directory server titles)
10571 </PRE>
10572 <!--chtml else-->
10573 <PRE>
10574 Navigation General Alpine Commands
10575 ------------------------- -----------------------
10576 P Prev Directory Server ? Display this help text
10577 N Next Directory Server E Back to MAIN Alpine menu
10578 - Previous page
10579 Spc (space bar) Next page
10580 W WhereIs (search for word in directory server titles)
10582 Setup LDAP Directory Server Commands
10583 ------------------------------------------------
10584 A Add new directory server $ Shuffle the order of directory servers
10585 D Delete existing dir server C Change configuration for highlighted server
10586 </PRE>
10587 <!--chtml endif-->
10589 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10591 This screen lets you add, delete, modify, or change the order of your
10592 directory servers. You may also set some optional behavior for each server.
10593 The "Add Dir" command brings up a blank form to
10594 fill in. You will have to supply at least the name of the LDAP server.
10595 You will often have to supply a search base to be used with that server,
10596 as well. Once the form has been brought up on your screen, there is help
10597 available for each of the options you may set.
10598 <P>
10599 The "Del Dir" command allows you to remove a directory server
10600 from your configuration.
10601 <P>
10602 The "Change" command is similar to the "Add Dir" command.
10603 The difference is that instead of bringing up a form for a new server
10604 configuration, you are changing the configuration of an existing entry.
10605 For example, you might want to correct a typing error, change a
10606 nickname, or change one of the options set for that server.
10607 <P>
10608 The "Shuffle" command is used to change the order of directory
10609 servers.
10610 <P><UL>
10611 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10612 </UL>
10613 <P>
10614 <End of help on this topic>
10615 </BODY>
10616 </HTML>
10617 ============= h_address_display ========================
10618 <HTML>
10619 <HEAD>
10620 <TITLE>SEARCH RESULTS INDEX</TITLE>
10621 </HEAD>
10622 <BODY>
10623 <H1>SEARCH RESULTS INDEX</H1>
10624 This screen shows the results, if any, of your Directory Server search.
10625 Commands (besides those for screen navigation) are:
10626 <DL>
10627 <DT>View
10628 <!--chtml if pinemode="function_key"-->
10629 (F4)
10630 <!--chtml else-->
10631 (V)
10632 <!--chtml endif-->
10633 </DT>
10634 <DD>See the full information for the selected entry.
10636 <DT>Compose
10637 <!--chtml if pinemode="function_key"-->
10638 (F9)
10639 <!--chtml else-->
10640 (C)
10641 <!--chtml endif--></DT>
10642 <DD>Compose a message with the selected entry as the recipient.
10644 <DT>Role
10645 <!--chtml if pinemode="function_key"-->
10646 (F2)
10647 <!--chtml else-->
10648 (#)
10649 <!--chtml endif--></DT>
10650 <DD>Compose a message with the selected entry as the recipient. This differs
10651 from Compose in that you may select a role before beginning your composition.
10653 <DT>Forward
10654 <!--chtml if pinemode="function_key"-->
10655 (F10)
10656 <!--chtml else-->
10657 (F)
10658 <!--chtml endif--></DT>
10659 <DD>Send the full information for the selected entry as an
10660 email message to someone else.
10662 <DT>Save
10663 <!--chtml if pinemode="function_key"-->
10664 (F11)
10665 <!--chtml else-->
10666 (S)
10667 <!--chtml endif-->
10668 </DT>
10669 <DD>Save to your address book:
10670 <UL>
10671 <LI>the result of the search (as just found through your query) for the
10672 selected entry; or
10673 <LI>the selected entry for repeated Directory Server searching when used
10674 in the future.
10675 </UL>
10676 or<BR>
10677 Export to a file (external to Alpine):
10678 <UL>
10679 <LI>the full information for the selected entry; or
10680 <LI>the email address from the selected entry; or
10681 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10682 </UL>
10683 <DT>WhereIs
10684 <!--chtml if pinemode="function_key"-->
10685 (F12)
10686 <!--chtml else-->
10687 (W)
10688 <!--chtml endif-->
10689 </DT>
10690 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10691 displayed text, not the full records for each entry.)
10692 </DL>
10693 <End of help on this topic>
10694 </BODY>
10695 </HTML>
10696 ============= h_address_select ========================
10697 <HTML>
10698 <HEAD>
10699 <TITLE>SEARCH RESULTS INDEX</TITLE>
10700 </HEAD>
10701 <BODY>
10702 <H1>SEARCH RESULTS INDEX</H1>
10703 This screen shows the results, if any, of your Directory Server search.
10704 Commands (besides those for screen navigation) are:
10705 <DL>
10706 <DT>Select
10707 </DT>
10708 <DD>Select this entry for use.
10710 <DT>ExitSelect
10711 <DD>Exit without selecting any of the entries.
10713 <DT>WhereIs
10714 </DT>
10715 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10716 displayed text, not the full records for each entry.)
10717 </DL>
10718 <End of help on this topic>
10719 </BODY>
10720 </HTML>
10721 ===== h_folder_maint =====
10722 <HTML>
10723 <HEAD>
10724 <TITLE>Help for Folder List</TITLE>
10725 </HEAD>
10726 <BODY>
10727 <H1>FOLDER LIST COMMANDS</H1>
10728 <!--chtml if pinemode="function_key"-->
10729 <PRE>
10730 Available Commands -- Group 1 Available Commands -- Group 2
10731 ------------------------------- ------------------------------
10732 F1 Show Help Text F1 Show Help Text
10733 F2 See commands in next group F2 See commands in next group
10734 F3 MAIN MENU Screen F3 Quit Alpine
10735 F4 Select folder and view it F4 MAIN MENU Screen
10736 F5 Move to previous folder
10737 F6 Move to next folder F6 Specify a folder to go to
10738 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
10739 F8 Show next screen of listing F8 Compose a message
10740 F9 Add a new folder F9 Print folder listing
10741 F10 Delete selected folder
10742 F11 Rename selected folder
10743 F12 Whereis (search folder names)
10745 Available Commands -- Group 3
10746 F1 Show Help Text
10747 F2 See commands in next group
10748 F5 Go to next new message
10749 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
10750 F8 Compose a message using roles
10751 F9 Export folder to a file
10752 F10 Import the file back to a folder
10753 </PRE>
10754 <!--chtml else-->
10755 <PRE>
10756 Navigating the Folder Screen Operations on the Selected Folder
10757 ---------------------------- ---------------------------------
10758 P Move to previous folder V View Index of selected folder
10759 N Move to next folder D Delete
10760 - Show previous page of listing R Rename
10761 Spc (space bar) Show next page E Export to file
10762 U Import from file to folder
10764 FOLDER LIST Screen Commands General Alpine Command
10765 --------------------------- -----------------------
10766 A Add a folder O Show all other available commands
10767 G Specify a folder to go to ? Show Help text
10768 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
10769 W Whereis (search folder names) Q Quit Alpine
10770 % Print folder listing C Compose a message
10771 # Compose a message using roles
10772 </PRE>
10773 <!--chtml endif-->
10774 <P>
10775 These commands are only available in the FOLDER LIST screen when the
10776 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
10777 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
10778 <DT>Select:</DT>
10779 <DD>Select folders by certain criteria:<UL>
10780 <LI>All: of limited use, since there is no Apply command.
10781 <LI>by Property: <UL>
10782 <LI>folder contains messages not yet seen
10783 <LI>folder contains new messages
10784 <LI>folder contains exactly as many, more, or fewer messages
10785 than a given number
10786 </UL>
10787 <LI>by Text: <UL>
10788 <LI>contained in name of folder (Name Select)
10789 <LI>contained in messages in folder (Content Select)
10790 </UL>
10791 </UL></DD>
10793 <DT>Select current:</DT>
10794 <DD>Select the folder the cursor is on. (Can be used to "manually"
10795 add one or more folders to a set created with the Select command described
10796 above.)</DD>
10797 <DT>Zoom mode:</DT>
10798 <DD>Toggles display of only selected folders or all folders on and off.</DD>
10799 </DL>
10800 <P>
10801 If the feature
10802 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
10803 is set then the TAB key will display the number of recent messages and
10804 the total number of messages in the highlighted folder.
10805 <P>
10806 The "Export" command causes the lowest common denominator style
10807 mailbox to be written to a file.
10808 If the file already exists, you are asked if you want to delete it.
10809 If you say No, then the operation is aborted.
10810 Export might be a reasonable way to store a backup or an archival copy of
10811 a folder.
10812 The exported-to file is a local file on the system where you are running Alpine.
10813 The "Import" command is the opposite of the Export command.
10814 It reads a file created by Export and asks where it should save it in your
10815 folders.
10816 This could be a new folder or an existing folder.
10817 If the folder already exists, the messages from the exported file will be
10818 appended to the folder.
10819 <P>
10820 <CENTER>Description of the FOLDER LIST Screen</CENTER>
10822 The purpose of the FOLDER LIST screen is to help you browse and manage
10823 the folders and directories (also known as "hierarchy")
10824 contained within a collection.
10826 <P>
10827 Folders and directories are arranged alphabetically across lines of
10828 the screen. Directories, if present, are denoted by a special
10829 character at the end of the name known as the hierarchy delimiter
10830 (typically, "/"). By default, folders and directories are
10831 mixed together. The
10832 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
10833 configuration option can be used to group directories toward the
10834 beginning or end of the list.
10836 <P>
10837 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
10838 commands change the "selected" (i.e., highlighted) folder or
10839 directory, and the View Fldr/Dir commands will "open" the
10840 selected item. Folder and directory management is provided via the
10841 Rename, Delete and Add commands.
10843 <P><CENTER>About Folders</CENTER>
10844 What are Folders?<P>
10846 Folders are simply files where messages are kept. Every message has to be
10847 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
10848 folder for sent mail and a folder for saved messages.<P>
10850 You may create as many other folders as you wish. They must be given
10851 names that can be filenames on the filesystem.
10852 <P>
10854 You can move messages from one folder to another by opening the original
10855 folder and saving messages into the other folder just as you can save
10856 message from your INBOX to any other folder.<P>
10858 Folders are typically just files in the filesystem. However, the files
10859 that are
10860 folders have some special formatting in them (so that Alpine knows where one
10861 message ends and another begins) and should <EM>not</EM> be edited outside of
10862 Alpine. If you want copies of your messages in text files that you can edit
10863 or otherwise manipulate, use the Export command to copy them from Alpine into
10864 your regular file area.
10866 <P>
10867 FOR MORE INFORMATION: See the section on
10868 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
10869 <P>
10870 <CENTER>About Directories</CENTER>
10871 <P>
10872 A directory is simply a container used to group folders within a
10873 folder list. You can create as many directories as you like. And
10874 directories can even contain directories themselves.
10876 <P>
10877 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
10878 to note that not all IMAP servers support directories. If you find that
10879 the Add command fails to offer the "Create Directory" subcommand,
10880 then it's likely that directories are not supported by the server serving
10881 in that collection.
10883 <P>
10884 Similarly, servers that do provide for directories may not do so in
10885 the same way. On some servers, for example, each folder name you
10886 create is at the same time capable of being a directory. When this
10887 happens, Alpine will display both the folder name and the name of the
10888 directory (with trailing hierarchy delimiter) in the folder list.
10890 <P>
10891 Another issue with IMAP access, though with a much smaller set of servers,
10892 is that not all servers accept the request to list out the available
10893 folders and directories in the same way. If you find yourself having
10894 trouble viewing folders on your server, you might investigate the
10895 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
10896 feature.
10897 <P>
10898 <UL>
10899 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10900 </UL>
10901 <P>
10902 <End of help on this topic>
10903 </BODY>
10904 </HTML>
10905 ========= h_valid_folder_names ========
10906 <HTML>
10907 <HEAD>
10908 <TITLE>Explanation of Valid Folder Names</TITLE>
10909 </HEAD>
10910 <BODY>
10911 <H1>Folder Name Syntax Explained</H1>
10913 Once your folder collections are defined, you can usually refer to
10914 folders by their simple (unqualified) name, or pick from a FOLDER LIST
10915 display. However, understanding the complete syntax for folder names,
10916 both local and remote, is handy when using the Goto command and when
10917 you are adding new folder collections via the Setups/collectionList screen.
10918 <P>
10919 An Alpine folder name looks like
10921 <P>
10922 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
10923 <P>
10925 The square brackets ([]) mean that the part is optional.
10927 <P>
10928 If there is no remote-specification, then the folder name is interpreted
10929 locally on the computer running Alpine.
10930 Local folder names depend on the operating system used by the computer
10931 running Alpine, as well as the configuration of that system. For example,
10932 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
10933 "~/mail/september-1994" might be a reasonable folder name on a
10934 system running Unix.
10936 <P>
10937 Alpine users have the option of using folders that are stored on some other
10938 computer. Alpine accesses remote folders via IMAP (the Internet Message
10939 Access Protocol), or in the case of news, via NNTP (the Network News
10940 Transport Protocol). To be able to access remote folders in Alpine, the
10941 remote host must be running the appropriate server software (imapd or
10942 nntpd) and you must correctly specify the name of the folder to Alpine,
10943 including the domain name of the remote machine. For example,
10944 <P>
10945 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
10946 <P>
10947 could be a remote folder specification, and so could
10948 <P>
10949 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
10950 and
10951 <P>
10952 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
10953 <P>
10954 Note that in the case of remote folders, the directory/file path in the specification is
10955 determined by the operating system of the remote computer, <B>not</B> by
10956 the operating system of the computer on which you are running Alpine.
10957 <P>
10958 As you can tell, the name of the computer is in {} brackets
10959 followed immediately by the name of the folder. (In each of these cases the
10960 optional namespace is missing.) If, as in these
10961 examples, there is no remote access protocol specified, then IMAP is
10962 assumed. Check
10963 <A HREF="h_folder_server_syntax">here</A>
10964 for a more detailed look at what options can be placed between the brackets.
10965 If there are no brackets at all, then the folder name is interpreted locally
10966 on the computer on which you are running Alpine.
10968 <P>
10969 To the right of the brackets when a server name is present, or at the
10970 start of the foldername if no server is present, the sharp sign,
10971 "#", holds special meaning. It indicates a folder name
10972 outside the area reserved for your personal folders. In fact, it's
10973 used to indicate both the name of the folder, and a special phrase
10974 telling Alpine how to interpret the name that follows.
10976 <P>
10977 So, for example, Alpine can be used to access a newsgroup that might be
10978 available on your computer using:
10979 <P>
10980 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
10981 <P>
10982 The sharp sign indicates the folder name is outside your personal
10983 folder area. The "news." phrase after it tells Alpine to
10984 interpret the remainder of the name as a newsgroup.
10986 <P>
10987 Similarly, to access a newsgroup on your IMAP server, you might
10988 use something like:
10989 <P>
10990 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
10992 <P>
10993 There are a number of such special phrases (or "namespaces")
10994 available. For a more detailed explanation read about
10995 <A HREF="h_folder_name_namespaces">Namespaces</A>.
10997 <P>
10998 Note that "INBOX" has special meaning in both local and remote folder
10999 names. The name INBOX refers to your "principal incoming
11000 message folder" and will be mapped to the actual file name used for your
11001 INBOX on any given host. Therefore, a name like
11002 "{xxx.art.example.com}INBOX" refers to whatever file is used to
11003 store incoming mail for you on that particular host.
11005 <P>
11006 <End of help on this topic>
11007 </BODY>
11008 </HTML>
11009 ======= h_folder_name_namespaces =======
11010 <HTML>
11011 <HEAD>
11012 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
11013 </HEAD>
11014 <BODY>
11015 <H1>Folder Name Namespaces Explained</H1>
11017 An Alpine folder name looks like
11019 <P>
11020 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
11021 <P>
11023 The local part of a folder name has an optional "Namespace" which
11024 tells Alpine how to interpret the rest of the name.
11026 <P>
11027 By default the folder name is interpreted as defining a section of your personal
11028 folder area. This area and how you specify it are defined by the
11029 server, if one is specified, or, typically, the home
11030 directory, if no server is defined.
11032 <P>
11033 If a namespace is specified, it begins with the
11034 sharp, "#", character followed by the name of the namespace
11035 and then the namespace's path-element-delimiter. Aside from the
11036 path's format, namespaces can also imply access rights, content
11037 policy, audience, location, and, occasionally, access methods.
11039 <P>
11040 Each server exports its own set (possibly of size one) of
11041 namespaces. Hence, it's likely communication with your server's
11042 administrator will be required for specific configurations. Some of
11043 the more common namespaces, however, include:
11045 <DL>
11046 <DT>#news.</DT>
11047 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
11048 names are hierarchically defined with each level delimited by a period.
11049 <P>
11050 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11051 <P>
11052 </DD>
11053 <DT>#public/</DT>
11054 <DD>This specifies a folder area that the server may export to the general
11055 public.
11056 </DD>
11057 <DT>#shared/</DT>
11058 <DD>This specifies a folder area that the server may export to groups
11059 of users.
11060 </DD>
11061 <DT>#ftp/</DT>
11062 <DD>This specifies a folder area that is the same as that it may have
11063 exported via the "File Transfer Protocol".
11064 </DD>
11065 <DT>#mh/</DT>
11066 <DD>This specifies the personal folder area associated with folders
11067 and directories that were created using the MH message handling system.
11068 </DD>
11069 <DT>#move/</DT>
11070 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
11071 <P>
11072 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
11073 <P>
11074 The #move namespace is followed by two folder names separated by a delimiter
11075 character.
11076 The delimiter character may be any character that does not appear in
11077 the MailDropFolder name.
11078 The meaning of #move is that mail will be copied from the MailDropFolder to
11079 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
11080 Periodic checks at frequency
11081 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
11082 time between checks set by
11083 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
11084 are made for new mail arriving in the MailDropFolder.
11085 An example that copies mail from a POP inbox to a local folder follows
11086 <P>
11087 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
11088 <P>
11089 To you it appears that mail is being delivered to the local folder when it
11090 is copied from the MailDropFolder, and you read mail from the local folder.
11091 <P>
11092 Note that if the DestinationFolder does not exist then the messages are not
11093 copied from the MailDropFolder.
11094 A #move folder may only be used as an
11095 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
11096 an Inbox.
11097 When you are in the FOLDER LIST of Incoming Message Folders (after turning
11098 on the
11099 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
11100 option)
11101 the Add command has a subcommand "Use Mail Drop"
11102 which may be helpful for defining the folder in your Alpine configuration.
11103 The same is true when you edit the
11104 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
11105 option in Setup/Config.
11106 Each of these configuration methods will also create the DestinationFolder
11107 if it doesn't already exist.
11108 If you are having problems, make sure the DestinationFolder exists.
11109 You may find some more useful information about Mail Drops at
11110 <A HREF="h_maildrop">What is a Mail Drop?</A>.
11111 </DD>
11112 </DL>
11113 <P>
11115 In addition, the server may support access to other user's folders,
11116 provided you have suitable permissions. Common methods use a prefix
11117 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
11118 indicate the root of the other user's folder area.
11120 <P>
11121 No, nothing's simple.
11123 <P>
11124 <End of help on this topic>
11125 </BODY>
11126 </HTML>
11127 ============= h_whatis_vcard ========================
11128 <HTML>
11129 <HEAD>
11130 <TITLE>VCARD EXPLAINED</TITLE>
11131 </HEAD>
11132 <BODY>
11133 <H1>What is the vCard format?</H1>
11134 A "vCard" is a sort of electronic business card, for exchanging
11135 information about and among people and organizations electronically.
11136 More information about vCard can be found (as of May 1998) on the WWW site
11137 of the Internet Mail Consortium at the URL:
11138 <P>
11139 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
11140 <P>
11141 <End of help on this topic>
11142 </BODY>
11143 </HTML>
11144 ===== h_folder_open =====
11145 <HTML>
11146 <HEAD>
11147 <TITLE>Explanation of Folder Selection</TITLE>
11148 </HEAD>
11149 <BODY>
11150 <BR>
11151 <BR>
11152 This screen is designed to allow you to quickly and easily survey your
11153 folders and select one to open.
11154 <!--chtml if pinemode="function_key"-->
11155 <PRE>
11156 Navigating the List of Folders General Alpine Commands
11157 ------------------------------ -----------------------
11158 P Move to previous folder ? Show this help text
11159 N Move to next folder
11160 - Show previous screen of folders
11161 Spc (space bar) Show next screen
11162 W WhereIs (search folder names)
11164 Folder Selection Commands
11165 -------------------------
11166 E Exit the Folder Select menu (without selecting a folder)
11167 S Select the currently highlighted folder
11168 </PRE>
11169 <!--chtml else-->
11170 <PRE>
11171 Navigating the List of Folders General Alpine Commands
11172 ------------------------------ -----------------------
11173 F5 Move to previous folder F1 Show this help text
11174 F6 Move to next folder
11175 F7 Show previous screen of folders
11176 F8 Show next screen of folders
11177 F12 WhereIs (search folder names)
11179 Folder Selection Commands
11180 -------------------------
11181 F3 Exit the Folder Select menu (without selecting a folder)
11182 F4 Select the currently highlighted folder
11183 </PRE>
11184 <!--chtml endif-->
11185 <P>
11186 FOR MORE INFORMATION: See the section on
11187 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11188 <P>
11189 <End of help on this topic>
11190 </BODY>
11191 </HTML>
11192 ===== h_folder_subscribe =====
11193 <HTML>
11194 <HEAD>
11195 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
11196 </HEAD>
11197 <BODY>
11198 <H1>FOLDER SUBSCRIBE HELP</H1>
11200 This screen is designed to help you subscribe to newsgroups you are
11201 not currently subscribed to. The screen display is a list of all
11202 available newsgroups (or possibly a partial list if you specified a
11203 partial name when entering the screen). Groups you have already
11204 subscribed to have the letters "SUB" next to them. You may
11205 select a single new group to subscribe to by moving the cursor to that
11206 group and pressing "S" or carriage return. Alternatively,
11207 you may change into ListMode with the "ListMode" command.
11208 The display will change slightly so that each group has a checkbox in
11209 front of it. Use the cursor and the Set/Unset command to place an
11210 "X" in front of each newsgroup you wish to subscribe to.
11211 <P>
11213 When you are finished marking groups, the "Subscribe"
11214 command will subscribe you to those groups you have marked. Note, you
11215 may not unsubscribe to groups with this command. Instead of the
11216 "A" "Subscribe" command, use the "D"
11217 UnSbscrbe command.
11218 <P>
11220 <!--chtml if pinemode="function_key"-->
11221 <PRE>
11222 Navigating the List of Newsgroups General Alpine Commands
11223 --------------------------------- -----------------------
11224 F5 Move to previous group F1 Show this help text
11225 F6 Move to next group
11226 F7 Show previous screen of groups
11227 F8 Show next screen of groups
11228 F12 WhereIs (search group names)
11229 F9 Use ListMode
11231 Group Selection Commands
11232 -------------------------
11233 F3 Exit the News Subscribe menu (without selecting any groups)
11234 F4 Subscribe to the currently highlighted newsgroup
11235 </PRE>
11236 <!--chtml else-->
11237 <PRE>
11238 Navigating the List of Newsgroups General Alpine Commands
11239 --------------------------------- -----------------------
11240 P Move to previous group ? Show this help text
11241 N Move to next group
11242 - Show previous screen of groups
11243 Spc (space bar) Show next screen
11244 W WhereIs (search group names)
11245 L Use ListMode
11247 Group Selection Commands
11248 -------------------------
11249 E Exit the News Subscribe menu (without selecting any groups)
11250 S Subscribe to the currently highlighted newsgroup
11251 </PRE>
11252 <!--chtml endif-->
11253 <P>
11254 When in ListMode, there is an additional command for marking groups to
11255 subscribe to:
11256 <P>
11257 <!--chtml if pinemode="function_key"-->
11258 <PRE>
11259 ListMode Commands
11260 -------------------------
11261 F9 Set or unset the highlighted group
11262 </PRE>
11263 <!--chtml else-->
11264 <PRE>
11265 ListMode Commands
11266 -------------------------
11267 X Set or unset the highlighted group
11268 </PRE>
11269 <!--chtml endif-->
11270 <P>
11271 <End of help on this topic>
11272 </BODY>
11273 </HTML>
11274 ===== h_folder_postnews =====
11275 <HTML>
11276 <HEAD>
11277 <TITLE>Newsgroup selecting for Posting explained</TITLE>
11278 </HEAD>
11279 <BODY>
11280 This screen is designed to allow you to quickly and easily survey
11281 the available newsgroups and select one to post news to.
11282 <P>
11283 <!--chtml if pinemode="function_key"-->
11284 <PRE>
11285 Navigating the List of Newsgroups General Alpine Commands
11286 --------------------------------- -----------------------
11287 F5 Move to previous group F1 Show this help text
11288 F6 Move to next group
11289 F7 Show previous screen of groups
11290 F8 Show next screen of groups
11291 F12 WhereIs (search group names)
11293 Group Selection Commands
11294 -------------------------
11295 F3 Exit the Selection menu (without selecting a group)
11296 F4 Select the currently highlighted newsgroup
11297 </PRE>
11298 <!--chtml else-->
11299 <PRE>
11300 Navigating the List of Newsgroups General Alpine Commands
11301 --------------------------------- -----------------------
11302 P Move to previous group ? Show this help text
11303 N Move to next group
11304 - Show previous screen of groups
11305 Spc (space bar) Show next screen of groups
11306 W WhereIs (search group names)
11308 Group Selection Commands
11309 -------------------------
11310 E Exit the Selection menu (without selecting a group)
11311 S Select the currently highlighted newsgroup
11312 </PRE>
11313 <!--chtml endif-->
11314 <P>
11315 <End of help on this topic>
11316 </BODY>
11317 </HTML>
11318 ===== h_folder_save =====
11319 <HTML>
11320 <HEAD>
11321 <TITLE>Folder Select for Save Explained</TITLE>
11322 </HEAD>
11323 <BODY>
11324 This screen is designed to allow you to quickly and easily survey your
11325 folders and select one to use for saving the current message.
11326 <P>
11328 <!--chtml if pinemode="function_key"-->
11329 <PRE>
11330 Navigating the List of Folders General Alpine Commands
11331 ------------------------------ -----------------------
11332 F5 Move to previous folder F1 Show this help text
11333 F6 Move to next folder
11334 F7 Show previous screen of folders
11335 F8 Show next screen of folders
11336 F12 WhereIs (search folder names)
11338 Folder Selection Commands
11339 -------------------------
11340 F3 Exit the Folder Select menu (without selecting a folder)
11341 F4 Select the currently highlighted folder
11342 F11 AddNew folder (just like Select, but you type in a new folder name)
11343 </PRE>
11344 <!--chtml else-->
11345 <PRE>
11346 Navigating the List of Folders General Alpine Commands
11347 ------------------------------ -----------------------
11348 P Move to previous folder ? Show this help text
11349 N Move to next folder
11350 - Show previous screen of folders
11351 Spc (space bar) Show next screen of folders
11352 W WhereIs (search folder names)
11354 Folder Selection Commands
11355 -------------------------
11356 E Exit the Folder Select menu (without selecting a folder)
11357 S Select the currently highlighted folder
11358 A AddNew folder (just like Select, but you type in a new folder name)
11359 </PRE>
11360 <!--chtml endif-->
11361 <P>
11362 FOR MORE INFORMATION: See the section on
11363 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11364 <P>
11365 <End of help on this topic>
11366 </BODY>
11367 </HTML>
11368 ===== h_folder_fcc =====
11369 <HTML>
11370 <HEAD>
11371 <TITLE>Folder Select for Fcc Explained</TITLE>
11372 </HEAD>
11373 <BODY>
11374 This screen is designed to allow you to quickly and easily survey your
11375 folders and select one to use as the file carbon copy (fcc) for the
11376 current message.
11377 <P>
11379 <!--chtml if pinemode="function_key"-->
11380 <PRE>
11381 Navigating the List of Folders General Alpine Commands
11382 ------------------------------ -----------------------
11383 F5 Move to previous folder F1 Show this help text
11384 F6 Move to next folder
11385 F7 Show previous screen of folders
11386 F8 Show next screen of folders
11387 F12 WhereIs (search folder names)
11389 Folder Selection Commands
11390 -------------------------
11391 F3 Exit the Folder Select menu (without selecting a folder)
11392 F4 Select the currently highlighted folder
11393 F11 AddNew folder (just like Select, but you type in a new folder name)
11394 </PRE>
11395 <!--chtml else-->
11396 <PRE>
11397 Navigating the List of Folders General Alpine Commands
11398 ------------------------------ -----------------------
11399 P Move to previous folder ? Show this help text
11400 N Move to next folder
11401 - Show previous screen of folders
11402 Spc (space bar) Show next screen of folders
11403 W WhereIs (search folder names)
11405 Folder Selection Commands
11406 -------------------------
11407 E Exit the Folder Select menu (without selecting a folder)
11408 S Select the currently highlighted folder
11409 A AddNew folder (just like Select, but you type in a new folder name)
11410 </PRE>
11411 <!--chtml endif-->
11412 <P>
11413 FOR MORE INFORMATION: See the section on
11414 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11415 <P>
11416 <End of help on this topic>
11417 </BODY>
11418 </HTML>
11419 ===== h_folder_pattern_roles =====
11420 <HTML>
11421 <HEAD>
11422 <TITLE>Folder Select for Current Folder Explained</TITLE>
11423 </HEAD>
11424 <BODY>
11425 This screen is designed to allow you to quickly and easily survey your
11426 folders and select one to use as the specific Current Folder
11427 in a Pattern.
11428 <P>
11430 <!--chtml if pinemode="function_key"-->
11431 <PRE>
11432 Navigating the List of Folders General Alpine Commands
11433 ------------------------------ -----------------------
11434 F5 Move to previous folder F1 Show this help text
11435 F6 Move to next folder
11436 F7 Show previous screen of folders
11437 F8 Show next screen of folders
11438 F12 WhereIs (search folder names)
11440 Folder Selection Commands
11441 -------------------------
11442 F3 Exit the Folder Select menu (without selecting a folder)
11443 F4 Select the currently highlighted folder
11444 F11 AddNew folder (just like Select, but you type in a new folder name)
11445 </PRE>
11446 <!--chtml else-->
11447 <PRE>
11448 Navigating the List of Folders General Alpine Commands
11449 ------------------------------ -----------------------
11450 P Move to previous folder ? Show this help text
11451 N Move to next folder
11452 - Show previous screen of folders
11453 Spc (space bar) Show next screen of folders
11454 W WhereIs (search folder names)
11456 Folder Selection Commands
11457 -------------------------
11458 E Exit the Folder Select menu (without selecting a folder)
11459 S Select the currently highlighted folder
11460 A AddNew folder (just like Select, but you type in a new folder name)
11461 </PRE>
11462 <!--chtml endif-->
11463 <P>
11464 FOR MORE INFORMATION: See the section on
11465 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11466 <P>
11467 <End of help on this topic>
11468 </BODY>
11469 </HTML>
11470 ===== h_folder_stayopen_folders =====
11471 <HTML>
11472 <HEAD>
11473 <TITLE>Folder Select Explained</TITLE>
11474 </HEAD>
11475 <BODY>
11476 This screen is designed to allow you to quickly and easily survey your
11477 folders and select one to use as a Stay-Open folder.
11478 <P>
11480 <!--chtml if pinemode="function_key"-->
11481 <PRE>
11482 Navigating the List of Folders General Alpine Commands
11483 ------------------------------ -----------------------
11484 F5 Move to previous folder F1 Show this help text
11485 F6 Move to next folder
11486 F7 Show previous screen of folders
11487 F8 Show next screen of folders
11488 F12 WhereIs (search folder names)
11490 Folder Selection Commands
11491 -------------------------
11492 F3 Exit the Folder Select menu (without selecting a folder)
11493 F4 Select the currently highlighted folder
11494 F11 AddNew folder (just like Select, but you type in a new folder name)
11495 </PRE>
11496 <!--chtml else-->
11497 <PRE>
11498 Navigating the List of Folders General Alpine Commands
11499 ------------------------------ -----------------------
11500 P Move to previous folder ? Show this help text
11501 N Move to next folder
11502 - Show previous screen of folders
11503 Spc (space bar) Show next screen of folders
11504 W WhereIs (search folder names)
11506 Folder Selection Commands
11507 -------------------------
11508 E Exit the Folder Select menu (without selecting a folder)
11509 S Select the currently highlighted folder
11510 A AddNew folder (just like Select, but you type in a new folder name)
11511 </PRE>
11512 <!--chtml endif-->
11513 <P>
11514 FOR MORE INFORMATION: See the section on
11515 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11516 <P>
11517 <End of help on this topic>
11518 </BODY>
11519 </HTML>
11520 ===== h_folder_action_roles =====
11521 <HTML>
11522 <HEAD>
11523 <TITLE>Folder Select Explained</TITLE>
11524 </HEAD>
11525 <BODY>
11526 This screen is designed to allow you to quickly and easily survey your
11527 folders and select one to use as the folder into which messages
11528 matching this filter will be moved.
11529 <P>
11531 <!--chtml if pinemode="function_key"-->
11532 <PRE>
11533 Navigating the List of Folders General Alpine Commands
11534 ------------------------------ -----------------------
11535 F5 Move to previous folder F1 Show this help text
11536 F6 Move to next folder
11537 F7 Show previous screen of folders
11538 F8 Show next screen of folders
11539 F12 WhereIs (search folder names)
11541 Folder Selection Commands
11542 -------------------------
11543 F3 Exit the Folder Select menu (without selecting a folder)
11544 F4 Select the currently highlighted folder
11545 F11 AddNew folder (just like Select, but you type in a new folder name)
11546 </PRE>
11547 <!--chtml else-->
11548 <PRE>
11549 Navigating the List of Folders General Alpine Commands
11550 ------------------------------ -----------------------
11551 P Move to previous folder ? Show this help text
11552 N Move to next folder
11553 - Show previous screen of folders
11554 Spc (space bar) Show next screen of folders
11555 W WhereIs (search folder names)
11557 Folder Selection Commands
11558 -------------------------
11559 E Exit the Folder Select menu (without selecting a folder)
11560 S Select the currently highlighted folder
11561 A AddNew folder (just like Select, but you type in a new folder name)
11562 </PRE>
11563 <!--chtml endif-->
11564 <P>
11565 FOR MORE INFORMATION: See the section on
11566 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11567 <P>
11568 <End of help on this topic>
11569 </BODY>
11570 </HTML>
11571 ===== h_abook_config =====
11572 <HTML>
11573 <HEAD>
11574 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11575 </HEAD>
11576 <BODY>
11577 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11578 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11579 <!--chtml if pinemode="function_key"-->
11580 <PRE>
11581 Available Commands
11582 -------------------------------
11583 F1 Show Help Text
11584 F3 Back to MAIN Alpine menu
11585 F4 Change configuration for address book
11586 F5 Move to previous address book
11587 F6 Move to next address book
11588 F7 Previous page of address books
11589 F8 Next page of address books
11590 F9 Add new address book
11591 F10 Delete existing address book
11592 F11 Shuffle the order of address books
11593 F12 Whereis (search address book titles)
11594 </PRE>
11595 <!--chtml else-->
11596 <PRE>
11597 Navigation General Alpine Commands
11598 ----------------------- -----------------------
11599 P Prev Address Book ? Display this help text
11600 N Next Address Book E Back to MAIN Alpine menu
11601 - Previous page
11602 Spc (space bar) Next page
11603 W WhereIs (search for word in address book titles)
11605 Setup Address Books Commands
11606 ------------------------------------------------
11607 A Add new address book $ Shuffle the order of address books
11608 D Delete existing address book C Change configuration for address book
11609 </PRE>
11610 <!--chtml endif-->
11612 <H2>Description of the Setup Address Books Screen</H2>
11614 This screen lets you add, delete, modify, or change the order of your
11615 address books. The "Add Abook" command brings up a blank form to
11616 fill in. If you are adding a remote address book on an IMAP server
11617 you should fill in the name of the IMAP server. Otherwise, leave
11618 that field blank. (Note that remote IMAP address books are an Alpine
11619 concept and are unlikely to interoperate with other mail clients.)
11620 For a remote address book, fill in the name of the remote folder
11621 in the Folder field. This should be a folder that is used only for
11622 this one purpose, not a general purpose folder you expect to store
11623 messages in.
11624 <P>If you are adding a local address book, fill in the
11625 Folder Name field with a local file name (e.g., .addressbook).
11626 <P>
11627 <B>Please note:</B> Remote address books stored on an IMAP server are
11628 of an entirely different format (namely, a special-purpose
11629 "mail folder") than that of the local addressbook familiar
11630 to Alpine users. Therefore,
11631 you cannot use "add a remote address book" to make an existing
11632 Alpine .addressbook file you may have on a remote IMAP server accessible to
11633 Alpine running on a different host.
11634 <P>
11636 The "Del Abook" command allows you to remove an address book
11637 from your configuration. It will also ask you if you wish to remove
11638 the data for that address book, which would erase all traces of the
11639 address book if you answer Yes.
11640 <P>
11642 The "Change" command is similar to the "Add Abook" command.
11643 The difference is that instead of adding a new address book to your
11644 configuration, you are changing the configuration of an existing entry.
11645 For example, you might want to correct a typing error or change a
11646 nickname. The "Change" command is not a move command. If you
11647 change the folder name or server name the data will not be moved for you.
11648 <P>
11650 The "Shuffle" command is used for two purposes. If you shuffle
11651 an address book toward another address book in the same group then
11652 the order of those two address books will be swapped. If you shuffle
11653 the last Personal address book down towards the Global address book
11654 section, it will become a Global address book. If you shuffle
11655 the first Global address book up it will become a Personal address
11656 book. The main difference between Personal and Global address
11657 books is that Global address books are forced read-only.
11658 <P><UL>
11659 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11660 </UL>
11661 <P>
11662 <End of help on this topic>
11663 </BODY>
11664 </HTML>
11665 ===== h_abook_top =====
11666 <HTML>
11667 <HEAD>
11668 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11669 </HEAD>
11670 <BODY>
11671 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11672 <!--chtml if pinemode="function_key"-->
11673 <PRE>
11674 Available Commands -- Group 1 Available Commands -- Group 2
11675 ------------------------------- ------------------------------
11676 F1 Show Help Text F1 Show Help Text
11677 F2 See commands in next group F2 See commands in next group
11678 F3 Exit to MAIN MENU F3 Quit Alpine
11679 F4 View/Edit selected address book
11680 F5 Move to previous address book F5 FOLDER LIST screen
11681 F6 Move to next address book F6 Specify a folder to go to
11682 F7 Previous page F7 MESSAGE INDEX screen
11683 F8 Next page F9 Print list of address books
11684 F12 Whereis (search for word)
11685 </PRE>
11686 <!--chtml else-->
11687 <PRE>
11688 Navigation General Alpine Commands
11689 ----------------------- -----------------------
11690 P Previous Entry ? Display this help text
11691 N Next Entry O Show all other available commands
11692 - Previous page < Back to MAIN Alpine menu
11693 Spc (space bar) Next page Q Quit Alpine
11694 W WhereIs (search for word) L FOLDER LIST screen
11695 G Specify a folder to go to
11696 Address Book Commands I MESSAGE INDEX screen
11697 ------------------------------------------------
11698 > View/Edit selected address book
11699 or
11700 > Search on selected directory server
11702 % Print list of address books and directory servers
11703 </PRE>
11704 <!--chtml endif-->
11706 <H2>Description of the Address Book List Screen</H2>
11708 From this screen you may choose which address book you wish to view
11709 or edit. For more information on address books, view one of your
11710 address books (with
11711 <!--chtml if pinemode="function_key"-->
11712 F4
11713 <!--chtml else-->
11714 ">"
11715 <!--chtml endif-->)
11716 and see the Help Text there.<P>
11718 You may also choose a directory server on which to search for entries.
11719 You do that by highlighting the directory server line and using
11720 <!--chtml if pinemode="function_key"-->
11721 F4
11722 <!--chtml else-->
11723 ">"
11724 <!--chtml endif-->.<P>
11726 If you wish to define new address books or directory servers go to the Main
11727 menu and choose Setup. You may then either choose to setup AddressBooks or
11728 Directory (among other things). It's possible that the Directory option
11729 will not be there if the Alpine you are using does not contain LDAP directory
11730 lookup functionality.
11732 <P><UL>
11733 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11734 </UL><P>
11735 <End of help on this topic>
11736 </BODY>
11737 </HTML>
11738 ===== h_abook_opened =====
11739 <HTML>
11740 <HEAD>
11741 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
11742 </HEAD>
11743 <BODY>
11744 <H1>THE ALPINE ADDRESS BOOK</H1>
11745 <H2>ADDRESS BOOK COMMANDS</H2>
11746 <PRE>
11747 <!--chtml if pinemode="function_key"-->
11748 Available Commands -- Group 1 Available Commands -- Group 2
11749 ------------------------------- ------------------------------
11750 F1 Show Help Text F1 Show Help Text
11751 F2 See commands in next group F2 See commands in next group
11752 F3 Exit this screen F3 Quit Alpine
11753 F4 View/Edit selected entry F4 Go to MAIN MENU screen
11754 F5 Move to previous entry F5 FOLDER LIST screen
11755 F6 Move to next entry F6 Specify a folder to go to
11756 F7 Previous page of address book F7 MESSAGE INDEX screen
11757 F8 Next page of address book F8 Compose to entry using roles
11758 F9 Add new entry to address book F9 Print address book
11759 F10 Delete selected entry F10 TakeAddr to another addrbook
11760 F11 Compose to selected entry F11 Save or Export addrbook selections
11761 F12 Whereis (search address book) F12 Forward entry by mail
11763 Available Commands -- Group 3
11764 ------------------------------
11765 F3 Select F6 Zoom (or unZoom)
11766 F5 Select Current F7 Apply Command to Selection
11767 <!--chtml else-->
11768 Address Book Navigation General Alpine Commands
11769 ----------------------- -----------------------
11770 P Prev Address ? Display this help text
11771 N Next Address O Show all other available commands
11772 - Previous page of address book M Back to MAIN MENU
11773 Spc (space bar) Next page Q Quit Alpine
11774 W WhereIs (search for word C Compose message to selected addr
11775 or name in address book) # Compose to addr using roles
11776 < To List of Address Books if L FOLDER LIST screen
11777 more than one, else to MAIN G Specify a folder to go to
11778 I MESSAGE INDEX screen
11780 Address Book Commands
11781 ----------------------------------------------------
11782 > View/Update selected entry D Delete selected entries
11783 % Print address book S Save or Export address book selections
11784 F Forward entries by mail @ Add new entry to address book
11786 ; Select command Z Toggle Zoom Mode
11787 : Select highlighted entry A Apply command to selected entries
11789 <!--chtml endif-->
11790 </PRE>
11791 Note: The presence or absence of the final four commands above is
11792 controlled by the option
11793 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
11794 <P>
11796 <H2>Description of the Address Book Screen</H2>
11798 This screen lets you edit and manage entries in your address book. It
11799 also acts as a short-cut for composing messages to people in the address
11800 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
11801 message starts "pre-addressed" to whatever address book entry is
11802 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
11803 role to use in your composition.
11804 <P>
11805 Alpine's address book helps you keep a list of addresses you send email to so
11806 you do not have to remember addresses that are often complex. Each entry
11807 in the address book has five fields, all of them optional. The three
11808 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
11810 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
11811 This is what you type in as you are addressing the message in the
11812 composer. If there is a matching entry in your address book(s),
11813 Alpine will extract the corresponding FullName and Address fields to
11814 generate the actual address for your message.
11816 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
11817 of the
11818 person or organization. Usually the full names are put in last
11819 name first so they sort nicely in alphabetical order. Whatever
11820 you put as the name here will appear on the message when it is
11821 finally delivered. Examples:<PRE>
11822 Garcia Marquez, Gabriel
11823 Henscheid, Eckhard
11824 Alpine-Info mailing list
11825 Library materials renewal requests
11826 Kim An-guk
11827 "George III, King of Great Britain, 1738-1820"
11828 </PRE>
11829 (In the second-to-last example, no comma is used in the name so that
11830 the family name appears first in the address book and when the entry is
11831 used in the composer.
11832 In the last example, retaining the commas is intended;
11833 double-quotation marks surround the name to
11834 prevent the transposition of its parts when the entry is used in
11835 the composer.)
11837 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
11838 a valid Internet address that conforms to the Internet message
11839 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
11841 The two fields that aren't usually visible are:<DL>
11843 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
11844 message to this address to be saved in. If this field is set, and
11845 this address is the first one in the message's To: header, then
11846 Alpine will use this folder name for the FCC in lieu of the normal
11847 FCC folder name.
11849 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
11850 </DL>
11851 <P>
11852 Due to screen width limitations, these last two fields do not show up in
11853 the normal ADDRESS BOOK display. You may select the
11854 "View/Update" command to
11855 view or modify them. You may use the configuration variable
11856 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
11857 to add these fields to your ADDRESS BOOK
11858 display, or to modify the format of the display.
11860 <H2>Sorting the Address book</H2>
11862 By default, address book entries are sorted alphabetically on the full
11863 name with distribution lists sorted to the end. Sorting can be changed by
11864 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
11865 --assuming you have "write" permission for the address book file.
11866 <P>
11867 Unlike the sorting of folders (which only changes presentation), sorting an
11868 address book actually changes the file as it is kept on the computer. For
11869 this reason you won't be able to sort a shared or system-wide address
11870 book.
11872 <H2>Adding New Entries</H2>
11874 The easiest way to add new entries to your address book is to use the
11875 "TakeAddr" command when viewing a message.
11876 This command allows you to take addresses from the header and body of the
11877 message and put them into your address book, without having to type
11878 them in.
11879 <P>
11881 To manually add a new entry from within the address book screen, use the AddNew
11882 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
11883 Use this command both for adding a simple alias and for adding a
11884 distribution list.
11886 <H2>Distribution Lists</H2>
11888 Address book entries can be simple cases of aliases (a single nickname is linked
11889 to a single email address) or distribution lists (a single nickname
11890 pointing at more than one email address). Each distribution list has a
11891 nickname, a full name and a list of addresses. The addresses may be
11892 actual addresses or they may be other nicknames in your address book.
11893 They may even refer to other distribution lists.
11894 There's really no difference between a simple alias and a distribution list,
11895 other than the number of addresses.
11896 Therefore, you can turn a simple alias with one address into a distribution
11897 list simply by adding more addresses.
11898 To add entries to an existing list or alias
11899 use the View/Update (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->) command. Delete (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->"D"<!--chtml endif-->) will delete
11900 a single address from the list if the cursor is placed on the address;
11901 it will delete the entire distribution list if the cursor is on the
11902 nickname/fullname line. View/Update may also be used to delete addresses
11903 from a list.
11904 <P>
11905 Address field entries in distribution lists may take any one of three
11906 forms: a nickname existing in any of the defined address books, a normal
11907 address of the form "jsmith@art.example.com", or a complete
11908 fullname/address combination, e.g. "John Smith
11909 <jsmith@art.example.com>".
11910 <P>
11911 Distribution lists in Alpine address books can only be used by the person or
11912 people who have access to that address book. They are not usually used to
11913 implement discussion groups, but can be used to facilitate small
11914 discussion groups if all the participants have access to the same shared
11915 address book.
11917 <H2>FCC and Comments</H2>
11919 As mentioned above, each entry in the address book also has two other optional
11920 fields, Fcc and Comments. The command to look at or change either of these
11921 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
11922 Comments field is just for your own use. The Fcc field overrides the
11923 default Fcc if this address is the first one on the To line. The WhereIs
11924 command may be used to search for particular strings in the address book,
11925 including fields that are not visible (like Comment and Fcc by default).
11927 <H2>Aggregate Operations</H2>
11929 If the feature
11930 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
11931 is turned on (the default), then the four commands "Select",
11932 "Select Current", "Zoom", and "Apply"
11933 are available. The two selection commands allow you to mark a set of
11934 address book entries as being selected. If you have more than one address
11935 book, the selections may be in more than one of those address books.
11936 The "Zoom" command will toggle between displaying only the selected
11937 entries and all of the entries. The "Apply" command allows you to
11938 apply one of the regular address book commands to all of the selected
11939 entries. Usually the address book commands apply to only the entry
11940 highlighted by the cursor. The "Apply" command works with the
11941 commands "ComposeTo", "Delete", "Print",
11942 "Save", "Forward", and "Role".
11944 <H2>Exporting and Forwarding Address book entries</H2>
11946 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
11947 address book entry is placed in a plain text file in your home directory
11948 <!--chtml if pinemode="running"-->
11949 (which, in the present configuration of your system, is
11950 "<!--#echo var="HOME_DIR"-->")
11951 <!--chtml endif-->
11952 or current working directory
11953 <!--chtml if pinemode="running"-->
11954 (which, at least for your current Alpine "session,"
11955 is "<!--#echo var="CURRENT_DIR"-->")
11956 <!--chtml endif-->, depending on the
11957 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
11958 configuration setting. If you have some entries selected and use the
11959 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
11960 placed in the text file.
11961 <P>
11962 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
11963 address book entry is placed in a special attachment and you are put into
11964 the composer. You can fill in some comments in the body of the message,
11965 if you'd like, and send it to somebody else who uses Alpine. The recipient
11966 may use the TakeAddr command on that message to insert the address book
11967 entry you sent in their own address book. If you have some entries
11968 selected and use the Apply Forward command all of the selected entries
11969 will be forwarded in a single message. You may
11970 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
11971 The recipient must be using Alpine in order to receive this correctly.
11972 One way for the recipient to handle this might be to create an empty
11973 address book and then "Take" your forwarded address book entries into
11974 that empty address book.
11976 <H2>Multiple and/or Site-Wide Address books</H2>
11978 You may have more than one personal address book. In addition, there may
11979 be one or more global address books. This capability allows you to have
11980 multiple personal address books (some of which may be shared) and it also
11981 allows system administrators to implement site-wide address books that
11982 contain entries for users on multiple machines within the organization.
11983 <P><DL>
11984 <DT>Searching
11985 <DD> If you enter a nickname when composing a message, your
11986 personal address books will be searched through in order, and then the
11987 global address book(s) searched. If more than one address book has an entry
11988 for the nickname, Alpine uses the first one that it finds, so an entry in
11989 your personal address book would override a global address book entry. If
11990 after searching all the address books there is still no match, (Unix) Alpine
11991 then searches the local host password file on the assumption that you have
11992 entered a local user name rather than an address book nickname.
11993 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
11994 command, but global address books are always searched after personal
11995 address books.
11997 <P><DT>Tab completion
11998 <DD> If the
11999 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
12000 feature is turned on (the default) then the Tab key may be used
12001 in the composer to complete partially typed nicknames in the To
12002 or Cc lines. You type the first few letters of a nickname and then
12003 press the Tab key. It there is only one nickname that matches it will
12004 be filled in by Alpine. If there is more than one the unambiguous part
12005 of the nicknames will be filled in. For example, if your address book or
12006 books contains only the two entries "barley" and "barbecue"
12007 beginning with the letters "ba", then if you type "ba"
12008 followed by a Tab character Alpine will fill in "bar" and stop.
12009 If you then type a second Tab character you will be presented with a list
12010 of matching nicknames to select from. Alternatively, you could type another
12011 "b" resulting in "barb" and then a Tab would fill
12012 in the entire "barbecue" entry.
12014 <P><DT>Defining
12015 <DD> You define multiple personal address books in the
12016 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
12017 from the MAIN MENU.
12018 You may add as many as you like. Global address books are usually
12019 site-wide address books defined by the System administrator, but
12020 you may define global address books of your own just like you define
12021 personal address books.
12023 <P><DT>Creating and updating
12024 <DD> Personal address books are normally created empty
12025 and populated by explicit additions from within Alpine, e.g. via the
12026 TakeAddr command. Unlike personal address books, global address books may
12027 not be modified/updated from within Alpine; that is, they are Read-Only.
12028 Thus, global address books are created, populated and updated outside of
12029 Alpine. They might be hand-edited, generated by a program from another
12030 database, or by copying an existing address book. They might also be
12031 some other user's personal address book, and so be modified normally by
12032 that user but accessed Read-Only by you. See the Alpine Technical
12033 Notes document (included in the Alpine distribution) for more information on
12034 this.
12036 <P><DT>Accessing
12037 <DD>There are two different types of address books in Alpine.
12038 A local address book is stored in a regular file and the normal file
12039 access permissions apply. A remote address book is stored on an IMAP
12040 server in a special folder that contains only messages pertaining to
12041 that address book. The last message in the remote folder contains a
12042 copy of the address book data, and that data is copied to a local cache
12043 file in your home directory. From there it is accessed just like a local
12044 address book. The name of the cache file is kept track of in a special
12045 file called the
12046 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
12047 the name of which is stored in
12048 your Alpine configuration file the first time you use a remote address book.
12049 Just as local Alpine address books use a format that only Alpine understands,
12050 remote Alpine address books do the same and other mail reading programs
12051 are unlikely to be able to understand them.<P>
12052 While global address books are explicitly intended to be shared, there is
12053 nothing to prevent you from sharing a personal address book with other
12054 Alpine users. This might be useful in the case of a small workgroup.
12055 However, it is recommended that updates to shared personal address books
12056 be done when other Alpine users are not accessing the address book. Alpine
12057 does not do any file-locking to manage concurrent updates to the
12058 addressbook, but it does check to see if the file has been modified before
12059 making any changes. Consequently, inadvertent concurrent updates will
12060 only cause other Alpine users to have to restart their address book
12061 operation, which will cause Alpine to reopen the updated file.
12063 <P><DT>Converting to Remote
12064 <DD>The easiest way to convert an existing local
12065 address book into a remote address book is to create an empty new remote
12066 personal address book by typing "A" to execute the
12067 "Add Pers Abook" command in the SETUP Addressbook screen.
12068 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
12069 address book.
12070 After you have added the empty
12071 remote address book, go into the screen for the address book you wish
12072 to copy and "Select" "All".
12073 This selects every entry in that
12074 address book. Then type the command "Apply Save".
12075 You will be asked for the address book to save to. You may use ^P and ^N
12076 to get to the new empty address book, then hit RETURN and the addresses
12077 will be copied.
12078 At this point you'll probably want to unselect all the entries in the local
12079 address book before proceeding. You do that with
12080 "Select" "unselect All".
12082 </DL>
12083 <UL>
12084 <LI><A HREF="h_address_format">Explanation of Address formats</A>
12085 </UL>
12086 <P><UL>
12087 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12088 </UL>
12089 <P>
12090 <End of help on this topic>
12091 </BODY>
12092 </HTML>
12093 ===== h_abook_select_addr =====
12094 <HTML>
12095 <HEAD>
12096 <TITLE>Addressbook Selection Explained</TITLE>
12097 </HEAD>
12098 <BODY>
12099 <H1>SELECT ADDRESS</H1>
12100 <!--chtml if pinemode="function_key"-->
12101 <PRE>
12102 Navigating the List of Messages General Alpine Commands
12103 ------------------------------- -----------------------
12104 F5 Move to previous entry F1 Show this help text
12105 F6 Move to next entry
12106 F7 Show previous screen of address book
12107 F8 Show next screen of address book
12108 F12 WhereIs (search through address book)
12110 Address Selection Commands
12111 --------------------------
12112 F3 Exit the Address Select screen (without selecting an address)
12113 F4 Select the currently highlighted entry
12114 </PRE>
12115 <!--chtml else-->
12116 <PRE>
12117 Navigating the List of Messages General Alpine Commands
12118 ------------------------------- -----------------------
12119 P Move to previous entry ? Show this help text
12120 N Move to next entry
12121 - Show previous screen of address book
12122 Spc (space bar) Show next screen of address book
12123 W WhereIs (search through address book)
12125 Address Selection Commands
12126 --------------------------
12127 E Exit the Address Select screen (without selecting an address)
12128 S Select the currently highlighted entry
12129 </PRE>
12130 <!--chtml endif-->
12131 <P>
12133 This screen is designed to let you easily scan your address book(s) in
12134 order to select an entry for the message you are composing. You cannot
12135 edit your address book in any way at this time, for address book
12136 maintenance, select the address book command when not composing a message.
12137 <P>
12139 If you are composing a message and know the nickname of the person/list you
12140 want, you can bypass this screen by simply typing in the nickname on the
12141 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12142 selecting an entry does not cancel your message.
12143 <P>
12145 FOR MORE INFORMATION on addressing see
12146 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12147 <A HREF="h_abook_opened">Address Book Screen's</A>
12148 help text.
12149 <P>
12150 <End of help on this topic>
12151 </BODY>
12152 </HTML>
12153 ===== h_abook_select_top =====
12154 <HTML>
12155 <HEAD>
12156 <TITLE>Addressbook Selection Navigation Explained</TITLE>
12157 </HEAD>
12158 <BODY>
12159 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
12160 <!--chtml if pinemode="function_key"-->
12161 <PRE>
12162 Navigating the List of Address Books General Alpine Commands
12163 ------------------------------------ -----------------------
12164 F4 View the highlighted address book
12165 F5 Move to previous address book F1 Show this help text
12166 F6 Move to next address book
12167 F7 Show previous screen of address books
12168 F8 Show next screen of address books
12169 F12 WhereIs (search through address books)
12171 Address Selection Commands
12172 --------------------------
12173 F3 Exit the Address Select screen (without selecting an address)
12174 F4 Select the currently selected entries (if using ListMode)
12175 F9 Change to ListMode
12176 </PRE>
12177 <!--chtml else-->
12178 <PRE>
12179 Navigating the List of Address Books General Alpine Commands
12180 ------------------------------------ -----------------------
12181 > View the highlighted address book
12182 P Move to previous address book ? Show this help text
12183 N Move to next address book
12184 - Show previous screen of address books
12185 Spc (space bar) Show next screen of address books
12186 W WhereIs (search through address books)
12188 Address Selection Commands
12189 --------------------------
12190 E Exit the Address Select screen (without selecting an address)
12191 S Select the currently selected entries (if using ListMode)
12192 L Change to ListMode
12193 </PRE>
12194 <!--chtml endif-->
12195 <P>
12197 This screen is designed to let you easily scan your address book(s) in
12198 order to select entries for the message you are composing. You cannot
12199 edit your address book in any way at this time. For address book
12200 maintenance, select the address book command when not composing a message.
12201 <P>
12203 If you are composing a message and know the nickname of the person/list you
12204 want, you can bypass this screen by simply typing in the nickname on the
12205 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12206 selecting an entry does not cancel your message.
12207 <P>
12209 The ListMode command will add a column at the left edge of the screen.
12210 You mark the entries that you wish to select with the "X" command.
12211 This allows you to choose more than one entry at a time.
12212 <P>
12214 An alternative method of composing a message to entries in your
12215 address book(s) is to first use the "Select" command from
12216 the address book maintenance screen and then the "Apply"
12217 "ComposeTo" command to start the composer composing to the
12218 selected entries.
12219 <P>
12221 FOR MORE INFORMATION on addressing see
12222 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12223 <A HREF="h_abook_opened">Address Book Screen's</A>
12224 help text.
12225 <P>
12226 <End of help on this topic>
12227 </BODY>
12228 </HTML>
12229 ===== h_abook_select_listmode =====
12230 <HTML>
12231 <HEAD>
12232 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
12233 </HEAD>
12234 <BODY>
12235 <H1>COMPOSER: SELECT ADDRESSES</H1>
12236 <!--chtml if pinemode="function_key"-->
12237 <PRE>
12238 Navigating the List of Messages General Alpine Commands
12239 ------------------------------- -----------------------
12240 F5 Move to previous entry F1 Show this help text
12241 F6 Move to next entry
12242 F7 Show previous screen of address book
12243 F8 Show next screen of address book
12244 F12 WhereIs (search through address book)
12246 Address Selection Commands
12247 --------------------------
12248 F3 Exit the Address Select screen (without selecting an address)
12249 F4 Select the currently highlighted entry
12250 F9 Change to ListMode
12251 </PRE>
12252 <!--chtml else-->
12253 <PRE>
12254 Navigating the List of Messages General Alpine Commands
12255 ------------------------------- -----------------------
12256 P Move to previous entry ? Show this help text
12257 N Move to next entry
12258 - Show previous screen of address book
12259 Spc (space bar) Show next screen of address book
12260 W WhereIs (search through address book)
12262 Address Selection Commands
12263 --------------------------
12264 E Exit the Address Select screen (without selecting an address)
12265 S Select the currently highlighted entry
12266 L Change to ListMode
12267 </PRE>
12268 <!--chtml endif-->
12269 <P>
12271 This screen is designed to let you easily scan your address book(s) in
12272 order to select entries for the message you are composing. You cannot
12273 edit your address book in any way at this time, for address book
12274 maintenance, select the address book command when not composing a message.
12275 <P>
12277 If you are composing a message and know the nickname of the person/list you
12278 want, you can bypass this screen by simply typing in the nickname on the
12279 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12280 selecting an entry does not cancel your message.
12281 <P>
12283 The ListMode command will add a column at the left edge of the screen.
12284 You mark the entries that you wish to select with the "X" command.
12285 This allows you to choose more than one entry at a time.
12286 <P>
12288 An alternative method of composing a message to entries in your
12289 address book(s) is to first use the "Select" command from
12290 the address book maintenance screen and then the "Apply"
12291 "ComposeTo" command to start the composer composing to the
12292 selected entries.
12293 <P>
12295 FOR MORE INFORMATION on addressing see
12296 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12297 <A HREF="h_abook_opened">Address Book Screen's</A>
12298 help text.
12299 <P>
12300 <End of help on this topic>
12301 </BODY>
12302 </HTML>
12303 ===== h_abook_select_checks =====
12304 <HTML>
12305 <HEAD>
12306 <TITLE>Address Selection from Composer Explained</TITLE>
12307 </HEAD>
12308 <BODY>
12309 <H1>COMPOSER: SELECT ADDRESSES</H1>
12310 <!--chtml if pinemode="function_key"-->
12311 <PRE>
12312 Navigating the List of Messages General Alpine Commands
12313 ------------------------------- -----------------------
12314 F5 Move to previous entry F1 Show this help text
12315 F6 Move to next entry
12316 F7 Show previous screen of address book
12317 F8 Show next screen of address book
12318 F12 WhereIs (search through address book)
12320 Address Selection Commands
12321 --------------------------
12322 F3 Exit the Address Select screen (without selecting an address)
12323 F4 Select the currently highlighted entry
12324 F8 Either Sets or Unsets all entries in this address book
12325 F9 Set or Unset the highlighted entry
12326 </PRE>
12327 <!--chtml else-->
12328 <PRE>
12329 Navigating the List of Messages General Alpine Commands
12330 ------------------------------- -----------------------
12331 P Move to previous entry ? Show this help text
12332 N Move to next entry
12333 - Show previous screen of address book
12334 Spc (space bar) Show next screen of address book
12335 W WhereIs (search through address book)
12337 Address Selection Commands
12338 --------------------------
12339 E Exit the Address Select screen (without selecting an address)
12340 S Select the currently highlighted entry
12341 X Set or Unset the highlighted entry
12342 A Either Sets or Unsets all entries in this address book
12343 </PRE>
12344 <!--chtml endif-->
12345 <P>
12347 Mark the entries you wish to select with the "X Set/Unset"
12348 command. Type "S Select" to select all of the entries you
12349 have marked, just as if you had typed them in by hand.
12350 <P>
12352 An alternative method of composing a message to entries in your
12353 address book(s) is to first use the "Select" command from
12354 the address book maintenance screen and then the "Apply"
12355 "ComposeTo" command to start the composer composing to the
12356 selected entries.
12357 <P>
12359 FOR MORE INFORMATION on addressing see
12360 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12361 <A HREF="h_abook_opened">Address Book Screen's</A>
12362 help text.
12363 <P>
12364 <End of help on this topic>
12365 </BODY>
12366 </HTML>
12367 ===== h_abook_select_nicks_take =====
12368 <HTML>
12369 <HEAD>
12370 <TITLE>Take Address Nickname Selection Explained</TITLE>
12371 </HEAD>
12372 <BODY>
12373 <H1>TAKEADDR: SELECT NICKNAME</H1>
12374 <!--chtml if pinemode="function_key"-->
12375 <PRE>
12376 Navigating the List of Messages General Alpine Commands
12377 ------------------------------- -----------------------
12378 F5 Move to previous entry F1 Show this help text
12379 F6 Move to next entry
12380 F7 Show previous screen of address book
12381 F8 Show next screen of address book
12382 F12 WhereIs (search through address book)
12384 Message Selection Commands
12385 --------------------------
12386 F3 Exit the Nickname Select screen (without selecting an address)
12387 F4 Select the currently highlighted entry
12388 </PRE>
12389 <!--chtml else-->
12390 <PRE>
12391 Navigating the List of Messages General Alpine Commands
12392 ------------------------------- -----------------------
12393 P Move to previous entry ? Show this help text
12394 N Move to next entry
12395 - Show previous screen of address book
12396 Spc (space bar) Show next screen of address book
12397 W WhereIs (search through address book)
12399 Message Selection Commands
12400 --------------------------
12401 E Exit the Nickname Select screen (without selecting an address)
12402 S Select the currently highlighted entry
12403 </PRE>
12404 <!--chtml endif-->
12405 <P>
12407 This screen is designed to let you modify or add to an existing
12408 address book entry. You have already selected the name(s) and
12409 address(es) through "Take Address". This screen simply lets
12410 you scan your address books and select the nickname to be
12411 changed/augmented. If you want to add a new entry, then you are in
12412 the wrong place-- Select "Exit" command.
12413 <P>
12415 FOR MORE INFORMATION on addressing see
12416 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12417 <A HREF="h_abook_opened">Address Book Screen's</A>
12418 help text.
12419 <P>
12420 <End of help on this topic>
12421 </BODY>
12422 </HTML>
12423 ===== h_abook_select_nick =====
12424 <HTML>
12425 <HEAD>
12426 <TITLE>Nickname Selection Explained</TITLE>
12427 </HEAD>
12428 <BODY>
12429 <H1>SELECT NICKNAME</H1>
12430 <!--chtml if pinemode="function_key"-->
12431 <PRE>
12432 Navigating the List of Messages General Alpine Commands
12433 ------------------------------- -----------------------
12434 F5 Move to previous entry F1 Show this help text
12435 F6 Move to next entry
12436 F7 Show previous screen of address book
12437 F8 Show next screen of address book
12438 F12 WhereIs (search through address book)
12440 Message Selection Commands
12441 --------------------------
12442 F3 Exit the Nickname Select screen (without selecting an address)
12443 F4 Select the currently highlighted entry
12444 </PRE>
12445 <!--chtml else-->
12446 <PRE>
12447 Navigating the List of Messages General Alpine Commands
12448 ------------------------------- -----------------------
12449 P Move to previous entry ? Show this help text
12450 N Move to next entry
12451 - Show previous screen of address book
12452 Spc (space bar) Show next screen of address book
12453 W WhereIs (search through address book)
12455 Message Selection Commands
12456 --------------------------
12457 E Exit the Nickname Select screen (without selecting an address)
12458 S Select the currently highlighted entry
12459 </PRE>
12460 <!--chtml endif-->
12461 <P>
12463 This screen is designed to let you look at the nicknames in your address
12464 books before choosing a new one.
12465 <P>
12467 FOR MORE INFORMATION on addressing see
12468 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12469 <A HREF="h_abook_opened">Address Book Screen's</A>
12470 help text.
12471 <P>
12472 <End of help on this topic>
12473 </BODY>
12474 </HTML>
12475 ===== h_takeaddr_screen =====
12476 <HTML>
12477 <HEAD>
12478 <TITLE>Take Address Screen Explained</TITLE>
12479 </HEAD>
12480 <BODY>
12481 <H1>TAKE ADDRESS COMMANDS</H1>
12482 <!--chtml if pinemode="function_key"-->
12483 <PRE>
12484 Navigating the List of Addresses Address Selection Commands
12485 -------------------------------- --------------------------
12486 F5 Move to previous entry F3 Exit without taking address
12487 F6 Move to next entry F4 Take current address(es)
12488 F7 Show previous page of address list
12489 F8 Show next page of address list
12490 F2 WhereIs (search list)
12491 --------------
12492 Mode Toggle F9 Set/Unset current address
12493 ----------- F10 Set all
12494 F12 Toggle between List and single mode F11 Unset all
12495 </PRE>
12496 <!--chtml else-->
12497 <PRE>
12498 Navigating the List of Addresses Address Selection Commands
12499 -------------------------------- --------------------------
12500 P Move to previous entry < Exit without taking address
12501 N Move to next entry T Take address
12502 - Show previous page of address list
12503 Spc (space bar) Show next page of address list
12504 W WhereIs (search list) List Mode
12505 ---------
12506 Single Mode X Set/Unset current address
12507 ----------- A Set all addresses
12508 L Switch to list mode U Unset all addresses
12509 S Switch to single mode
12510 </PRE>
12511 <!--chtml endif-->
12513 <H2>Description of the Take Address Screen</H2>
12515 This screen is designed to let you select one or more address/name
12516 combinations from the current message and put them into your address book.
12517 The cursor is initially placed on the line with the message author.
12518 Other lines include the names of people and/or mailing lists who also
12519 received the message. Other people "involved" in the
12520 message (e.g. the person named as Reply-To:) are also listed here.
12521 <P>
12523 The simple case is adding a new, single entry into your address book. To
12524 do this, simply highlight the correct line and press
12525 <!--chtml if pinemode="function_key"-->
12526 F4.
12527 <!--chtml else-->
12528 "T".
12529 <!--chtml endif-->
12530 To create a new list or add to an existing list, switch the screen display
12531 into List Mode by pressing
12532 <!--chtml if pinemode="function_key"-->
12533 F12.
12534 <!--chtml else-->
12535 "L".
12536 <!--chtml endif-->
12537 In List Mode, you select the
12538 group of addresses you wish to manipulate by marking them with an
12539 "X".
12540 The Set/Unset
12541 <!--chtml if pinemode="function_key"-->
12542 (F9)
12543 <!--chtml else-->
12544 ("X")
12545 <!--chtml endif-->
12546 command will turn the "X" on for the
12547 highlighted address if it was off or turn it off if it was previously on.
12548 The SetAll command will select all of the addresses, and the UnSetAll
12549 command will turn off all the selections. Once you've gotten the
12550 selection the way you want it, you may create a new list by pressing
12551 <!--chtml if pinemode="function_key"-->
12552 F4.
12553 <!--chtml else-->
12554 "T".
12555 <!--chtml endif-->
12556 <P>
12558 In both the simple and list cases, after choosing to take the address,
12559 you will be asked for the nickname of the entry. Typing in a new name
12560 creates the new entry/list. Entering an existing nickname will replace
12561 the entry (simple case) or add to the list (list case). Alternatively,
12562 you can press Ctrl-T at the nickname prompt and select an existing
12563 nickname from your address book.
12564 <P>
12566 You will normally start in Single Mode, unless you used the Apply command
12567 to startup the TakeAddr screen, in which case you will start in List Mode.
12568 You may switch between the two modes at any time. If you've already
12569 selected several addresses in List Mode, those will be remembered when you
12570 switch to Single Mode and then back to List Mode. The set of addresses
12571 that are pre-selected when you start in List Mode are the From addresses
12572 of all of the messages you are operating on. You may, of course, easily
12573 erase those selections with the UnSetAll command.
12574 <P>
12576 If you have more than one writable address book, you will be prompted for
12577 the name of the address book you wish to add the new entry to before
12578 anything else. You can use ^N and ^P to choose among the defined address
12579 books, or type in the address book name.
12580 <P>
12582 FOR MORE INFORMATION on addressing see
12583 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12584 <A HREF="h_abook_opened">Address Book Screen's</A>
12585 help text.
12586 <P>
12587 <End of help on this topic>
12588 </BODY>
12589 </HTML>
12590 ===== h_takeexport_screen =====
12591 <HTML>
12592 <HEAD>
12593 <TITLE>Take Export Screen Explained</TITLE>
12594 </HEAD>
12595 <BODY>
12596 <H1>TAKE EXPORT COMMANDS</H1>
12597 <!--chtml if pinemode="function_key"-->
12598 <PRE>
12599 Navigating the List of Addresses Address Selection Commands
12600 -------------------------------- --------------------------
12601 F5 Move to previous entry F3 Exit without taking address
12602 F6 Move to next entry F4 Take current address(es)
12603 F7 Show previous page of address list
12604 F8 Show next page of address list
12605 F2 WhereIs (search list)
12606 --------------
12607 Mode Toggle F9 Set/Unset current address
12608 ----------- F10 Set all
12609 F12 Toggle between List and single mode F11 Unset all
12610 </PRE>
12611 <!--chtml else-->
12612 <PRE>
12613 Navigating the List of Addresses Address Selection Commands
12614 -------------------------------- --------------------------
12615 P Move to previous entry < Exit without taking address
12616 N Move to next entry T Take address
12617 - Show previous page of address list
12618 Spc (space bar) Show next page of address list
12619 W WhereIs (search list) List Mode
12620 ---------
12621 Single Mode X Set/Unset current address
12622 ----------- A Set all addresses
12623 L Switch to list mode U Unset all addresses
12624 S Switch to single mode
12625 </PRE>
12626 <!--chtml endif-->
12628 <H2>Description of the Take Export Screen</H2>
12630 This screen is designed to let you select one or more addresses
12631 from the current message and put them into a file.
12632 Only the user@domain_name part of each address is put into the file.
12633 <P>
12635 To put a single entry into a file simply highlight the correct line and press
12636 <!--chtml if pinemode="function_key"-->
12637 F4.
12638 <!--chtml else-->
12639 "T".
12640 <!--chtml endif-->
12641 To put more than one entry into a file
12642 switch the screen display
12643 into List Mode by pressing
12644 <!--chtml if pinemode="function_key"-->
12645 F12.
12646 <!--chtml else-->
12647 "L".
12648 <!--chtml endif-->
12649 In List Mode, you select the
12650 group of addresses you wish to manipulate by marking them with an
12651 "X".
12652 The Set/Unset
12653 <!--chtml if pinemode="function_key"-->
12654 (F9)
12655 <!--chtml else-->
12656 ("X")
12657 <!--chtml endif-->
12658 command will turn the "X" on for the
12659 highlighted address if it was off or turn it off if it was previously on.
12660 The SetAll command will select all of the addresses, and the UnSetAll
12661 command will turn off all the selections. Once you've gotten the
12662 selection the way you want it, you may put the addresses in a file by typing
12663 <!--chtml if pinemode="function_key"-->
12664 F4.
12665 <!--chtml else-->
12666 "T".
12667 <!--chtml endif-->
12668 <P>
12670 You will be asked for the name of a file to put the addresses in.
12671 If the file already exists, you will be asked whether you want to Overwrite
12672 (replace) the contents of the file or Append to the contents of the file.
12673 <P>
12675 <End of help on this topic>
12676 </BODY>
12677 </HTML>
12678 ============= h_abook_view ========================
12679 <HTML>
12680 <HEAD>
12681 <TITLE>Address Book View Explained</TITLE>
12682 </HEAD>
12683 <BODY>
12684 This function allows you to view the contents of an address book entry. You
12685 can only view one entry at a time.
12686 <P>
12687 <DL>
12688 <DT>Help
12689 <!--chtml if pinemode="function_key"-->
12690 (F1)
12691 <!--chtml else-->
12692 (?)
12693 <!--chtml endif-->
12694 </DT>
12695 <DD>
12696 Display this help text.
12698 <DT>Abook
12699 <!--chtml if pinemode="function_key"-->
12700 (F3)
12701 <!--chtml else-->
12702 (<)
12703 <!--chtml endif-->
12704 </DT>
12705 <DD>
12706 Go back to index of address book entries.
12708 <DT>Update
12709 <!--chtml if pinemode="function_key"-->
12710 (F4)
12711 <!--chtml else-->
12712 (U)
12713 <!--chtml endif-->
12714 </DT>
12715 <DD>
12716 Update (modify) this entry.
12718 <DT>ComposeTo
12719 <!--chtml if pinemode="function_key"-->
12720 (F5)
12721 <!--chtml else-->
12722 (C)
12723 <!--chtml endif-->
12724 </DT>
12725 <DD>Compose a message to the address(es) in this entry.
12727 <DT>Role
12728 <!--chtml if pinemode="function_key"-->
12729 (F6)
12730 <!--chtml else-->
12731 (#)
12732 <!--chtml endif-->
12733 </DT>
12734 <DD>Compose a message to the address(es) in this entry using roles.
12736 <DT>Prev Page
12737 <!--chtml if pinemode="function_key"-->
12738 (F7)
12739 <!--chtml else-->
12740 (-)
12741 <!--chtml endif-->
12742 </DT>
12743 <DD>
12744 Show the previous page of the current entry.
12746 <DT>Next Page
12747 <!--chtml if pinemode="function_key"-->
12748 (F8)
12749 <!--chtml else-->
12750 (Space)
12751 <!--chtml endif-->
12752 </DT>
12753 <DD>
12754 Show the next page of the current entry.
12756 <DT>Print
12757 <!--chtml if pinemode="function_key"-->
12758 (F9)
12759 <!--chtml else-->
12760 (%)
12761 <!--chtml endif-->
12762 </DT>
12763 <DD>Print the current entry. You can select the
12764 printer or the print command via the "Setup" command
12765 on the MAIN MENU.
12767 <DT>WhereIs
12768 <!--chtml if pinemode="function_key"-->
12769 (F10)
12770 <!--chtml else-->
12771 (W)
12772 <!--chtml endif-->
12773 </DT>
12774 <DD>Search the entry for a string of letters. If it is
12775 found, move to it. The string can be one word or a phrase.
12776 If there are multiple occurrences, the cursor moves to the
12777 first occurrence beyond the current cursor position.
12779 <DT>Fwd Email
12780 <!--chtml if pinemode="function_key"-->
12781 (F11)
12782 <!--chtml else-->
12783 (F)
12784 <!--chtml endif-->
12785 </DT>
12786 <DD>Begin composition of a new mail message with the displayed
12787 text already inserted in the message body.
12789 </DL>
12790 <P>
12791 <End of help on this topic>
12792 </BODY>
12793 </HTML>
12794 ============= h_ldap_view ========================
12795 <HTML>
12796 <HEAD>
12797 <TITLE>LDAP Response View Explained</TITLE>
12798 </HEAD>
12799 <BODY>
12800 This function allows you to view the contents of a directory entry. You
12801 can only view one entry at a time.
12802 <P>
12803 <DL>
12804 <DT>Help
12805 <!--chtml if pinemode="function_key"-->
12806 (F1)
12807 <!--chtml else-->
12808 (?)
12809 <!--chtml endif-->
12810 </DT>
12811 <DD>
12812 Display this help text.
12814 <DT>Results Index
12815 <!--chtml if pinemode="function_key"-->
12816 (F3)
12817 <!--chtml else-->
12818 (<)
12819 <!--chtml endif-->
12820 </DT>
12821 <DD>Go back to index of search results.
12823 <DT>ComposeTo
12824 <!--chtml if pinemode="function_key"-->
12825 (F5)
12826 <!--chtml else-->
12827 (C)
12828 <!--chtml endif-->
12829 </DT>
12830 <DD>Compose a message to the address(es) in this entry.
12832 <DT>Role
12833 <!--chtml if pinemode="function_key"-->
12834 (F6)
12835 <!--chtml else-->
12836 (#)
12837 <!--chtml endif-->
12838 </DT>
12839 <DD>Compose a message to the address(es) in this entry using roles.
12841 <DT>Prev Page
12842 <!--chtml if pinemode="function_key"-->
12843 (F7)
12844 <!--chtml else-->
12845 (-)
12846 <!--chtml endif-->
12847 </DT>
12848 <DD>
12849 Show the previous page of the current entry.
12851 <DT>Next Page
12852 <!--chtml if pinemode="function_key"-->
12853 (F8)
12854 <!--chtml else-->
12855 (Space)
12856 <!--chtml endif-->
12857 </DT>
12858 <DD>
12859 Show the next page of the current entry.
12861 <DT>Print
12862 <!--chtml if pinemode="function_key"-->
12863 (F9)
12864 <!--chtml else-->
12865 (%)
12866 <!--chtml endif-->
12867 </DT>
12868 <DD>Print the current entry on paper. You can select the
12869 printer or the print command via the "Setup" command
12870 on the MAIN MENU.
12872 <DT>WhereIs
12873 <!--chtml if pinemode="function_key"-->
12874 (F10)
12875 <!--chtml else-->
12876 (W)
12877 <!--chtml endif-->
12878 </DT>
12879 <DD>Search the entry for a string of letters. If it is
12880 found, move to it. The string can be one word or a phrase.
12881 If there are multiple occurrences, the cursor moves to the
12882 first occurrence beyond the current cursor position.
12884 <DT>Fwd Email
12885 <!--chtml if pinemode="function_key"-->
12886 (F11)
12887 <!--chtml else-->
12888 (F)
12889 <!--chtml endif-->
12890 </DT>
12891 <DD>Begin composition of a new mail message with the displayed
12892 text already inserted in the message body.
12894 <DT>Save
12895 <!--chtml if pinemode="function_key"-->
12896 (F12)
12897 <!--chtml else-->
12898 (S)
12899 <!--chtml endif-->
12900 </DT>
12901 <DD>Save the displayed entry to one of your address books or export
12902 it to a file.
12903 </DL>
12904 <P>
12905 <End of help on this topic>
12906 </BODY>
12907 </HTML>
12908 ===== h_attachment_screen =====
12909 <HTML>
12910 <HEAD>
12911 <TITLE>Attachment Index Screen Explained</TITLE>
12912 </HEAD>
12913 <BODY>
12914 The "ATTACHMENT INDEX" displays a list of the current
12915 message's attachments, and allows various operations on them. The
12916 first attachment is usually the message text, but does not include the
12917 header portion of the message.
12918 <P>
12919 Available commands include:
12920 <P>
12921 <DL>
12923 <DT>Help</DT>
12924 <DD>Show this help text.
12926 <DT>Msg #<I>num</I></DT>
12927 <DD>Leave this screen without displaying or saving any attachments.
12929 <DT>View</DT>
12930 <DD>View the currently selected attachment.
12932 <DT>Prev Attach</DT>
12933 <DD>Move to previous attachment.
12935 <DT>Next Attach</DT>
12936 <DD>Move to next attachment.
12938 <DT>Prev Page</DT>
12939 <DD>Previous page of the listed attachments.
12941 <DT>Next Page</DT>
12942 <DD>Next page of the listed attachments.
12944 <DT>Delete</DT>
12945 <DD>Mark the currently selected attachment for Deletion.
12946 This does not modify the current message by deleting the attachment from
12947 it, but instead the delete flag <EM>only</EM> has an effect when saving
12948 the message to a folder.
12949 Attachments marked for deletion are not copied to the destination folder
12950 along with the rest of the message when it is saved.
12951 It is ok for the destination folder to be the same as the current folder.
12952 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
12954 <DT>Undelete</DT>
12955 <DD>Turn off the Delete flag for the selected attachment.
12957 <DT>Save</DT>
12958 <DD>Save the selected attachment to a file. If the attachment is of
12959 type "RFC822/Message", then the attachment will be saved to
12960 the specified mail folder.
12962 <DT>Export</DT>
12963 <DD>If the attachment is of
12964 type "RFC822/Message", then "Export" is used to
12965 copy the message to a file in the same way this command works on
12966 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
12968 <DT>Pipe</DT>
12969 <DD>Pipe the attachment contents into a UNIX command (if enabled).
12970 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
12972 <DT>WhereIs</DT>
12973 <DD>Find a matching string in the attachment list.
12975 <DT>AboutAttch</DT>
12976 <DD>Examine various aspects of the selected attachment.
12978 <DT>Print</DT>
12979 <DD>Print the selected attachment.
12981 <DT>Forward</DT>
12982 <DD>Forward the selected attachment as an attachment.
12983 </DL>
12985 <P>
12987 All attachments can be saved or piped into a UNIX command, but some may
12988 not be readily displayed by either Alpine or an external tool. In such
12989 cases, the reason why the message cannot be displayed is displayed on
12990 Alpine's message line.
12991 <P>
12992 <End of help on this topic>
12993 </BODY>
12994 </HTML>
12995 ============= h_mail_text_att_view ========================
12996 <HTML>
12997 <HEAD>
12998 <TITLE>Attachment View Screen Explained</TITLE>
12999 </HEAD>
13000 <BODY>
13001 This function allows you to view the contents of a text attachment. You
13002 can only view one attachment at a time.
13003 <P>
13004 Available commands include:
13005 <P>
13006 <DL>
13008 <DT>Help</DT>
13009 <DD>Display this help text
13011 <DT>AttchIndex</DT>
13012 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
13014 <DT>Prev Page</DT>
13015 <DD>Show the previous page of the current attachment.
13017 <DT>Next Page</DT>
13018 <DD>Show the next page of the current attachment by pressing the space bar.
13020 <DT>Delete</DT>
13021 <DD>Mark the viewed attachment for Deletion. The delete
13022 flag <EM>only</EM> has affect when saving the message to a folder.
13023 Attachments marked for deletion are exluded from the messsage when
13024 it is saved. In addition, the delete mark <EM>only</EM> applies to
13025 this Alpine session.
13027 <DT>Undelete</DT>
13028 <DD>Turn off the Delete flag for the selected attachment.
13030 <DT>Save</DT>
13031 <DD>Copy the current attachment to a file. If you just enter
13032 a filename, the attachment will be saved with that name in
13033 your home directory
13034 <!--chtml if pinemode="running"-->
13035 (which, in the present configuration of your system, is
13036 "<!--#echo var="HOME_DIR"-->")
13037 <!--chtml endif-->
13038 or current working directory
13039 <!--chtml if pinemode="running"-->
13040 (which, at least for your current Alpine "session,"
13041 is "<!--#echo var="CURRENT_DIR"-->")
13042 <!--chtml endif-->, depending on the
13043 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13044 configuration setting. You may enter the full
13045 path and filename to save it in another directory instead.
13047 <DT>Export</DT>
13048 <DD>If the attachment is of
13049 type "RFC822/Message", then "Export" is used to
13050 copy the message to a file in the same way this command works on
13051 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13052 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
13053 defined, they may affect the contents of the exported file.)
13055 <DT>Pipe</DT>
13056 <DD>Pipe the attachment contents into a UNIX command (if enabled)
13058 <DT>WhereIs</DT>
13059 <DD>Search the attachment for a string of letters. If it is
13060 found, move to it. The string can be one word or a phrase.
13061 If there are multiple occurrences, the cursor moves to the
13062 first occurrence beyond the current cursor position.
13064 <DT>Print</DT>
13065 <DD>Print the current attachment on paper. You can select the
13066 printer or the print command via the "Setup" command
13067 on the MAIN MENU.
13069 <DT>Forward</DT>
13070 <DD>Forward the selected attachment as an attachment.
13071 </DL>
13072 <P>
13073 <End of help on this topic>
13074 </BODY>
13075 </HTML>
13076 ============= h_journal ==============
13077 <HTML>
13078 <HEAD>
13079 <TITLE>Recent Message Journal Explained</TITLE>
13080 </HEAD>
13081 <BODY>
13083 The following commands are available on this screen:
13084 <P>
13085 <DL>
13086 <DT>Help</DT>
13087 <DD>Show this help text
13089 <DT>Exit</DT>
13090 <DD>Exit Viewer, and go back to mail processing
13092 <DT>Prev Page</DT>
13093 <DD>Show the previous page text
13095 <DT>Next Page</DT>
13096 <DD>Show the next page of text by pressing the space bar
13098 <DT>Print</DT>
13099 <DD>Print the displayed text on paper. You can select the
13100 printer or the print command via the "Setup" command
13101 on the MAIN MENU.
13103 <DT>Fwd Email</DT>
13104 <DD>Begin composition of a new mail message with the displayed
13105 text already inserted in the message body.
13107 <DT>Save</DT>
13108 <DD>Copy the displayed text to a file. If you just enter
13109 a filename, the text will be saved with that name in
13110 your
13111 home directory
13112 <!--chtml if pinemode="running"-->
13113 (which, in the present configuration of your system, is
13114 "<!--#echo var="HOME_DIR"-->")
13115 <!--chtml endif-->
13116 or current working directory
13117 <!--chtml if pinemode="running"-->
13118 (which, at least for your current Alpine "session,"
13119 is "<!--#echo var="CURRENT_DIR"-->")
13120 <!--chtml endif-->, depending on the
13121 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13122 configuration setting. You may enter the full
13123 path and filename to save it in another directory instead.
13125 <DT>WhereIs</DT>
13126 <DD>Search the text for a string of letters. If it is
13127 found, move to it. The string can be one word or a phrase.
13128 If there are multiple occurrences, the cursor moves to the
13129 first occurrence beyond the current cursor position.
13130 </DL>
13131 <P>
13132 <End of help on this topic>
13133 </BODY>
13134 </HTML>
13135 ============= h_debugjournal ==============
13136 <HTML>
13137 <HEAD>
13138 <TITLE>Debug Journal Explained</TITLE>
13139 </HEAD>
13140 <BODY>
13142 The following commands are available on this screen:
13143 <P>
13144 <DL>
13145 <DT>Help</DT>
13146 <DD>Show this help text
13148 <DT>Exit</DT>
13149 <DD>Exit Viewer, and go back to mail processing
13151 <DT>Timestamps</DT>
13152 <DD>Turn on or off timestamps.
13154 <DT>DebugView</DT>
13155 <DD>Set the level of debugging you want to see. The level may be any number
13156 in the range 0-9. Higher numbers show more debugging detail. Note that the
13157 debugging information has already been captured. This setting just causes the
13158 debugging information that you see to be filtered. If you set this to
13159 the number "5" then you will be shown all of the debugging information
13160 at levels 5 and below.
13161 It's actually a bit more complicated than that. A fixed amount of memory
13162 is used to store the debug information.
13163 Since the amount of memory used is limited the debugging information
13164 has to be trimmed back when it gets too large.
13166 <DT>Prev Page</DT>
13167 <DD>Show the previous page text
13169 <DT>Next Page</DT>
13170 <DD>Show the next page of text by pressing the space bar
13172 <DT>Print</DT>
13173 <DD>Print the displayed text on paper. You can select the
13174 printer or the print command via the "Setup" command
13175 on the MAIN MENU.
13177 <DT>Fwd Email</DT>
13178 <DD>Begin composition of a new mail message with the displayed
13179 text already inserted in the message body.
13181 <DT>Save</DT>
13182 <DD>Copy the displayed text to a file. If you just enter
13183 a filename, the text will be saved with that name in
13184 your
13185 home directory
13186 <!--chtml if pinemode="running"-->
13187 (which, in the present configuration of your system, is
13188 "<!--#echo var="HOME_DIR"-->")
13189 <!--chtml endif-->
13190 or current working directory
13191 <!--chtml if pinemode="running"-->
13192 (which, at least for your current Alpine "session,"
13193 is "<!--#echo var="CURRENT_DIR"-->")
13194 <!--chtml endif-->, depending on the
13195 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13196 configuration setting. You may enter the full
13197 path and filename to save it in another directory instead.
13199 <DT>WhereIs</DT>
13200 <DD>Search the text for a string of letters. If it is
13201 found, move to it. The string can be one word or a phrase.
13202 If there are multiple occurrences, the cursor moves to the
13203 first occurrence beyond the current cursor position.
13204 </DL>
13205 <P>
13206 <End of help on this topic>
13207 </BODY>
13208 </HTML>
13209 ============= h_simple_text_view ==============
13210 <HTML>
13211 <HEAD>
13212 <TITLE>Simple Text View Screen Explained</TITLE>
13213 </HEAD>
13214 <BODY>
13216 The following commands are available on this screen:
13217 <P>
13218 <DL>
13219 <DT>Help</DT>
13220 <DD>Show this help text
13222 <DT>Exit</DT>
13223 <DD>Exit Viewer, and go back to mail processing
13225 <DT>Prev Page</DT>
13226 <DD>Show the previous page text
13228 <DT>Next Page</DT>
13229 <DD>Show the next page of text by pressing the space bar
13231 <DT>Print</DT>
13232 <DD>Print the displayed text on paper. You can select the
13233 printer or the print command via the "Setup" command
13234 on the MAIN MENU.
13236 <DT>Fwd Email</DT>
13237 <DD>Begin composition of a new mail message with the displayed
13238 text already inserted in the message body.
13240 <DT>Save</DT>
13241 <DD>Copy the displayed text to a file. If you just enter
13242 a filename, the attachment will be saved with that name in
13243 your
13244 home directory
13245 <!--chtml if pinemode="running"-->
13246 (which, in the present configuration of your system, is
13247 "<!--#echo var="HOME_DIR"-->")
13248 <!--chtml endif-->
13249 or current working directory
13250 <!--chtml if pinemode="running"-->
13251 (which, at least for your current Alpine "session,"
13252 is "<!--#echo var="CURRENT_DIR"-->")
13253 <!--chtml endif-->, depending on the
13254 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13255 configuration setting. You may enter the full
13256 path and filename to save it in another directory instead.
13258 <DT>WhereIs</DT>
13259 <DD>Search the attachment for a string of letters. If it is
13260 found, move to it. The string can be one word or a phrase.
13261 If there are multiple occurrences, the cursor moves to the
13262 first occurrence beyond the current cursor position.
13263 </DL>
13264 <P>
13265 <End of help on this topic>
13266 </BODY>
13267 </HTML>
13268 ======= h_pine_for_windows ========
13269 <HTML>
13270 <HEAD>
13271 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
13272 </HEAD>
13273 <BODY>
13274 <H1>Getting Help In PC-Alpine</H1>
13276 <P>
13277 PC-Alpine offers general and specific help text. From the <A
13278 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
13279 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
13280 specific help for that screen is available from the toolbar Help menu or
13281 with the
13282 <!--chtml if pinemode="function_key"-->
13283 "F1" key.
13284 <!--chtml else-->
13285 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
13286 typing "?" would be mistaken as entering text.
13287 <!--chtml endif-->
13289 <P>
13290 Although this version of Alpine is for Microsoft Windows, it is not
13291 considered a full "Graphical User Interface" application.
13292 Yet, many of the controls that Windows users are accustomed to seeing,
13293 such as scrollbars and toolbars, are available.
13295 <P>
13296 PC-Alpine offers considerable mouse support. You can view what is
13297 "click-able" by dragging your mouse over any screen; when the
13298 arrow cursor changes into a hand, you found something. Mouse-click
13299 possibilities include navigating between screens and folders and
13300 double-clicking on hyperlinks to open your Web browser.
13301 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
13302 screen. Examples of right-click options include "copy" after
13303 selecting text to copy and "View in New Window" when you click
13304 on a particular message in the Message Index. The menu choices available
13305 to you will vary based upon what screen is open, where on the screen your
13306 cursor is located, and even what action you have already taken.
13308 <P>
13309 <End of help on this topic>
13310 </BODY>
13311 </HTML>
13312 ===== h_composer =====
13313 <HTML>
13314 <HEAD>
13315 <TITLE>COMPOSER COMMANDS</TITLE>
13316 </HEAD>
13317 <BODY>
13318 <H1>COMPOSER COMMANDS</H1>
13320 CURSOR MOTION KEYS |EDITING KEYS<BR>
13321 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13322 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13323 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
13324 ^N (Down Arrow) Next line | <!--chtml if pinemode="function_key"-->F9<!--chtml else-->^K<!--chtml endif--> <A HREF="h_compose_markcutpaste">Cut</A> marked text or<BR>
13325 ^A Beginning of line | delete current line<BR>
13326 ^E End of line | <!--chtml if pinemode="function_key"-->F10<!--chtml else-->^U<!--chtml endif--> <A HREF="h_compose_markcutpaste">Paste</A> text, undelete lines<BR>
13327 ^Y Previous page | cut with ^K, or unjustify<BR>
13328 ^V Next page |-------------------------------------<BR>
13329 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13330 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
13331 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
13332 <!--chtml if pinemode="function_key"-->F3<!--chtml else-->^C<!--chtml endif--> <A HREF="h_compose_cancel">Cancel</A> | <!--chtml if pinemode="function_key"-->F1<!--chtml else-->^G<!--chtml endif--> Get help | <!--chtml if pinemode="function_key"-->F4<!--chtml else-->^J<!--chtml endif--> <A HREF="h_compose_justify">Justify</A> paragraph<BR>
13333 <!--chtml if pinemode="function_key"-->F11<!--chtml else-->^O <!--chtml endif--> <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13334 <!--chtml if pinemode="function_key"-->F2<!--chtml else-->^X<!--chtml endif--> <A HREF="h_compose_send">Send</A> | <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^_<!--chtml endif--> <A HREF="h_compose_alted">Alt. editor</A> | <!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif--> <A HREF="h_compose_readfile">Read in a file</A><BR>
13336 <P>
13337 NOTE:
13338 <OL>
13339 <LI>For help on a particular command, highlight the bold text associated
13340 with it above and hit Return.
13341 <LI> The availability of certain commands
13342 is determined by Alpine configuration files and system capabilities.
13343 At some sites, certain commands may not be available due to security or
13344 support concerns.
13345 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13346 Ctrl-\, ESC.
13347 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13348 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13349 </OL>
13351 <P>
13352 HINT: To move rapidly to the bottom of a message you are composing,
13353 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
13354 with the Mark and Cut commands to eliminate large amounts of unwanted
13355 text in a Reply.
13357 <H2>Description of Composer</H2>
13359 Alpine has a built-in editing program that allows you to compose messages
13360 without having to leave Alpine. The editor is designed to be very simple to
13361 use so that you can get started writing email right away.
13363 <P>
13364 Messages are usually just text, about 80 columns wide. Using upper and
13365 lower case is encouraged. On some systems the size limit of the message
13366 is about 100,000 characters, which is about 2,000 lines. You can include
13367 punctuation and special characters found on most keyboards, but you can't
13368 include characters with diacritical marks and certain special symbols.
13370 <P>
13371 Text automatically wraps as you type past the end of a line so you do not
13372 have to hit return. Using the
13373 "<A HREF="h_compose_justify">Justify</A>" command,
13374 you can also reformat text explicitly, perhaps after you have
13375 deleted some text.
13377 <P>
13378 You can include other text files with the
13379 "<A HREF="h_compose_readfile">Read File</A>" command,
13380 which will prompt you for the name of the file to insert at the
13381 current cursor postion.
13383 <P>
13384 <UL>
13385 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13386 </UL>
13387 <P>
13388 <End of help on this topic>
13389 </BODY>
13390 </HTML>
13391 ====== h_composer_browse =====
13392 <HTML>
13393 <HEAD>
13394 <TITLE>BROWSER</TITLE>
13395 </HEAD>
13396 <BODY>
13397 <H1>BROWSER</H1>
13398 This screen lets you browse your files and directories. To go to another
13399 directory (identified by "(dir)"), move the cursor to it and
13400 choose "Select" (the default choice on the menu);
13401 or choose "Goto" and enter the name of the directory.
13402 <!--chtml if pinemode="os_windows"-->
13403 <!--chtml else-->
13404 In Unix Alpine, you may use
13405 "~" to refer to your home directory or "~user" to refer
13406 to another's home directory.
13407 <!--chtml endif--><P>
13408 To select a file, move the cursor to it and
13409 choose "Select" (the default choice on the menu).
13410 <P>
13411 <UL>
13412 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13413 inclusion in the
13414 message body (that is, you chose "Read File" with the cursor under
13415 the
13416 "----- Message Text -----" line
13417 while composing, then "To Files"): Since the file
13418 selected will become part of the message text, it must be in a format
13419 suitable for that (Alpine does not check!), such as a plain text file.
13420 Files of other formats (for example, graphics, databases, software
13421 programs) should be
13422 <B>attached</B> to the message instead --
13423 by moving the cursor in the COMPOSE MESSAGE screen into the
13424 message header area and pressing
13425 <!--chtml if pinemode="function_key"-->
13426 F6.
13427 <!--chtml else-->
13428 Ctrl-J.
13429 <!--chtml endif-->
13431 <P><LI>
13432 Note <B>if</B> you are currently using the BROWSER for saving a message
13433 attachment, or exporting a message, to a file: You can use the Add command to
13434 provide the name for a new file to save/export to, and then select that name
13435 to use it for the save/export operation. Back at the prompt
13436 "EXPORT: Copy message to file in ..." hit Enter, then choose
13437 either Overwrite or Append (it doesn't make a difference, since the file is
13438 so far empty). Note: If you cancel the
13439 operation at that point, the file created with the Add command will remain
13440 0 bytes in size.
13442 </UL>
13443 <P><UL>
13444 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13445 </UL>
13446 <P>
13447 <End of help on this topic>
13448 </BODY>
13449 </HTML>
13450 ====== h_composer_ins =====
13451 <HTML>
13452 <HEAD>
13453 <TITLE>INSERT TEXT FILE</TITLE>
13454 </HEAD>
13455 <BODY>
13456 <H1>INSERT TEXT FILE</H1>
13458 Use this function to insert a text file. The file name
13459 given can be an absolute file path name for your system
13460 <!--chtml if pinemode="os_windows"-->
13461 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13462 with a relative pathname, or simply a file name without
13463 drive or directory specification.
13464 <!--chtml else-->
13465 (for example, "/tmp/exported.earlier" on Unix hosts),
13466 a file in your home directory, or a file path relative to your
13467 home directory. In Unix Alpine, you may use "~" to refer to
13468 your home directory or "~user" to refer to another
13469 account's home directory.
13470 <!--chtml endif-->
13471 <P>
13472 No wild card characters may be used.
13473 The file must reside on the system running Alpine.
13474 <P>
13475 If the
13476 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13477 feature is set, names are relative to your current working directory
13478 <!--chtml if pinemode="running"-->
13479 (which, at least for your current Alpine "session,"
13480 is "<!--#echo var="CURRENT_DIR"-->")
13481 <!--chtml endif-->
13482 rather than your home directory
13483 <!--chtml if pinemode="running"-->
13484 (which, in the present configuration of your system, is
13485 "<!--#echo var="HOME_DIR"-->")
13486 <!--chtml endif-->
13487 .
13488 <P><UL>
13489 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13490 </UL>
13491 <P>
13492 <End of help on this topic>
13493 </BODY>
13494 </HTML>
13495 ====== h_composer_ins_m =====
13496 <HTML>
13497 <HEAD>
13498 <TITLE>INSERT MESSAGE</TITLE>
13499 </HEAD>
13500 <BODY>
13501 <H1>INSERT MESSAGE</H1>
13503 Type in the number of a message in the currently open folder to insert it
13504 into your message.
13505 <P><UL>
13506 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13507 </UL>
13508 <P>
13509 <End of help on this topic>
13510 </BODY>
13511 </HTML>
13512 ====== h_composer_search =====
13513 <HTML>
13514 <HEAD>
13515 <TITLE>Explanation of Composer Whereis Command </TITLE>
13516 </HEAD>
13517 <BODY>
13518 <H1>Help For Whereis Command</H1>
13520 Whereis is used to search the message for a word or part of a word.
13521 When searching in the composer, only the message part of your mail is
13522 searched, and the cursor is put on the first occurrence appearing
13523 after the location of the cursor. The search will wrap to the
13524 beginning of the message when it no longer finds matches in the
13525 remainder of the message.
13527 To search for the same string a second time, press
13528 <!--chtml if pinemode="function_key"-->
13529 "F6"
13530 <!--chtml else-->
13531 "^W"
13532 <!--chtml endif-->
13533 to begin search and then just press RETURN to accept the previous
13534 search string shown in square brackets rather than entering a new
13535 search string.<P>
13537 The "Search" prompt has several sub-command available:
13539 <DL>
13540 <DT>Get Help</DT>
13541 <DD> Takes you to this help page.
13543 <DT>Cancel</DT>
13544 <DD> Cancels the prompt. No search takes place.
13546 <DT>First Line</DT>
13547 <DD> Takes you back to the composer with the cursor on the first character
13548 of the first line of text.
13550 <DT>Last Line</DT>
13551 <DD> Takes you back to the composer with the cursor on the last character
13552 of the last line of text.
13554 <DT>Replace (Optional)</DT>
13555 <DD> This sub-command is enabled by the
13556 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13557 feature (which is on by default); see its help screen for details on how replacing works.
13559 </DL>
13561 <End of help on this topic>
13562 </BODY>
13563 </HTML>
13564 ====== h_sigedit_search =====
13565 <HTML>
13566 <HEAD>
13567 <TITLE>Explanation of Whereis Command </TITLE>
13568 </HEAD>
13569 <BODY>
13570 <H1>Help For Whereis Command</H1>
13572 Whereis is used to search for a word or part of a word.
13573 When searching the cursor is put on the first occurrence appearing
13574 after the location of the cursor. The search will wrap to the
13575 beginning of the signature when it no longer finds matches in the
13576 remainder of the signature.
13578 To search for the same string a second time, press
13579 <!--chtml if pinemode="function_key"-->
13580 "F6"
13581 <!--chtml else-->
13582 "^W"
13583 <!--chtml endif-->
13584 to begin search and then just press RETURN to accept the previous
13585 search string shown in square brackets rather than entering a new
13586 search string.<P>
13588 The "Search" prompt has several sub-command available:
13590 <DL>
13591 <DT>Get Help</DT>
13592 <DD> Takes you to this help page.
13594 <DT>Cancel</DT>
13595 <DD> Cancels the prompt. No search takes place.
13597 <DT>First Line</DT>
13598 <DD> Takes you back to the composer with the cursor on the first character
13599 of the first line of text.
13601 <DT>Last Line</DT>
13602 <DD> Takes you back to the composer with the cursor on the last character
13603 of the last line of text.
13605 <DT>Replace (Optional)</DT>
13606 <DD> This sub-command is enabled by the
13607 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13608 feature (which is on by default); see its help screen for details on how replacing works.
13610 </DL>
13612 <End of help on this topic>
13613 </BODY>
13614 </HTML>
13615 ======= h_composer_to ====
13616 <HTML>
13617 <HEAD>
13618 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13619 </HEAD>
13620 <BODY>
13621 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13623 <H2>The "To:" field</H2>
13624 The address you enter here must be a valid email address that is reachable
13625 from your site.
13627 <H2>Email Address Format</H2>
13628 You may enter a full name and email address,
13629 <!--chtml if pinemode="os_windows"-->
13630 <!--chtml else-->
13631 a local (meaning, on the same
13632 host as the one you are running Alpine on) username that Alpine will
13633 complete for you,
13634 <!--chtml endif-->
13635 the nickname of someone in a
13636 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13637 mail alias defined by your system administrator. When you move the cursor
13638 out of this field, the nicknames will be expanded to the addresses in your
13639 address book, and the local usernames will be expanded to include the
13640 persons' actual names. You may enter as many addresses as you wish, but they
13641 must be separated by commas. You can move around this and other header fields
13642 with the arrow keys and use many of the usual composer editing keys.
13643 <P>
13644 <UL>
13645 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13646 </UL>
13648 <P>
13649 <H2>MESSAGE HEADER COMMANDS</H2>
13650 <!--chtml if pinemode="function_key"-->
13651 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13652 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13653 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13654 ^P (Up Arrow) Previous line |<BR>
13655 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13656 ^A Beginning of line | delete current line<BR>
13657 ^E End of line | F10 Undelete line(s)<BR>
13658 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13659 F8 Next page |-------------------------------------<BR>
13660 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13661 ----------------------------------------|<BR>
13662 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13663 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13664 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13665 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13666 <!--chtml else-->
13667 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13668 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13669 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13670 ^P (Up Arrow) Previous line | <BR>
13671 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13672 ^A Beginning of line | delete current line<BR>
13673 ^E End of line | ^U Undelete line(s)<BR>
13674 ^Y Previous page |<BR>
13675 ^V Next page |-------------------------------------<BR>
13676 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13677 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13678 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13679 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13680 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13681 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13682 <!--chtml endif-->
13684 <P>
13685 NOTE:
13686 <OL>
13687 <LI>For help on a particular command, highlight the bold text associated
13688 with it above and hit Return.
13689 <LI> The availability of certain commands
13690 is determined by Alpine configuration files and system capabilities.
13691 At some sites, certain commands may not be available due to security or
13692 support concerns.
13693 </OL>
13695 <P>
13696 <UL>
13697 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13698 </UL><P>
13699 <End of help on this topic>
13700 </BODY>
13701 </HTML>
13702 ======= h_composer_cc ====
13703 <HTML>
13704 <HEAD>
13705 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13706 </HEAD>
13707 <BODY>
13708 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13709 The Cc: field is just like the To: field, except it is used for addressees
13710 that you wish to send a "carbon" copy to. That is, the message is
13711 not directly meant directly "for" these recipients, but you wanted
13712 them to see the message. The only difference the recipients see is that their
13713 name is in the Cc: field, rather than the To: field.
13714 <P>
13715 For help with Cc: field editing
13716 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13717 <P>
13718 <UL>
13719 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13720 </UL>
13721 <P>
13722 <UL>
13723 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13724 </UL><P>
13725 <End of help on this topic>
13726 </BODY>
13727 </HTML>
13728 ======= h_composer_bcc ====
13729 <HTML>
13730 <HEAD>
13731 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
13732 </HEAD>
13733 <BODY>
13734 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
13735 The "Bcc:" (Blind carbon copy) header is used when you wish to send
13736 a copy of the message to one or more people whose addresses you do not
13737 wish disclosed, either to reduce clutter or for confidentiality.
13738 <P>
13739 The format of the Bcc: field is just the same as the To: and Cc: fields in
13740 the way the addresses are entered. The recipients listed here will
13741 receive a copy of the message, but --assuming your site's mail transport
13742 software is properly configured-- their addresses will not show up in the
13743 headers of the message, as delivered to all of the recipients. The To:
13744 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
13745 <P>
13746 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
13747 will automatically generate and place in the To: field a pseudo-address of
13748 "undisclosed-recipients: ;"
13749 or whatever string has been specified in the
13750 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13751 variable.
13752 <P>
13753 The reason for this is to avoid embarrassment caused by some Internet
13754 mail transfer software that interprets a "missing" To: header as
13755 an error and replaces it with an Apparently-to: header that may contain
13756 the addresses you entered on the Bcc: line. In addition, it may be
13757 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
13758 <P>
13759 You can manipulate what text ends up on the (originally) empty To:
13760 field. Just remember to put a colon and semicolon at the end of the
13761 field, which is a special notation denoting that it is not a real address.
13762 <P>
13763 For information on message header editing
13764 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13765 <P>
13766 <UL>
13767 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13768 </UL>
13769 <P>
13770 <UL>
13771 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13772 </UL><P>
13773 <End of help on this topic>
13774 </BODY>
13775 </HTML>
13776 ======= h_composer_lcc ====
13777 <HTML>
13778 <HEAD>
13779 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
13780 </HEAD>
13781 <BODY>
13782 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
13783 The "Lcc:" (List carbon copy) header is intended to be used when
13784 you wish to send a message to a list of people but avoid having all
13785 of their addresses visible, in order to reduce clutter when the
13786 message is received.
13787 <P>
13788 It is similar to the
13789 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
13790 in that individual
13791 addressees are hidden, but Lcc is designed to work specifically with
13792 distribution lists you have created in your
13793 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
13794 the nickname of the list on the Lcc line will result in the full name of
13795 your Alpine Address Book list being placed on the To: line of the message,
13796 using a special notation that distinguishes it from a real address. You
13797 must leave the To: line blank for your list name to appear there.
13798 <P>
13799 For example, if you have this list entered in your Address Book:<PRE>
13801 largo Key Largo List DISTRIBUTION LIST:
13802 bogie@mgm.com
13803 lauren@mgm.com
13804 walter@mgm.com</PRE>
13807 and you enter "largo" on the Lcc: line while composing a message,
13808 the result is:<PRE>
13810 To : Key Largo List: ;
13811 Cc :
13812 Bcc :
13813 Fcc : sent-mail
13814 Lcc : Key Largo List <bogie@mgm.com>,
13815 lauren@mgm.com,
13816 walter@mgm.com
13817 Subject :</PRE>
13819 Each recipient listed on the Lcc: line receives a copy of the message
13820 without their address being visible (as though they were listed on the
13821 Bcc: line). The colon-semicolon notation used to put the full-name of the
13822 list on the To: line is a special address format that doesn't specify any
13823 actual addressees, but does give some information to the recipients of the
13824 message.
13825 <P>
13826 Note: if after entering an LCC, you delete the list name that is placed
13827 on the To: line, then recipients will see <PRE>
13828 To: undisclosed-recipients: ;</PRE>
13830 (or whatever string is defined in the
13831 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13832 variable) just as in the BCC case.
13833 <P>
13834 For help with Lcc: field editing
13835 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13836 <P>
13837 <UL>
13838 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13839 </UL>
13840 <P>
13841 <UL>
13842 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13843 </UL><P>
13844 <End of help on this topic>
13845 </BODY>
13846 </HTML>
13847 ======= h_composer_from =======
13848 <HTML>
13849 <HEAD>
13850 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
13851 </HEAD>
13852 <BODY>
13853 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
13855 This header carries your return address. It is the address toward which
13856 replies (and often, future unrelated correspondence) will be directed,
13857 unless you have <A HREF="h_config_custom_hdrs">defined an optional
13858 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
13859 sure this address is correct.
13860 <P>
13861 For help with message header editing
13862 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13863 <P>
13864 <UL>
13865 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13866 </UL>
13867 <P>
13868 <UL>
13869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13870 </UL><P>
13871 <End of help on this topic>
13872 </BODY>
13873 </HTML>
13874 ======= h_composer_reply_to =======
13875 <HTML>
13876 <HEAD>
13877 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
13878 </HEAD>
13879 <BODY>
13880 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
13882 Most people should not need this header. The Reply-To: header is used in
13883 cases where you would like replies to your messages to be directed to an
13884 address other than your normal "From:" address. This is atypical,
13885 but can happen when you use multiple machines and do not have the same account
13886 name on each one, or when you wish to direct certain replies to accounts
13887 or folders designated for specific classes of correspondence.
13888 <P>
13889 For help with message header editing
13890 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13891 <P>
13892 <UL>
13893 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13894 </UL>
13896 <P>
13897 <UL>
13898 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13899 </UL><P>
13900 <End of help on this topic>
13901 </BODY>
13902 </HTML>
13903 ======= h_composer_custom_addr ====
13904 <HTML>
13905 <HEAD>
13906 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13907 </HEAD>
13908 <BODY>
13909 <H1>CUSTOMIZED HEADER FIELD</H1>
13910 This is a customized header, i.e. not one that is part of Alpine's normal
13911 set of Compose headers.
13912 <P>
13913 For help with message header editing
13914 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13915 <P>
13916 <UL>
13917 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13918 </UL>
13919 <P>
13920 <UL>
13921 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13922 </UL><P>
13923 <End of help on this topic>
13924 </BODY>
13925 </HTML>
13926 ======= h_composer_custom_free ====
13927 <HTML>
13928 <HEAD>
13929 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
13930 </HEAD>
13931 <BODY>
13932 <H1>CUSTOMIZED HEADER FIELD</H1>
13933 This is a customized header, i.e. not one that is part of Alpine's normal
13934 set of Compose headers.
13935 <P>
13936 This field consists of arbitrary text.
13937 <P>
13938 For help with message header editing
13939 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13940 <P>
13941 <UL>
13942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13943 </UL><P>
13944 <End of help on this topic>
13945 </BODY>
13946 </HTML>
13947 ====== h_composer_news =====
13948 <HTML>
13949 <HEAD>
13950 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
13951 </HEAD>
13952 <BODY>
13953 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
13954 Use the newsgroups line to specify any and all USENET newsgroups to which
13955 your message should be posted. When composing a message from scratch, this
13956 line may be hidden. If so, just press the rich headers command
13957 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
13958 to make it visible.
13959 <P>
13960 <EM>Be aware</EM> that when you post to a newsgroup thousands of
13961 people will be reading your message. Also, you or your system manager
13962 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
13963 in order for you to be able to post.
13964 <P>
13965 For help with message header editing
13966 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13967 <P><UL>
13968 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13969 </UL>
13970 <P>
13971 <End of help on this topic>
13972 </BODY>
13973 </HTML>
13974 ======= h_composer_fcc ====
13975 <HTML>
13976 <HEADER>
13977 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
13978 </HEADER>
13979 <BODY>
13980 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
13981 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
13982 each outgoing message. The default value can be configured with the
13983 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
13984 the file carbon copy on any message you send by editing the FCC header.<p>
13986 You may type ^T to get a list of all your folders and select one to use as
13987 the FCC for this message.<P>
13989 For help with message header editing
13990 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13991 <P>
13992 <UL>
13993 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13994 </UL><P>
13995 <End of help on this topic>
13996 </BODY>
13997 </HTML>
13998 ======= h_composer_subject ====
13999 <HTML>
14000 <HEADER>
14001 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
14002 </HEADER>
14003 <BODY>
14004 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
14006 The subject header provides a place to enter a few words that summarize
14007 the topic of the message you are sending. You may leave this line blank,
14008 but it is considered a courtesy to use a meaningful subject.<p>
14010 For help with message header editing
14011 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14012 <P>
14013 <UL>
14014 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14015 </UL><P>
14016 <End of help on this topic>
14017 </BODY>
14018 </HTML>
14019 ======= h_composer_attachment ====
14020 <HTML>
14021 <HEAD>
14022 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
14023 </HEAD>
14024 <BODY>
14025 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
14027 The "Attchmnt:" field is where you specify what file or
14028 files you'd like attached to
14029 the message you are composing. Those files must reside on the machine
14030 running Alpine. If your file is on a PC or Mac and you run Alpine with an
14031 account on a Unix machine, you'll have to transfer it before attaching it.
14032 Contact local computer support people for assistance with transferring.
14034 <P>
14035 The file name
14036 given can be an absolute file path name for your system
14037 <!--chtml if pinemode="os_windows"-->
14038 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
14039 with a relative pathname, or simply a file name without
14040 drive or directory specification.
14041 <!--chtml else-->
14042 (for example, "/tmp/exported.earlier" on Unix hosts),
14043 a file in your home directory, or a file path relative to your
14044 home directory. In Unix Alpine, you may use "~" to refer to
14045 your home directory or "~user" to refer to another
14046 account's home directory.
14047 <!--chtml endif--><P>
14048 No wild card characters may be used.
14049 <P>If the
14050 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
14051 feature is set, names are relative to your current working directory
14052 <!--chtml if pinemode="running"-->
14053 (which, at least for your current Alpine "session,"
14054 is "<!--#echo var="CURRENT_DIR"-->")
14055 <!--chtml endif-->
14056 rather than your home directory
14057 <!--chtml if pinemode="running"-->
14058 (which, in the present configuration of your system, is
14059 "<!--#echo var="HOME_DIR"-->")
14060 <!--chtml endif-->
14061 .
14062 <P>
14063 Alpine uses MIME encoding for attachments, so binaries and files of any
14064 length can safely be delivered to any MIME-capable mail reading program.
14065 If you send an attachment to someone who does not have a MIME-capable mail
14066 reading program yet, then the main message text will be readable, but
14067 attachments (even attachments that are just plain text) are not.
14068 <P>
14070 Typing the filename on the Attchmnt: line achieves the same
14071 result as using the
14072 <!--chtml if pinemode="function_key"-->
14073 F6
14074 <!--chtml else-->
14075 Ctrl-J
14076 <!--chtml endif--> command.
14077 <P>
14079 If you Forward a message with attachments, you may delete them from your
14080 Forwarded message by editing the Attchmnt header line.
14081 <P>
14083 For help with message header editing
14084 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14085 <P>
14086 <UL>
14087 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14088 </UL><P>
14089 <End of help on this topic>
14090 </BODY>
14091 </HTML>
14092 ======= h_composer_ctrl_j ====
14093 <HTML>
14094 <HEAD>
14095 <TITLE>COMPOSER ATTACH</TITLE>
14096 </HEAD>
14097 <BODY>
14098 After the
14099 <!--chtml if pinemode="function_key"-->
14100 F6
14101 <!--chtml else-->
14102 Ctrl-J
14103 <!--chtml endif--> command:
14104 At the "File to attach:" prompt, enter the name of the
14105 existing file to attach to your message.
14106 When the feature
14107 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
14108 is set
14109 you need only enter the beginning of the filename (enough of it to uniquely
14110 identify the file) and press TAB to complete it.
14112 Or, press ^T to use the BROWSER screen for
14113 selecting the file. <P>
14114 For more information on attaching files, see the help screen for the
14115 composer's
14116 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
14117 but can be revealed using the
14118 <!--chtml if pinemode="function_key"-->
14119 F5
14120 <!--chtml else-->
14121 Ctrl-R
14122 <!--chtml endif-->
14123 command with the cursor positioned above the
14124 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
14125 <P>
14126 <End of help on this topic>
14127 </BODY>
14128 </HTML>
14129 ======= h_edit_nav_cmds =========
14130 <HTML>
14131 <HEAD>
14132 <TITLE>Composer Editing Commands Explained</TITLE>
14133 </HEAD>
14134 <BODY>
14135 <H1>EDITING and NAVIGATION COMMANDS</H1>
14136 <!--chtml if pinemode="function_key"-->
14137 <PRE>
14138 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14139 ^B (Left Arrow) Back character | ^D Delete current character
14140 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14141 ^P (Up Arrow) Previous line |
14142 ^N (Down Arrow) Next line | F9 Cut marked text or
14143 ^A Beginning of line | delete current line
14144 ^E End of line | F10 Undelete line(s)
14145 F7 Previous page |
14146 F8 Next page |-------------------------------------
14147 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14148 ----------------------------------------|
14149 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
14150 F3 Cancel | F1 Get help | F12 RichView (expand lists)
14151 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
14152 </PRE>
14153 <!--chtml else-->
14154 <PRE>
14155 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14156 ^B (Left Arrow) Back character | ^D Delete current character
14157 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14158 ^P (Up Arrow) Previous line |
14159 ^N (Down Arrow) Next line | ^K Cut marked text or
14160 ^A Beginning of line | delete current line
14161 ^E End of line | ^U Undelete line(s)
14162 ^Y Previous page |
14163 ^V Next page |-------------------------------------
14164 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14165 ----------------------------------------|
14166 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
14167 ^C Cancel | ^G Get help | ^R RichView (expand lists)
14168 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
14169 </PRE>
14170 <!--chtml endif-->
14171 <End of help on this topic>
14172 </BODY>
14173 </HTML>
14174 ===== h_composer_sigedit =====
14175 <HTML>
14176 <HEAD>
14177 <TITLE>Signature Editor Commands Explained</TITLE>
14178 </HEAD>
14179 <BODY>
14180 <H1>SIGNATURE EDITOR COMMANDS</H1>
14181 <!--chtml if pinemode="function_key"-->
14182 <PRE>
14183 CURSOR MOTION KEYS |EDITING KEYS
14184 ^B (Left Arrow) Back character | ^D Delete current character
14185 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14186 ^P (Up Arrow) Previous line | ^^ Set a mark
14187 ^N (Down Arrow) Next line | F9 Cut marked text or
14188 ^A Beginning of line | delete current line
14189 ^E End of line | F10 Paste text, undelete lines
14190 F7 Previous page | cut with ^K, or unjustify
14191 F8 Next page |-------------------------------------
14192 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14193 ---------------------------------------| F6 Whereis (search for string)
14194 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14195 F3 Cancel | F1 Get help | F4 Justify paragraph
14196 | ^Z Suspend | ^L Redraw Screen
14197 F2 Send | F6 Alt. editor | F5 Read in a file
14198 </PRE>
14199 <!--chtml else-->
14200 <PRE>
14201 CURSOR MOTION KEYS |EDITING KEYS
14202 ^B (Left Arrow) Back character | ^D Delete current character
14203 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14204 ^P (Up Arrow) Previous line | ^^ Set a mark
14205 ^N (Down Arrow) Next line | ^K Cut marked text or
14206 ^A Beginning of line | delete current line
14207 ^E End of line | ^U Paste text, undelete lines
14208 ^Y Previous page | cut with ^K, or unjustify
14209 ^V Next page |-------------------------------------
14210 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14211 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14212 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14213 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14214 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14215 ^X Send | ^_ Alt. editor | ^R Read in a file
14216 </PRE>
14217 <!--chtml endif-->
14219 NOTE: The presence or absence of the following commands is determined
14220 by "Feature-List" options in your Alpine configuration. Also,
14221 some of these commands may be administratively disabled by your system
14222 manager; if they don't work, please check with your local help desk
14223 before reporting a bug.
14224 <P>
14225 <UL>
14226 <LI>Suspend (suspends Alpine and gives a system prompt)
14227 <LI>Alternate editor (allows you to compose with your own editor)
14228 </UL>
14229 <P>
14231 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14232 Ctrl-\, ESC
14233 <P>
14235 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14236 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14237 <P>
14238 <End of help on this topic>
14239 </BODY>
14240 </HTML>
14241 ===== h_composer_commentedit =====
14242 <HTML>
14243 <HEAD>
14244 <TITLE>Comment Editor Commands Explained</TITLE>
14245 </HEAD>
14246 <BODY>
14247 <H1>COMMENT EDITOR COMMANDS</H1>
14248 <!--chtml if pinemode="function_key"-->
14249 <PRE>
14250 CURSOR MOTION KEYS |EDITING KEYS
14251 ^B (Left Arrow) Back character | ^D Delete current character
14252 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14253 ^P (Up Arrow) Previous line | ^^ Set a mark
14254 ^N (Down Arrow) Next line | F9 Cut marked text or
14255 ^A Beginning of line | delete current line
14256 ^E End of line | F10 Paste text, undelete lines
14257 F7 Previous page | cut with ^K, or unjustify
14258 F8 Next page |-------------------------------------
14259 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14260 ---------------------------------------| F6 Whereis (search for string)
14261 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14262 F3 Cancel | F1 Get help | F4 Justify paragraph
14263 | ^Z Suspend | ^L Redraw Screen
14264 F2 Send | F6 Alt. editor | F5 Read in a file
14265 </PRE>
14266 <!--chtml else-->
14267 <PRE>
14268 CURSOR MOTION KEYS |EDITING KEYS
14269 ^B (Left Arrow) Back character | ^D Delete current character
14270 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14271 ^P (Up Arrow) Previous line | ^^ Set a mark
14272 ^N (Down Arrow) Next line | ^K Cut marked text or
14273 ^A Beginning of line | delete current line
14274 ^E End of line | ^U Paste text, undelete lines
14275 ^Y Previous page | cut with ^K, or unjustify
14276 ^V Next page |-------------------------------------
14277 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14278 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14279 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14280 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14281 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14282 ^X Send | ^_ Alt. editor | ^R Read in a file
14283 </PRE>
14284 <!--chtml endif-->
14286 NOTE: The presence or absence of the following commands is determined
14287 by "Feature-List" options in your Alpine configuration. Also,
14288 some of these commands may be administratively disabled by your system
14289 manager; if they don't work, please check with your local help desk
14290 before reporting a bug.
14291 <P>
14292 <UL>
14293 <LI>Suspend (suspends Alpine and gives a system prompt)
14294 <LI>Alternate editor (allows you to compose with your own editor)
14295 </UL>
14296 <P>
14298 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14299 Ctrl-\, ESC
14300 <P>
14302 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14303 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14304 <P>
14305 <End of help on this topic>
14306 </BODY>
14307 </HTML>
14308 ======= h_composer_abook_nick =======
14309 <HTML>
14310 <HEAD>
14311 <TITLE>Addressbook Nickname Explained</TITLE>
14312 </HEAD>
14313 <BODY>
14314 This is a short nickname for this address book entry. If it is used in
14315 place of an address from the composer, the composer will fill in the
14316 address(es) for the entry that matches the nickname.
14317 <P>
14319 Look <A HREF="h_edit_nav_cmds">here</A>
14320 to see the available Editing and Navigation commands.
14321 <P>
14322 <End of help on this topic>
14323 </BODY>
14324 </HTML>
14325 ======= h_composer_abook_full =======
14326 <HTML>
14327 <HEAD>
14328 <TITLE>Addressbook Fullname Explained</TITLE>
14329 </HEAD>
14330 <BODY>
14331 This is the full name field for this entry. If this is going to be a
14332 distribution list (more than one address), it should be a descriptive
14333 phrase describing the list. It will be included in the mail header if you
14334 put the list in the To: or CC: field, or in the To: line if you put the
14335 list in the Lcc: field. It's OK to leave this field blank (and OK to
14336 leave any of the other fields blank, too). If this address book entry is
14337 going to be a simple entry with just one address, then this field is the
14338 person's name. When you send mail to this entry, this is the field to the
14339 left of the brackets. That is, it is the most readable part of the
14340 address. For example, in the sample address:
14341 <PRE>
14342 John Doe <jdoe@some.domain>
14343 </PRE>
14344 "John Doe" is the full name field. If you are sorting your address book
14345 with one of the options that uses full names, then it might be useful to
14346 enter the full name as "Last, First", for example:
14347 <PRE>
14348 Doe, John
14349 </PRE>
14350 so that it will be sorted using Doe instead of John. This will be changed
14351 back into John Doe when you use it.
14352 <P>
14353 Look <A HREF="h_edit_nav_cmds">here</A>
14354 to see the available Editing and Navigation commands.
14355 <P>
14356 <End of help on this topic>
14357 </BODY>
14358 </HTML>
14359 ======= h_composer_abook_fcc =======
14360 <HTML>
14361 <HEAD>
14362 <TITLE>Addressbook Fcc Explained</TITLE>
14363 </HEAD>
14364 <BODY>
14365 If this entry is the first one in the To: line of an outgoing message,
14366 this field will be used for the Fcc (File Carbon Copy) instead of whatever
14367 you would normally get (which depends on which
14368 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
14369 you've chosen).
14370 <P>
14371 If this field consists of two double quotes ("") that tells Alpine
14372 that you don't want any Fcc associated with this entry.
14373 <P>
14374 Look <A HREF="h_edit_nav_cmds">here</A>
14375 to see the available Editing and Navigation commands.
14376 <P>
14377 <End of help on this topic>
14378 </BODY>
14379 </HTML>
14380 ====== h_config_combined_abook_display =====
14381 <HTML>
14382 <HEAD>
14383 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14384 </HEAD>
14385 <BODY>
14386 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14388 This feature affects the address book display screens.
14389 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14390 will cause the remaining address books and directory servers to disappear
14391 from the screen, leaving only the entries of the expanded address book.
14392 If this feature is set, then the other address books will remain on the screen,
14393 so that all of the address books can be present at once.
14395 <P>
14396 The way that commands work won't be changed.
14397 For example, the Select All command will select all of the entries in the
14398 current address book, not all of the entries in all of the address books.
14399 The WhereIs command will change a little.
14400 It will search through all of the text on the screen plus all of the entries
14401 from expanded address books.
14403 <P>
14404 When this feature is set, the setting of the feature
14405 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14406 has an effect.
14407 <P>
14408 <End of help on this topic>
14409 </BODY>
14410 </HTML>
14411 ====== h_config_titlebar_color_style =====
14412 <HTML>
14413 <HEAD>
14414 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14415 </HEAD>
14416 <BODY>
14417 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14419 This option affects the colors used to display the titlebar (the top
14420 line on the screen) when viewing a message.
14422 <P>
14423 The available options include:
14424 <P>
14426 <DL>
14427 <DT>default</DT>
14428 <DD>The color of the titlebar will be the color you set for the
14429 <A HREF="h_config_title_color">Title Color</A>.
14430 The Title Color may be set by using the
14431 <A HREF="h_color_setup">Setup Kolor</A> screen.
14432 </DD>
14434 <DT>indexline</DT>
14435 <DD>The color of the titlebar will be the same as the color of the
14436 index line corresponding to the message being viewed.
14437 The rules that determine what color the index line will be may be set
14438 up by going to the Setup/Rules/Indexcolor screen.
14439 If the index line for a message is not colored explicitly by the
14440 Indexcolor rules, then the titlebar will be colored the same as for
14441 the "default" option above (which is not the same color that
14442 the index line itself will have).
14443 </DD>
14445 <DT>reverse-indexline</DT>
14446 <DD>This is similar to the "indexline" option except the
14447 foreground and background colors from the corresponding index line will
14448 be reversed.
14449 For example, if the index line color is red letters on a white background,
14450 then the titlebar will be white letters on a red background.
14451 If the index line for a message is not colored explicitly by the
14452 Indexcolor rules, then the titlebar will be colored the same as for
14453 the "default" option above (which is not the same color that
14454 the index line itself will have).
14455 </DD>
14456 </DL>
14458 <P>
14460 <UL>
14461 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14462 </UL><P>
14463 <End of help on this topic>
14464 </BODY>
14465 </HTML>
14466 ====== h_config_index_color_style =====
14467 <HTML>
14468 <HEAD>
14469 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14470 </HEAD>
14471 <BODY>
14472 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14474 This option affects the colors used to display the current line in the
14475 MESSAGE INDEX screen.
14476 If you do not have Index Color Rules defined, then this option will
14477 have no effect in the index.
14478 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14479 <P>
14480 If the option
14481 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14482 is turned on and the
14483 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14484 is set to something other than the default, then
14485 this option also affects the color used to display the current folder
14486 in the Incoming FOLDER LIST screen.
14488 <P>
14489 The available options include:
14490 <P>
14492 <DL>
14493 <DT>flip-colors</DT>
14494 <DD>This is the default.
14495 If an index line is colored because it matches one of your
14496 Index Color Rules, then its colors will be reversed when it is the currently
14497 highlighted line.
14498 For example, if the line is normally red text on a blue background, then
14499 when it is the current line it will be drawn as blue text on a red background.
14500 <P>
14501 The rest of the option values all revert to this flip-colors behavior if
14502 there is no Reverse Color defined.
14503 </DD>
14505 <DT>reverse</DT>
14506 <DD>With this option the Reverse color is always used to highlight the
14507 current line.
14508 </DD>
14510 <DT>reverse-fg</DT>
14511 <DD>The foreground part of the Reverse Color is used to highlight
14512 the current line.
14513 If this would cause the text to be unreadable (because the foreground and
14514 background colors are the same) or if it would cause no change in the
14515 color of the index line, then the colors are flipped instead.
14516 <P>
14517 Some people think this works particularly well if you use different
14518 background colors to emphasize "interesting" lines,
14519 but always with the same Normal foreground color,
14520 and you use a different foreground color for the Reverse Color.
14521 </DD>
14523 <DT>reverse-fg-no-ambiguity</DT>
14524 <DD>With the "reverse-fg" rule above, it is possible that
14525 the resulting color will be exactly the same as the regular Reverse
14526 Color.
14527 That can lead to some possible confusion because an
14528 "interesting"
14529 line that is the current line will be displayed exactly the same as a
14530 non-interesting line that is current.
14531 You can't tell whether the line is just a regular current line or if it is
14532 an "interesting" current line by looking at the color.
14533 Setting the option to this value removes that ambiguity.
14534 It is the same as the "reverse-fg" setting unless the resulting
14535 interesting current line would look just like a non-interesting current line.
14536 In that case, the interesting line's colors are simply flipped (like in the
14537 default behavior).
14538 <P>
14539 As an alternative way to preserve the line's interestingness in this case,
14540 you may find that using both a different foreground and a different
14541 background color for the interesting line will help.
14542 </DD>
14544 <DT>reverse-bg</DT>
14545 <DD>The background part of the Reverse Color is used to highlight
14546 the current line.
14547 If this would cause the text to be unreadable (because the foreground and
14548 background colors are the same) or if it would cause no change in the
14549 color of the index line, then the colors are flipped instead.
14550 <P>
14551 Some people think this works particularly well if you use different
14552 foreground colors to emphasize "interesting" lines,
14553 but always with the same Normal background color,
14554 and you use a different background color for the Reverse Color.
14555 </DD>
14557 <DT>reverse-bg-no-ambiguity</DT>
14558 <DD>As with the "reverse-fg" case, the "reverse-bg"
14559 rule may also result in a color that is exactly the same as the regular
14560 Reverse Color.
14561 Setting the option to this value removes that ambiguity.
14562 It is the same as the "reverse-bg" setting unless the resulting
14563 current line has the same color as the Reverse Color.
14564 In that case, the interesting line's colors are simply flipped (like in the
14565 default behavior).
14566 </DD>
14567 </DL>
14569 <P>
14571 <UL>
14572 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14573 </UL><P>
14574 <End of help on this topic>
14575 </BODY>
14576 </HTML>
14577 ====== h_config_expanded_addrbooks =====
14578 <HTML>
14579 <HEAD>
14580 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14581 </HEAD>
14582 <BODY>
14583 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14585 If multiple address books (either personal or global) are defined, and you
14586 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14587 screen, then set this feature. This feature will have no effect unless the
14588 feature
14589 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14590 is also set.
14591 <P>
14592 <End of help on this topic>
14593 </BODY>
14594 </HTML>
14595 ====== h_config_combined_folder_display =====
14596 <HTML>
14597 <HEAD>
14598 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14599 </HEAD>
14600 <BODY>
14601 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14603 This feature affects the folder list display screens.
14604 Normally, each folder list is viewed within its collection only. This
14605 command allows folder lists to be viewed within a single screen that
14606 combines the contents of all collections.
14608 <P>
14609 The way that commands work won't be changed.
14610 For example, the Select All command will select all of the folders in the
14611 current collection, not all of the entries in all of the collections.
14612 The WhereIs command will change a little.
14613 It will search through all of the folders in the current collection as well
14614 as all the folder in any other expanded collection.
14616 <P>
14617 When this feature is set, the setting of the feature
14618 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14619 has an effect.
14620 <P>
14621 <End of help on this topic>
14622 </BODY>
14623 </HTML>
14624 ====== h_config_combined_subdir_display =====
14625 <HTML>
14626 <HEAD>
14627 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14628 </HEAD>
14629 <BODY>
14630 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14632 This feature affects the Folder List screen when
14633 the
14634 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14635 feature is enabled. Normally, selecting a directory from the Folder
14636 List takes you into a new screen displaying only the contents of
14637 that directory.
14639 <P>
14640 Enabling this feature will cause the contents of the selected
14641 directory to be
14642 displayed within the boundaries of the "Collection" it
14643 is a part of. All previously displayed collections will remain
14644 in the screen.
14646 <P>
14647 The way that commands work won't be changed.
14648 For example, the Select All command will select all of the folders in the
14649 directory, as opposed to all of the entries in all of the collections.
14650 The WhereIs command will change a little.
14651 It will search through all of the folders in the current collection as well
14652 as all the folder in any other expanded collection.
14654 <P>
14655 <End of help on this topic>
14656 </BODY>
14657 </HTML>
14658 ====== h_config_separate_fold_dir_view =====
14659 <HTML>
14660 <HEAD>
14661 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14662 </HEAD>
14663 <BODY>
14664 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14666 This feature affects folder collections wherein a folder
14667 and directory can have the same name. By default, Alpine displays them
14668 only once, denoting that it is both a folder and directory by appending
14669 the folder name with the hierarchy character enclosed
14670 in square brackets.
14673 <P>
14674 Enabling this feature will cause Alpine to display such names
14675 separately marking the name representing a directory with a trailing
14676 hierarchy delimiter (typically the slash, "/", character).
14678 <P>
14679 The feature also alters the command set slightly. By default, the
14680 right-arrow descends into the directory, while hitting the Return key will
14681 cause the folder by that name to be opened.
14683 <P>
14684 With this feature set, the Return key will open the highlighted folder, or
14685 enter the highlighted directory.
14687 <P>
14688 <End of help on this topic>
14689 </BODY>
14690 </HTML>
14691 ====== h_config_expanded_folders =====
14692 <HTML>
14693 <HEAD>
14694 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14695 </HEAD>
14696 <BODY>
14697 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14699 If multiple folder collections are defined, and you
14700 wish to have them all expanded implicitly upon entering the FOLDER LIST
14701 screen, then set this feature. This feature will have no effect unless the
14702 feature
14703 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14704 is also set.
14705 <P>
14706 <End of help on this topic>
14707 </BODY>
14708 </HTML>
14709 ======= h_config_ldap_server =======
14710 <HTML>
14711 <HEAD>
14712 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14713 </HEAD>
14714 <BODY>
14715 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14716 This is the name of the host where an LDAP server is running.
14717 For redundancy, this may be a space-delimited set of server names, in which
14718 case the first server that answers is used.
14719 Each of the server names may be optionally followed by
14720 a colon and a port number.
14721 If this form is used then the port number configured below in the
14722 <EM>port</EM> field is not used.
14723 <P>
14724 To find out whether your organization has its own LDAP server,
14725 contact its computing support staff.
14726 <P><UL>
14727 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14728 </UL>
14729 <P>
14730 <End of help on this topic>
14731 </BODY>
14732 </HTML>
14733 ======= h_config_ldap_base =======
14734 <HTML>
14735 <HEAD>
14736 <TITLE>LDAP OPTION: Search-Base</TITLE>
14737 </HEAD>
14738 <BODY>
14739 <H1>LDAP OPTION: Search-Base</H1>
14741 This is the search base to be used on this server. It functions as a filter
14742 by restricting your searches in the LDAP server database
14743 to the specified contents of the specified fields. Without it, searches
14744 submitted to this directory server may fail. It might be something
14745 like:
14747 <PRE>
14748 O = <Your Organization Name>, C = US
14749 </PRE>
14750 or it might be blank.
14751 (Some LDAP servers actually ignore anything specified here.)
14752 <P>
14753 If in doubt what parameters you should specify here,
14754 contact the maintainers of the LDAP server.
14755 <P><UL>
14756 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14757 </UL>
14758 <P>
14759 <End of help on this topic>
14760 </BODY>
14761 </HTML>
14762 ======= h_config_ldap_port =======
14763 <HTML>
14764 <HEAD>
14765 <TITLE>LDAP OPTION: Port</TITLE>
14766 </HEAD>
14767 <BODY>
14768 <H1>LDAP OPTION: Port</H1>
14770 This is the TCP port number to be used with this LDAP server. If you leave
14771 this blank port 389 will be used.
14772 <P>
14773 <End of help on this topic>
14774 </BODY>
14775 </HTML>
14776 ======= h_config_ldap_nick =======
14777 <HTML>
14778 <HEAD>
14779 <TITLE>LDAP OPTION: Nickname</TITLE>
14780 </HEAD>
14781 <BODY>
14782 <H1>LDAP OPTION: Nickname</H1>
14784 This is a nickname to be used in displays. If you don't supply a
14785 nickname the server name
14786 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
14787 will be used instead. This option is strictly for your convenience.
14788 <P>
14789 <End of help on this topic>
14790 </BODY>
14791 </HTML>
14792 ======= h_config_ldap_binddn =======
14793 <HTML>
14794 <HEAD>
14795 <TITLE>LDAP OPTION: Bind-DN</TITLE>
14796 </HEAD>
14797 <BODY>
14798 <H1>LDAP OPTION: Bind-DN</H1>
14800 You may need to authenticate to the LDAP server before you are able to use it.
14801 This is the Distinguished Name to bind to when authenticating to this server.
14802 Try leaving this blank until you know you need it.
14803 <P>
14804 Alpine only knows about LDAP Simple authentication.
14805 It does not attempt LDAP SASL authentication.
14806 The DN and password will be sent in the clear unless TLS encryption is
14807 being used on this connection.
14808 Because of this, you may want to set the LDAP feature
14809 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
14810 or the feature
14811 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14812 if you are going to be providing a password.
14813 <P><UL>
14814 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14815 </UL>
14816 <P>
14817 <End of help on this topic>
14818 </BODY>
14819 </HTML>
14820 ======= h_config_ldap_opts_impl =======
14821 <HTML>
14822 <HEAD>
14823 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
14824 </HEAD>
14825 <BODY>
14826 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
14828 Set this to have lookups done to this server implicitly from the composer.
14829 If an address doesn't look like a fully-qualified address, it will be looked
14830 up in your address books, and if it doesn't match a nickname there, then it
14831 will be looked up on the LDAP servers that have this feature set.
14832 The lookups will also be done when using the address completion feature
14833 (TAB command) in the composer if any of the serves have this feature set.
14834 Also see the LDAP feature
14835 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
14836 and the Setup/Config feature
14837 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14838 <P>
14839 <End of help on this topic>
14840 </BODY>
14841 </HTML>
14842 ======= h_config_ldap_opts_tls =======
14843 <HTML>
14844 <HEAD>
14845 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
14846 </HEAD>
14847 <BODY>
14848 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
14850 When connecting to this server Alpine will attempt to use TLS encryption
14851 on the connection.
14852 Also see the closely related feature
14853 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
14854 <P>
14855 <End of help on this topic>
14856 </BODY>
14857 </HTML>
14858 ======= h_config_ldap_opts_tlsmust =======
14859 <HTML>
14860 <HEAD>
14861 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
14862 </HEAD>
14863 <BODY>
14864 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
14866 When connecting to this server Alpine will attempt to use TLS encryption
14867 on the connection.
14868 If the StartTLS operation fails then the connection will not be used.
14869 <P>
14870 <End of help on this topic>
14871 </BODY>
14872 </HTML>
14873 ====== h_config_ldap_opts_rhs =====
14874 <HTML>
14875 <HEAD>
14876 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
14877 </HEAD>
14878 <BODY>
14879 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
14881 Normally implicit LDAP lookups from the composer are done only for the
14882 strings you type in from the composer screen. In other words, you type in
14883 something in the To or CC field and press return, then the string is looked up.
14884 First that string is looked up in your address books. If a match is found
14885 there, then the results of that match are looked up again. If you place
14886 a string in your address book that you want to have looked up on the LDAP
14887 directory server, you need to turn on this feature. If you set this feature
14888 for a server, you almost always will also want to set the
14889 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
14890 feature. An example might serve to best illustrate this feature.
14891 <P>
14892 If an LDAP lookup of "William Clinton" normally returns an
14893 entry with an
14894 address of pres@whitehouse.gov, then you might put an entry in your address
14895 book that looks like:
14896 <P>
14897 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
14898 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
14899 <P>
14900 Now, when you type "bill" into an
14901 address field in the composer Alpine will
14902 find the "bill" entry in your address book.
14903 It will replace "bill" with
14904 "William Clinton".
14905 It will then search for an entry with that nickname
14906 in your address book and not find one. If this feature
14907 is set, Alpine will then attempt to lookup
14908 "William Clinton" on the LDAP server and find the entry with address
14909 pres@whitehouse.gov.
14910 <P>
14911 A better way to accomplish the same thing is probably to use the feature
14912 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
14913 <P>
14914 <End of help on this topic>
14915 </BODY>
14916 </HTML>
14917 ====== h_config_ldap_opts_ref =====
14918 <HTML>
14919 <HEAD>
14920 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
14921 </HEAD>
14922 <BODY>
14923 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
14925 Normally when you save the results of an LDAP directory lookup to your
14926 address book the results of the lookup are saved. If this feature is set
14927 and the entry being saved was found on this directory server, then the
14928 search criteria is saved instead of the results of the search. When this
14929 address book entry is used in the future, instead of copying the results
14930 from the address book the directory lookup will be done again. This could
14931 be useful if the copied result might become stale because the data on
14932 the directory server changes (for example, the entry's email address changes).
14933 You probably don't want to set this feature if the server is at all slow or
14934 unreliable.
14935 <P>
14936 The way this actually works is that instead of saving the email address
14937 in your address book, Alpine saves enough information to look up the same
14938 directory entry again. In particular, it saves the server name and the
14939 distinguished name of the entry. It's possible that the server administrators
14940 might change the format of distinguished names on the server, or that the
14941 entry might be removed from the server. If Alpine notices this, you will be warned
14942 and a backup copy of the email address will be used. You may want to create
14943 a new entry in this case, since you will get the annoying warning every
14944 time you use the old entry. You may do that by Saving the entry to a new
14945 nickname in the same address book. You will be asked whether or not you
14946 want to use the backup email address.
14947 <P>
14948 A related feature in the Setup/Config screen is
14949 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
14950 <P>
14951 <End of help on this topic>
14952 </BODY>
14953 </HTML>
14954 ======= h_config_ldap_opts_nosub =======
14955 <HTML>
14956 <HEAD>
14957 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
14958 </HEAD>
14959 <BODY>
14960 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
14962 Spaces in your input are normally handled specially.
14963 Each space character is replaced
14964 by
14965 <P>
14966 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
14967 <P>
14968 in the search query (but not by "* <SPACE> *").
14969 The reason this is done is so the input string
14970 <P>
14971 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
14972 <P>
14973 (which is converted to "Greg* Donald") will match
14974 the names "Greg Donald",
14975 "Gregory Donald", "Greg F. Donald", and
14976 "Gregory F Donald"; but it won't match "Greg McDonald".
14977 If the "Search-Rule" you were using was "begins-with",
14978 then it would also match the name "Greg Donaldson".
14979 <P>
14980 Turning on this feature will disable this substitution.
14981 <P>
14982 <End of help on this topic>
14983 </BODY>
14984 </HTML>
14985 ====== h_config_ldap_searchtypes =======
14986 <HTML>
14987 <HEAD>
14988 <TITLE>LDAP OPTION: Search-Type</TITLE>
14989 </HEAD>
14990 <BODY>
14991 <H1>LDAP OPTION: Search-Type</H1>
14993 This affects the way that LDAP searches are done.
14994 In particular, this tells the server where to look for the string to be matched.
14995 If set to "name" then the string that is being searched for will
14996 be compared with the string in the
14997 "Name" field on the server
14998 (technically, it is the "commonname" field on the server).
14999 "Surname" means we're looking for a
15000 match in the "Surname" field on the
15001 server (actually the "sn" field).
15002 "Givenname" really is "givenname"
15003 and "email" is the electronic mail address (this is actually the field
15004 called "mail" or "electronicmail" on the server).
15005 The other three types are combinations of
15006 the types listed so far. "Name-or-email"
15007 means the string should appear
15008 in either the "name" field OR the "email" field.
15009 Likewise, "surname-or-givenname"
15010 means "surname" OR "givenname"
15011 and "sur-or-given-or-name-or-email" means the obvious thing.
15012 <P>
15013 This search TYPE is combined with the
15014 search <A HREF="h_config_ldap_searchrules">RULE</A>
15015 to form the actual search query.
15016 <P>
15017 The usual default value for this
15018 option is "sur-or-given-or-name-or-email".
15019 This type of search may be slow on some servers.
15020 Try "name-or-email", which is often
15021 faster, or just "name" if the performance seems to be a problem.
15022 <P>
15023 Some servers have been configured with different attribute names for
15024 these four fields.
15025 In other words, instead of using the attribute name "mail"
15026 for the email address field, the server might be configured to use something
15027 else, for example, "rfc822mail" or "internetemailaddress".
15028 Alpine can be configured to use these different attribute names by using
15029 the four configuration options:
15030 <P><UL>
15031 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15032 </UL>
15033 <P><UL>
15034 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15035 </UL>
15036 <P><UL>
15037 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15038 </UL>
15039 <P><UL>
15040 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15041 </UL>
15042 <P>
15043 <End of help on this topic>
15044 </BODY>
15045 </HTML>
15046 ====== h_config_ldap_searchrules =======
15047 <HTML>
15048 <HEAD>
15049 <TITLE>LDAP OPTION: Search-Rule</TITLE>
15050 </HEAD>
15051 <BODY>
15052 <H1>LDAP OPTION: Search-Rule</H1>
15054 This affects the way that LDAP searches are done.
15055 If set to "equals" then
15056 only exact matches count.
15057 "Contains" means that the string you type in
15058 is a substring of what you are matching against.
15059 "Begins-with" and "ends-with"
15060 mean that the string starts or ends with the string you type in.
15061 <P>
15062 Spaces in your input are normally handled specially, but you can turn that
15063 special handling off with the
15064 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15065 feature.
15066 <P>
15067 The usual default value for this option is "begins-with".
15068 <P>
15069 <End of help on this topic>
15070 </BODY>
15071 </HTML>
15072 ======= h_config_ldap_email_attr =======
15073 <HTML>
15074 <HEAD>
15075 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
15076 </HEAD>
15077 <BODY>
15078 <H1>LDAP OPTION: EmailAttribute</H1>
15080 This is the name of the attribute that is searched for when looking for
15081 an email address. The default value for this option is "mail" or
15082 "electronicmail".
15083 If the server you are using uses a different attribute name for the email
15084 address, put that attribute name here.
15085 <P>
15086 This will affect the search filter used if your Search-Type is one that
15087 contains a search for "email".
15088 It will also cause the attribute value matching this attribute name to be used
15089 as the email address when you look up an entry from the composer.
15090 <P>
15091 <End of help on this topic>
15092 </BODY>
15093 </HTML>
15094 ======= h_config_ldap_sn_attr =======
15095 <HTML>
15096 <HEAD>
15097 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
15098 </HEAD>
15099 <BODY>
15100 <H1>LDAP OPTION: SurnameAttribute</H1>
15102 This is the name of the attribute that is searched for when looking for
15103 the surname of the entry. The default value for this option is "sn".
15104 If the server you are using uses a different attribute name for the surname,
15105 put that attribute name here.
15106 This will affect the search filter used if your Search-Type is one that
15107 contains a search for "surname".
15108 <P>
15109 <End of help on this topic>
15110 </BODY>
15111 </HTML>
15112 ======= h_config_ldap_gn_attr =======
15113 <HTML>
15114 <HEAD>
15115 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
15116 </HEAD>
15117 <BODY>
15118 <H1>LDAP OPTION: GivennameAttribute</H1>
15120 This is the name of the attribute that is searched for when looking for
15121 the given name of the entry. The default value for this option is "givenname".
15122 If the server you are using uses a different attribute name for the given name,
15123 put that attribute name here.
15124 This will affect the search filter used if your Search-Type is one that
15125 contains a search for "givenname".
15126 <P>
15127 <End of help on this topic>
15128 </BODY>
15129 </HTML>
15130 ======= h_config_ldap_cn_attr =======
15131 <HTML>
15132 <HEAD>
15133 <TITLE>LDAP OPTION: NameAttribute</TITLE>
15134 </HEAD>
15135 <BODY>
15136 <H1>LDAP OPTION: NameAttribute</H1>
15138 This is the name of the attribute that is searched for when looking for
15139 the name of the entry. The default value for this option is "cn", which
15140 stands for common name.
15141 If the server you are using uses a different attribute name for the name,
15142 put that attribute name here.
15143 This will affect the search filter used if your Search-Type is one that
15144 contains a search for "name".
15145 <P>
15146 <End of help on this topic>
15147 </BODY>
15148 </HTML>
15149 ======= h_config_ldap_time =======
15150 <HTML>
15151 <HEAD>
15152 <TITLE>LDAP OPTION: Timelimit</TITLE>
15153 </HEAD>
15154 <BODY>
15155 <H1>LDAP OPTION: Timelimit</H1>
15157 This places a limit on the number of seconds the LDAP search will continue.
15158 The default is 30 seconds. A value of 0 means no limit. Note that some servers
15159 may place limits of their own on searches.
15160 <P>
15161 <End of help on this topic>
15162 </BODY>
15163 </HTML>
15164 ======= h_config_ldap_size =======
15165 <HTML>
15166 <HEAD>
15167 <TITLE>LDAP OPTION: Sizelimit</TITLE>
15168 </HEAD>
15169 <BODY>
15170 <H1>LDAP OPTION: Sizelimit</H1>
15172 This places a limit on the number of entries returned by the LDAP server.
15173 A value of 0 means no limit. The default is 0. Note that some servers
15174 may place limits of their own on searches.
15175 <P>
15176 <End of help on this topic>
15177 </BODY>
15178 </HTML>
15179 ======= h_config_ldap_cust =======
15180 <HTML>
15181 <HEAD>
15182 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
15183 </HEAD>
15184 <BODY>
15185 <H1>LDAP OPTION: Custom-Search-Filter</H1>
15187 This one is for advanced users only! If you define this, then the
15188 "Search-Type" and "Search-Rule" defined are both ignored.
15189 However, the feature
15190 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15191 is still in effect.
15192 That is, the space substitution will take place even in a custom filter unless
15193 you disable it.
15194 <P>
15195 If your LDAP service stops working and you suspect it might be because
15196 of your custom filter, just delete this filter and try using the
15197 "Search-Type" and "Search-Rule" instead.
15198 Another option that sometimes causes trouble is the
15199 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
15200 <P>
15201 This variable may be set to the string representation of an LDAP search
15202 filter (see RFC1960). In the places where you want the address string to be
15203 substituted in, put a '%s' in this filter string. Here are some examples:
15204 <P>
15205 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
15206 is equivalent to the "Custom-Search-Filter"
15207 <PRE>
15208 (cn=%s*)
15209 </PRE>
15210 When you try to match against the string "string" the program replaces
15211 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
15212 they will all be replaced with the string. There is a limit of 10 "%s"'s.
15213 <P>
15214 A "Search-Type" of "name-or-email" with "Search-Rule"
15215 of "contains" is equivalent to
15216 <PRE>
15217 (|(cn=*%s*)(mail=*%s*))
15218 </PRE>
15219 <P>
15220 If your server uses a different attribute <EM>name</EM> than
15221 Alpine uses by default,
15222 (for example, it uses "rfc822mail" instead of "mail"),
15223 then you may be able to use one or more of the four attribute configuration
15224 options instead of defining a custom filter:
15225 <P><UL>
15226 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15227 </UL>
15228 <P><UL>
15229 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15230 </UL>
15231 <P><UL>
15232 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15233 </UL>
15234 <P><UL>
15235 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15236 </UL>
15237 <P>
15238 <End of help on this topic>
15239 </BODY>
15240 </HTML>
15241 ======= h_composer_abook_comment =======
15242 <HTML>
15243 <HEAD>
15244 <TITLE>Addressbook Comment Explained</TITLE>
15245 </HEAD>
15246 <BODY>
15247 This is a comment to help you remember what this entry is. The WhereIs
15248 command searches comments so that it is easier to find an entry with a comment
15249 you know about attached to it. This field is not used in the outgoing message.
15250 <P>
15251 Look <A HREF="h_edit_nav_cmds">here</A>
15252 to see the available Editing and Navigation commands.
15253 <P>
15254 <End of help on this topic>
15255 </BODY>
15256 </HTML>
15257 ======= h_composer_abook_addrs =======
15258 <HTML>
15259 <HEAD>
15260 <TITLE>Addressbook Lists</TITLE>
15261 </HEAD>
15262 <BODY>
15263 <H1>Addressbook Lists</H1>
15265 This is a list of addresses to send to when sending to this address book
15266 entry. Each member of the list may be an address or another nickname from
15267 any of your address books. If it is an address, it is OK to include the
15268 full name field as well as the electronic address portion of that address.
15269 For example, the following are all legitimate entries in this field:
15271 <DL><DT> </DT>
15272 <DD>john (a nickname in your address book)
15273 <DD>jdoe@some.domain
15274 <DD>John Doe <jdoe@some.domain>
15275 </DL>
15277 The addresses should be listed separated by commas, just like you would
15278 enter them from the composer.
15280 <P>
15282 The only difference between a distribution list and a simple entry with a
15283 single address, is that a distribution list has more than one address
15284 listed in the Addresses: field, whereas a simple personal entry has just
15285 one address.
15287 <P>
15289 For individual address book entries, if there is a full name in the
15290 Fullname: field (filling in the Fullname: field is not required), it is
15291 used. If the full name is specified in the Address: field and not in the
15292 Fullname: field, then the full name from the Address: field is used.
15294 <P>
15296 If you type the nickname of a distribution list from one of your address
15297 books in the Lcc: field, then the full name of that list is used in the
15298 To: field. If you put a list in the To: or Cc: fields, that list will be
15299 expanded into all of its addresses. If the list has a full name, then
15300 that will appear at the beginning of the addresses.
15302 <DL><DT> </DT>
15303 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
15304 <sal@here.there>
15305 </DL>
15307 If the first address in the distribution list also has a full name, then
15308 the list full name and that full name are combined into something like the
15309 following:
15311 <DL><DT> </DT>
15312 <DD>Sewing Club -- John Smith <john@somewhere>
15313 </DL>
15316 If you specify a list via Lcc, the full name is used in the To: line. If
15317 you specify a list in the To: or Cc: fields, then it uses the same method
15318 as for individual entries for filling in the full name.
15320 <P>
15322 For help with editing and navigation commands, check the Help for the
15323 Nickname: field.
15325 <P>
15326 <End of help on this topic>
15327 </BODY>
15328 </HTML>
15329 ======= h_config_role_nick =======
15330 <HTML>
15331 <HEAD>
15332 <TITLE>Nickname Explained</TITLE>
15333 </HEAD>
15334 <BODY>
15335 <H1>Nickname Explained</H1>
15337 This is a nickname to help you.
15338 You should have a different nickname for each role you define.
15339 The nickname will be used in the SETUP ROLE RULES screen to allow you to
15340 pick a role to edit.
15341 It will also be used when you send a message to let you know you are
15342 sending with a different role than you use by default, and
15343 it will be useful for choosing a role when composing with the Role command
15344 or when composing with one of the Role Uses set to With Confirmation.
15345 This field is not used in the outgoing message.
15346 <P>
15347 Look <A HREF="h_edit_nav_cmds">here</A>
15348 to see the available Editing and Navigation commands.
15349 <P>
15350 <End of help on this topic>
15351 </BODY>
15352 </HTML>
15353 ======= h_config_role_comment =======
15354 <HTML>
15355 <HEAD>
15356 <TITLE>Comment Explained</TITLE>
15357 </HEAD>
15358 <BODY>
15359 <H1>Comment Explained</H1>
15361 This is a comment to help you.
15362 This comment does not play any functional role, it is simply an optional
15363 comment to help you remember what the rule is for.
15364 <P>
15365 Look <A HREF="h_edit_nav_cmds">here</A>
15366 to see the available Editing and Navigation commands.
15367 <P>
15368 <End of help on this topic>
15369 </BODY>
15370 </HTML>
15371 ======= h_config_other_nick =======
15372 <HTML>
15373 <HEAD>
15374 <TITLE>Nickname Explained</TITLE>
15375 </HEAD>
15376 <BODY>
15377 <H1>Nickname Explained</H1>
15379 This is a nickname to help you.
15380 You should have a different nickname for each rule you define.
15381 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15382 pick a rule to edit.
15383 <P>
15384 Look <A HREF="h_edit_nav_cmds">here</A>
15385 to see the available Editing and Navigation commands.
15386 <P>
15387 <End of help on this topic>
15388 </BODY>
15389 </HTML>
15390 ======= h_config_score_nick =======
15391 <HTML>
15392 <HEAD>
15393 <TITLE>Nickname Explained</TITLE>
15394 </HEAD>
15395 <BODY>
15396 <H1>Nickname Explained</H1>
15398 This is a nickname to help you.
15399 You should have a different nickname for each scoring rule you define.
15400 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15401 pick a rule to edit.
15402 <P>
15403 Look <A HREF="h_edit_nav_cmds">here</A>
15404 to see the available Editing and Navigation commands.
15405 <P>
15406 <End of help on this topic>
15407 </BODY>
15408 </HTML>
15409 ======= h_config_incol_nick =======
15410 <HTML>
15411 <HEAD>
15412 <TITLE>Nickname Explained</TITLE>
15413 </HEAD>
15414 <BODY>
15415 <H1>Nickname Explained</H1>
15417 This is a nickname to help you.
15418 You should have a different nickname for each color rule you define.
15419 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15420 pick a rule to edit.
15421 <P>
15422 Look <A HREF="h_edit_nav_cmds">here</A>
15423 to see the available Editing and Navigation commands.
15424 <P>
15425 <End of help on this topic>
15426 </BODY>
15427 </HTML>
15428 ======= h_config_filt_nick =======
15429 <HTML>
15430 <HEAD>
15431 <TITLE>Nickname Explained</TITLE>
15432 </HEAD>
15433 <BODY>
15434 <H1>Nickname Explained</H1>
15436 This is a nickname to help you.
15437 You should have a different nickname for each filtering rule you define.
15438 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15439 pick a rule to edit.
15440 <P>
15441 Look <A HREF="h_edit_nav_cmds">here</A>
15442 to see the available Editing and Navigation commands.
15443 <P>
15444 <End of help on this topic>
15445 </BODY>
15446 </HTML>
15447 ======= h_config_score_topat =======
15448 <HTML>
15449 <HEAD>
15450 <TITLE>"To:" Pattern Explained</TITLE>
15451 </HEAD>
15452 <BODY>
15453 <H1>"To:" Pattern Explained</H1>
15455 Any text you enter as the "To pattern"
15456 will be compared to the recipients from the To: line of
15457 the message being scored.
15458 When the text you entered matches
15459 all or part of the To: line of a message, then the Score Value
15460 you have specified will be added to the score for the message.
15461 (Any other non-blank parts of the Pattern must match, too.)
15462 <P>
15464 You may enter a complete email address, part of an address, or a
15465 list of addresses or partial addresses.
15466 For example:
15467 <P>
15469 <PRE>
15470 To pattern = friend@public.com
15472 To pattern = rated.net
15474 To pattern = xxx@adults.com
15475 admin@msn.com
15476 fool@motleyfool.com
15477 </PRE>
15479 <P>
15480 Each of those are valid To patterns.
15481 <P>
15483 Messages match those patterns if any of the
15484 addresses in the To: line of the message contains the pattern.
15485 If the pattern is a list of patterns
15486 (like the last example above) then it is a match if any of the patterns in
15487 the list match any of the addresses in the To: line.
15488 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15489 present for a match.
15490 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15491 address2 must be present.
15492 That is exactly what using a list does.)
15493 <P>
15495 Some messages may be "bounced" to you, and will
15496 have a "Resent-To:" header line.
15497 If the message contains a Resent-To: line
15498 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15499 Alpine will look for
15500 matches to your "To patterns" there, and <EM>NOT</EM> in
15501 the original To: line.
15502 <P>
15504 When entering a pattern, you may choose an address from your address book
15505 with the "T" command.
15506 <P>
15508 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15509 "!" "toggle NOT" command.
15510 This changes the meaning of the To pattern so that it has the opposite meaning.
15511 It will be considered a match if there are no matches between the
15512 addresses in the To: line and the list of To patterns.
15513 <P>
15514 Don't make the mistake of putting the "!" in the data field for
15515 the pattern.
15516 For example, if you type the characters "!frizzle" into the To
15517 pattern, the pattern will look like:
15518 <P>
15519 <PRE>
15520 To pattern = !frizzle
15521 </PRE>
15522 <P>
15523 This means you want to match the 8 character sequence "!frizzle".
15524 In order to match messages that do not have "frizzle" in
15525 their To field, first type the characters "frizzle" followed
15526 by carriage return for the value of the To pattern, then negate it
15527 by typing the "!" command.
15528 It should end up looking like
15529 <P>
15530 <PRE>
15531 ! To pattern = frizzle
15532 </PRE>
15533 <P>
15534 You are not limited to using the six standard header patterns that are
15535 normally shown (To, From, Sender, Cc, News, and Subject).
15536 You may add any other header to a Pattern by
15537 using the "eXtraHdr" command to specify a different
15538 message header line; and then the Add or Change command to fill in
15539 a pattern for the new header line, just like you would for a standard header.
15540 <P>
15541 A technicality: Since comma is the character used to separate multiple
15542 values in a pattern field, you have to escape comma with a backslash (\) if
15543 you want to include a literal comma in the field.
15544 In other words, if you type a backslash followed by a comma it will
15545 be interpreted as a comma by Alpine, instead of as a separator between
15546 pattern values.
15547 All other backslashes are literal backslashes and should not be escaped.
15548 <P>
15549 Look "<A HREF="h_rule_patterns">here</A>"
15550 for more information on Patterns.
15551 <P>
15552 Look <A HREF="h_edit_nav_cmds">here</A>
15553 to see the available Editing and Navigation commands.
15554 <P>
15555 <End of help on this topic>
15556 </BODY>
15557 </HTML>
15558 ======= h_config_incol_topat =======
15559 <HTML>
15560 <HEAD>
15561 <TITLE>"To:" Pattern Explained</TITLE>
15562 </HEAD>
15563 <BODY>
15564 <H1>"To:" Pattern Explained</H1>
15566 Any text you enter as the "To pattern"
15567 will be compared to the recipients from the To: lines of
15568 the messages in the index.
15569 When the text you entered matches
15570 all or part of the To: line of a message, then the Index Line Color you have
15571 specified will be used for that line in the index.
15572 (Any other non-blank parts of the Pattern must match, too.)
15573 <P>
15575 You may enter a complete email address, part of an address, or a
15576 list of addresses or partial addresses.
15577 For example:
15578 <P>
15580 <PRE>
15581 To pattern = friend@public.com
15582 To pattern = rated.net
15583 To pattern = xxx@adults.com
15584 admin@msn.com
15585 fool@motleyfool.com
15586 </PRE>
15588 <P>
15589 Each of those are valid To patterns.
15590 <P>
15592 Messages match those patterns if any of the
15593 addresses in the To: line of the message contains the pattern.
15594 If the pattern is a list of patterns
15595 (like the last example above) then it is a match if any of the patterns in
15596 the list match any of the addresses in the To: line.
15597 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15598 present for a match.
15599 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15600 address2 must be present.
15601 That is exactly what using a list does.)
15602 <P>
15604 Some messages may be "bounced" to you, and will
15605 have a "Resent-To:" header line.
15606 If the message contains a Resent-To: line
15607 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15608 Alpine will look for
15609 matches to your "To patterns" there, and <EM>NOT</EM> in
15610 the original To: line.
15611 <P>
15613 When entering a pattern, you may choose an address from your address book
15614 with the "T" command.
15615 <P>
15617 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15618 "!" "toggle NOT" command.
15619 This changes the meaning of the To pattern so that it has the opposite meaning.
15620 It will be considered a match if there are no matches between the
15621 addresses in the To: line and the list of To patterns.
15622 <P>
15623 Don't make the mistake of putting the "!" in the data field for
15624 the pattern.
15625 For example, if you type the characters "!frizzle" into the To
15626 pattern, the pattern will look like:
15627 <P>
15628 <PRE>
15629 To pattern = !frizzle
15630 </PRE>
15631 <P>
15632 This means you want to match the 8 character sequence "!frizzle".
15633 In order to match messages that do not have "frizzle" in
15634 their To field, first type the characters "frizzle" followed
15635 by carriage return for the value of the To pattern, then negate it
15636 by typing the "!" command.
15637 It should end up looking like
15638 <P>
15639 <PRE>
15640 ! To pattern = frizzle
15641 </PRE>
15642 <P>
15644 You are not limited to using the six standard header patterns that are
15645 normally shown (To, From, Sender, Cc, News, and Subject).
15646 You may add any other header to a Pattern by
15647 using the "eXtraHdr" command to specify a different
15648 message header line; and then the Add or Change command to fill in
15649 a pattern for the new header line, just like you would for a standard header.
15650 <P>
15651 A technicality: Since comma is the character used to separate multiple
15652 values in a pattern field, you have to escape comma with a backslash (\) if
15653 you want to include a literal comma in the field.
15654 In other words, if you type a backslash followed by a comma it will
15655 be interpreted as a comma by Alpine, instead of as a separator between
15656 pattern values.
15657 All other backslashes are literal backslashes and should not be escaped.
15658 <P>
15659 Look "<A HREF="h_rule_patterns">here</A>"
15660 for more information on Patterns.
15661 <P>
15662 Look <A HREF="h_edit_nav_cmds">here</A>
15663 to see the available Editing and Navigation commands.
15664 <P>
15665 <End of help on this topic>
15666 </BODY>
15667 </HTML>
15668 ======= h_config_other_topat =======
15669 <HTML>
15670 <HEAD>
15671 <TITLE>"To:" Pattern Explained</TITLE>
15672 </HEAD>
15673 <BODY>
15674 <H1>"To:" Pattern Explained</H1>
15676 For some of the OTHER RULES actions, there is no message that is being
15677 compared against.
15678 If that is the case, then only the Current Folder Type is checked.
15679 In particular, this To pattern is ignored.
15680 Actions that fall into this category include both
15681 Sort Order and Index Format.
15682 <P>
15683 A technicality: Since comma is the character used to separate multiple
15684 values in a pattern field, you have to escape comma with a backslash (\) if
15685 you want to include a literal comma in the field.
15686 In other words, if you type a backslash followed by a comma it will
15687 be interpreted as a comma by Alpine, instead of as a separator between
15688 pattern values.
15689 All other backslashes are literal backslashes and should not be escaped.
15690 <P>
15691 Look "<A HREF="h_rule_patterns">here</A>"
15692 for more information on Patterns.
15693 <P>
15694 Look <A HREF="h_edit_nav_cmds">here</A>
15695 to see the available Editing and Navigation commands.
15696 <P>
15697 <End of help on this topic>
15698 </BODY>
15699 </HTML>
15700 ======= h_config_filt_topat =======
15701 <HTML>
15702 <HEAD>
15703 <TITLE>"To:" Pattern Explained</TITLE>
15704 </HEAD>
15705 <BODY>
15706 <H1>"To:" Pattern Explained</H1>
15708 Any text you enter as the "To pattern"
15709 will be compared to the recipients from the To: line of
15710 messages when Alpine opens folders.
15711 When the text you entered matches
15712 all or part of the To: line of a message, then the Filter Action you have
15713 specified will be carried out.
15714 (Any other non-blank parts of the Pattern must match, too.)
15715 <P>
15717 You may enter a complete email address, part of an address, or a
15718 list of addresses or partial addresses.
15719 For example:
15720 <P>
15722 <PRE>
15723 To pattern = friend@public.com
15724 To pattern = rated.net
15725 To pattern = xxx@adults.com
15726 admin@msn.com
15727 fool@motleyfool.com
15728 </PRE>
15730 <P>
15731 Each of those are valid To patterns.
15732 <P>
15734 Messages match those patterns if any of the
15735 addresses in the To: line of the message contains the pattern.
15736 If the pattern is a list of patterns
15737 (like the last example above) then it is a match if any of the patterns in
15738 the list match any of the addresses in the To: line.
15739 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15740 present for a match.
15741 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15742 address2 must be present.
15743 That is exactly what using a list does.)
15744 <P>
15746 Some messages may be "bounced" to you, and will
15747 have a "Resent-To:" header line.
15748 If the message contains a Resent-To: line
15749 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15750 Alpine will look for
15751 matches to your "To patterns" there, and <EM>NOT</EM> in
15752 the original To: line.
15753 <P>
15755 When entering a pattern, you may choose an address from your address book
15756 with the "T" command.
15757 <P>
15759 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15760 "!" "toggle NOT" command.
15761 This changes the meaning of the To pattern so that it has the opposite meaning.
15762 It will be considered a match if there are no matches between the
15763 addresses in the To: line and the list of To patterns.
15764 <P>
15765 Don't make the mistake of putting the "!" in the data field for
15766 the pattern.
15767 For example, if you type the characters "!frizzle" into the To
15768 pattern, the pattern will look like:
15769 <P>
15770 <PRE>
15771 To pattern = !frizzle
15772 </PRE>
15773 <P>
15774 This means you want to match the 8 character sequence "!frizzle".
15775 In order to match messages that do not have "frizzle" in
15776 their To field, first type the characters "frizzle" followed
15777 by carriage return for the value of the To pattern, then negate it
15778 by typing the "!" command.
15779 It should end up looking like
15780 <P>
15781 <PRE>
15782 ! To pattern = frizzle
15783 </PRE>
15784 <P>
15786 You are not limited to using the six standard header patterns that are
15787 normally shown (To, From, Sender, Cc, News, and Subject).
15788 You may add any other header to a Pattern by
15789 using the "eXtraHdr" command to specify a different
15790 message header line; and then the Add or Change command to fill in
15791 a pattern for the new header line, just like you would for a standard header.
15792 <P>
15793 A technicality: Since comma is the character used to separate multiple
15794 values in a pattern field, you have to escape comma with a backslash (\) if
15795 you want to include a literal comma in the field.
15796 In other words, if you type a backslash followed by a comma it will
15797 be interpreted as a comma by Alpine, instead of as a separator between
15798 pattern values.
15799 All other backslashes are literal backslashes and should not be escaped.
15800 <P>
15801 Look "<A HREF="h_rule_patterns">here</A>"
15802 for more information on Patterns.
15803 <P>
15804 Look <A HREF="h_edit_nav_cmds">here</A>
15805 to see the available Editing and Navigation commands.
15806 <P>
15807 <End of help on this topic>
15808 </BODY>
15809 </HTML>
15810 ======= h_config_role_topat =======
15811 <HTML>
15812 <HEAD>
15813 <TITLE>"To:" Pattern Explained</TITLE>
15814 </HEAD>
15815 <BODY>
15816 <H1>"To:" Pattern Explained</H1>
15818 Any text you enter as the "To pattern"
15819 will be compared to the recipients from the To: line of
15820 the message being replied to or forwarded.
15821 (Any other non-blank parts of the Pattern must match, too.)
15822 In the case of the Compose command, this pattern and the other header
15823 patterns are ignored.
15824 <P>
15826 You may enter a complete email address, part of an address, or a
15827 list of addresses or partial addresses.
15828 For example:
15829 <P>
15831 <PRE>
15832 To pattern = friend@public.com
15833 To pattern = rated.net
15834 To pattern = xxx@adults.com
15835 admin@msn.com
15836 fool@motleyfool.com
15837 </PRE>
15839 <P>
15840 Each of those are valid To patterns.
15841 <P>
15843 Messages match those patterns if any of the
15844 addresses in the To: line of the message contains the pattern.
15845 If the pattern is a list of patterns
15846 (like the last example above) then it is a match if any of the patterns in
15847 the list match any of the addresses in the To: line.
15848 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15849 present for a match.
15850 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15851 address2 must be present.
15852 That is exactly what using a list does.)
15853 <P>
15855 Some messages may be "bounced" to you, and will
15856 have a "Resent-To:" header line.
15857 If the message contains a Resent-To: line
15858 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15859 Alpine will look for
15860 matches to your "To patterns" there, and <EM>NOT</EM> in
15861 the original To: line.
15862 <P>
15864 When entering a pattern, you may choose an address from your address book
15865 with the "T" command.
15866 <P>
15868 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15869 "!" "toggle NOT" command.
15870 This changes the meaning of the To pattern so that it has the opposite meaning.
15871 It will be considered a match if there are no matches between the
15872 addresses in the To: line and the list of To patterns.
15873 <P>
15874 Don't make the mistake of putting the "!" in the data field for
15875 the pattern.
15876 For example, if you type the characters "!frizzle" into the To
15877 pattern, the pattern will look like:
15878 <P>
15879 <PRE>
15880 To pattern = !frizzle
15881 </PRE>
15882 <P>
15883 This means you want to match the 8 character sequence "!frizzle".
15884 In order to match messages that do not have "frizzle" in
15885 their To field, first type the characters "frizzle" followed
15886 by carriage return for the value of the To pattern, then negate it
15887 by typing the "!" command.
15888 It should end up looking like
15889 <P>
15890 <PRE>
15891 ! To pattern = frizzle
15892 </PRE>
15893 <P>
15895 You are not limited to using the six standard header patterns that are
15896 normally shown (To, From, Sender, Cc, News, and Subject).
15897 You may add any other header to a Pattern by
15898 using the "eXtraHdr" command to specify a different
15899 message header line; and then the Add or Change command to fill in
15900 a pattern for the new header line, just like you would for a standard header.
15901 <P>
15902 A technicality: Since comma is the character used to separate multiple
15903 values in a pattern field, you have to escape comma with a backslash (\) if
15904 you want to include a literal comma in the field.
15905 In other words, if you type a backslash followed by a comma it will
15906 be interpreted as a comma by Alpine, instead of as a separator between
15907 pattern values.
15908 All other backslashes are literal backslashes and should not be escaped.
15909 <P>
15910 Look "<A HREF="h_rule_patterns">here</A>"
15911 for more information on Patterns.
15912 <P>
15913 Look <A HREF="h_edit_nav_cmds">here</A>
15914 to see the available Editing and Navigation commands.
15915 <P>
15916 <End of help on this topic>
15917 </BODY>
15918 </HTML>
15919 ======= h_config_role_frompat =======
15920 <HTML>
15921 <HEAD>
15922 <TITLE>"From:" Pattern Explained</TITLE>
15923 </HEAD>
15924 <BODY>
15925 <H1>"From:" Pattern Explained</H1>
15927 This is just like the "To pattern" except that it is compared with
15928 the address in the From: line of the message
15929 instead of the addresses from the To: line.
15930 See the help for the To pattern for more information on header patterns.
15931 <P>
15932 Look "<A HREF="h_rule_patterns">here</A>"
15933 for more information on Patterns.
15934 <P>
15935 Look <A HREF="h_edit_nav_cmds">here</A>
15936 to see the available Editing and Navigation commands.
15937 <P>
15938 <End of help on this topic>
15939 </BODY>
15940 </HTML>
15941 ======= h_config_role_senderpat =======
15942 <HTML>
15943 <HEAD>
15944 <TITLE>"Sender:" Pattern Explained</TITLE>
15945 </HEAD>
15946 <BODY>
15947 <H1>"Sender:" Pattern Explained</H1>
15949 This is just like the "To pattern" except that it is compared with
15950 the address from the Sender: line of the message
15951 instead of the addresses from the To: line.
15952 See the help for the To pattern for more information on header patterns.
15953 <P>
15954 Look "<A HREF="h_rule_patterns">here</A>"
15955 for more information on Patterns.
15956 <P>
15957 Look <A HREF="h_edit_nav_cmds">here</A>
15958 to see the available Editing and Navigation commands.
15959 <P>
15960 <End of help on this topic>
15961 </BODY>
15962 </HTML>
15963 ======= h_config_role_ccpat =======
15964 <HTML>
15965 <HEAD>
15966 <TITLE>"Cc:" Pattern Explained</TITLE>
15967 </HEAD>
15968 <BODY>
15969 <H1>"Cc:" Pattern Explained</H1>
15971 This is just like the "To pattern" except that it is compared with
15972 the addresses from the Cc: line of the message
15973 instead of the addresses from the To: line.
15974 See the help for the To pattern for more information on header patterns.
15975 <P>
15976 Look "<A HREF="h_rule_patterns">here</A>"
15977 for more information on Patterns.
15978 <P>
15979 Look <A HREF="h_edit_nav_cmds">here</A>
15980 to see the available Editing and Navigation commands.
15981 <P>
15982 <End of help on this topic>
15983 </BODY>
15984 </HTML>
15985 ======= h_config_role_recippat =======
15986 <HTML>
15987 <HEAD>
15988 <TITLE>Recipient Pattern Explained</TITLE>
15989 </HEAD>
15990 <BODY>
15991 <H1>Recipient Pattern Explained</H1>
15993 This is just like the "To pattern" except that it is compared with
15994 the addresses from both the To: line and the Cc: line of the
15995 message instead of just the addresses from the To: line.
15996 In other words, it is considered a match if the pattern matches
15997 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
15998 in the Cc: line.
15999 (Notice that defining the Recipient pattern does not have the same
16000 effect as defining both the To and Cc patterns.
16001 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
16002 It is equivalent to having two different rules;
16003 one with a To pattern and the other with the same Cc pattern.)
16004 <P>
16005 A technicality: Since comma is the character used to separate multiple
16006 values in a pattern field, you have to escape comma with a backslash (\) if
16007 you want to include a literal comma in the field.
16008 In other words, if you type a backslash followed by a comma it will
16009 be interpreted as a comma by Alpine, instead of as a separator between
16010 pattern values.
16011 All other backslashes are literal backslashes and should not be escaped.
16012 <P>
16013 Look "<A HREF="h_rule_patterns">here</A>"
16014 for more information on Patterns.
16015 <P>
16016 Look <A HREF="h_edit_nav_cmds">here</A>
16017 to see the available Editing and Navigation commands.
16018 <P>
16019 <End of help on this topic>
16020 </BODY>
16021 </HTML>
16022 ======= h_config_role_particpat =======
16023 <HTML>
16024 <HEAD>
16025 <TITLE>Participant Pattern Explained</TITLE>
16026 </HEAD>
16027 <BODY>
16028 <H1>Participant Pattern Explained</H1>
16030 This is just like the "To pattern" except that it is compared with
16031 the addresses from the From: line, the To: line, and the Cc: line of the
16032 message instead of just the addresses from the To: line.
16033 In other words, it is considered a match if the pattern matches
16034 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
16035 in the To: line, <EM>OR</EM> an address in the Cc: line.
16036 (Notice that defining the Participant pattern does not have the same
16037 effect as defining all of the From, To, and Cc patterns.
16038 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
16039 From <EM>AND</EM> To <EM>AND</EM> Cc.
16040 It is equivalent to having three different rules;
16041 one with a From pattern, another with the same To pattern, and a third with
16042 the same Cc pattern.)
16043 <P>
16044 A technicality: Since comma is the character used to separate multiple
16045 values in a pattern field, you have to escape comma with a backslash (\) if
16046 you want to include a literal comma in the field.
16047 In other words, if you type a backslash followed by a comma it will
16048 be interpreted as a comma by Alpine, instead of as a separator between
16049 pattern values.
16050 All other backslashes are literal backslashes and should not be escaped.
16051 <P>
16052 Look "<A HREF="h_rule_patterns">here</A>"
16053 for more information on Patterns.
16054 <P>
16055 Look <A HREF="h_edit_nav_cmds">here</A>
16056 to see the available Editing and Navigation commands.
16057 <P>
16058 <End of help on this topic>
16059 </BODY>
16060 </HTML>
16061 ======= h_config_role_newspat =======
16062 <HTML>
16063 <HEAD>
16064 <TITLE>News Pattern Explained</TITLE>
16065 </HEAD>
16066 <BODY>
16067 <H1>News Pattern Explained</H1>
16069 If this pattern is non-blank, then for this rule to be considered a
16070 match, at least one of the newsgroups from
16071 the Newsgroups line of the message must match this pattern.
16072 If this pattern is a list of patterns, then at least one of the
16073 newsgroups must match at least one of the patterns.
16074 (Any other non-blank parts of the Pattern must match, too.)
16075 <P>
16076 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
16077 "!" "toggle NOT" command.
16078 This changes the meaning of the News pattern so that it has the opposite meaning.
16079 It will be considered a match if there are no matches between the
16080 addresses in the Newsgroups: line and the list of News patterns.
16081 <P>
16082 Don't make the mistake of putting the "!" in the data field for
16083 the pattern.
16084 For example, if you type the characters "!frizzle" into the News
16085 pattern, the pattern will look like:
16086 <P>
16087 <PRE>
16088 News pattern = !frizzle
16089 </PRE>
16090 <P>
16091 This means you want to match the 8 character sequence "!frizzle".
16092 In order to match messages that do not have "frizzle" in
16093 their Newsgroups header, first type the characters "frizzle" followed
16094 by carriage return for the value of the News pattern, then negate it
16095 by typing the "!" command.
16096 It should end up looking like
16097 <P>
16098 <PRE>
16099 ! News pattern = frizzle
16100 </PRE>
16101 <P>
16102 A technicality: Since comma is the character used to separate multiple
16103 values in a pattern field, you have to escape comma with a backslash (\) if
16104 you want to include a literal comma in the field.
16105 In other words, if you type a backslash followed by a comma it will
16106 be interpreted as a comma by Alpine, instead of as a separator between
16107 pattern values.
16108 All other backslashes are literal backslashes and should not be escaped.
16109 <P>
16111 Look "<A HREF="h_rule_patterns">here</A>"
16112 for more information on Patterns.
16113 <P>
16114 Look <A HREF="h_edit_nav_cmds">here</A>
16115 to see the available Editing and Navigation commands.
16116 <P>
16117 <End of help on this topic>
16118 </BODY>
16119 </HTML>
16120 ======= h_config_role_subjpat =======
16121 <HTML>
16122 <HEAD>
16123 <TITLE>"Subject:" Pattern Explained</TITLE>
16124 </HEAD>
16125 <BODY>
16126 <H1>"Subject:" Pattern Explained</H1>
16128 This is similar to the other parts of the Pattern.
16129 It is compared with
16130 the contents from the Subject of the message.
16131 <P>
16132 Look "<A HREF="h_rule_patterns">here</A>"
16133 for more information on Patterns.
16134 <P>
16135 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
16136 "!" "toggle NOT" command.
16137 This changes the meaning of the Subject pattern so that it has the opposite meaning.
16138 It will be considered a match if there are no matches between the
16139 text in the Subject: line and the list of Subject patterns.
16140 <P>
16142 If you wish to have a header pattern that is not one of the six standard
16143 header patterns, you may add it with the "eXtraHdr" command.
16144 <P>
16145 A technicality: Since comma is the character used to separate multiple
16146 values in a pattern field, you have to escape comma with a backslash (\) if
16147 you want to include a literal comma in the field.
16148 In other words, if you type a backslash followed by a comma it will
16149 be interpreted as a comma by Alpine, instead of as a separator between
16150 pattern values.
16151 All other backslashes are literal backslashes and should not be escaped.
16152 <P>
16153 Look <A HREF="h_edit_nav_cmds">here</A>
16154 to see the available Editing and Navigation commands.
16155 <P>
16156 <End of help on this topic>
16157 </BODY>
16158 </HTML>
16159 ======= h_config_role_alltextpat =======
16160 <HTML>
16161 <HEAD>
16162 <TITLE>AllText Pattern Explained</TITLE>
16163 </HEAD>
16164 <BODY>
16165 <H1>AllText Pattern Explained</H1>
16167 This is similar to the header patterns.
16168 Instead of comparing with text in a particular header field it
16169 is compared with all of the text in the message header and body.
16170 <P>
16171 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
16172 "!" "toggle NOT" command.
16173 This changes the meaning of the AllText pattern so that it has the opposite meaning.
16174 It will be considered a match if there are no matches between the
16175 text of the message and the list of AllText patterns.
16176 <P>
16177 Don't make the mistake of putting the "!" in the data field for
16178 the pattern.
16179 For example, if you type the characters "!frizzle" into the AllText
16180 pattern, the pattern will look like:
16181 <P>
16182 <PRE>
16183 AllText pattern = !frizzle
16184 </PRE>
16185 <P>
16186 This means you want to match the 8 character sequence "!frizzle".
16187 In order to match messages that do not have "frizzle" in
16188 the text of the message, first type the characters "frizzle" followed
16189 by carriage return for the value of the AllText pattern, then negate it
16190 by typing the "!" command.
16191 It should end up looking like
16192 <P>
16193 <PRE>
16194 ! AllText pattern = frizzle
16195 </PRE>
16196 <P>
16197 It is possible that you may notice degraded performance when using
16198 AllText Patterns.
16199 <P>
16200 A technicality: Since comma is the character used to separate multiple
16201 values in a pattern field, you have to escape comma with a backslash (\) if
16202 you want to include a literal comma in the field.
16203 In other words, if you type a backslash followed by a comma it will
16204 be interpreted as a comma by Alpine, instead of as a separator between
16205 pattern values.
16206 All other backslashes are literal backslashes and should not be escaped.
16207 <P>
16208 Look "<A HREF="h_rule_patterns">here</A>"
16209 for more information on Patterns.
16210 <P>
16211 Look <A HREF="h_edit_nav_cmds">here</A>
16212 to see the available Editing and Navigation commands.
16213 <P>
16214 <End of help on this topic>
16215 </BODY>
16216 </HTML>
16217 ======= h_config_role_bodytextpat =======
16218 <HTML>
16219 <HEAD>
16220 <TITLE>BodyText Pattern Explained</TITLE>
16221 </HEAD>
16222 <BODY>
16223 <H1>BodyText Pattern Explained</H1>
16225 This is similar to the header patterns.
16226 Instead of comparing with text in a particular header field it
16227 is compared with all of the text in the message body.
16228 <P>
16229 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
16230 "!" "toggle NOT" command.
16231 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
16232 It will be considered a match if there are no matches between the
16233 text of the body of the message and the list of BodyText patterns.
16234 <P>
16235 Don't make the mistake of putting the "!" in the data field for
16236 the pattern.
16237 For example, if you type the characters "!frizzle" into the BodyText
16238 pattern, the pattern will look like:
16239 <P>
16240 <PRE>
16241 BdyText pattern = !frizzle
16242 </PRE>
16243 <P>
16244 This means you want to match the 8 character sequence "!frizzle".
16245 In order to match messages that do not have "frizzle" in
16246 their BodyText, first type the characters "frizzle" followed
16247 by carriage return for the value of the BodyText pattern, then negate it
16248 by typing the "!" command.
16249 It should end up looking like
16250 <P>
16251 <PRE>
16252 ! BodyText pattern = frizzle
16253 </PRE>
16254 <P>
16255 It is possible that you may notice degraded performance when using
16256 BodyText Patterns.
16257 <P>
16258 A technicality: Since comma is the character used to separate multiple
16259 values in a pattern field, you have to escape comma with a backslash (\) if
16260 you want to include a literal comma in the field.
16261 In other words, if you type a backslash followed by a comma it will
16262 be interpreted as a comma by Alpine, instead of as a separator between
16263 pattern values.
16264 All other backslashes are literal backslashes and should not be escaped.
16265 <P>
16266 Look "<A HREF="h_rule_patterns">here</A>"
16267 for more information on Patterns.
16268 <P>
16269 Look <A HREF="h_edit_nav_cmds">here</A>
16270 to see the available Editing and Navigation commands.
16271 <P>
16272 <End of help on this topic>
16273 </BODY>
16274 </HTML>
16275 ======= h_config_role_charsetpat =======
16276 <HTML>
16277 <HEAD>
16278 <TITLE>Character Set Pattern Explained</TITLE>
16279 </HEAD>
16280 <BODY>
16281 <H1>Character Set Pattern Explained</H1>
16283 A message may use one or more character sets.
16284 This part of the Pattern matches messages that make use of
16285 certain specified character sets.
16286 It will be considered a match if a message uses any of the character
16287 sets in the list you give here.
16289 <P>
16290 When filling in a value for this field, you may use
16291 the "T" command, which presents you with a large list of
16292 possible character sets to choose from.
16293 You may also just type in the name of a character set, and it need not
16294 be one that Alpine knows about.
16296 <P>
16297 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
16298 GB2312) you may also use some shorthand names that Alpine provides.
16299 These names are more understandable shorthand names for sets of
16300 character set names.
16301 Two examples are "Cyrillic" and "Greek".
16302 Selecting one of these shorthand names is equivalent to selecting all of
16303 the character sets that make up the set.
16304 You can see all of these shorthand names and the lists of character sets
16305 they stand for by typing the "T" command.
16307 <P>
16308 For the purposes of this Pattern,
16309 Alpine will search through a message for all of the text parts and
16310 collect the character sets declared for each part.
16311 It will also look in the Subject line for a character set used there.
16312 Alpine does not actually look at the text of the message or the text
16313 of the Subject to determine if a declared character set is actually
16314 used, it looks only at the declarations themselves in the MIME part headers
16315 and in the Subject.
16317 <P>
16318 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
16319 "!" "toggle NOT" command.
16320 This changes the meaning of the Character Set pattern so that
16321 it has the opposite meaning.
16322 It will be considered a match if none of the character sets in the
16323 list are used in a message.
16324 <P>
16325 Don't make the mistake of putting the "!" in the data field for
16326 the pattern.
16327 For example, if you type the characters "!GB2312" into the
16328 Character Set pattern, the pattern will look like:
16329 <P>
16330 <PRE>
16331 Charset pattern = !GB2312
16332 </PRE>
16333 <P>
16334 This means you want to match the 7 character sequence "!GB2312".
16335 In order to match messages that do not have the
16336 character set "GB2312"
16337 set, first type the characters "GB2312" followed
16338 by carriage return for the value of the Character Set pattern, then negate it
16339 by typing the "!" command.
16340 It should end up looking like
16341 <P>
16342 <PRE>
16343 ! Charset pattern = GB2312
16344 </PRE>
16345 <P>
16346 A technicality: Since comma is the character used to separate multiple
16347 values in a pattern field, you have to escape comma with a backslash (\) if
16348 you want to include a literal comma in the field.
16349 In other words, if you type a backslash followed by a comma it will
16350 be interpreted as a comma by Alpine, instead of as a separator between
16351 pattern values.
16352 All other backslashes are literal backslashes and should not be escaped.
16353 <P>
16354 Look "<A HREF="h_rule_patterns">here</A>"
16355 for more information on Patterns.
16356 <P>
16357 Look <A HREF="h_edit_nav_cmds">here</A>
16358 to see the available Editing and Navigation commands.
16359 <P>
16360 <End of help on this topic>
16361 </BODY>
16362 </HTML>
16363 ======= h_config_role_keywordpat =======
16364 <HTML>
16365 <HEAD>
16366 <TITLE>Keyword Pattern Explained</TITLE>
16367 </HEAD>
16368 <BODY>
16369 <H1>Keyword Pattern Explained</H1>
16371 A folder may have user-defined keywords.
16372 These are similar to the Important flag, which the user may set using the
16373 Flag command.
16374 The difference is that the Important flag is always present for each folder.
16375 User-defined keywords are picked by the user.
16376 You may add new keywords by defining them in the
16377 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16378 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16379 the Flag command may be used to set or clear the keyword on individual messages.
16380 If you have given a keyword a nickname when configuring it,
16381 that nickname may be used instead of the actual keyword.
16383 <P>
16384 When filling in a value for this field, it may be easiest to use
16385 the "T" command, which presents you with a list of the keywords
16386 you have defined to choose from.
16388 <P>
16389 This part of the Pattern matches messages with certain keywords set.
16390 It will be considered a match if a message has any of the keywords in the
16391 list set.
16392 A keyword that you have not defined using the
16393 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16394 will not be a match.
16396 <P>
16397 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16398 "!" "toggle NOT" command.
16399 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16400 It will be considered a match if none of the keywords in the list are set
16401 for a message.
16402 A keyword that you have not defined using the
16403 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16404 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16405 <P>
16406 Don't make the mistake of putting the "!" in the data field for
16407 the pattern.
16408 For example, if you type the characters "!frizzle" into the Keyword
16409 pattern, the pattern will look like:
16410 <P>
16411 <PRE>
16412 Keyword pattern = !frizzle
16413 </PRE>
16414 <P>
16415 This means you want to match the 8 character sequence "!frizzle".
16416 In order to match messages that do not have the keyword "frizzle"
16417 set, first type the characters "frizzle" followed
16418 by carriage return for the value of the Keyword pattern, then negate it
16419 by typing the "!" command.
16420 It should end up looking like
16421 <P>
16422 <PRE>
16423 ! Keyword pattern = frizzle
16424 </PRE>
16425 <P>
16426 A technicality: Since comma is the character used to separate multiple
16427 values in a pattern field, you have to escape comma with a backslash (\) if
16428 you want to include a literal comma in the field.
16429 In other words, if you type a backslash followed by a comma it will
16430 be interpreted as a comma by Alpine, instead of as a separator between
16431 pattern values.
16432 All other backslashes are literal backslashes and should not be escaped.
16433 <P>
16434 Look "<A HREF="h_rule_patterns">here</A>"
16435 for more information on Patterns.
16436 <P>
16437 Look <A HREF="h_edit_nav_cmds">here</A>
16438 to see the available Editing and Navigation commands.
16439 <P>
16440 <End of help on this topic>
16441 </BODY>
16442 </HTML>
16443 ======= h_config_role_arbpat =======
16444 <HTML>
16445 <HEAD>
16446 <TITLE>Extra Header Patterns Explained</TITLE>
16447 </HEAD>
16448 <BODY>
16449 <H1>Extra Header Patterns Explained</H1>
16451 The header patterns that come after the Participant pattern but before the
16452 AllText pattern are extra header patterns that you have added to a rule's
16453 Pattern. These are just like the other header patterns except that
16454 the contents of the particular header listed on the left hand side will
16455 be used for comparisons.
16456 <P>
16457 The "eXtraHdr" command may be used to add more of these
16458 header patterns to the rule you are editing.
16459 <P>
16460 The "RemoveHdr" command may be used to delete the highlighted
16461 extra header pattern from the rule you are editing.
16462 <P>
16463 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16464 "!" "toggle NOT" command.
16465 This changes the meaning of the pattern so that it has the opposite meaning.
16466 It will be considered a match if there are no matches between the
16467 text in the header line and the list of patterns.
16468 <P>
16469 Don't make the mistake of putting the "!" in the data field for
16470 the pattern.
16471 For example, if you type the characters "!frizzle" into the
16472 pattern, the pattern will look like:
16473 <P>
16474 <PRE>
16475 Xyz pattern = !frizzle
16476 </PRE>
16477 <P>
16478 This means you want to match the 8 character sequence "!frizzle".
16479 In order to match messages that do not have "frizzle" in
16480 their Xyz field, first type the characters "frizzle" followed
16481 by carriage return for the value of the pattern, then negate it
16482 by typing the "!" command.
16483 It should end up looking like
16484 <P>
16485 <PRE>
16486 ! Xyz pattern = frizzle
16487 </PRE>
16489 <P>
16490 A technicality: Since comma is the character used to separate multiple
16491 values in a pattern field, you have to escape comma with a backslash (\) if
16492 you want to include a literal comma in the field.
16493 In other words, if you type a backslash followed by a comma it will
16494 be interpreted as a comma by Alpine, instead of as a separator between
16495 pattern values.
16496 All other backslashes are literal backslashes and should not be escaped.
16497 <P>
16498 Look "<A HREF="h_rule_patterns">here</A>"
16499 for more information on Patterns.
16500 <P>
16501 Look <A HREF="h_edit_nav_cmds">here</A>
16502 to see the available Editing and Navigation commands.
16503 <P>
16504 <End of help on this topic>
16505 </BODY>
16506 </HTML>
16507 ======= h_config_role_cat_cmd =======
16508 <HTML>
16509 <HEAD>
16510 <TITLE>Categorizer Command Explained</TITLE>
16511 </HEAD>
16512 <BODY>
16513 <H1>Categorizer Command Explained</H1>
16515 This is a command that is run with its standard input set to the message
16516 being checked and its standard output discarded.
16517 The full directory path should be specified.
16518 The command will be run and then its exit status will be checked against
16519 the Exit Status Interval, which defaults to just the value zero.
16520 If the exit status of the command falls in the interval, it is considered
16521 a match, otherwise it is not a match.
16522 <P>
16524 This option may actually be a list of commands.
16525 The first one that exists and is executable is used.
16526 That makes it possible to use the same configuration with Unix Alpine and
16527 PC-Alpine.
16528 <P>
16530 If none of the commands in the list exists and is executable then the rule
16531 is <EM>not</EM> a match.
16532 If it is possible that the command may not exist, you should be careful
16533 to structure your rules so that nothing destructive
16534 happens when the command does not exist.
16535 For example, you might have a filter that filters away spam when there is
16536 a match but does nothing when there is not a match.
16537 That would cause no harm if the command didn't exist.
16538 However, if you have a filter that filters away spam when there is not
16539 a match and keeps it when there is a match, that would filter everything
16540 if the categorizer command didn't exist.
16541 <P>
16542 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16543 setup for the bogofilter filter.
16545 <P>
16546 Look "<A HREF="h_rule_patterns">here</A>"
16547 for more information on Patterns.
16548 <P>
16549 Look <A HREF="h_edit_nav_cmds">here</A>
16550 to see the available Editing and Navigation commands.
16551 <P>
16552 <End of help on this topic>
16553 </BODY>
16554 </HTML>
16555 ======= h_config_role_cat_cmd_example =======
16556 <HTML>
16557 <HEAD>
16558 <TITLE>Categorizer Command Example</TITLE>
16559 </HEAD>
16560 <BODY>
16561 <H1>Categorizer Command Example</H1>
16563 Bogofilter
16564 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16565 is a mail filter that attempts to classify mail as spam or
16566 non-spam using statistical analysis of the message content.
16567 When run with no arguments and a message as standard input, it exits with
16568 exit status 0 if it thinks a message is spam and 1 if it thinks
16569 it is not spam.
16570 To use bogofilter as your Categorizer Command you would simply set Command to
16571 the pathname of the bogofilter program.
16572 For example,
16573 <P>
16574 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16575 <P>
16576 Exit status of zero is what you are interested in, so you'd set the
16577 Exit Status Interval to
16578 <P>
16579 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16580 <P>
16582 In order to prevent downloading an entire huge message to check for spam, you
16583 might want to set the Character Limit to a few thousand characters (the
16584 assumption being that the spam will reveal itself in those characters)
16585 <P>
16586 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16587 <P>
16589 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16590 be to move the message to a spam folder.
16591 It would usually be wise to also check the "Message is Recent"
16592 part of the rule so that messages are only checked when they first arrive,
16593 and to restrict the Current Folder Type to just your INBOX.
16594 The reason for checking only Recent messages is to save the time it takes
16595 to run bogofilter on each message.
16596 As an experiment, you might start out by using this in an Indexcolor Rule
16597 instead of a Filter Rule.
16598 In that case, you probably wouldn't check the Recent checkbox.
16599 <P>
16600 The use described above assumes that you are somehow maintaining bogofilter's
16601 database of words associated with spam and non-spam messages.
16602 One way to start your database would be to select a bunch of spam messages
16603 in Alpine (you might Save spam messages to a special folder or use Alpine's
16604 Select command to select several) and then Apply
16605 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16606 a pipe command to the spam messages.
16607 For example, you could have a shell script or an alias
16608 called <EM>this_is_spam</EM>, which would simply be the command
16609 <P>
16610 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16611 <P>
16613 It is probably best to use the pipe command's Raw Text, With Delimiter,
16614 and Free Output options,
16615 which are at the bottom of the screen when you type the pipe command.
16616 That's because bogofilter expects the raw message as input, and uses
16617 the Delimiters to tell when a new message starts.
16618 You would not need to use a separate pipe for each message, because
16619 bogofilter can handle multiple messages at once.
16620 <P>
16621 Similarly, you would select a group of non-spam messages
16622 and run them through a <EM>this_is_nonspam</EM> script
16623 that was something like
16624 <P>
16625 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16626 <P>
16628 For the more adventurous, the next step might be to automate the upkeep of
16629 the bogofilter database.
16630 It might make more sense to have bogofilter be part of the delivery process,
16631 but it is also possible to do it entirely from within Alpine.
16632 Instead of using just plain "bogofilter" as the Categorizer Command,
16633 the "-u" argument will cause bogofilter to update the database.
16634 <P>
16635 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16636 <P>
16637 You'd want a couple more aliases or shell scripts called something like
16638 <EM>change_to_spam</EM>
16639 <P>
16640 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16641 <P>
16642 and
16643 <EM>change_to_nonspam</EM>
16644 <P>
16645 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16646 <P>
16647 When you run across a message in your INBOX that should have been
16648 classified as spam you would pipe it to the change_to_spam script, and
16649 when you run across a message in your spam folder that should have been
16650 left in your INBOX you would pipe it through change_to_nonspam.
16652 <P>
16653 There is a technical problem with this approach.
16654 Alpine may check your filters more than once.
16655 In particular, every time you start Alpine the filters will be checked for
16656 each message.
16657 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16658 then Alpine will recheck for matches in messages that have changed state
16659 at the time you close the folder and before expunging.
16660 This is usually ok.
16661 However, in this case it is a problem because the command
16662 <P>
16663 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16664 <P>
16665 has the side effect of updating the database.
16666 So you run the risk of updating the database multiple times for a single
16667 message instead of updating it just once per message.
16668 There are some ways to work around this problem.
16669 What you need is a way to mark the message after you have run the filter.
16670 One way to mark messages is with the use of a keyword (say "Bogo").
16671 Besides having the filter move the message to a spam folder, also have it
16672 set the Bogo keyword.
16673 (Note that you will have to set up the "Bogo" keyword in the
16674 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16675 This rule can only set the Bogo keyword for the messages that it matches.
16676 You will also need to add a second rule right after this one that
16677 matches all the messages that don't have the Bogo keyword set
16678 (put the keyword in the Keyword pattern and toggle
16679 the Not with the ! command)
16680 and takes the action of setting it.
16681 Then change the "bogofilter -u" rule so that it won't be a match
16682 (and so it won't re-run the bogofilter command) if the keyword is already
16683 set.
16684 <P>
16685 What you will end up with is a rule that runs "bogofilter -u"
16686 on all messages that don't have the Bogo keyword set.
16687 This will have the side effect of inserting that message in the bogofilter
16688 database, match or not.
16689 If this rule matches (it is spam), the Bogo keyword will be set and
16690 the message will be moved to a spam folder.
16691 If it does not match, the
16692 following rule will mark the message by turning on the keyword.
16693 This second rule should be a non-terminating
16694 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
16695 rule so that it doesn't stop the filtering process before the rest of
16696 your rules are consulted.
16698 <P>
16699 In summary, the first rule is something like
16700 <PRE>
16701 Nickname = bogofilter -u rule
16702 Current Folder Type =
16703 (*) Specific
16704 Folder = INBOX
16706 ! Keyword pattern = Bogo
16708 External Categorizer Commands =
16709 Command = /usr/local/bin/bogofilter -u
16710 Exit Status Interval = (0,0)
16711 Character Limit = <No Value Set: using "-1"> (optionally set this)
16713 Filter Action =
16714 (*) Move
16715 Folder = spam
16717 Set These Keywords = Bogo
16718 </PRE>
16719 <P>
16720 and the following rule is
16721 <PRE>
16722 Nickname = Set Bogo Keyword
16723 Current Folder Type =
16724 (*) Specific
16725 Folder = INBOX
16727 ! Keyword pattern = Bogo
16729 Filter Action =
16730 (*) Just Set Message Status
16732 Set These Keywords = Bogo
16734 Features =
16735 [X] dont-stop-even-if-rule-matches
16736 </PRE>
16737 <P>
16738 If it is possible for you to insert bogofilter in the delivery process instead
16739 of having it called from Alpine you could prevent having to wait
16740 for the bogofilter processing while you read your mail.
16741 You would have bogofilter add a header to the message at the time of delivery
16742 that identified it as spam or nonspam.
16743 With this method, you could avoid using a Categorizer Command while running Alpine,
16744 and just match on the header instead.
16745 You might still want to use the scripts mentioned above to initialize the
16746 database or to re-classify wrongly classified messages.
16748 <P>
16749 Finally, it isn't for the faint-hearted,
16750 but it is also possible to run bogofilter from PC-Alpine.
16751 You can install Cygwin from
16752 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
16753 then compile bogofilter in the cygwin environment, and run it from
16754 within PC-Alpine.
16755 You would end up with a Categorizer command that looked something like
16756 <P>
16757 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
16758 <P>
16759 Note that the ".exe" extension is explicit,
16760 and that the bogofilter.exe executable should be in the same directory
16761 as cygwin1.dll.
16763 <P>
16764 <End of help on this topic>
16765 </BODY>
16766 </HTML>
16767 ======= h_config_role_cat_status =======
16768 <HTML>
16769 <HEAD>
16770 <TITLE>Exit Status Interval Explained</TITLE>
16771 </HEAD>
16772 <BODY>
16773 <H1>Exit Status Interval Explained</H1>
16775 The categorizer command is run and the result is the exit status of
16776 that command.
16777 If that exit status falls in the Exit Status Interval
16778 then it is considered a match, otherwise it is not a match.
16779 Of course for the entire rule to match, it must also be checked against
16780 the other defined parts of the Pattern.
16781 <P>
16782 The Exit Status Interval defaults to the single value 0 (zero).
16783 If you define it, it should be set to something like:
16784 <P>
16785 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
16786 <P>
16787 where "min_exit_value" and "max_exit_value" are integers.
16788 The special values "INF" and "-INF" may be used for large
16789 positive and negative integers.
16790 <P>
16791 Actually, a list of intervals may be used if you wish.
16792 A list would look like
16793 <P>
16794 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
16795 <P>
16796 When there is an Exit Status Interval defined, it is a match if the exit status
16797 of the categorizer command is contained in any of the intervals.
16798 The intervals include both endpoints.
16799 <P>
16800 The default interval is
16801 <P>
16802 <CENTER><SAMP>(0,0)</SAMP></CENTER>
16803 <P>
16804 and it matches only if the command exits with exit status equal to zero.
16806 <P>
16807 Look "<A HREF="h_rule_patterns">here</A>"
16808 for more information on Patterns.
16809 <P>
16810 Look <A HREF="h_edit_nav_cmds">here</A>
16811 to see the available Editing and Navigation commands.
16812 <P>
16813 <End of help on this topic>
16814 </BODY>
16815 </HTML>
16816 ======= h_config_role_cat_limit =======
16817 <HTML>
16818 <HEAD>
16819 <TITLE>Character Limit Explained</TITLE>
16820 </HEAD>
16821 <BODY>
16822 <H1>Character Limit Explained</H1>
16824 Setting this option makes it possible to limit how much of the message
16825 is made available to the categorizer command as input.
16826 The default value (-1) means that the entire message is fed to the
16827 command.
16828 A value of 0 (zero) means that only the headers of the message are
16829 made available.
16830 A positive integer means that the headers plus that many characters from
16831 the body of the message are passed to the categorizer.
16833 <P>
16834 Look "<A HREF="h_rule_patterns">here</A>"
16835 for more information on Patterns.
16836 <P>
16837 Look <A HREF="h_edit_nav_cmds">here</A>
16838 to see the available Editing and Navigation commands.
16839 <P>
16840 <End of help on this topic>
16841 </BODY>
16842 </HTML>
16843 ======= h_config_role_age =======
16844 <HTML>
16845 <HEAD>
16846 <TITLE>Age Interval Explained</TITLE>
16847 </HEAD>
16848 <BODY>
16849 <H1>Age Interval Explained</H1>
16851 The Age Interval, if defined, is part of the Pattern.
16852 If you use this, it should be set to something like:
16853 <P>
16854 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
16855 <P>
16856 where "min_age" and "max_age" are non-negative integers.
16857 The special value "INF" may be used for the max value.
16858 It represents infinity.
16859 <P>
16860 In rare cases it may be useful to use the more general form of the value,
16861 which is a comma-separated list of intervals.
16862 It would look something like:
16863 <P>
16864 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
16865 <P>
16866 When there is an Age Interval defined, it is a match if the age, in days, of
16867 the message is contained in the interval.
16868 The interval includes both endpoints.
16869 If the option is set to a list of intervals then it is a match if the
16870 age of the message is contained in any of the intervals.
16871 <P>
16872 Even though this option is called Age, it isn't actually
16873 the <EM>age</EM> of the message.
16874 Instead, it is how many days ago the message arrived in one of your folders.
16875 If the current time is a little past midnight, then a message that arrived
16876 just before midnight arrived yesterday, even though the message is only
16877 a few minutes old.
16878 By default, the date being used is not the date in the Date
16879 header of the message.
16880 It is the date that the message arrived in one of your folders.
16881 When you Save a message from one folder to another that arrival date
16882 is preserved.
16883 If you would like to use the date in the Date header that is possible.
16884 Turn on the option
16885 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
16886 near the bottom of the rule definition.
16887 <P>
16888 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
16889 The age interval
16890 <P>
16891 <CENTER><SAMP>(2,2)</SAMP></CENTER>
16892 <P>
16893 matches all messages that arrived on the day before yesterday.
16894 The interval
16895 <P>
16896 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
16897 <P>
16898 matches all messages that arrived at least 180 days before today.
16899 The interval
16900 <P>
16901 <CENTER><SAMP>(0,1)</SAMP></CENTER>
16902 <P>
16903 matches all messages that arrived today or yesterday.
16905 <P>
16906 Look "<A HREF="h_rule_patterns">here</A>"
16907 for more information on Patterns.
16908 <P>
16909 Look <A HREF="h_edit_nav_cmds">here</A>
16910 to see the available Editing and Navigation commands.
16911 <P>
16912 <End of help on this topic>
16913 </BODY>
16914 </HTML>
16915 ======= h_config_role_size =======
16916 <HTML>
16917 <HEAD>
16918 <TITLE>Size Interval Explained</TITLE>
16919 </HEAD>
16920 <BODY>
16921 <H1>Size Interval Explained</H1>
16923 The Size Interval, if defined, is part of the Pattern.
16924 If you use this, it should be set to something like:
16925 <P>
16926 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
16927 <P>
16928 where "min_size" and "max_size" are non-negative integers.
16929 The special value "INF" may be used for the max value.
16930 It represents infinity.
16931 <P>
16932 In rare cases it may be useful to use the more general form of the value,
16933 which is a comma-separated list of intervals.
16934 It would look something like:
16935 <P>
16936 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
16937 <P>
16938 When there is a Size Interval defined, it is a match if the size of
16939 the message is contained in the interval.
16940 The interval includes both endpoints.
16941 If the option is set to a list of intervals then it is a match if the
16942 size of the message is contained in any of the intervals.
16943 <P>
16944 The size interval
16945 <P>
16946 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
16947 <P>
16948 matches all messages with sizes greater than or equal to 10000, and less
16949 than or equal to 50000.
16950 The interval
16951 <P>
16952 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
16953 <P>
16954 matches all messages with sizes greater than or equal to 100000.
16956 <P>
16957 Look "<A HREF="h_rule_patterns">here</A>"
16958 for more information on Patterns.
16959 <P>
16960 Look <A HREF="h_edit_nav_cmds">here</A>
16961 to see the available Editing and Navigation commands.
16962 <P>
16963 <End of help on this topic>
16964 </BODY>
16965 </HTML>
16966 ======= h_config_role_scorei =======
16967 <HTML>
16968 <HEAD>
16969 <TITLE>Score Interval Explained</TITLE>
16970 </HEAD>
16971 <BODY>
16972 <H1>Score Interval Explained</H1>
16974 The Score Interval, if defined, is part of the Pattern.
16975 If you use this, it should be set to something like:
16976 <P>
16977 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
16978 <P>
16979 where "min_score" and "max_score" are integers between
16980 -32000 and 32000.
16981 The special values "-INF" and "INF" may be used for
16982 the min and max values.
16983 These represent negative and positive infinity.
16984 <P>
16985 Actually, the value may be a list of intervals rather than just a
16986 single interval if that is useful.
16987 The elements of the list are separated by commas like:
16988 <P>
16989 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
16990 <P>
16991 When there is a Score Interval defined, it is a match if the score for
16992 the message is contained in any of the intervals.
16993 The intervals include both endpoints.
16994 The score for a message is calculated by looking at every scoring rule
16995 defined and adding up the Score Values for the rules that match the message.
16996 Scoring rules are created using the
16997 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
16999 <P>
17000 Look "<A HREF="h_rule_patterns">here</A>"
17001 for more information on Patterns.
17002 <P>
17003 Look <A HREF="h_edit_nav_cmds">here</A>
17004 to see the available Editing and Navigation commands.
17005 <P>
17006 <End of help on this topic>
17007 </BODY>
17008 </HTML>
17009 ======= h_config_role_fldr_type =======
17010 <HTML>
17011 <HEAD>
17012 <TITLE>Current Folder Type Explained</TITLE>
17013 </HEAD>
17014 <BODY>
17015 <H1>Current Folder Type Explained</H1>
17017 The Current Folder Type is part of the role's Pattern.
17018 It refers to the type of the currently open folder, which is the folder
17019 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
17020 In order for a role to be considered a match, the current folder must
17021 be of the type you set here.
17022 The three types "Any", "News", and "Email" are
17023 all what you might think.
17024 <P>
17025 If the Current Folder Type for a role's Pattern is set to "News", for
17026 example, then
17027 that role will only be a match if the current folder is a newsgroup and
17028 the rest of the Pattern matches.
17029 The value "Specific" may be used when you want to limit the match
17030 to a specific folder (not just a specific type of folder), or to a list of
17031 specific folders.
17032 <P>
17033 In order to match a specific folder you Select the "Specific"
17034 button <EM>AND</EM> fill in
17035 the name (or list of names) of
17036 the folder in the "Folder List" field.
17037 If the current folder is any of the folders in the list, that is considered
17038 a match.
17039 The name of each folder in the list may be either "INBOX",
17040 the technical specification
17041 of the folder (like what appears in your configuration file) or, if the
17042 folder is one of your incoming folders, it may be the nickname you've given
17043 the folder.
17044 Here are a couple samples of specific folder names:
17045 <P>
17046 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17047 <P>
17048 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17049 <P>
17050 The easiest way to fill in the "Folder List" field is to use
17051 the "T" command that is available when the "Folder List" line is
17052 highlighted, or to use the "Take" command with the configuration
17053 feature
17054 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
17055 turned on.
17056 Note that you won't be able to edit the "Folder List" line unless the
17057 Current Folder Type is set to "Specific", and any value that
17058 "Folder List" has is ignored unless the type
17059 is set to "Specific".
17060 <P>
17061 When reading a newsgroup, there may be a performance penalty
17062 incurred when collecting the information necessary to check a Pattern.
17063 For this reason, the default Current Folder Type is set to "Email".
17064 <P>
17065 Look "<A HREF="h_rule_patterns">here</A>"
17066 for more information on Patterns.
17067 <P>
17068 Look <A HREF="h_edit_nav_cmds">here</A>
17069 to see the available Editing and Navigation commands.
17070 <P>
17071 <End of help on this topic>
17072 </BODY>
17073 </HTML>
17074 ======= h_config_filt_rule_type =======
17075 <HTML>
17076 <HEAD>
17077 <TITLE>Filter Action Explained</TITLE>
17078 </HEAD>
17079 <BODY>
17080 <H1>Filter Action Explained</H1>
17082 The Filter Action specifies the action to be taken when the Pattern is a
17083 match.
17084 It may be set to "Delete" "Move", or
17085 "Just Set Message Status".
17086 <P>
17087 If it is set to "Delete", then the message that matches the
17088 Pattern will be deleted from the open folder.
17089 <P>
17090 If it is set to "Move", then the name of the folder to which
17091 the matching message should be moved is given in the "Folder List" field on the
17092 next line of the screen.
17093 A list of folders separated by commas may be given, in which case the
17094 message will be copied to all of the folders in the list before it is
17095 deleted.
17096 <P>
17097 If it is set to neither of those two values (it is set to the value
17098 labeled "Just Set Message Status") then the message status
17099 setting will happen
17100 but the message will not be deleted or moved.
17101 <P>
17102 If you are Moving a message you may also set Message Status if you wish.
17103 <P>
17104 The easiest way to fill in the "Folder List" field is to use
17105 the T command that is available when the "Folder List" line is
17106 highlighted.
17107 Note that you won't be able to edit the "Folder List" line unless the
17108 Filter Action is set to "Move", and any value that
17109 "Folder List" has is ignored unless the type
17110 is set to "Move".
17111 <P>
17112 There are a few tokens that may be used in the names in the Folder List.
17113 They are all related to the date on which the filtering is taking place.
17114 The tokens are words surrounded by underscores.
17115 For example, if you want your filter to move messages to a folder named
17116 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
17117 you could specify the folder as
17118 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
17119 which would result in a file named something like
17120 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
17121 or
17122 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
17123 which would result in a file named something like
17124 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
17125 The available tokens are listed
17126 <A HREF="h_index_tokens">here</A>.
17127 <P>
17128 Look "<A HREF="h_rule_patterns">here</A>"
17129 for more information on Patterns.
17130 <P>
17131 Look <A HREF="h_edit_nav_cmds">here</A>
17132 to see the available Editing and Navigation commands.
17133 <P>
17134 <End of help on this topic>
17135 </BODY>
17136 </HTML>
17137 ======= h_config_score_fldr_type =======
17138 <HTML>
17139 <HEAD>
17140 <TITLE>Current Folder Type Explained</TITLE>
17141 </HEAD>
17142 <BODY>
17143 <H1>Current Folder Type Explained</H1>
17145 The Current Folder Type is part of the scoring rule's Pattern.
17146 It refers to the type of the folder that
17147 the message being scored is in.
17148 In order for a rule to be considered a match, the current folder must
17149 be of the type you set here.
17150 The three types "Any", "News", and "Email" are
17151 all what you might think.
17152 <P>
17153 If the Current Folder Type for a Pattern is set to "News", for
17154 example, then
17155 that Pattern will only match if the current folder is a newsgroup and
17156 the rest of the Pattern matches.
17157 The value "Specific" may be used when you want to limit the match
17158 to a specific folder (not just a specific type of folder), or to a list of
17159 specific folders.
17160 <P>
17161 In order to match a specific folder you Select the "Specific"
17162 button <EM>AND</EM> fill in
17163 the name (or list of names) of
17164 the folder in the "Folder List" field.
17165 If the current folder is any of the folders in the list, that is considered
17166 a match.
17167 The name of each folder in the list may be either "INBOX", the technical specification
17168 of the folder (like what appears in your configuration file) or, if the
17169 folder is one of your incoming folders, it may be the nickname you've given
17170 the folder.
17171 Here are a couple samples of specific folder names:
17172 <P>
17173 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17174 <P>
17175 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17176 <P>
17177 The easiest way to fill in the "Folder List" field is to use
17178 the T command that is available when the "Folder List" line is
17179 highlighted.
17180 Note that you won't be able to edit the "Folder List" line unless the
17181 Current Folder Type is set to "Specific", and any value that
17182 "Folder List" has is ignored unless the type
17183 is set to "Specific".
17184 <P>
17185 When reading a newsgroup, there may be a performance penalty
17186 incurred when collecting the information necessary to check a Pattern.
17187 For this reason, the default Current Folder Type is set to "Email".
17188 For example, if you have Index Line Coloring rules that have Score Intervals
17189 defined then the scores for all the visible messages will need to be calculated.
17190 If some of your Scoring rules have
17191 a Current Folder Type of
17192 "Any" or "News" this may cause the MESSAGE INDEX
17193 screen to draw more slowly when in a newsgroup.
17194 <P>
17195 Look "<A HREF="h_rule_patterns">here</A>"
17196 for more information on Patterns.
17197 <P>
17198 Look <A HREF="h_edit_nav_cmds">here</A>
17199 to see the available Editing and Navigation commands.
17200 <P>
17201 <End of help on this topic>
17202 </BODY>
17203 </HTML>
17204 ======= h_config_other_fldr_type =======
17205 <HTML>
17206 <HEAD>
17207 <TITLE>Current Folder Type Explained</TITLE>
17208 </HEAD>
17209 <BODY>
17210 <H1>Current Folder Type Explained</H1>
17212 The Current Folder Type is part of the rule's Pattern.
17213 It refers to the type of the folder being viewed.
17214 In order for a rule to be considered a match, the current folder must
17215 be of the type you set here.
17216 The three types "Any", "News", and "Email" are
17217 all what you might think.
17218 <P>
17219 If the Current Folder Type for a Pattern is set to "News", for
17220 example, then
17221 that Pattern will only match if the current folder is a newsgroup.
17222 The value "Specific" may be used when you want to limit the match
17223 to a specific folder (not just a specific type of folder), or to a list of
17224 specific folders.
17225 <P>
17226 In order to match a specific folder you Select the "Specific"
17227 button <EM>AND</EM> fill in
17228 the name (or list of names) of
17229 the folder in the "Folder List" field.
17230 If the current folder is any of the folders in the list, that is considered
17231 a match.
17232 The name of each folder in the list may be either "INBOX", the technical specification
17233 of the folder (like what appears in your configuration file) or, if the
17234 folder is one of your incoming folders, it may be the nickname you've given
17235 the folder.
17236 Here are a couple samples of specific folder names:
17237 <P>
17238 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17239 <P>
17240 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17241 <P>
17242 The easiest way to fill in the "Folder List" field is to use
17243 the T command that is available when the "Folder List" line is
17244 highlighted.
17245 Note that you won't be able to edit the "Folder List" line unless the
17246 Current Folder Type is set to "Specific", and any value that
17247 "Folder List" has is ignored unless the type
17248 is set to "Specific".
17249 <P>
17250 Look "<A HREF="h_rule_patterns">here</A>"
17251 for more information on Patterns.
17252 <P>
17253 Look <A HREF="h_edit_nav_cmds">here</A>
17254 to see the available Editing and Navigation commands.
17255 <P>
17256 <End of help on this topic>
17257 </BODY>
17258 </HTML>
17259 ======= h_config_incol_fldr_type =======
17260 <HTML>
17261 <HEAD>
17262 <TITLE>Current Folder Type Explained</TITLE>
17263 </HEAD>
17264 <BODY>
17265 <H1>Current Folder Type Explained</H1>
17267 The Current Folder Type is part of the Line Coloring rule's Pattern.
17268 It refers to the type of the folder for which the MESSAGE INDEX is
17269 being viewed.
17270 In order for a rule to be considered a match, the current folder must
17271 be of the type you set here.
17272 The three types "Any", "News", and "Email" are
17273 all what you might think.
17274 <P>
17275 If the Current Folder Type for a Pattern is set to "News", for
17276 example, then
17277 that Pattern will only match if the current folder is a newsgroup and
17278 the rest of the Pattern matches.
17279 The value "Specific" may be used when you want to limit the match
17280 to a specific folder (not just a specific type of folder), or to a list of
17281 specific folders.
17282 <P>
17283 In order to match a specific folder you Select the "Specific"
17284 button <EM>AND</EM> fill in
17285 the name (or list of names) of
17286 the folder in the "Folder List" field.
17287 If the current folder is any of the folders in the list, that is considered
17288 a match.
17289 The name of each folder in the list may be either "INBOX", the technical specification
17290 of the folder (like what appears in your configuration file) or, if the
17291 folder is one of your incoming folders, it may be the nickname you've given
17292 the folder.
17293 Here are a couple samples of specific folder names:
17294 <P>
17295 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17296 <P>
17297 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17298 <P>
17299 The easiest way to fill in the "Folder List" field is to use
17300 the T command that is available when the "Folder List" line is
17301 highlighted.
17302 Note that you won't be able to edit the "Folder List" line unless the
17303 Current Folder Type is set to "Specific", and any value that
17304 "Folder List" has is ignored unless the type
17305 is set to "Specific".
17306 <P>
17307 When reading a newsgroup, there may be a performance penalty
17308 incurred when collecting the information necessary to check a Pattern.
17309 For this reason, the default Current Folder Type is set to "Email".
17310 For example, a rule with a non-Normal Index Line Color
17311 and a Current Folder Type of
17312 "Any" or "News" may cause the MESSAGE INDEX
17313 screen to draw more slowly when in a newsgroup.
17314 <P>
17315 Look "<A HREF="h_rule_patterns">here</A>"
17316 for more information on Patterns.
17317 <P>
17318 Look <A HREF="h_edit_nav_cmds">here</A>
17319 to see the available Editing and Navigation commands.
17320 <P>
17321 <End of help on this topic>
17322 </BODY>
17323 </HTML>
17324 ======= h_config_filt_fldr_type =======
17325 <HTML>
17326 <HEAD>
17327 <TITLE>Current Folder Type Explained</TITLE>
17328 </HEAD>
17329 <BODY>
17330 <H1>Current Folder Type Explained</H1>
17332 The Current Folder Type is part of the Filtering rule's Pattern.
17333 It refers to the type of the folder for which the filtering is being done.
17334 In order for a rule to be considered a match, the current folder must
17335 be of the type you set here.
17336 The three types "Any", "News", and "Email" are
17337 all what you might think.
17338 <P>
17339 If the Current Folder Type for a Pattern is set to "News", for
17340 example, then
17341 that Pattern will only match if the current folder is a newsgroup and
17342 the rest of the Pattern matches.
17343 The value "Specific" may be used when you want to limit the match
17344 to a specific folder (not just a specific type of folder), or to a list of
17345 specific folders.
17346 <P>
17347 In order to match a specific folder you Select the "Specific"
17348 button <EM>AND</EM> fill in
17349 the name (or list of names) of
17350 the folder in the "Folder List" field.
17351 If the current folder is any of the folders in the list, that is considered
17352 a match.
17353 The name of each folder in the list may be either "INBOX", the technical specification
17354 of the folder (like what appears in your configuration file) or, if the
17355 folder is one of your incoming folders, it may be the nickname you've given
17356 the folder.
17357 Here are a couple samples of specific folder names:
17358 <P>
17359 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17360 <P>
17361 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17362 <P>
17363 The easiest way to fill in the "Folder List" field is to use
17364 the T command that is available when the "Folder List" line is
17365 highlighted.
17366 Note that you won't be able to edit the "Folder List" line unless the
17367 Current Folder Type is set to "Specific", and any value that
17368 "Folder List" has is ignored unless the type
17369 is set to "Specific".
17370 <P>
17371 When reading a newsgroup, there may be a performance penalty
17372 incurred when collecting the information necessary to check a Pattern.
17373 For this reason, the default Current Folder Type is set to "Email".
17374 For example, a rule with a Current Folder Type of either
17375 "Any" or "News" may cause the filtering to happen
17376 more slowly when opening a newsgroup.
17377 <P>
17378 Look "<A HREF="h_rule_patterns">here</A>"
17379 for more information on Patterns.
17380 <P>
17381 Look <A HREF="h_edit_nav_cmds">here</A>
17382 to see the available Editing and Navigation commands.
17383 <P>
17384 <End of help on this topic>
17385 </BODY>
17386 </HTML>
17387 ======= h_config_role_stat_imp =======
17388 <HTML>
17389 <HEAD>
17390 <TITLE>Message Important Status Explained</TITLE>
17391 </HEAD>
17392 <BODY>
17393 <H1>Message Important Status Explained</H1>
17395 This part of the Pattern may have one of three possible values.
17396 The default value is "Don't care", which matches any message.
17397 The other two values are "Yes", which means the message must be
17398 flagged "Important" in order to be a match; or "No", which
17399 means the message must <EM>not</EM> be flagged "Important" in order
17400 to be a match.
17401 <P>
17402 Look "<A HREF="h_rule_patterns">here</A>"
17403 for more information on Patterns.
17404 <P>
17405 Look <A HREF="h_edit_nav_cmds">here</A>
17406 to see the available Editing and Navigation commands.
17407 <P>
17408 <End of help on this topic>
17409 </BODY>
17410 </HTML>
17411 ======= h_config_role_stat_new =======
17412 <HTML>
17413 <HEAD>
17414 <TITLE>Message New Status Explained</TITLE>
17415 </HEAD>
17416 <BODY>
17417 <H1>Message New Status Explained</H1>
17419 This part of the Pattern may have one of three possible values.
17420 The default value is "Don't care", which matches any message.
17421 The other two values are "Yes", which means the message must be
17422 "New" in order to be a match; or "No", which
17423 means the message must <EM>not</EM> be "New" in order
17424 to be a match.
17425 "New" is the same as <EM>Unseen</EM> and not "New" is the
17426 same as <EM>Seen</EM>.
17427 <P>
17428 The nomenclature for New and Recent is a bit confusing:
17429 <P>
17430 New means that the message is Unseen.
17431 It could have been in your mailbox for a long time but if you haven't looked
17432 at it, it is still considered New.
17433 That matches the default Alpine index display that shows an N for such a
17434 message.
17435 <P>
17436 Recent means that the message was added to this folder since the last time
17437 you opened the folder.
17438 Alpine also shows an N by default for these types of messages.
17439 If you were to run two copies of Alpine that opened a folder one right after
17440 the other, a message would only show up as Recent in (at most) the first
17441 Alpine session.
17442 <P>
17443 Look "<A HREF="h_rule_patterns">here</A>"
17444 for more information on Patterns.
17445 <P>
17446 Look <A HREF="h_edit_nav_cmds">here</A>
17447 to see the available Editing and Navigation commands.
17448 <P>
17449 <End of help on this topic>
17450 </BODY>
17451 </HTML>
17452 ======= h_config_role_stat_recent =======
17453 <HTML>
17454 <HEAD>
17455 <TITLE>Message Recent Status Explained</TITLE>
17456 </HEAD>
17457 <BODY>
17458 <H1>Message Recent Status Explained</H1>
17460 This part of the Pattern may have one of three possible values.
17461 The default value is "Don't care", which matches any message.
17462 The other two values are "Yes", which means the message must be
17463 "Recent" in order to be a match; or "No", which
17464 means the message must <EM>not</EM> be "Recent" in order
17465 to be a match.
17466 "Recent" means that the message was added to the folder since
17467 the last time the folder was opened.
17468 If more than one mail client has the folder opened, the message will
17469 appear to be "Recent" to only one of the clients.
17470 <P>
17471 The nomenclature for New and Recent is a bit confusing:
17472 <P>
17473 New means that the message is Unseen.
17474 It could have been in your mailbox for a long time but if you haven't looked
17475 at it, it is still considered New.
17476 That matches the default Alpine index display that shows an N for such a
17477 message.
17478 <P>
17479 Recent means that the message was added to this folder since the last time
17480 you opened the folder.
17481 Alpine also shows an N by default for these types of messages.
17482 If you were to run two copies of Alpine that opened a folder one right after
17483 the other, a message would only show up as Recent in (at most) the first
17484 Alpine session.
17485 <P>
17486 Look "<A HREF="h_rule_patterns">here</A>"
17487 for more information on Patterns.
17488 <P>
17489 Look <A HREF="h_edit_nav_cmds">here</A>
17490 to see the available Editing and Navigation commands.
17491 <P>
17492 <End of help on this topic>
17493 </BODY>
17494 </HTML>
17495 ======= h_config_role_stat_del =======
17496 <HTML>
17497 <HEAD>
17498 <TITLE>Message Deleted Status Explained</TITLE>
17499 </HEAD>
17500 <BODY>
17501 <H1>Message Deleted Status Explained</H1>
17503 This part of the Pattern may have one of three possible values.
17504 The default value is "Don't care", which matches any message.
17505 The other two values are "Yes", which means the message must be
17506 marked "Deleted" in order to be a match; or "No", which
17507 means the message must <EM>not</EM> be marked "Deleted" in order
17508 to be a match.
17509 <P>
17510 If you are thinking of using this part of the Pattern as a way to prevent
17511 messages from being filtered more than once in a Filter Pattern,
17512 take a look at the Filter Option
17513 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17514 instead.
17515 It should work better than using this field since it will hide the filtered
17516 messages even if they are already Deleted.
17517 That option is at the bottom of the Filter configuration screen.
17518 <P>
17519 Look "<A HREF="h_rule_patterns">here</A>"
17520 for more information on Patterns.
17521 <P>
17522 Look <A HREF="h_edit_nav_cmds">here</A>
17523 to see the available Editing and Navigation commands.
17524 <P>
17525 <End of help on this topic>
17526 </BODY>
17527 </HTML>
17528 ======= h_config_role_stat_ans =======
17529 <HTML>
17530 <HEAD>
17531 <TITLE>Message Answered Status Explained</TITLE>
17532 </HEAD>
17533 <BODY>
17534 <H1>Message Answered Status Explained</H1>
17536 This part of the Pattern may have one of three possible values.
17537 The default value is "Don't care", which matches any message.
17538 The other two values are "Yes", which means the message must be
17539 marked "Answered" in order to be a match; or "No", which
17540 means the message must <EM>not</EM> be marked "Answered" in order
17541 to be a match.
17542 <P>
17543 Look "<A HREF="h_rule_patterns">here</A>"
17544 for more information on Patterns.
17545 <P>
17546 Look <A HREF="h_edit_nav_cmds">here</A>
17547 to see the available Editing and Navigation commands.
17548 <P>
17549 <End of help on this topic>
17550 </BODY>
17551 </HTML>
17552 ======= h_config_role_abookfrom =======
17553 <HTML>
17554 <HEAD>
17555 <TITLE>Address in Address Book Explained</TITLE>
17556 </HEAD>
17557 <BODY>
17558 <H1>Address in Address Book Explained</H1>
17560 This option gives you a way to match messages that contain an address
17561 that is in one of your address books.
17562 Only the simple entries in your address books are searched.
17563 Address book distribution lists are ignored!
17564 <P>
17565 This part of the Pattern may have one of five possible values.
17566 The default value is "Don't care", which matches any message.
17567 The value "Yes, in any address book" means at least one of the addresses
17568 from the message must be in at least one of your
17569 address books in order to be a match.
17570 The value "No, not in any address book"
17571 means none of the addresses may
17572 be in any of your address books in order to be a match.
17573 <P>
17574 The values "Yes, in specific address books" and
17575 "No, not in any of specific address books" are similar but instead
17576 of depending on all address books you are allowed to give a list of address
17577 books to look in.
17578 Usually this would be a single address book but it may be a
17579 list of address books as well.
17580 For each of these "specific" address book options you Select which
17581 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17582 name (or list of names) of the address book in the
17583 "Abook List" field.
17584 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17585 The easiest way to fill in the Abook List field it to use
17586 the "T" command that is available when the "Abook List"
17587 line is highlighted.
17588 Note that you won't be able to edit the "Abook List" line unless the
17589 option is set to one of the two "Specific", values.
17590 <P>
17591 The addresses from the message that are checked for are determined by the
17592 setting you have for "Types of addresses to check for in address book".
17593 If you set this to "From" the From address from the message will
17594 be looked up in the address book.
17595 If you set it to "To" instead then the To addresses will be used.
17596 If any of the To addresses are in the address book then it is considered
17597 a match for "Yes" or not a match for "No".
17598 You could set it to both From and To, in which case all of the From and To
17599 addresses are used.
17600 The "Reply-To" and "Sender" cases are a little unusual.
17601 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17602 exists or the From address if there is no Reply-To address.
17603 Same for the Sender address.
17604 <P>
17605 Look "<A HREF="h_rule_patterns">here</A>"
17606 for more information on Patterns.
17607 <P>
17608 Look <A HREF="h_edit_nav_cmds">here</A>
17609 to see the available Editing and Navigation commands.
17610 <P>
17611 <End of help on this topic>
17612 </BODY>
17613 </HTML>
17614 ======= h_config_inabook_from =======
17615 <HTML>
17616 <HEAD>
17617 <TITLE>From</TITLE>
17618 </HEAD>
17619 <BODY>
17620 <H1>From</H1>
17622 Setting the From line will cause the address from the From header line
17623 of the message to be checked for in the address book.
17624 <P>
17625 <End of help on this topic>
17626 </BODY>
17627 </HTML>
17628 ======= h_config_inabook_replyto =======
17629 <HTML>
17630 <HEAD>
17631 <TITLE>Reply-To</TITLE>
17632 </HEAD>
17633 <BODY>
17634 <H1>Reply-To</H1>
17636 Setting the Reply-To line will cause the address from the Reply-To header line
17637 of the message to be checked for in the address book.
17638 However, if there is no Reply-To header line in the message the From header
17639 line will be used instead.
17640 We understand this is dumb but we don't have an easy way around it.
17641 <P>
17642 <End of help on this topic>
17643 </BODY>
17644 </HTML>
17645 ======= h_config_inabook_sender =======
17646 <HTML>
17647 <HEAD>
17648 <TITLE>Sender</TITLE>
17649 </HEAD>
17650 <BODY>
17651 <H1>Sender</H1>
17653 Setting the Sender line will cause the address from the Sender header line
17654 of the message to be checked for in the address book.
17655 However, if there is no Sender header line in the message the From header
17656 line will be used instead.
17657 We understand this is dumb but we don't have an easy way around it.
17658 <P>
17659 <End of help on this topic>
17660 </BODY>
17661 </HTML>
17662 ======= h_config_inabook_to =======
17663 <HTML>
17664 <HEAD>
17665 <TITLE>To</TITLE>
17666 </HEAD>
17667 <BODY>
17668 <H1>To</H1>
17670 Setting the To line will cause the address from the To header line
17671 of the message to be checked for in the address book.
17672 <P>
17673 <End of help on this topic>
17674 </BODY>
17675 </HTML>
17676 ======= h_config_inabook_cc =======
17677 <HTML>
17678 <HEAD>
17679 <TITLE>CC</TITLE>
17680 </HEAD>
17681 <BODY>
17682 <H1>CC</H1>
17684 Setting the CC line will cause the address from the CC header line
17685 of the message to be checked for in the address book.
17686 <P>
17687 <End of help on this topic>
17688 </BODY>
17689 </HTML>
17690 ======= h_config_role_stat_8bitsubj =======
17691 <HTML>
17692 <HEAD>
17693 <TITLE>Raw 8-bit in Subject Explained</TITLE>
17694 </HEAD>
17695 <BODY>
17696 <H1>Raw 8-bit in Subject Explained</H1>
17698 It seems that lots of unwanted email contains unencoded 8-bit characters
17699 in the Subject.
17700 Normally, characters with the 8th bit set are not allowed in the Subject
17701 header unless they are MIME-encoded.
17702 This option gives you a way to match messages that have Subjects that
17703 contain unencoded 8-bit characters.
17704 <P>
17705 This part of the Pattern may have one of three possible values.
17706 The default value is "Don't care", which matches any message.
17707 The other two values are "Yes", which means the Subject of
17708 the message must contain unencoded 8-bit characters (characters with the
17709 most significant bit set)
17710 in order to be a match; or "No", which
17711 means the Subject must <EM>not</EM>
17712 contain unencoded 8-bit characters in order to be a match.
17713 <P>
17714 Look "<A HREF="h_rule_patterns">here</A>"
17715 for more information on Patterns.
17716 <P>
17717 Look <A HREF="h_edit_nav_cmds">here</A>
17718 to see the available Editing and Navigation commands.
17719 <P>
17720 <End of help on this topic>
17721 </BODY>
17722 </HTML>
17723 ======= h_config_role_bom =======
17724 <HTML>
17725 <HEAD>
17726 <TITLE>Beginning of Month</TITLE>
17727 </HEAD>
17728 <BODY>
17729 <H1>Beginning of Month</H1>
17731 This option gives you a limited ability to take different actions depending on whether
17732 this is the first time Alpine has been run this month or not.
17733 Though it would be nice to have such an option available, this is not the
17734 same as whether or not this is the first time a paricular folder has been
17735 opened this month.
17736 If you want some action (probably Filtering) to take place in a folder each
17737 month, then you will need to be sure that the folder is opened during the
17738 first Alpine session of the month in order for this option to be helpful.
17739 <P>
17740 This part of the Pattern may have one of three possible values.
17741 The default value is "Don't care", which matches any message.
17742 The other two values are "Yes", which means this is the first
17743 time Alpine has been run this month;
17744 or "No", which
17745 means this is not the first time Alpine has been run this month.
17746 <P>
17747 Look "<A HREF="h_rule_patterns">here</A>"
17748 for more information on Patterns.
17749 <P>
17750 Here are some technical details.
17751 The way that Alpine decides if it is the beginning of the month or not is
17752 to compare today's date with the date stored in the
17753 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17754 variable in the config file.
17755 If the month of today's date is later than the month stored in the variable,
17756 then this is considered to be the first time you have run Alpine this month, and
17757 that turns the Beginning of the Month option on.
17758 <P>
17759 Look <A HREF="h_edit_nav_cmds">here</A>
17760 to see the available Editing and Navigation commands.
17761 <P>
17762 <End of help on this topic>
17763 </BODY>
17764 </HTML>
17765 ======= h_config_role_boy =======
17766 <HTML>
17767 <HEAD>
17768 <TITLE>Beginning of Year</TITLE>
17769 </HEAD>
17770 <BODY>
17771 <H1>Beginning of Year</H1>
17773 This option gives you a limited ability to take different actions depending on whether
17774 this is the first time Alpine has been run this year or not.
17775 Though it would be nice to have such an option available, this is not the
17776 same as whether or not this is the first time a paricular folder has been
17777 opened this year.
17778 If you want some action (probably Filtering) to take place in a folder each
17779 year, then you will need to be sure that the folder is opened during the
17780 first Alpine session of the year in order for this option to be helpful.
17781 <P>
17782 This part of the Pattern may have one of three possible values.
17783 The default value is "Don't care", which matches any message.
17784 The other two values are "Yes", which means this is the first
17785 time Alpine has been run this year;
17786 or "No", which
17787 means this is not the first time Alpine has been run this year.
17788 <P>
17789 Look "<A HREF="h_rule_patterns">here</A>"
17790 for more information on Patterns.
17791 <P>
17792 Here are some technical details.
17793 The way that Alpine decides if it is the beginning of the year or not is
17794 to compare today's date with the date stored in the
17795 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
17796 variable in the config file.
17797 If the year of today's date is later than the year stored in the variable,
17798 then this is considered to be the first time you have run Alpine this year, and
17799 that turns the Beginning of the Year option on.
17800 <P>
17801 Look <A HREF="h_edit_nav_cmds">here</A>
17802 to see the available Editing and Navigation commands.
17803 <P>
17804 <End of help on this topic>
17805 </BODY>
17806 </HTML>
17807 ======= h_config_role_inick =======
17808 <HTML>
17809 <HEAD>
17810 <TITLE>Initialize Values From Role Explained</TITLE>
17811 </HEAD>
17812 <BODY>
17813 <H1>Initialize Values From Role Explained</H1>
17815 This is a power user feature.
17816 You will usually want to leave this field empty.
17817 The value of this field is the nickname of another one of your roles.
17818 The Action values from that other role
17819 are used as the initial values of the Action items for this role.
17820 If you put something in any of the action fields for this role, that will
17821 override whatever was in the corresponding field of the initializer role.
17822 <P>
17823 You might use this field if the "Action" part of one of your roles
17824 is something you want to use in more than one role.
17825 Instead of filling in those action values again for each role, you
17826 may give the nickname of the role where the values are filled in.
17827 It's just a shortcut way to define Role Actions.
17828 <P>
17829 Here's an example to help explain how this works.
17830 Suppose you have a role with nickname "role1" and role1 has
17831 (among other things)
17832 <P>
17833 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
17834 <P>
17835 set.
17836 If in "role2" you set "Initialize settings using role" to
17837 "role1", then role2 will inherit the Set Reply-To value
17838 from role1 by default (and any of the other inheritable action values
17839 that are set).
17840 So if role2 had
17841 <P>
17842 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
17843 <P>
17844 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
17845 However, if role2 had
17846 <P>
17847 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
17848 <P>
17849 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
17850 <P>
17851 If you wish,
17852 you may choose a nickname from your list of roles by using the
17853 "T" command.
17854 If the role you are using to initialize also has a role it initializes from,
17855 then that initialization happens first.
17856 That is, inheritance works as expected with the grandparent and
17857 great-grandparent (and so on) roles having the expected effect.
17858 <P>
17859 Look <A HREF="h_edit_nav_cmds">here</A>
17860 to see the available Editing and Navigation commands.
17861 <P>
17862 <End of help on this topic>
17863 </BODY>
17864 </HTML>
17865 ======= h_config_role_setfrom =======
17866 <HTML>
17867 <HEAD>
17868 <TITLE>Set From Explained</TITLE>
17869 </HEAD>
17870 <BODY>
17871 <H1>Set From Explained</H1>
17873 This describes part of the action to be taken if the Pattern for this
17874 role is a match.
17875 This field consists of a single address that will be used as the From
17876 address on the message you are sending.
17877 This should be a fully-qualified address like
17878 <P>
17879 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17880 <P>
17881 or just
17882 <P>
17883 <CENTER><SAMP>user@domain</SAMP></CENTER>
17884 <P>
17885 If you wish,
17886 you may choose an address from your address book with the
17887 "T" command.
17888 <P>
17889 If this is left blank, then your normal From address will be used.
17890 <P>
17891 You may also find it useful to add the changed From address to the
17892 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
17893 configuration option.
17894 <P>
17895 Look <A HREF="h_edit_nav_cmds">here</A>
17896 to see the available Editing and Navigation commands.
17897 <P>
17898 <End of help on this topic>
17899 </BODY>
17900 </HTML>
17901 ======= h_config_role_setreplyto =======
17902 <HTML>
17903 <HEAD>
17904 <TITLE>Set Reply-To Explained</TITLE>
17905 </HEAD>
17906 <BODY>
17907 <H1>Set Reply-To Explained</H1>
17909 This describes part of the action to be taken if the Pattern for this
17910 role is a match.
17911 This field consists of a single address that will be used as the Reply-To
17912 address on the message you are sending.
17913 This may be a fully-qualified address like
17914 <P>
17915 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
17916 <P>
17917 or just
17918 <P>
17919 <CENTER><SAMP>user@domain</SAMP></CENTER>
17920 <P>
17921 If you wish,
17922 you may choose an address from your address book with the
17923 "T" command.
17924 <P>
17925 If this is left blank, then there won't be a Reply-To address unless
17926 you have configured one specially with the
17927 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
17928 configuration option.
17929 <P>
17930 Look <A HREF="h_edit_nav_cmds">here</A>
17931 to see the available Editing and Navigation commands.
17932 <P>
17933 <End of help on this topic>
17934 </BODY>
17935 </HTML>
17936 ======= h_config_role_setfcc =======
17937 <HTML>
17938 <HEAD>
17939 <TITLE>Set Fcc Explained</TITLE>
17940 </HEAD>
17941 <BODY>
17942 <H1>Set Fcc Explained</H1>
17944 This describes part of the action to be taken if the Pattern for this
17945 role is a match.
17946 This field consists of a single folder name that will be used in
17947 the Fcc field of the message you are sending.
17948 You may put anything here that you would normally type into the Fcc
17949 field from the composer.
17950 <P>
17951 In addition, an fcc of "" (two double quotation marks) means
17952 no Fcc.
17953 <P>
17954 A blank field here means that Alpine will use its normal rules for deciding
17955 the default value of the Fcc field.
17956 For many roles, perhaps most, it may make more sense for you to use the
17957 other Alpine facilities for setting the Fcc.
17958 In particular, if you want the Fcc to depend on who you are sending the
17959 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
17960 is probably more useful.
17961 In that case, you would want to leave the Fcc field here blank.
17962 However, if you have a role that depends on who the message you are replying
17963 to was From, or what address that message was sent to;
17964 then it might make sense to set the Fcc for that role here.
17965 <P>
17966 If you wish,
17967 you may choose a folder from your folder collections by using the
17968 "T" command.
17969 <P>
17970 Look <A HREF="h_edit_nav_cmds">here</A>
17971 to see the available Editing and Navigation commands.
17972 <P>
17973 <End of help on this topic>
17974 </BODY>
17975 </HTML>
17976 ======= h_config_role_usesmtp =======
17977 <HTML>
17978 <HEAD>
17979 <TITLE>Use SMTP Server Explained</TITLE>
17980 </HEAD>
17981 <BODY>
17982 <H1>Use SMTP Server Explained</H1>
17984 This describes part of the action to be taken if the Pattern for this
17985 role is a match.
17986 If this field has a value, then it will be used as the SMTP server
17987 to send mail when this role is being used (unless the SMTP server variable
17988 is set in the system-wide fixed configuration file).
17989 It has the same semantics as the
17990 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
17991 variable in the Setup/Config screen.
17992 <P>
17993 If you are using this to post from home when you are at home and from
17994 work when you are at work you need to be careful about postponing messages.
17995 When you postpone a composition that was using a role with this variable
17996 set, the SMTP server list will be saved
17997 with the postponed composition.
17998 It cannot be changed later.
17999 Because of this, you may want to make this a list of SMTP servers
18000 with the preferred server at the front of the list and alternate servers
18001 later in the list.
18002 In your "Home" role you would put the home SMTP server first and
18003 the work SMTP server last.
18004 In your "Work" role you would put the work SMTP server first and
18005 the home SMTP server last.
18006 Then if you start a composition as "Work", postpone
18007 it, and then later resume it from home the work SMTP server will fail but
18008 the home SMTP server later in the list will succeed.
18009 <P>
18010 You may be able to simplify things by making the regular
18011 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
18012 variable in the Setup/Config screen a list instead of using roles
18013 to set the SMTP server.
18015 <P>
18016 Look <A HREF="h_edit_nav_cmds">here</A>
18017 to see the available Editing and Navigation commands.
18018 <P>
18019 <End of help on this topic>
18020 </BODY>
18021 </HTML>
18022 ======= h_config_role_usenntp =======
18023 <HTML>
18024 <HEAD>
18025 <TITLE>Use NNTP Server Explained</TITLE>
18026 </HEAD>
18027 <BODY>
18028 <H1>Use NNTP Server Explained</H1>
18030 This describes part of the action to be taken if the Pattern for this
18031 role is a match.
18032 If this field has a value, then it will be used as the NNTP server
18033 to post to newsgroups when this role is being used (unless the NNTP server
18034 variable
18035 is set in the system-wide fixed configuration file).
18036 It has the same semantics as the
18037 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18038 variable in the Setup/Config screen.
18039 <P>
18040 This role setting can facilitate posting to the right nntp server for someone
18041 who reads news from various news sources. The feature
18042 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
18043 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
18044 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
18045 nntp servers for roles may be more desirable for some people.
18046 <P>
18047 If you are using this to post from home when you are at home and from
18048 work when you are at work you need to be careful about postponing messages.
18049 When you postpone a composition that was using a role with this variable
18050 set, the NNTP server list will be saved
18051 with the postponed composition.
18052 It cannot be changed later.
18053 Because of this, you may want to make this a list of NNTP servers
18054 with the preferred server at the front of the list and alternate servers
18055 later in the list.
18056 In your "Home" role you would put the home NNTP server first and
18057 the work NNTP server last.
18058 In your "Work" role you would put the work NNTP server first and
18059 the home NNTP server last.
18060 Then if you start a composition as "Work", postpone
18061 it, and then later resume it from home the work NNTP server will fail but
18062 the home NNTP server later in the list will succeed.
18063 <P>
18064 You may be able to simplify things by making the regular
18065 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18066 variable in the Setup/Config screen a list instead of using roles
18067 to set the NNTP server.
18069 <P>
18070 Look <A HREF="h_edit_nav_cmds">here</A>
18071 to see the available Editing and Navigation commands.
18072 <P>
18073 <End of help on this topic>
18074 </BODY>
18075 </HTML>
18076 ======= h_config_role_setotherhdr =======
18077 <HTML>
18078 <HEAD>
18079 <TITLE>Set Other Headers Explained</TITLE>
18080 </HEAD>
18081 <BODY>
18082 <H1>Set Other Headers Explained</H1>
18084 This describes part of the action to be taken if the Pattern for this
18085 role is a match.
18086 This field gives you a way to set values for headers besides
18087 "From" and "Reply-To".
18088 If you want to set either of those, use the specific
18089 "Set From" and "Set Reply-To" settings above.
18090 <P>
18091 This field is similar to the
18092 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
18093 Each header you specify here must include the header tag
18094 ("To:", "Approved:", etc.)
18095 and may optionally include a value for that header.
18096 In order to see these headers when you compose using this role you
18097 must use the rich header
18098 <!--chtml if pinemode="function_key"-->(F5)
18099 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
18100 Here's an example that shows how you might set the To address.
18101 <P>
18102 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
18103 <P>
18104 Headers set in this way are different from headers set with the
18105 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
18106 will replace any value that already exists.
18107 For example, if you are Replying to a message there will already be at
18108 least one address in the To header (the address you are Replying to).
18109 However, if you Reply using a role that sets the To header, that role's
18110 To header value will be used instead.
18111 <P>
18112 Limitation: Because commas are used to separate the list of
18113 Other Headers, it is not possible to have the value of a
18114 header contain a comma;
18115 nor is there currently an "escape" mechanism provided
18116 to make this work.
18117 <P>
18118 Look <A HREF="h_edit_nav_cmds">here</A>
18119 to see the available Editing and Navigation commands.
18120 <P>
18121 <End of help on this topic>
18122 </BODY>
18123 </HTML>
18124 ======= h_config_role_setlitsig =======
18125 <HTML>
18126 <HEAD>
18127 <TITLE>Set Literal Signature Explained</TITLE>
18128 </HEAD>
18129 <BODY>
18130 <H1>Set Literal Signature Explained</H1>
18132 This describes part of the action to be taken if the Pattern for this
18133 role is a match.
18134 This field contains the actual text for your signature, as opposed to
18135 the name of a file containing your signature.
18136 If this is defined it takes precedence over any value set in the
18137 "Set Signature" field.
18138 <P>
18139 This is simply a different way to store the signature.
18140 The signature is stored inside your Alpine configuration file instead of in
18141 a separate file.
18142 Tokens work the same way they do with
18143 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
18144 help text there for more information.
18145 <P>
18147 The two character sequence \n (backslash followed by
18148 the character n) will be used to signify a line-break in your signature.
18149 You don't have to enter the \n, but it will be visible in the
18150 CHANGE THIS ROLE RULE window after you are done editing the signature.
18151 <P>
18152 Look <A HREF="h_edit_nav_cmds">here</A>
18153 to see the available Editing and Navigation commands.
18154 <P>
18155 <End of help on this topic>
18156 </BODY>
18157 </HTML>
18158 ======= h_config_role_setsig =======
18159 <HTML>
18160 <HEAD>
18161 <TITLE>Set Signature Explained</TITLE>
18162 </HEAD>
18163 <BODY>
18164 <H1>Set Signature Explained</H1>
18166 This describes part of the action to be taken if the Pattern for this
18167 role is a match.
18168 <P>
18169 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
18170 option from Setup/Config
18171 or the "Set LiteralSig" option for this role are defined,
18172 then this option will be ignored.
18173 You can tell that that is the case because the value of this
18174 option will show up as
18175 <P>
18176 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
18177 <P>
18178 You may either use all Literal Signatures (signatures stored in your
18179 configuration file) throughout Alpine, or all signature files.
18180 You can't mix the two.
18181 <P>
18182 This field consists of a filename that will be used as the signature
18183 file when using this role.
18184 <P>
18185 If the filename is followed by a vertical bar (|) then instead
18186 of reading the contents of the file the file is assumed to be a
18187 program that will produce the text to be used on its standard output.
18188 The program can't have any arguments and doesn't receive any input from Alpine,
18189 but the rest of the processing works as if the contents came from a file.
18190 <P>
18191 Instead of storing the data in a local file, the
18192 signature data may be stored remotely in an IMAP folder.
18193 In order to do this,
18194 you must use a remote name for the signature.
18195 A remote signature name might look like:
18196 <P>
18197 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
18198 <P>
18200 The syntax used here is the same as the syntax used for a remote
18201 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18202 Note that you may not access an existing signature file remotely,
18203 you have to create a new <EM>folder</EM> that contains the signature data.
18204 If the name you use here for the signature data is a remote name, then when
18205 you edit the file using the "F" command the data will
18206 be saved remotely in the folder.
18207 You aren't required to do anything special to create the folder, it
18208 gets created if you use a remote name.
18210 <P>
18211 If you type "F" you may edit the contents of the file (as opposed to
18212 the name of the file) you have specified.
18213 If you type "T" you may use a browser to choose an existing filename.
18214 <P>
18215 Besides containing regular text, a signature file may also
18216 contain (or a signature program may produce) tokens that are replaced with text
18217 that depends on the message you are replying to or forwarding.
18218 The tokens all look like _word_ (a word surrounded by underscores).
18219 For example, if the token
18220 <P>
18221 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18222 <P>
18223 is included in the text of the signature file, then when you reply to
18224 or forward a message, the token will be replaced with the actual date
18225 the message you are replying to or forwarding was sent.
18226 <P>
18227 If you use a role that has a signature file for a plain composition
18228 (that is, not a reply or forward) then there is no original message, so
18229 any tokens that depend on the message will be replaced with nothing.
18230 So if you want a signature file to be useful for new compositions it
18231 shouldn't include any of the tokens that depend on the message being
18232 replied to or forwarded.
18233 <P>
18234 The list of available tokens is
18235 <A HREF="h_index_tokens">here</A>.
18236 <P>
18237 Actually, for the adventurous, there is a way to conditionally include text based
18238 on whether or not a token would result in specific replacement text.
18239 For example, you could include some text based on whether or not
18240 the _NEWS_ token would result in any newsgroups if it was used.
18241 It's explained in detail
18242 <A HREF="h_reply_token_conditionals">here</A>.
18243 <P>
18244 In the very unlikely event that you want to include a literal token in
18245 a signature file, you must precede it with a backslash character.
18246 For example, to include the literal text _DATE_ you must actually use
18247 \_DATE_.
18248 It is not possible to have a literal backslash followed by an expanded token.
18249 <P>
18250 A blank field here means that Alpine will use its normal rules for deciding
18251 which file (if any) to use for the signature file.
18252 <P>
18253 An alternate method for storing the signature is available in
18254 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
18255 <P>
18256 Look <A HREF="h_edit_nav_cmds">here</A>
18257 to see the available Editing and Navigation commands.
18258 <P>
18259 <End of help on this topic>
18260 </BODY>
18261 </HTML>
18262 ======= h_config_role_settempl =======
18263 <HTML>
18264 <HEAD>
18265 <TITLE>Set Template Explained</TITLE>
18266 </HEAD>
18267 <BODY>
18268 <H1>Set Template Explained</H1>
18270 This describes part of the action to be taken if the Pattern for this
18271 role is a match.
18272 This field consists of a filename that will be used as the template
18273 file when using this role.
18274 The template file is a file that is included at the top of the message you
18275 are composing.
18276 <P>
18277 If the filename is followed by a vertical bar (|) then instead
18278 of reading the contents of the file the file is assumed to be a
18279 program that will produce the text to be used on its standard output.
18280 The program can't have any arguments and doesn't receive any input from Alpine,
18281 but the rest of the processing works as if the contents came from a file.
18282 <P>
18283 Instead of storing the data in a local file, the
18284 template may be stored remotely in an IMAP folder.
18285 In order to do this,
18286 you must use a remote name for the template.
18287 A remote template name might look like:
18288 <P>
18289 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
18290 <P>
18292 The syntax used here is the same as the syntax used for a remote
18293 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18294 Note that you may not access an existing template file remotely,
18295 you have to create a new <EM>folder</EM> that contains the template data.
18296 If the name you use here for the template is a remote name, then when
18297 you edit the file using the "F" command the data will
18298 be saved remotely in the folder.
18299 You aren't required to do anything special to create the folder, it
18300 gets created if you use a remote name.
18301 <P>
18302 If you type "F" you may edit the contents of the file (as opposed to
18303 the name of the file) you have specified.
18304 If you type "T" you may use a browser to choose an existing filename.
18305 <P>
18306 Besides containing regular text, the template file may also
18307 contain (or a template file program may produce) tokens that are replaced with text
18308 that depends on the message you are replying to or forwarding.
18309 The tokens all look like _word_ (a word surrounded by underscores).
18310 For example, if the token
18311 <P>
18312 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18313 <P>
18314 is included in the text of the template file, then when you reply to
18315 or forward a message, the token will be replaced with the actual date
18316 the message you are replying to or forwarding was sent.
18317 <P>
18318 If you use a role that has a template file for a plain composition
18319 (that is, not a reply or forward) then there is no original message, so
18320 any tokens that depend on the message will be replaced with nothing.
18321 So if you want a template file to be useful for new compositions it
18322 shouldn't include any of the tokens that depend on the message being
18323 replied to or forwarded.
18324 <P>
18325 The list of available tokens is
18326 <A HREF="h_index_tokens">here</A>.
18327 <P>
18328 Actually, for the adventurous, there is a way to conditionally include text based
18329 on whether or not a token would result in specific replacement text.
18330 For example, you could include some text based on whether or not
18331 the _NEWS_ token would result in any newsgroups if it was used.
18332 It's explained in detail
18333 <A HREF="h_reply_token_conditionals">here</A>.
18334 <P>
18335 In the very unlikely event that you want to include a literal token in
18336 a template file, you must precede it with a backslash character.
18337 For example, to include the literal text _DATE_ you must actually use
18338 \_DATE_.
18339 It is not possible to have a literal backslash followed by an expanded token.
18340 <P>
18341 A blank template field means that Alpine will not use a template file when
18342 this role is being used.
18343 <P>
18344 Look <A HREF="h_edit_nav_cmds">here</A>
18345 to see the available Editing and Navigation commands.
18346 <P>
18347 <End of help on this topic>
18348 </BODY>
18349 </HTML>
18350 ======= h_config_filt_stat_imp =======
18351 <HTML>
18352 <HEAD>
18353 <TITLE>Set Important Status Explained</TITLE>
18354 </HEAD>
18355 <BODY>
18356 <H1>Set Important Status Explained</H1>
18358 This describes part of the action to be taken if the Pattern for this
18359 filter is a match.
18360 If set to "Don't change it" then this does nothing.
18361 If set to "Set this state" then the Important flag is set
18362 for the matching message.
18363 If set to "Clear this state" then the Important flag is cleared
18364 for the matching message.
18365 The important flag usually causes an asterisk to show up in the MESSAGE
18366 INDEX.
18367 It may also be useful when selecting a set of messages
18368 with the Select command.
18369 <P>
18370 Look <A HREF="h_edit_nav_cmds">here</A>
18371 to see the available Editing and Navigation commands.
18372 <P>
18373 <End of help on this topic>
18374 </BODY>
18375 </HTML>
18376 ======= h_config_filt_stat_new =======
18377 <HTML>
18378 <HEAD>
18379 <TITLE>Set New Status Explained</TITLE>
18380 </HEAD>
18381 <BODY>
18382 <H1>Set New Status Explained</H1>
18384 This describes part of the action to be taken if the Pattern for this
18385 filter is a match.
18386 If set to "Don't change it" then this does nothing.
18387 If set to "Set this state" then the
18388 matching message is marked New.
18389 If set to "Clear this state" then the
18390 matching message is marked Seen.
18391 <P>
18392 Look <A HREF="h_edit_nav_cmds">here</A>
18393 to see the available Editing and Navigation commands.
18394 <P>
18395 <End of help on this topic>
18396 </BODY>
18397 </HTML>
18398 ======= h_config_filt_stat_ans =======
18399 <HTML>
18400 <HEAD>
18401 <TITLE>Set Answered Status Explained</TITLE>
18402 </HEAD>
18403 <BODY>
18404 <H1>Set Answered Status Explained</H1>
18406 This describes part of the action to be taken if the Pattern for this
18407 filter is a match.
18408 If set to "Don't change it" then this does nothing.
18409 If set to "Set this state" then the Answered flag is set
18410 for the matching message.
18411 If set to "Clear this state" then the Answered flag is cleared
18412 for the matching message.
18413 <P>
18414 Look <A HREF="h_edit_nav_cmds">here</A>
18415 to see the available Editing and Navigation commands.
18416 <P>
18417 <End of help on this topic>
18418 </BODY>
18419 </HTML>
18420 ======= h_config_filt_stat_del =======
18421 <HTML>
18422 <HEAD>
18423 <TITLE>Set Deleted Status Explained</TITLE>
18424 </HEAD>
18425 <BODY>
18426 <H1>Set Deleted Status Explained</H1>
18428 This describes part of the action to be taken if the Pattern for this
18429 filter is a match.
18430 If set to "Don't change it" then this does nothing.
18431 If set to "Set this state" then the
18432 matching message is marked Deleted.
18433 If set to "Clear this state" then the
18434 matching message is marked UnDeleted.
18435 <P>
18436 You should not use this option unless you are prepared to have matching
18437 messages expunged from the folder permanently.
18438 For example, if you type the Expunge command, this filter is applied
18439 before the expunge, so matching messages will be marked Deleted and then
18440 will be permanently expunged from the folder.
18441 However, since the index isn't redrawn in between the time that the message
18442 is marked Deleted and the time that you are asked to expunge, the only
18443 indication that you are expunging the message comes in the number of messages
18444 being expunged.
18445 The same thing may happen when you close a folder.
18446 It is also possible that an expunge not initiated by you will
18447 delete matching messages.
18448 <P>
18449 Look <A HREF="h_edit_nav_cmds">here</A>
18450 to see the available Editing and Navigation commands.
18451 <P>
18452 <End of help on this topic>
18453 </BODY>
18454 </HTML>
18455 ======= h_config_role_scoreval =======
18456 <HTML>
18457 <HEAD>
18458 <TITLE>Score Value Explained</TITLE>
18459 </HEAD>
18460 <BODY>
18461 <H1>Score Value Explained</H1>
18463 A message's score is the sum of the Score Values from all of the Scoring rules
18464 with Patterns that match the message.
18465 The value you give here is the Score Value associated with this rule.
18466 A Score Value is an integer between -100 and 100, with the default
18467 value of zero.
18468 <P>
18469 Alternatively, if the
18470 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18471 field is defined
18472 (on the line right below the "Score Value" field)
18473 then the "Score Value" is ignored and
18474 the "Score From Header" field is used instead.
18475 <P>
18476 Look <A HREF="h_edit_nav_cmds">here</A>
18477 to see the available Editing and Navigation commands.
18478 <P>
18479 <End of help on this topic>
18480 </BODY>
18481 </HTML>
18482 ======= h_config_role_scorehdrtok =======
18483 <HTML>
18484 <HEAD>
18485 <TITLE>Score Value From Header Explained</TITLE>
18486 </HEAD>
18487 <BODY>
18488 <H1>Score Value From Header Explained</H1>
18490 This option provides a way to use a number that appears in the headers of your
18491 messages as the message's score, or as a component of that score.
18492 If this field is defined then it is used instead of the "Score Value".
18493 The idea behind this option is that there may be a score embedded in the
18494 headers of messages that has already been calculated outside of Alpine.
18495 For example, messages delivered to you may contain an "X-Spam" header and
18496 somewhere in that header there is a score.
18497 <P>
18498 The value for this option is the name of the header followed by parentheses
18499 with two arguments inside:
18500 <P>
18501 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18502 <P>
18503 No space is allowed between the comma and the start of the field_separators.
18504 It would be interpreted as the first separator if it was there.
18505 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18506 starts after that and goes to the second separator, and so on.
18507 It's easier to explain with examples.
18508 <P>
18509 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18510 <P>
18511 In the above example the header that is used is the "X-Spam" header.
18512 The value of that header (the part after the colon and the space) is split
18513 into fields separated by spaces.
18514 <P>
18515 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18516 <P>
18517 The second field is selected and converted to an integer. It only makes sense
18518 if Field2 really is an integer.
18519 <P>
18520 Here's an example of a SpamAssassin header.
18521 The exact look of the header will vary, but if your incoming mail
18522 contains headers that look like the following
18523 <P>
18524 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18525 <P>
18526 you might want to use the hits value as a score.
18527 Since the score is an integer value you can't make use of the decimal part of
18528 the number, but
18529 you might split off the hits=10 part as a score by using the characters "="
18530 and "." as your separators.
18531 <P>
18532 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18533 <P>
18534 The first field starts with the Y in Yes and goes until the "=" after
18535 hits.
18536 The second field is "10" so the score value would be 10.
18537 <P>
18538 Another example we've seen has headers that look like
18539 <P>
18540 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18541 <P>
18542 Because there are two equals before the 7% the value
18543 <P>
18544 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18545 <P>
18546 should capture the probability as the score.
18547 <P>
18548 The Score From Header scoring value actually works just like the
18549 regular Score Value in that the rest of the pattern has to match before
18550 it is used and the scores from all the different scoring rules that
18551 match for a particular message are added together.
18552 When using the Score From Header method it may (or may not) make sense to
18553 use only a single scoring rule with a pattern that matches every message.
18554 <P>
18555 Look <A HREF="h_edit_nav_cmds">here</A>
18556 to see the available Editing and Navigation commands.
18557 <P>
18558 <End of help on this topic>
18559 </BODY>
18560 </HTML>
18561 ======= h_config_role_replyuse =======
18562 <HTML>
18563 <HEAD>
18564 <TITLE>Reply Use Explained</TITLE>
18565 </HEAD>
18566 <BODY>
18567 <H1>Reply Use Explained</H1>
18569 This option determines how this particular role will be used when Replying
18570 to a message.
18571 There are three possible values for this option.
18572 The value "Never"
18573 means that this role will not be a candidate for use when Replying.
18574 The role's Pattern will not be checked for a match, however the role will
18575 be available to be manually switched to if there is a confirmation prompt.
18576 <P>
18578 The options "With confirmation" and "Without confirmation"
18579 mean that you do want to consider this role when Replying.
18580 For either of these settings, the role's Pattern will be compared with
18581 the message being replied to.
18582 If there is a match then this role will either be used without confirmation
18583 or will be the default when confirmation is asked for, depending on
18584 which of the two options is selected.
18585 If confirmation is requested, you will also have a chance to
18586 manually change the role to any one of your other roles.
18587 <P>
18589 You won't be prompted for confirmation if none of your role Patterns
18590 match the message being replied to.
18591 This is independent of the value of the current option.
18592 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18593 feature may be used to change this behavior.
18594 <P>
18595 <End of help on this topic>
18596 </BODY>
18597 </HTML>
18598 ======= h_config_role_forwarduse =======
18599 <HTML>
18600 <HEAD>
18601 <TITLE>Forward Use Explained</TITLE>
18602 </HEAD>
18603 <BODY>
18604 <H1>Forward Use Explained</H1>
18606 This option determines how this particular role will be used when Forwarding
18607 a message.
18608 There are three possible values for this option.
18609 The value "Never"
18610 means that this role will not be a candidate for use when Forwarding.
18611 The role's Pattern will not be checked for a match, however the role will
18612 be available to be manually switched to if there is a confirmation prompt.
18613 <P>
18615 The options "With confirmation" and "Without confirmation"
18616 mean that you do want to consider this role when Forwarding.
18617 For either of these settings, the role's Pattern will be compared with
18618 the message being forwarded.
18619 If there is a match then this role will either be used without confirmation
18620 or will be the default when confirmation is asked for, depending on
18621 which of the two options is selected.
18622 If confirmation is requested, you will also have a chance to
18623 manually change the role to any one of your other roles.
18624 <P>
18626 You won't be prompted for confirmation if none of your role Patterns
18627 match the message being forwarded.
18628 This is independent of the value of the current option.
18629 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18630 feature may be used to change this behavior.
18631 <P>
18632 <End of help on this topic>
18633 </BODY>
18634 </HTML>
18635 ======= h_config_role_composeuse =======
18636 <HTML>
18637 <HEAD>
18638 <TITLE>Compose Use Explained</TITLE>
18639 </HEAD>
18640 <BODY>
18641 <H1>Compose Use Explained</H1>
18643 This option determines how this particular role will be used when Composing
18644 a new message using the "Compose" command.
18645 This does not affect what happens when using the "Role" command
18646 to compose a new message.
18647 The "Role" command allows you to select a role from all of the
18648 roles you have defined, regardless of what Uses you've assigned to those
18649 roles.
18650 <P>
18652 There are three possible values for this option.
18653 The value "Never"
18654 means that this role will not be a candidate for use when Composing.
18655 The role's Current Folder Type will not be checked for a match, however the role
18656 will be available to be manually switched to if there is a confirmation prompt.
18657 <P>
18659 The options "With confirmation" and "Without confirmation"
18660 mean that you do want to consider this role when Composing.
18661 For either of these settings,
18662 the role's Current Folder Type will be checked (since there is no message
18663 to compare with, the rest of the Pattern is considered a match).
18664 If there is a match then this role will either be used without confirmation
18665 or will be the default when confirmation is asked for, depending on
18666 which of the two options is selected.
18667 If confirmation is requested, you will also have a chance to
18668 manually change the role to any one of your other roles.
18669 <P>
18671 When using the Compose command the role checking is a little different
18672 because there is no message being replied to or forwarded.
18673 Because of this the Current Folder Type is checked but the header pattern
18674 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18675 A role is considered to be a match if it is a candidate for Compose Use and
18676 its Current Folder Type matches the currently open folder.
18677 This could be useful if you want to set a role based on the folder you
18678 are reading, or the type of folder you are reading.
18679 <P>
18681 You won't be prompted for confirmation if none of your role Patterns
18682 are a match.
18683 This is independent of the value of the current option.
18684 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18685 feature may be used to change this behavior.
18686 <P>
18687 <End of help on this topic>
18688 </BODY>
18689 </HTML>
18690 ======= h_config_filter_folder =======
18691 <HTML>
18692 <HEAD>
18693 <TITLE>Filter Folder Explained</TITLE>
18694 </HEAD>
18695 <BODY>
18696 <H1>Filter Folder Explained</H1>
18698 When the Filter Action is set to "Move",
18699 the folder or folders specified here will be used to store messages matching
18700 the provided pattern.
18702 <P>
18703 If you set the Filter Action to "Move" you must give a folder name
18704 here.
18706 <P>
18707 If you wish,
18708 you may choose a folder from your folder collections by using the
18709 "T" command.
18710 <P>
18711 Besides regular text, the folder name may also contain
18712 tokens that are replaced with text representing the current date
18713 when you run Alpine.
18714 For example, if the folder name you use is
18715 <P>
18716 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
18717 <P>
18718 that is replaced with something like
18719 <P>
18720 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
18721 <P>
18722 Or,
18723 <P>
18724 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
18725 <P>
18726 becomes
18727 <P>
18728 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
18729 <P>
18730 The token names must be surrounded by underscores in order to be recognized
18731 as tokens.
18732 The tokens that may be used are those that are derived from the current date.
18733 They're listed near the bottom of the list of tokens give
18734 <A HREF="h_index_tokens">here</A>.
18735 <P>
18736 Look "<A HREF="h_rule_patterns">here</A>"
18737 for more information on Patterns.
18738 <P>
18739 Look <A HREF="h_edit_nav_cmds">here</A>
18740 to see the available Editing and Navigation commands.
18741 <P>
18742 <End of help on this topic>
18743 </BODY>
18744 </HTML>
18745 ======= h_config_filter_kw_set =======
18746 <HTML>
18747 <HEAD>
18748 <TITLE>Set These Keywords Explained</TITLE>
18749 </HEAD>
18750 <BODY>
18751 <H1>Set These Keywords Explained</H1>
18753 This describes part of the action to be taken if the Pattern for this
18754 filter is a match.
18755 Read a little about keywords in the help text for the
18756 <A HREF="h_common_flag">Flag</A> command.
18757 This option is a list of keywords that will be Set when there is a match.
18758 If you wish, you may choose keywords from the list of keywords you have
18759 defined with the "T" command.
18760 You may add new keywords by defining them in the
18761 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18762 If you have given a keyword a nickname when configuring it,
18763 that nickname may be used instead of the actual keyword.
18765 <P>
18766 Look <A HREF="h_edit_nav_cmds">here</A>
18767 to see the available Editing and Navigation commands.
18768 <P>
18769 <End of help on this topic>
18770 </BODY>
18771 </HTML>
18772 ======= h_config_filter_kw_clr =======
18773 <HTML>
18774 <HEAD>
18775 <TITLE>Clear These Keywords Explained</TITLE>
18776 </HEAD>
18777 <BODY>
18778 <H1>Clear These Keywords Explained</H1>
18780 This describes part of the action to be taken if the Pattern for this
18781 filter is a match.
18782 Read a little about keywords in the help text for the
18783 <A HREF="h_common_flag">Flag</A> command.
18784 This option is a list of keywords that will be Cleared when there is a match.
18785 If you wish, you may choose keywords from the list of keywords you have
18786 defined with the "T" command.
18787 You may add new keywords by defining them in the
18788 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
18789 If you have given a keyword a nickname when configuring it,
18790 that nickname may be used instead of the actual keyword.
18792 <P>
18793 Look <A HREF="h_edit_nav_cmds">here</A>
18794 to see the available Editing and Navigation commands.
18795 <P>
18796 <End of help on this topic>
18797 </BODY>
18798 </HTML>
18799 ======= h_index_tokens =======
18800 <HTML>
18801 <HEAD>
18802 <TITLE>Tokens for Index and Replying</TITLE>
18803 </HEAD>
18804 <BODY>
18806 This set of special tokens may be used in the
18807 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
18808 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
18809 in signature files,
18810 in template files used in
18811 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
18812 that is the target of a Filter Rule.
18813 Some of them aren't available in all situations.
18814 <P>
18815 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
18816 option, but they must be surrounded by underscores for the
18817 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
18818 and in the target of Filter Rules.
18819 <P>
18820 <P>
18822 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
18824 <DL>
18825 <DT>SUBJECT</DT>
18826 <DD>
18827 This token represents the Subject the sender gave the message.
18828 Alternatives for use in the index screen are
18829 SUBJKEY, SUBJKEYINIT, SUBJECTTEXT, SUBJKEYTEXT, and SUBJKEYINITTEXT.
18830 You may color the subject text in the MESSAGE INDEX screen differently by using the
18831 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
18832 <A HREF="h_config_index_opening_color">Index Opening Color</A>
18833 options available from
18834 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18835 </DD>
18837 <DT>FROM</DT>
18838 <DD>
18839 This token represents the personal name (or email address if the name
18840 is unavailable) of the person specified in the message's "From:"
18841 header field.
18842 You may color the from text in the MESSAGE INDEX screen differently by using the
18843 <A HREF="h_config_index_from_color">Index From Color</A>
18844 option available from
18845 the <A HREF="h_color_setup">Setup Kolor</A> screen.
18846 </DD>
18848 <DT>ADDRESS</DT>
18849 <DD>
18850 This is similar to the "FROM" token, only it is always the
18851 email address, never the personal name.
18852 For example, "mailbox@domain".
18853 </DD>
18855 <DT>MAILBOX</DT>
18856 <DD>
18857 This is the same as the "ADDRESS" except that the
18858 domain part of the address is left off.
18859 For example, "mailbox".
18860 </DD>
18862 <DT>SENDER</DT>
18863 <DD>
18864 This token represents the personal name (or email address) of the person
18865 listed in the message's "Sender:" header field.
18866 </DD>
18868 <DT>TO</DT>
18869 <DD>
18870 This token represents the personal names (or email addresses if the names
18871 are unavailable) of the persons specified in the
18872 message's "To:" header field.
18873 </DD>
18875 <DT>NEWSANDTO</DT>
18876 <DD>
18877 This token represents the newsgroups from the
18878 message's "Newsgroups:" header field <EM>and</EM>
18879 the personal names (or email addresses if the names
18880 are unavailable) of the persons specified in the
18881 message's "To:" header field.
18882 </DD>
18884 <DT>TOANDNEWS</DT>
18885 <DD>
18886 Same as "NEWSANDTO" except in the opposite order.
18887 </DD>
18889 <DT>NEWS</DT>
18890 <DD>
18891 This token represents the newsgroups from the
18892 message's "Newsgroups:" header field.
18893 </DD>
18895 <DT>CC</DT>
18896 <DD>
18897 This token represents the personal names (or email addresses if the names
18898 are unavailable) of the persons specified in the
18899 message's "Cc:" header field.
18900 </DD>
18902 <DT>RECIPS</DT>
18903 <DD>
18904 This token represents the personal names (or email addresses if the names
18905 are unavailable) of the persons specified in both the
18906 message's "To:" header field and
18907 the message's "Cc:" header field.
18908 </DD>
18910 <DT>NEWSANDRECIPS</DT>
18911 <DD>
18912 This token represents the newsgroups from the
18913 message's "Newsgroups:" header field <EM>and</EM>
18914 the personal names (or email addresses if the names
18915 are unavailable) of the persons specified in the
18916 message's "To:" and "Cc:" header fields.
18917 </DD>
18919 <DT>RECIPSANDNEWS</DT>
18920 <DD>
18921 Same as "NEWSANDRECIPS" except in the opposite order.
18922 </DD>
18924 <DT>INIT</DT>
18925 <DD>
18926 This token represents the initials from the personal name
18927 of the person specified in the message's "From:"
18928 header field.
18929 If there is no personal name, it is blank.
18930 </DD>
18932 <DT>DATE</DT>
18933 <DD>
18934 This token represents the date on which the message was sent, according
18935 to the "Date" header field.
18936 It has the format MMM DD. For example, "Oct 23".
18937 The feature
18938 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
18939 which adjusts for the timezone the message was sent from,
18940 may have an effect on the value of this token as well as the values of
18941 all of the other DATE or TIME tokens.
18942 Some of the DATE and TIME tokens are displayed in a locale-specific
18943 way unless the option
18944 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
18945 </DD>
18947 <DT>SMARTDATE</DT>
18948 <DD>
18949 This token represents the date on which the message was sent, according
18950 to the "Date" header field.
18951 It is "Today" if the message was sent today,
18952 "Yesterday" for yesterday,
18953 "Wednesday" if it was last Wednesday, and so on. If the
18954 message is from last year and is more than six months old it includes the year, as well.
18955 See the SMARTDATE alternatives below, as well.
18956 </DD>
18958 <DT>SMARTTIME</DT>
18959 <DD>
18960 This token represents the most relevant elements of the date on which
18961 the message was sent (according to the "Date" header field),
18962 in a compact form. If the message was sent today, only the time is used
18963 (e.g. "9:22am", "10:07pm"); if it was sent during
18964 the past week, the day of the week and the hour are used
18965 (e.g. "Wed09am", "Thu10pm"); other dates are
18966 given as date, month, and year (e.g. "23Aug00",
18967 "9Apr98").
18968 </DD>
18970 <DT>SMARTDATETIME</DT>
18971 <DD>
18972 This is a combination of SMARTDATE and SMARTTIME.
18973 It is SMARTDATE unless the SMARTDATE value is "Today", in which
18974 case it is SMARTTIME.
18975 See the SMARTDATETIME alternatives below, as well.
18976 </DD>
18978 <DT>DATEISO</DT>
18979 <DD>
18980 This token represents the date on which the message was sent, according
18981 to the "Date" header field.
18982 It has the format YYYY-MM-DD. For example, "1998-10-23".
18983 </DD>
18985 <DT>SHORTDATEISO</DT>
18986 <DD>
18987 This token represents the date on which the message was sent, according
18988 to the "Date" header field.
18989 It has the format YY-MM-DD. For example, "98-10-23".
18990 </DD>
18992 <DT>SHORTDATE1</DT>
18993 <DD>
18994 This token represents the date on which the message was sent, according
18995 to the "Date" header field.
18996 It has the format MM/DD/YY. For example, "10/23/98".
18997 </DD>
18999 <DT>SHORTDATE2</DT>
19000 <DD>
19001 This token represents the date on which the message was sent, according
19002 to the "Date" header field.
19003 It has the format DD/MM/YY. For example, "23/10/98".
19004 </DD>
19006 <DT>SHORTDATE3</DT>
19007 <DD>
19008 This token represents the date on which the message was sent, according
19009 to the "Date" header field.
19010 It has the format DD.MM.YY. For example, "23.10.98".
19011 </DD>
19013 <DT>SHORTDATE4</DT>
19014 <DD>
19015 This token represents the date on which the message was sent, according
19016 to the "Date" header field.
19017 It has the format YY.MM.DD. For example, "98.10.23".
19018 </DD>
19020 <DT>LONGDATE</DT>
19021 <DD>
19022 This token represents the date on which the message was sent, according
19023 to the "Date" header field.
19024 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
19025 </DD>
19027 <DT>SMARTDATE alternatives</DT>
19028 <DD>
19029 There are several versions of SMARTDATE that are all the same except
19030 for the way they format dates far in the past.
19031 SMARTDATE formats the date using the information from your locale settings
19032 to format the date string. It may end up formatting dates so that they look
19033 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19034 The feature
19035 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19036 may have an affect on the values of these tokens.
19037 If you want more control you may use one of the following.
19038 <DL>
19039 <DT>SMARTDATE</DT> <DD>If the option
19040 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19041 then this will be locale specific. Control this with the
19042 LC_TIME locale setting on a UNIX system. On Windows
19043 the Regional Options control panel may be used to set the Short date
19044 format. At the programming level, the strftime routine is what Alpine
19045 uses to print the date.
19046 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19047 to SMARTDATES1.</DD>
19048 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
19049 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19050 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
19051 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
19052 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
19053 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
19054 </DL>
19055 </DD>
19057 <DT>SMARTDATETIME alternatives</DT>
19058 <DD>
19059 There are several versions of SMARTDATETIME that are all very similar.
19060 The ones that end in 24 use a 24-hour clock for Today's messages instead
19061 of a 12-hour clock.
19062 The other variation is
19063 for the way they format dates far in the past.
19064 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
19065 to format the date string. It may end up formatting dates so that they look
19066 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19067 The feature
19068 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19069 may have an affect on the values of these tokens.
19070 The possible choices are:
19071 <DL>
19072 <DT>SMARTDATETIME</DT> <DD>If the option
19073 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19074 then this will be locale specific. Control this with the
19075 LC_TIME locale setting on a UNIX system. On Windows
19076 the Regional Options control panel may be used to set the Short date
19077 format. At the programming level, the strftime routine is what Alpine
19078 uses to print the date.
19079 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19080 to SMARTDATETIMES1.</DD>
19081 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
19082 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
19083 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
19084 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19085 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
19086 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
19087 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
19088 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
19089 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
19090 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
19091 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
19092 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
19093 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
19094 </DL>
19095 </DD>
19097 <DT>DAYDATE</DT>
19098 <DD>
19099 This token represents the date on which the message was sent, according
19100 to the "Date" header field.
19101 It looks like "Sat, 23 Oct 1998".
19102 This token is never converted in any locale-specific way.
19103 </DD>
19105 <DT>PREFDATE</DT>
19106 <DD>
19107 This token represents the date on which the message was sent, according
19108 to the "Date" header field.
19109 It is your operating system's idea of the preferred date representation for the current locale.
19110 Internally it uses the %x version of the date from the strftime routine.
19111 </DD>
19113 <DT>PREFTIME</DT>
19114 <DD>
19115 This token represents the time at which the message was sent, according
19116 to the "Date" header field.
19117 It is the preferred time representation for the current locale.
19118 Internally it uses the %X version of the time from the strftime routine.
19119 </DD>
19121 <DT>PREFDATETIME</DT>
19122 <DD>
19123 This token represents the date and time at which the message was sent, according
19124 to the "Date" header field.
19125 It is the preferred date and time representation for the current locale.
19126 Internally it uses the %c version of the time from the strftime routine.
19127 </DD>
19129 <DT>DAY</DT>
19130 <DD>
19131 This token represents the day of the month on which the message was sent,
19132 according to the "Date" header field.
19133 For example, "23" or "9".
19134 </DD>
19136 <DT>DAY2DIGIT</DT>
19137 <DD>
19138 This token represents the day of the month on which the message was sent,
19139 according to the "Date" header field.
19140 For example, "23" or "09".
19141 It is always 2 digits.
19142 </DD>
19144 <DT>DAYORDINAL</DT>
19145 <DD>
19146 This token represents the ordinal number that is the day of
19147 the month on which the message was sent,
19148 according to the "Date" header field.
19149 For example, "23rd" or "9th".
19150 </DD>
19152 <DT>DAYOFWEEK</DT>
19153 <DD>
19154 This token represents the day of the week on which the message was sent,
19155 according to the "Date" header field.
19156 For example, "Sunday" or "Wednesday".
19157 </DD>
19159 <DT>DAYOFWEEKABBREV</DT>
19160 <DD>
19161 This token represents the day of the week on which the message was sent,
19162 according to the "Date" header field.
19163 For example, "Sun" or "Wed".
19164 </DD>
19166 <DT>MONTHABBREV</DT>
19167 <DD>
19168 This token represents the month the message was sent, according
19169 to the "Date" header field.
19170 For example, "Oct".
19171 </DD>
19173 <DT>MONTHLONG</DT>
19174 <DD>
19175 This token represents the month in which the message was sent, according
19176 to the "Date" header field.
19177 For example, "October".
19178 </DD>
19180 <DT>MONTH</DT>
19181 <DD>
19182 This token represents the month in which the message was sent, according
19183 to the "Date" header field.
19184 For example, "10" or "9".
19185 </DD>
19187 <DT>MONTH2DIGIT</DT>
19188 <DD>
19189 This token represents the month in which the message was sent, according
19190 to the "Date" header field.
19191 For example, "10" or "09".
19192 It is always 2 digits.
19193 </DD>
19195 <DT>YEAR</DT>
19196 <DD>
19197 This token represents the year the message was sent, according
19198 to the "Date" header field.
19199 For example, "1998" or "2001".
19200 </DD>
19202 <DT>YEAR2DIGIT</DT>
19203 <DD>
19204 This token represents the year the message was sent, according
19205 to the "Date" header field.
19206 For example, "98" or "01".
19207 It is always 2 digits.
19208 </DD>
19210 <DT>TIME24</DT>
19211 <DD>
19212 This token represents the time at which the message was sent, according
19213 to the "Date" header field.
19214 There is no adjustment made for different time zones, so you'll get
19215 the time the message was sent according to the time zone the sender
19216 was in.
19217 It has the format HH:MM. For example, "17:28".
19218 </DD>
19220 <DT>TIME12</DT>
19221 <DD>
19222 This token represents the time at which the message was sent, according
19223 to the "Date" header field.
19224 This time is for a 12 hour clock.
19225 It has the format HH:MMpm.
19226 For example, "5:28pm" or "11:13am".
19227 </DD>
19229 <DT>TIMEZONE</DT>
19230 <DD>
19231 This token represents the numeric timezone from
19232 the "Date" header field.
19233 It has the format [+-]HHMM. For example, "-0800".
19234 </DD>
19236 </DL>
19238 <P>
19239 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
19241 <DL>
19242 <DT>MSGNO</DT>
19243 <DD>
19244 This token represents the message's current position in the folder that,
19245 of course, may change as the folder is sorted or new mail arrives.
19246 </DD>
19248 <DT>STATUS</DT>
19249 <DD>
19250 This token represents a three character wide field displaying various
19251 aspects of the message's state.
19252 The first character is either blank,
19253 a '*' for message marked Important, or a '+' indicating a message
19254 addressed directly to you (as opposed to your having received it via a
19255 mailing list, for example).
19256 When the feature
19257 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
19258 is set, if the first character would have been
19259 blank then it will instead be a '-' if the message is cc'd to you.
19260 The second character is typically blank,
19261 though the arrow cursor may occupy it if either the
19262 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
19263 or the
19264 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
19265 is set (or you actually are on a slow link).
19266 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
19267 '<A HREF="h_flag_answered">A</A>' (Answered),
19268 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
19269 '<A HREF="h_flag_new">N</A>' (New), or blank.
19270 <P>
19271 If you are using a threaded view of the index and this message is at the
19272 top of a collapsed portion of a thread,
19273 then this token refers to all of the messages in the collapsed portion of
19274 the thread instead of just the top message.
19275 The first character will be a '*' if <EM>any</EM> of the messages in the thread
19276 are marked Important, else a '+' if any of the messages are addressed
19277 to you, else a '-' if any of the messages are cc'd to you.
19278 The third character will be a 'D' if <EM>all</EM> of the messages
19279 in the collapsed thread are marked deleted,
19280 an 'A' if <EM>all</EM> of the messages
19281 in the collapsed thread are marked answered,
19282 it will be an 'N' if any of
19283 the messages are undeleted and unseen, and it will be blank otherwise.
19284 </DD>
19286 <DT>FULLSTATUS</DT>
19287 <DD>
19288 This token represents a less abbreviated alternative
19289 to the "STATUS" token.
19290 It is six characters wide.
19291 The first character is '+', '-', or blank, the
19292 second blank, the third either '*' or blank, the fourth
19293 '<A HREF="h_flag_new">N</A>' or blank,
19294 the fifth '<A HREF="h_flag_answered">A</A>'
19295 or blank, and the sixth character is
19296 either '<A HREF="h_flag_deleted">D</A>' or
19297 blank.
19298 <P>
19299 If you are using a threaded view of the index and this message is at the
19300 top of a collapsed portion of a thread,
19301 then this token refers to all of the messages in the collapsed portion of
19302 the thread instead of just the top message.
19303 The first character is '+', '-', or blank depending on whether <EM>any</EM>
19304 of the messages in the collapsed thread are addressed to you or cc'd to you.
19305 The third character will be '*' if any of the messages are marked
19306 Important.
19307 The fourth character will be 'N' if all of the messages in the thread
19308 are New, else 'n' if some of the messages in the thread are New, else blank.
19309 The fifth character will be 'A' or 'a' or blank, and the sixth character
19310 will be 'D' or 'd' or blank.
19311 </DD>
19313 <DT>IMAPSTATUS</DT>
19314 <DD>
19315 This token represents an even less abbreviated alternative to the
19316 "STATUS" token.
19317 It differs from "FULLSTATUS" in only the fourth character, which is
19318 an 'N' if the message is new to this folder since the last time
19319 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
19320 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
19321 new to the folder since it was last opened <EM>but</EM> has not been
19322 viewed, or a blank if the message has been in the folder since it was
19323 last opened and has been viewed.
19324 <P>
19325 If you are using a threaded view of the index and this message is at the
19326 top of a collapsed portion of a thread,
19327 then the fourth character will be
19328 'N' if all of the messages in the thread are unseen and recent;
19329 else 'n' if some of the messages in the thread are unseen and recent;
19330 else 'U' if all of the messages in the thread are unseen and not recent;
19331 else 'u' if some of the messages in the thread are unseen and not recent;
19332 else 'R' if all of the messages in the thread are seen and recent;
19333 else 'r' if some of the messages in the thread are seen and recent;
19334 else blank.
19335 </DD>
19337 <DT>SHORTIMAPSTATUS</DT>
19338 <DD>
19339 This is the same as the last four of the six characters of IMAPSTATUS,
19340 so the '+' To Me information will be missing.
19341 </DD>
19343 <DT>SIZE</DT>
19344 <DD>
19345 This token represents the total size, in bytes, of the message.
19346 If a "K" (Kilobyte)
19347 follows the number, the size is approximately 1,000
19348 times that many bytes (rounded to the nearest 1,000).
19349 If an "M" (Megabyte) follows the number, the size is approximately
19350 1,000,000 times that many bytes.
19351 Commas are not used in this field.
19352 This field is seven characters wide, including the enclosing parentheses.
19353 Sizes are rounded when "K" or "M" is present.
19354 The progression of sizes used looks like:
19356 <P>
19357 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
19358 <P>
19359 </DD>
19361 <DT>SIZECOMMA</DT>
19362 <DD>
19363 This token represents the total size, in bytes, of the message.
19364 If a "K" (Kilobyte)
19365 follows the number, the size is approximately 1,000
19366 times that many bytes (rounded to the nearest 1,000).
19367 If an "M" (Megabyte) follows the number, the size is approximately
19368 1,000,000 times that many bytes.
19369 Commas are used if the number shown is 1,000 or greater.
19370 The SIZECOMMA field is one character wider than the SIZE field.
19371 Sizes are rounded when "K" or "M" is present.
19372 The progression of sizes used looks like:
19374 <P>
19375 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
19376 <P>
19377 </DD>
19379 <DT>KSIZE</DT>
19380 <DD>
19381 This token represents the total size of the message, expressed in
19382 kilobytes or megabytes, as most appropriate.
19383 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19384 The progression of sizes used looks like:
19386 <P>
19387 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19388 <P>
19389 </DD>
19391 <DT>SIZENARROW</DT>
19392 <DD>
19393 This token represents the total size, in bytes, of the message.
19394 If a "K" (Kilobyte)
19395 follows the number, the size is approximately 1,000
19396 times that many bytes.
19397 If an "M" (Megabyte) follows the number, the size is approximately
19398 1,000,000 times that many bytes.
19399 If a "G" (Gigabyte) follows the number, the size is approximately
19400 1,000,000,000 times that many bytes.
19401 This field uses only five characters of screen width, including the enclosing
19402 parentheses.
19403 The progression of sizes used looks like:
19405 <P>
19406 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19407 <P>
19408 </DD>
19410 <DT>DESCRIPSIZE</DT>
19411 <DD>
19412 This token is intended to represent a more useful description of the
19413 message than just its size, but it isn't very useful at this point.
19414 The plus sign in this view means there are attachments.
19415 Note that including this token in
19416 the "<!--#echo var="VAR_index-format"-->" could slow down the
19417 display a little while Alpine collects the necessary information.
19418 </DD>
19420 <DT>SUBJKEY</DT>
19421 <DD>
19422 This token is the same as the SUBJECT token unless keywords are set for
19423 the message.
19424 In that case, a list of keywords enclosed in braces will be prepended to
19425 the subject of the message.
19426 Only those keywords that you have defined in your
19427 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19428 in Setup/Config are considered in the list.
19429 In other words, keywords that have been set by some other means, perhaps
19430 by another email program, won't show up unless included in
19431 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19432 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19433 prepended to the subject in the MESSAGE TEXT screen.
19434 If you have given a keyword a nickname
19435 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19436 instead of the actual keyword.
19437 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19438 option may be used to modify this token slightly.
19439 It is also possible to color keywords in the index using the
19440 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19441 </DD>
19443 <DT>SUBJKEYINIT</DT>
19444 <DD>
19445 This token is the same as the SUBJKEY token except that instead of
19446 prepending a list of keywords to the subject, a list of first initials
19447 of keywords will be prepended instead.
19448 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19449 set (or Work and Now are the Alpine nicknames of keywords that are set)
19450 then the SUBJKEY token would cause a result like
19451 <P>
19452 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19453 <P>
19454 whereas the SUBJKEYINIT token would give
19455 <P>
19456 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19457 <P>
19458 Only those keywords that you have defined in your
19459 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19460 in Setup/Config are considered in the list.
19461 In other words, keywords that have been set by some other means, perhaps
19462 by another email program, won't show up unless included in
19463 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19464 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19465 option may be used to modify this token slightly.
19466 It is also possible to color keywords in the index using the
19467 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19468 </DD>
19470 <DT>SUBJECTTEXT</DT>
19471 <DD>
19472 Same as SUBJECT but if there is room in the Subject field for more text,
19473 the opening part of the text of the message is displayed after the subject.
19474 The time needed to fetch the text may cause a performance problem
19475 which can, of course, be avoided by using the SUBJECT version of
19476 the Subject instead.
19477 You may color this opening text differently by using the
19478 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19479 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19480 You may adjust the characters that are displayed between the Subject and the
19481 opening text with the option
19482 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19483 </DD>
19485 <DT>SUBJKEYTEXT</DT>
19486 <DD>
19487 Same as SUBJKEY but with the opening message text.
19488 </DD>
19490 <DT>OPENINGTEXT</DT>
19491 <DD>
19492 This is similar to SUBJECTTEXT.
19493 Instead of combining the Subject and the opening text in a single
19494 field in the index screen this token allows you to allocate a
19495 separate column just for the opening text of the message.
19496 The time needed to fetch this text may cause a performance problem.
19497 You may color this opening text differently by using the
19498 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19499 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19500 </DD>
19502 <DT>OPENINGTEXTNQ</DT>
19503 <DD>
19504 This is very similar to OPENINGTEXT.
19505 The NQ stands for No Quotes.
19506 The only difference is that quoted text (lines beginning with >) is deleted.
19507 For some messages this may be confusing.
19508 For example, a message might have a line preceding some quoted
19509 text that reads something like "On May 8th person A said."
19510 That no longer makes sense after the quoted text is deleted and it
19511 will appear that person A said whatever the text after the quote
19512 is, even though that is really person B talking.
19513 </DD>
19515 <DT>SUBJKEYINITTEXT</DT>
19516 <DD>
19517 Same as SUBJKEYINIT but with the opening message text.
19518 </DD>
19520 <DT>KEY</DT>
19521 <DD>
19522 This is a space-delimited list of keywords that are set for the message.
19523 Only those keywords that you have defined in your
19524 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19525 in Setup/Config are considered in the list.
19526 In other words, keywords that have been set by some other means, perhaps
19527 by another email program, won't show up unless included in
19528 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19529 If you have given a keyword a nickname
19530 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19531 instead of the actual keyword.
19532 It is also possible to color keywords in the index using the
19533 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19534 This token defaults to an arbitrary width of 5.
19535 You should set it to whatever width suits you using something
19536 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19537 </DD>
19539 <DT>KEYINIT</DT>
19540 <DD>
19541 This is a list of keyword initials that are set for the message.
19542 If you have given a keyword a nickname
19543 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19544 is displayed instead of the initial of the actual keyword.
19545 It is also possible to color keyword initials in the index using the
19546 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19547 This token defaults to an arbitrary width of 2.
19548 You should set it to whatever width suits you using something
19549 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19550 </DD>
19552 <DT>PRIORITY</DT>
19553 <DD>
19554 The X-Priority header is a non-standard header that is used in a
19555 somewhat standard way by many mail programs.
19556 Alpine expects the value of this header to be a digit with a value
19557 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19558 Since this priority is something that the sender sets it is only an indication
19559 of the priority that the sender attaches to the mail and it is therefore almost
19560 totally unreliable for use as a filtering criterion.
19561 This token will display the numeric value of the priority if it is between
19562 1 and 5.
19563 It will be suppressed (blank) if the value is 3, which is normal priority.
19564 This token may be colored with the
19565 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19566 </DD>
19568 <DT>PRIORITYALPHA</DT>
19569 <DD>
19570 This is a more verbose interpretation of the X-Priority field.
19571 Once again nothing is displayed unless the value of the field
19572 is 1, 2, 4, or 5.
19573 The values displayed for those values are:
19574 <P>
19575 <TABLE>
19576 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19577 <TR> <TD>2</TD> <TD>High</TD> </TR>
19578 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19579 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19580 </TABLE>
19581 <P>
19582 This token may be colored with the
19583 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19584 </DD>
19586 <DT>PRIORITY!</DT>
19587 <DD>
19588 This is a one character, non-numeric version of the X-Priority field.
19589 If the value of the X-Priority header is 1 or 2 an exclamation
19590 point is displayed.
19591 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19592 This token may be colored with the
19593 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19594 </DD>
19596 <DT>ATT</DT>
19597 <DD>
19598 This is a one column wide field that represents the number of attachments
19599 a message has. It will be blank if there are no attachments, a single
19600 digit for one to nine attachments, or an asterisk for more than nine.
19601 Note that including this token in
19602 the "<!--#echo var="VAR_index-format"-->" could slow down the
19603 display a little while Alpine collects the necessary information.
19604 </DD>
19606 <DT>FROMORTO</DT>
19607 <DD>
19608 This token represents <EM>either</EM> the personal name (or email address) of
19609 the person listed in the message's "From:" header
19610 field, <EM>or</EM>, if that address is yours or one of your
19611 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19612 the first person specified in the
19613 message's "To:" header field
19614 with the prefix "To: " prepended.
19615 If the from address is yours and there is also no "To" address,
19616 Alpine will use the address on the "Cc" line.
19617 If there is no address there, either, Alpine will look for a newsgroup name
19618 from the "Newsgroups" header field and put
19619 that after the "To: " prefix.
19620 </DD>
19622 <DT>FROMORTONOTNEWS</DT>
19623 <DD>
19624 This is almost the same as <EM>FROMORTO</EM>.
19625 The difference is that newsgroups aren't considered.
19626 When a message is from you, doesn't have a To or Cc, and does have
19627 a Newsgroups header; this token will be your name instead of the name
19628 of the newsgroup (like it would be with FROMORTO).
19629 </DD>
19631 <DT>TEXT</DT>
19632 <DD>
19633 This is a different sort of token.
19634 It allows you to display a label within each index line.
19635 It will be the same fixed text for each line.
19636 It is different from all the other tokens in that there is no space column
19637 displayed after this token.
19638 Instead, it is butted up against the following field.
19639 It also has a different syntax.
19640 The text to display is given following a colon after the
19641 word "TEXT".
19642 For example,
19643 <P>
19644 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19645 <P>
19646 would insert the literal text "abc=" (without the quotes)
19647 into the index display line.
19648 You must quote the text if it includes space characters, like
19649 <P>
19650 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
19651 <P>
19652 </DD>
19654 <DT>HEADER</DT>
19655 <DD>
19656 This allows you to display the text from a particular header line in the
19657 message.
19658 The syntax for this token is substantially different from all the others
19659 in order that you might be able to display a portion of the text following
19660 a particular header.
19661 The header name you are interested in is given following a colon
19662 after the word "HEADER".
19663 For example,
19664 <P>
19665 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
19666 <P>
19667 would display the text of the X-Spam header, if any.
19668 Like for other index tokens a width field may (and probably should)
19669 follow this.
19670 <P>
19671 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
19672 <P>
19673 displays the first ten characters of the X-Spam header.
19674 Unlike other index tokens, the syntax for HEADER is more flexible.
19675 An optional second argument comes after a comma inside the parentheses.
19676 It specifies the "field" number.
19677 By default, the field separator is a space character.
19678 No extra space characters are allowed in the argument list.
19679 <P>
19680 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
19681 <P>
19682 would display the second field, left-justified, in a 10 character
19683 wide field.
19684 The second field would consist of all the text after the first space
19685 up to the next space or the end of the header.
19686 The default field number is zero, which stands for the entire line.
19687 There is also an optional third argument that is a list of field
19688 separators. It defaults to a space character.
19689 The example
19690 <P>
19691 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
19692 <P>
19693 would cause the field separators to be any of colon, percent,
19694 or space (there is a space character between the percent and the
19695 right parenthesis).
19696 The first field runs from the start of the header value up to the first
19697 colon, percent, or space; the second goes from there to the next; and so on.
19698 In order to use a comma character as a field separator you must escape
19699 it by preceding it with a backslash (\).
19700 The same is true of the backslash character itself.
19701 There is one further optional argument.
19702 It is an R or an L to specify right or left adjustment of the text
19703 within the field.
19704 The default is to left justify, however if you are displaying numbers
19705 you might prefer to right justify.
19706 <P>
19707 Here's an example of a SpamAssassin header.
19708 The exact look of the header will vary, but if your incoming mail
19709 contains headers that look like the following
19710 <P>
19711 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
19712 <P>
19713 you might want to display the hits value.
19714 The first field starts with the Y in Yes.
19715 To get what you're interested in you might use "=" and
19716 space as the field separators and display the third field, like
19717 <P>
19718 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
19719 <P>
19720 or maybe you would break at the dot instead
19721 <P>
19722 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
19723 <P>
19724 Another example we've seen has headers that look like
19725 <P>
19726 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
19727 <P>
19728 Because there are two equals and a comma before the 7% and a comma
19729 after it, the token
19730 <P>
19731 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
19732 <P>
19733 should display the probability (for example 7% or 83%) right justified
19734 in a 3-wide field.
19735 </DD>
19737 <DT>ARROW</DT>
19738 <DD>
19739 This gives an alternative way to display the current message in the
19740 MESSAGE INDEX screen.
19741 Usually the current message is indicated by the line being shown in
19742 reverse video.
19743 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
19744 the current line will include an "arrow" that
19745 looks like
19746 <P>
19747 <CENTER><SAMP>-></SAMP></CENTER>
19748 <P>
19749 in the ARROW token's field.
19750 For all of the non-current messages, the ARROW field will be filled
19751 with blanks.
19752 If you use the fixed-field width feature the length of the "arrow"
19753 may be adjusted.
19754 The arrow will be drawn as width-1 dashes followed by a greater than sign.
19755 For example, if you use ARROW(3) you will get
19756 <P>
19757 <CENTER><SAMP>--></SAMP></CENTER>
19758 <P>
19759 and ARROW(1) will give you just
19760 <P>
19761 <CENTER><SAMP>></SAMP></CENTER>
19762 <P>
19763 It is also possible to set the color of the ARROW field.
19764 By default (and for non-current messages) the arrow is colored the same
19765 as the index line it is part of.
19766 You may set it to be another color with the
19767 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
19768 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19769 </DD>
19771 <DT>SCORE</DT>
19772 <DD>
19773 This gives the
19774 <a href="h_rules_score">score</a>
19775 of each message.
19776 This will be six columns wide to accomodate the widest possible score.
19777 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
19778 to limit the width of the field to the widest score that
19779 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
19780 If you have not defined any score rules the scores will all be zero.
19781 If any of your score rules contain AllText or BodyText patterns
19782 then including SCORE in the <!--#echo var="VAR_index-format"-->
19783 may slow down the display of the MESSAGE INDEX screen.
19784 </DD>
19785 </DL>
19787 <P>
19788 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
19790 <DL>
19791 <DT>CURNEWS</DT>
19792 <DD>
19793 This token represents the current newsgroup if there is one.
19794 For example, "comp.mail.pine".
19795 </DD>
19797 <DT>MSGID</DT>
19798 <DD>
19799 This token represents the message ID of the message.
19800 This token does not work with Filter Rule folder names.
19801 </DD>
19803 <DT>CURDATE</DT>
19804 <DD>
19805 This token represents the current date.
19806 It has the format MMM DD. For example, "Oct 23".
19807 </DD>
19809 <DT>CURDATEISO</DT>
19810 <DD>
19811 This token represents the current date.
19812 It has the format YYYY-MM-DD. For example, "1998-10-23".
19813 </DD>
19815 <DT>CURDATEISOS</DT>
19816 <DD>
19817 This token represents the current date.
19818 It has the format YY-MM-DD. For example, "98-10-23".
19819 </DD>
19821 <DT>CURPREFDATE</DT>
19822 <DD>
19823 This token represents the current date.
19824 It is your operating system's idea of the preferred date representation for the current locale.
19825 Internally it uses the %x version of the date from the strftime routine.
19826 </DD>
19828 <DT>CURPREFTIME</DT>
19829 <DD>
19830 This token represents the current time.
19831 It is the preferred time representation for the current locale.
19832 Internally it uses the %X version of the time from the strftime routine.
19833 </DD>
19835 <DT>CURPREFDATETIME</DT>
19836 <DD>
19837 This token represents the current date and time.
19838 It is the preferred date and time representation for the current locale.
19839 Internally it uses the %c version of the time from the strftime routine.
19840 </DD>
19842 <DT>CURTIME24</DT>
19843 <DD>
19844 This token represents the current time.
19845 It has the format HH:MM. For example, "17:28".
19846 </DD>
19848 <DT>CURTIME12</DT>
19849 <DD>
19850 This token represents the current time.
19851 This time is for a 12 hour clock.
19852 It has the format HH:MMpm.
19853 For example, "5:28pm" or "11:13am".
19854 </DD>
19856 <DT>CURDAY</DT>
19857 <DD>
19858 This token represents the current day of the month.
19859 For example, "23" or "9".
19860 </DD>
19862 <DT>CURDAY2DIGIT</DT>
19863 <DD>
19864 This token represents the current day of the month.
19865 For example, "23" or "09".
19866 It is always 2 digits.
19867 </DD>
19869 <DT>CURDAYOFWEEK</DT>
19870 <DD>
19871 This token represents the current day of the week.
19872 For example, "Sunday" or "Wednesday".
19873 </DD>
19875 <DT>CURDAYOFWEEKABBREV</DT>
19876 <DD>
19877 This token represents the current day of the week.
19878 For example, "Sun" or "Wed".
19879 </DD>
19881 <DT>CURMONTH</DT>
19882 <DD>
19883 This token represents the current month.
19884 For example, "10" or "9".
19885 </DD>
19887 <DT>CURMONTH2DIGIT</DT>
19888 <DD>
19889 This token represents the current month.
19890 For example, "10" or "09".
19891 It is always 2 digits.
19892 </DD>
19894 <DT>CURMONTHLONG</DT>
19895 <DD>
19896 This token represents the current month.
19897 For example, "October".
19898 </DD>
19900 <DT>CURMONTHABBREV</DT>
19901 <DD>
19902 This token represents the current month.
19903 For example, "Oct".
19904 </DD>
19906 <DT>CURYEAR</DT>
19907 <DD>
19908 This token represents the current year.
19909 For example, "1998" or "2001".
19910 </DD>
19912 <DT>CURYEAR2DIGIT</DT>
19913 <DD>
19914 This token represents the current year.
19915 For example, "98" or "01".
19916 It is always 2 digits.
19917 </DD>
19919 <DT>LASTMONTH</DT>
19920 <DD>
19921 This token represents last month.
19922 For example, if this is November (the 11th month),
19923 it is equal to "10" or if this is October (the 10th month),
19924 it is "9".
19925 It is possible that this and the other tokens beginning with LASTMONTH
19926 below could be useful when used with a Filtering Rule that
19927 has the "Beginning of Month" option set.
19928 </DD>
19930 <DT>LASTMONTH2DIGIT</DT>
19931 <DD>
19932 This token represents last month.
19933 For example, if this is November (the 11th month),
19934 it is equal to "10" or if this is October (the 10th month),
19935 it is "09".
19936 It is always 2 digits.
19937 </DD>
19939 <DT>LASTMONTHLONG</DT>
19940 <DD>
19941 This token represents last month.
19942 For example, if this is November the value is "October".
19943 </DD>
19945 <DT>LASTMONTHABBREV</DT>
19946 <DD>
19947 This token represents last month.
19948 For example, if this is November the value is "Oct".
19949 </DD>
19951 <DT>LASTMONTHYEAR</DT>
19952 <DD>
19953 This token represents what the year was a month ago.
19954 For example, if this is October, 1998, it is "1998".
19955 If this is January, 1998, it is "1997".
19956 </DD>
19958 <DT>LASTMONTHYEAR2DIGIT</DT>
19959 <DD>
19960 This token represents what the year was a month ago.
19961 For example, if this is October, 1998, it is "98".
19962 If this is January, 1998, it is "97".
19963 </DD>
19965 <DT>LASTYEAR</DT>
19966 <DD>
19967 This token represents last year.
19968 For example, if this is 1998, it equals "1997".
19969 It is possible that this
19970 could be useful when used with a Filtering Rule that
19971 has the "Beginning of Year" option set.
19972 </DD>
19974 <DT>LASTYEAR2DIGIT</DT>
19975 <DD>
19976 This token represents last year.
19977 For example, if this is 1998, it equals "97".
19978 It is always 2 digits.
19979 </DD>
19981 <DT>ROLENICK</DT>
19982 <DD>
19983 This token represents the nickname of the
19984 role currently being used. If no role is being used,
19985 then no text will be printed for this token.
19986 This token does not work with Filter Rule folder names.
19987 </DD>
19988 </DL>
19990 <P>
19991 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
19992 See the help for the
19993 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
19994 to see why you might want to use this.
19995 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
19996 must be surrounded by underscores when used.
19998 <DL>
19999 <DT>NEWLINE</DT>
20000 <DD>
20001 This is an end of line marker.
20002 </DD>
20003 </DL>
20005 <P>
20006 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
20008 <DL>
20009 <DT>CURSORPOS</DT>
20010 <DD>
20011 This token is different from the others.
20012 When it is replaced it is replaced with nothing, but it sets an Alpine
20013 internal variable that tells the composer to start with the cursor
20014 positioned at the position where this token was.
20015 If both the template file and the signature file contain
20016 a "CURSORPOS" token, then the position in the template file
20017 is used.
20018 If there is a template file and neither it nor the signature file contains
20019 a "CURSORPOS" token, then the cursor is positioned
20020 after the end of the contents of the
20021 template file when the composer starts up.
20022 </DD>
20023 </DL>
20025 <P>
20026 <End of help on this topic>
20027 </BODY>
20028 </HTML>
20029 ======= h_reply_token_conditionals =======
20030 <HTML>
20031 <HEAD>
20032 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
20033 </HEAD>
20034 <BODY>
20035 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
20037 Conditional text inclusion may be used with
20038 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
20039 in signature files, and in template files used in
20040 <A HREF="h_rules_roles">"roles"</A>.
20041 It may <EM>not</EM> be used with the
20042 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
20044 <P>
20045 There is a limited if-else capability for including text.
20046 The if-else condition is based
20047 on whether or not a given token would result in replacement text you
20048 specify.
20049 The syntax of this conditional inclusion is
20050 <P>
20051 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
20052 <P>
20053 The left parenthesis must follow the underscore immediately, with no
20054 intervening space.
20055 It means the token is expanded and the results of that expansion are
20056 compared against the "match_this" argument.
20057 If there is an exact match, then the "if_matched" text is used
20058 as the replacement text.
20059 Otherwise, the "if_not_matched" text is used.
20060 One of the most useful values for the "match_this" argument is
20061 the empty string, "".
20062 In that case the expansion is compared against the empty string.
20063 <P>
20064 Here's an example to make it clearer.
20065 This text could be included in one of your template files:
20066 <P>
20067 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
20068 <P>
20069 If that is included in a template file that you are using while replying
20070 to a message (because you chose to use the role it was part of),
20071 and that message has a newsgroup header and a newsgroup in that header,
20072 then the text
20073 <P>
20074 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
20075 <P>
20076 will be included in the message you are about to compose.
20077 On the other hand, if the message you are replying to does not have
20078 a newsgroup, then the text
20079 <P>
20080 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
20081 <P>
20082 would be included instead.
20083 This would also work in signature files and in
20084 the "<!--#echo var="VAR_reply-leadin"-->" option.
20085 If the "match_this", "if_matched",
20086 or "if_not_matched" arguments contain
20087 spaces, parentheses, or commas;
20088 they have to be quoted with double quotation marks (like in the example
20089 above).
20090 If you want to include a literal quote (") in the text you must escape the
20091 quote by preceding it with a backslash (\) character.
20092 If you want to include a literal backslash character you must escape it
20093 by preceding it with another backslash.
20094 <P>
20095 The comma followed by "if_not_matched" is optional.
20096 If there is no "if_not_matched"
20097 present then no text is included if the not_matched case is true.
20098 Here's another example:
20099 <P>
20100 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
20101 <P>
20102 Here you can see that tokens may appear in the arguments.
20103 The same is true for tokens with the conditional parentheses.
20104 They may appear in arguments,
20105 though you do have to be careful to get the quoting and escaping of
20106 nested double quotes correct.
20107 If this was in the signature file being used and you were replying to a message
20108 sent to comp.mail.pine the resulting text would be:
20109 <P>
20110 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
20111 <P>
20112 If you were replying to a message that wasn't sent to any newsgroup the
20113 resulting text would be a single blank line.
20114 The reason you'd get a blank line is because the end of the line is
20115 outside of the conditional, so is always included.
20116 If you wanted to get rid of that blank line you could do so by moving
20117 the end of line inside the conditional.
20118 In other words, it's ok to have multi-line
20119 "if_matched" or "if_not_matched" arguments in your
20120 template file.
20121 The text just continues until the next double quotation, even if it's not
20122 on the same line.
20123 <P>
20124 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
20125 <P>
20126 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
20127 <P>
20128 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
20129 while reading the newsgroup comp.mail.pine the resulting text would be:
20130 <P>
20131 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
20132 <P>
20133 If you were replying to a message while reading an email folder instead
20134 of a newsgroup the resulting leadin text would be
20135 <P>
20136 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
20137 <P>
20138 Here's one more (contrived) example illustrating a matching argument
20139 that is not the empty string.
20140 <P>
20141 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
20142 <P>
20143 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
20144 were replying to
20145 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
20146 would be
20147 <P>
20148 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
20149 <P>
20150 But if you were replying to a message sent on Oct. 27 (and that wasn't
20151 today) you would get
20152 <P>
20153 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
20154 <P>
20156 <End of help on this topic>
20157 </BODY>
20158 </HTML>
20159 ======= h_composer_cntxt_nick =======
20160 <HTML>
20161 <HEAD>
20162 <TITLE>Collection Nickname Explained</TITLE>
20163 </HEAD>
20164 <BODY>
20165 <H1>Collection Edit Help -- Nickname Field</H1>
20167 This field is provided so you can add a short nickname to use when
20168 referring to this collection within Alpine. Spaces are allowed, and
20169 you don't need to use double-quotes. However, the double-quote
20170 character is not allowed.
20171 <P>
20172 Look <A HREF="h_edit_nav_cmds">here</A>
20173 to see the available Editing and Navigation commands.
20174 <P>
20175 <End of help on this topic>
20176 </BODY>
20177 </HTML>
20178 ======= h_folder_server_syntax =======
20179 <HTML>
20180 <HEAD>
20181 <TITLE>Server Name Syntax</TITLE>
20182 </HEAD>
20183 <BODY>
20184 <H1>Server Name Syntax</H1>
20186 This help describes the syntax that may be used for server names
20187 that may be associated with remote folders or SMTP servers.
20189 <P>
20190 A server name is the hostname of the server.
20191 It's a good idea to use the host's fully-qualified network name.
20193 <P>
20194 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
20195 <P>
20197 However, IP addresses are allowed if surrounded
20198 with square-brackets.
20200 <P>
20201 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
20202 <P>
20204 An optional network port number may be supplied by appending
20205 a colon (:) followed by the port number
20206 to the server name.
20207 By default, the IMAP port number, 143, is used.
20209 <P>
20210 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
20211 <P>
20213 Besides server name and optional port number, various other optional
20214 parameters may be supplied that alter Alpine's interaction with the server.
20215 A parameter is supplied by appending a slash (/) character followed by
20216 the parameter's name and,
20217 depending on the particular parameter, the value assigned to that
20218 name, to the server name (and optional port number).
20219 Parameter names are <EM>not</EM> case sensitive.
20220 Currently supported parameters include:
20222 <DL>
20224 <DT>User</DT>
20225 <DD>This parameter requires an associated value, and is intended to
20226 provide the username identifier with which to establish the server
20227 connection.
20228 If your SMTP server offers SMTP AUTH authentication, adding this
20229 parameter to the
20230 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
20231 option will cause Alpine to attempt to authenticate to the server using the
20232 supplied username.
20233 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
20234 or "AUTHINFO USER" authentication, adding this parameter to the
20235 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
20236 option (or to the server name for any folder collection using NNTP)
20237 will cause Alpine to attempt
20238 to authenticate to the server using the supplied username.
20239 An example might be:
20241 <P>
20242 <CENTER><SAMP>/user=katie</SAMP></CENTER>
20243 <P>
20245 </DD>
20247 <DT>TLS</DT>
20248 <DD>
20249 Normally, when a new connection is made an attempt is made to
20250 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
20251 If that fails then a non-encrypted connection will be attempted instead.
20252 This is a unary parameter indicating communication with the server must
20253 take place over a TLS connection. If the attempt to use TLS fails then
20254 this parameter will cause the connection to fail instead of falling
20255 back to an unsecure connection.
20257 <P>
20258 <CENTER><SAMP>/tls</SAMP></CENTER>
20259 <P>
20261 </DD>
20263 <DT>SSL</DT>
20264 <DD>
20265 This is a unary parameter indicating communication with the server should
20266 take place over a Secure Socket Layer connection. The server must support
20267 this method, and be prepared to accept connections on the appropriate
20268 port (993 by default).
20269 Alpine must be linked with an SSL library for this option to be operational.
20271 <P>
20272 <CENTER><SAMP>/ssl</SAMP></CENTER>
20273 <P>
20275 </DD>
20277 <DT>TLS1</DT>
20278 <DD>
20279 This parameter indicates that the connection to the server will be made
20280 over the SSL port, but using the TLSv1 protocol, instead of the usual
20281 SSLv3 or SSLv2 protocols.
20282 Alpine must be linked with an SSL library for this option to be operational.
20284 <P>
20285 <CENTER><SAMP>/tls1</SAMP></CENTER>
20286 <P>
20288 </DD>
20290 <DT>DTLS1</DT>
20291 <DD>
20292 This parameter indicates that the connection to the server will be made
20293 over the SSL port, but using the DTLSv1 protocol, instead of the usual
20294 SSLv3 or SSLv2 protocols.
20295 Alpine must be linked with an SSL library for this option to be operational.
20297 <P>
20298 <CENTER><SAMP>/dtls1</SAMP></CENTER>
20299 <P>
20301 </DD>
20303 <DT>TLS1_1</DT>
20304 <DD>
20305 This parameter indicates that the connection to the server will be made
20306 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
20307 SSLv3 or SSLv2 protocols.
20308 Alpine must be linked with an SSL library for this option to be operational.
20310 <P>
20311 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
20312 <P>
20314 </DD>
20316 <DT>TLS1_2</DT>
20317 <DD>
20318 This parameter indicates that the connection to the server will be made
20319 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
20320 SSLv3 or SSLv2 protocols.
20321 Alpine must be linked with an SSL library for this option to be operational.
20323 <P>
20324 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
20325 <P>
20327 </DD>
20330 <DT>NoValidate-Cert</DT>
20331 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
20332 This is needed if the server uses self-signed certificates or if Alpine
20333 cannot validate the certificate for some other known reason.
20334 <P>
20335 </DD>
20337 <DT>Anonymous</DT>
20338 <DD>This is a unary parameter (that means it does not have a value)
20339 indicating that the connection be logged in as
20340 "anonymous" rather than a specific user.
20341 Not all servers offer anonymous
20342 access; those which do generally only offer read-only access to certain
20343 "public" folders.
20345 <P>
20346 <CENTER><SAMP>/anonymous</SAMP></CENTER>
20347 <P>
20349 </DD>
20351 <DT>Secure</DT>
20352 <DD>This is a unary parameter indicating that the connection use the
20353 most secure authentication method mutually supported by Alpine and the
20354 server.
20355 Alpine is capable of authenticating connections to
20356 the server using several methods.
20357 By default, Alpine will attempt each
20358 method until either a connection is established or the
20359 list of methods is exhausted.
20360 This parameter causes Alpine to instead fail
20361 the connection if the first (generally most "secure") method fails.
20363 <P>
20364 <CENTER><SAMP>/secure</SAMP></CENTER>
20365 <P>
20367 </DD>
20369 <DT>Submit</DT>
20370 <DD>This is a unary parameter for use with the
20371 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
20372 It indicates that the connection should be made to the Submit server
20373 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
20374 (port 587) instead of the SMTP port (25).
20375 At the time this help was written the submit option was equivalent to
20376 specifying port 587.
20378 <P>
20379 <CENTER><SAMP>/submit</SAMP></CENTER>
20380 <P>
20381 or
20382 <P>
20383 <CENTER><SAMP>host:587</SAMP></CENTER>
20384 <P>
20386 </DD>
20388 <DT>Debug</DT>
20389 <DD>This is a unary parameter indicating that the connection be established
20390 in a verbose mode. Basically, it causes Alpine to log the communication with
20391 the server in Alpine's debug file.
20392 Normally, the pine -d command-line flag would be used instead.
20393 <P>
20394 </DD>
20396 <DT>NoRsh</DT>
20397 <DD>By default, Alpine attempts to login using "rsh",
20398 the UNIX remote shell program.
20399 Including "NoRsh" will cause connections to this server to skip
20400 the "rsh" attempt.
20401 This might be useful to avoid long timeouts caused by rsh firewalls, for
20402 example.
20403 <P>
20404 </DD>
20406 <DT>Loser</DT>
20407 <DD>This option makes sense only for IMAP servers that do not perform
20408 a SEARCH command correctly. If your filtering rules
20409 fail to filter some messages, that should have been filtered, then this
20410 option will make Alpine download all data necessary to perform that search.
20411 There is a performance penalty when using this option. Downloading the
20412 data to perfom the search will take longer than requesting the IMAP
20413 server to perform the filtering, but the filtering will be done correctly.
20414 <P>
20415 </DD>
20418 <DT>Service</DT>
20419 <DD>This parameter requires an associated value. The default value is
20420 "IMAP" which indicates communication with the server based
20421 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20422 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20424 Other service values include:
20425 <DL>
20426 <DT>NNTP</DT>
20427 <DD>This value indicates communication with the server takes place via
20428 the Network News Transfer Protocol. Use this to define a collection
20429 of newsgroups on a remote news server. So
20431 <P>
20432 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20433 <P>
20434 or just
20435 <P>
20436 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20437 <P>
20439 is the way to specify NNTP access.
20440 <P>
20441 </DD>
20443 <DT>POP3</DT>
20444 <DD>This value indicates communication with the server takes place via the
20445 Post Office Protocol 3 protocol.
20447 <P>
20448 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20449 <P>
20450 or just
20451 <P>
20452 <CENTER><SAMP>/POP3</SAMP></CENTER>
20453 <P>
20455 Note that there are several important issues
20456 to consider when selecting this option:
20457 <OL>
20458 <LI> POP3 provides access to only your INBOX. In other words,
20459 secondary folders such as your "saved-messages" are inaccessible.
20460 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20461 model and will leave your mail on the server. Refer to the
20462 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20463 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20464 </OL>
20465 </DD>
20466 </DL>
20467 </DL>
20469 <P>
20470 Note that it is possible to include more than one parameter in a server
20471 specification by concatenating the parameters. For example:
20473 <P>
20474 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20475 <P>
20477 <P>
20478 <End of help on this topic>
20479 </BODY>
20480 </HTML>
20481 ======= h_composer_cntxt_server =======
20482 <HTML>
20483 <HEAD>
20484 <TITLE>Collection Server: Explained</TITLE>
20485 </HEAD>
20486 <BODY>
20487 <H1>Collection Edit Help -- Server Field</H1>
20489 This collection's "Server:" definition indicates the
20490 hostname of the server providing access to the folders in this
20491 collection.
20492 The syntax of this server name is the same as for other server names used
20493 in remote folder names in
20494 Alpine and is described
20495 <A HREF="h_folder_server_syntax">here</A>.
20497 <P>
20498 <End of help on this topic>
20499 </BODY>
20500 </HTML>
20501 ======= h_composer_cntxt_path =======
20502 <HTML>
20503 <HEAD>
20504 <TITLE>Collection Path: Explained</TITLE>
20505 </HEAD>
20506 <BODY>
20507 <H1>Collection Edit Help -- Path Field</H1>
20509 The collection's "Path:" definition indicates the location
20510 of the folders in this collection. If the path or any of its components
20511 do not exist, Alpine will prompt you for their creation when exiting the
20512 Add/Change screen.
20514 <P>
20515 By default the path is interpreted as defining a section of your personal
20516 folder area. This area and how you specify it are defined by the
20517 server, if one is specified in the collection, or, typically, the home
20518 directory if no server is defined.
20520 <P>
20521 To define a collection outside the default "area", prefix
20522 the path with the "namespace" to use when interpreting the
20523 given path. If a namespace is specified, the Path begins with the
20524 sharp, "#", character followed by the name of the namespace
20525 and then the namespace's path-element-delimiter. Aside from the
20526 path's format, namespaces can also imply access rights, content
20527 policy, audience, location, and, occasionally, access methods.
20529 <P>
20530 Each server exports its own set (possibly of size one) of
20531 namespaces. Hence, it's likely communication with your server's
20532 administrator will be required for specific configurations. Some of
20533 the more common namespaces, however, include:
20535 <DL>
20536 <DT>#news.</DT>
20537 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20538 names are hierarchically defined with each level delimited by a period.
20539 </DD>
20540 <DT>#public/</DT>
20541 <DD>This specifies a folder area that the server may export to the general
20542 public.
20543 </DD>
20544 <DT>#shared/</DT>
20545 <DD>This specifies a folder area that the folder may export to groups
20546 of users.
20547 </DD>
20548 <DT>#ftp/</DT>
20549 <DD>This specifies a folder area that is the same as that it may have
20550 exported via the "File Transfer Protocol".
20551 </DD>
20552 <DT>#mh/</DT>
20553 <DD>This specifies the personal folder area associated with folders
20554 and directories that were created using the MH message handling system.
20555 </DD>
20556 </DL>
20557 <P>
20559 In addition, the server may support access to other user's folders,
20560 provided you have suitable permissions. Common methods use a prefix
20561 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20562 indicate the root of the other user's folder area.
20564 <P>
20565 No, nothing's simple.
20567 <P>
20568 <End of help on this topic>
20569 </BODY>
20570 </HTML>
20571 ======= h_composer_cntxt_view =======
20572 <HTML>
20573 <HEAD>
20574 <TITLE>Collection View: Explained</TITLE>
20575 </HEAD>
20576 <BODY>
20577 <H1>Collection Edit Help -- View Field</H1>
20579 The collection's "View:" definition provides a way to limit
20580 the displayed list of folders within a collection. By default, only
20581 folders that contain the specified characters anywhere in their name
20582 are shown in the collection's folder list.
20584 <P>
20585 Additionally, you can use a wildcard character to better control
20586 the list of folders selected for display. The wildcard specifier is
20587 the star, "*", character.
20589 <P>
20590 So, for example, to define a collection of all folders ending with
20591 "c", you'd specify a view of "*c" (without the
20592 quote characters!). Or, similarly, to define a collection of folders
20593 whose names start with "a" and end with "z", you'd
20594 specify a view of "a*z".
20596 <P>
20597 <End of help on this topic>
20598 </BODY>
20599 </HTML>
20600 ======= h_composer_abook_add_server =======
20601 <HTML>
20602 <HEAD>
20603 <TITLE>Addressbook Server Name Field Explained</TITLE>
20604 </HEAD>
20605 <BODY>
20606 This field should be left blank if the address book is stored in a regular
20607 file on this system. If it is a remote address book stored on an IMAP
20608 server then this is the name of that IMAP server.
20609 <P>
20610 Look <A HREF="h_edit_nav_cmds">here</A>
20611 to see the available Editing and Navigation commands.
20612 <P>
20613 <End of help on this topic>
20614 </BODY>
20615 </HTML>
20616 ======= h_composer_abook_add_folder =======
20617 <HTML>
20618 <HEAD>
20619 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20620 </HEAD>
20621 <BODY>
20622 For a remote address book (one for which the Server Name is filled in)
20623 this is the name of a folder on the remote server. The address book data
20624 will be stored in this folder. This folder should be used only for
20625 storing this single address book, not for other address books or for
20626 other messages.
20627 <P>
20628 For a local address book (one for which the Server Name is not filled in)
20629 this is the name of a file in which the address book will be stored.
20630 The file is in the same directory as the Alpine configuration file if the
20631 configuration file is local.
20632 If the configuration file is remote, then this will be in the home directory
20633 for Unix Alpine and in the directory specified by the
20634 "-aux local_directory" command line argument.
20635 <P>
20636 Look <A HREF="h_edit_nav_cmds">here</A>
20637 to see the available Editing and Navigation commands.
20638 <P>
20639 <End of help on this topic>
20640 </BODY>
20641 </HTML>
20642 ======= h_composer_abook_add_nick =======
20643 <HTML>
20644 <HEAD>
20645 <TITLE>Addressbook NickName Field Explained</TITLE>
20646 </HEAD>
20647 <BODY>
20648 This is just an optional nickname for this address book. If present, it
20649 is used in some of the displays and error messages in the address book
20650 maintenance screens. It is for your convenience only and serves no
20651 other purpose.
20652 <P>
20653 Look <A HREF="h_edit_nav_cmds">here</A>
20654 to see the available Editing and Navigation commands.
20655 <P>
20656 <End of help on this topic>
20657 </BODY>
20658 </HTML>
20659 ======= h_composer_qserv_cn =======
20660 <HTML>
20661 <HEAD>
20662 <TITLE>Directory Query Form Explained</TITLE>
20663 </HEAD>
20664 <BODY>
20666 Fill in as many of these fields as you wish to narrow down your
20667 search. All the fields you fill in must match in order for an entry
20668 to be returned. You may use the wildcard character "*" in
20669 any of the fields, it matches any zero or more characters at that
20670 point in the string. There are no implicit wildcards, so the match is
20671 exact unless you include wildcards.
20672 <P>
20674 Note that if an attribute isn't present at all, then the match will fail.
20675 For example, if a server doesn't support the Locality attribute, then no
20676 matter what you put in the Locality field (other than leaving it empty)
20677 the search will fail.
20678 <P>
20680 This field, the Common Name field, is typically a person's full name.
20681 <P>
20683 <H1>EDITING and NAVIGATION COMMANDS</H1>
20684 <!--chtml if pinemode="function_key"-->
20685 <PRE>
20686 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20687 ^B (Left Arrow) Back character | ^D Delete current character
20688 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20689 ^P (Up Arrow) Previous line |
20690 ^N (Down Arrow) Next line | F9 Cut marked text or
20691 ^A Beginning of line | delete current line
20692 ^E End of line | F10 Undelete line(s)
20693 F7 Previous page |
20694 F8 Next page |-------------------------------------
20695 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20696 ----------------------------------------|
20697 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
20698 F2 Cancel | F1 Get help |
20699 F3 Search | ^Z Suspend | ^L Redraw Screen
20700 </PRE>
20701 <!--chtml else-->
20702 <PRE>
20703 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20704 ^B (Left Arrow) Back character | ^D Delete current character
20705 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20706 ^P (Up Arrow) Previous line |
20707 ^N (Down Arrow) Next line | ^K Cut marked text or
20708 ^A Beginning of line | delete current line
20709 ^E End of line | ^U Undelete line(s)
20710 ^Y Previous page |
20711 ^V Next page |-------------------------------------
20712 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20713 ----------------------------------------|
20714 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
20715 ^C Cancel | ^G Get help |
20716 ^X Search | ^Z Suspend | ^L Redraw Screen
20717 </PRE>
20718 <!--chtml endif-->
20719 <P><UL>
20720 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20721 </UL><P>
20722 <End of help on this topic>
20723 </BODY>
20724 </HTML>
20725 ======= h_composer_qserv_sn =======
20727 The Surname is usually the family name of a person.
20729 <End of help on this topic>
20730 ======= h_composer_qserv_gn =======
20732 This is the part of a person's name that isn't the surname or initials.
20734 <End of help on this topic>
20735 ======= h_composer_qserv_mail =======
20737 This is the email address of a person.
20739 <End of help on this topic>
20740 ======= h_composer_qserv_org =======
20742 This is the organization a person belongs to.
20744 <End of help on this topic>
20745 ======= h_composer_qserv_unit =======
20747 This is the organizational unit a person belongs to.
20749 <End of help on this topic>
20750 ======= h_composer_qserv_country =======
20752 This is the country a person belongs to.
20754 <End of help on this topic>
20755 ======= h_composer_qserv_state =======
20757 This is the state a person belongs to.
20759 <End of help on this topic>
20760 ======= h_composer_qserv_locality =======
20762 This is the locality a person belongs to.
20764 <End of help on this topic>
20765 ======= h_composer_qserv_custom =======
20767 This one is for advanced users only! If you put something in this field,
20768 then the rest of the fields are ignored.
20770 This field may be set to the string representation of an LDAP search
20771 filter (see RFC1960). Here are some examples:
20773 To search for an entry with a surname equal to "clinton" you could set
20774 the custom filter to:
20776 (sn=clinton)
20778 This is equivalent to putting "clinton" in the SurName field.
20779 To search for an entry that has a surname that begins with "clint" and
20780 has a givenname equal to "william" you could use:
20782 (&(sn=clint*)(givenname=william))
20784 This is equivalent to setting the SurName field to "clint*" and the
20785 GivenName field to "william".
20786 To search for an entry where either the common name OR the email address
20787 contains "abcde" you could use:
20789 (|(cn=*abcde*)(mail=*abcde*))
20791 That isn't equivalent to anything you can do by setting the other fields
20792 because of the OR.
20794 <End of help on this topic>
20795 ======= h_composer_qserv_qq =======
20797 This one is a little different from the rest of the categories. It causes
20798 a search to be formed from the configured search filter that you filled
20799 in when you added the directory server to your configuration. It can also
20800 be combined with the other fields if you'd like.
20802 <End of help on this topic>
20803 ======= h_address_format =======
20804 <HTML>
20805 <HEAD>
20806 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
20807 </HEAD>
20808 <BODY>
20809 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
20811 A valid email address on the Internet has a username, an "@" sign,
20812 and then a domain, with no spaces.
20813 For example, jsmith@art.example.com might be the email address
20814 of a person
20815 with the username "jsmith" who has an account in the domain
20816 "art.example.com". The number of dot-separated segments on the
20817 right of the "@" sign can vary - a shorter example would be
20818 isabelle@elsewhere.edu (the shortest possible form: here, only the
20819 organization's domain is specified after the "@" sign); a longer
20820 example would be
20821 jsingh@shakti.edutech.example.com
20822 (here, the name of the host "shakti" in the domain
20823 edutech.example.com is also specified).
20824 <P>
20825 If you do not know the exact email address of someone you want to write
20826 to, ask them what it is using other means of communication than email; or
20827 use the tools for
20828 finding people's addresses that are available on the Internet.
20829 <P>
20830 If you are sending to someone on the same system as you are, you can leave
20831 the "@" sign and all the information to its right off of the
20832 address, and Alpine will fill it in automatically,
20833 unless the feature
20834 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
20835 <P>
20837 When an email address you send a message to is not reachable -- either because
20838 it is simply an incorrect address, or because email can temporarily not be
20839 delivered to it due to a technical problem on the way to or at the recipient's
20840 end -- you will almost always get an error notification email message back.
20841 <P>
20842 If you encounter problems with, or have questions about, email delivery or
20843 email address syntax, contact your local network computing consultants.
20844 <P><UL>
20845 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20846 </UL>
20847 <P>
20848 <End of help on this topic>
20849 </BODY>
20850 </HTML>
20851 ======= h_flag_user_flag =======
20852 <HTML>
20853 <HEAD>
20854 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
20855 </HEAD>
20856 <BODY>
20857 <H1>STATUS FLAG: User Defined Keyword</h1>
20859 This is a keyword that is defined for this folder.
20860 It was most likely defined by the owner of the folder.
20861 Alpine will not set or clear this flag on its own.
20863 <P><UL>
20864 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20865 </UL><P>
20866 <End of help on this topic>
20867 </BODY>
20868 </HTML>
20869 ======= h_flag_important =======
20870 <html>
20871 <title>STATUS FLAG: Important</title>
20872 <body>
20873 <h1>STATUS FLAG: Important</h1>
20876 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
20877 MESSAGE INDEX
20878 screen, can only be set by the user, and is intended to be used in
20879 whatever fashion makes sense to you. You are the only one that can set or
20880 clear it.
20882 <P>
20883 <End of help on this topic>
20884 </BODY>
20885 </HTML>
20886 ======= h_flag_new =======
20887 <html>
20888 <title>STATUS FLAG: New</title>
20889 <body>
20890 <h1>STATUS FLAG: New</h1>
20893 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
20894 MESSAGE INDEX screen,
20895 is automatically set when messages are delivered to your Inbox (or other
20896 folder specified outside of Alpine). Likewise, it is cleared automatically
20897 the first time you read the message it is associated with.
20899 <P>
20900 Sometimes it's helpful in prioritizing your mail. For example, perhaps
20901 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
20902 you'd like to be reminded of it next time you read mail. This can be done
20903 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
20906 <P>
20907 <End of help on this topic>
20908 </BODY>
20909 </HTML>
20910 ======= h_flag_answered =======
20911 <html>
20912 <title>STATUS FLAG: Answered</title>
20913 <body>
20914 <h1>STATUS FLAG: Answered</h1>
20916 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
20917 MESSAGE INDEX
20918 screen, is automatically set when you reply to a message. This flag is not
20919 automatically cleared.
20921 <P>
20922 <End of help on this topic>
20923 </BODY>
20924 </HTML>
20925 ======= h_flag_forwarded =======
20926 <html>
20927 <title>STATUS FLAG: Forwarded</title>
20928 <body>
20929 <h1>STATUS FLAG: Forwarded</h1>
20931 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
20932 MESSAGE INDEX
20933 screen, is automatically set when you forward a message. This flag is not
20934 automatically cleared.
20936 <P>
20937 <End of help on this topic>
20938 </BODY>
20939 </HTML>
20940 ======= h_flag_deleted =======
20941 <html>
20942 <title>STATUS FLAG: Deleted</title>
20943 <body>
20944 <h1>STATUS FLAG: Deleted</h1>
20946 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
20947 MESSAGE INDEX
20948 screen, is set when you use the ""D Delete" command.
20949 It is cleared
20950 when you use the "U Undelete" command.
20952 <P>
20953 Messages marked with this flag will be permanently removed from
20954 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
20955 command, or
20956 when you indicate acceptance of their removal upon leaving the folder.
20958 <P>
20959 Note, there can be other actions implicit in the
20960 "D Delete" command,
20961 such as advancing to the next message, that may be momentarily undesirable.
20962 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
20963 flag <A HREF="h_common_flag">explicitly</A>.
20965 <P>
20966 <End of help on this topic>
20967 </BODY>
20968 </HTML>
20969 ====== h_config_incoming_timeo ======
20970 <HTML>
20971 <HEAD>
20972 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
20973 </HEAD>
20974 <BODY>
20975 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
20977 This option has no effect unless the feature
20978 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
20979 is set, which in turn has no effect unless
20980 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
20981 is set.
20982 <P>
20983 Sets the time in seconds that Alpine will
20984 attempt to open a network connection used for monitoring for Unseen
20985 messages in Incoming Folders. The default is 5.
20986 If a connection has not completed within this many seconds Alpine will
20987 give up and consider it a failed connection.
20988 <P>
20989 <UL>
20990 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
20991 </UL><P>
20992 <End of help on this topic>
20993 </BODY>
20994 </HTML>
20995 ====== h_config_psleep ======
20996 <HTML>
20997 <HEAD>
20998 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
20999 </HEAD>
21000 <BODY>
21001 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
21003 <P>
21004 In the good old days a mailcap viewer was used to examine an
21005 attachment before saving it, and after viewing the attachment control
21006 would return to the operating system when the viewer was closed. Therefore,
21007 when the mailcap viewer returned control to the operating system, it
21008 could be assumed that the user who opened the attachment was done
21009 examining it, and the copy of the attachment that was used, could be removed.
21011 <P>
21012 However, today this assumption is not longer valid. Some viewers return
21013 control to the operating system before they actually read the attachment
21014 to be examined. This causes Alpine to delete the attachment before it
21015 is read by the viewer, causing the viewer to fail opening the attachment.
21017 <P>
21018 In order to work around this problem, Alpine checks, after the viewer has
21019 returned control to the operating system, if there is any process that is
21020 using the attachment. This variable controls the number of seconds that
21021 must elapse between checks. Once it is found that no process is using the
21022 attachment, this is removed.
21024 <P>
21025 The minimum value for this variable is 60 (checks will be made once per
21026 minute), and the maximum value is 600 (checks will be made once every 10
21027 minutes). The default value is 60.
21029 <P>
21030 <UL>
21031 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21032 </UL><P>
21033 <End of help on this topic>
21034 </BODY>
21035 </HTML>
21036 ====== h_config_incoming_interv ======
21037 <HTML>
21038 <HEAD>
21039 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
21040 </HEAD>
21041 <BODY>
21042 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
21044 This option has no effect unless the feature
21045 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21046 is set, which in turn has no effect unless
21047 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21048 is set.
21049 <P>
21050 This option specifies, in seconds, how often Alpine will check
21051 for new mail and state changes in Incoming Folders when Incoming Folders
21052 Checking is turned on.
21053 The default is 3 minutes (180).
21054 This value applies only to folders that are local to the system that
21055 Alpine is running on or that are accessed using the IMAP protocol.
21056 The similar option
21057 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
21058 applies to all other monitored folders.
21059 <P>
21060 <UL>
21061 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21062 </UL><P>
21063 <End of help on this topic>
21064 </BODY>
21065 </HTML>
21066 ====== h_config_incoming_second_interv ======
21067 <HTML>
21068 <HEAD>
21069 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
21070 </HEAD>
21071 <BODY>
21072 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
21074 This option has no effect unless the feature
21075 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21076 is set, which in turn has no effect unless
21077 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21078 is set.
21079 <P>
21080 This option together with the option
21081 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21082 specifies, in seconds, how often Alpine will check
21083 for new mail and state changes in Incoming Folders when Incoming Folders
21084 Checking is turned on.
21085 The default for this option is 3 minutes (180).
21086 For folders that are local to this system or
21087 that are accessed using the IMAP protocol
21088 the value of the option
21089 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21090 is used.
21091 For all other monitored folders, the value of this option is used.
21092 <P>
21093 The reason there are two separate options is because it is usually
21094 less expensive to check local and IMAP folders than it is to check
21095 other types, like POP or NNTP folders.
21096 You may want to set this secondary value to a higher number than
21097 the primary check interval.
21098 <P>
21099 <UL>
21100 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21101 </UL><P>
21102 <End of help on this topic>
21103 </BODY>
21104 </HTML>
21105 ====== h_config_incoming_list ======
21106 <HTML>
21107 <HEAD>
21108 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
21109 </HEAD>
21110 <BODY>
21111 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
21113 This option has no effect unless the feature
21114 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21115 is set, which in turn has no effect unless
21116 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21117 is set.
21118 <P>
21119 When monitoring the Incoming Message Folders for Unseen messages Alpine will
21120 normally monitor all Incoming Folders.
21121 You may use this option to restrict the list of monitored folders to a
21122 subset of all Incoming Folders.
21123 <P>
21124 <UL>
21125 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21126 </UL><P>
21127 <End of help on this topic>
21128 </BODY>
21129 </HTML>
21130 ====== h_config_pers_name ======
21131 <HTML>
21132 <HEAD>
21133 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
21134 </HEAD>
21135 <BODY>
21136 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
21138 This value is used to determine the full name part of the "From" address
21139 on messages you send.
21140 <!--chtml if pinemode="os_windows"-->
21141 PC-Alpine requires that this be set in order to properly construct the "From" address.
21142 <!--chtml else-->
21143 If unset, Unix Alpine will obtain your full name from
21144 the system password file. PC-Alpine, on the other hand, requires that this be set.
21145 <!--chtml endif-->
21146 <P>
21147 If you want to change the value of what gets included in the From header
21148 in messages you send (other than just the Personal Name)
21149 look <A HREF="h_config_change_your_from">here</A> for a description.
21150 <P><UL>
21151 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21152 </UL><P>
21153 <End of help on this topic>
21154 </BODY>
21155 </HTML>
21156 ====== h_config_pruned_folders ======
21157 <html>
21158 <header>
21159 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
21160 </header>
21161 <body>
21162 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
21164 This variable allows you to define a list of one or more folders that
21165 Alpine will offer to prune for you in the same way it automatically offers
21166 to prune your "sent-mail" folder each month.
21167 Each folder in this list must be a folder in your default folder collection
21168 (the first folder collection if you have more than one), and it is just
21169 the relative name of the folder in the collection, not the fully-qualified name.
21170 It is similar to sent-mail.
21171 Instead of something like
21172 <P>
21173 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
21174 <P>
21175 the correct value to use would be
21176 <P>
21177 <CENTER><SAMP>folder</SAMP></CENTER>
21178 <P>
21179 There is an assumption here that your first collection is the folders in
21180 <P>
21181 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
21182 <P>
21184 Once a month, for each folder listed, Alpine will offer to move
21185 the contents of the folder to a new folder of the same name but with
21186 the previous month's date appended. Alpine will then look for any such
21187 date-appended folder names created for a previous month, and offer each
21188 one it finds for deletion.
21189 <P>
21191 If you decline the first offer, no mail is moved and no new folder is
21192 created.
21193 <P>
21195 The new folders will be created
21196 in your default folder collection.
21197 <P>
21199 <UL>
21200 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21201 </UL><P>
21202 <End of help on this topic>
21203 </body>
21204 </html>
21205 ====== h_config_upload_cmd ======
21206 <HTML>
21207 <HEAD>
21208 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
21209 </HEAD>
21210 <BODY>
21211 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
21213 This option affects the behavior of the Composer's "Read File"
21214 (^R in the message body) and "Attach File" (^J in the header)
21215 commands. It specifies
21216 a Unix program name, and any necessary command line arguments, that Alpine can
21217 use to transfer files from your personal computer into messages that you are
21218 composing.<P>
21220 <B>Note:</B> this facility is intended for use with serial line transfer
21221 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21222 to work with TCP/IP file transfer programs such as ftp.<P>
21224 If a program is specified, the commands listed above are modified to offer a
21225 subcommand (^Y) to activate the transfer. Obviously, the Unix program
21226 specified here must match the transfer program or protocol available on the
21227 personal computer.<P>
21229 Alpine expects to exchange uploaded data via a file on your Unix system. When
21230 the specified upload program finishes, Alpine expects the uploaded data to be
21231 contained in this file.<P>
21233 When upload is invoked via the "Read File" subcommand, Alpine
21234 generates a
21235 temporary file name that it will pass to the specified Unix program. Alpine
21236 will read the resulting uploaded text from this file and then delete it when
21237 the upload command is finished.<P>
21239 When upload is invoked via the "Attach File" subcommand, Alpine will
21240 prompt
21241 you for the name of the file that is to contain the uploaded information that
21242 it is to attach. Alpine will attach this file to the composition, but will
21243 <B>not</B> delete this file after the upload command is finished.<P>
21245 The special token "_FILE_" may be included among the Unix program's
21246 command
21247 line arguments. Alpine will replace this symbol with the name of the file
21248 being used to exchange the uploaded information. This token allows you to
21249 position the file name where it is required in the Unix program's command
21250 line arguments.<P>
21252 If the "_FILE_" token is not present in the specified command, the
21253 temporary file's name is automatically appended to the specified Unix
21254 program. In other words, you don't need to use "_FILE_" if it is the
21255 <B>last</B> command line argument.
21256 <P><UL>
21257 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21258 </UL><P>
21259 <End of help on this topic>
21260 </BODY>
21261 </HTML>
21262 ====== h_config_upload_prefix ======
21263 <HTML>
21264 <HEAD>
21265 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
21266 </HEAD>
21267 <BODY>
21268 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
21270 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
21271 It defines text to be written to the terminal emulator (via standard output)
21272 immediately prior to starting upload command. This is useful for
21273 integrated serial line file transfer agents that permit command passing
21274 (e.g., Kermit's APC method).<P>
21276 The special token "_FILE_" may be included in the string specification.
21277 That symbol will be replaced with the (Alpine-created) name of the temporary
21278 file in which Alpine will expect to find the uploaded file.
21279 <P><UL>
21280 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21281 </UL><P>
21282 <End of help on this topic>
21283 </BODY>
21284 </HTML>
21285 ====== h_config_download_cmd ======
21286 <HTML>
21287 <HEAD>
21288 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
21289 </HEAD>
21290 <BODY>
21291 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
21293 This option affects the behavior of the Export command. It specifies a Unix
21294 program name, and any necessary command line arguments, that Alpine can use to
21295 transfer the exported message to your personal computer's disk.<P>
21296 Note: this facility is intended for use with serial line transfer
21297 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21298 to work with TCP/IP file transfer programs such as ftp.<P>
21299 If a program is specified, the Export command is modified to offer a
21300 subcommand (^V) to activate the transfer (in lieu of saving it to
21301 the machine where Alpine is running). Obviously, the Unix program
21302 specified here must match the transfer program or protocol available on the
21303 personal computer.<P>
21305 When this subcommand is selected and before Alpine invokes the specified Unix
21306 program, Alpine will create a temporary file containing the text of the
21307 exported message. Alpine uses this file to pass the exported message text to
21308 the specified Unix program.<P>
21310 The special token "_FILE_" may be included among the Unix program's command
21311 line arguments. Alpine will replace this symbol with the temporary file's name
21312 before executing the Unix program. This token allows you to position the
21313 file name where it is required in the Unix program's command line arguments.
21314 <P>
21315 If the "_FILE_" token is not present in the specified command, the
21316 temporary file's name is automatically appended to the specified Unix
21317 program. In other words, you don't need to use "_FILE_" if it is the
21318 <B>last</B> command line argument.
21319 <P><UL>
21320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21321 </UL><P>
21322 <End of help on this topic>
21323 </BODY>
21324 </HTML>
21325 ====== h_config_download_prefix ======
21326 <HTML>
21327 <HEAD>
21328 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
21329 </HEAD>
21330 <BODY>
21331 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
21333 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
21334 It defines text to be written to the terminal emulator (via standard output)
21335 immediately prior to starting the download command. This is useful for
21336 integrated serial line file transfer agents that permit command passing
21337 (e.g., Kermit's APC method).
21338 <P>
21339 The special token "_FILE_" may be included in the string
21340 specification.
21341 That symbol will be replaced with the (Alpine-created) name of the temporary
21342 file into which Alpine will place the message to be downloaded.
21343 <P><UL>
21344 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21345 </UL><P>
21346 <End of help on this topic>
21347 </BODY>
21348 </HTML>
21349 ====== h_config_mailcap_path ======
21350 <HTML>
21351 <HEAD>
21352 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
21353 </HEAD>
21354 <BODY>
21355 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
21356 This variable is used to replace Alpine's default mailcap file search path.
21357 It takes one or more file names (full paths must be specified) in which to
21358 look for mail capability data. The default search path can be found in this
21359 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
21360 If there is more than one file name listed, list members should be delimited
21361 by
21362 <!--chtml if pinemode="os_windows"-->
21363 a semi-colon (;) under Windows; for example:<PRE>
21364 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
21365 </PRE>
21366 <!--chtml else-->
21367 a colon (:) under UNIX; for example:<PRE>
21368 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
21369 </PRE>
21370 <!--chtml endif-->
21371 <P><UL>
21372 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21373 </UL>
21374 <P>
21375 <End of help on this topic>
21376 </BODY>
21377 </HTML>
21378 ====== h_config_mimetype_path ======
21379 <HTML>
21380 <HEAD>
21381 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21382 </HEAD>
21383 <BODY>
21384 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21386 This variable is used to replace Alpine's default mime.types file search path.
21387 It takes one or more file names (full paths must be specified) in which to
21388 look for file-name-extension to MIME type mapping data. The default search
21389 path can be found in this
21390 <A HREF="h_news_config">Alpine Configuration</A> help.
21392 <P>
21394 If there is more than one file name listed, list members should be delimited
21395 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21396 <P>
21397 <End of help on this topic>
21398 </BODY></HTML>
21399 ====== h_config_set_att_ansi ======
21400 <HTML><HEAD>
21401 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21402 </HEAD>
21403 <BODY>
21404 <H1>OPTION: Set printer to attached ansi printer</H1>
21406 Type "S" to set your printer to "attached-to-ansi".<BR>
21407 It is OK to include "attached-to-ansi" in your personal list below.
21408 <P>
21409 <End of help on this topic>
21410 </BODY></HTML>
21411 ====== h_config_set_att_ansi2 ======
21412 <HTML><HEAD>
21413 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21414 </HEAD>
21415 <BODY>
21416 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21418 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21419 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21420 list below.
21422 <P>
21424 This is the same as the "attached-to-ansi" option except that a
21425 formfeed character will not be appended to the end of the print job.
21426 If your printer already ejects the paper by itself at the end of the
21427 job, you may prefer the "no-formfeed" form of this printer so that you
21428 don't get an extra blank page between print jobs.
21429 <P>
21431 <End of help on this topic>
21432 </BODY></HTML>
21433 ====== h_config_set_att_wyse ======
21434 <HTML><HEAD>
21435 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21436 </HEAD>
21437 <BODY>
21438 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21440 Type "S" to set your printer to "attached-to-wyse".<BR>
21441 It is OK to include "attached-to-wyse" in your personal list below.
21442 <P>
21443 This is very similar to "attached-to-ansi".
21444 The only difference is in the control characters sent to turn the printer
21445 on and off.
21446 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21447 to turn on the printer and ESC LEFT_BRACKET 4 i
21448 to turn it off.
21449 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21450 <End of help on this topic>
21451 </BODY></HTML>
21452 ====== h_config_set_att_wyse2 ======
21453 <HTML><HEAD>
21454 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21455 </HEAD>
21456 <BODY>
21457 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21459 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21460 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21461 list below.
21463 <P>
21465 This is the same as the "attached-to-wyse" option except that a
21466 formfeed character will not be appended to the end of the print job.
21467 If your printer already ejects the paper by itself at the end of the
21468 job, you may prefer the "no-formfeed" form of this printer so that you
21469 don't get an extra blank page between print jobs.
21470 <P>
21472 <End of help on this topic>
21473 </BODY></HTML>
21474 ====== h_config_set_stand_print ======
21475 <HTML>
21476 <HEAD>
21477 <TITLE>OPTION: Set default printer</TITLE>
21478 </HEAD>
21479 <H1>OPTION: Set default printer</H1>
21480 <BODY>
21481 Move to the printer you want and type "S" to set it to be your
21482 default printer. This list is not modifiable by you and has been
21483 set up by the system administrators. If there is more than one printer
21484 listed in the Command List, you will be able to cycle through that
21485 whole list at the time you print, starting with your default.
21486 It is OK to include entries from this Standard list in your personal
21487 list below.
21488 <P>
21489 <End of help on this topic>
21490 </BODY>
21491 </HTML>
21492 ====== h_config_set_custom_print ======
21493 <HTML>
21494 <HEAD>
21495 <TITLE>OPTION: Set default printer</TITLE>
21496 </HEAD>
21497 <H1>OPTION: Set default printer</H1>
21498 <BODY>
21499 You may add as many print commands as you want to your personal list.
21500 Specify one of them as your default printer by moving to the printer
21501 you want and typing "S". If there is more than one printer listed
21502 in the Command List, you will be able to cycle through that list at
21503 the time you print, starting with your default. It is OK to include
21504 entries from the Standard list above or to include the command
21505 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21506 "attached-to-wyse-no-formfeed" as one of the entries here.
21507 <P>
21508 <End of help on this topic>
21509 </BODY>
21510 </HTML>
21511 ====== h_config_user_id =====
21512 <HTML>
21513 <HEAD>
21514 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21515 </HEAD>
21516 <BODY>
21517 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21519 This value is used as part of the "From" address on messages you send.
21520 It is also the default login name for remote IMAP server access. Set this
21521 to the username part you want to appear on outgoing email.
21522 <P>
21523 If you want to change the value of what gets included in the From header
21524 in messages you send (other than just the User ID)
21525 look <A HREF="h_config_change_your_from">here</A> for a description.
21527 <P><UL>
21528 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21529 </UL><P>
21530 <End of help on this topic>
21531 </BODY>
21532 </HTML>
21533 ====== h_config_user_dom =====
21534 <HTML>
21535 <HEAD>
21536 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21537 </HEAD>
21538 <BODY>
21539 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21541 This value specifies the domain part (right-hand side) of your return
21542 address on outgoing email and is also used as the default domain for email
21543 composed to a local user.
21544 <!--chtml if pinemode="os_windows"-->
21545 This value is required for PC-Alpine. If you are unsure as to what this should be,
21546 contact your local help desk, system administrator, or Internet Service Provider.
21547 <!--chtml else-->
21548 If unset, Unix Alpine will obtain the domain from
21549 the system. Often this value will be set for your whole site by the
21550 system administrator.<P>
21551 <!--chtml endif-->
21552 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21553 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21554 <P>
21555 If you want to change the value of what gets included in the From header
21556 in messages you send (other than just the User Domain)
21557 look <A HREF="h_config_change_your_from">here</A> for a description.
21558 <P><UL>
21559 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21560 </UL><P>
21561 <End of help on this topic>
21562 </BODY>
21563 </HTML>
21564 ====== h_config_smtp_server =====
21565 <HTML>
21566 <HEAD>
21567 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21568 </HEAD>
21569 <BODY>
21570 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21571 This value specifies the name of one or more SMTP
21572 (Simple Mail Transfer Protocol) servers for sending mail.
21573 <!--chtml if pinemode="os_windows"-->
21574 You must have an SMTP server for use with PC-Alpine.
21575 SMTP servers are
21576 normally set up by a system administrator for use by all members of a given
21577 campus or department.
21578 Contact your local help desk to ask what SMTP
21579 servers you should use.
21580 <!--chtml else-->
21581 Unix Alpine users may not need to set an SMTP server.
21582 Alpine will attempt to execute the program (usually sendmail) that is used
21583 to insert mail into the mail system.
21584 If this works for you, you may leave this option blank.
21585 If there is an SMTP server running on the Unix host you may be able to
21586 improve sending performance slightly by setting the SMTP server option
21587 to "localhost" or to the actual name of the Unix host.
21588 <P>
21589 If the Unix host doesn't work the way Alpine was expecting you will need to
21590 set the value of this option.
21591 SMTP servers are
21592 normally set up by a system administrator for use by all members of a given
21593 campus or department.
21594 Contact your local help desk to ask what SMTP
21595 servers you should use.
21596 <!--chtml endif-->
21597 <P>
21598 Your SMTP server may offer SMTP AUTH authentication.
21599 It may even require it.
21600 If your SMTP server offers SMTP AUTH authentication you may specify a
21601 "user" name parameter to cause Alpine to attempt to authenticate.
21602 This parameter requires an associated value,
21603 the username identifier with which to establish the server
21604 connection.
21605 An example might be:
21607 <P>
21608 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21609 <P>
21611 If AUTH authentication is offered by the server, this will cause Alpine to
21612 attempt to use it.
21613 If AUTH authentication is not offered by the server, this will cause Alpine
21614 to fail sending with an error similar to:
21616 <P>
21617 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21618 <P>
21620 Another type of authentication that is used by some ISPs is called
21621 "POP before SMTP" or "IMAP before SMTP",
21622 which means that you have to authenticate
21623 yourself to the POP or IMAP server by opening a mailbox before you
21624 can send mail.
21625 To do this, you usually only have to open your INBOX.
21627 <P>
21628 You may tell Alpine to use the
21629 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21630 port (587) instead of the SMTP port (25) by including the "submit"
21631 parameter
21632 in this option.
21633 At this time "/submit" is simply equivalent to specifying
21634 port 587, though it may imply more than that at some point in the future.
21635 Some ISPs are blocking port 25 in order to reduce the amount of spam
21636 being sent to their users.
21637 You may find that the submit option allows you to get around such a block.
21639 <P>
21640 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21641 <P>
21643 To specify any non-standard port number on the SMTP server you may follow
21644 the hostname with a colon followed by the portnumber.
21646 <P>
21647 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21648 <P>
21650 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21651 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21652 If that fails then a non-encrypted connection will be attempted instead.
21653 You may specify that a TLS connection is required if you wish.
21654 If you append "/tls" to the name then the connection will fail
21655 instead of falling back to a non-secure connection.
21657 <P>
21658 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
21659 <P>
21662 For more details about server name possibilities see
21663 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21664 <P>
21666 <UL>
21667 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21668 </UL>
21669 <P>
21670 <End of help on this topic>
21671 </BODY>
21672 </HTML>
21673 ====== h_config_nntp_server =====
21674 <HTML>
21675 <HEAD>
21676 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
21677 <BODY>
21678 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
21680 This value specifies the name of one or more NNTP
21681 (Network News Transfer Protocol)
21682 servers for reading and posting USENET news.
21683 NNTP servers are normally
21684 set up by a system administrator for use by all members of a given campus
21685 or department.
21686 Contact your local help desk to ask what NNTP servers you should use.
21687 <!--chtml if pinemode="os_windows"--><!--chtml else-->
21688 Often Unix Alpine users will find that this variable has been
21689 set for the whole system (and they don't have to worry about it).
21690 <!--chtml endif-->
21691 When you define an NNTP server here, Alpine implicitly defines a news
21692 collection for you, assuming that server as the news server and assuming
21693 that you will use the NNTP protocol and a local newsrc configuration file
21694 for reading news.
21695 For more about reading news with Alpine, see
21696 <A HREF="h_reading_news">how to use Alpine to read news</A>.
21697 <P>
21698 Your NNTP server may offer NNTP "AUTHINFO SASL"
21699 or "AUTHINFO USER" authentication.
21700 It may even require it.
21701 If your NNTP server does offer such authentication you may specify a user name
21702 parameter to cause Alpine to attempt to authenticate.
21703 The same is true for the server name in a folder collection that uses NNTP.
21704 This parameter requires an associated value,
21705 the username identifier with which to establish the server connection.
21706 An example might be:
21708 <P>
21709 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
21710 <P>
21712 If authentication is offered by the server, this will cause Alpine to
21713 attempt to use it.
21714 If authentication is not offered by the server, this will cause Alpine
21715 to fail with an error similar to:
21717 <P>
21718 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
21719 <P>
21720 For more details about the server name possibilities see
21721 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21722 <P><UL>
21723 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21724 </UL><P>
21725 <End of help on this topic>
21726 </BODY>
21727 </HTML>
21728 ====== h_config_inbox_path =====
21729 <HTML>
21730 <HEAD>
21731 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
21732 </HEAD>
21733 <BODY>
21734 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
21736 This value overrides the default value of your INBOX name/path/location.
21737 <!--chtml if pinemode="os_windows"-->
21738 PC-Alpine users must specify an inbox path and it must be a folder on an
21739 IMAP server.
21740 <!--chtml else-->
21741 Unix and VMS Alpine users will often find that this variable
21742 has been pre-configured by your system administrator.
21743 <!--chtml endif-->
21744 You may be able to specify an alternate INBOX that is either a local folder
21745 or a folder on an IMAP server.
21746 <P>
21747 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
21748 where "monet.art.example.com" is replaced by the name of your IMAP
21749 mail server.
21750 <P>
21751 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21752 details on the syntax of folder definitions.
21753 <P>
21754 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
21755 mail is disappearing.
21756 <P><UL>
21757 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21758 </UL><P>
21759 <End of help on this topic>
21760 </BODY>
21761 </HTML>
21762 ====== h_config_change_your_from =====
21763 <HTML>
21764 <HEAD>
21765 <TITLE>How to Change your From Address</TITLE>
21766 </HEAD>
21767 <BODY>
21768 <H1>How to Change your From Address</H1>
21770 If the From address that Alpine includes in mail that you send is not correct,
21771 you may want to configure a different default value for the From address.
21772 You may follow these directions to change the default:
21774 <P>
21775 <UL>
21776 <LI> Go to the Main Alpine Menu
21777 <LI> From there type the Setup Command
21778 <LI> From there type the Config Command
21779 </UL>
21781 <P>
21782 You've probably already seen this SETUP CONFIGURATION screen.
21783 If not, there are many options you may want to set here.
21784 To set the value of the From header you may use the
21785 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
21786 Find it by scrolling down a few pages or use the WhereIs command to
21787 search for "customized".
21788 You may want to read the help text associated with the option.
21789 <P>
21790 To add a custom From header, type the Add command and enter the
21791 full header line, including the leading "From: ".
21792 For example:
21793 <P>
21794 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
21795 <P>
21796 Now exit the Setup command and try sending mail to yourself to see
21797 what the From line looks like.
21798 <P>
21799 When you are in the composer you may edit the custom From line by typing
21800 Ctrl-R while your cursor is in the headers of the message and then moving
21801 to the From line and editing.
21802 If you want to leave the default value the same but add the possibility
21803 of being able to edit the header when you compose, add just the header
21804 name without a value.
21805 For example:
21806 <P>
21807 <CENTER><SAMP>From:</SAMP></CENTER>
21808 <P>
21809 If you change your From address you may also find it useful to add the
21810 changed From address to the
21811 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
21812 configuration option.
21813 <P>
21814 <UL>
21815 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21816 </UL><P>
21817 <End of help on this topic>
21818 </BODY>
21819 </HTML>
21820 ====== h_config_default_fcc =====
21821 <HTML>
21822 <HEAD>
21823 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
21824 </HEAD>
21825 <BODY>
21826 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
21828 This value specifies where a copy of outgoing mail should be saved. If
21829 this is not a path name, it will be in the default collection for saves.
21830 Any valid folder specification, local or IMAP, is allowed. This default
21831 folder carbon copy only applies when the
21832 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
21833 is set to use the default folder.
21834 <!--chtml if pinemode="os_windows"-->
21835 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
21836 <!--chtml else-->
21837 Unix Alpine default
21838 is normally "sent-mail" in the default folder collection.
21839 <!--chtml endif-->
21840 <P>
21841 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
21842 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
21843 IMAP server (remember that in order to later access this remote folder through Alpine, it
21844 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21845 for more information). An example:<p>
21846 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
21847 <P>
21848 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
21849 <P>
21850 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21851 details on the syntax of folder definitions.
21852 <P>
21853 <UL>
21854 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21855 </UL><P>
21856 <End of help on this topic>
21857 </BODY>
21858 </HTML>
21859 ====== h_config_def_save_folder =====
21860 <HTML>
21861 <HEAD>
21862 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
21863 </HEAD>
21864 <BODY>
21865 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
21867 This option determines the default folder name for save-message operations
21868 ("saves").
21869 <P>
21870 If this is not a path name, it will be in the default collection for saves.
21871 Any valid folder specification, local or IMAP, is allowed. This default
21872 folder only applies when the
21873 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
21874 doesn't override it.
21875 <!--chtml if pinemode="os_windows"-->
21876 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
21877 <!--chtml else-->
21878 Unix Alpine default
21879 is normally "saved-messages" in the default folder collection.
21880 <!--chtml endif-->
21881 If you access your email through an IMAP server, especially if you often switch between Unix
21882 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
21883 IMAP server (remember that in order to later access this remote folder through Alpine, it
21884 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
21885 for more information). An example:<p>
21886 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
21887 <P>
21888 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21889 details on the syntax of folder definitions.
21890 <P>
21891 <UL>
21892 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21893 </UL><P>
21894 <End of help on this topic>
21895 </BODY>
21896 </HTML>
21897 ====== h_config_postponed_folder =====
21898 <HTML>
21899 <HEAD>
21900 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
21901 </HEAD>
21902 <BODY>
21903 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
21905 This value overrides the default name for the folder where postponed
21906 messages are saved. If this is not a path name, it will be in the default
21907 collection for message Saves. Any valid folder specification, local or
21908 remote, is allowed.
21909 PC-Alpine default
21910 is "POSTPOND" (stored as POSTPOND.MTX).
21911 The Unix Alpine default is normally "postponed-msgs"
21912 in the default collection.
21913 <P>
21914 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
21915 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
21916 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
21917 in all Alpine copies you use.
21918 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
21919 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
21920 for more information). An
21921 example:<p>
21922 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
21923 <P>
21924 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21925 details on the syntax of folder definitions.
21926 <P>
21927 <UL>
21928 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21929 </UL><P>
21930 <End of help on this topic>
21931 </BODY>
21932 </HTML>
21933 ====== h_config_read_message_folder =====
21934 <HTML>
21935 <HEAD>
21936 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
21937 </HEAD>
21938 <BODY>
21939 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
21941 By virtue of specifying a folder name here, Alpine will be configured to
21942 save all messages that you have read during a session into the designated
21943 "read messages" folder. This allows you to more easily distinguish
21944 between your really new email (in your INBOX) and those that you have
21945 already read. Depending on how you define the
21946 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
21947 setting, you may or may not be asked when you quit
21948 Alpine if you want read messages to be moved to this folder. In either
21949 case, moving the messages means they will be deleted from your INBOX.
21950 <P>
21951 If this is not a path name, it will be in the default collection for
21952 saves. Any valid folder specification, local or remote (via IMAP), is
21953 allowed. There is no default for the name of the read message folder.
21954 <P>
21955 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
21956 details on the syntax of folder definitions.
21957 <P>
21958 <UL>
21959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21960 </UL><P>
21961 <End of help on this topic>
21962 </BODY>
21963 </HTML>
21964 ====== h_config_form_folder =====
21965 <HTML>
21966 <HEAD>
21967 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
21968 </HEAD>
21969 <BODY>
21970 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
21972 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
21973 contain messages that you have composed and that are intended to be
21974 sent in their original form repeatedly.
21976 <P>
21977 Setting this variable will alter Alpine's usual behavior when you
21978 execute the Compose command. Normally, Alpine offers a chance to
21979 continue a postponed or interrupted message should one or the other
21980 exist. When this variable is set to a folder name that exists, Alpine
21981 will also offer the chance to select a message from the folder to
21982 insert into the composer (much like when continuing a postponed message).
21983 The difference, however, is that Alpine will not automatically delete
21984 the selected message from the Form Letter Folder.
21985 <P>
21986 Setting this variable will also affect Alpine's behavior when you
21987 Postpone a message from the composer. Normally, Alpine simply stashes
21988 the message away in your
21989 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
21990 Regardless of the specified folder's existence, Alpine will ask which
21991 folder you intend the message to be stored in. Choose the
21992 "F" option to store the message in your Form Letter Folder.
21993 This is the most common way to add a message to the folder.
21995 <P>
21996 Another method of adding messages to the folder is via the Alpine
21997 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
21998 you expect to send in the same form again, you can enter the Form
21999 Letter Folder's name in this field. Alpine, as usual, will copy the
22000 message as it's sent. Note, when you later select this message from
22001 your Form Letter Folder, it will have the same recipients as the original
22002 message.
22004 <P>
22005 To delete a message from the Form Letter Folder, you can either select
22006 the folder from a suitable FOLDER LIST screen, or use the Delete
22007 command in the MESSAGE INDEX offered when selecting from the folder as
22008 part of the Compose command. You can delete a Form Letter Folder just
22009 as any other folder from a suitable FOLDER LIST screen.
22011 <P>
22012 You may find that the <A HREF="h_rules_roles">"Roles"</A>
22013 facility can be used
22014 to replace the Form Letter Folder.
22016 <P>
22017 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22018 details on the syntax of folder definitions.
22020 <P>
22021 <UL>
22022 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22023 </UL><P>
22024 <End of help on this topic>
22025 </BODY>
22026 </HTML>
22027 ====== h_config_archived_folders =====
22028 <HTML>
22029 <HEAD>
22030 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
22031 </HEAD>
22032 <BODY>
22033 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
22035 This is like
22036 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
22037 only more general. You may archive
22038 any of the folders in your incoming collection. This is a list of folder
22039 pairs, with the first separated from the second in the pair by a space.
22040 The first folder in a pair is the folder you want to archive, and the
22041 second folder is the folder that read messages from the first should be
22042 moved to. Depending on how you define the
22043 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22044 setting, you may or may not be asked when you
22045 leave the first folder if you want read messages to be moved to the
22046 second folder. In either case, moving the messages means they will be
22047 deleted from the first folder.
22048 <P>
22049 The name of the first folder in each pair can be either the technical
22050 specification of the folder (like what appears in your configuration file)
22051 or (much easier) the nickname that you gave the folder when you made it
22052 an incoming folder.
22053 <p>
22054 For example:<p>
22055 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
22056 <p>or, using nicknames:<p>
22057 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
22058 <P>
22059 If these are not path names, they will be in the default collection for
22060 saves. Any valid folder specification, local or remote (via IMAP), is
22061 allowed. There is no default.
22062 <P>
22063 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22064 details on the syntax of folder definitions.
22065 <P>
22066 <UL>
22067 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22068 </UL><P>
22069 <End of help on this topic>
22070 </BODY>
22071 </HTML>
22072 ====== h_config_newsrc_path ======
22073 <HTML>
22074 <HEAD>
22075 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
22076 </HEAD>
22077 <BODY>
22078 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
22080 This option overrides the default name Alpine uses for your "newsrc" news
22081 status and subscription file. If set, Alpine will take this value as the
22082 full pathname for the desired newsrc file.<P>
22084 If this option is <B>not</B> set,
22085 <!--chtml if pinemode="os_windows"-->
22086 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
22087 of the current drive, e.g. "C:\") and then it looks in the same
22088 directory as your pinerc file for NEWSRC.
22089 <!--chtml else-->
22090 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
22091 your account's home directory).
22092 <!--chtml endif-->
22093 <P><UL>
22094 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22095 </UL>
22096 <P>
22097 <End of help on this topic>
22098 </BODY>
22099 </HTML>
22100 ====== h_config_literal_sig =====
22101 <HTML>
22102 <HEAD>
22103 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
22104 </HEAD>
22105 <BODY>
22106 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
22108 With this option your actual signature, as opposed to
22109 the name of a file containing your signature,
22110 is stored in the Alpine configuration file.
22111 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
22112 <P>
22114 This is simply a different way to store the signature.
22115 The signature is stored inside your Alpine configuration file instead of in
22116 a separate file.
22117 Tokens work the same way they do with the
22118 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
22119 help.
22120 <P>
22122 The Setup/Signature command on Alpine's MAIN MENU will edit
22123 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
22124 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
22125 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
22126 instead.
22127 <P>
22129 The two character sequence \n (backslash followed by
22130 the character n) will be used to signify a line-break in your signature.
22131 You don't have to enter the \n, but it will be visible in the
22132 SETUP CONFIGURATION window after you are done editing the signature.
22134 <P>
22135 <UL>
22136 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22137 </UL><P>
22138 <End of help on this topic>
22139 </BODY>
22140 </HTML>
22141 ====== h_config_signature_file =====
22142 <HTML>
22143 <HEAD>
22144 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
22145 </HEAD>
22146 <BODY>
22147 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
22149 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
22150 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
22151 You can tell that that is the case because the value of the
22152 "<!--#echo var="VAR_signature-file"-->" will show up as
22153 <P>
22154 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
22155 <P>
22156 You may either use all Literal Signatures (signatures stored in your
22157 configuration file) throughout Alpine, or all signature files.
22158 You can't mix the two.
22159 <P>
22160 This is the name of a file that will be automatically inserted into
22161 outgoing messages.
22162 It typically contains information such as your
22163 name, email address and organizational affiliation.
22164 Alpine adds the
22165 signature into the message as soon as you enter the composer so you
22166 can choose to remove it or edit it on a message by message basis.
22167 Signature file placement in message replies is controlled by the
22168 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
22169 setting in the feature list.
22170 <P>
22172 The default file name is
22173 <!--chtml if pinemode="os_windows"-->
22174 "PINE.SIG" in the same directory as your PINERC file if your
22175 PINERC file is a local file.
22176 If your PINERC file is remote, then it will be in the directory specified
22177 by the "-aux local_directory" command line option.
22178 <!--chtml else-->
22179 ".signature".
22180 <!--chtml endif-->
22181 <P>
22183 To create or edit your signature file choose Setup from the MAIN MENU
22184 and then select S for Signature (Main/Setup/Signature). This puts you
22185 into the Signature Editor where you can enter a <EM>few</EM> lines of
22186 text containing your identity and affiliation.
22188 <P>
22189 If the filename is followed by a vertical bar (|) then instead
22190 of reading the contents of the file the file is assumed to be a
22191 program that will produce the text to be used on its standard output.
22192 The program can't have any arguments and doesn't receive any input from Alpine,
22193 but the rest of the processing works as if the contents came from a file.
22195 <P>
22196 Instead of storing the data in a local file, the
22197 signature data may be stored remotely in an IMAP folder.
22198 In order to do this,
22199 you must use a remote name for the file.
22200 A remote <!--#echo var="VAR_signature-file"--> name might look like:
22201 <P>
22202 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
22203 <P>
22205 The syntax used here is the same as the syntax used for remote configuration
22206 files from the command line.
22207 Note that you may not access an existing signature file remotely,
22208 you have to create a new <EM>folder</EM> that contains the signature data.
22209 If the name you use here for the signature file is a remote name, then when
22210 you edit the file from the Setup/Signature command the data will be stored
22211 remotely in the folder.
22212 You aren't required to do anything special to create the folder, it
22213 gets created automatically if you use a remote name.
22215 <P>
22216 Besides regular text, the signature file may also contain
22217 (or a signature program may produce) tokens that
22218 are replaced with text that usually depends on the message you are replying
22219 to or forwarding.
22220 For example, if the signature file contains the token
22221 <P>
22222 <CENTER><SAMP>_DATE_</SAMP></CENTER>
22223 <P>
22224 anywhere in the text, then that token is replaced by the date
22225 the message you are replying to or forwarding was sent.
22226 If it contains
22227 <P>
22228 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
22229 <P>
22230 that is replaced with the current date.
22231 The first is an example of a token that depends on the message you
22232 are replying to (or forwarding) and the second is an example which
22233 doesn't depend on anything other than the current date.
22234 You have to be a little careful with this facility since tokens that
22235 depend on the message you are replying to or forwarding will be replaced
22236 by nothing in the case where you are composing a new message from scratch.
22237 The use of <A HREF="h_rules_roles">"roles"</A> may help you
22238 in this respect.
22239 It allows you to use different signature files in different cases.
22240 <P>
22242 The list of tokens available for use in the signature file is
22243 <A HREF="h_index_tokens">here</A>.
22244 <P>
22246 Instead of, or along with the use of "roles" to give you
22247 different signature files in different situations, there is also
22248 a way to conditionally include text based
22249 on whether or not a token would result in specific replacement text.
22250 For example, you could include some text based on whether or not
22251 the _NEWS_ token would result in any newsgroups if it was used.
22252 This is explained in detail
22253 <A HREF="h_reply_token_conditionals">here</A>.
22254 This isn't for the faint of heart.
22255 <P>
22256 In the very unlikely event that you want to include a literal token
22257 in the signature you must precede it with a backslash character.
22258 For example,
22259 <P>
22260 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
22261 <P>
22262 would produce something like
22263 <P>
22264 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
22265 <P>
22266 It is not possible to have a literal backslash followed by an expanded token.
22267 <P>
22268 An alternate method for storing the signature data is available by using the
22269 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
22270 This variable will be used by default.
22271 <P>
22272 <UL>
22273 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22274 </UL><P>
22275 <End of help on this topic>
22276 </BODY>
22277 </HTML>
22278 ====== h_config_init_cmd_list =====
22279 <HTML>
22280 <HEAD>
22281 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
22282 </HEAD>
22283 <BODY>
22284 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
22286 The initial keystroke--or command--list option lets you start Alpine at
22287 any place you like.
22288 Whatever keystrokes you specify here will be executed
22289 by Alpine upon startup as a macro.
22290 The words SPACE, TAB, DOWN, UP, LEFT, and
22291 RIGHT indicate the pressing of those keys.
22292 CR indicates the pressing of the RETURN key.
22293 F1 through F12 represent the function keys, and ^ followed
22294 by a character indicates that key pressed along with the control key (in
22295 other words, ^P means Ctrl-P).
22296 As a shortcut notation, an element of the list may be several characters
22297 surrounded by double-quotes (").
22298 That will be expanded into the individual keystrokes
22299 (excluding the double-quote characters).
22300 For example, the quoted-string
22302 <P><CENTER>"ABC"</CENTER>
22304 <P>
22305 is interpreted the same as the three separate list members
22307 <P><CENTER>A and B and C</CENTER>
22309 <P>
22310 which is also the same as
22312 <P><CENTER>A,B,C</CENTER>
22314 <P>
22315 An example: To view message 1 on startup,
22316 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
22318 <P><CENTER>I,J,1,CR,V</CENTER>
22320 <P>
22321 An equivalent version of this is
22323 <P><CENTER>"IJ1",CR,V</CENTER>
22325 <P>
22326 Restrictions: You cannot pre-type into the composer with the initial
22327 keystroke list, and you cannot mix function key commands with letter
22328 commands.
22330 <P><UL>
22331 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22332 </UL>
22333 <P>
22334 <End of help on this topic>
22335 </BODY>
22336 </HTML>
22337 ====== h_config_comp_hdrs =====
22338 <html>
22339 <header>
22340 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
22341 </header>
22342 <body>
22343 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
22345 You can control which headers you want visible when composing outgoing
22346 email using this option.
22347 You can specify any of the regular set, any
22348 <A HREF="h_compose_richhdr">Rich Header</A>,
22349 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22350 that you have already defined.
22351 If you use this setting at all, you must specify all the
22352 headers you want to see, you can't just add to the regular header set.
22353 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
22355 Note that the "Newsgroups:" header will be abbreviated in the Composer
22356 display, but should be spelled out in full here.<p>
22357 <UL>
22358 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22359 </UL><P>
22360 <End of help on this topic>
22361 </body>
22362 </html>
22363 ====== h_config_custom_hdrs =====
22364 <HTML>
22365 <HEAD>
22366 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
22367 </HEAD>
22368 <BODY>
22369 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
22371 You may add your own custom headers to outgoing messages.
22372 Each header you specify here must include the header tag
22373 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
22374 and may optionally include a value for that header.
22375 If you want to see these custom headers each time you compose a message,
22376 you must add them to your
22377 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22378 otherwise they become part
22379 of the rich header set that you only see when you press the
22380 <A HREF="h_compose_richhdr">Rich Header</A>
22381 <!--chtml if pinemode="function_key"-->(F5)
22382 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22383 (If you are looking for a way to change which headers are <EM>displayed</EM>
22384 when you view a message, take a look at the
22385 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22386 option instead.)
22387 Here's an example that shows how you might set your From address
22388 <P>
22389 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22390 <P>
22391 and another showing how you might set a Reply-To address
22392 <P>
22393 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22394 <P>
22395 You may also set non-standard header values here.
22396 For example, you could add
22397 <P>
22398 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22399 <P>
22400 or even
22401 <P>
22402 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22403 <P>
22404 If you include a value after the colon then that header will be included
22405 in your outgoing messages unless you delete it before sending.
22406 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22407 it will not be included in outgoing messages unless you edit a value
22408 in manually.
22409 For example, if
22410 <P>
22411 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22412 <P>
22413 is in the list, then the Reply-To header will be available for editing
22414 but won't be included unless a value is added while in the composer.
22415 <P>
22416 It's actually a little more complicated than that.
22417 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22418 defaults.
22419 If the message you are about to compose already has a value for a header,
22420 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22421 For example, if you are Replying to a message the Subject field
22422 will already be filled in.
22423 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22424 custom subject will <EM>NOT</EM> be used.
22425 The subject derived from the subject of the message you are Replying
22426 to will be used instead.
22427 <P>
22428 It is also possible to make header setting even more complicated and more
22429 automatic by using
22430 <A HREF="h_rules_roles">Roles</A>,
22431 but if all you want to do is set a default value for a header, you don't
22432 need to think about Roles.
22433 <P>
22434 If you change your From address you may also find it useful to add the
22435 changed From address to the
22436 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22437 configuration option.
22438 <P>
22439 Limitation: Because commas are used to separate the list of
22440 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22441 header contain a comma.
22442 Nor is there currently an "escape" mechanism provided
22443 to make this work.
22444 <P><UL>
22445 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22446 </UL>
22447 <P>
22448 <End of help on this topic>
22449 </BODY>
22450 </HTML>
22451 ====== h_config_viewer_headers =====
22452 <HTML>
22453 <HEAD>
22454 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22455 </HEAD>
22456 <BODY>
22457 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22459 You may change the default list of headers that are viewed by listing
22460 the headers you want to view here. If the headers in your
22461 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22462 will be shown. The order of the headers you list will be honored. If
22463 the special value "all-except" is included as the first
22464 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22465 message except those in the list will be shown. The values are all
22466 case insensitive.
22468 <P>
22469 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22470 then the original default headers are ignored. So, if you just wanted
22471 to add the header Organization to the list, you would have to list
22472 Organization plus all of the other headers originally in the default
22473 list. If you just included Organization and nothing else, then you
22474 would see only the Organization header, nothing else.
22476 <P>
22477 The default list of headers includes:
22478 <UL>
22479 <LI>From
22480 <LI>Resent-From
22481 <LI>To
22482 <LI>Resent-To
22483 <LI>Cc
22484 <LI>Resent-cc
22485 <LI>Bcc
22486 <LI>Newsgroups
22487 <LI>Followup-To
22488 <LI>Date
22489 <LI>Resent-Date
22490 <LI>Subject
22491 <LI>Resent-Subject
22492 <LI>Reply-To
22493 </UL>
22495 <P>
22496 If you are looking for a way to control which headers are included in
22497 outgoing mail and are visible or not in the composer, take a look at the
22498 options
22499 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22500 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22501 this option.
22502 <P>
22503 <UL>
22504 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22505 </UL><P>
22506 <End of help on this topic>
22507 </BODY>
22508 </HTML>
22509 ====== h_config_viewer_margin_left =====
22510 <HTML>
22511 <HEAD>
22512 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22513 </HEAD>
22514 <BODY>
22515 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22517 This variable controls the left-hand vertical margin's width in
22518 Alpine's Message Viewing screen.
22519 Its value is the number of space characters preceding each displayed line.
22520 For consistency with
22521 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22522 you may specify the column number to start in
22523 (column numbering begins with number 1)
22524 instead of the width of the margin by appending a lower case letter
22525 "c" to the number.
22526 For example, a value of "2c" means to start the text in column two,
22527 which is entirely equivalent to a value of "1", which means to
22528 leave a margin of 1 space.
22529 <P>
22530 The default is a left margin of 0 (zero).
22531 Misconfigurations (for example, negative values or values with starting
22532 left columns greater than the ending right column)
22533 are silently ignored.
22534 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22535 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22536 instead.
22538 <P>
22539 <End of help on this topic>
22540 </BODY>
22541 </HTML>
22542 ====== h_config_viewer_margin_right =====
22543 <HTML>
22544 <HEAD>
22545 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22546 </HEAD>
22547 <BODY>
22548 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22550 This variable controls the right-hand vertical margin's width in
22551 Alpine's Message Viewing screen.
22552 Its value is the number of space characters following each displayed line.
22553 You may specify the column number to end the text in
22554 (column numbering begins with number 1)
22555 instead of the width of the margin by appending a lower case letter
22556 "c" to the number.
22557 For example, a value of "76c" means to end the text in column 76.
22558 If the screen is 80 characters wide, this is equivalent to a value
22559 of "4", which means to leave a margin of 4 spaces.
22560 However, if you use different size screens at different times, then these
22561 two values are not equivalent.
22562 <P>
22563 The default right margin is 4.
22564 Misconfigurations (for example, negative values or values with starting
22565 left columns greater than the ending right column)
22566 are silently ignored.
22567 If the number of columns for text between the
22568 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22569 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22570 instead.
22572 <P>
22573 <End of help on this topic>
22574 </BODY>
22575 </HTML>
22576 ====== h_config_quote_suppression =====
22577 <HTML>
22578 <HEAD>
22579 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22580 </HEAD>
22581 <BODY>
22582 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22584 This option should be used with care.
22585 It will cause some of the quoted text to be eliminated from the
22586 display when viewing a message in the MESSAGE TEXT screen.
22587 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22588 value "5",
22589 this will cause quoted text that is longer than five lines to be truncated.
22590 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22591 Quoted text of more than six lines will have the first five lines displayed
22592 followed by a line that looks something like
22593 <P>
22594 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22595 <P>
22596 As a special case, if exactly one line of quoted text would be hidden, the
22597 entire quote will be shown instead.
22598 So for the above example, quoted text that is exactly six lines long will
22599 will be shown in its entirety.
22600 (In other words, instead of hiding a single line and adding a line
22601 that announces that one line was hidden, the line is just shown.)
22602 <P>
22603 If the sender of a message has carefully chosen the quotes that he or she
22604 includes, hiding those quotes may change the meaning of the message.
22605 For that reason, Alpine requires that when you want to set the value of this
22606 variable to something less than four lines, you actually have to set it
22607 to the negative of that number.
22608 So if you want to set this option to "3", you actually have to
22609 set it to "-3".
22610 The only purpose of this is to get you to think about whether or not you
22611 really want to do this!
22612 If you want to delete all quoted text you set the value of this option
22613 to the special value "-10".
22614 <P>
22615 The legal values for this option are
22616 <P>
22617 <TABLE>
22618 <TR>
22619 <TD> 0 </TD>
22620 <TD> Default, don't hide anything </TD>
22621 </TR>
22622 <TR>
22623 <TD> -1,-2,-3 </TD>
22624 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22625 </TR>
22626 <TR>
22627 <TD> 4,5,6,... </TD>
22628 <TD> Suppress if more than that many lines </TD>
22629 </TR>
22630 <TR>
22631 <TD> -10 </TD>
22632 <TD> Suppress all quoted lines </TD>
22633 </TR>
22634 </TABLE>
22635 <P>
22636 If you set this option to a non-default value you may sometimes wish to
22637 view the quoted text that is not shown.
22638 When this is the case, the
22639 <A HREF="h_common_hdrmode">HdrMode Command</A>
22640 may be used to show the hidden text.
22641 Typing the "H" command once will show the hidden text.
22642 Typing a second "H" will also turn on Full Header mode.
22643 The presence or absence of the HdrMode command is determined by the
22644 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22645 Feature-List option in your Alpine configuration, so you will want to
22646 be sure that is turned on if you use quote suppression.
22647 <P>
22648 For the purposes of this option, a quote is a line that begins with the
22649 character ">".
22650 <P>
22651 Quotes are only suppressed when displaying a message on the screen.
22652 The entire quote will be left intact when printing or forwarding or something
22653 similar.
22654 <P>
22655 <End of help on this topic>
22656 </BODY>
22657 </HTML>
22658 ====== h_config_saved_msg_name_rule =====
22659 <HTML>
22660 <HEAD>
22661 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
22662 </HEAD>
22663 <BODY>
22664 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
22666 This option determines the default folder name when saving
22667 a message.
22669 <P>
22670 The default option is "default-folder", which is the folder
22671 called "saved-messages" in Unix Alpine and
22672 "savemail" in PC-Alpine. To change the default folder, modify
22673 the Alpine option called
22674 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
22676 <P>
22677 Choosing any of the "by-" options cause Alpine to attempt to
22678 get the chosen option's value for the message being saved (or for the
22679 first message being saved if using an aggregrate save).
22680 For example, if "by-from" is chosen, Alpine attempts to get the
22681 value of who the message came from (i.e. the from address).
22682 Alpine then attempts to save the message to a folder matching that value.
22683 If "by-from" is chosen and no value is obtained, Alpine uses
22684 "by-sender".
22685 The opposite is also true.
22686 If "by-recipient" is chosen and the message was posted to a
22687 newsgroup, Alpine will use the newsgroup name.
22688 If "by-replyto" is chosen and no value is obtained, Alpine uses
22689 "by-from".
22691 <P>
22692 If any of the "by-realname" options are chosen, Alpine will attempt
22693 to use the personal name part of the address instead of the mailbox part.
22694 If any of the "by-nick" options are chosen, the
22695 address is looked up in your address book and if found, the
22696 nickname for that entry is used.
22697 Only simple address book entries are checked, not distribution lists.
22698 Similarly, if any of the
22699 "by-fcc" options are chosen, the fcc from the corresponding
22700 address book entry is used.
22701 If by-realname, or the by-nick or by-fcc lookups result in no value,
22702 then if the chosen option ends with the "then-from",
22703 "then-sender", "then-replyto",
22704 or "then-recip" suffix, Alpine
22705 reverts to the same behavior as "by-from",
22706 "by-sender", "by-replyto", or "by-recip"
22707 depending on which option was specified.
22708 If the chosen option doesn't end with one of
22709 the "then-" suffixes, then Alpine reverts to the default
22710 folder when no match is found in the address book.
22712 <P>
22713 Choosing the option called "last-folder-used", causes Alpine
22714 to save to the folder that you saved to the last time you saved a
22715 message. The first time you save a message in an Alpine session, Alpine
22716 attempts to save the message to the default folder.
22718 <P>
22719 Here is an example to make some of the options clearer.
22720 If the message is From
22721 <P>
22722 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
22723 <P>
22724 and this rule is set to "by-from", then the default folder offered
22725 in the save dialog would be "flint".
22726 <P>
22727 If this rule is set to "by-realname-of-from" then the default would
22728 be "Fred Flintstone".
22729 <P>
22730 If this rule is set to "by-nick-of-from" then Alpine will search
22731 for the address "flint@bedrock.org" in your address book.
22732 If an entry is found and it has a nickname associated with it, that nickname
22733 will be offered as the default folder.
22734 If not, the default saved message folder will be offered as the default.
22735 <P>
22736 If this rule is set to "by-fcc-of-from" then Alpine will search
22737 for the address "flint@bedrock.org" in your address book.
22738 If an entry is found and it has an Fcc associated with it, that Fcc
22739 will be offered as the default folder.
22740 If not, the default saved message folder will be offered as the default.
22741 <P>
22742 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
22743 for the address "flint@bedrock.org" in your address book.
22744 If an entry is found and it has a nickname associated with it, that nickname
22745 will be offered as the default folder.
22746 If it is not found (or has no nickname) then the default offered will be
22747 the same as it would be for the "by-from" rule.
22748 That is, it would be "flint"
22749 <P>
22750 <UL>
22751 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22752 </UL><P>
22753 <End of help on this topic>
22754 </BODY>
22755 </HTML>
22756 ====== h_config_fcc_rule =====
22757 <HTML>
22758 <HEAD>
22759 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
22760 </HEAD>
22761 <BODY>
22762 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
22764 This option determines the default name for folder carbon copy. Choose
22765 one:
22767 <DL>
22768 <DT>default-fcc</DT>
22769 <DD>This is the normal default, the value of which is set in the
22770 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
22771 configuration.
22772 </DD>
22774 <DT>last-fcc-used</DT>
22775 <DD> Causes Alpine to use the folder that was last
22776 used in the fcc field
22777 </DD>
22779 <DT>by-nickname</DT>
22780 <DD>Means that Alpine will use the nickname
22781 from your address book that matches the first address in the To line.
22782 If there is no match, it will use the value of the
22783 "<!--#echo var="VAR_default-fcc"-->" variable.
22784 </DD>
22786 <DT>by-recipient</DT>
22787 <DD>Means Alpine will form a folder name
22788 based on the left hand side of the first address in the To line.
22789 </DD>
22791 <DT>by-nick-then-recip</DT>
22792 <DD>Means that it will use the
22793 matching nickname from your address book if there is one, otherwise it
22794 will extract the recipient name from the address and use that (like
22795 by-recipient).
22796 </DD>
22798 <DT>current-folder</DT>
22799 <DD>Causes a copy to be written to
22800 the currently open folder, unless that is the INBOX. In the case
22801 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
22802 used instead.
22803 </DD>
22804 </DL>
22806 <P>
22807 Note: Whatever the fcc specified by the rule here, it will be
22808 over-ridden by any fcc entries you have in your address book.
22810 <P>
22811 <UL>
22812 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22813 </UL><P>
22814 <End of help on this topic>
22815 </BODY>
22816 </HTML>
22817 ====== h_config_sort_key =====
22818 <HTML>
22819 <HEAD>
22820 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
22821 </HEAD>
22822 <BODY>
22823 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
22825 This option determines the order in which messages will be displayed in
22826 the MESSAGE INDEX screen. Choose from:
22827 <P>
22828 <UL>
22829 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22830 <LI> <A HREF="h_index_sort_date">Date</A>
22831 <LI> <A HREF="h_index_sort_subj">Subject</A>
22832 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22833 <LI> <A HREF="h_index_sort_thread">Thread</A>
22834 <LI> <A HREF="h_index_sort_from">From</A>
22835 <LI> <A HREF="h_index_sort_size">Size</A>
22836 <LI> <A HREF="h_index_sort_score">Score</A>
22837 <LI> <A HREF="h_index_sort_to">To</A>
22838 <LI> <A HREF="h_index_sort_cc">Cc</A>
22839 </UL>
22841 <P>
22842 Each type of sort may also be reversed.
22843 Normal default is by "Arrival".
22845 <P>
22846 A possible point of confusion arises when you change the configuration
22847 of the <!--#echo var="VAR_sort-key"-->.
22848 The folder will normally be re-sorted when you go back to viewing the
22849 index.
22850 However, if you have manually sorted the folder with the
22851 Sort
22852 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22853 command, then it will not be re-sorted until the next time it is opened.
22855 <P>
22856 <UL>
22857 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22858 </UL><P>
22859 <End of help on this topic>
22860 </BODY>
22861 </HTML>
22862 ====== h_config_other_startup =====
22863 <HTML>
22864 <HEAD>
22865 <TITLE>OPTION: Set Startup Rule</TITLE>
22866 </HEAD>
22867 <BODY>
22868 <H1>OPTION: Set Startup Rule</H1>
22870 This option determines which message will be the <EM>current message</EM> when
22871 the folder is first opened.
22872 It works the same way that the option
22873 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
22874 works, so look there for help.
22875 It may be used for any folder, not just incoming folders.
22877 <P>
22878 <UL>
22879 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22880 </UL><P>
22881 <End of help on this topic>
22882 </BODY>
22883 </HTML>
22884 ====== h_config_perfolder_sort =====
22885 <HTML>
22886 <HEAD>
22887 <TITLE>Set Sort Order</TITLE>
22888 </HEAD>
22889 <BODY>
22890 <H1>Set Sort Order</H1>
22892 This option determines the order in which messages will be displayed in
22893 the MESSAGE INDEX screen when the Current Folder Type set in the
22894 Pattern is a match. Choose from:
22895 <P>
22896 <UL>
22897 <LI> <A HREF="h_index_sort_default">Default</A>
22898 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
22899 <LI> <A HREF="h_index_sort_date">Date</A>
22900 <LI> <A HREF="h_index_sort_subj">Subject</A>
22901 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
22902 <LI> <A HREF="h_index_sort_thread">Thread</A>
22903 <LI> <A HREF="h_index_sort_from">From</A>
22904 <LI> <A HREF="h_index_sort_size">Size</A>
22905 <LI> <A HREF="h_index_sort_score">Score</A>
22906 <LI> <A HREF="h_index_sort_to">To</A>
22907 <LI> <A HREF="h_index_sort_cc">Cc</A>
22908 </UL>
22910 <P>
22911 Each type of sort may also be reversed.
22912 Normal default is by "Arrival".
22914 <P>
22915 A possible point of confusion arises when you change the configuration
22916 of the Sort Order for the currently open folder.
22917 The folder will normally be re-sorted when you go back to viewing the
22918 index.
22919 However, if you have manually sorted the folder with the
22920 Sort
22921 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
22922 command, then it will not be re-sorted until the next time it is opened.
22924 <P>
22925 <UL>
22926 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22927 </UL><P>
22928 <End of help on this topic>
22929 </BODY>
22930 </HTML>
22931 ====== h_config_fld_sort_rule =====
22932 <HTML>
22933 <HEAD>
22934 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
22935 </HEAD>
22936 <BODY>
22937 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
22939 This option controls the order in which folder list entries will be
22940 presented in the FOLDER LIST screen. Choose one of the following:
22942 <DL>
22943 <DT>Alphabetical</DT>
22944 <DD>sort by alphabetical name independent of type
22945 </DD>
22947 <DT>Alpha-with-dirs-last</DT>
22948 <DD>sort by alphabetical name grouping directory entries
22949 to the end of the list
22950 </DD>
22952 <DT>Alpha-with-dirs-first</DT>
22953 <DD>sort by alphabetical name grouping directory entries
22954 to the start of the list
22955 </DD>
22956 </DL>
22958 The normal default is "Alphabetical".
22960 <P>
22961 <UL>
22962 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22963 </UL><P>
22964 <End of help on this topic>
22965 </BODY>
22966 </HTML>
22967 ====== h_config_ab_sort_rule =====
22968 <HTML>
22969 <HEAD>
22970 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
22971 </HEAD>
22972 <BODY>
22973 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
22975 This option controls the order in which address book entries will be
22976 presented. Choose one of the following:
22978 <DL>
22979 <DT>fullname</DT>
22980 <DD>use fullname field, lists mixed in
22981 </DD>
22983 <DT>fullname-with-lists-last</DT>
22984 <DD>use fullname field, but put lists at end
22985 </DD>
22987 <DT>nickname</DT>
22988 <DD>use nickname field, lists mixed in
22989 </DD>
22991 <DT>nickname-with-lists-last</DT>
22992 <DD>use nickname field, but put lists at end
22993 </DD>
22995 <DT>dont-sort</DT>
22996 <DD>don't change order of file
22997 </DD>
22998 </DL>
23000 <P>
23001 The normal default is "fullname-with-lists-last".
23002 If you use an address book from more than one computer and those
23003 computers sort the address book differently then the sort order
23004 will be the order where the last change to the address book was
23005 made.
23006 There are two reasons the sorting might be different on different
23007 systems.
23008 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
23009 places.
23010 Second, the collation rules on the two computers may be different.
23011 For example, one system might ignore special characters while the other
23012 doesn't or one may sort upper and lower case letters together while
23013 the other doesn't.
23014 In any case, the order you see is the order on the system where the
23015 last change was made, for example by an address book edit or a
23016 Take Address command.
23018 <P>
23019 <UL>
23020 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23021 </UL><P>
23022 <End of help on this topic>
23023 </BODY>
23024 </HTML>
23025 ====== h_config_post_char_set =====
23026 <HTML>
23027 <HEAD>
23028 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
23029 </HEAD>
23030 <BODY>
23031 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
23033 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
23034 when sending messages.
23036 <P>
23038 When sending a message the text typed in the composer is
23039 labeled with the character set specified by this option.
23040 If the composed text is not fully representable in the
23041 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
23042 instead;
23044 <P>
23045 Attachments are labeled with your
23046 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
23048 <P>
23049 Generally, there should be little need to set this option.
23050 If left unset, the
23051 default behavior is to label composed text as specifically as
23052 possible. That is, if the composed text has no non-ASCII characters,
23053 it is labeled as "US-ASCII." Similarly, if it is composed of
23054 only ISO-8859-15 characters, it is labeled as such. Alpine will
23055 attempt to automatically detect a number of character sets including ISO-8859-15,
23056 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23057 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
23058 If the message contains a mix of character sets,
23059 it is labeled as "UTF-8."
23061 <P>
23063 This setting is provided to allow you to force a particular character set that
23064 Alpine does not automatically detect. For example, if a message is representable
23065 in more than one character set then Alpine may choose a different default
23066 than you want.
23067 Lastly, by setting this option explicitly to
23068 "UTF-8" all non-ASCII messages you send will be labeled as
23069 "UTF-8" instead of something more specific.
23071 <P>
23072 In the Setup/Config screen you may choose from a list of all the
23073 character sets Alpine knows about by using the "T" ToCharsets command.
23075 <P>
23076 The options
23077 <A HREF="h_config_char_set">"Display Character Set"</A>
23078 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23079 are closely related.
23080 Setting the feature
23081 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23082 should cause this option to be ignored.
23084 <P>
23085 <UL>
23086 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23087 </UL><P>
23088 <End of help on this topic>
23089 </BODY>
23090 </HTML>
23091 ====== h_config_unk_char_set =====
23092 <HTML>
23093 <HEAD>
23094 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
23095 </HEAD>
23096 <BODY>
23097 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
23099 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
23100 when reading or replying to messages.
23102 <P>
23104 A text message should either be made up of all US-ASCII characters
23105 or it should contain a charset label which tells the software which
23106 character set encoding to use to interpret the message.
23107 Sometimes a malformed message may be unlabeled but contain non-ascii text.
23108 This message is outside of the standards so any attempt to read it could fail.
23109 When Alpine attempts to read such a message it will try to interpret the
23110 text in the character set you specify here.
23111 For example, if you have correspondents who send you unlabeled messages that
23112 are usually made up of characters from the WINDOWS-1251 character set, setting
23113 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
23114 allow you to read those messages.
23115 Of course, if the unlabeled message is actually in some other character set,
23116 then you may see garbage on your screen.
23117 <P>
23118 Instead of just unlabeled text, this option also affects text which is labeled
23119 with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE"
23120 or "US-ASCII".
23122 <P>
23123 In the Setup/Config screen you may choose from a list of all the
23124 character sets Alpine knows about by using the "T" ToCharsets command.
23126 <P>
23127 <UL>
23128 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23129 </UL><P>
23130 <End of help on this topic>
23131 </BODY>
23132 </HTML>
23133 ====== h_config_char_set =====
23134 <HTML>
23135 <HEAD>
23136 <TITLE>OPTION: Display Character Set</TITLE>
23137 </HEAD>
23138 <BODY>
23139 <H1>OPTION: Display Character Set</H1>
23141 The Display Character Set configuration option is used when viewing messages.
23142 <P>
23143 Alpine uses Unicode characters internally and
23144 it is a goal for Alpine to handle email in many different languages.
23145 Alpine will properly display only left-to-right character sets
23146 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
23147 font is in use, in the sense that
23148 characters are assumed to take up zero, one, or two character cell
23149 widths from left to right on the screen. This is true even in PC-Alpine.
23150 <P>
23152 Alpine recognizes some local character sets that are right-to-left
23153 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
23154 (Arabic) and properly converts texts in these character sets to/from
23155 Unicode; however, there are known display bugs with these character
23156 sets.
23157 <P>
23159 There are three possible configuration character settings and some
23160 environment variable settings that can affect how Alpine
23161 handles international characters.
23162 The first two of these are only available in UNIX Alpine.
23163 The three configuration options are
23164 Display Character Set,
23165 Keyboard Character Set, and
23166 <!--#echo var="VAR_posting-character-set"-->.
23167 The Keyboard Character Set defaults to being the same value
23168 as the Display Character Set, and that is usually correct, because
23169 the keyboard almost always produces characters in the same character set
23170 as the display displays.
23171 The Display Character Set is the character set that Alpine
23172 will attempt to use when sending characters to the display.
23173 <P>
23175 By default, the Display Character Set variable is not set and UNIX Alpine
23176 will attempt to get this information from the environment.
23177 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
23178 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
23179 An explicit configuration setting for Display Character Set will,
23180 of course, override any default setting.
23181 <P>
23182 For PC-Alpine the Display Character Set
23183 and the Keyboard Character Set
23184 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
23185 <P>
23187 It is probably best to use UNIX Alpine in a terminal emulator
23188 capable of displaying UTF-8 characters, since that will allow you to
23189 view just about any received text that is correctly formatted (note,
23190 however, the above comments about known index display bugs with certain
23191 character sets). You'll need to have an emulator that uses a UTF-8 font
23192 and you'll need to set up your environment to use a UTF-8 charmap. For
23193 example, on a Linux system you might include
23194 <P>
23195 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
23196 <P>
23198 or something similar in your UNIX startup files.
23199 You'd also have to select a UTF-8 font in your terminal emulator.
23200 <P>
23202 The types of values that the character set variables may be set to are
23203 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
23204 The <CODE>ISO-2022</CODE> character sets are not supported for input or
23205 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
23206 for use only as a <!--#echo var="VAR_posting-character-set"-->.
23207 In the Setup/Config screen you may choose from a list of all the
23208 character sets Alpine knows about by using the "T" ToCharsets command.
23209 Here is a list of many of the possible character sets:
23211 <P>
23212 <TABLE>
23213 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
23214 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
23215 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
23216 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
23217 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
23218 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
23219 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
23220 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
23221 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
23222 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
23223 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
23224 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
23225 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
23226 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
23227 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
23228 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
23229 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
23230 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
23231 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
23232 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
23233 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
23234 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
23235 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
23236 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23237 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23238 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23239 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23240 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23241 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
23242 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
23243 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
23244 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
23245 </TABLE>
23246 <P>
23248 When reading incoming email, Alpine understands many different
23249 character sets and is able to convert the incoming mail into Unicode.
23250 The Unicode will be converted to the Display Character Set
23251 for display on your terminal.
23252 Characters typed at the keyboard will be converted from the
23253 Keyboard Character Set to Unicode for Alpine's internal
23254 use.
23255 You may find that you can read some malformed messages that do not
23256 contain a character set label by setting the option
23257 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
23258 <P>
23260 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
23261 The default behavior obtained by leaving this variable unset is usually
23262 what is wanted. In that default case, Alpine will attempt
23263 to label the message with the most specific character set from the
23264 rather arbitrary set
23265 <P>
23266 US-ASCII, ISO-8859-15,
23267 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23268 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
23269 <P>
23271 For example, if the message is made up of only US-ASCII characters, it
23272 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
23273 that will be the label. If that doesn't work the same is tried for the
23274 remaining members of the list.
23276 <P>
23277 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
23278 explicit value instead.
23279 For example, if you usually send messages in Greek, setting this
23280 option to ISO-8859-7 will result in messages being labeled as
23281 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
23282 are only Greek characters, or UTF-8 if there are some characters
23283 that aren't representable in ISO-8859-7.
23284 Another possibility is to set this option explicitly to UTF-8.
23285 In that case
23286 Alpine labels only ascii messages as US-ASCII and all other
23287 messages as UTF-8.
23288 <P>
23290 The options
23291 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23292 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23293 are closely related to this option.
23294 Setting the feature
23295 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23296 should cause this option to be ignored.
23298 <P>
23299 When displaying a message, Alpine compares this setting to the character
23300 set specified in the message. If not all of the
23301 characters in the message can be displayed using the Display Character Set
23302 then Alpine places an editorial
23303 comment in the displayed text (enclosed in square-brackets) indicating
23304 that some characters may not be displayed correctly.
23305 This comment may be eliminated by turning on the option
23306 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
23308 <P>
23309 <UL>
23310 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23311 </UL><P>
23312 <End of help on this topic>
23313 </BODY>
23314 </HTML>
23315 ====== h_config_key_char_set =====
23316 <HTML>
23317 <HEAD>
23318 <TITLE>OPTION: Keyboard Character Set</TITLE>
23319 </HEAD>
23320 <BODY>
23321 <H1>OPTION: Keyboard Character Set</H1>
23323 UNIX Alpine only.
23324 <P>
23325 The Keyboard Character Set identifies the character set of the characters
23326 coming from your keyboard.
23327 It defaults to having the same value as your
23328 <A HREF="h_config_char_set">"Display Character Set"</A>,
23329 which in turn defaults to a value obtained from your environment.
23330 It is unlikely that you will need to use this option, because the keyboard
23331 almost always produces the same kind of characters as the display displays.
23333 <P>
23334 This character set is also used when accessing files in your local
23335 file system.
23336 The names of the files are assumed to be in the same character set as
23337 what the keyboard produces, as well as the contents of the files.
23339 <P>
23340 In the Setup/Config screen you may choose from a list of all the
23341 character sets Alpine knows about by using the "T" ToCharsets command.
23343 <P>
23344 The options
23345 <A HREF="h_config_char_set">"Display Character Set"</A>
23346 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23347 are closely related.
23348 Setting the feature
23349 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23350 should cause this option to be ignored.
23352 <P>
23353 <UL>
23354 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23355 </UL><P>
23356 <End of help on this topic>
23357 </BODY>
23358 </HTML>
23359 ====== h_config_editor =====
23360 <HTML>
23361 <HEAD>
23362 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
23363 </HEAD>
23364 <BODY>
23365 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
23367 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
23368 normally an alternative to Alpine's internal composer (Pico). You could use
23369 this setting to specify an alternate editor to use occasionally or if you
23370 have a favorite editor and want to use it all the time (see the
23371 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
23372 If you specify multiple editors for this option, ^_ will invoke the first one
23373 of those specified that exists and is executable. When specifying a program
23374 for use here, make sure that the format of the text it saves -- which, when
23375 you exit it, will become the message body in Alpine -- is appropriate
23376 for the body of an email message; avoid proprietary formats that may result in
23377 a message body that the recipient of your message will be unable to decipher.
23378 <P>
23379 <!--chtml if pinemode="os_windows"-->
23380 <!--chtml else-->
23381 If you are in doubt about what editors are available on your system, or which
23382 of them may be appropriate for specification here, ask your local computing
23383 support staff.
23384 <!--chtml endif-->
23385 <P>
23386 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23387 unset, outgoing text will be set as flowed. In most cases this will be fine,
23388 but if the editor has a "flowed text" mode, it would be best to
23389 use that.
23391 <P><UL>
23392 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23393 </UL>
23394 <P>
23395 <End of help on this topic>
23396 </BODY>
23397 </HTML>
23398 ====== h_config_speller =====
23399 <HTML>
23400 <HEAD>
23401 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23402 </HEAD>
23403 <BODY>
23404 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23406 UNIX Alpine only.
23407 <P>
23408 For PC-Alpine, you must install the aspell library code that you
23409 may get from
23410 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23411 <P>
23412 This option affects the behavior of the ^T (spell check) command in the
23413 Composer. It specifies the program invoked by ^T in the Composer.
23414 By default, Alpine uses
23415 <P>
23416 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23417 <P>
23418 if it knows where to find "aspell".
23419 If there is no "aspell" command available but the command "ispell" is available
23420 then the command used is
23421 <P>
23422 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23423 <P>
23424 Otherwise, the ancient "spell" command is used.
23425 <P>
23426 If you specify a value for this command (with full pathname) then that is what
23427 will be used instead of any of the defaults.
23428 When invoking this
23429 spell-checking program, Alpine appends a tempfile name (where the message is
23430 passed) to the command line. Alpine expects the speller to correct the
23431 spelling in that file. When you exit from that program Alpine will read the
23432 tempfile back into the composer.
23433 <P>
23434 Don't set this speller option to the standard Unix spell command.
23435 That won't work because spell works in a different way.
23437 <P>
23438 <UL>
23439 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23440 </UL><P>
23441 <End of help on this topic>
23442 </BODY>
23443 </HTML>
23444 ====== h_config_aspell_dictionary =====
23445 <HTML>
23446 <HEAD>
23447 <TITLE>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></TITLE>
23448 </HEAD>
23449 <BODY>
23450 <H1>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></H1>
23452 PC Alpine only.
23453 <P>
23454 This option specifies a list of dictionaries you will use with
23455 aspell. A sample entry is "en_US" for american english, or
23456 "en_GB" for brittish english.
23458 <P>
23459 <UL>
23460 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23461 </UL><P>
23462 <End of help on this topic>
23463 </BODY>
23464 </HTML>
23465 ====== h_config_display_filters =====
23466 <HTML>
23467 <HEAD>
23468 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23469 </HEAD>
23470 <BODY>
23471 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23473 This option defines a list of text-filtering commands (programs or
23474 scripts) that may be used to filter text portions of received messages
23475 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23476 display screen, exporting to a text file).
23477 For security reasons, the full path name of the
23478 filter command must be specified.
23480 <P>
23481 The command is executed and the message is piped into its standard input.
23482 The standard output of the command is read back by Alpine. The
23483 "_TMPFILE_" token (see below) overrides this default behavior.
23485 <P>
23486 The filter's use is based on the configured "trigger" string. The
23487 format of a filter definition is:
23489 <P>
23490 <CENTER><trigger> <command> <arguments></CENTER>
23492 <P>
23493 You can specify as many filters as you wish, separating them with a comma.
23494 Each filter can have only one trigger and command. Thus, two trigger
23495 strings that invoke the same command require separate filter
23496 specifications.
23498 <P>
23499 The "trigger" is simply text that, if found in the message,
23500 will invoke the associated command. If the trigger contains any space
23501 characters, it must be placed within quotes. Likewise, should you
23502 wish a filter to be invoked unconditionally, define the trigger as the
23503 null string, "" (two consecutive double-quote characters). If the
23504 trigger string is found anywhere in the text of the message the filter
23505 is invoked. Placing the trigger text within the tokens defined below
23506 changes where within the text the trigger must be before considering
23507 it a match.
23509 <P>
23510 Trigger Modifying Tokens:
23511 <DL>
23512 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23513 <DD>This token tells Alpine to invoke the supplied command
23514 if the text is in a character set matching <VAR>string</VAR>
23515 (e.g., ISO-8859-2 or ISO-2022-JP).
23516 </DD>
23519 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23520 <DD>This token tells Alpine to invoke the supplied command
23521 if the enclosed <VAR>string</VAR> is found to be the first
23522 non-whitespace text.
23523 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23524 the space character.
23525 </DD>
23527 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23528 <DD>This token tells Alpine to invoke the supplied command
23529 if the enclosed <VAR>string</VAR> is found at the beginning
23530 of any line in the text.
23531 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23532 the space character.
23533 </DD>
23534 </DL>
23536 <P>
23537 The "command" and "arguments" portion is simply
23538 the command line to be invoked if the trigger string is found. Below
23539 are tokens that Alpine will recognize and replace with special values
23540 when the command is actually invoked.
23542 <P>
23543 Command Modifying Tokens:
23545 <DL>
23546 <DT>_TMPFILE_</DT>
23547 <DD>When the command is executed, this token is
23548 replaced with the path and name of the temporary
23549 file containing the text to be filtered. Alpine
23550 expects the filter to replace this data with the
23551 filter's result.
23553 <P>
23554 NOTE: Use of this token implies that the text to
23555 be filtered is not piped into standard input of the
23556 executed command and its standard output is ignored.
23557 Alpine restores the tty modes before invoking the
23558 filter in case the filter interacts with the user
23559 via its own standard input and output.
23560 </DD>
23562 <DT>_RESULTFILE_</DT>
23563 <DD>When the command is executed, this token is
23564 replaced with the path and name of a temporary
23565 file intended to contain a status message from the
23566 filter. Alpine displays this in the message status
23567 field.
23568 </DD>
23570 <DT>_DATAFILE_</DT>
23571 <DD>When the command is executed, this token is
23572 replaced with the path and name of a temporary
23573 file that Alpine creates once per session and deletes
23574 upon exit. The file is intended to be used by the
23575 filter to store state information between instances
23576 of the filter.
23577 </DD>
23579 <DT>_PREPENDKEY_</DT>
23580 <DD>When the command is executed, this token indicates that a random
23581 number will be passed down the input stream before the message text.
23582 This number could be used as a session key. It is sent in this way to
23583 improve security. The number is unique to the current Alpine session
23584 and is only generated once per session.
23585 </DD>
23587 <DT>_SILENT_</DT>
23588 <DD>When the filter is executed, this token tells Alpine not to repaint
23589 the screen while the command is being executed. This can be used with
23590 filters that do not interact with the user, and therefore repainting
23591 the screen is not necessary.
23592 </DD>
23593 </DL>
23595 <P>
23596 The feature
23597 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23598 <P>
23599 Performance caveat/considerations:
23600 <BR>
23601 Testing for the trigger and invoking the filter doesn't come for free.
23602 There is overhead associated with searching for the trigger string, testing
23603 for the filter's existence and actually piping the text through the filter.
23604 The impact can be reduced if the Trigger Modifying Tokens above are
23605 employed.
23606 <P>
23607 <End of help on this topic>
23608 </BODY>
23609 </HTML>
23610 ====== h_config_sending_filter =====
23611 <HTML>
23612 <HEAD>
23613 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23614 </HEAD>
23615 <BODY>
23616 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23618 This option defines a list of text-filtering commands (programs and
23619 scripts) that may be selectively invoked to process a message just before
23620 it is sent. If set, the Composer's ^X (Send) command will allow you to
23621 select which filter (or none) to apply to the message before it is sent.
23622 For security reasons, the full path of the filter program must be
23623 specified.
23625 <P>
23626 Command Modifying Tokens:
23628 <DL>
23629 <DT>_RECIPIENTS_</DT>
23630 <DD>When the command is executed, this token is replaced
23631 with the space delimited list of recipients of the
23632 message being sent.
23633 </DD>
23635 <DT>_TMPFILE_</DT>
23636 <DD>
23637 When the command is executed, this token is
23638 replaced with the path and name of the temporary
23639 file containing the text to be filtered. Alpine
23640 expects the filter to replace this data with the
23641 filter's result.
23643 <P>
23644 NOTE: Use of this token implies that the text to
23645 be filtered is not piped into standard input of the
23646 executed command and its standard output is ignored.
23647 Alpine restores the tty modes before invoking the
23648 filter in case the filter interacts with the user
23649 via its own standard input and output.
23650 </DD>
23652 <DT>_RESULTFILE_</DT>
23653 <DD>When the command is executed, this token is
23654 replaced with the path and name of a temporary
23655 file intended to contain a status message from the
23656 filter. Alpine displays this in the message status
23657 field.
23658 </DD>
23660 <DT>_DATAFILE_</DT>
23661 <DD>When the command is executed, this token is replaced
23662 in the command line with the path and name of a
23663 temporary file that Alpine creates once per session
23664 and deletes upon exit. The file is intended to be
23665 used by the filter to store state information between
23666 instances of the filter.
23667 </DD>
23669 <DT>_PREPENDKEY_</DT>
23670 <DD>When the command is executed, this token indicates
23671 that a random number will be passed down the input
23672 stream before the message text. This number could
23673 be used as a session key. It is sent in this way
23674 to improve security. The number is unique to the
23675 current Alpine session and is only generated once per
23676 session.
23677 </DD>
23679 <DT>_INCLUDEALLHDRS_</DT>
23680 <DD>When the command is executed, this token indicates
23681 that the headers of the message will be passed down the input stream
23682 before the message text.
23683 </DD>
23685 <DT>_MIMETYPE_</DT>
23686 <DD>When the command is executed, this token is replaced in the
23687 command name with a temporary file name used to accept any new MIME
23688 Content-Type information necessitated by the output of the filter.
23689 Upon the filter's exit, if the file contains new MIME type
23690 information, Alpine verifies its format and replaces the outgoing
23691 message's MIME type information with that contained in the file. This
23692 is basically a cheap way of sending something other than Text/Plain.
23693 </DD>
23694 </DL>
23696 <P>
23697 NOTE: Only the body text, which is visible in the Composer, is piped
23698 through this filter. Attachments are not sent to the filter.
23699 <P>
23700 Sending filters are not used if the feature
23701 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
23702 <P>
23703 <UL>
23704 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23705 </UL><P>
23706 <End of help on this topic>
23707 </BODY>
23708 </HTML>
23709 ====== h_config_keywords =====
23710 <HTML>
23711 <HEAD>
23712 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
23713 </HEAD>
23714 <BODY>
23715 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
23717 You may define your own set of keywords and optionally set them on a
23718 message by message basis.
23719 These are similar to the "Important" flag which the user
23720 may set using the Flag command.
23721 The difference is that the Important flag is always present for each folder.
23722 User-defined keywords are chosen by the user.
23723 You may set up the list of possible keywords here, or you may add keywords
23724 from the Flag Details screen that you
23725 can get to after typing the
23726 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
23727 command.
23728 After the keywords have been defined,
23729 then you use the <A HREF="h_common_flag">Flag command</A>
23730 to set or clear the keywords in each message.
23731 The behavior of the flag command may be modified by using the
23732 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
23733 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
23735 <P>
23736 Keywords may be used when Selecting messages (Select Keyword).
23737 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
23738 Filter Rules may be used to set keywords automatically.
23739 Keywords may be displayed as part of the Subject of a message by using
23740 the SUBJKEY or SUBJKEYINIT tokens in the
23741 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
23742 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
23743 option may be used to modify the display of keywords using
23744 SUBJKEY and SUBJKEYINIT slightly.
23745 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
23746 screen by using the KEY or KEYINIT tokens.
23747 It is also possible to color keywords in the index using the
23748 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
23749 Keywords are not supported by all mail servers.
23751 <P>
23752 You may give keywords nicknames if you wish.
23753 If the keyword definition you type in contains a SPACE character, then the
23754 actual value of the keyword is everything after the last SPACE and the
23755 nickname for that keyword is everything before the last SPACE.
23756 For example, suppose you are trying to interoperate with another email program
23757 that uses a particular keyword with an unpleasant name.
23758 Maybe it uses a keyword called
23759 <P>
23760 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
23761 <P>
23762 but for you that keyword means that the message is work-related.
23763 You could define a keyword to have the value
23764 <P>
23765 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
23766 <P>
23767 and then you would use the name "Work" when dealing with
23768 that keyword in Alpine.
23769 If you defined it as
23770 <P>
23771 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
23772 <P>
23773 the nickname would be everything before the last SPACE, that is the nickname
23774 would be "My Work".
23775 <P>
23776 Some commonly used keywords begin with dollar signs.
23777 This presents a slight complication, because the dollar sign is normally used
23778 to signify
23779 <A HREF="h_news_config">environment variable expansion</A>
23780 in the Alpine configuration.
23781 In order to specify a keyword that begins with a dollar sign you must
23782 precede the dollar sign with a second dollar sign to escape its special
23783 meaning.
23784 For example, if you want to include the keyword
23785 <P>
23786 <CENTER><SAMP>$Label1</SAMP></CENTER>
23787 <P>
23788 as one of your possible keywords, you must enter the text
23789 <P>
23790 <CENTER><SAMP>$$Label1</SAMP></CENTER>
23791 <P>
23793 instead.
23794 <P>
23795 There are a couple limitations.
23796 First, not all servers support keywords.
23797 Second, some servers (including the IMAP server included with Alpine)
23798 have a per folder limit on the number of keywords that may be defined.
23799 This count commonly includes every keyword you have ever used in the
23800 folder, even if it is no longer being used.
23801 In other words, you can add keywords but you cannot remove them easily.
23802 If you have changed keywords over the life of a folder and find that
23803 you have reached such a limit, one possible solution might be to copy
23804 all of the messages to a newly created folder (using Alpine) and then
23805 delete the original and rename the new folder.
23806 The reason this might work is that only the keywords currently set in
23807 any of the messages will be used in the new folder, hopefully putting you
23808 under the limit.
23810 <P>
23811 <UL>
23812 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23813 </UL><P>
23814 <End of help on this topic>
23815 </BODY>
23816 </HTML>
23817 ====== h_config_alt_addresses =====
23818 <HTML>
23819 <HEAD>
23820 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
23821 </HEAD>
23822 <BODY>
23823 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
23825 This option provides a place for you to list alternate email addresses
23826 you may have.
23827 Each address in the list should be the actual email address part of an
23828 address, without the full name field or the angle brackets.
23829 For example:
23831 <P>
23832 <CENTER><SAMP>user@example.com</SAMP></CENTER>
23833 <P>
23835 The matching is case-insensitive, so this would match any of
23836 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
23837 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
23839 <P>
23840 If set, the option affects the behavior of the Reply
23841 command and the "+" symbol in the MESSAGE INDEX, which denotes that
23842 a message has been addressed specifically to you.
23844 <P>
23845 In the default INDEX display
23846 the personal name (or email address) of
23847 the person listed in the message's "From:" header
23848 field is usually displayed except when that address is yours or one of your
23849 alternate addresses.
23850 In that case you will usually see the name of
23851 the first person specified in the
23852 message's "To:" header field
23853 with the prefix "To: " prepended.
23855 <P>
23856 With respect to Reply, the reply-to-all option will exclude addresses
23857 listed here.
23859 <P>
23860 The feature
23861 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
23862 is somewhat related to this option.
23864 <P>
23865 In addition to a list of actual addresses,
23866 you may use regular expressions (as used with egrep with the ignore case flag)
23867 to describe the addresses you want to match.
23868 Alpine will somewhat arbitrarily interpret your entry as a regular
23869 expression if it contains any of the characters
23870 *, |, +, ?, {, [, ^, $, or \.
23871 Otherwise, it will be treated literally.
23872 The feature
23873 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
23874 may be used to turn off regular expression processing regardless of whether or not
23875 special characters appear in the entry.
23877 <P>
23878 A description of how regular expressions work is beyond the
23879 scope of this help text, but some examples follow.
23881 <P>
23882 The entry
23884 <P>
23885 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
23886 <P>
23888 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
23889 address with a domain name of <SAMP>example.com</SAMP> (such as
23890 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
23891 one of your alternate addresses.
23892 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
23893 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
23894 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
23895 Complicating things further, the dollar sign
23896 is special in the Alpine configuration (it signifies environment variable expansion)
23897 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
23898 Quotes around the whole expression will not escape the dollar sign successfully.
23899 So this example should look like
23901 <P>
23902 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
23903 <P>
23905 <P>
23906 The entry
23908 <P>
23909 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
23910 <P>
23912 would match
23913 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
23914 as <SAMP>fred@example.com</SAMP>.
23916 <P>
23917 You could match all addresses that look like
23918 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
23919 entry
23921 <P>
23922 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
23923 <P>
23925 Notice that you have to escape the plus sign with a backslash because plus
23926 is a special character in regular expressions.
23927 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
23928 the expression
23930 <P>
23931 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
23932 <P>
23934 would do it, but it would be easier to just add fred@example.com as a
23935 separate entry.
23937 <P>
23938 One more example, a match of all first-level subdomains, is given by
23940 <P>
23941 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
23942 <P>
23944 <P>
23945 Because the regular expression matching is based on an old library
23946 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
23947 but they should be close.
23949 <P>
23950 <UL>
23951 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23952 </UL><P>
23953 <End of help on this topic>
23954 </BODY>
23955 </HTML>
23956 ====== h_config_abook_formats =====
23957 <HTML>
23958 <HEAD>
23959 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
23960 </HEAD>
23961 <BODY>
23962 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
23964 This option specifies the format that address books are displayed in.
23965 Normally, address books are displayed with the nicknames in the first
23966 column, the fullnames in the second column, and addresses in the third
23967 column. The system figures out reasonable defaults for the widths of
23968 the columns. An address book may be given a different format by
23969 listing special tokens in the order you want them to display. The
23970 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
23971 So, for example, to get the default behavior you could list
23973 <P>
23974 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
23976 <P>
23977 (You can also use the token DEFAULT to get the default behavior for
23978 an address book format.)
23980 <P>
23981 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
23982 is a list, so if you have more than one address book you may have a
23983 separate format for each by putting its format at the corresponding
23984 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
23986 <P>
23988 Listed first are the personal address books, then the global address
23989 books. So, if you have two personal address books and one global
23990 address book, you may have up to three formats in the
23991 "<!--#echo var="VAR_addressbook-formats"-->" list. If
23992 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
23993 are address books, the last element is used repeatedly.
23995 <P>
23997 Each of the tokens may also be optionally followed by parentheses with
23998 either a number or a percentage inside the parentheses. For example,
23999 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
24000 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
24001 of the available space (the screen width minus the space for
24002 inter-column spaces) to the fullnames column, while plain
24003 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
24004 reasonable number of columns.
24006 <P>
24007 There are always 2 spaces between every column, so if you use
24008 fixed column widths (like 13) you should remember to take that into
24009 account.
24011 <P>
24012 <UL>
24013 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24014 </UL><P>
24015 <End of help on this topic>
24016 </BODY>
24017 </HTML>
24018 ====== h_config_set_index_format =====
24019 <HTML>
24020 <HEAD>
24021 <TITLE>Set Index Format</TITLE>
24022 </HEAD>
24023 <BODY>
24024 <H1>Set Index Format</H1>
24026 This option is used to customize the content of lines in the
24027 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
24028 This action works exactly like the regular
24029 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
24030 except that you can have a folder-specific value for it if you specify it here.
24031 Consult the help for
24032 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
24033 for more information.
24035 <P>
24036 <UL>
24037 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24038 </UL><P>
24039 <End of help on this topic>
24040 </BODY>
24041 </HTML>
24042 ====== h_config_index_format =====
24043 <HTML>
24044 <HEAD>
24045 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
24046 </HEAD>
24047 <BODY>
24048 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
24050 This option is used to customize the content of lines in the
24051 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
24052 to convey some amount of immediately relevant information about each
24053 message in the current folder.
24054 <P>
24056 Alpine provides a pre-defined set of informational fields with
24057 reasonable column widths automatically computed. You can, however,
24058 replace this default set by listing special tokens in the order you
24059 want them displayed.
24060 <P>
24062 The list of available tokens is
24063 <A HREF="h_index_tokens">here</A>.
24064 <P>
24066 Spaces are used to separate listed tokens. Additionally, you can
24067 specify how much of the screen's width the token's associated data
24068 should occupy on the index line by appending to the token a pair of
24069 parentheses enclosing either a number or percentage. For example,
24070 "SUBJECT(13)" means to allocate 13 characters of space to the subject
24071 column, and "SUBJECT(20%)" means to
24072 allocate 20% of the available space
24073 to the subjects column, while plain "SUBJECT" means the system will
24074 attempt to figure out a reasonable amount of space.
24075 <P>
24077 There is always one space between every pair of columns, so if you use fixed
24078 column widths (like 13) you should remember to take that into account.
24079 Several of the fields are virtually fixed-width, so it doesn't make
24080 much sense to specify the width for them. The fields STATUS,
24081 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
24082 and DESCRIPSIZE all fall into that category.
24083 You <EM>may</EM> specify widths for those if you wish, but
24084 you're probably better off letting the system pick those widths. <P>
24086 <P>
24087 The default is equivalent to:
24089 <P>
24090 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
24092 <P>
24093 This means that the four fields without percentages will be allocated
24094 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
24095 the from and subject fields. If one of those two fields is specified
24096 as a percentage and the other is left for the system to choose, then
24097 the percentage is taken as an absolute percentage of the screen, not
24098 of the space remaining after allocating the first four columns. It
24099 doesn't usually make sense to do it that way. If you leave off all
24100 the widths, then the subject and from fields (if both are present) are
24101 allocated space in a 2 to 1 ratio, which is almost exactly the same as
24102 the default.
24104 <P>
24105 What you are most likely to do with this configuration option is to
24106 specify which fields appear at all, which order they appear in, and the
24107 percentage of screen that is used for the from and subject fields if you
24108 don't like the 2 to 1 default.
24110 <P>
24111 If you want to retain the default format that Pine 4.64 had, use
24113 <P>
24114 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
24115 <P>
24116 <EM>and</EM> set the feature
24117 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
24118 <UL>
24119 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24120 </UL><P>
24121 <End of help on this topic>
24122 </BODY>
24123 </HTML>
24124 ====== h_config_reply_intro =====
24125 <HTML>
24126 <HEAD>
24127 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
24128 </HEAD>
24129 <BODY>
24130 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
24132 This option is used to customize the content of the introduction line
24133 that is included when replying to a message and including the original
24134 message in the reply.
24135 The normal default (what you will get if you delete this variable) looks
24136 something like:
24137 <P>
24138 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
24139 <P>
24140 where the day of the week is only included if it is available in the
24141 original message.
24142 You can replace this default with text of your own.
24143 The text may contain tokens that are replaced with text
24144 that depends on the message you are replying to.
24145 For example, the default is equivalent to:
24146 <P>
24147 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24148 <P>
24150 Since this variable includes regular text mixed with special tokens
24151 the tokens have to be surrounded by underscore characters.
24152 For example, to use the token "<SAMP>PREFDATE</SAMP>"
24153 you would need to use "<SAMP>_PREFDATE_</SAMP>",
24154 not "<SAMP>PREFDATE</SAMP>".
24155 <P>
24156 The list of available tokens is
24157 <A HREF="h_index_tokens">here</A>.
24159 <P>
24160 By default, the text is all on a single line and is followed by a blank line.
24161 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
24162 than 80 characters when replying to a particular message, it is shortened.
24163 However, if you use the token
24164 <P>
24165 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
24166 <P>
24168 anywhere in the value, no end of line or blank line is appended, and no
24169 shortening is done.
24170 The _NEWLINE_ token may be used to get rid of the blank line following
24171 the text, to add more blank lines, or to form a multi-line
24172 "<!--#echo var="VAR_reply-leadin"-->".
24173 To clarify how _NEWLINE_ works recall that the default value is:
24174 <P>
24175 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24176 <P>
24178 That is equivalent to
24179 <P>
24180 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
24181 <P>
24183 In the former case, two newlines are added automatically because
24184 no _NEWLINE_ token appears in the value of the option (for backwards
24185 compatibility). In the latter case, the newlines are explicit.
24186 If you want to remove the blank line that follows the
24187 "<!--#echo var="VAR_reply-leadin"-->" text use a single
24188 _NEWLINE_ token like
24189 <P>
24190 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
24191 <P>
24193 Because of the backwards compatibility problem, it is not possible to
24194 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
24195 and that will cause the automatic adding of two newlines!
24196 If you want, you may embed newlines in the middle of the text, as well,
24197 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
24199 <P>
24200 By default, no attempt is made to localize the date.
24201 If you prefer a localized form you may find that one of the tokens
24202 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
24203 If you want more control one of the many other date tokens, such as _DATEISO_,
24204 might be better.
24206 <P>
24207 For the adventurous, there is a way to conditionally include text based
24208 on whether or not a token would result in specific replacement text.
24209 For example, you could include some text based on whether or not
24210 the _NEWS_ token would result in any newsgroups if it was used.
24211 It's explained in detail
24212 <A HREF="h_reply_token_conditionals">here</A>.
24214 <P>
24215 In the very unlikely event that you want to include a literal token
24216 in the introduction line you must precede it with a backslash character.
24217 For example,
24218 <P>
24219 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
24220 <P>
24221 would produce something like
24222 <P>
24223 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
24224 <P>
24225 It is not possible to have a literal backslash followed by an expanded token.
24226 <P>
24227 <UL>
24228 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24229 </UL><P>
24230 <End of help on this topic>
24231 </BODY>
24232 </HTML>
24233 ====== h_config_remote_abook_history =====
24234 <HTML>
24235 <HEAD>
24236 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
24237 </HEAD>
24238 <BODY>
24239 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
24241 Sets how many extra copies of
24242 remote address book
24243 data will be kept in each remote address book folder.
24244 The default is three.
24245 These extra copies are simply old versions of the data. Each time a change
24246 is made a new copy of the address book data is appended to the folder. Old
24247 copies are trimmed, if possible, when Alpine exits.
24248 An old copy can be put back into use by
24249 deleting and expunging newer versions of the data from the folder.
24250 Don't delete the first message from the folder. It is a special header
24251 message for the remote address book and it must be there.
24252 This is to prevent regular folders from being used as remote address book
24253 folders and having their data destroyed.
24254 <P>
24255 This option is also used to determine how many extra copies of remote
24256 Alpine configuration files are kept.
24257 <P>
24258 <UL>
24259 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24260 </UL><P>
24261 <End of help on this topic>
24262 </BODY>
24263 </HTML>
24264 ====== h_config_remote_abook_validity =====
24265 <HTML>
24266 <HEAD>
24267 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
24268 </HEAD>
24269 <BODY>
24270 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
24272 Sets the minimum number of minutes that a
24273 remote address book will be considered up to date.
24274 Whenever an entry contained in a remote address book is used,
24275 if more than this many minutes have
24276 passed since the last check the remote server will be queried to see if the
24277 address book has changed.
24278 If it has changed, the local copy is updated.
24279 The default value is five minutes.
24280 The special value of -1 means never check.
24281 The special value of zero means only check when the address book is first
24282 opened.
24283 <P>
24284 No matter what the value, the validity check is always done when the
24285 address book is about to be changed by the user.
24286 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
24287 while in the address book maintenance screen for the remote address book.
24288 <P>
24289 <UL>
24290 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24291 </UL><P>
24292 <End of help on this topic>
24293 </BODY>
24294 </HTML>
24295 ====== h_config_user_input_timeo =====
24296 <HTML>
24297 <HEAD>
24298 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
24299 </HEAD>
24300 <BODY>
24301 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
24303 If this is set to an integer greater than zero, then this is the number
24304 of <EM>hours</EM> to wait for user input before Alpine times out.
24305 If Alpine is
24306 in the midst of composing a message or is waiting for user response to
24307 a question, then it will not timeout.
24308 However, if Alpine is sitting idle waiting for
24309 the user to tell it what to do next and the user does not give any
24310 input for this many hours, Alpine will exit.
24311 No expunging or moving of read
24312 messages will take place.
24313 It will exit similarly to the way it would exit
24314 if it received a hangup signal.
24315 This may be useful for cleaning up unused Alpine sessions that have been
24316 forgotten by their owners.
24317 The Alpine developers envision system administrators
24318 setting this to a value of several hours (24?) so that it won't surprise
24319 a user who didn't want to be disconnected.
24320 <P>
24321 <UL>
24322 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24323 </UL><P>
24324 <End of help on this topic>
24325 </BODY>
24326 </HTML>
24327 ====== h_config_ssh_open_timeo =====
24328 <HTML>
24329 <HEAD>
24330 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
24331 </HEAD>
24332 <BODY>
24333 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
24335 Sets the time in seconds that Alpine will
24336 attempt to open a UNIX secure shell connection.
24337 The default is 15, the minimum non-zero value is 5,
24338 and the maximum is unlimited. If this is set to zero ssh connections
24339 will be completely disabled.
24340 <P>
24341 <UL>
24342 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24343 </UL><P>
24344 <End of help on this topic>
24345 </BODY>
24346 </HTML>
24347 ====== h_config_rsh_open_timeo =====
24348 <HTML>
24349 <HEAD>
24350 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
24351 </HEAD>
24352 <BODY>
24353 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
24355 Sets the time in seconds that Alpine will
24356 attempt to open a UNIX remote shell connection.
24357 The default is 15, the minimum non-zero value is 5,
24358 and the maximum is unlimited. If this is set to zero rsh connections
24359 will be completely disabled.
24360 This might be useful if rsh connections will never work in your environment
24361 but are causing delays due to firewalls or some other reason.
24362 <P>
24363 <UL>
24364 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24365 </UL><P>
24366 <End of help on this topic>
24367 </BODY>
24368 </HTML>
24369 ====== h_config_tcp_open_timeo =====
24370 <HTML>
24371 <HEAD>
24372 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
24373 </HEAD>
24374 <BODY>
24375 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
24377 Sets the time in seconds that Alpine will
24378 attempt to open a network connection. The default is 30, the minimum is 5,
24379 and the maximum is system defined (typically 75). If a connection has not
24380 completed within this many seconds Alpine will give up and consider it a
24381 failed connection.
24382 <P>
24383 <UL>
24384 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24385 </UL><P>
24386 <End of help on this topic>
24387 </BODY>
24388 </HTML>
24389 ====== h_config_tcp_readwarn_timeo =====
24390 <HTML>
24391 <HEAD>
24392 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
24393 </HEAD>
24394 <BODY>
24395 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
24397 Sets the time in seconds that Alpine will
24398 wait for a network read before warning you that things are moving slowly
24399 and possibly giving you the option to break the connection.
24400 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24401 1000 seconds.
24402 <P>
24403 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24404 <P>
24405 <UL>
24406 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24407 </UL><P>
24408 <End of help on this topic>
24409 </BODY>
24410 </HTML>
24411 ====== h_config_tcp_writewarn_timeo =====
24412 <HTML>
24413 <HEAD>
24414 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24415 </HEAD>
24416 <BODY>
24417 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24419 Sets the time in seconds that Alpine will
24420 wait for a network write before warning you that things are moving slowly
24421 and possibly giving you the option to break the connection.
24422 The default is 0 which means it is unset. If set to a non-zero value, the
24423 minimum is 5 and the maximum is 1000.
24424 <P>
24425 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24426 <P>
24427 <UL>
24428 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24429 </UL><P>
24430 <End of help on this topic>
24431 </BODY>
24432 </HTML>
24433 ====== h_config_tcp_query_timeo =====
24434 <HTML>
24435 <HEAD>
24436 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24437 </HEAD>
24438 <BODY>
24439 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24441 When Alpine times out a network read or write it will normally just display
24442 a message saying "Still waiting".
24443 However, if enough time has elapsed since it started waiting it will offer
24444 to let you break the connection.
24445 That amount of time is set by this option, which defaults to 60 seconds,
24446 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24447 <P>
24448 <UL>
24449 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24450 </UL><P>
24451 <End of help on this topic>
24452 </BODY>
24453 </HTML>
24454 ====== h_config_incoming_folders =====
24455 <HTML>
24456 <HEAD>
24457 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24458 </HEAD>
24459 <BODY>
24460 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24462 This is a list of one or more folders other than <EM>INBOX</EM> that
24463 may receive new messages.
24464 It is related to the
24465 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24466 feature.
24467 This variable is normally manipulated with the Add, Delete, and Rename
24468 commands in the FOLDER LIST for the Incoming Message Folders collection.
24469 <P>
24470 <UL>
24471 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24472 </UL><P>
24473 <End of help on this topic>
24474 </BODY>
24475 </HTML>
24476 ====== h_config_folder_spec =====
24477 <HTML>
24478 <HEAD>
24479 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24480 </HEAD>
24481 <BODY>
24482 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24484 This is a list of one or more collections where saved mail is stored.
24485 The first collection in this list is the default
24486 collection for <EM>Save</EM>s,
24487 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24488 <P>
24489 This variable is normally manipulated using the Setup/collectionList screen.
24490 <P>
24491 <UL>
24492 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24493 </UL><P>
24494 <End of help on this topic>
24495 </BODY>
24496 </HTML>
24497 ====== h_config_news_spec =====
24498 <HTML>
24499 <HEAD>
24500 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24501 </HEAD>
24502 <BODY>
24503 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24505 This is a list of collections where news folders are located.
24506 <P>
24507 This variable is normally manipulated using the Setup/collectionList screen.
24508 <P>
24509 <UL>
24510 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24511 </UL><P>
24512 <End of help on this topic>
24513 </BODY>
24514 </HTML>
24515 ====== h_config_address_book =====
24516 <HTML>
24517 <HEAD>
24518 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24519 </HEAD>
24520 <BODY>
24521 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24523 A list of personal address books.
24524 Each entry in the list is an
24525 optional nickname followed by a pathname or file name relative to the home
24526 directory.
24527 The nickname is separated from the rest of the line with whitespace.
24528 Instead of a local pathname or file name, a remote folder name can be given.
24529 This causes the address book to
24530 be a Remote address book.
24531 <P>
24532 Use the Setup/AddressBook screen to modify this variable.
24533 <P>
24534 <UL>
24535 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24536 </UL><P>
24537 <End of help on this topic>
24538 </BODY>
24539 </HTML>
24540 ====== h_config_glob_addrbook =====
24541 <HTML>
24542 <HEAD>
24543 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24544 </HEAD>
24545 <BODY>
24546 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24548 A list of shared address books. Each entry in the list is an
24549 optional nickname followed by a pathname or file name relative to the home
24550 directory.
24551 A SPACE character separates the nickname from the rest of the line.
24552 Instead of a local pathname or file name, a remote folder name can be given.
24553 This causes the address book to
24554 be a Remote address book.
24555 Global address books are
24556 defined to be ReadOnly.
24557 <P>
24558 Use the Setup/AddressBook screen to modify this variable.
24559 <P>
24560 <UL>
24561 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24562 </UL><P>
24563 <End of help on this topic>
24564 </BODY>
24565 </HTML>
24566 ====== h_config_last_vers =====
24567 <HTML>
24568 <HEAD>
24569 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24570 </HEAD>
24571 <BODY>
24572 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24574 This is set automatically by Alpine.
24575 It is used to keep track of the last version of Alpine that
24576 was run by the user.
24577 Whenever the version number increases, a new version message is printed out.
24578 This may not be set in the system-wide configuration files.
24579 <P>
24580 <UL>
24581 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24582 </UL><P>
24583 <End of help on this topic>
24584 </BODY>
24585 </HTML>
24586 ====== h_config_printer =====
24587 <HTML>
24588 <HEAD>
24589 <TITLE>OPTION: Printer</TITLE>
24590 </HEAD>
24591 <BODY>
24592 <H1>OPTION: Printer</H1>
24594 Your default printer selection.
24595 <P>
24596 Use the Setup/Printer screen to modify this variable.
24597 <P>
24598 <UL>
24599 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24600 </UL><P>
24601 <End of help on this topic>
24602 </BODY>
24603 </HTML>
24604 ====== h_config_print_cat =====
24605 <HTML>
24606 <HEAD>
24607 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24608 </HEAD>
24609 <BODY>
24610 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24612 This is an internal Alpine variable.
24613 It will be equal to 1, 2, or 3 depending on whether the default printer is
24614 attached, standard, or a personal print command.
24615 <P>
24616 Use the Setup/Printer screen to modify this variable.
24617 <P>
24618 <UL>
24619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24620 </UL><P>
24621 <End of help on this topic>
24622 </BODY>
24623 </HTML>
24624 ====== h_config_print_command =====
24625 <HTML>
24626 <HEAD>
24627 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24628 </HEAD>
24629 <BODY>
24630 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24632 List of personal print commands.
24633 <P>
24634 Use the Setup/Printer screen to modify this variable.
24635 <P>
24636 <UL>
24637 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24638 </UL><P>
24639 <End of help on this topic>
24640 </BODY>
24641 </HTML>
24642 ====== h_config_pat_old =====
24643 <HTML>
24644 <HEAD>
24645 <TITLE>OPTION: Patterns</TITLE>
24646 </HEAD>
24647 <BODY>
24648 <H1>OPTION: Patterns</H1>
24650 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24651 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24652 and Patterns-Other.
24653 Patterns-Scores and Patterns-Filters have been replaced since then by
24654 Patterns-Scores2 and Patterns-Filters2.
24655 <P>
24656 Use the Setup/Rules screens to modify these variable.
24657 <P>
24658 <UL>
24659 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24660 </UL><P>
24661 <End of help on this topic>
24662 </BODY>
24663 </HTML>
24664 ====== h_config_pat_roles =====
24665 <HTML>
24666 <HEAD>
24667 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
24668 </HEAD>
24669 <BODY>
24670 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
24672 List of rules used for roles.
24673 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
24674 other options.
24675 <P>
24676 Use the Setup/Rules/Roles screen to modify this variable.
24677 <P>
24678 <UL>
24679 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24680 </UL><P>
24681 <End of help on this topic>
24682 </BODY>
24683 </HTML>
24684 ====== h_config_pat_filts =====
24685 <HTML>
24686 <HEAD>
24687 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
24688 </HEAD>
24689 <BODY>
24690 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
24692 List of rules used for filters.
24693 <P>
24694 Use the Setup/Rules/Filters screen to modify this variable.
24695 <P>
24696 <UL>
24697 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24698 </UL><P>
24699 <End of help on this topic>
24700 </BODY>
24701 </HTML>
24702 ====== h_config_pat_scores =====
24703 <HTML>
24704 <HEAD>
24705 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
24706 </HEAD>
24707 <BODY>
24708 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
24710 List of rules used for scoring.
24711 <P>
24712 Use the Setup/Rules/SetScores screen to modify this variable.
24713 <P>
24714 <UL>
24715 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24716 </UL><P>
24717 <End of help on this topic>
24718 </BODY>
24719 </HTML>
24720 ====== h_config_pat_other =====
24721 <HTML>
24722 <HEAD>
24723 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
24724 </HEAD>
24725 <BODY>
24726 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
24728 List of rules used for miscellaneous configuration.
24729 <P>
24730 Use the Setup/Rules/Other screen to modify this variable.
24731 <P>
24732 <UL>
24733 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24734 </UL><P>
24735 <End of help on this topic>
24736 </BODY>
24737 </HTML>
24738 ====== h_config_pat_incols =====
24739 <HTML>
24740 <HEAD>
24741 <TITLE>OPTION: patterns-indexcolors</TITLE>
24742 </HEAD>
24743 <BODY>
24744 <H1>OPTION: patterns-indexcolors</H1>
24746 List of rules used for coloring lines in the index.
24747 <P>
24748 Use the Setup/Rules/Indexcolor screen to modify this variable.
24749 <P>
24750 <UL>
24751 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24752 </UL><P>
24753 <End of help on this topic>
24754 </BODY>
24755 </HTML>
24756 ====== h_config_pat_srch =====
24757 <HTML>
24758 <HEAD>
24759 <TITLE>OPTION: patterns-search</TITLE>
24760 </HEAD>
24761 <BODY>
24762 <H1>OPTION: patterns-search</H1>
24764 List of rules used only for searching with the Select command in the MESSAGE INDEX.
24765 <P>
24766 Use the Setup/Rules/searCh screen to modify this variable.
24767 <P>
24768 <UL>
24769 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24770 </UL><P>
24771 <End of help on this topic>
24772 </BODY>
24773 </HTML>
24774 ====== h_config_font_name =====
24775 <HTML>
24776 <HEAD>
24777 <TITLE>OPTION: Font Name</TITLE>
24778 </HEAD>
24779 <BODY>
24780 <H1>OPTION: Font Name</H1>
24782 PC-Alpine only.
24783 <P>
24784 Name of normal font.
24785 <P>
24786 Use the pulldown Config menu to modify this variable.
24787 <P>
24788 <UL>
24789 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24790 </UL><P>
24791 <End of help on this topic>
24792 </BODY>
24793 </HTML>
24794 ====== h_config_font_size =====
24795 <HTML>
24796 <HEAD>
24797 <TITLE>OPTION: Font Size</TITLE>
24798 </HEAD>
24799 <BODY>
24800 <H1>OPTION: Font Size</H1>
24802 PC-Alpine only.
24803 <P>
24804 Size of normal font.
24805 <P>
24806 Use the pulldown Config menu to modify this variable.
24807 <P>
24808 <UL>
24809 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24810 </UL><P>
24811 <End of help on this topic>
24812 </BODY>
24813 </HTML>
24814 ====== h_config_font_style =====
24815 <HTML>
24816 <HEAD>
24817 <TITLE>OPTION: Font Style</TITLE>
24818 </HEAD>
24819 <BODY>
24820 <H1>OPTION: Font Style</H1>
24822 PC-Alpine only.
24823 <P>
24824 Style of normal font.
24825 <P>
24826 Use the pulldown Config menu to modify this variable.
24827 <P>
24828 <UL>
24829 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24830 </UL><P>
24831 <End of help on this topic>
24832 </BODY>
24833 </HTML>
24834 ====== h_config_font_char_set =====
24835 <HTML>
24836 <HEAD>
24837 <TITLE>OPTION: Font Character Set</TITLE>
24838 </HEAD>
24839 <BODY>
24840 <H1>OPTION: Font Character Set</H1>
24842 PC-Alpine only.
24843 <P>
24844 Character set of normal font.
24845 <P>
24846 Use the pulldown Config menu to modify this variable.
24847 <P>
24848 <UL>
24849 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24850 </UL><P>
24851 <End of help on this topic>
24852 </BODY>
24853 </HTML>
24854 ====== h_config_print_font_name =====
24855 <HTML>
24856 <HEAD>
24857 <TITLE>OPTION: Print-Font-Name</TITLE>
24858 </HEAD>
24859 <BODY>
24860 <H1>OPTION: Print-Font-Name</H1>
24862 PC-Alpine only.
24863 <P>
24864 Name of printer font.
24865 <P>
24866 Use the pulldown Config menu to modify this variable.
24867 <P>
24868 <UL>
24869 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24870 </UL><P>
24871 <End of help on this topic>
24872 </BODY>
24873 </HTML>
24874 ====== h_config_print_font_size =====
24875 <HTML>
24876 <HEAD>
24877 <TITLE>OPTION: Print-Font-Size</TITLE>
24878 </HEAD>
24879 <BODY>
24880 <H1>OPTION: Print-Font-Size</H1>
24882 PC-Alpine only.
24883 <P>
24884 Size of printer font.
24885 <P>
24886 Use the pulldown Config menu to modify this variable.
24887 <P>
24888 <UL>
24889 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24890 </UL><P>
24891 <End of help on this topic>
24892 </BODY>
24893 </HTML>
24894 ====== h_config_print_font_style =====
24895 <HTML>
24896 <HEAD>
24897 <TITLE>OPTION: Print-Font-Style</TITLE>
24898 </HEAD>
24899 <BODY>
24900 <H1>OPTION: Print-Font-Style</H1>
24902 PC-Alpine only.
24903 <P>
24904 Style of printer font.
24905 <P>
24906 Use the pulldown Config menu to modify this variable.
24907 <P>
24908 <UL>
24909 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24910 </UL><P>
24911 <End of help on this topic>
24912 </BODY>
24913 </HTML>
24914 ====== h_config_print_font_char_set =====
24915 <HTML>
24916 <HEAD>
24917 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
24918 </HEAD>
24919 <BODY>
24920 <H1>OPTION: Print-Font-Char-Set</H1>
24922 PC-Alpine only.
24923 <P>
24924 Character set of printer font.
24925 <P>
24926 Use the pulldown Config menu to modify this variable.
24927 <P>
24928 <UL>
24929 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24930 </UL><P>
24931 <End of help on this topic>
24932 </BODY>
24933 </HTML>
24934 ====== h_config_window_position =====
24935 <HTML>
24936 <HEAD>
24937 <TITLE>OPTION: Window-Position</TITLE>
24938 </HEAD>
24939 <BODY>
24940 <H1>OPTION: Window-Position</H1>
24942 PC-Alpine only.
24943 <P>
24944 Position on the screen of the Alpine window.
24945 <P>
24946 Alpine normally maintains this variable itself, and it is set automatically.
24947 This variable is provided to those who wish to use the same window position
24948 across different machines from the same configuration.
24949 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
24950 must also be set for this setting to be used.
24951 <P>
24952 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
24953 C is the number of columns, R is the number of rows, and X and Y specify the
24954 top left corner of the window.
24955 <P>
24956 <UL>
24957 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24958 </UL><P>
24959 <End of help on this topic>
24960 </BODY>
24961 </HTML>
24962 ====== h_config_cursor_style =====
24963 <HTML>
24964 <HEAD>
24965 <TITLE>OPTION: Cursor Style</TITLE>
24966 </HEAD>
24967 <BODY>
24968 <H1>OPTION: Cursor Style</H1>
24970 PC-Alpine only.
24971 <P>
24972 Cursor style.
24973 <P>
24974 Use the pulldown Config menu to modify this variable.
24975 <P>
24976 <UL>
24977 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24978 </UL><P>
24979 <End of help on this topic>
24980 </BODY>
24981 </HTML>
24982 ====== h_config_ldap_servers =====
24983 <HTML>
24984 <HEAD>
24985 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
24986 </HEAD>
24987 <BODY>
24988 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
24990 List of LDAP servers and associated data.
24991 <P>
24992 Use the Setup/Directory screen to modify this variable.
24993 <P>
24994 <UL>
24995 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24996 </UL><P>
24997 <End of help on this topic>
24998 </BODY>
24999 </HTML>
25000 ====== h_config_sendmail_path =====
25001 <HTML>
25002 <HEAD>
25003 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
25004 </HEAD>
25005 <BODY>
25006 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
25008 This names the path to an
25009 alternative program, and any necessary arguments, to be used in posting
25010 mail messages. See the Technical notes for more information.
25011 <P>
25012 <UL>
25013 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25014 </UL><P>
25015 <End of help on this topic>
25016 </BODY>
25017 </HTML>
25018 ====== h_config_oper_dir =====
25019 <HTML>
25020 <HEAD>
25021 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
25022 </HEAD>
25023 <BODY>
25024 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
25026 This names the root of the
25027 tree to which you are restricted when reading and writing folders and
25028 files. It is usually used in the system-wide,
25029 <EM>fixed</EM> configuration file.
25030 <P>
25031 <UL>
25032 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25033 </UL><P>
25034 <End of help on this topic>
25035 </BODY>
25036 </HTML>
25037 ====== h_config_rshpath =====
25038 <HTML>
25039 <HEAD>
25040 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
25041 </HEAD>
25042 <BODY>
25043 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
25045 Sets the name of the command used to open a UNIX remote shell
25046 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
25047 <P>
25048 <UL>
25049 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25050 </UL><P>
25051 <End of help on this topic>
25052 </BODY>
25053 </HTML>
25054 ====== h_config_rshcmd =====
25055 <HTML>
25056 <HEAD>
25057 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
25058 </HEAD>
25059 <BODY>
25060 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
25062 Sets the format of the command used to
25063 open a UNIX remote shell connection. The default is
25064 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25065 provided command. The first is for the command's pathname, the second is
25066 for the host to connnect to, the third is for the user to connect as, and
25067 the fourth is for the connection method (typically <CODE>imap</CODE>).
25068 <P>
25069 <UL>
25070 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25071 </UL><P>
25072 <End of help on this topic>
25073 </BODY>
25074 </HTML>
25075 ====== h_config_sshpath =====
25076 <HTML>
25077 <HEAD>
25078 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
25079 </HEAD>
25080 <BODY>
25081 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
25083 Sets the name of the command used to open a UNIX secure shell
25084 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
25085 <P>
25086 <UL>
25087 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25088 </UL><P>
25089 <End of help on this topic>
25090 </BODY>
25091 </HTML>
25092 ====== h_config_sshcmd =====
25093 <HTML>
25094 <HEAD>
25095 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
25096 </HEAD>
25097 <BODY>
25098 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
25100 Sets the format of the command used to
25101 open a UNIX secure shell connection. The default is
25102 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25103 provided command. The first is for the command's pathname, the second is
25104 for the host to connnect to, the third is for the user to connect as, and
25105 the fourth is for the connection method (typically <CODE>imap</CODE>).
25106 <P>
25107 <UL>
25108 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25109 </UL><P>
25110 <End of help on this topic>
25111 </BODY>
25112 </HTML>
25113 ====== h_config_new_ver_quell =====
25114 <HTML>
25115 <HEAD>
25116 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
25117 </HEAD>
25118 <BODY>
25119 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
25121 When a new version of Alpine is run for the first time it offers a
25122 special explanatory screen to the user upon startup. This option
25123 helps control when and if that special screen appears for users that
25124 have previously run Alpine. It takes as its value an Alpine version
25125 number. Alpine versions less than the specified value will supress this
25126 special screen while versions equal to or greater than that specified
25127 will behave normally.
25128 <P>
25129 <UL>
25130 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25131 </UL><P>
25132 <End of help on this topic>
25133 </BODY>
25134 </HTML>
25135 ====== h_config_disable_drivers =====
25136 <HTML>
25137 <HEAD>
25138 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
25139 </HEAD>
25140 <BODY>
25141 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
25143 This variable is a list of mail drivers that will be disabled.
25144 The candidates for disabling are listed below.
25145 There may be more in the future if you compile Alpine with
25146 a newer version of the c-client library.
25147 <P>
25149 <UL>
25150 <LI> mbox
25151 <LI> mbx
25152 <LI> mh
25153 <LI> mmdf
25154 <LI> mtx
25155 <LI> mx
25156 <LI> news
25157 <LI> phile
25158 <LI> tenex
25159 <LI> unix
25160 </UL>
25161 <P>
25163 The <EM>mbox</EM> driver enables the following behavior: if there is a
25164 file called <CODE>mbox</CODE>
25165 in your home directory, and if that file is either empty or in Unix mailbox
25166 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
25167 will automatically transfer mail from the system mail spool directory into the
25168 <CODE>mbox</CODE> file and
25169 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
25170 this will not happen.
25171 <P>
25173 It is not recommended to disable the driver that supports the system default
25174 mailbox format. On most non-SCO systems, that driver is the
25175 <EM>unix</EM> driver.
25176 On most SCO systems, it is the <EM>mmdf</EM> driver.
25177 The system default driver may be
25178 configured to something else on your system; check with your system manager
25179 for additional information.
25180 <P>
25182 It is most likely not very useful for you to disable any of the drivers other
25183 than possibly <EM>mbox</EM>.
25184 You could disable some of the others if you know for
25185 certain that you don't need them but the performance gain in doing so
25186 is very modest.
25187 <P>
25188 <UL>
25189 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25190 </UL><P>
25191 <End of help on this topic>
25192 </BODY>
25193 </HTML>
25194 ====== h_config_disable_auths =====
25195 <HTML>
25196 <HEAD>
25197 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
25198 </HEAD>
25199 <BODY>
25200 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
25202 This variable is a list of SASL (Simple Authentication and Security
25203 Layer) authenticators that will be disabled.
25204 SASL is a mechanism for
25205 authenticating to IMAP, POP3, SMTP, and other network servers.
25206 <P>
25208 Alpine matches its list of supported authenticators with the server to
25209 determine the most secure authenticator that is supported by both.
25210 If no matching authenticators are found, Alpine will revert to plaintext
25211 login (or, in the case of SMTP, will be unable to authenticate at all).
25212 <P>
25213 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
25214 <P>
25216 Normally, you will not disable any authenticators.
25217 There are two exceptions:
25218 <P>
25219 <OL>
25220 <LI> You use a broken server that advertises an authenticator,
25221 but does not actually implement it.
25222 <LI> You have a Kerberos-capable version of Alpine and the server is
25223 also Kerberos-capable, but you can not obtain Kerberos
25224 credentials on the server machine, thus you desire to disable
25225 GSSAPI (which in turn disables Alpine's Kerberos support).
25226 </OL>
25227 <P>
25228 It is never necessary to disable authenticators, since Alpine will try
25229 other authenticators before giving up.
25230 However, disabling the relevant authenticator avoids annoying error messages.
25231 <P>
25232 <UL>
25233 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25234 </UL><P>
25235 <End of help on this topic>
25236 </BODY>
25237 </HTML>
25238 ====== h_config_abook_metafile =====
25239 <HTML>
25240 <HEAD>
25241 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
25242 </HEAD>
25243 <BODY>
25244 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
25246 This is usually set by Alpine and is the name of a file
25247 that contains data about
25248 remote address books and remote configuration files.
25249 <P>
25250 <UL>
25251 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25252 </UL><P>
25253 <End of help on this topic>
25254 </BODY>
25255 </HTML>
25256 ====== h_config_composer_wrap_column =====
25257 <HTML>
25258 <HEAD>
25259 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
25260 </HEAD>
25261 <BODY>
25262 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
25265 This option specifies an aspect of Alpine's Composer. This gives the
25266 maximum width that auto-wrapped lines will have. It's also the maximum
25267 width of lines justified using the <A HREF="h_compose_justify">^J
25268 Justify</A> command. The normal default
25269 is "74". The largest allowed setting is normally "80"
25270 in order to
25271 prevent very long lines from being sent in outgoing mail. When the mail
25272 is actually sent, trailing spaces will be stripped off of each line.
25274 <P>
25275 <UL>
25276 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25277 </UL><P>
25278 <End of help on this topic>
25279 </BODY>
25280 </HTML>
25281 ====== h_config_deadlets =====
25282 <HTML>
25283 <HEAD>
25284 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
25285 </HEAD>
25286 <BODY>
25287 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
25290 This option affects Alpine's behavior when you cancel a message being
25291 composed. Alpine's usual behavior is to write the canceled message to
25292 a file named
25293 <!--chtml if pinemode="os_windows"-->
25294 "DEADLETR",
25295 <!--chtml else-->
25296 "dead.letter" in your home directory,
25297 <!--chtml endif-->
25298 overwriting any previous message.
25299 <P>
25300 If you set this option to a value higher than one, then that many copies
25301 of dead letter files will be saved.
25302 For example, if you set this option to "3" then you may have
25303 files named
25304 <!--chtml if pinemode="os_windows"-->
25305 "DEADLETR",
25306 "DEADLETR2", and
25307 "DEADLETR3".
25308 <!--chtml else-->
25309 "dead.letter",
25310 "dead.letter2", and
25311 "dead.letter3" in your home directory.
25312 <!--chtml endif-->
25313 In this example, the most recently cancelled message will be in
25314 <!--chtml if pinemode="os_windows"-->
25315 "DEADLETR",
25316 <!--chtml else-->
25317 "dead.letter",
25318 <!--chtml endif-->
25319 and the third most recently cancelled message will be in
25320 <!--chtml if pinemode="os_windows"-->
25321 "DEADLETR3".
25322 <!--chtml else-->
25323 "dead.letter3".
25324 <!--chtml endif-->
25325 The fourth most recently cancelled message will no longer be saved.
25327 <P>
25328 If you set this option to zero, then NO record of canceled messages is
25329 maintained.
25330 <P>
25331 If the feature
25332 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
25333 is set, that overrides whatever you set for this option.
25334 If this option had existed at the time, then the Quell feature would not
25335 have been added, but it is still there for backwards compatibility.
25336 So, in order for this option to have the desired effect, make sure the
25337 Quell feature is turned off.
25339 <P>
25340 <UL>
25341 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25342 </UL><P>
25343 <End of help on this topic>
25344 </BODY>
25345 </HTML>
25346 ====== h_config_maxremstream =====
25347 <HTML>
25348 <HEAD>
25349 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
25350 </HEAD>
25351 <BODY>
25352 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
25354 This option affects low-level behavior of Alpine.
25355 The default value for this option is <EM>3</EM>.
25356 If your INBOX is accessed using the IMAP protocol
25357 from an IMAP server, that connection is kept open throughout the
25358 duration of your Alpine session, independent of the value of this option.
25359 The same is true of any
25360 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25361 you have defined.
25362 This option controls Alpine's behavior when connecting to remote IMAP folders
25363 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
25364 It specifies the maximum number of remote IMAP connections (other than
25365 those mentioned above) that Alpine will use for accessing the rest of your
25366 folders.
25367 If you set this option to zero, you will turn off most remote connection
25368 re-use.
25369 It's difficult to understand exactly what this option does, and it is usually
25370 fine to leave it set to its default value.
25371 It is probably more likely that you will be interested in setting the
25372 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
25373 instead of changing the value of this option.
25374 A slightly longer explanation of what is going on with this option
25375 is given in the next paragraphs.
25377 <P>
25378 There are some time costs involved in opening and closing remote IMAP
25379 folders, the main costs being the time you have to wait for the connection
25380 to the server and the time for the folder to open.
25381 Opening a folder may involve not only the time the server takes to do its
25382 processing but time that Alpine uses to do filtering.
25383 These times can vary widely.
25384 They depend on how loaded the server is, how large
25385 the folder being opened is, and how you set up filtering, among other things.
25386 Once Alpine has opened a connection to a particular folder, it will attempt
25387 to keep that connection open in case you use it again.
25388 In order to do this,
25389 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
25390 this option) IMAP connections you have alloted for this purpose.
25391 <P>
25392 For example, suppose the value of this option is set to "2".
25393 If your INBOX is accessed on a remote server using the IMAP protocol, that
25394 doesn't count as one of the remote connections but it is always kept open.
25395 If you then open another IMAP folder, that would be your first
25396 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
25397 If you open a third folder the second will be left open, in case you
25398 return to it.
25399 You won't be able to tell it has been left open.
25400 It will appear to be closed when you leave the folder but the connection
25401 will remain in the background.
25402 Now suppose you go back to the second folder (the first folder after the
25403 INBOX).
25404 A connection to that folder is still open so you won't have to wait
25405 for the startup time to open it.
25406 Meanwhile, the connection to the third folder will be left behind.
25407 Now, if you open a fourth folder, you will bump into the
25408 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25409 than INBOX and you have the option set to "2".
25410 The connection that is being used for
25411 the third folder will be re-used for this new fourth folder.
25412 If you go back to the third folder after this, it is no longer already
25413 connected when you get there.
25414 You'll still save some time since Alpine will re-use the connection to the
25415 fourth folder and you have already logged in on that connection,
25416 but the folder will have to be re-opened from scratch.
25417 <P>
25418 If a folder is large and the startup cost is dominated by the time it takes
25419 to open that folder or to run filters on it, then it will pay to make the
25420 value of this option large enough to keep it open.
25421 On the other hand, if you only revisit a handful of folders or if
25422 the folders are small, then it might
25423 make more sense to keep this number small so that the reconnect
25424 time (the time to start up a new connection and authenticate)
25425 is eliminated instead.
25426 <P>
25427 You may also need to consider the impact on the server.
25428 On the surface, a larger number here may cause a larger impact on the
25429 server, since you will have more connections open to the server.
25430 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25431 associated with reopening a folder, but the <EM>server</EM> will be
25432 avoiding those costs as well.
25433 <P>
25434 When twenty five minutes pass without any active use of an IMAP connection
25435 being saved for possible re-use, that connection will be shut down,
25437 <P>
25438 <UL>
25439 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25440 </UL><P>
25441 <End of help on this topic>
25442 </BODY>
25443 </HTML>
25444 ====== h_config_permlocked =====
25445 <HTML>
25446 <HEAD>
25447 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25448 </HEAD>
25449 <BODY>
25450 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25452 This option affects low-level behavior of Alpine.
25453 There is no default value for this option.
25454 It is related to the options
25455 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25456 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25457 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25459 <P>
25460 Note: changes made to this list take effect the next time you open a
25461 folder in the list.
25463 <P>
25464 This is a list of folders that will be permanently kept open once they
25465 are first opened.
25466 The names in this list may be either the nickname of an Incoming folder
25467 or the full technical specification of a folder.
25468 The folders in this list need not be remote IMAP folders, they could usefully
25469 be local folders, as well.
25470 If a folder in the list is a newsgroup or is not accessed either locally
25471 or via IMAP, then the entry will be ignored.
25472 For example, folders accessed via NNTP or POP3 will not be kept open, since
25473 the way that new mail is found with those protocols involves closing and
25474 reopening the connection.
25475 <P>
25476 Once a Stay Open folder has been opened, new-mail checking will continue
25477 to happen on that folder for the rest of the Alpine session.
25478 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25479 need to be added explicitly.
25480 <P>
25481 Another difference that you may notice between a Stay Open folder and a
25482 non-Stay Open folder is which message is selected as the current message
25483 when you enter the folder index.
25484 Normally, the starting position for an incoming folder (which most Stay Open
25485 folders will likely be) is controlled by the
25486 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25487 However, if a folder is a Stay Open folder, when you re-enter the folder
25488 after the first time the current message will be the same as it was when
25489 you left the folder.
25490 An exception is made if you use the TAB command to get to the folder.
25491 In that case, the message number will be incremented by one from what it
25492 was when you left the folder.
25493 <P>
25494 The above special behavior is thought to be useful.
25495 However, it is special and different from what you might at first expect.
25496 The feature
25497 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25498 may be used to turn off this special treatment.
25499 <P>
25500 If the message that was current when you left the folder no longer exists,
25501 then the regular startup rule will be used instead.
25503 <P>
25504 <UL>
25505 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25506 </UL><P>
25507 <End of help on this topic>
25508 </BODY>
25509 </HTML>
25510 ====== h_config_viewer_overlap =====
25511 <html>
25512 <header>
25513 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25514 </header>
25515 <body>
25516 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25518 This option specifies an aspect of Alpine's Message Viewing screen. When
25519 the space bar is used to page forward in a message, the number of lines
25520 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25521 bottom of the screen. That is, if this was set to two lines, then the
25522 bottom two lines of the screen would be repeated on the top of the next
25523 screen. The normal default value is "2".<p>
25524 <UL>
25525 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25526 </UL><P>
25527 <End of help on this topic>
25528 </body>
25529 </html>
25530 ====== h_config_scroll_margin =====
25531 <HTML>
25532 <HEAD>
25533 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25534 </HEAD>
25535 <BODY>
25536 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25538 This option controls when Alpine's line-by-line scrolling occurs.
25539 Typically, when a selected item is at the top or bottom screen edge
25540 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25541 displayed items are scrolled down or up by a single line.
25543 <P>
25544 This option allows you to tell Alpine the number of lines from the top and
25545 bottom screen edge that line-by-line paging should occcur. For example,
25546 setting this value to one (1) will cause Alpine to scroll the display
25547 vertically when you move to select an item on the display's top or
25548 bottom edge.
25550 <P>
25551 By default, this variable is zero, indicating that scrolling happens
25552 when you move up or down to select an item immediately off the display's
25553 top or bottom edge.
25555 <P>
25556 <UL>
25557 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25558 </UL><P>
25559 <End of help on this topic>
25560 </BODY>
25561 </HTML>
25562 ====== h_config_wordseps =====
25563 <HTML>
25564 <HEAD>
25565 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25566 </HEAD>
25567 <BODY>
25568 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25570 This option affects how a "word" is defined in the composer.
25571 The definition of a word is used when using the Forward Word and Backward
25572 Word commands in the composer, as well as when using the spell checker.
25573 Whitespace is always considered a word separator.
25574 Punctuation (like question marks, periods, commas, and so on) is always
25575 a word separator if it comes at the end of a word.
25576 By default, a punctuation character that is in the middle of a word does
25577 not break up that word as long as the character before and the character
25578 after it are both alphanumeric.
25579 If you add a character to this option it will be considered a
25580 word separator even when it occurs in the middle of an alphanumeric word.
25581 For example, if you want to skip through each part of an address instead
25582 of skipping the whole address at once you might want to include "@"
25583 and "." in this list.
25584 If you want the word-skipper to stop on each part of a UNIX filename you
25585 could add "/" to the list.
25586 The equal sign and dash are other possibilities you might find helpful.
25587 <P>
25588 <UL>
25589 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25590 </UL><P>
25591 <End of help on this topic>
25592 </BODY>
25593 </HTML>
25594 ====== h_config_reply_indent_string =====
25595 <HTML>
25596 <HEAD>
25597 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25598 </HEAD>
25599 <BODY>
25600 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25602 This option specifies an aspect of Alpine's Reply command.
25603 When a message is replied to and the text of the message is included, the
25604 included text usually has the string "> " prepended
25605 to each line indicating it is quoted text.
25606 (In case you haven't seen this before, "string" is a technical term
25607 that means chunk of text.)
25609 <P>
25610 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25611 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25612 use one of the standard values,
25613 "> " or ">", for this option.
25615 <P>
25616 This option specifies a different value for that string.
25617 If you wish to use a string that begins or ends with a space,
25618 enclose the string in double quotes.
25620 <P>
25621 Besides simple text, the prepended string can be based
25622 on the message being replied to.
25623 The following tokens are substituted for the message's corresponding value:
25625 <DL>
25626 <DT>_FROM_</DT>
25627 <DD>This token gets replaced with the message sender's "username".
25628 If the name is longer than six characters, only the first six characters are
25629 used.
25630 </DD>
25632 <DT>_NICK_</DT>
25633 <DD>This token gets replaced with the nickname of the message sender's
25634 address as found in your addressbook.
25635 If no addressbook entry is found,
25636 Alpine replaces the characters "_NICK_" with nothing.
25637 If the nickname is longer than six characters, only the first six characters are
25638 used.
25639 </DD>
25641 <DT>_INIT_</DT>
25642 <DD>This token gets replaced with the initials of the sender of the message.
25643 </DD>
25645 </DL>
25647 NOTE: When the
25648 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25649 feature is enabled, you are given the opportunity to edit the string, whether
25650 it is the default or one automatically generated using the above tokens.
25651 <P>
25652 If you change your <!--#echo var="VAR_reply-indent-string"-->
25653 so that it is not equal to the default value of "> ", then
25654 quoted text will not be flowed
25655 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
25656 when you reply.
25657 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
25658 set to the default value.
25659 <P>
25660 <UL>
25661 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25662 </UL><P>
25663 <End of help on this topic>
25664 </BODY>
25665 </HTML>
25666 ====== h_config_quote_replace_string =====
25667 <HTML>
25668 <HEAD>
25669 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
25670 </HEAD>
25671 <BODY>
25672 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
25674 This option specifies what string to use as a quote when <b>viewing</b> a
25675 message. The standard way of quoting messages when replying is the string
25676 "> " (quote space).
25677 With this variable set, viewing a message will
25678 replace occurrences of
25679 "> " and ">" with the replacement string.
25680 This setting works best when
25681 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
25682 or the equivalent setting in your correspondents' mail programs
25683 is set to the default
25684 "> ", but it will also work fine with the
25685 <!--#echo var="VAR_reply-indent-string"--> set to ">".
25686 <P>
25687 By default, this setting will only work on messages that are flowed, which is
25688 the default way of sending messages for many mail clients including
25689 Alpine. Enable the feature
25690 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
25691 to also have quote-replacement performed on non-flowed messages.
25692 <P>
25694 Setting this option will replace ">" and
25695 "> " with the new setting. This string may include trailing
25696 spaces. To preserve those spaces enclose the full string in double quotes.
25697 <P>
25698 No padding to separate the text of the message from the quote string is
25699 added. This means that if you do not add trailing spaces to the value of
25700 this variable, text will be displayed right next to the quote string,
25701 which may be undesirable. This can be avoided by adding a new string
25702 separated by a space from your selection of quote string replacement. This
25703 last string will be used for padding. For example, setting this variable to
25704 <br>">" " " has the effect of setting
25705 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
25706 a space from the last quote string to make it more readable.
25707 <P>
25708 One possible setting for this variable could be
25709 " " (four spaces wrapped in quotes), which
25710 would have the effect of indenting each level of quoting four spaces and
25711 removing the ">"'s. Different levels of quoting could be made
25712 more discernible by setting colors for quoted text.
25713 <P>
25714 Replying to or forwarding the viewed message will preserve the original
25715 formatting of the message, so quote-replacement will not be performed on
25716 messages that are being composed.
25717 <P>
25718 <UL>
25719 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25720 </UL><P>
25721 <End of help on this topic>
25722 </BODY>
25723 </HTML>
25724 ====== h_config_empty_hdr_msg =====
25725 <HTML>
25726 <HEAD>
25727 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
25728 </HEAD>
25729 <BODY>
25730 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
25732 When sending, if both the To and Cc fields are empty and you
25733 are sending the message to a Bcc,
25734 Alpine will put a special address in the To line. The default value is:
25736 <P>
25737 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
25739 <P>
25740 The reason for this is to avoid embarrassment caused by some Internet
25741 mail transfer software that interprets a "missing"
25742 <SAMP>To:</SAMP> header as an error and replaces it with an
25743 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
25744 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
25745 Bcc. You may change the part of this message that comes before the
25746 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
25747 variable to something else.
25749 <P>
25750 The normal default is "undisclosed-recipients".
25752 <P>
25753 <UL>
25754 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25755 </UL><P>
25756 <End of help on this topic>
25757 </BODY>
25758 </HTML>
25759 ====== h_config_status_msg_delay =====
25760 <HTML>
25761 <HEAD>
25762 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
25763 </HEAD>
25764 <BODY>
25765 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
25767 This option has evolved over time, causing the possible values to be
25768 counter-intuitive.
25769 Read carefully before you set this option.
25770 First we explain what the option does, then there is a longer discussion
25771 following that.
25772 <P>
25773 If this is set to zero, the default value, it has <EM>no</EM> effect.
25774 Positive and negative values serve two similar, but different purposes.
25775 <P>
25776 If it is set to a positive number, it causes the cursor to move to the
25777 status line whenever a status message is printed and pause there for this
25778 many seconds.
25779 It will probably only be useful if the
25780 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
25781 also turned on.
25782 Setting this option to a positive number can only be used to
25783 <EM>increase</EM> the status message delay.
25784 This may be useful for Braille displays, or other non-traditional displays.
25785 <P>
25786 If it is set to a negative number the interpretation is a bit complicated.
25787 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
25788 allow you to read important status messages.
25789 Of course, this may cause you to miss some important messages.
25790 If you see a message flash by but miss what it says you can use the
25791 Journal command from the MAIN MENU to read it.
25792 If you set this option to a negative value, the delay will be
25793 no more than one second less than the absolute value
25794 of the value you set.
25795 So if you set it to -1, the delay will be no more than zero seconds, no
25796 delay at all.
25797 If you set it to -2, the delay will be no more than 1 second.
25798 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
25799 If the delay that Alpine would have used by default is less than this delay,
25800 then the smaller delay set by Alpine will be used.
25801 Setting this option to a negative value can only reduce the amount of
25802 delay, never increase it.
25803 <P>
25804 Here is a more detailed explanation.
25805 Status messages are the messages that show up spontaneously in the
25806 status message line, usually the third line from the bottom of the screen.
25807 By default, Alpine assigns each status message it produces a minimum
25808 display time.
25809 Some status messages have a minimum display time of zero.
25810 You can see an example of such a message by paging up in this help text
25811 until you reach the top of the screen.
25812 If you try to page past the top you will see the message
25813 <P>
25814 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
25815 <P>
25816 in the status line.
25817 If there is another more important use of the status message line this message
25818 might be replaced quickly, or it even might not be shown at all.
25819 However, if there is no reason to get rid of the message, it might stay
25820 there for several seconds while you read the help.
25821 An example where it is replaced immediately happens when you page up in
25822 the help text past the top of the screen, but then type the "WhereIs"
25823 command right after paging up.
25824 The message will disappear immediately without causing a delay (unless you
25825 have set this option to a positive value) to allow you to type input for
25826 the "WhereIs" command.
25827 Since it isn't a very important message, Alpine has set its minimum display
25828 time to zero seconds.
25829 <P>
25830 Other messages have minimum display times of three or more seconds.
25831 These are usually error messages that Alpine thinks you ought to see.
25832 For example, it might be a message about a failed Save or a failed folder open.
25833 It is often the case that this minimum display time won't delay you in
25834 any way because the status message line is not needed for another reason.
25835 However, there are times when Alpine has to delay what it is doing in
25836 order to display a status message for the minimum display time.
25837 This happens when a message is being displayed and Alpine wants to ask
25838 for input from the keyboard.
25839 For example, when you Save a message you use the status message line.
25840 You get a prompt there asking for the name of the folder to save to.
25841 If there is a status message being displayed that has not
25842 yet displayed for its minimum
25843 time Alpine will display that status message surrounded with the characters
25844 > and < to show you that it is delaying.
25845 That might happen, for example, if you tried to save to a folder that
25846 caused an error, then followed that immediately with another Save command.
25847 You might find yourself waiting for a status message like
25848 <P>
25849 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
25850 <P>
25851 to finish displaying for three seconds.
25852 If that is something you find happening to you frequently, you may use
25853 negative values of this option to decrease or eliminate that delay, at
25854 the risk of missing the message.
25855 <P>
25856 <UL>
25857 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25858 </UL><P>
25859 <End of help on this topic>
25860 </BODY>
25861 </HTML>
25862 ====== h_config_active_msg_interval =====
25863 <HTML>
25864 <HEAD>
25865 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
25866 </HEAD>
25867 <BODY>
25868 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
25870 When Alpine is delayed for some reason it usually shows that
25871 something is happening with a small animated display in the status
25872 message line near the bottom of the screen.
25873 This option sets how frequently the characters (for example, a spinning bar)
25874 in the active status message lines are updated.
25875 At most, it can be set to be udpated 20 times per second.
25877 <P>
25878 Setting this value to zero will prevent display of the animations
25879 altogether.
25881 <P>
25882 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
25883 can be used to remove the randomness from this animated display.
25885 <P>
25886 <UL>
25887 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25888 </UL><P>
25889 <End of help on this topic>
25890 </BODY>
25891 </HTML>
25892 ====== h_config_mailchecknoncurr =====
25893 <HTML>
25894 <HEADER>
25895 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
25896 </HEADER>
25897 <BODY>
25898 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
25900 This option is closely related to the
25901 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
25902 option, as well as the
25903 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
25904 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
25905 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
25906 new-mail checking is disabled and this option will have no effect.
25907 <P>
25908 Normally this option is set to zero, which means that the value used will be
25909 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
25910 If you set this option to a value different from zero
25911 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
25912 then that is the check interval that will be used
25913 for folders that are not the currently open folder or the INBOX.
25914 You may not even have any folders that are noncurrent and not the INBOX.
25915 If you do, it is likely that they are due to
25916 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25917 you have configured.
25918 This option also affects the rate of mail checking done on cached
25919 connections to folders you previously had open but are no longer actively
25920 using.
25921 You aren't expected to understand that last sentence, but if you are interested
25922 take a look at
25923 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
25924 and the related options.
25925 <P>
25926 <UL>
25927 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25928 </UL><P>
25929 <End of help on this topic>
25930 </BODY>
25931 </HTML>
25932 ====== h_config_fifopath =====
25933 <HTML>
25934 <HEADER>
25935 <TITLE>OPTION: NewMail FIFO Path</TITLE>
25936 </HEADER>
25937 <BODY>
25938 <H1>OPTION: NewMail FIFO Path</H1>
25940 This option is only available in UNIX Alpine.
25941 However, there is a very similar feature built in to PC-Alpine.
25942 In PC-Alpine's Config menu at the top of the screen
25943 is an option called "New Mail Window".
25944 <P>
25945 You may have Alpine create a FIFO special file (also called a named pipe) where
25946 it will send a one-line message each time a new message is received in
25947 the current folder, the INBOX, or any open
25948 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
25949 To protect against two different Alpines both writing to the same FIFO, Alpine
25950 will only create the FIFO and write to it if it doesn't already exist.
25951 <P>
25952 A possible way to use this option would be to have a separate window
25953 on your screen running the command
25954 <P>
25955 <CENTER><SAMP>cat filename</SAMP></CENTER>
25956 <P>
25957 where "filename" is the name of the file given for this option.
25958 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
25959 start Alpine and <EM>then</EM> run the "cat" command.
25960 You may be tempted to use "tail -f filename" to view the new
25961 mail log.
25962 However, the common implementations of the tail command will not do what you
25963 are hoping.
25964 <P>
25965 The width of the messages produced for the FIFO may be altered with the
25966 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
25967 <P>
25968 On some systems, fifos may only be created in a local filesystem.
25969 In other words, they may not be in NFS filesystems.
25970 This requirement is not universal.
25971 If the system you are using supports it, it should work.
25972 (It is often the case that your home directory is in an NFS filesystem.
25973 If that is the case, you might try using a file in the "/tmp"
25974 filesystem, which is usually a local filesytem.)
25975 Even when it is possible to use an NFS-mounted filesystem as a place to name
25976 the fifo (for example, your home directory), it will still be the case that
25977 the reader (probably the "cat" command) and the
25978 writer (Alpine) of the fifo must be running on the same system.
25979 <P>
25980 <UL>
25981 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25982 </UL><P>
25983 <End of help on this topic>
25984 </BODY>
25985 </HTML>
25986 ====== h_config_newmailwidth =====
25987 <HTML>
25988 <HEADER>
25989 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
25990 </HEADER>
25991 <BODY>
25992 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
25994 For UNIX Alpine, this option is only useful if you have turned on the
25995 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
25996 That option causes new mail messages to be sent to a fifo file.
25997 Those messages will be 80 characters wide by default.
25998 You can change the width of those messages by changing this option.
25999 For example, if you are reading those messages in another window you might
26000 want to set this width to the width of that other window.
26001 <P>
26002 If you are using PC-Alpine, it has an option in the Config menu to turn
26003 on the "New Mail Window".
26004 This present option also controls the width of that window.
26005 <P>
26006 <UL>
26007 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26008 </UL><P>
26009 <End of help on this topic>
26010 </BODY>
26011 </HTML>
26012 ====== h_config_mailcheck =====
26013 <HTML>
26014 <HEADER>
26015 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
26016 </HEADER>
26017 <BODY>
26018 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
26020 This option specifies, in seconds,
26021 how often Alpine will check for new mail.
26022 If set to zero, new-mail checking is disabled.
26023 (You can always manually force a new-mail check by typing ^L (Ctrl-L), which is also the command to refresh the screen, or by typing the Next command when the
26024 current message is the last message of the folder.)
26025 There is a minimum value for this option, normally 15 seconds.
26026 The default value is normally 150 seconds.
26027 The higher you set this option, the easier it is on the server.
26028 <P>
26029 There are some situations where automatic new-mail checking does not work.
26030 See the discussion about new-mail checking in
26031 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
26032 <P>
26033 The new-mail checking will not happen exactly at the frequency that you specify.
26034 For example, Alpine may elect to defer a non-INBOX mail check if you
26035 are busy typing.
26036 Or, it may check more frequently than you have specified if that is
26037 thought to be necessary to keep the server from closing the connection
26038 to the folder due to inactivity.
26039 If Alpine checks for new mail as a side effect of another command, it will reset
26040 the timer, so that new-mail checking may seem to happen irregularly instead of
26041 every X seconds like clockwork.
26042 <P>
26043 If you are anxious to know about new mail as soon as possible, set the check
26044 interval low, and you'll know about the new mail by approximately
26045 that amount of time after it arrives.
26046 If you aren't so worried about knowing right away, set this option to a
26047 higher value.
26048 That will save the server some processing time and may save you some of
26049 the time you spend waiting for new-mail checks to happen if you are
26050 dealing with a slow server or slow network connection.
26051 <P>
26052 If you suspect that new-mail checking is causing slow downs for you,
26053 you may want to look into the options
26054 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
26055 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
26056 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
26057 which refine when mail checking is done.
26058 <P>
26059 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
26060 there is a minimum time
26061 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
26062 between new-mail checks.
26063 Because of this minimum you may notice that new mail does not
26064 appear promptly when you expect it.
26065 The reason for this is to protect the server from over-zealous opening and
26066 closing of the Mail Drop folder, since that is a costly operation.
26067 <P>
26068 <UL>
26069 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26070 </UL><P>
26071 <End of help on this topic>
26072 </BODY>
26073 </HTML>
26074 ====== h_config_quell_checks_comp =====
26075 <HTML>
26076 <HEAD>
26077 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
26078 </HEAD>
26079 <BODY>
26080 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
26082 This option is closely related to the
26083 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26084 option, the
26085 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26086 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
26087 <P>
26088 If this option is set, then the normal new-mail checking that happens
26089 while you are composing will not happen for folders other than your
26090 INBOX (which depends on the setting
26091 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
26092 <P>
26093 You might want to set this option if you are experiencing delays while
26094 composing that you think might be related to the speed of the new-mail
26095 checks.
26096 <P>
26097 Even with this option turned on, an occasional new-mail check may be done
26098 in order to keep the server from killing the connection to the folder.
26099 For example, IMAP servers may remove a connection to a folder if there
26100 has been no activity on the connection for 30 minutes or more.
26101 Instead of letting that happen, Alpine will check for new mail before the
26102 30 minutes is up even though you have turned on this feature to quell
26103 those checks.
26104 <P>
26105 Besides new-mail checks, checkpoint operations on the folders
26106 will also be quelled when you set this option.
26107 The purpose of checkpointing is to write the changes to a folder out to
26108 disk periodically in order to avoid losing those changes when system or
26109 software problems occur.
26110 New-mail checking and checkpointing while you are not composing are not
26111 affected by this option.
26113 <P>
26114 <End of help on this topic>
26115 </BODY>
26116 </HTML>
26117 ====== h_config_quell_checks_comp_inbox =====
26118 <HTML>
26119 <HEAD>
26120 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
26121 </HEAD>
26122 <BODY>
26123 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
26125 This option is closely related to the
26126 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26127 option, the
26128 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26129 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
26130 <P>
26131 If this option is set, then the normal new-mail checking that happens
26132 while you are composing will not happen for your INBOX.
26133 Checking of other folders is controlled in a similar way with the
26134 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
26135 <P>
26136 You might want to set this option if you are experiencing delays while
26137 composing that you think might be related to the speed of the new-mail
26138 checks.
26139 <P>
26140 Even with this option turned on, an occasional new-mail check may be done
26141 in order to keep the server from killing the connection to the folder.
26142 For example, IMAP servers may remove a connection to a folder if there
26143 has been no activity on the connection for 30 minutes or more.
26144 Instead of letting that happen, Alpine will check for new mail before the
26145 30 minutes is up even though you have turned on this feature to quell
26146 those checks.
26147 <P>
26148 Besides new-mail checks, checkpoint operations on the INBOX
26149 will also be quelled when you set this option.
26150 The purpose of checkpointing is to write the changes to a folder out to
26151 disk periodically in order to avoid losing those changes when system or
26152 software problems occur.
26153 New-mail checking and checkpointing while you are not composing are not
26154 affected by this option.
26155 <P>
26156 <End of help on this topic>
26157 </BODY>
26158 </HTML>
26159 ====== h_config_maildropcheck =====
26160 <HTML>
26161 <HEADER>
26162 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
26163 </HEADER>
26164 <BODY>
26165 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
26167 New-mail checking for a
26168 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
26169 mail checking for a regular folder.
26170 One of the differences is that the connection to the Mail Drop is not
26171 kept open and so the cost of checking
26172 (delay for you and additional load for the server) may be significant.
26173 Because of this additional cost we set a minimum time that
26174 must pass between checks.
26175 This minimum only applies to the automatic checking done by Alpine.
26176 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
26177 at the end of a folder index, then the check is done right away.
26178 <P>
26179 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
26180 new-mail checks.
26181 You may want to set this minimum high in order to avoid experiencing some
26182 of the delays associated with the checks.
26183 Note that the time between checks is still controlled by the regular
26184 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
26185 When Alpine is about to do an automatic check for new mail (because
26186 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
26187 new-mail check
26188 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
26189 the Mail Drop is checked for new mail as well.
26190 Therefore, it is only useful to set this option to a value that is higher
26191 than the <!--#echo var="VAR_mail-check-interval"-->.
26192 <P>
26193 If this option is set to zero, automatic Mail Drop new-mail
26194 checking is disabled.
26195 There is a minimum value, normally 60 seconds.
26196 The default value is normally 60 seconds as well.
26197 This applies to the INBOX and to the currently open folder if that is
26198 different from the INBOX.
26200 <P>
26201 <UL>
26202 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26203 </UL><P>
26204 <End of help on this topic>
26205 </BODY>
26206 </HTML>
26207 ====== h_config_nntprange =====
26208 <HTML>
26209 <HEADER>
26210 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
26211 </HEADER>
26212 <BODY>
26213 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
26215 This option applies only to newsgroups accessed using the NNTP protocol.
26216 It does not, for example,
26217 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
26219 <P>
26220 When you open a connection to a News server using the NNTP protocol, you
26221 normally have access to all of the articles in each newsgroup.
26222 If a server keeps a large backlog of messages it may speed performance
26223 some to restrict attention to only the newer messages in a group.
26224 This option allows you to set how many article numbers should be checked
26225 when opening a newsgroup.
26226 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
26227 of messages you ever want to see.
26228 For example, if you only ever wanted to look at the last 500 messages in each
26229 newsgroup you could set this option to 500.
26230 In actuality, it isn't quite that.
26231 Instead, for performance reasons, it specifies the range of article
26232 numbers to be checked, beginning
26233 with the highest numbered article and going backwards from there.
26234 If there are messages that have been canceled or deleted
26235 their article numbers are still counted as part of the range.
26236 <P>
26237 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
26238 numbers
26239 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
26240 <P>
26241 to be considered when reading a newsgroup.
26242 The number of messages that show up in your index will be less than or equal
26243 to the value of "<!--#echo var="VAR_nntp-range"-->".
26245 <P>
26246 The purpose of this option is simply to speed up access when reading news.
26247 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
26248 numbers, and can avoid downloading any information about the ignored articles.
26249 There is a cost you pay for this speedup.
26250 That cost is that there is no way for you to see those ignored articles.
26251 The articles that come before the range you specify are invisible to you and
26252 to Alpine, as if they did not exist at all.
26253 There is no way to see those messages using, for example, an unexclude command
26254 or something similar.
26255 The only way to see those articles is to set this option high enough (or
26256 set it to zero) and then to reopen the newsgroup.
26258 <P>
26259 If this option is set to 0 (which is also the default),
26260 then the range is unlimited.
26261 This option applies globally to all NNTP servers and to all newsgroups
26262 on those servers.
26263 There is no way to set different values for different newsgroups or servers.
26265 <P>
26266 <UL>
26267 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26268 </UL><P>
26269 <End of help on this topic>
26270 </BODY>
26271 </HTML>
26272 ====== h_config_news_active =====
26273 <html>
26274 <header>
26275 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
26276 </header>
26277 <body>
26278 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
26280 This option tells Alpine where to look for the "active file" for newsgroups
26281 when accessing news locally, rather than via NNTP. The default path is
26282 usually "/usr/lib/news/active".<p>
26283 <UL>
26284 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26285 </UL><P>
26286 <End of help on this topic>
26287 </body>
26288 </html>
26289 ====== h_config_news_spool =====
26290 <html>
26291 <header>
26292 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
26293 </header>
26294 <body>
26295 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
26297 This option tells Alpine where to look for the "news spool" for newsgroups
26298 when accessing news locally, rather than via NNTP. The default path is
26299 usually "/var/spool/news".<p>
26300 <UL>
26301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26302 </UL><P>
26303 <End of help on this topic>
26304 </body>
26305 </html>
26306 ====== h_config_image_viewer =====
26307 <html>
26308 <header>
26309 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
26310 </header>
26311 <body>
26312 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
26313 <body>
26314 This option specifies the program Alpine should call to view MIME
26315 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
26316 no longer needed, but remains for backward compatibility. The more
26317 general method for associating external printing and viewing programs with
26318 specific MIME data types is to use the system's (or your personal)
26319 "mailcap" configuration file.<p>
26320 <UL>
26321 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26322 </UL><P>
26323 <End of help on this topic>
26324 </body>
26325 </html>
26326 ====== h_config_domain_name =====
26327 <HTML>
26328 <HEAD>
26329 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
26330 </HEAD>
26331 <BODY>
26332 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
26334 This option is used only if the
26335 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
26336 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
26337 strips the hostname from your return ("From") address and when
26338 completing unqualified addresses that you enter into the composer.
26339 <P>
26340 If you set this, see also the <A HREF="h_config_quell_local_lookup">
26341 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
26344 <!--chtml if pinemode="os_windows"-->
26345 <P>This option is not applicable to PC-Alpine.
26346 <!--chtml else-->
26347 <P>
26348 <!--chtml endif-->
26349 <UL>
26350 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26351 </UL>
26352 <P>
26353 <End of help on this topic>
26354 </BODY>
26355 </HTML>
26356 ====== h_config_prune_date =====
26357 <HTML>
26358 <HEAD>
26359 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
26360 </HEAD>
26361 <BODY>
26362 <H1>OPTION: Last-Time-Prune Question</H1>
26364 This value records the last time you were asked about deleting old
26365 sent-mail.
26366 It is set automatically by Alpine at the beginning of each month.
26367 In the past, if you wished to suppress the monthly sent-mail
26368 pruning feature, you could set this to a date in the future.
26369 This value is relative to the year 1900, so
26370 to set this, for example, to October 2005, use 105.10.
26371 <P>
26372 You can still do that if you wish, or you can use the
26373 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
26374 a little more convenient to use.
26375 <P>
26376 <UL>
26377 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26378 </UL><P>
26379 <End of help on this topic>
26380 </BODY>
26381 </HTML>
26382 ====== h_config_goto_default =====
26383 <HTML>
26384 <HEAD>
26385 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
26386 </HEAD>
26387 <BODY>
26388 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
26390 This value affects Alpine's behavior when you use the Goto command.
26391 Alpine's usual behavior has two parts. If your current folder is
26392 "Inbox", Alpine will offer the last open folder as the
26393 default. If the current folder is other than "Inbox",
26394 "Inbox" is offered as the default.
26396 <P>
26397 The available options include:
26399 <DL>
26401 <DT>folder-in-first-collection</DT>
26403 <DD> Alpine will offer the most recently visited folder in the default
26404 collection found in the "Collection List" screen as the default.
26405 </DD>
26407 <DT> inbox-or-folder-in-first-collection</DT>
26409 <DD> If the current folder is "Inbox",
26410 Alpine will offer the most recently visited folder in the
26411 default collection found in the "Collection List" screen.
26412 If the current folder is other than "Inbox",
26413 "Inbox" is offered as the default.
26414 </DD>
26416 <DT> inbox-or-folder-in-recent-collection</DT>
26418 <DD> This is Alpine's default behavior.
26419 If the current folder is "Inbox",
26420 Alpine will offer the last open
26421 folder as the default.
26422 If the current folder is other than "Inbox",
26423 "Inbox" is offered as the default.
26424 </DD>
26426 <DT> first-collection-with-inbox-default</DT>
26428 <DD> Instead of offering the most recently visited folder in the default
26429 collection, the default collection is offered but with "Inbox" as
26430 the default folder.
26431 If you type in a folder name it will be in the default collection.
26432 If you simply accept the default, however, your "Inbox" will be opened.
26433 </DD>
26435 <DT> most-recent-folder</DT>
26437 <DD> The last accepted value simply causes the most recently opened
26438 folder to be offered as the default regardless of the currently opened
26439 folder.
26440 </DD>
26441 </DL>
26443 <P>
26444 NOTE: The default while a newsgroup is open remains the same; the last
26445 open newsgroup.
26447 <P>
26448 <UL>
26449 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26450 </UL><P>
26451 <End of help on this topic>
26452 </BODY>
26453 </HTML>
26454 ====== h_config_thread_lastreply_char =====
26455 <HTML>
26456 <HEAD>
26457 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26458 </HEAD>
26459 <BODY>
26460 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26462 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26463 INDEX display when using a
26464 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26465 of "show-thread-structure", "mutt-like", or
26466 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26467 The value of this option is a single character.
26468 This character is used instead of the vertical line character when there are
26469 no more replies directly to the parent of the current message.
26470 It can be used to "round-off" the bottom of the vertical line
26471 by setting it to a character such as a backslash (\) or
26472 a backquote (`).
26473 The default value of this option is the backslash character (\).
26474 This option may not be set to the Empty Value.
26475 In that case, the default will be used instead.
26477 <P>
26478 <UL>
26479 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26480 </UL><P>
26481 <End of help on this topic>
26482 </BODY>
26483 </HTML>
26484 ====== h_config_thread_indicator_char =====
26485 <HTML>
26486 <HEAD>
26487 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26488 </HEAD>
26489 <BODY>
26490 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26492 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26493 INDEX display when using a
26494 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26495 than "none" and sorting by Threads or OrderedSubject.
26496 The value of this option is a single character.
26497 This character is used to indicate that part of a thread (a conversation) is
26498 hidden beneath a message.
26499 The message could be expanded
26500 if desired with the "/" Collapse/Expand command.
26501 By default, the value of this option is the greater than sign (>).
26502 <P>
26503 If this option is set to the Empty Value, then the column (and the following
26504 blank column) will be deleted from the display.
26506 <P>
26507 This option is closely related to the
26508 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26509 Another similar option that affects the thread display is the
26510 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26512 <P>
26513 <UL>
26514 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26515 </UL><P>
26516 <End of help on this topic>
26517 </BODY>
26518 </HTML>
26519 ====== h_config_thread_exp_char =====
26520 <HTML>
26521 <HEAD>
26522 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26523 </HEAD>
26524 <BODY>
26525 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26527 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26528 INDEX display when using a
26529 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26530 than "none".
26531 The value of this option is a single character.
26532 This character is used to indicate that part of a thread has been expanded
26533 and could be collapsed if desired with
26534 the "/" Collapse/Expand command.
26535 By default, the value of this option is a dot (.).
26536 <P>
26537 If this option is set to the Empty Value, then the column (and the following
26538 blank column) will be deleted from the display.
26540 <P>
26541 This option is closely related to the
26542 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26543 Another similar option that affects the thread display is the
26544 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26546 <P>
26547 <UL>
26548 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26549 </UL><P>
26550 <End of help on this topic>
26551 </BODY>
26552 </HTML>
26553 ====== h_config_thread_index_style =====
26554 <HTML>
26555 <HEAD>
26556 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26557 </HEAD>
26558 <BODY>
26559 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26561 When a folder is sorted by Threads or OrderedSubject,
26562 this option will affect the INDEX displays.
26563 <P>
26565 The possible values for this option are:
26567 <DL>
26568 <DT>regular-index-with-expanded-threads</DT>
26569 <DD>This is the default display.
26570 If the configuration option
26571 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26572 is set to something other than "none", then this setting
26573 will cause Alpine to start off with a MESSAGE INDEX with all of
26574 the threads expanded.
26575 That is, each message will have a line in the MESSAGE INDEX display.
26576 The Collapse/Expand command (/) may be used to manually collapse or
26577 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26578 <P>
26579 This setting affects the display when the folder is first threaded.
26580 The collapsed state may also be re-initialized by re-sorting the folder manually
26581 using the SortIndex command ($).
26582 After re-sorting the threads will once again all be expanded, even if you
26583 have previously collapsed some of them.
26584 <P>
26585 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26586 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26587 in a different order.
26588 </DD>
26590 <DT>regular-index-with-collapsed-threads</DT>
26591 <DD>If the configuration option
26592 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26593 is set to something other than "none", then this setting
26594 will cause Alpine to start out with all of the threads collapsed instead of
26595 starting out with all of the threads expanded.
26596 The Collapse/Expand command (/) may be used to manually collapse or
26597 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26598 <P>
26599 This setting affects the display when the folder is first threaded.
26600 The collapsed state may also be re-initialized by re-sorting the folder manually
26601 using the SortIndex command ($).
26602 After re-sorting the threads will once again all be collapsed, even if you
26603 have previously expanded some of them.
26604 </DD>
26606 <DT>separate-index-screen-always</DT>
26607 <DD>With this setting and the next, you will see an index of threads
26608 instead of an
26609 index of messages, provided you have sorted by Threads or OrderedSubject.
26610 <P>
26611 The THREAD INDEX contains a '*' in the first column if any message in the thread
26612 is marked Important.
26613 If not, it contains a '+' if any message in the thread is to you.
26614 The second column is blank. The third column contains a 'D' if all of the
26615 messages in the thread are deleted.
26616 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26617 <P>
26618 When you view a particular thread from the THREAD INDEX you will be
26619 in the MESSAGE INDEX display
26620 but the index will only contain messages from the thread you are viewing.
26621 </DD>
26623 <DT>separate-index-screen-except-for-single-messages</DT>
26624 <DD>This is very similar to the option above.
26625 When you are in the THREAD INDEX, one of the available commands
26626 is "ViewThd".
26627 With the setting "separate-index-screen-always" (the option above)
26628 when you view a particular thread you will be in the
26629 MESSAGE INDEX display and the index will only contain messages from
26630 the thread you are viewing.
26631 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26632 will be an index with only one message in it.
26633 If you use this "separate-index-screen-except-for-single-messages"
26634 setting instead, then that index that contains a single message
26635 will be skipped and you will go directly from the THREAD INDEX into the
26636 MESSAGE TEXT screen.
26637 </DD>
26639 </DL>
26641 <P>
26642 <UL>
26643 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26644 </UL><P>
26645 <End of help on this topic>
26646 </BODY>
26647 </HTML>
26648 ====== h_config_thread_disp_style =====
26649 <HTML>
26650 <HEAD>
26651 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26652 </HEAD>
26653 <BODY>
26654 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
26656 When a folder is sorted by Threads or OrderedSubject,
26657 this option will affect the MESSAGE INDEX display.
26658 By default, Alpine will display the MESSAGE INDEX in the
26659 "show-thread-structure" style if a folder is sorted
26660 by Threads or OrderedSubject.
26661 <P>
26663 The possible values for this option are:
26665 <DL>
26666 <DT>none</DT>
26667 <DD>Regular index display.
26668 The same index line as would be displayed without threading is used.
26669 The only difference will be in the order of the messages.
26670 </DD>
26672 <DT>show-thread-structure</DT>
26673 <DD>Threaded Subjects will be indented and vertical bars and horizontal
26674 lines will be added to make it easier to see the relationships among
26675 the messages in a thread (a conversation).
26676 </DD>
26678 <DT>mutt-like</DT>
26679 <DD>This is the same as the option above except that the Subject
26680 is suppressed (is blank) if it matches the previous Subject in the thread.
26681 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
26682 Here is an example of what a mutt-like index might look like.
26683 In this example, the first column represents the message number, the
26684 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
26685 is set to "regular-index-with-expanded-threads", and the
26686 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
26687 is set to a backslash:
26688 <PRE>
26689 1 Some topic
26690 2 . Subject original message in thread
26691 3 |-> reply to 2
26692 4 . |-> another reply to 2
26693 5 . | \-> reply to 4
26694 6 . | \-> reply to 5
26695 7 | \-> reply to 6
26696 8 |-> another reply to 2
26697 9 . |->New subject another reply to 2 but with a New subject
26698 10 | |-> reply to 9
26699 11 | \-> another reply to 9
26700 12 | \-> reply to 11
26701 13 \-> final reply to 2
26702 14 Next topic
26703 </PRE>
26704 </DD>
26706 <DT>indent-subject-1</DT>
26707 <DD>Threaded Subjects will be indented one space per level of the conversation.
26708 The bars and lines that show up in the show-thread-structure display will
26709 not be there with this style.
26710 </DD>
26712 <DT>indent-subject-2</DT>
26713 <DD>Same as above but indent two spaces per level instead of one space.
26714 </DD>
26716 <DT>indent-from-1</DT>
26717 <DD>Similar to indent-subject-1, except that instead of indenting the
26718 Subject field one space the From field of a thread will be indented one
26719 space per level of the conversation.
26720 </DD>
26722 <DT>indent-from-2</DT>
26723 <DD>Same as above but indent two spaces per level instead of one space.
26724 </DD>
26726 <DT>show-structure-in-from</DT>
26727 <DD>The structure of the thread is illustrated with indenting, vertical bars,
26728 and horizontal lines just like with the show-thread-structure option, but
26729 the From field is used to show the relationships instead of the Subject field.
26730 </DD>
26732 </DL>
26734 <P>
26735 <UL>
26736 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26737 </UL><P>
26738 <End of help on this topic>
26739 </BODY>
26740 </HTML>
26741 ====== h_config_pruning_rule =====
26742 <HTML>
26743 <HEAD>
26744 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
26745 </HEAD>
26746 <BODY>
26747 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
26749 By default, Alpine will ask at the beginning of each month whether or not
26750 you want to rename your sent-mail folder to a name like sent-mail-month-year.
26751 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
26752 change the format of the folder to sent-mail-yyyy-mm.)
26753 It will also ask whether you would like to delete old sent-mail folders.
26754 If you have defined
26755 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
26756 or
26757 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
26758 Alpine will also ask about pruning those folders.
26759 <P>
26761 With this option you may provide an automatic answer to these questions.
26762 The default value is to ask you what you'd like to do.
26763 <P>
26765 The six possible values for this option are:
26767 <DL>
26768 <DT>ask about rename, ask about deleting</DT>
26769 <DD>This is the default.
26770 Alpine will ask whether you want to rename the folders and whether you
26771 want to delete each of the old folders.
26772 </DD>
26774 <DT>ask about rename, don't delete</DT>
26775 <DD>Alpine will ask whether you want to rename the folders, but won't
26776 ask about or delete old folders.
26777 </DD>
26779 <DT>always rename, ask about deleting</DT>
26780 <DD>This means you want to always answer yes and have Alpine automatically
26781 rename the folder if possible.
26782 You will also be asked about deleting old folders.
26783 </DD>
26785 <DT>always rename, don't delete</DT>
26786 <DD>This means you want to always answer yes and have Alpine automatically
26787 rename the folder if possible.
26788 There will be no deleting of old folders.
26789 </DD>
26791 <DT>don't rename, ask about deleting</DT>
26792 <DD>This means you want to always answer no.
26793 Alpine will not rename the folder.
26794 You will be asked about deleting old folders.
26795 </DD>
26797 <DT>don't rename, don't delete</DT>
26798 <DD>This means you want to always answer no.
26799 Alpine will not rename the folder.
26800 There will be no deleting of old folders, either.
26801 </DD>
26802 </DL>
26804 <P>
26805 <UL>
26806 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26807 </UL><P>
26808 <End of help on this topic>
26809 </BODY>
26810 </HTML>
26811 ====== h_config_reopen_rule =====
26812 <HTML>
26813 <HEAD>
26814 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
26815 </HEAD>
26816 <BODY>
26817 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
26819 Alpine normally checks for new mail in the currently open folder
26820 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
26822 <P>
26823 There are some situations where automatic new-mail checking does not work.
26824 For example, if a mail folder is opened using the POP protocol or a newsgroup
26825 is being read using the NNTP protocol, then new-mail checking is disabled.
26827 <P>
26828 It may be possible to check for new mail in these cases by reopening the
26829 folder.
26830 Alpine does not do this for you automatically, but you may do the commands
26831 manually to cause this to happen.
26832 You reopen by going back to the folder list screen from the message
26833 index screen with the "<" command,
26834 and then going back into the message index screen with
26835 the ">" command.
26836 (Actually, any method you would normally use to open a folder will work the
26837 same as the "<" followed by ">" method.
26838 For example, the GoTo Folder command will work, or you may use L to go to the
26839 Folder List screen and Carriage Return to reopen the folder.)
26841 <P>
26842 There are some cases where Alpine knows that reopening the folder should
26843 be useful as a way to discover new mail.
26844 At the time of this writing, connections made using the POP protocol,
26845 news reading using the NNTP protocol, local news reading, and local
26846 ReadOnly folders that are in the traditional UNIX or the MMDF format all
26847 fall into this category.
26848 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
26849 has no way of knowing, so it might also just be an exercise in futility.
26850 All remote, ReadOnly folders other than those listed just above fall into this
26851 category.
26852 The setting of this option together with the type of folder
26853 controls how Alpine will react to the apparent attempt to reopen a folder.
26855 <P>
26856 If you don't reopen, then you will just be back in
26857 the message index with no change.
26858 You left the index and came back, but the folder remained "open"
26859 the whole time.
26860 However, if you do reopen the folder, the folder is closed and then reopened.
26861 In this case, the current state of the open folder is lost.
26862 The New status, Important and Answered flags,
26863 selected state, Zoom state, collapsed or expanded state of threads,
26864 current message number,
26865 and any other temporary state is all lost when the reopen happens.
26866 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
26868 <P>
26869 In the possibilities listed below, the text says "POP/NNTP" in
26870 several places.
26871 That really implies the case where Alpine knows it is a good way to discover
26872 new mail, which is more than just POP and NNTP, but POP and NNTP are
26873 the cases of most interest.
26874 This option probably has more possible values than it deserves. They are:
26876 <DL>
26877 <DT>Always reopen</DT>
26878 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
26879 whenever you type a command that implies a reopen, regardless of the
26880 access method.
26881 In other words, it is assumed you would always answer Yes if asked
26882 about reopening.
26883 </DD>
26885 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
26886 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26887 will ask you whether to reopen other remote folders,
26888 with a default answer of Yes.
26889 </DD>
26891 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
26892 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
26893 will ask you whether to reopen other remote folders,
26894 with a default answer of No.
26895 </DD>
26897 <DT>Yes for POP/NNTP, No for other remote</DT>
26898 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
26899 will assume a No answer for all other remote folders.
26900 </DD>
26902 <DT>Always ask [Yes]</DT>
26903 <DD>Alpine will not differentiate based on access method.
26904 It will always ask for all remote folders, with a default answer of Yes.
26905 </DD>
26907 <DT>Always ask [No]</DT>
26908 <DD>Alpine will not differentiate based on access method.
26909 It will always ask for all remote folders, with a default answer of No.
26910 </DD>
26912 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
26913 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
26914 of Yes.
26915 It will never attempt to reopen other remote folders.
26916 </DD>
26918 <DT>Ask about POP/NNTP [No], No for other remote</DT>
26919 <DD>This is the default.
26920 Alpine will ask if the access method is POP or NNTP, with a default answer
26921 of No.
26922 It will never attempt to reopen other remote folders.
26923 </DD>
26925 <DT>Never reopen</DT>
26926 <DD>Alpine will never attempt to reopen already open folders.
26927 </DD>
26928 </DL>
26930 <P>
26931 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
26932 any of the other situations where it is likely that reopening is a good way
26933 to discover new mail.
26935 <P>
26936 There is an alternative that may be of useful in some situations.
26937 Instead of manually checking for new mail you can set up a
26938 <A HREF="h_maildrop">Mail Drop</A>
26939 and automatically check for new mail.
26941 <P>
26942 <UL>
26943 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26944 </UL><P>
26945 <End of help on this topic>
26946 </BODY>
26947 </HTML>
26948 ====== h_config_inc_startup =====
26949 <HTML>
26950 <HEAD>
26951 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
26952 </HEAD>
26953 <BODY>
26954 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
26956 This value affects Alpine's behavior when opening the "INBOX" or
26957 one of the "INCOMING MESSAGE FOLDERS".
26958 It determines which message will be the <EM>current message</EM> when
26959 the folder is first opened.
26960 The default value is "first-unseen".
26962 <P>
26963 The seven possible values for this option are:
26965 <DL>
26966 <DT>first-unseen</DT>
26967 <DD>The current message is set to the first
26968 unseen message that has not been marked deleted, or the last message if
26969 all of the messages have been seen previously.
26970 Messages which have not been seen or which have been seen but re-marked
26971 as New are considered unseen messages.
26972 See the note at the bottom of this help about newsgroups.
26973 </DD>
26975 <DT>first-recent</DT>
26976 <DD>Similar to the default, but rather than starting on the first
26977 unseen message Alpine starts on the first <EM>recent</EM> message.
26978 A message is recent if it arrived since the last time the folder was
26979 open. This value causes the current message to be set to the first
26980 recent message if there is one, otherwise to the last
26981 message in the folder.
26982 </DD>
26984 <DT>first-important</DT>
26985 <DD>This will result in the current message being set to the first
26986 message marked Important (but not Deleted).
26987 If no messages are marked Important, then it will be the last message.
26988 Messages are marked Important by <EM>you</EM>, not by the sender, using
26989 the
26990 <A HREF="h_common_flag">Flag command</A>.
26991 Or they may be marked Important by an Alpine
26992 <A HREF="h_mainhelp_filtering">Filter</A>
26993 that you have set up.
26994 </DD>
26996 <DT>first-important-or-unseen</DT>
26997 <DD>This selects the first of the first unseen and the first important
26998 messages.
26999 </DD>
27001 <DT>first-important-or-recent</DT>
27002 <DD>This selects the first of the first recent and the first important
27003 messages.
27004 </DD>
27006 <DT>first</DT>
27007 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
27008 If all messages are deleted you start on the last message.
27009 </DD>
27011 <DT>last</DT>
27012 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
27013 If all messages are deleted you start on the last message.
27014 </DD>
27015 </DL>
27017 <P>
27018 NOTE: For newsgroups in the incoming collection, "first-unseen" and
27019 "first-recent" are the same and are affected by whether or not the
27020 feature
27021 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
27022 is turned on.
27023 Also, there is no permanent storage in news for an Important flag.
27024 This means that no messages will be marked Important when a newsgroup is
27025 first opened.
27027 <P>
27028 <UL>
27029 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27030 </UL><P>
27031 <End of help on this topic>
27032 </BODY>
27033 </HTML>
27034 ====== h_config_browser =====
27035 <HTML>
27036 <HEAD>
27037 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
27038 </HEAD>
27039 <BODY>
27040 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
27041 <!--chtml if pinemode="os_windows"-->
27042 PC-Alpine users do not need to enter anything here, unless:<UL>
27043 <LI> they want to override, for use with Alpine, the application defined
27044 in the Windows operating system for handling URLs; or
27045 <LI> they are (planning on) using the same configuration file with
27046 Unix Alpine.
27047 </UL>
27048 <P>
27049 Note that if using a viewer that has a space in its path, you should
27050 use the DOS name for that directory or file. Example:
27051 <PRE>
27052 url-viewer=C:\Progra~1\mozilla\mozilla.exe
27053 </PRE>
27054 <HR><P>
27055 <!--chtml endif-->
27056 This option affects Alpine's handling of URLs that are found in
27057 messages you read. Normally, only URLs Alpine can handle directly
27058 are automatically offered for selection in the "Message
27059 Text" screen. When one or more applications
27060 capable of deciphering URLs on their command line are added here, Alpine
27061 will choose the first available to display URLs it cannot handle directly.
27062 A viewer's availability is based on its being specified with a <B>full
27063 directory path</B> and the evaluation of any optionally supplied
27064 parameters described below.
27066 <P>
27067 Additionally, to support various connection methods and applications, each
27068 entry in this list can optionally begin with one or more of
27069 the following special tokens. The allowed tokens include:
27071 <P>
27072 <DL>
27073 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
27074 <DD>
27075 The <VAR>test-string</VAR> is a shell command that Alpine will run to
27076 evaluate a viewer's availability. The command specified by the test
27077 string is run and if its resulting exit status is non-zero, Alpine will
27078 not consider the associated viewer for use.
27079 </DD>
27081 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
27082 <DD>
27083 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
27084 URL schemes that are to be used with the associated viewer. This is
27085 the way to configure Alpine to recognize URLs other than the built-in set.
27086 <P>
27087 It can also be used to override Alpine's built-in handlers.
27088 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
27089 and Alpine would use (provided it passed all other criteria) the associated
27090 viewer when it encounterd a URL of the form "news:comp.mail.pine".
27092 </DD>
27093 </DL>
27095 <P>
27096 By default, Alpine will simply append a space character followed by the
27097 selected URL prior to launching the command in your specified SHELL. You can
27098 optionally specify where in the command the selected URL should appear
27099 by using the "_URL_" token. All occurrences found in the command
27100 will be replaced with the selected URL before the command is handed
27101 to the shell. If such replacement occurs, the default appending of the
27102 selected URL does not take place.
27104 <P>
27105 NOTE: If the viewer you specify has any command-line arguments,
27106 including the "_URL_" token, you will need to add a
27107 double-quote character before the command path and after the last
27108 argument (see the "lynx" example below).
27110 <P>
27111 So, here are some example entries:
27112 <PRE>
27113 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
27114 "/usr/local/bin/lynx _URL_"
27115 C:\BIN\NETSCAPE.BAT
27116 </PRE>
27117 <P>
27118 This example shows that for the first viewer in the list to be used
27119 the environment variable "DISPLAY" must be defined. If it
27120 is, then the path and file "/usr/local/bin/netscape" must exist.
27121 If neither condition is met,
27122 then the path and file "/usr/local/bin/lynx" must exist.
27123 If it does, then the "_URL_" token is replaced by the selected URL.
27124 If the path to "lynx" is invalid,
27125 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
27126 Note that the last
27127 entry is a DOS/Windows path. This is one way to support Alpine running
27128 on more than one architecture with the same configuration file.<P>
27129 <P>
27130 <!--chtml if pinemode="os_windows"-->
27131 <!--chtml else-->
27132 Note that depending on the type of browser used and the method of
27133 its invocation (such as whether it will open in a separate window) from
27134 the MESSAGE TEXT screen, the browser may "supplant"
27135 the MESSAGE TEXT screen, and you will have to quit the browser to return to
27136 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
27137 In other words, launching the browser from Alpine may make Alpine
27138 "disappear" (although it is still "running")
27139 until you close the browser again.<P>
27140 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27141 environment: for advanced users and systems administrators</A>
27142 </UL>
27143 <!--chtml endif-->
27144 <P>If you are unsure what browsers are available on your system or how to
27145 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
27146 local computing support staff.
27147 <P><UL>
27148 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27149 </UL>
27150 <P>
27151 <End of help on this topic>
27152 </BODY>
27153 </HTML>
27154 ====== h_config_browser_xterm =====
27155 <HTML>
27156 <HEAD>
27157 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
27158 </HEAD>
27159 <BODY>
27160 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27161 environment: for advanced users and systems administrators</H1>
27162 If you are using Alpine with an X-terminal (emulator) and want to define an
27163 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
27164 you may want to do so in a manner that causes any <B>already</B>
27165 invoked viewer application to be used for viewing URLs you select from Alpine
27166 messages, and a <B>new</B> URL-viewer process to be
27167 started <B>only</B> if the same application has <B>not already</B>
27168 been launched -- for one reason, to avoid file-locking contentions among
27169 multiple invocations of the same URL-viewer application.
27170 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
27171 option does not do this.) A method of doing that would be:<OL>
27172 <LI> use
27173 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
27174 check (using commands appropriate for your Unix shell
27175 in place of <VAR>test-string</VAR>) for the presence of a
27176 lockfile created by the URL-viewer application -- which implies that the
27177 application is already running, though this is not foolproof.
27178 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
27179 application with its appropriate command line option(s) to
27180 show the URL selected from the Alpine message in an already open window of
27181 that application, or perhaps in a new window of that application.
27183 <LI> In the
27184 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
27185 application without those command line options, but this time using the
27186 _TEST(...)_ token to check whether the environment variable "DISPLAY"
27187 is defined.
27188 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
27189 windows environment (for instance, using VT-100 terminal emulation), you
27190 may wish to specify a non-X windows URL-viewer application such as Lynx
27191 as the last entry.
27192 </OL><BR>
27193 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
27194 the command shell, the URL-viewer application(s), and possibly the specific
27195 version of the latter, you are using.
27196 <P>
27197 Relevant command
27198 line options for the Netscape browser for showing URLs (selected from Alpine)
27199 when Netscape is already running are discussed in the document
27200 "Remote Control of UNIX Netscape"
27201 found at the URL (as of 12 Aug. 1998):
27202 <P>
27204 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
27206 <P>(If the URL-viewer application is
27207 <B>not</B> running on the same host as Alpine, but being launched from an
27208 applications server, you may not be able to use the command line options for
27209 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
27210 <P>
27211 <!--chtml if this-method="shown-to-work"-->
27212 An example using the Korn shell and the Netscape browser (first entry wrapped
27213 because of its length, but should all appear on one line):
27214 <P>
27215 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
27217 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
27218 "/usr/local/bin/lynx '_URL_'"
27219 <P>
27220 <!--chtml endif-->
27221 <P>
27222 <UL>
27223 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27224 </UL><P>
27225 <End of help on this topic>
27226 </BODY>
27227 </HTML>
27228 ====== h_config_enable_full_hdr =====
27229 <HTML>
27230 <HEAD>
27231 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
27232 </HEAD>
27233 <BODY>
27234 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
27236 This feature enables the "H Full Headers" command which toggles between
27237 the display of all headers in the message and the normal edited view of
27238 headers. The Full Header command also controls which headers are included
27239 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
27240 Full Header mode will respect the
27241 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
27242 feature setting.)
27243 <P>
27244 If Full Header mode is turned on and you Forward a message, you will
27245 be asked if you'd like to forward the message as an attachment, as opposed
27246 to including the text of the message in the body of your new message.
27247 <P>
27248 If you have also turned on the
27249 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
27250 option then the Full Headers command actually rotates through three states
27251 instead of just two.
27252 The first is the normal view with long quotes suppressed.
27253 The second is the normal view but with the long quotes included.
27254 The last enables the display of all headers in the message.
27255 When using Export, Pipe, Print, Forward, or Reply the quotes are
27256 never suppressed, so the first two states are identical.
27257 <P>
27258 Normally, the Header Mode will reset
27259 to the default behavior when moving to a new message.
27260 The mode can be made to persist from message to message by setting the feature
27261 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
27262 <P>
27263 <UL>
27264 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27265 </UL><P>
27266 <End of help on this topic>
27267 </BODY>
27268 </HTML>
27269 ====== h_config_enable_full_hdr_and_text =====
27270 <HTML>
27271 <HEAD>
27272 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
27273 </HEAD>
27274 <BODY>
27275 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
27277 This feature affects how the "H Full Headers" command displays
27278 message text. If set, the raw message text will be displayed. This
27279 especially affects MIME formatted email, where the entire MIME format
27280 will be displayed. This feature similarly affects how messages are
27281 included for the Export, Pipe, Print, Forward, and Reply functions.
27282 <P>
27283 When viewing a raw message that has attachments with this feature set,
27284 you will not be able to view attachments without first leaving full
27285 headers mode. This is because MIME parsing is not done on the raw message.
27286 <P>
27287 <UL>
27288 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27289 </UL><P>
27290 <End of help on this topic>
27291 </BODY>
27292 </HTML>
27293 ====== h_config_enable_pipe =====
27294 <HTML>
27295 <HEAD>
27296 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
27297 </HEAD>
27298 <BODY>
27299 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
27301 This feature enables the "| Pipe" command that sends the current message
27302 to the specified command for external processing.
27303 <P>
27305 A short description of how the pipe command works is given
27306 <A HREF="h_pipe_command">here</A>.
27308 <P>
27309 <UL>
27310 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27311 </UL><P>
27312 <End of help on this topic>
27313 </BODY>
27314 </HTML>
27315 ====== h_config_quell_full_hdr_reset =====
27316 <HTML>
27317 <HEAD>
27318 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
27319 </HEAD>
27320 <BODY>
27321 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
27323 The <A HREF="h_common_hdrmode">HdrMode Command</A>
27324 normally resets to the default state when switching to a new message.
27325 For example, if you've used the "H" command to turn on Full
27326 Headers for a message you are viewing, and then you type the Next command
27327 to look at the next message, the full headers will no longer be shown.
27328 Setting this feature disables that reset.
27329 Instead, the Header Mode remains the same from message to message.
27331 <P>
27332 The presence or absence of the HdrMode command is determined by the
27333 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
27334 Feature-List option.
27335 <P>
27336 <UL>
27337 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27338 </UL><P>
27339 <End of help on this topic>
27340 </BODY>
27341 </HTML>
27342 ====== h_config_enable_tab_complete =====
27343 <HTML>
27344 <HEAD>
27345 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
27346 </HEAD>
27347 <BODY>
27348 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
27350 This feature enables the TAB key when at a prompt for a filename. In this
27351 case, TAB will cause the partial name already entered to be automatically
27352 completed, provided the partial name is unambiguous.
27353 This feature is on by default.
27354 <P>
27355 Similarly, this feature also enables TAB completion of address book
27356 nicknames when at a prompt for a nickname,
27357 or when typing in an address field in the composer.
27358 <P>
27359 <End of help on this topic>
27360 </BODY>
27361 </HTML>
27362 ====== h_config_quit_wo_confirm =====
27363 <HTML>
27364 <HEAD>
27365 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
27366 </HEAD>
27367 <BODY>
27368 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
27370 This feature controls whether or not Alpine will ask for confirmation when a
27371 Quit command is received.
27372 <P>
27373 <End of help on this topic>
27374 </BODY>
27375 </HTML>
27376 ====== h_config_quote_replace_noflow =====
27377 <HTML>
27378 <HEAD>
27379 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
27380 </HEAD>
27381 <BODY>
27382 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
27384 This feature, which is only active when
27385 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
27386 also set,
27387 enables quote-replacement on non-flowed messages. It is off
27388 by default because a non-flowed message is more dependent on its format,
27389 and thus quote-replacement may cause less-than-pleasing results.
27390 Setting this feature will cause quote-replacement similar to that of flowed
27391 messages, but with the added possibility of long lines being wrapped
27392 into new lines if the Quote-Replacement-String is longer than the string
27393 it is replacing, which is "> ".
27394 <P>
27395 <End of help on this topic>
27396 </BODY>
27397 </HTML>
27398 ====== h_config_enable_jump =====
27399 <HTML>
27400 <HEAD>
27401 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27402 </HEAD>
27403 <BODY>
27404 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27406 When this feature is set you may enter a number (followed by RETURN)
27407 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27408 screens. In other words, it obviates the need for typing the "J" for the
27409 Jump command.
27410 <P>
27411 <End of help on this topic>
27412 </BODY>
27413 </HTML>
27414 ====== h_config_enable_alt_ed =====
27415 <HTML>
27416 <HEAD>
27417 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27418 </HEAD>
27419 <BODY>
27420 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27422 If this feature is set (the default), and the
27423 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27424 <B>is not</B> set, entering
27425 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27426 for the name of the editor you would like to use.
27427 <P>
27428 If the environment variable $EDITOR is set, its value will be offered as
27429 a default.
27430 <P>
27431 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27432 <B>is</B> set, the ^_ key will activate the specified
27433 editor without prompting, in which case it is not necessary to
27434 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27435 <P>
27436 <UL>
27437 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27438 </UL><P>
27439 <End of help on this topic>
27440 </BODY>
27441 </HTML>
27442 ====== h_config_alt_ed_now =====
27443 <HTML>
27444 <HEAD>
27445 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27446 </HEAD>
27447 <BODY>
27448 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27450 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27451 variable are both set, Alpine will
27452 automatically activate the specified editor when the cursor is moved from
27453 the header of the message being composed into the message text. For
27454 replies, the alternate editor will be activated immediately. If this
27455 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27456 automatically ask for the name of an alternate editor when the cursor
27457 is moved out of the header being composed, or if a reply is being done.
27459 <P><UL>
27460 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27461 </UL>
27462 <P>
27463 <End of help on this topic>
27464 </BODY>
27465 </HTML>
27466 ====== h_config_enable_bounce =====
27467 <HTML>
27468 <HEAD>
27469 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27470 </HEAD>
27471 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27472 <BODY>
27474 Setting this feature enables the "B Bounce" command, which will prompt
27475 for an address and *remail* the message to the new recipient. This command
27476 is used to re-direct messages that you have received in error, or need to
27477 be redirected for some other reason (e.g. list moderation). The final
27478 recipient will see a header indicating that you have Resent the msg, but
27479 the message's From: header will show the original author of the message,
27480 and replies to it will go back to that author, and not to you.
27481 <P>
27482 <End of help on this topic>
27483 </BODY>
27484 </HTML>
27485 ====== h_config_enable_agg_ops =====
27486 <HTML>
27487 <HEAD>
27488 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27489 </HEAD>
27490 <BODY>
27491 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27493 When this feature is set you may use the commands and subcommands that relate to
27494 performing operations on more than one message at a time. We call these
27495 "aggregate operations". In particular, the
27496 <!--chtml if pinemode="function_key"-->"F5
27497 <!--chtml else-->";
27498 <!--chtml endif--> Select",
27500 <!--chtml if pinemode="function_key"-->
27501 "F6
27502 <!--chtml else-->
27503 "A
27504 <!--chtml endif-->
27505 Apply", and
27506 <!--chtml if pinemode="function_key"-->
27507 "F4
27508 <!--chtml else-->
27509 "Z
27510 <!--chtml endif-->
27511 Zoom" commands are enabled by this feature. Select is used to
27512 "tag" one or more messages meeting the specified criteria. Apply can
27513 then be used to apply any message command to all of the selected/tagged
27514 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27515 view between just those Selected and all messages in the folder.
27516 <P>
27517 This feature also enables the
27518 <!--chtml if pinemode="function_key"-->
27519 "F7"
27520 <!--chtml else-->
27521 "^X"
27522 <!--chtml endif-->
27524 subcommand in the MESSAGE INDEX
27525 WhereIs command that causes all messages matching the WhereIs argument to
27526 become selected; and the Select, Select Current, and ZoomMode commands in the
27527 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27528 <P>
27529 Some related help topics are
27530 <UL>
27531 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27532 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27533 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27534 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27535 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27536 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27537 </UL>
27538 <P>
27539 <UL>
27540 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27541 </UL><P>
27542 <End of help on this topic>
27543 </BODY>
27544 </HTML>
27546 ====== h_config_enable_flag =====
27547 <HTML>
27548 <HEAD>
27549 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27550 </HEAD>
27551 <BODY>
27552 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27554 Setting this feature enables the
27555 <A HREF="h_common_flag">"* Flag"</A>
27556 command that allows you to
27557 manipulate the status flags associated with a message. By default, Flag
27558 will set the "Important" flag, which results in an asterisk being
27559 displayed in column one of the MESSAGE INDEX for such messages.
27560 <P>
27561 <End of help on this topic>
27562 </BODY>
27563 </HTML>
27564 ====== h_config_flag_screen_default =====
27565 <HTML>
27566 <HEAD>
27567 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27568 </HEAD>
27569 <BODY>
27570 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27572 The feature modifies the behavior of the
27573 <a href="h_common_flag">Flag</a>
27574 command (provided it too is
27575 <A HREF="h_config_enable_flag">enabled</A>).
27576 By default, when the "* Flag" command is selected,
27577 Alpine offers a prompt to set one of several flags and also offers the
27578 option of entering the detailed flag manipulation screen via the "^T"
27579 key. Enabling this feature causes Alpine to immediately enter the detailed
27580 flag screen rather than first offer the simple prompt.
27581 The
27582 <A HREF="h_config_flag_screen_kw_shortcut"><!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></A> option offers a slightly different way of setting keywords.
27583 <P>
27584 <End of help on this topic>
27585 </BODY>
27586 </HTML>
27587 ====== h_config_flag_screen_kw_shortcut =====
27588 <HTML>
27589 <HEAD>
27590 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27591 </HEAD>
27592 <BODY>
27593 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27595 This feature modifies the behavior of the
27596 <a href="h_common_flag">Flag</a> command
27597 and the <A HREF="h_index_cmd_select">Select</A> command.
27598 This feature is set by default.
27599 When this feature is not set, when the "* Flag" command is selected,
27600 Alpine offers a prompt to set one of several flags and also offers the
27601 option of entering the detailed flag manipulation screen via the "^T"
27602 key.
27603 If you have
27604 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27605 defined, then enabling this feature adds a shortcut way to set or unset
27606 keywords.
27607 You use "*" followed by the first letter of a keyword (or the nickname of
27608 a keyword if you've given it a nickname) and that will set the keyword.
27609 <P>
27610 An example is easier to understand than the explanation.
27611 The flag command can always be used to set the system flags.
27612 For example, to set the Answered flag you would type
27613 <P>
27614 <CENTER><SAMP>* A</SAMP></CENTER>
27615 <P>
27616 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27617 option in the Config screen.
27618 By default, to set a keyword like "Work" you would usually
27619 have to go to the Flag Details screen using
27620 the "^T To Flag Details" command.
27621 Instead, if you have enabled this feature, you may type
27622 <P>
27623 <CENTER><SAMP>* W</SAMP></CENTER>
27624 <P>
27625 to set the Work flag, or
27626 <P>
27627 <CENTER><SAMP>* ! W</SAMP></CENTER>
27628 <P>
27629 to unset it.
27630 Just like for the other flag setting commands, the case of the letter does
27631 not matter, so "w" or "W" both set the "Work"
27632 keyword.
27633 <P>
27634 Notice that you can only use this trick for one keyword that begins
27635 with "W".
27636 If you happen to have a "Work" keyword and another keyword that is
27637 "WIFI" the "* W" command will set the first one in
27638 your list of keywords.
27639 Also, there are five letters that are reserved for system
27640 flags and the NOT command.
27641 If you type "* A" it will always set the Answered flag, not
27642 your "Aardvark" keyword.
27643 In order to set the "Aardvark" keyword you'll still have to use
27644 the Flag Details screen.
27645 <P>
27646 Because enabling the
27647 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
27648 option causes Alpine to skip directly to the Flag Details screen when the
27649 Flag command is used,
27650 setting it will cause this feature to have no effect at all.
27651 <P>
27652 Similarly, when Selecting by Keyword, setting this option will allow you
27653 to use Keyword initials instead of full keywords.
27654 <P>
27655 <End of help on this topic>
27656 </BODY>
27657 </HTML>
27658 ====== h_config_can_suspend =====
27659 <HTML>
27660 <HEAD>
27661 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
27662 </HEAD>
27663 <BODY>
27664 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
27666 Setting this feature will allow you to type ^Z (Control Z) to
27667 <!--chtml if pinemode="os_windows"-->
27668 minimize Alpine into its icon, bringing into focus whatever
27669 application is running behind the PC-Alpine window.
27670 <!--chtml else-->
27671 temporarily suspend Alpine.
27673 <P>
27674 This does not exit Alpine, but puts it in the background to watch
27675 for new mail and such. Normally, you type a command, such
27676 as "fg" at your system prompt to return to your Alpine session.
27678 <P>
27679 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
27680 adjusts whether Alpine is placed into the background of the shell its
27681 running in or starts a news shell.
27682 <!--chtml endif-->
27684 <P>
27685 <UL>
27686 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27687 </UL><P>
27688 <End of help on this topic>
27689 </BODY>
27690 </HTML>
27691 ====== h_config_take_lastfirst ======
27692 <HTML>
27693 <HEAD>
27694 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
27695 </HEAD>
27696 <BODY>
27697 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
27699 Normally, when TakeAddr is used to copy an address from a message into
27700 an address book entry, Alpine will attempt to rewrite the full name of the
27701 address in the form
27702 <P>
27704 Last, First<P>
27706 instead of<P>
27708 First Last
27710 <P>
27711 It does this because many people find it useful to sort by Last name
27712 instead of First name. If this feature is set, then the TakeAddr command
27713 will not attempt to reverse the name in this manner.
27714 <P>
27715 <End of help on this topic>
27716 </BODY></HTML>
27717 ====== h_config_disable_regex ======
27718 <HTML>
27719 <HEAD>
27720 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
27721 </HEAD>
27722 <BODY>
27723 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
27725 Normally, the
27726 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
27727 option is interpreted as a regular expression.
27728 One type of address that might cause trouble is an address that
27729 contains a plus sign.
27730 If you want to have an address with a plus as one of your
27731 <!--#echo var="VAR_alt-addresses"-->
27732 and you don't want to use regular expressions, then setting this
27733 feature will cause Alpine to treat the addresses you list literally instead.
27734 <P>
27735 <End of help on this topic>
27736 </BODY></HTML>
27737 ====== h_config_take_fullname ======
27738 <HTML>
27739 <HEAD>
27740 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
27741 </HEAD>
27742 <BODY>
27743 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
27745 Normally, when TakeAddr is used to copy an address or addresses
27746 from a message into an address book entry, Alpine will try to preserve
27747 the full name associated with each address in the list of addresses.
27748 The reason for this is so that if the entry is a list or later becomes a
27749 list, then information about the individual addresses in the list
27750 is preserved.
27751 If you would rather just have the simple addresses in the list of addresses,
27752 set this feature. For example, with the default setting you might
27753 see something like this in the ADDRESS BOOK editor after you type TakeAddr
27754 <P>
27755 <PRE>
27756 Nickname : nick
27757 Fullname : Bedrock Elders
27758 Fcc :
27759 Comment :
27760 Addresses : Fred Flintstone <flint@bedrock.org>,
27761 Barney Rubble <rubble@bedrock.org>
27762 </PRE>
27763 <P>
27764 but with this feature set it would look like
27765 <P>
27766 <PRE>
27767 Nickname : nick
27768 Fullname : Bedrock Elders
27769 Fcc :
27770 Comment :
27771 Addresses : flint@bedrock.org,
27772 rubble@bedrock.org
27773 </PRE>
27774 <P>
27775 instead. Note the difference in the Addresses field.
27776 <P>
27777 <End of help on this topic>
27778 </BODY></HTML>
27779 ====== h_config_print_from ======
27780 <HTML>
27781 <HEAD>
27782 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
27783 </HEAD>
27784 <BODY>
27785 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
27787 If this feature is set, then the Berkeley-mail style From line is included
27788 at the start of each message that is printed. This line looks something
27789 like the following, with the address replaced by the address from the
27790 From line of the message being printed:
27791 <P>
27792 From user@domain.somewhere.com Mon May 13
27793 14:11:06 1998
27794 <P>
27795 <End of help on this topic>
27796 </BODY>
27797 </HTML>
27798 ====== h_config_expanded_distlists ======
27799 <HTML>
27800 <HEAD>
27801 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
27802 </HEAD>
27803 <BODY>
27804 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
27805 If this feature is set, then distribution lists in the address book
27806 screen will always be expanded automatically.
27807 <P>
27808 <End of help on this topic>
27809 </BODY>
27810 </HTML>
27811 ====== h_config_compose_news_wo_conf ======
27812 <HTML>
27813 <HEAD>
27814 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
27815 </HEAD>
27816 <BODY>
27817 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
27818 This feature controls one aspect of Alpine's Composer. If you enter the
27819 composer while reading a newsgroup, you will normally be prompted to
27820 determine whether you intend the new message to be posted to the current
27821 newsgroup or not. If this feature is set, Alpine will not prompt you
27822 in this situation, and will assume that you do indeed wish to post
27823 to the newsgroup you are reading.
27824 <P>
27825 <End of help on this topic>
27826 </BODY>
27827 </HTML>
27828 ====== h_config_compose_rejects_unqual ======
27829 <HTML>
27830 <HEAD>
27831 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
27832 </HEAD>
27833 <BODY>
27834 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
27836 This feature controls one aspect of the message composer; in particular,
27837 what happens when an unqualified name is entered into an address header.
27838 If set, unqualified names entered as addresses will be treated as errors
27839 unless they match an addressbook nickname. Alpine will not attempt to turn
27840 them into complete addresses by adding your local domain.<P>
27842 A complete (fully qualified) address is one containing a username followed
27843 by an "@" ("at") symbol, followed by a domain name (e.g.
27844 "jsmith@example.com"). An unqualified name is one <B>without</B>
27845 the "@" symbol and domain name (e.g. "jsmith").
27847 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
27849 <P>
27851 When you enter a fully qualified address, Alpine does not interpret or
27852 modify it, but simply passes it on to the mail-transport-agent (MTA) for
27853 your system. Alpine conforms to the Internet standards governing message
27854 headers and will not send an unqualifed name to the MTA. Therefore, when
27855 you enter an unqualified name, Alpine will normally attempt to turn it into
27856 a fully qualified address, first by checking to see if you have entered a
27857 matching nickname in your addressbook, or failing that, by simply adding
27858 your own domain to the name entered. So if your address is
27859 "jsmith@example.com" and you enter "fred", then (assuming
27860 "fred" is not a nickname in your addressbook), Alpine will turn
27861 that into "fred@example.com".<P>
27863 There are situations where it is not desirable for Alpine to interpret such
27864 unqualified names as valid (local) addresses. For example, if "fred"
27865 turned out to be a typo (intended to be an addressbook nickname), but
27866 there actually was a "fred" in your local domain, the message might
27867 be mis-delivered without your realizing it. In order to reduce the likelihood
27868 of such accidents, setting this feature will cause Alpine to treat such
27869 addresses as errors, and require that you explicitly enter the full local
27870 address (e.g. "fred@example.com") or correct the name so that it
27871 matches an address book nickname.<P>
27873 Consider this a safety feature against mis-directed mail.
27874 <P>
27875 <UL>
27876 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27877 </UL><P>
27878 <End of help on this topic>
27879 </BODY>
27880 </HTML>
27881 ====== h_config_quell_local_lookup ======
27882 <HTML>
27883 <HEAD>
27884 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
27885 </HEAD>
27886 <BODY>
27887 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
27889 This feature controls an aspect of Alpine's Composer, and if needed, will
27890 usually be set by your system manager in Alpine's system-wide configuration
27891 file. Specifically, if this feature is set, Alpine will not attempt to look
27892 in the system password file to find a Full Name for the entered address.
27893 <P>
27894 Normally, names you enter into address fields (e.g. To: or Cc:) are
27895 checked against your address book(s) to see if they match an address book
27896 nickname. Failing that, (in Unix Alpine) the name is then checked against
27897 the Unix password file. If the entered name matches a username in the
27898 system password file, Alpine extracts the corresponding Full Name information
27899 for that individual, and adds that to the address being entered.
27900 <P>
27901 However, password file matching can have surprising (incorrect) results if
27902 other users of the system do not receive mail at the domain you are using.
27903 That is, if either the
27904 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
27905 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
27906 option
27907 is set such that the administrative domain of other users on the system
27908 isn't accurately reflected, Alpine should be told that a passwd file match
27909 is coincidental, and Full Name info will be incorrect. For example, a
27910 personal name from the password file could get falsely paired with the
27911 entered name as it is turned into an address in the configured domain.
27912 <P>
27913 If you are seeing this behavior, enabling this feature will prevent Unix
27914 Alpine from looking up names in the password file to find the Full Name
27915 for incomplete addresses you enter.<P>
27916 <UL>
27917 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27918 </UL>
27919 <P>
27920 <End of help on this topic>
27921 </BODY>
27922 </HTML>
27923 ====== h_config_tab_checks_recent ======
27924 <HTML>
27925 <HEAD>
27926 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
27927 </HEAD>
27928 <BODY>
27929 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
27931 In a FOLDER LIST screen, the TAB key usually just changes which
27932 folder is highlighted.
27933 If this feature is set, then the TAB key will cause the number of
27934 recent messages and the total number of messages in the highlighted folder
27935 to be displayed instead.
27937 <P>
27938 <End of help on this topic>
27939 </BODY>
27940 </HTML>
27941 ====== h_config_maildrops_preserve_state ======
27942 <HTML>
27943 <HEAD>
27944 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
27945 </HEAD>
27946 <BODY>
27947 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
27949 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
27950 Normally, when mail is moved from a Mail Drop folder to a destination
27951 folder, it is delivered as new mail.
27952 Any Seen/New, Answered, Important/Flagged state that has changed will be
27953 ignored.
27954 All of the mail will be considered unSeen, unAnswered, and unImportant after
27955 it is moved.
27956 <P>
27957 If this feature is set, then the state changes that have been made
27958 to the messages in the Mail Drop folder will be preserved.
27959 <P>
27960 In any case, messages that are already marked Deleted when the
27961 mail is to be moved from the Mail Drop will be ignored.
27962 <P>
27963 <End of help on this topic>
27964 </BODY>
27965 </HTML>
27966 ====== h_config_preopen_stayopens ======
27967 <HTML>
27968 <HEAD>
27969 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
27970 </HEAD>
27971 <BODY>
27972 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
27974 This feature is related to the option
27975 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
27976 Normally, Stay Open folders are only opened on demand, when the user
27977 asks to open them.
27978 From then on they are kept open for the duration of the session.
27979 However, if this feature is set, then the Stay Open folders will all be
27980 opened at startup, at the same time that the INBOX is opened.
27982 <P>
27983 <End of help on this topic>
27984 </BODY>
27985 </HTML>
27986 ====== h_config_expunge_inbox ======
27987 <HTML>
27988 <HEAD>
27989 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
27990 </HEAD>
27991 <BODY>
27992 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
27994 The INBOX is normally treated differently from regular folders in several
27995 ways.
27996 One of the differences is that the normal "close" sequence of
27997 events is deferred until Alpine is exited, instead of happening when you
27998 leave the INBOX to view another folder.
27999 The "close" sequence normally includes the Expunging
28000 of deleted messages
28001 (either automatically or after a prompt, controlled by the features
28002 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28003 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28004 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28005 handling of the
28006 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
28008 <P>
28009 If this feature is set the "close" sequence handling will take
28010 place every time you leave the INBOX.
28011 The INBOX will still be kept open, but the offer to Expunge and the archiving
28012 to the <!--#echo var="VAR_read-message-folder"-->
28013 will take place each time you leave the INBOX instead of only once at the
28014 end of the session.
28016 <P>
28017 <End of help on this topic>
28018 </BODY>
28019 </HTML>
28020 ====== h_config_expunge_stayopens ======
28021 <HTML>
28022 <HEAD>
28023 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
28024 </HEAD>
28025 <BODY>
28026 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
28028 This feature is related to the option
28029 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
28030 Stay Open folders are treated differently from regular folders in several
28031 ways.
28032 One of the differences is that the normal "close" sequence of
28033 events is deferred until Alpine is exited, instead of happening when you
28034 leave the folder to view another folder.
28035 The "close" sequence normally includes the Expunging
28036 of deleted messages
28037 (either automatically or after a prompt, controlled by the features
28038 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28039 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28040 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28041 handling of
28042 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
28044 <P>
28045 If this feature is set the "close" sequence handling will take
28046 place when you leave the Stay Open folder.
28047 The folder will still be kept open, but the offer to Expunge and the archiving
28048 will take place each time you leave the folder instead of only once at the
28049 end of the session.
28050 This feature does not affect the INBOX, which will still only be processed
28051 when you exit Alpine.
28052 However, there is a similar feature that affects only the INBOX called
28053 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
28055 <P>
28056 <End of help on this topic>
28057 </BODY>
28058 </HTML>
28059 ====== h_config_preserve_start_stop ======
28060 <HTML>
28061 <HEAD>
28062 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
28063 </HEAD>
28064 <BODY>
28065 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
28067 This feature controls how special control key characters, typically
28068 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
28069 are known as the "stop" and "start" characters and are sometimes used in
28070 communications paths to control data flow between devices that operate at
28071 different speeds.
28073 <P>
28075 By default, Alpine turns the system's handling of these special characters
28076 off except during printing. However, if you see Alpine reporting input errors
28077 such as:
28078 <P>
28079 [ Command "^Q" not defined for this screen.]
28080 <P>
28081 and, at the same time, see your display become garbled, then it is likely
28082 that setting this option will solve the problem. Be aware, though, that
28083 enabling this feature will also cause Alpine to ostensibly "hang"
28084 whenever the Ctrl-S key combination is entered as the system is now
28085 interpreting such input as a "stop output" command. To "start
28086 output" again, simply type Ctrl-Q.
28087 <P>
28088 <End of help on this topic>
28089 </BODY>
28090 </HTML>
28091 ====== h_config_enable_incoming ======
28092 <HTML>
28093 <HEAD>
28094 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
28095 </HEAD>
28096 <BODY>
28097 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
28099 Alpine's Incoming Message Folders collection
28100 provides a convenient way to access multiple incoming folders.
28101 It is also useful if you have accounts on multiple computers.
28102 <P>
28104 If set, this feature defines a pseudo-folder collection called
28105 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
28106 in this collection will be your INBOX, which will no longer show up in
28107 your Default folder collection.
28108 <P>
28110 You may add more folders to the Incoming Message Folders collection by
28111 using the
28112 <!--chtml if pinemode="function_key"-->
28113 "F10
28114 <!--chtml else-->
28115 "A
28116 <!--chtml endif-->
28117 Add" command in the FOLDER LIST screen. You will be prompted for
28118 the host the folder is stored on (which defaults to the same host used
28119 for your INBOX), a nickname, and the actual folder name. Once a set
28120 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
28121 or MESSAGE TEXT screens) may be used to scan the folders for those
28122 with Recent messages. If you add more folders to
28123 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
28124 no effect.
28125 <P>
28126 NOTE: Normally the software that actually delivers mail (the stuff that happens
28127 before Alpine is involved) is in a better position to do delivery filtering
28128 than is Alpine itself.
28129 If possible, you may want to look at programs such as
28130 "filter" or "procmail", which are examples of delivery
28131 filtering programs.
28132 If you'd prefer to have Alpine do the filtering for you, you may set that
28133 up.
28134 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
28135 <P>
28136 <UL>
28137 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28138 </UL><P>
28139 <End of help on this topic>
28140 </BODY>
28141 </HTML>
28142 ====== h_config_enable_incoming_checking ======
28143 <HTML>
28144 <HEAD>
28145 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
28146 </HEAD>
28147 <BODY>
28148 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
28150 This feature is only operational if you have enabled the optional
28151 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
28152 If you do have Incoming Message Folders and you also set this feature,
28153 then the number of Unseen messages in each folder will be displayed
28154 in the FOLDER LIST screen for the Incoming Message Folders.
28155 The number of Unseen messages in a folder will be displayed in parentheses
28156 to the right of the name of each folder.
28157 If there are no Unseen messages in a folder then only the name
28158 is displayed, not a set of parentheses with zero inside them.
28159 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
28160 the Incoming Message Folders to cause an immediate update.
28161 <P>
28162 If a check for Unseen messages fails for a particular folder then Alpine
28163 will no longer attempt to check that folder for the duration of the
28164 session and this will be indicated by a question mark inside the
28165 parentheses.
28166 <P>
28167 The features
28168 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
28169 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
28170 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
28171 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
28172 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
28173 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
28174 all affect how this feature behaves.
28175 <P>
28176 <UL>
28177 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28178 </UL><P>
28179 <End of help on this topic>
28180 </BODY>
28181 </HTML>
28182 ====== h_config_incoming_checking_total ======
28183 <HTML>
28184 <HEAD>
28185 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
28186 </HEAD>
28187 <BODY>
28188 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
28190 This option has no effect unless the feature
28191 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28192 is set, which in turn has no effect unless
28193 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28194 is set.
28195 <P>
28196 When incoming folder checking is turned on the default is to display
28197 the number of unseen messages in each folder.
28198 More precisely, it is the number of undeleted unseen messages.
28199 Using this option you may also display the total number of messages
28200 in each folder.
28201 Instead of a single number representing the number of unseen messages
28202 you will get two numbers separated by a slash character.
28203 The first is the number of unseen messages and the second is the
28204 total number of messages.
28205 <P>
28206 You may also use the recent message count instead of the unseen message
28207 count by turning on the feature
28208 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>.
28209 <P>
28210 <UL>
28211 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28212 </UL><P>
28213 <End of help on this topic>
28214 </BODY>
28215 </HTML>
28216 ====== h_config_incoming_checking_recent ======
28217 <HTML>
28218 <HEAD>
28219 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
28220 </HEAD>
28221 <BODY>
28222 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
28224 This option has no effect unless the feature
28225 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28226 is set, which in turn has no effect unless
28227 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28228 is set.
28229 <P>
28230 When incoming folder checking is turned on the default is to display
28231 the number of unseen messages in each folder.
28232 More precisely, it is the number of undeleted unseen messages.
28233 Using this option you may display the number of recent messages instead
28234 of the number of unseen messages.
28235 A message is only counted as recent if this is the first session to
28236 see it, so the recent count might be less than the unseen count.
28237 The difference between the two would be accounted for by the unseen messages
28238 in the folder which were there previously but have not been looked at yet.
28239 <P>
28240 If you simultaneously run more than one email client at a time
28241 (for example, you run more than one Alpine in parallel) then turning
28242 this feature on can cause some confusion.
28243 The confusion stems from the fact that each message is only considered to be
28244 recent in one session.
28245 That means that the counts of new messages may be different in the two
28246 Alpines running side by side, because each incoming message will only be
28247 counted as recent in one of the two sessions.
28248 <P>
28249 You may also display the total number of messages
28250 in each folder by using the
28251 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
28252 option.
28253 <P>
28254 <UL>
28255 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28256 </UL><P>
28257 <End of help on this topic>
28258 </BODY>
28259 </HTML>
28260 ====== h_config_attach_in_reply ======
28261 <HTML>
28262 <HEAD>
28263 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
28264 </HEAD>
28265 <BODY>
28266 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
28268 This feature controls an aspect of Alpine's Reply command. If set, any MIME
28269 attachments that were part of the original message will automatically be
28270 included in the Reply.
28271 <P>
28272 <End of help on this topic>
28273 </BODY>
28274 </HTML>
28275 ====== h_config_include_header =====
28276 <HTML>
28277 <HEAD>
28278 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
28279 </HEAD>
28280 <BODY>
28281 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
28283 This feature controls an aspect of Alpine's Reply command. If set, and the
28284 original message is being included in the reply, then headers from that
28285 message will also be part of the reply.
28286 <P>
28287 <End of help on this topic>
28288 </HEAD>
28289 </HTML>
28290 ====== h_config_sig_at_bottom =====
28291 <HTML>
28292 <HEAD>
28293 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
28294 </HEAD>
28295 <BODY>
28296 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
28298 This feature controls an aspect of Alpine's Reply command. If this feature
28299 is set, and the original message is being included in the reply, then the
28300 contents of your signature file (if any) will be inserted after the included
28301 message.
28302 <P>
28303 This feature does not affect the results of a Forward command.
28304 <P>
28305 <End of help on this topic>
28306 </BODY>
28307 </HTML>
28308 ====== h_config_sigdashes =====
28309 <HTML>
28310 <HEAD>
28311 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
28312 </HEAD>
28313 <BODY>
28314 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
28316 This feature enables support for the common USENET news convention
28317 of preceding a message signature with the special line consisting of
28318 the three characters "-- " (i.e., dash, dash, and space).
28320 <P>
28321 When enabled and a
28322 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
28323 Alpine will insert the special line before including the file's text (unless
28324 the special line already exists somewhere in the file's text).
28326 <P>
28327 In addition, when you Reply or Followup to a message containing one of
28328 these special lines and choose to include its text, Alpine will observe
28329 the convention of not including text beyond the special line in your
28330 reply.
28331 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28332 mode is enabled and turned on, then Alpine <EM>will</EM>
28333 include the text beyond the special line regardless of the setting of
28334 this feature.
28336 <P>
28337 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
28338 for a related feature.
28340 <P>
28341 <UL>
28342 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28343 </UL><P>
28344 <End of help on this topic>
28345 </BODY>
28346 </HTML>
28347 ====== h_config_new_thread_blank_subject =====
28348 <HTML>
28349 <HEAD>
28350 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
28351 </HEAD>
28352 <BODY>
28353 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
28355 When this feature is enabled (the default) Alpine will create a new thread
28356 every time that the subject line becomes empty at any time during composition.
28358 <P>
28359 This behavior is particularly useful in case you are replying to a message.
28360 Replying to a message causes the message to be in the same thread than the
28361 original message that is being replied to. However, many authors want to create
28362 a new message (in a different thread) while replying to a message, and they do
28363 this by changing the full subject, by first deleting the original subject and
28364 typing the new subject of the current message.
28366 <P>
28367 Enabling this feature causes that any time that the subject is deleted, the
28368 message being composed will be considered the first message of a new thread.
28370 <P>
28371 <UL>
28372 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28373 </UL><P>
28374 <End of help on this topic>
28375 </BODY>
28376 </HTML>
28377 ====== h_config_strip_sigdashes =====
28378 <HTML>
28379 <HEAD>
28380 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
28381 </HEAD>
28382 <BODY>
28383 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
28385 This feature doesn't do anything if the feature
28386 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
28387 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
28388 then turning on this feature enables support for the convention
28389 of not including text beyond the sigdashes line when Replying or Following
28390 up to a message and including the text of that message.
28391 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28392 mode is enabled and turned on, then Alpine <EM>will</EM>
28393 include the text beyond the special line regardless of the setting of
28394 this feature.
28395 <P>
28396 In other words, this is a way to turn on the signature stripping behavior
28397 without also turning on the dashes-adding behavior.
28398 <P>
28399 <UL>
28400 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28401 </UL><P>
28402 <End of help on this topic>
28403 </BODY>
28404 </HTML>
28405 ====== h_config_forward_as_attachment =====
28406 <HTML>
28407 <HEAD>
28408 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28409 </HEAD>
28410 <BODY>
28411 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28413 This feature affects the way forwarded message text is handled. When set, rather than
28414 include the text of the forwarded message below any additional text you provide in the
28415 composer, the forwarded message is attached in its entirety to the message you send.
28416 <P>
28417 This is useful in that it keeps the text you provide in the composer distinct from the
28418 text of the forwarded message. Similarly, it allows the recipient to
28419 conveniently operate on the forwarded message. For example, they might reply directly to
28420 the sender of the forwarded message, or process it as part of a spam report.
28421 <UL>
28422 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28423 </UL><P>
28424 <End of help on this topic>
28425 </BODY>
28426 </HTML>
28427 ====== h_config_preserve_field =====
28428 <HTML>
28429 <HEAD>
28430 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28431 </HEAD>
28432 <BODY>
28433 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28435 This feature affects Alpine's behavior when one replies to a message.
28436 When you receive a message, some or all of the recipients of the message
28437 have been added to the To: and Cc: fields. If you reply to such message,
28438 and this feature is disabled, then the original sender of the message is
28439 added to the To: field, and all other recipients are added to the Cc:
28440 field, while your address is added to the From: field.
28442 <P>
28443 However, if this feature is enabled, then Alpine will preserve the
28444 original fields as sent in the original message, so the Cc: and To:
28445 fields will be preserved. The sender's address will be added to the To:
28446 field, while your address is added to the From: field.
28448 <P>
28449 The behavior of this feature is that replies to all messages will behave
28450 in the way described above. If you only intend this to happen on a per
28451 message basis, then keep this feature disabled, and when replying to a
28452 message you will see a new option in the menu for the "Reply to all
28453 recipients?" question. In this case, pressing "p" will
28454 make Alpine toggle its question so you can preserve the To: and Cc:
28455 fields for that message only.
28457 <UL>
28458 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28459 </UL><P>
28460 <End of help on this topic>
28461 </BODY>
28462 </HTML>
28463 ====== h_config_sub_lists =====
28464 <HTML>
28465 <HEAD>
28466 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28467 </HEAD>
28468 <BODY>
28469 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28471 This feature affects the subcommands available when Saving,
28472 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28473 available. This command allows you to type in a substring of the folder
28474 you are looking for and when you type ^X it will display all folders
28475 that contain that substring in their names.
28476 This feature is set by default.
28478 <P>
28479 <End of help on this topic>
28480 </BODY>
28481 </HTML>
28482 ====== h_config_scramble_message_id =====
28483 <HTML>
28484 <HEAD>
28485 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28486 </HEAD>
28487 <BODY>
28488 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28490 Normally the Message-ID header that Alpine generates when sending a message
28491 contains the name of the computer from which the message is being sent.
28492 Some believe that this hostname could be used by spammers or could
28493 be used by others for nefarious purposes.
28494 If this feature is set, that name will be transformed with a simple
28495 Rot13 transformation.
28496 The result will still have the correct syntax for a Message-ID but the
28497 part of the MessageID that is often a domain name will not be an actual
28498 domain name because the letters will be scrambled.
28499 <P>
28500 In addition, other information such as the name program, version, and
28501 a code for operating system used to build Alpine, will be encoded using
28502 the Rot13 transformation, except for the version number which will be
28503 encoded using a Rot5 transformation.
28504 <P>
28505 It is possible (but unlikely?) that some spam detection
28506 software will use that as a reason to reject the mail as spam.
28507 It has also been reported that some spam detection software uses the
28508 fact that there are no dots after the "@" as a reason to reject
28509 messages.
28510 If your PC-Alpine Message-ID is using a name without a dot that is because
28511 that is what Windows thinks is your "Full computer name".
28512 The method used to set this varies from one type of Windows to another but
28513 check under Settings -> Control Panel -> System and
28514 look for Network Identification or Computer Name or something similar.
28515 How to set it is beyond the scope of Alpine.
28517 <P>
28518 <End of help on this topic>
28519 </BODY>
28520 </HTML>
28521 ====== h_downgrade_multipart_to_text =====
28522 <HTML>
28523 <HEAD>
28524 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28525 </HEAD>
28526 <BODY>
28527 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28529 <P>
28530 This feature affects Alpine's behavior when sending mail. Internet
28531 standards require Alpine to translate all non-ASCII characters in
28532 messages that it sends using MIME encoding. This encoding can be
28533 ostensibly broken for recipients if any agent between Alpine and the
28534 recipient, such as an email list expander, appends text to the
28535 message, such as list information or advertising. When sending such
28536 messages Alpine attempts to protect such encoding by placing extra
28537 MIME boundaries around the message text.
28538 <P>
28539 These extra boundaries are invisible to recipients that
28540 use MIME-aware email programs (the vast majority). However, if
28541 you correspond with users of email programs that are not MIME-aware,
28542 or do not handle the extra boundaries gracefully, you can
28543 use this feature to prevent Alpine from including the extra
28544 MIME information. Of course, it will increase the likelihood
28545 that non-ASCII text you send may appear corrupt to the recipient.
28546 <P>
28547 <End of help on this topic>
28548 </BODY>
28549 </HTML>
28550 ====== h_config_show_sort =====
28551 <HTML>
28552 <HEAD>
28553 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28554 </HEAD>
28555 <BODY>
28556 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28558 If this feature is set and there is sufficient space on the screen,
28559 a short indication of the current sort order will be
28560 added in the titlebar (the top line on the screen), before the name
28561 of the folder.
28562 For example, with the default Arrival sort in effect,
28563 the display would have the characters
28565 <P><CENTER>[A]</CENTER><P>
28567 added between the title of the screen and the folder name.
28568 The letters are the same as the letters you may type to manually
28569 sort a folder with the SortIndex command ($).
28570 The letters in the table below are the ones that may show
28571 up in the titlebar line.
28572 <P>
28573 <TABLE>
28574 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28575 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28576 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28577 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28578 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28579 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28580 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28581 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28582 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28583 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28584 </TABLE>
28585 <P>
28586 If the sort order is Reversed, the letter above will be preceded by the letter
28587 "R", for example
28589 <P><CENTER>[RS]</CENTER><P>
28591 means that a Reverse Subject sort is in effect.
28592 For the case where the sort is in Reverse Arrival order, the "A" is
28593 left out, and just an "R" is shown.
28595 <P><CENTER>[R]</CENTER>
28597 <P>
28598 <End of help on this topic>
28599 </BODY>
28600 </HTML>
28601 ====== h_config_disable_reset_disp =====
28602 <HTML>
28603 <HEAD>
28604 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28605 </HEAD>
28606 <BODY>
28607 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28609 UNIX Alpine only.
28610 <P>
28611 This feature affects Alpine's behavior when using
28612 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28613 Normally, before the display filter is run, the terminal mode is reset
28614 to what it was before you started Alpine.
28615 This may be necessary if the filter requires the use of the terminal.
28616 For example, it may need to interact with you.
28617 If you set this feature, then the terminal mode will not be reset.
28618 One thing that turning on this feature should fix is the coloring of
28619 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28620 breaks because the terminal reset resets the color state of the terminal.
28622 <P>
28623 <End of help on this topic>
28624 </BODY>
28625 </HTML>
28626 ====== h_config_disable_sender =====
28627 <HTML>
28628 <HEAD>
28629 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
28630 </HEAD>
28631 <BODY>
28632 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
28634 This feature affects Alpine's generation of the "Sender:" or
28635 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
28636 header fields.
28637 By default, Alpine will generate such a header in situations where the
28638 username or domain are not the same as
28639 the "From:" header on the message.
28640 With this feature set,
28641 no "Sender:" or "X-X-Sender" header will be generated.
28642 This may be desirable on a system that is virtually hosting many domains,
28643 and the sysadmin has other methods available for tracking a message to
28644 its originator.
28645 <P>
28646 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
28648 <P>
28649 <End of help on this topic>
28650 </BODY>
28651 </HTML>
28652 ====== h_config_use_sender_not_x =====
28653 <HTML>
28654 <HEAD>
28655 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
28656 </HEAD>
28657 <BODY>
28658 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
28660 Normally Alpine adds a header line
28661 labeled "X-X-Sender", if the sender is
28662 different from the From: line.
28663 The standard specifies that this header
28664 line should be labeled "Sender", not "X-X-Sender".
28665 Setting this feature causes
28666 "Sender" to be used instead of "X-X-Sender".
28667 <P>
28668 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
28670 <P>
28671 <End of help on this topic>
28672 </BODY>
28673 </HTML>
28674 ====== h_config_use_fk =====
28675 <HTML>
28676 <HEAD>
28677 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
28678 </HEAD>
28679 <BODY>
28680 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
28682 This feature specifies that Alpine will respond to function keys instead of
28683 the normal single-letter commands. In this mode, the key menus at the
28684 bottom of each screen will show function key designations instead of the
28685 normal mnemonic key.
28687 <P>
28688 <End of help on this topic>
28689 </BODY>
28690 </HTML>
28691 ====== h_config_cancel_confirm =====
28692 <HTML>
28693 <HEAD>
28694 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
28695 </HEAD>
28696 <BODY>
28697 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
28699 This feature affects what happens when you type ^C to cancel a composition.
28700 By default, if you attempt to cancel a composition by typing ^C, you will be
28701 asked to confirm the cancellation by typing a "C"
28702 for <EM>C</EM>onfirm.
28703 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
28704 risky because the "^C Y" needed to cancel a message
28705 is close (on the keyboard) to the "^X Y" needed to send a message.
28706 <P>
28707 If this feature is set the confirmation asked for
28708 will be a "<EM>Y</EM>es"
28709 instead of a "<EM>C</EM>onfirm" response.
28711 <P>
28712 <End of help on this topic>
28713 </BODY>
28714 </HTML>
28715 ====== h_config_compose_maps_del =====
28716 <HTML>
28717 <HEAD>
28718 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
28719 </HEAD>
28720 <BODY>
28721 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
28723 This feature affects the behavior of the DELETE key.
28724 If set, Delete will be equivalent to ^D, and delete
28725 the current character. Normally Alpine defines the Delete key
28726 to be equivalent to ^H, which deletes the <EM>previous</EM>
28727 character.
28729 <P>
28730 <End of help on this topic>
28731 </BODY>
28732 </HTML>
28733 ====== h_config_compose_bg_post =====
28734 <HTML>
28735 <HEAD>
28736 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
28737 </HEAD>
28738 <BODY>
28739 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
28741 This feature affects the behavior of Alpine's mail sending. If set, this
28742 feature enables a subcommand in the composer's "Send?" confirmation
28743 prompt. The subcommand allows you to tell Alpine to handle the actual
28744 posting in the background. While this feature usually allows posting
28745 to appear to happen very fast, it has no affect on the actual delivery
28746 time it takes a message to arrive at its destination.
28748 <P>
28749 Please Note:
28750 <OL>
28751 <LI>This feature will have no effect if the feature
28752 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
28753 is set.
28754 <LI>This feature isn't supported on all systems. All DOS and Windows,
28755 as well as several Unix ports, do not recognize this feature.
28756 <LI>Error handling is significantly different when this feature is
28757 enabled. Any message posting failure results in the message
28758 being appended to your "Interrupted" mail folder. When you
28759 type the <A HREF="h_common_compose">C</A>ompose command,
28760 Alpine will notice this folder and
28761 offer to extract any messages contained. Upon continuing a
28762 failed message, Alpine will display the nature of the failure
28763 in the status message line.
28764 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
28765 for message data to
28766 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
28767 if you typically run close to any sort of disk-space limits or quotas.
28768 </OL>
28769 <P>
28770 <End of help on this topic>
28771 </BODY>
28772 </HTML>
28773 ====== h_config_compose_dsn =====
28774 <HTML>
28775 <HEAD>
28776 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
28777 </HEAD>
28778 <BODY>
28779 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
28781 This feature affects the behavior of Alpine's mail sending. If set, this
28782 feature enables a subcommand in the composer's "Send?" confirmation
28783 prompt. The subcommand allows you to tell Alpine to request the type of
28784 Delivery Status Notification (DSN) that you would like. Most users will
28785 be happy with the default, and need not enable this feature.
28786 <P>
28787 If the feature
28788 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
28789 then this feature has no effect and the type of DSN is not selectable.
28791 <P>
28792 Turning on this feature and then turning on the DSNOpts from the send
28793 prompt reveals four on-off toggles at the bottom of the screen.
28794 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
28795 that no notification be returned to you, even if there is a delivery
28796 failure. The "D" key toggles between Delay and NoDelay. This tells the
28797 server that you are willing (or not) to receive delay notifications, which
28798 happen when there is an unusual delay at some mail server (in that mail
28799 server's opinion). The "S" key toggles between Success and NoSuccess.
28800 Success requests that you be sent a DSN message when the message is
28801 successfully delivered to the recipients mailbox. Setting NoErrRets will
28802 automatically turn off Delay and Success notification, and will flip the
28803 toggles to show that. Similarly, turning on Delay and/or Success will
28804 automatically toggle the "X" key to ErrRets. The fourth command, the
28805 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
28806 the full message be returned in any failed DSN. RetHdrs requests that
28807 only the headers be returned in any failed DSN. Notice that this command
28808 applies only to failed delivery status reports. For delay or success
28809 reports, the full message is never returned, only the headers are returned.
28811 <P>
28812 If you don't enable the DSN feature or if you don't turn it on for a
28813 particular message, the default is that you will be notified about failures,
28814 you might be notified about delays, and you won't be notified about
28815 successes. You will usually receive the full message back when there is
28816 a failure.
28818 <P>
28819 If you turn on the DSNOpts the default is to return as much information as
28820 possible to you. That is, by default, the Success and Delay options are
28821 turned on and the full message will be returned on failure.
28823 <P>
28824 The sending prompt will display the current DSN request (if any) in a
28825 shorthand form. It will be:
28827 <P><CENTER>[Never]</CENTER>
28829 <P>
28830 if you have requested NoErrRets. Otherwise, it will look something like:
28832 <P><CENTER>[FDS-Hdrs]</CENTER>
28834 <P>
28835 The "F" will always be there, indicating that you will be notified
28836 of failures. (Alpine doesn't provide a way to request no failure notification
28837 and at the same time request either success or delay notification. The only
28838 way to request no failure notifications is to request no notifications at
28839 all with NoErrRets.) The "D" and/or "S" will be present if you have
28840 requested Delay and/or Success notification. If one of those is missing,
28841 that means you are requesting no notification of the corresponding type.
28842 After the dash it will say either Hdrs or Full. Hdrs means to return only
28843 the headers and Full means to return the full message (applies to
28844 failure notifications only).
28846 <P>
28847 NOTE: This feature relies on your system's mail transport agent or
28848 configured
28849 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
28850 having the negotiation mechanism introduced in
28851 "Extended SMTP" (ESMTP) and the specific extension called
28852 "Delivery Status Notification" (DSN). If the mail tranport agent you
28853 are using doesn't support DSN, a short warning will be shown to you on
28854 the message line at the bottom of the screen after you send your message,
28855 but your message will have been sent anyway.
28857 <P>
28858 Note that DSNs don't provide a mechanism to request read receipts. That
28859 is, if you request notification on success you are notified when the
28860 message is delivered to the mailbox, not when the message is read.
28862 <P>
28863 ESMTP allows for graceful migration to upgraded mail transfer agents, but
28864 it is possible that this feature might cause problems for some servers.
28866 <P>
28867 <End of help on this topic>
28868 </BODY>
28869 </HTML>
28870 ====== h_config_auto_zoom =====
28871 <HTML>
28872 <HEAD>
28873 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
28874 </HEAD>
28875 <BODY>
28876 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
28878 This feature affects the behavior of the Select command.
28879 If set, the select command will automatically perform a zoom
28880 after the select is complete.
28881 This feature is set by default.
28882 <P>
28883 Some related help topics are
28884 <UL>
28885 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28886 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28887 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28888 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28889 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28890 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28891 </UL>
28893 <P>
28894 <End of help on this topic>
28895 </BODY>
28896 </HTML>
28897 ====== h_config_auto_unzoom =====
28898 <HTML>
28899 <HEAD>
28900 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
28901 </HEAD>
28902 <BODY>
28903 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
28905 This feature affects the behavior of the Apply command. If set, and if
28906 you are currently looking at a Zoomed Index view of selected messages,
28907 the Apply command will do the operation you specify, but then will
28908 implicitly do an "UnZoom", so that you will automatically be back in
28909 the normal Index view after the Apply.
28910 This feature is set by default.
28912 <P>
28913 Some related help topics are
28914 <UL>
28915 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28916 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28917 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28918 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
28919 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28920 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28921 </UL>
28922 <P>
28923 <End of help on this topic>
28924 </BODY>
28925 </HTML>
28926 ====== h_config_auto_unselect =====
28927 <HTML>
28928 <HEAD>
28929 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
28930 </HEAD>
28931 <BODY>
28932 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
28934 This feature affects the behavior of the Apply command. If set,
28935 the Apply command will do the operation you specify, but then will
28936 implicitly do an "UnSelect All", so that you will automatically be back in
28937 the normal Index view after the Apply.
28939 <P>
28940 Some related help topics are
28941 <UL>
28942 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
28943 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
28944 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
28945 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
28946 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
28947 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
28948 </UL>
28949 <P>
28950 <End of help on this topic>
28951 </BODY>
28952 </HTML>
28953 ====== h_config_fast_recent =====
28954 <HTML>
28955 <HEAD>
28956 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
28957 </HEAD>
28958 <BODY>
28959 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
28961 This feature controls the behavior of the TAB key when traversing folders
28962 in the optional
28963 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28964 collection or in optional <!--#echo var="VAR_news-collections"-->.
28966 <P>
28967 When the TAB
28968 (<A HREF="h_common_nextnew">NextNew</A>)
28969 key is pressed, the default behavior is to
28970 explicitly examine the status of the folder for the number of recent
28971 messages (messages delivered since the last time it was viewed).
28972 Depending on the size and number of messages in the folder, this test
28973 can be time consuming.
28975 <P>
28976 Enabling this feature will cause Alpine to only test for the existence of
28977 any recent messages rather than to obtain the count. This is much faster
28978 in many cases. The downside is that you're not given the number of recent
28979 messages when prompted to view the next folder.
28980 If the feature
28981 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
28982 is turned on, then the present feature will have no effect.
28984 <P>
28985 <UL>
28986 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28987 </UL><P>
28988 <End of help on this topic>
28989 </BODY>
28990 </HTML>
28991 ====== h_config_arrow_nav =====
28992 <HTML>
28993 <HEAD>
28994 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
28995 </HEAD>
28996 <BODY>
28997 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
28999 This feature controls the behavior of the left and right arrow keys.
29000 If set, the left and right arrow keys will operate like the usual
29001 navigation keys < and >.
29002 This feature is set by default.
29004 <P>
29005 If you set this feature, and do not like the changed behavior of the up/down
29006 arrow
29007 keys when navigating through the FOLDER LIST screen --
29008 <B>first</B> from column to column, if more than one folder is
29009 displayed per row,
29010 and <B>then</B> from row to row -- you may either also wish to set the feature
29011 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
29012 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
29013 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
29014 folders in each column.
29015 <P>
29016 <UL>
29017 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29018 </UL><P>
29019 <End of help on this topic>
29020 </BODY>
29021 </HTML>
29022 ====== h_config_relaxed_arrow_nav =====
29023 <HTML>
29024 <HEAD>
29025 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
29026 </HEAD>
29027 <BODY>
29028 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
29030 This feature controls the behavior of the left, right, up and down
29031 arrow keys in the FOLDER LIST screen when the "<A
29032 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
29033 set.
29034 This feature is set by default.
29036 <P>
29038 When this feature is set, the left and right
29039 arrow keys in the FOLDER LIST screen
29040 move the highlight bar to the left or right, and the up and
29041 down arrows move it up or down.
29043 <P>
29044 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
29045 feature is not set;
29046 the left and right arrow keys in the Folder List screen strictly
29047 track the commands bound to the '<' and '>' keys, and the up
29048 and down arrow keys move the highlight bar to the previous and next
29049 folder or directory name.
29051 <P>
29052 <UL>
29053 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29054 </UL><P>
29055 <End of help on this topic>
29056 </BODY>
29057 </HTML>
29058 ====== h_config_alt_compose_menu =====
29059 <HTML>
29060 <HEAD>
29061 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
29062 </HEAD>
29063 <BODY>
29064 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
29066 This feature controls the menu that is displayed when Compose is selected.
29067 If set, a list of options will be presented, with each option representing
29068 the type of composition that could be used. This feature is most useful for
29069 users who want to avoid being prompted with each option separately, or who
29070 want to avoid the checking of remote postponed or form letter folders.
29071 The possible types of composition are:
29073 <P>
29074 New, for starting a new composition. Note that if New is selected and roles
29075 are set, roles are checked for matches and applied according to the setting
29076 of the matching role.
29078 <P>
29079 Interrupted, for continuing an interrupted composition. This option is only
29080 offered if an interrupted message folder is detected.
29082 <P>
29083 Postponed, for continuing postponed compositions. This option is offered
29084 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
29085 the postponed folder actually exists. This option is especially handy
29086 for avoiding having to check for the existence of a remote postponed folder.
29088 <P>
29089 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
29090 is set in the config, and is not checked for existence for reasons similar
29091 to those explained by the postponed option.
29093 <P>
29094 setRole, for selecting a role to apply to a composition.
29096 <P>
29097 <End of help on this topic>
29098 </BODY>
29099 </HTML>
29100 ====== h_config_alt_role_menu =====
29101 <HTML>
29102 <HEAD>
29103 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
29104 </HEAD>
29105 <BODY>
29106 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
29108 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
29109 a role and compose a new message using that role.
29110 When this feature is set, the role command will first ask whether you want to
29111 Compose a new message, Forward the current message, Reply to the
29112 current message, or Bounce the current message.
29113 If you are not in the MESSAGE INDEX and are not viewing a message,
29114 then there is no current message and the question will be skipped.
29115 After you have chosen to Compose, Forward, Reply, or Bounce you will
29116 then choose the role to be used.
29117 <P>
29118 When Bouncing the "Set From" address is used for the
29119 Resent-From header, the "Set Fcc" value is used for the Fcc
29120 provided that the option
29121 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
29122 and the "Use SMTP Server" value is used for the SMTP server, if
29123 set.
29124 Other actions of the role are ignored when Bouncing.
29126 <P>
29127 <End of help on this topic>
29128 </BODY>
29129 </HTML>
29130 ====== h_config_always_spell_check =====
29131 <HTML>
29132 <HEAD>
29133 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
29134 </HEAD>
29135 <BODY>
29136 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
29137 <P>
29138 When this feature is set, every composed message will be spell-checked before
29139 being sent.
29140 <P>
29141 <End of help on this topic>
29142 </BODY>
29143 </HTML>
29144 ====== h_config_quell_asterisks =====
29145 <HTML>
29146 <HEAD>
29147 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
29148 </HEAD>
29149 <BODY>
29150 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
29151 <P>
29152 When you are running Alpine you will sometimes be asked for a password
29153 in a prompt on the third line from the bottom of the screen.
29154 Normally each password character you type will cause an asterisk to echo
29155 on the screen. That gives you some feedback to know that your typing is
29156 being recognized.
29157 There is a very slight security risk in doing it this way because someone
29158 watching over your shoulder might be able to see how many characters there
29159 are in your password.
29160 If you'd like to suppress the echoing of the asterisks set this feature.
29161 <P>
29162 <End of help on this topic>
29163 </BODY>
29164 </HTML>
29165 ====== h_config_quell_flowed_text =====
29166 <HTML>
29167 <HEAD>
29168 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
29169 </HEAD>
29170 <BODY>
29171 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
29172 <P>
29173 Alpine generates flowed text where possible.
29174 The method for generating flowed text is defined by
29175 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
29176 the benefit of doing so is
29177 to send message text that can properly be viewed both on normal width displays
29178 and on displays with smaller or larger than normal screen widths.
29179 With flowed text, a space at the end of a line tells the receiving mail
29180 client that the following line belongs to the same paragraph.
29181 Quoted text will also be affected, with only the innermost
29182 level of ">" quoting being followed by a space.
29183 However, if you have changed the
29184 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29185 so that it is not equal to the default value of "> ", then
29186 quoted text will not be flowed.
29187 For this reason, we recommend that you leave your
29188 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
29189 <P>
29190 This feature turns off the generation of flowed text, as it might be
29191 desired to more tightly control how a message is displayed on the receiving end.
29192 <P>
29193 If this feature is <EM>not</EM> set, you can control on a message by message
29194 basis whether or not flowed text is generated.
29195 You do this by typing ^V at the Send confirmation prompt that you get
29196 after typing ^X to send a message.
29197 ^V is a toggle that turns flowing off and back on if typed again.
29198 If for some reason flowing cannot be done on a particular message, then the
29199 ^V command will not be available.
29200 This would be the case, for example, if this feature was set, or if your
29201 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
29202 If the feature
29203 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29204 then the opportunity to control on a message by message basis
29205 whether or not flowed text is generated is lost.
29206 <P>
29207 When this feature is not set and you have typed ^V to turn off flowing,
29208 the Send confirmation prompt will change to look like
29209 <P>
29210 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
29211 <P>
29212 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
29213 also turn off the sending of flowed text messages, but it differs in that
29214 it also trims all trailing white space from a message before sending it.
29215 <P>
29216 If alternate editors are used extensively, be aware that a message will still
29217 be sent flowed if this feature is unset. In most cases this will be fine,
29218 but if the editor has a "flowed text" mode, it would be best to
29219 use that.
29220 <P>
29221 <End of help on this topic>
29222 </BODY>
29223 </HTML>
29224 ====== h_config_strip_ws_before_send =====
29225 <HTML>
29226 <HEAD>
29227 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
29228 </HEAD>
29229 <BODY>
29230 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
29231 <P>
29232 By default, trailing whitespace is not stripped from
29233 a message before sending. Trailing whitespace should have no effect on an
29234 email message, and in flowed text can aid in delimiting paragraphs.
29235 However, the old behavior of stripping trailing whitespace was in place
29236 to better deal with older clients that couldn't handle certain types of
29237 text encodings. This feature restores the old behavior
29238 <P>
29239 Trailing whitespace is of aid to flowed-text-formatted messages, which are
29240 generated by default but can be turned off via the
29241 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
29242 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
29243 of flowed text.
29244 <P>
29245 <End of help on this topic>
29246 </BODY>
29247 </HTML>
29248 ====== h_config_del_from_dot =====
29249 <HTML>
29250 <HEAD>
29251 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
29252 </HEAD>
29253 <BODY>
29254 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
29256 This feature controls the behavior of the Ctrl-K command in the composer.
29257 If set, ^K will cut from the current cursor position to the end of the line,
29258 rather than cutting the entire line.
29260 <P>
29261 <End of help on this topic>
29262 </BODY>
29263 </HTML>
29264 ====== h_config_print_index =====
29265 <HTML>
29266 <HEAD>
29267 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
29268 </HEAD>
29269 <BODY>
29270 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
29272 This feature controls the behavior of the Print command when in the
29273 MESSAGE INDEX screen. If set, the print command will give you a prompt
29274 asking if you wish to print the message index, or the currently highlighted
29275 message. If not set, the message will be printed.
29277 <P>
29278 <End of help on this topic>
29279 </BODY>
29280 </HTML>
29281 ====== h_config_allow_talk =====
29282 <HTML>
29283 <HEAD>
29284 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
29285 </HEAD>
29286 <BODY>
29287 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
29289 UNIX Alpine only.
29290 <P>
29291 By default, permission for others to "talk" to your terminal is turned
29292 off when you are running Alpine. When this feature is set, permission is
29293 instead turned on. If enabled, you may see unexpected messages in the
29294 middle of your Alpine screen from someone attempting to contact you via the
29295 "talk" program.
29297 <P>
29298 NOTE: The "talk" program has nothing to do with Alpine or email. The
29299 talk daemon on your system will attempt to print a message on your screen
29300 when someone else is trying to contact you. If you wish to see these
29301 messages while you are running Alpine, you should enable this feature.
29303 <P>
29304 If you do enable this feature and see a "talk" message, you must
29305 suspend or quit Alpine before you can respond.
29307 <P>
29308 <End of help on this topic>
29309 </BODY>
29310 </HTML>
29311 ====== h_config_send_filter_dflt =====
29312 <HTML>
29313 <HEAD>
29314 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
29315 </HEAD>
29316 <BODY>
29317 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
29318 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
29319 configured, setting this feature will cause
29320 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
29321 instead of unfiltered, the usual default.
29322 <P>
29323 <UL>
29324 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29325 </UL><P>
29326 <End of help on this topic>
29327 </BODY>
29328 </HTML>
29329 ====== h_config_custom_print =====
29330 <HTML>
29331 <HEAD>
29332 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
29333 </HEAD>
29334 <BODY>
29335 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
29337 When this feature is set, the print command will have an additional
29338 subcommand called "C CustomPrint". If selected, you will have
29339 the opportunity to enter any system print command --instead of being
29340 restricted to using those that have been previously configured in the
29341 printer setup menu.
29342 <P>
29344 <End of help on this topic>
29345 </BODY>
29346 </HTML>
29347 ====== h_config_enable_dot_files =====
29348 <HTML>
29349 <HEAD>
29350 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
29351 </HEAD>
29352 <BODY>
29353 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
29355 When this feature is set, files beginning with dot (".") will be
29356 visible in the file browser. For example, you'll be able to select them
29357 when using the browser to add an attachment to a message.
29358 <P>
29359 <End of help on this topic>
29360 </BODY>
29361 </HTML>
29362 ====== h_config_enable_dot_folders =====
29363 <HTML>
29364 <HEAD>
29365 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
29366 </HEAD>
29367 <BODY>
29368 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
29370 When this feature is set, folders beginning with dot (".") may be added
29371 and viewed.
29372 <P>
29373 <End of help on this topic>
29374 </BODY>
29375 </HTML>
29376 ====== h_config_ff_between_msgs =====
29377 <HTML>
29378 <HEAD>
29379 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
29380 </HEAD>
29381 <BODY>
29382 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
29384 Setting this feature causes a formfeed to be printed between messages when
29385 printing multiple messages (with Apply Print command).
29386 <P>
29387 <End of help on this topic>
29388 </BODY>
29389 </HTML>
29390 ====== h_config_blank_keymenu =====
29391 <HTML>
29392 <HEAD>
29393 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
29394 </HEAD>
29395 <BODY>
29396 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
29398 If this feature is set the command key menu that normally appears on the
29399 bottom two lines of the screen will not usually be there. Asking for
29400 help with ^G or ? will cause the key menu to appear instead of causing
29401 the help message to come up. If you want to actually see the help text,
29402 another ^G or ? will show it to you. After the key menu has popped
29403 up with the help key it will remain there for an O for Other command but
29404 disappear if any other command is typed.
29405 <P>
29406 <End of help on this topic>
29407 </BODY>
29408 </HTML>
29409 ====== h_config_enable_mouse =====
29410 <HTML>
29411 <HEAD>
29412 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29413 </HEAD>
29414 <BODY>
29415 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29417 This feature controls whether or not an X terminal mouse can be used with
29418 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29419 being used, the left mouse button on the mouse can be used to select text
29420 or commands.
29421 Clicking on a command at the bottom of the screen will behave as if you had
29422 typed that command.
29423 Clicking on an index line will move the current message highlight to
29424 that line.
29425 Double-clicking on an index line will view the message.
29426 Double-clicking on a link will view the link.
29427 <P>
29428 This type of mouse support will also work in some terminal emulators which are
29429 not actually X terminals, but which have extra code to support the xterm
29430 style mouse.
29431 For those emulators you not only need to turn this feature on but you also
29432 have to set the $DISPLAY environment variable even though it isn't needed
29433 for your terminal.
29434 That will cause Alpine to think that it is an xterm and to properly interpret the
29435 escape sequences sent by the mouse.
29436 <P>
29437 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29438 also modified. It is sometimes possible to hold the shift key down while clicking
29439 left or middle mouse buttons for the normal xterm cut/paste operations.
29440 There is also an Alpine command to toggle this mode on or off.
29441 The command is Ctrl-\ (Control-backslash).
29442 <P>
29443 <End of help on this topic>
29444 </BODY>
29445 </HTML>
29446 ====== h_config_enable_xterm_newmail =====
29447 <HTML>
29448 <HEAD>
29449 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29450 </HEAD>
29451 <BODY>
29452 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29454 This feature controls whether or not Alpine will attempt to announce new
29455 mail arrival when it is running in an X terminal window and that window
29456 is iconified. If set, and the $DISPLAY variable indicates that an X
29457 terminal is being used, Alpine will send appropriate escape sequences to
29458 the X terminal to modify the label on Alpine's icon to indicate that new
29459 mail has arrived. Alpine will also modify the Alpine window's title to
29460 indicate new mail.
29461 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29462 <P>
29463 <End of help on this topic>
29464 </BODY></HTML>
29465 ====== h_config_enable_newmail_short_text =====
29466 <HTML>
29467 <HEAD>
29468 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29469 </HEAD>
29470 <BODY>
29471 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29473 This feature controls the text to be displayed in an icon in the event
29474 of a new message arrival. Normally, the message will
29475 be the one that is displayed on the screen. This feature shortens the
29476 message to a count of the number of new messages in brackets. This may be
29477 more useful for those who use the window's title bar in the task bar as a
29478 new mail indicator. This feature is only useful if the
29479 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29480 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29481 feature, this feature is only relevant when run in an xterm environment.
29482 <P>
29483 <End of help on this topic>
29484 </BODY></HTML>
29485 ====== h_config_copy_to_to_from =====
29486 <HTML>
29487 <HEAD>
29488 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29489 </HEAD>
29490 <BODY>
29491 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29493 This feature affects the From address used when Replying to a message.
29494 It is probably only useful if you have some
29495 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29496 defined.
29497 When enabled, it checks to see if any of the addresses in the To or Cc
29498 fields of the message you are replying to is one of your addresses.
29499 If it is, and there is only one of them, then that address is used as
29500 the From address in the message you are composing.
29501 In other words, you will be using a From address that is the same
29502 as the To address that was used to get the mail to you in the first place.
29504 <P>
29505 If a role is being used and it has a From address defined, that From address will
29506 be used rather than the one derived from this feature.
29508 <P>
29509 <UL>
29510 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29511 </UL><P>
29512 <End of help on this topic>
29513 </BODY>
29514 </HTML>
29515 ====== h_config_prefix_editing =====
29516 <HTML>
29517 <HEAD>
29518 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29519 </HEAD>
29520 <BODY>
29521 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29523 This feature affects the Reply command's "Include original message
29524 in Reply?" prompt. When enabled, it causes the
29525 "Edit Indent String" sub-command to appear which allows
29526 you to edit the string Alpine would otherwise use to denote included
29527 text from the message being replied to.<P>
29529 Thus, you can change Alpine's default message quote character (usually
29530 an angle bracket) on a per message basis. So you could change your quoted message to
29531 look, for example, like this:<p>
29533 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29535 John: I just wanted to say hello and to congratulate you
29536 John: on a job well done!</pre><p>
29538 The configuration option
29539 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29540 may be used to change what appears as the default string to be edited.
29541 <P>
29542 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29543 currently being replied to.
29544 <P>
29545 If you change your <!--#echo var="VAR_reply-indent-string"-->
29546 so that it is not equal to the default value of "> ", then
29547 quoted text will not be flowed
29548 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29549 when you reply.
29550 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
29551 set to the default value.
29552 <P>
29553 <UL>
29554 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29555 </UL><P>
29556 <End of help on this topic>
29557 </BODY>
29558 </HTML>
29559 ====== h_config_enable_search_and_repl =====
29560 <HTML>
29561 <HEAD>
29562 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
29563 </HEAD>
29564 <BODY>
29565 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
29567 This feature modifies the behavior of Alpine's composer. Setting this
29568 feature causes Alpine to offer the "^R Replace" subcommand, which
29569 allows you to search and replace text strings in a message you are composing,
29570 inside the "^W Where is" command.
29572 <P>
29574 To search and replace text, first enter the text to be replaced at the
29575 "Search: " prompt. Then, rather than pressing Enter to just search for that
29576 text, press ^R, which turns the prompt into
29578 <P>
29580 Search (to replace):
29582 <P>
29584 and then press Enter. The cursor will highlight the first occurrence
29585 of the text string you entered, and the prompt will show:
29587 <P>
29589 Replace "<your text string>" with :
29591 <P>
29593 where <your text string> is what you entered at the previous prompt;
29594 here, enter the replacement text. To only replace the highlighted
29595 occurrence, simply press Enter now; to replace all occurrences in the
29596 message, press ^X (Repl All), then Enter. You will then be asked to confirm
29597 each replacement.
29599 <P>
29601 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
29602 ^X toggles between "Replace All" and "Replace One."
29604 <P>
29606 If you previously searched for text in a message, it will be offered for
29607 re-use as part of the prompt, shown in [ ] brackets.
29609 <P>
29610 <End of help on this topic>
29611 </BODY>
29612 </HTML>
29613 ====== h_config_enable_view_attach =====
29614 <HTML>
29615 <HEAD>
29616 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
29617 </HEAD>
29618 <BODY>
29619 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
29621 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29622 Setting this feature causes Alpine to present attachments in boldface.
29623 The first available attachment is displayed in inverse. This is the
29624 "selected" attachment. Pressing RETURN will cause Alpine to display
29625 the selected attachment. Use the arrow keys to change which of the
29626 attachments displayed in boldface is the current selection.
29628 <P>
29630 Speaking of arrow keys, the Up and Down Arrows will select the next
29631 and previous attachments if one is available on the screen for selection.
29632 Otherwise, they will simply adjust the viewed text one line up or down.
29634 <P>
29636 Similarly, when selectable items are present in a message, the Ctrl-F key
29637 can be used to select the next item in the message independent of which
29638 portion of the viewed message is currently displayed. The Ctrl-B key can
29639 be used to select the previous item in the same way.
29640 <P>
29641 <End of help on this topic>
29642 </BODY>
29643 </HTML>
29644 ====== h_config_enable_y_print =====
29645 <HTML>
29646 <HEAD>
29647 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
29648 </HEAD>
29649 <BODY>
29650 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
29652 This feature modifies the behavior of Alpine's Print command.
29653 <P>
29654 By default, Alpine's print command is available by pressing the "%" key.
29655 (This command is a substantial change from Pine versions before 4.00 --
29656 where the print command was "Y" -- based on numerous complaints about
29657 printing being invoked inadvertently, since Y also means "Yes.")
29659 <P>
29661 This feature is supplied to mitigate any disruption or anxiety users
29662 might feel as a result of this change.
29664 <P>
29666 Enabling this feature will cause Alpine to recognize both the old
29667 command, "Y" for Prynt, as well the new "%" method for invoking
29668 printing. Note, key menu labels are not changed as a result of
29669 enabling this feature.
29671 <P>
29673 <End of help on this topic>
29674 </BODY>
29675 </HTML>
29676 ====== h_config_enable_lessthan_exit =====
29677 <HTML>
29678 <HEAD>
29679 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
29680 </HEAD>
29681 <BODY>
29682 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
29684 If this feature is set, then on screens where there is an Exit command
29685 but no < command, the < key will perform the same function as the Exit
29686 command.
29687 This feature is set by default.
29688 <P>
29689 <End of help on this topic>
29690 </BODY>
29691 </HTML>
29692 ====== h_config_enable_view_url =====
29693 <HTML>
29694 <HEAD>
29695 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
29696 </HEAD>
29697 <BODY>
29698 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
29699 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29700 When this feature is set (the default) Alpine will select possible URLs from the
29701 displayed text and display them in boldface for selection.
29702 <P>
29703 The first available URL is displayed in inverse. This is the
29704 "selected" URL. Pressing RETURN will cause Alpine to display
29705 the selected URL via either built-in means as with mailto:, imap:,
29706 news:, and nntp:, or via an external application as defined
29707 by the <A HREF="h_config_browser">"url-viewer"</A>
29708 variable.
29709 <P>
29710 Use the arrow keys to change which of the URLs displayed in boldface
29711 is the current selection.
29712 <P>
29713 Speaking of arrow keys, the Up and Down Arrows will select the next
29714 and previous URL if one is available on the screen for selection (unless
29715 you have set the feature
29716 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
29717 Otherwise, they will simply adjust the viewed text one line up or down.
29718 <P>
29719 Similarly, when selectable items are present in a message, the Ctrl-F
29720 key can be used to select the next item in the message independent
29721 of which portion of the viewed message is currently displayed. The
29722 Ctrl-B key can be used to select the previous item in the same way.
29723 <P>
29724 <UL>
29725 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29726 </UL><P>
29727 <End of help on this topic>
29728 </BODY>
29729 </HTML>
29730 ====== h_config_enable_view_web_host =====
29731 <HTML>
29732 <HEAD>
29733 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
29734 </HEAD>
29735 <BODY>
29736 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
29738 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29739 When this feature is set (the default) Alpine will select possible web hostnames
29740 from the displayed text and display them in boldface for selection.
29741 This can be useful when you receive messages referencing World Wide Web
29742 sites without the use of complete URLs; for example, specifying only
29743 "www.patches.freeiz.com/alpine/" (which will <B>not</B> become a
29744 selectable
29745 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
29746 rather than explicitly
29747 "http://www.patches.freeiz.com/alpine/".
29748 <P>
29749 The first available hostname is displayed in inverse. This is the
29750 "selected" hostname. Pressing RETURN will cause Alpine to display
29751 the selected hostname via an external application as defined
29752 by the <A HREF="h_config_browser">"url-viewer"</A>
29753 variable.
29754 <P>
29755 Use the arrow keys (unless you have set the feature
29756 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29757 to change which of the hostnames displayed in
29758 boldface is the current selection.
29759 <P>
29760 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29761 key can be used to select the next web hostname in the message independent
29762 of which portion of the viewed message is currently displayed. The
29763 Ctrl-B key can be used to select the previous web hostnames in the same way.
29764 <P>
29765 <UL>
29766 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29767 </UL><P>
29768 <End of help on this topic>
29769 </BODY>
29770 </HTML>
29771 ====== h_config_enable_view_addresses =====
29772 <HTML>
29773 <HEAD>
29774 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
29775 </HEAD>
29776 <BODY>
29777 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
29779 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
29780 Setting this feature causes Alpine to select possible email addresses
29781 from the displayed text and display them in boldface for selection.
29783 <P>
29784 The first available email address is displayed in inverse. This is the
29785 "selected" address. Pressing RETURN will cause Alpine to enter
29786 the message composition screen with the To: field filled in with the
29787 selected address.
29788 <P>
29789 Use the arrow keys (unless you have set the feature
29790 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
29791 to change which of the hostnames displayed in
29792 boldface is the current selection.
29793 <P>
29794 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
29795 key can be used to select the next web hostname in the message independent
29796 of which portion of the viewed message is currently displayed. The
29797 Ctrl-B key can be used to select the previous web hostnames in the same way.
29798 <P>
29799 <UL>
29800 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29801 </UL><P>
29802 <End of help on this topic>
29803 </BODY>
29804 </HTML>
29805 ====== h_config_enable_view_arrows =====
29806 <HTML>
29807 <HEAD>
29808 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
29809 </HEAD>
29810 <BODY>
29811 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
29813 This feature modifies Up and Down arrow key behavior in Alpine's
29814 MESSAGE TEXT screen when selectable Attachments, URL's, or
29815 web-hostnames are presented. Alpine's usual behavior is to move to
29816 the next or previous selectable item if currently displayed or
29817 simply to adjust the screen view by one line.
29819 <P>
29821 Setting this feature causes the UP and Down arrow key to behave as
29822 if no selectable items were present in the message.
29824 <P>
29826 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
29827 item) functionality is unchanged.
29828 <P>
29830 <End of help on this topic>
29831 </BODY>
29832 <HTML>
29833 ====== h_config_quell_charset_warning =====
29834 <HTML>
29835 <HEAD>
29836 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
29837 </HEAD>
29838 <BODY>
29839 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
29841 By default, if the message you are viewing contains characters that are
29842 not representable in your
29843 <A HREF="h_config_char_set">"Display Character Set"</A>
29844 then Alpine will
29845 add a warning to the start of the displayed text.
29846 If this option is set, then that editorial message will be suppressed.
29847 <P>
29848 Setting this feature also suppresses the comment about the character set
29849 in header lines.
29850 For example, when viewing a message you might see
29851 <P>
29852 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
29853 <P>
29854 in the From header if your Character-Set is something other than ISO-8859-2.
29855 If you set this feature, the comment about the character set will
29856 no longer be there.
29857 <P>
29858 <End of help on this topic>
29859 </BODY>
29860 </HTML>
29861 ====== h_config_quell_host_after_url =====
29862 <HTML>
29863 <HEAD>
29864 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
29865 </HEAD>
29866 <BODY>
29867 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
29869 By default, links in HTML text are displayed with the host the link
29870 references appended, within square brackets, to the link text. Alpine
29871 does this to help indicate where a link will take you, particularly when
29872 the link text might suggest a different destination.
29874 <P>
29875 Setting this feature will prevent the server name from being appended
29876 to the displayed text.
29878 <P>
29879 <End of help on this topic>
29880 </BODY>
29881 </HTML>
29882 ====== h_config_prefer_plain_text =====
29883 <HTML>
29884 <HEAD>
29885 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
29886 </HEAD>
29887 <BODY>
29888 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
29890 A message being viewed may contain alternate versions of the same content.
29891 Those alternate versions are supposed to be ordered by the sending software such that the
29892 first alternative is the least preferred and the last alternative is the
29893 most preferred. Alpine will normally display the most-preferred version that
29894 it knows how to display. This is most often encountered where the two
29895 alternate versions are a plain text version and an HTML version, with the
29896 HTML version listed last as the most preferred.
29897 <P>
29898 If this option is set, then any plain text version will be preferred to
29899 all other versions.
29900 <P>
29901 When viewing a message there is a command "A TogglePreferPlain",
29902 which will temporarily change the sense of this option.
29903 If this option is set you will first see the plain text version of a
29904 message.
29905 If you then type the "A" command, you will see the most preferred version,
29906 most likely HTML, instead.
29907 Typing the "A" command a second time will switch it back.
29908 Alternatively, if the present option is not set you will originally see
29909 the most preferred version of the message and typing "A" will switch to
29910 the plain text version.
29911 <P>
29912 <End of help on this topic>
29913 </BODY>
29914 </HTML>
29915 ====== h_config_pass_control =====
29916 <HTML>
29917 <HEAD>
29918 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
29919 </HEAD>
29920 <BODY>
29921 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
29923 It is probably not useful to set this option.
29924 This is a legacy option left behind "just in case".
29925 Multi-byte characters that have an octet that has the same
29926 value as a control character are permitted through whether or not
29927 this option is turned on.
29928 <P>
29929 This feature controls how certain characters contained in messages are
29930 displayed.
29931 If set, all characters in a message will be sent to the
29932 screen. Normally, control characters are displayed as shown below to
29933 avoid a garbled screen and to
29934 avoid inadvertently changing terminal setup parameters.
29935 Control characters are usually displayed as two character sequences like
29936 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
29937 for Control-C,
29938 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
29939 for ESCAPE,
29940 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
29941 for DELETE, and
29942 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
29943 for the character with value 133 (0x85).
29944 (The DEL character is displayed as ^?, regular control characters are displayed
29945 as the character ^ followed by the character obtained by adding the
29946 five low-order bits of the character to 0x40, and the C1
29947 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
29948 character obtained by adding the
29949 five low-order bits of the character to 0x40.)
29950 Sometimes, in cases where changing a single control character into a
29951 two-character sequence would confuse Alpine's display routines,
29952 a question mark is substituted for the control character.
29953 <P>
29954 If you wish to filter out regular control characters but pass the
29955 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29956 you may leave this feature unset and set the feature <A HREF="h_config_pass_c1_control"><!--#echo var="FEAT_pass-c1-control-characters-as-is"--></A> instead.
29957 <P>
29958 <End of help on this topic>
29959 </BODY>
29960 </HTML>
29961 ====== h_config_pass_c1_control =====
29962 <HTML>
29963 <HEAD>
29964 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
29965 </HEAD>
29966 <BODY>
29967 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
29969 It is probably not useful to set this option.
29970 This is a legacy option left behind "just in case".
29971 Multi-byte characters that have an octet that has the same
29972 value as a control character are permitted through whether or not
29973 this option is turned on.
29974 <P>
29975 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29976 is set, then this feature has no effect.
29977 However, if you wish to filter out regular control characters but pass the
29978 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
29979 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
29980 unset and set this feature.
29981 <P>
29982 <End of help on this topic>
29983 </BODY>
29984 </HTML>
29985 ====== h_config_fcc_on_bounce =====
29986 <HTML>
29987 <HEAD>
29988 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
29989 </HEAD>
29990 <BODY>
29991 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
29993 This feature controls an aspect of Alpine's behavior when bouncing a
29994 message. If set, normal FCC ("File Carbon Copy") processing will be
29995 done, just as if you had composed a message to the address you are
29996 bouncing to. If not set, no FCC of the message will be saved.
29997 <P>
29998 <End of help on this topic>
29999 </BODY>
30000 </HTML>
30001 ====== h_config_show_cursor =====
30002 <HTML>
30003 <HEAD>
30004 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
30005 </HEAD>
30006 <BODY>
30007 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
30009 This feature controls an aspect of Alpine's displays. If set, the system
30010 cursor will move to convenient locations in the displays. For example,
30011 to the beginning of the status field of the highlighted index line, or
30012 to the highlighted word after a successful WhereIs command. It is intended
30013 to draw your attention to an "interesting" spot on the screen.
30014 <P>
30015 <End of help on this topic>
30016 </BODY>
30017 </HTML>
30018 ====== h_config_sort_fcc_alpha =====
30019 <HTML>
30020 <HEAD>
30021 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
30022 </HEAD>
30023 <BODY>
30024 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
30026 This feature controls an aspect of Alpine's FOLDER LIST screen.
30027 If set, the default Fcc folder will be sorted alphabetically with the other
30028 folders instead of appearing right after the INBOX.
30029 <P>
30030 <End of help on this topic>
30031 </BODY>
30032 </HTML>
30033 ====== h_config_sort_save_alpha =====
30034 <HTML>
30035 <HEAD>
30036 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
30037 </HEAD>
30038 <BODY>
30039 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
30041 This feature controls an aspect of Alpine's FOLDER LIST screen.
30042 If set, the default save folder will be sorted alphabetically with the other
30043 folders instead of appearing right after the INBOX (and default FCC folder).
30044 <P>
30045 <End of help on this topic>
30046 </BODY>
30047 </HTML>
30048 ====== h_config_single_list =====
30049 <HTML>
30050 <HEAD>
30051 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
30052 </HEAD>
30053 <BODY>
30054 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
30056 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30057 the folders will be listed one per line instead of several per line
30058 in the FOLDER LIST display.
30059 <P>
30060 <End of help on this topic>
30061 </BODY>
30062 </HTML>
30063 ====== h_config_vertical_list =====
30064 <HTML>
30065 <HEAD>
30066 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
30067 </HEAD>
30068 <BODY>
30069 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
30071 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30072 the folders will be listed alphabetically down the columns rather
30073 than across the columns as is the default.
30074 <P>
30075 <End of help on this topic>
30076 </BODY>
30077 </HTML>
30078 ====== h_config_verbose_post =====
30079 <HTML>
30080 <HEAD>
30081 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
30082 </HEAD>
30083 <BODY>
30084 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
30085 This feature controls an aspect of Alpine's message sending. When enabled,
30086 Alpine will send a VERB (i.e., VERBose) command early in the posting process
30087 intended to cause the SMTP server to provide a more detailed account of
30088 the transaction. This feature is typically only useful to system
30089 administrators and other support personel as an aid in troublshooting
30090 problems.
30091 <P>
30092 Note, this feature relies on a specific capability of the system's mail
30093 transport agent or configured
30094 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
30095 It is possible that this
30096 feature will cause problems for some tranport agents, and may result in
30097 sending failure. In addition, as the verbose output comes from the mail
30098 transport agent, it is likely to vary from one system to another.
30099 <P><UL>
30100 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30101 </UL><P>
30102 <End of help on this topic>
30103 </BODY>
30104 </HTML>
30105 ====== h_config_auto_reply_to =====
30106 <HTML>
30107 <HEAD>
30108 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
30109 </HEAD>
30110 <BODY>
30111 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
30113 This feature controls an aspect of Alpine's Reply command. If set, Alpine
30114 will not prompt when a message being replied to contains a "Reply-To:"
30115 header value, but will simply use its value (as opposed to using the
30116 "From:" field's value).
30118 <P>
30120 Note: Using the "Reply-To:" address is usually the preferred behavior,
30121 however, some mailing list managers choose to place the list's address in
30122 the "Reply-To:" field of any message sent out to the list. In such
30123 cases, this feature makes it all too easy for personal replies to be
30124 inadvertently sent to the entire mail list, so be careful!
30125 <P>
30126 <End of help on this topic>
30127 </BODY>
30128 </HTML>
30129 ====== h_config_del_skips_del =====
30130 <HTML>
30131 <HEAD>
30132 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
30133 </HEAD>
30134 <BODY>
30135 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
30137 This feature controls an aspect of Alpine's Delete command. If set, this
30138 feature will cause the Delete command to advance past following messages that
30139 are marked deleted. In other words, pressing "D" will both mark the
30140 current message deleted and advance to the next message that is not marked
30141 deleted.
30142 This feature is set by default.
30143 <P>
30144 <End of help on this topic>
30145 </BODY></HTML>
30146 ====== h_config_expunge_manually =====
30147 <HTML>
30148 <HEAD>
30149 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
30150 </HEAD>
30151 <BODY>
30152 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
30154 Normally, when you close a folder that contains deleted messages you are
30155 asked if you want to expunge those messages from the folder permanently.
30156 If this feature is set, you won't be asked and the deleted messages will
30157 remain in the folder.
30158 If you choose to set this feature you will have to expunge the
30159 messages manually using the eXpunge command, which you can use while
30160 in the MESSAGE INDEX screen.
30161 If you do not expunge deleted messages the size of your
30162 folder will continue to increase until you are out of disk space.
30163 <P>
30164 <UL>
30165 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30166 </UL><P>
30167 <End of help on this topic>
30168 </BODY>
30169 </HTML>
30170 ====== h_config_auto_expunge =====
30171 <HTML>
30172 <HEAD>
30173 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
30174 </HEAD>
30175 <BODY>
30176 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
30178 This features controls an aspect of Alpine's eXpunge command. If set, you
30179 will <B>not</B> be prompted to confirm your intent before the expunge takes
30180 place.
30181 Actually, this is only true for the INBOX folder and for folders in the
30182 Incoming Folders collection. See the feature
30183 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
30184 <P>
30185 <UL>
30186 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30187 </UL><P>
30188 <End of help on this topic>
30189 </BODY>
30190 </HTML>
30191 ====== h_config_full_auto_expunge =====
30192 <HTML>
30193 <HEAD>
30194 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
30195 </HEAD>
30196 <BODY>
30197 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
30199 This features controls an aspect of Alpine's eXpunge command. If set, you
30200 will <B>not</B> be prompted to confirm your intent before the expunge
30201 takes place. This feature sets this behavior for all folders, unlike the
30202 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
30203 feature that works only for incoming folders.
30204 <P>
30205 <UL>
30206 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30207 </UL><P>
30208 <End of help on this topic>
30209 </BODY>
30210 </HTML>
30211 ====== h_config_auto_read_msgs =====
30212 <HTML>
30213 <HEAD>
30214 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
30215 </HEAD>
30216 <BODY>
30217 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
30218 This feature controls an aspect of Alpine's behavior upon quitting. If set,
30219 and the
30220 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
30221 option is also set, then Alpine will
30222 automatically transfer all read messages to the designated folder and mark
30223 them as deleted in the INBOX. Messages in the INBOX marked with an
30224 "N" (meaning New, or unseen) are not affected.
30225 <P>
30226 <UL>
30227 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30228 </UL><P>
30229 <End of help on this topic>
30230 </BODY>
30231 </HTML>
30232 ====== h_config_auto_fcc_only =====
30233 <HTML>
30234 <HEAD>
30235 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
30236 </HEAD>
30237 <BODY>
30238 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
30239 This features controls an aspect of Alpine's composer.
30240 The only time this feature will be used is if you attempt to send mail
30241 that has no recipients but does have an Fcc.
30242 Normally, Alpine will ask if you really mean to copy the message only to
30243 the Fcc.
30244 That is, it asks if you really meant to have no recipients.
30245 If this feature is set, you
30246 will <B>not</B> be prompted to confirm your intent to make only a copy
30247 of a message with no recipients.
30248 <P>
30249 This feature is closely related to
30250 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
30251 The difference between this feature and that feature is that this feature
30252 considers a Bcc to be a recipient while that feature will ask for confirmation
30253 even if there is a Bcc when there is no To, Cc, or Newsgroup.
30254 The default values also differ. This feature defaults to asking the question
30255 and you have to turn it off.
30256 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
30257 unless you turn it on.
30258 <P>
30260 <UL>
30261 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30262 </UL><P>
30263 <End of help on this topic>
30264 </BODY>
30265 </HTML>
30266 ====== h_config_mark_fcc_seen =====
30267 <HTML>
30268 <HEAD>
30269 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
30270 </HEAD>
30271 <BODY>
30272 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
30274 This features controls the way Fccs (File carbon copies) are
30275 made of the messages you send.
30277 <P>
30278 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
30279 copy will be marked as Unseen.
30280 When you look at the folder it was saved in the message will appear to
30281 be a New message until you read it.
30282 When this feature is enabled, the message will be marked as having
30283 been Seen.
30285 <P>
30286 <UL>
30287 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30288 </UL><P>
30289 <End of help on this topic>
30290 </BODY>
30291 </HTML>
30292 ====== h_config_no_fcc_attach =====
30293 <HTML>
30294 <HEAD>
30295 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
30296 </HEAD>
30297 <BODY>
30298 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
30300 This features controls the way Fcc's (File carbon copies) are
30301 made of the messages you send.
30303 <P>
30304 Normally, Alpine saves an exact copy of your message as it was sent.
30305 When this feature is enabled, the "body" of the message
30306 you send (the text you type in the composer) is preserved in the
30307 copy as before, however all attachments are replaced with text
30308 explaining what had been sent rather than the attachments themselves.
30310 <P>
30311 This feature also affects Alpine's "Send ?" confirmation prompt
30312 in that a new "^F Fcc Attchmnts" option becomes available which
30313 allows you to interactively set whether or not attachments are saved
30314 to the Fcc'd copy.
30316 <P>
30317 <UL>
30318 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30319 </UL><P>
30320 <End of help on this topic>
30321 </BODY>
30322 </HTML>
30323 ====== h_config_read_in_newsrc_order =====
30324 <HTML>
30325 <HEAD>
30326 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
30327 </HEAD>
30328 <BODY>
30329 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
30331 This feature controls the order in which newsgroups will be presented. If
30332 set, they will be presented in the same order as they occur in your
30333 <!--chtml if pinemode="os_windows"-->
30334 "NEWSRC"
30335 <!--chtml else-->
30336 ".newsrc"
30337 <!--chtml endif-->
30338 file (the default location of which can be changed with the
30339 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
30340 <P>
30341 If not set, the newsgroups will be presented in alphabetical order.
30342 <P>
30343 <UL>
30344 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30345 </UL><P>
30346 <End of help on this topic>
30347 </BODY>
30348 </HTML>
30349 ====== h_config_quell_tz_comment =====
30350 <HTML>
30351 <HEAD>
30352 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
30353 </HEAD>
30354 <BODY>
30355 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
30357 Normally, when Alpine generates a Date header for outgoing mail,
30358 it will try to include the symbolic timezone at the end of the
30359 header inside parentheses.
30360 The symbolic timezone is often three characters long, but on
30361 some operating systems, it may be longer.
30362 Apparently there are some SMTP servers in the world that will reject an
30363 incoming message if it has a Date header longer than about 80 characters.
30364 If this feature is set, the symbolic timezone normally generated by
30365 Alpine will not be included.
30366 You probably don't need to worry about this feature unless you run into
30367 the problem described above.
30369 <P>
30370 <End of help on this topic>
30371 </BODY>
30372 </HTML>
30373 ====== h_config_post_wo_validation =====
30374 <HTML>
30375 <HEAD>
30376 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
30377 </HEAD>
30378 <BODY>
30379 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
30381 This feature controls whether the NNTP server is queried as newsgroups
30382 are entered for posting. Validation over slow links (e.g. dialup using
30383 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
30384 <P>
30385 <End of help on this topic>
30386 </BODY>
30387 </HTML>
30388 ====== h_config_send_wo_confirm =====
30389 <HTML>
30390 <HEAD>
30391 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
30392 </HEAD>
30393 <BODY>
30394 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
30396 By default, when you send or post a message you will be asked to confirm
30397 with a question that looks something like:
30399 <P>
30400 <CENTER><SAMP>Send message?</SAMP></CENTER>
30401 <P>
30403 If this feature is set, you
30404 will <B>not</B> be prompted to confirm your intent to send
30405 and your message will be sent.
30406 <P>
30407 If this feature is set it disables some possibilities and renders some
30408 other features meaningless.
30409 You will not be able to use
30410 <A HREF="h_config_sending_filter">Sending Filters</A>,
30411 Verbose sending mode,
30412 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30413 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30414 or ^V to turn off the generation of flowed text for this message.
30415 These options are normally available as suboptions in the Send prompt, but
30416 with no Send prompt the options are gone.
30418 <P>
30419 A somewhat related feature is
30420 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30421 which may be used to eliminate the extra confirmation
30422 question when posting to a newsgroup.
30423 <P>
30424 <UL>
30425 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30426 </UL><P>
30427 <End of help on this topic>
30428 </BODY>
30429 </HTML>
30430 ====== h_config_quell_filtering_done_message =====
30431 <HTML>
30432 <HEAD>
30433 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30434 </HEAD>
30435 <BODY>
30436 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30438 If you use Filter Rules that move messages or set status of messages
30439 you sometimes see a message from Alpine that looks like
30441 <P>
30442 <CENTER><SAMP>filtering done</SAMP></CENTER>
30443 <P>
30445 If this feature is set, this message will be suppressed.
30446 If the feature
30447 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30448 is set then this message will be suppressed regardless.
30450 <P>
30451 <UL>
30452 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30453 </UL><P>
30454 <End of help on this topic>
30455 </BODY>
30456 </HTML>
30457 ====== h_config_quell_filtering_messages =====
30458 <HTML>
30459 <HEAD>
30460 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30461 </HEAD>
30462 <BODY>
30463 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30465 If you use Filter Rules that move messages or set status of messages
30466 you sometimes see messages from Alpine that look like
30468 <P>
30469 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30470 <P>
30472 or
30474 <P>
30475 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30476 <P>
30478 or
30480 <P>
30481 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30482 <P>
30484 If this feature is set, these messages will be suppressed.
30485 The feature
30486 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30487 is related.
30489 <P>
30490 <UL>
30491 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30492 </UL><P>
30493 <End of help on this topic>
30494 </BODY>
30495 </HTML>
30496 ====== h_config_quell_post_prompt =====
30497 <HTML>
30498 <HEAD>
30499 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30500 </HEAD>
30501 <BODY>
30502 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30504 By default, when you post a message to a newsgroup you are asked to confirm
30505 that you want to post with the question
30507 <P>
30508 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30509 <P>
30511 If this feature is set, you
30512 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30513 and your message will be posted.
30515 <P>
30516 <UL>
30517 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30518 </UL><P>
30519 <End of help on this topic>
30520 </BODY>
30521 </HTML>
30522 ====== h_config_check_mail_onquit =====
30523 <HTML>
30524 <HEAD>
30525 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30526 </HEAD>
30527 <BODY>
30528 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30530 If this feature is set, Alpine will check for new mail after you give the
30531 Quit command.
30532 If new mail has arrived since the previous check, you will be notified
30533 and given the choice of quitting or not quitting.
30534 <P>
30535 <UL>
30536 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30537 </UL><P>
30538 <End of help on this topic>
30539 </BODY>
30540 </HTML>
30541 ====== h_config_inbox_no_confirm =====
30542 <HTML>
30543 <HEAD>
30544 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30545 </HEAD>
30546 <BODY>
30547 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30549 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30550 command and there are no more folders or newsgroups to visit, you are asked
30551 if you want to return to the INBOX.
30552 If this feature is set you will not be asked.
30553 It will be assumed that you do want to return to the INBOX.
30554 <P>
30555 <UL>
30556 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30557 </UL><P>
30558 <End of help on this topic>
30559 </BODY>
30560 </HTML>
30561 ====== h_config_dates_to_local =====
30562 <HTML>
30563 <HEAD>
30564 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
30565 </HEAD>
30566 <BODY>
30567 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
30569 Normally, the message dates that you see in the
30570 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
30571 For example, if a message was sent to you from a few timezones to the east
30572 it might appear that it was sent from the future;
30573 or if it was sent from somewhere to the west it might appear
30574 as if it is from yesterday even though it was sent only a few minutes ago.
30575 If this feature is set an attempt will be made to convert the dates
30576 to your local timezone to be displayed.
30577 <P>
30578 Note that this does not affect the results of Select by Date or of
30579 anything else other than these displayed dates.
30580 When viewing the message you may look at the original unconverted value of the Date
30581 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
30582 <P>
30583 <UL>
30584 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30585 </UL><P>
30586 <End of help on this topic>
30587 </BODY>
30588 </HTML>
30589 ====== h_config_tab_no_prompt =====
30590 <HTML>
30591 <HEAD>
30592 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
30593 </HEAD>
30594 <BODY>
30595 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
30597 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30598 command and there is a problem checking a folder, you are asked
30599 whether you want to continue with the search in the following folder or not.
30600 This question gives you a chance to stop the NextNew processing.
30601 (The checking problem might be caused by the fact that the folder does not
30602 exist, or by an authentication problem, or by a server problem
30603 of some sort.)
30604 <P>
30606 If this feature is set you will not be asked.
30607 It will be assumed that you do want to continue.
30608 <P>
30609 <UL>
30610 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30611 </UL><P>
30612 <End of help on this topic>
30613 </BODY>
30614 </HTML>
30615 ====== h_config_input_history =====
30616 <HTML>
30617 <HEAD>
30618 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
30619 </HEAD>
30620 <BODY>
30621 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
30623 Many of the prompts that ask for input in the status line near the
30624 bottom of the screen will respond to Up Arrow and Down Arrow
30625 with the history of previous entries.
30626 For example, in the MESSAGE INDEX screen when you use the WhereIs
30627 command the text you entered will be remembered and can be recalled
30628 by using the Up Arrow key.
30629 Another example, when saving a message the folders saved to will
30630 be remembered and can be recalled using the arrow keys.
30631 <P>
30632 In the Save prompt, some users prefer that the Up and Down arrow keys
30633 be used for the Previous Collection and Next Collection commands
30634 instead of for a history of previous saves.
30635 If this option is set the Up and Down arrow keys will become synonyms for the
30636 Previous Collection and Next Collection (^P and ^N) commands in the
30637 prompt for the name of a folder to Save to or in the prompt for the
30638 name of a folder to GoTo.
30639 When this feature is not set (the default), ^P and ^N will change the
30640 collection and the arrow keys will show the history.
30641 <P>
30642 <UL>
30643 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30644 </UL><P>
30645 <End of help on this topic>
30646 </BODY>
30647 </HTML>
30648 ====== h_config_confirm_role =====
30649 <HTML>
30650 <HEAD>
30651 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
30652 </HEAD>
30653 <BODY>
30654 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
30656 If you have roles, when you Reply to or Forward a message, or Compose
30657 a new message, Alpine
30658 will search through your roles for one that matches.
30659 Normally, if no matches are found you will be placed into the composer
30660 with no opportunity to select a role.
30661 If this feature is set, then you will be asked to confirm that you don't
30662 want a role.
30663 This will give you the opportunity to select a role (with the ^T command).
30664 If you confirm no role with a Return, you will be placed in
30665 the composer with no role.
30666 You may also confirm with either an "N" or a "Y".
30667 These behave the same as if you pressed the Return.
30668 (The "N" and "Y" answers are available because they
30669 match what you might type if there was a role match.)
30670 <P>
30671 If you are using the alternate form of the Compose command called
30672 "Role", then all of your roles will be available to you,
30673 independent of the value of this feauture and of the values set for all of
30674 Reply Use, Forward Use, and Compose Use.
30675 <P>
30676 <UL>
30677 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30678 </UL><P>
30679 <End of help on this topic>
30680 </BODY>
30681 </HTML>
30682 ====== h_config_news_cross_deletes =====
30683 <HTML>
30684 <HEAD>
30685 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
30686 </HEAD>
30687 <BODY>
30688 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
30690 This feature controls what Alpine does when you delete a message in a
30691 newsgroup that appears in more than one newsgroup. Such a message
30692 is sometimes termed a "crossposting" in that it was posted
30693 across several newsgroups.
30695 <P>
30696 Alpine's default behavior when you delete such a message is to remove
30697 only the copy in the current newsgroup from view when you use the
30698 "Exclude" command or the next time you visit the newsgroup.
30700 <P>
30701 Enabling this feature causes Alpine to remove every occurrence of the
30702 message from all newsgroups it appears in and to which you are
30703 subscribed.
30705 <P>
30706 NOTE: As currently implemented, enabling this feature may increase the
30707 time it takes the Expunge command and newsgroup closing to complete.
30709 <P>
30710 <UL>
30711 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30712 </UL><P>
30713 <End of help on this topic>
30714 </BODY>
30715 </HTML>
30716 ====== h_config_news_catchup =====
30717 <HTML>
30718 <HEAD>
30719 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
30720 </HEAD>
30721 <BODY>
30722 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
30724 This feature controls what Alpine does as it closes a newsgroup.
30725 When set, Alpine will offer to delete all messages from the newsgroup
30726 as you are quitting Alpine or opening a new folder.
30728 <P>
30729 This feature is useful if you typically read all the interesting messages
30730 in a newsgroup each time you open it. This feature saves you from
30731 having to delete each message in a newsgroup as you read it or from
30732 selecting all the messages and doing an
30733 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
30734 move on to the next folder or newsgroup.
30736 <P>
30737 <UL>
30738 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30739 </UL><P>
30740 <End of help on this topic>
30741 </BODY>
30742 </HTML>
30743 ====== h_config_next_thrd_wo_confirm =====
30744 <HTML>
30745 <HEAD>
30746 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
30747 </HEAD>
30748 <BODY>
30749 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
30751 This feature controls an aspect of Alpine's Next and Prev commands in
30752 the case where you are using one of the
30753 "separate-index-screen" styles for the configuration option
30754 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
30755 and currently have the folder sorted by a Threaded or OrderedSubject sort.
30756 When you are Viewing a particular thread you have a
30757 MESSAGE INDEX of only the messages in that thread.
30758 If you press the Next command with the last message in the thread highlighted
30759 you will normally be asked if you want to "View next thread?",
30760 assuming there is a next thread to view.
30761 If this feature is set it will be assumed that you always want to view the
30762 next thread and you won't be asked to confirm that.
30763 Similarly, if the first message of the thread is highlighted and you
30764 press the Prev command, this feature will prevent the question
30765 "View previous thread".
30766 <P>
30767 This feature only has an effect in the MESSAGE INDEX screen.
30768 If you then view a particular message from that screen and press the
30769 Next command, you will be sent to the next thread without being asked,
30770 independent of the setting of this feature.
30771 <P>
30772 The feature
30773 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
30774 <P>
30775 <End of help on this topic>
30776 </BODY>
30777 </HTML>
30778 ====== h_config_kw_braces =====
30779 <HTML>
30780 <HEAD>
30781 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
30782 </HEAD>
30783 <BODY>
30784 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
30786 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
30787 TEXT screens.
30788 If you have modified the
30789 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
30790 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
30791 are used to display keywords or their initials along with the Subject; then
30792 this option may be used to modify the resulting display slightly.
30793 By default, the keywords or initials displayed for these tokens will be
30794 surrounded with curly braces ({ and }) and a trailing space.
30795 For example, if keywords "Work" and "Now" are set for
30796 a message, the "SUBJKEY" token will normally look like
30797 <P>
30798 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
30799 <P>
30800 and the SUBJKEYINIT token would look like
30801 <P>
30802 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
30803 <P>
30804 The default character before the keywords is the left brace ({) and the
30805 default after the keywords is the right brace followed by a space (} ).
30806 <P>
30807 This option allows you to change that.
30808 You should set it to two values separated by a space.
30809 The values may be quoted if they include space characters.
30810 So, for example, the default value could be specified explicitly by setting this
30811 option to
30812 <P>
30813 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
30814 <P>
30815 The first part wouldn't need to be quoted (but it doesn't hurt).
30816 The second part does need the quotes because it includes a space character.
30817 If you wanted to change the braces to brackets you could use
30818 <P>
30819 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
30820 <P>
30821 Inside the quotes you can use backslash quote to mean quote, so
30822 <P>
30823 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
30824 <P>
30825 would produce
30826 <P>
30827 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
30828 <P>
30829 It is also possible to color keywords in the index using the
30830 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
30831 <P>
30832 It is not possible to change the fact that a space character is used to
30833 separate the keywords if more than one keyword is set for a message.
30834 It is also not possible to change the fact that there are no separators
30835 between the keyword initials if more than one keyword is set.
30836 <P>
30837 <End of help on this topic>
30838 </BODY>
30839 </HTML>
30840 ====== h_config_opening_sep =====
30841 <HTML>
30842 <HEAD>
30843 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
30844 </HEAD>
30845 <BODY>
30846 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
30848 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
30849 With some setups the text of the subject is followed
30850 by the opening text of the message if there is any room available in the index line.
30851 If you have configured your
30852 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
30853 to include one of the Subject tokens that causes this behavior
30854 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
30855 to modify what is displayed slightly.
30856 By default, the Subject is separated from the opening text of the message by
30857 the three characters space dash space;
30858 <P>
30859 <CENTER><SAMP>" - "</SAMP></CENTER>
30860 <P>
30861 Use this option to set it to something different.
30862 The value must be quoted if it includes any space characters.
30863 For example, the default value could be specified explicitly by setting this
30864 option to
30865 <P>
30866 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
30867 <P>
30868 <End of help on this topic>
30869 </BODY>
30870 </HTML>
30871 ====== h_config_select_wo_confirm =====
30872 <HTML>
30873 <HEAD>
30874 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
30875 </HEAD>
30876 <BODY>
30877 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
30879 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
30880 These commands all take text input to specify the name of the folder or
30881 file to be used, but allow you to press ^T for a list of possible names.
30882 If set, the selected name will be used immediately, without further
30883 opportunity to confirm or edit the name.
30884 <P>
30885 Some related help topics are
30886 <UL>
30887 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
30888 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
30889 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
30890 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
30891 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
30892 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
30893 </UL>
30894 <P>
30895 <End of help on this topic>
30896 </BODY>
30897 </HTML>
30898 ====== h_config_save_part_wo_confirm =====
30899 <HTML>
30900 <HEAD>
30901 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
30902 </HEAD>
30903 <BODY>
30904 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
30906 This feature controls an aspect of Alpine's Save command.
30907 By default, when you Save a message that has some deleted parts, you will
30908 be asked to confirm that you want to Save with a prompt that looks like:
30909 <P>
30910 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
30911 <P>
30912 If this feature is set, you will not be asked.
30913 <P>
30914 <End of help on this topic>
30915 </BODY>
30916 </HTML>
30917 ====== h_config_use_resentto =====
30918 <HTML>
30919 <HEAD>
30920 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
30921 </HEAD>
30922 <BODY>
30923 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
30925 This feature is turned off by default because turning it on causes problems
30926 with some deficient IMAP servers.
30927 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
30928 <A HREF="h_rule_patterns">Pattern</A>
30929 contains a To header pattern and this feature is turned on,
30930 then a check is made in the message to see
30931 if a Resent-To header is present, and that is used instead of the To header.
30932 If this feature is not turned on, then the regular To header will always
30933 be used.
30935 <P>
30936 <End of help on this topic>
30937 </BODY>
30938 </HTML>
30939 ====== h_config_use_reg_start_for_stayopen =====
30940 <HTML>
30941 <HEAD>
30942 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
30943 </HEAD>
30944 <BODY>
30945 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
30947 This feature affects which message is selected as the current message
30948 when you enter a
30949 <A HREF="h_config_permlocked">Stay Open</A> folder.
30950 <P>
30951 Normally, the starting position for an incoming folder (which most Stay Open
30952 folders will likely be) is controlled by the
30953 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
30954 However, if a folder is a Stay Open folder, when you re-enter the folder
30955 after the first time the current message will be the same as it was when
30956 you left the folder.
30957 An exception is made if you use the TAB command to get to the folder.
30958 In that case, the message number will be incremented by one from what it
30959 was when you left the folder.
30960 <P>
30961 The above special behavior is thought to be useful.
30962 However, it is special and different from what you might at first expect.
30963 If this feature is set, then Stay Open folders will not be treated specially
30964 as far as the startup rule is concerned.
30966 <P>
30967 <End of help on this topic>
30968 </BODY>
30969 </HTML>
30970 ====== h_config_use_current_dir =====
30971 <HTML>
30972 <HEAD>
30973 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
30974 </HEAD>
30975 <BODY>
30976 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
30978 This feature controls an aspect of several commands.
30979 If set, your "current working directory"
30980 <!--chtml if pinemode="running"-->
30981 (which, at least for your current Alpine "session,"
30982 is "<!--#echo var="CURRENT_DIR"-->")
30983 <!--chtml endif-->
30984 will be used instead of your home directory
30985 <!--chtml if pinemode="running"-->
30986 (which, in the present configuration of your system, is
30987 "<!--#echo var="HOME_DIR"-->")
30988 <!--chtml endif-->
30989 for all of the following operations:<UL>
30990 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
30991 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
30992 <LI> <!--chtml if pinemode="function_key"-->F4
30993 <!--chtml else-->Ctrl-R
30994 <!--chtml endif--> file inclusion in the COMPOSER
30995 <LI> <!--chtml if pinemode="function_key"-->F5
30996 <!--chtml else-->Ctrl-J
30997 <!--chtml endif--> file attachment in the COMPOSER
30998 </UL>
30999 <!--chtml if pinemode="os_windows"-->
31000 <P>
31001 If you are starting PC-Alpine from a desktop icon or the Start menu,
31002 you can set the "current drive"
31003 by specifying it in the "Start in:"
31004 box found in the Shortcut tab of the Properties.
31005 <!--chtml endif-->
31006 <P>
31007 <UL>
31008 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31009 </UL>
31011 <P>
31012 <End of help on this topic>
31013 </BODY>
31014 </HTML>
31015 ====== h_config_save_wont_delete =====
31016 <HTML>
31017 <HEAD>
31018 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
31019 </HEAD>
31020 <BODY>
31021 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
31023 This feature controls one aspect of the Save command. If set, Save will
31024 not mark the message "deleted" (its default behavior) after
31025 it has been copied to the designated folder.
31027 <P>
31028 <End of help on this topic>
31029 </BODY>
31030 </HTML>
31031 ====== h_config_use_boring_spinner =====
31032 <HTML>
31033 <HEAD>
31034 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
31035 </HEAD>
31036 <BODY>
31037 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
31039 When Alpine is delayed for some reason it usually shows that
31040 something is happening with a small animated display in the status
31041 message line near the bottom of the screen.
31042 Setting this feature will cause that animation to be the same
31043 each time instead of having Alpine choose a random animation.
31044 You may turn the animation off altogether by setting the
31045 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
31046 option to zero.
31048 <P>
31049 <End of help on this topic>
31050 </BODY>
31051 </HTML>
31052 ====== h_config_unsel_wont_advance =====
31053 <HTML>
31054 <HEAD>
31055 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
31056 </HEAD>
31057 <BODY>
31058 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
31060 This feature controls one aspect of the Unselect Current message command.
31061 Normally, when the Unselect current message command (:) is typed when the
31062 current message is selected, the message will be unselected and the next
31063 message will become the current message.
31064 If this feature is set, the cursor will not advance to the next message.
31065 Instead, the current message will remain the current message after
31066 unselecting.
31068 <P>
31069 <End of help on this topic>
31070 </BODY>
31071 </HTML>
31072 ====== h_config_prune_uses_iso =====
31073 <HTML>
31074 <HEAD>
31075 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
31076 </HEAD>
31077 <BODY>
31078 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
31080 By default, Alpine asks monthly whether or not you would like to rename
31081 some folders to a new name containing the date.
31082 It also asks whether or not you would like to delete some old folders.
31083 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
31084 explanation.
31086 <P>
31087 By default, the name used when renaming a folder looks like
31088 <P>
31089 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
31090 <P>
31091 For example, the first time you run Alpine in May of 2004,
31092 the folder "sent-mail" might be renamed to
31093 <P>
31094 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
31095 <P>
31096 If this feature is set, the name used will be of the form
31097 <P>
31098 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
31099 <P>
31100 where "yyyy" is the year and "mm" is the two-digit
31101 month (01, 02, ..., 12).
31102 For the April, 2004 example above, it would instead be
31103 <P>
31104 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
31105 <P>
31106 because April is the 4th month of the year.
31107 A reason you might want to set this feature is so that the folders
31108 will sort in chronological order.
31110 <P>
31111 <End of help on this topic>
31112 </BODY>
31113 </HTML>
31114 ====== h_config_save_advances =====
31115 <HTML>
31116 <HEAD>
31117 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
31118 </HEAD>
31119 <BODY>
31120 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
31122 This feature controls one aspect of the Save command. If set, Save will
31123 (in addition to copying the current message to the designated folder) also
31124 advance to the next message.
31126 <P>
31127 <End of help on this topic>
31128 </BODY>
31129 </HTML>
31130 ====== h_config_force_arrow =====
31131 <HTML>
31132 <HEAD>
31133 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
31134 </HEAD>
31135 <BODY>
31136 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
31138 This feature affects Alpine's MESSAGE INDEX display routine.
31139 If set, the normal inverse-video cursor will be
31140 replaced by a simple "arrow" cursor, which normally occupies the
31141 second column of the index display.
31142 <P>
31143 This is the same index cursor you get if you turn on
31144 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
31145 line coloring will still be present if this feature is turned on and
31146 <!--#echo var="FEAT_assume-slow-link"--> is off.
31147 <P>
31148 An alternative version of the Arrow cursor is available by including the
31149 <A HREF="h_config_index_arrow_color">ARROW</A>
31150 token in the
31151 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31152 <P>
31153 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
31154 but that is not implemented.
31156 <P>
31157 <End of help on this topic>
31158 </BODY>
31159 </HTML>
31160 ====== h_config_force_low_speed =====
31161 <HTML>
31162 <HEAD>
31163 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
31164 </HEAD>
31165 <BODY>
31166 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
31168 UNIX Alpine only.
31169 <P>
31170 This feature affects Alpine's display routines. If set, the normal
31171 inverse-video cursor (used to highlight the current item in a list) will be
31172 replaced by an "arrow" cursor and other
31173 screen update optimizations for
31174 low-speed links (e.g. 2400 bps dialup connections) will be activated.
31175 One of the optimizations is that colored index lines (set up with Indexcolor
31176 Rules) will not be colored.
31177 If you are just turning this feature on because you like using
31178 the "arrow" cursor you may have an arrow cursor with index line
31179 coloring by turning this feature off and the
31180 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
31182 <P>
31183 <End of help on this topic>
31184 </BODY>
31185 </HTML>
31186 ====== h_config_show_delay_cue =====
31187 <HTML>
31188 <HEAD>
31189 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
31190 </HEAD>
31191 <BODY>
31192 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
31194 If set, this feature will cause an asterisk to appear in the upper
31195 left-hand corner of the screen whenever Alpine checks for new mail.
31196 Two asterisks whenever Alpine saves (checkpoints) the state of the current
31197 mailbox to disk.
31199 <!--chtml if pinemode="os_windows"-->
31200 <P>
31201 In addition, PC-Alpine will display a less-than symbol, '<', when
31202 it is trying to open a network connection (e.g, to open your INBOX
31203 on an IMAP
31204 server) or read from the network connection. A greater-than symbol,
31205 will be displayed when PC-Alpine is trying to write to the network
31206 connection (e.g, sending a command to your IMAP server).
31207 <!--chtml endif-->
31209 <P>
31210 <End of help on this topic>
31211 </BODY>
31212 </HTML>
31213 ====== h_config_color_style =====
31214 <HTML>
31215 <HEAD>
31216 <TITLE>OPTION: Color Style</TITLE>
31217 </HEAD>
31218 <BODY>
31219 <H1>OPTION: Color Style</H1>
31221 UNIX Alpine only.
31222 <P>
31223 If the terminal or terminal emulator you are using is capable of displaying
31224 colors, this option controls whether or not color will be used in Alpine.
31225 If you turn color on and things are set up correctly,
31226 you should see color appear on the screen immmediately.
31227 Modern terminal emulators are usually capable of displaying colors.
31228 <P>
31229 The available options include:
31230 <P>
31232 <DL>
31233 <DT>no-color</DT>
31234 <DD>Don't use color.
31235 </DD>
31237 <DT>use-termdef</DT>
31238 <DD>In order to decide if your terminal is capable of color, Alpine looks in
31239 the terminal capabilities database, TERMINFO or TERMCAP, depending on
31240 how Alpine was compiled.
31241 This is a good option to choose if you switch between a color and a non-color
31242 terminal with the same Alpine configuration.
31243 Alpine will know to use color on the color terminal because it is described
31244 in the termcap entry, and Alpine will know to use black and white on the
31245 non-color terminal.
31246 The Alpine Technical Notes
31247 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
31248 have more information on configuring a TERMCAP or TERMINFO
31249 entry for color Alpine.
31250 This is usually something a system administrator does.
31251 </DD>
31253 <DT>force-ansi-8color</DT>
31254 <DD>This is probably the setting that most people should use.
31255 Because setting up a termcap entry is confusing and because the
31256 terminal capabilities database is often not correctly configured for color,
31257 this choice and the next may be easier for you to use.
31258 If your terminal emulator responds to ANSI color escape sequences, which
31259 many do, this option will cause Alpine to believe your terminal will respond
31260 to the escape sequences that produce eight different foreground and background
31261 colors.
31262 The escape sequences used to set the foreground colors are
31264 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
31266 where the color_number is an ASCII digit between 0 and 7.
31267 The numbers 0 through 7 should correspond to the colors black, red, green,
31268 yellow, blue, magenta, cyan, and white.
31269 Some terminal emulators use a pre-ANSI scheme that swaps
31270 the colors blue and red and the colors yellow and cyan.
31271 This will cause the default colors to be different, but other than that
31272 things should work fine.
31273 There is also a 9th color available, the last one shown, which is the default
31274 color from the terminal emulator.
31275 When used as a background color some people refer to this color as
31276 "transparent", which is why the letters "TRAN" are
31277 shown in the color swatch of the SETUP COLOR screen.
31278 The foreground transparent color is shown as
31279 the color of the "TRAN" text.
31280 (The transparent color will not work correctly in a PC-Alpine configuration.)
31281 The escape sequences used to set the background colors are the same
31282 as for the foreground colors except a "4" replaces the "3".
31283 The escape sequences for foreground and background default colors (transparent)
31284 are 39m and 49m.
31285 <P>
31286 Note: With the Tera Term terminal emulator this setting works well.
31287 You should also have the Tera Term "Full color" option turned OFF.
31288 You may find the "Full color" option in Tera Term's "Setup"
31289 menu, in the "Window" submenu.
31290 </DD>
31292 <DT>force-ansi-16color</DT>
31293 <DD>Many terminal emulators know about the same eight colors above
31294 plus eight more.
31295 This option attempts to use all 16 colors.
31296 The same escape sequences as for the eight-color terminal are used
31297 for the first eight colors.
31298 The escape sequences used to set foreground colors 8-15 are the same as
31299 for 0-7 except the "3" is replaced with a "9".
31300 The background color sequences for colors 8-15 are the same as for 0-7
31301 except the "4" is replaced with "10".
31302 You can tell if the 16 colors are working by turning on this option
31303 and then going into one of the color configuration screens, for example,
31304 the configuration screen for Normal Color.
31305 If you see 16 different colors to select from (plus a 17th for
31306 the transparent color), it's working.
31307 </DD>
31309 <DT>force-xterm-256color</DT>
31310 <DD>Some versions of xterm (and some other terminal emulators)
31311 have support for 256 colors.
31312 The escape sequences used to set the foreground colors are
31314 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
31316 where the color_number is an ASCII digit between 0 and 255.
31317 Background colors are the same with the 38 replaced with a 48.
31318 The numbers 0 through 15 are probably similar to the 16 color version
31319 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
31320 The terminal default (transparent) color is the 257th color at the bottom.
31321 Some terminal emulators will misinterpret these escape sequences causing
31322 the terminal to blink or overstrike characters or to do something else
31323 undesirable.
31324 <P>
31325 The PuTTY terminal emulator has an option called "Allow terminal to
31326 use xterm 256-colour mode" which allows PuTTY to work well with
31327 this 256-color setting.
31329 </DD>
31330 </DL>
31332 <P>
31333 The normal default is "no-color".
31334 <P>
31336 Once you've turned on color you may set the
31337 colors of many objects on the screen individually.
31338 For example, you may add colors to the status letters on the MESSAGE
31339 INDEX page.
31340 Most categories of color that Alpine supports are configurable here.
31341 For example, "Normal Color"
31342 is the color used to display most of the text in Alpine, and
31343 "Reverse Color" is used to display highlighted text, such as the
31344 current message in the MESSAGE INDEX.
31345 <P>
31346 Lines in the MESSAGE INDEX may also be colored.
31347 Use Setup Rules to get to the Indexcolor configuration screen.
31348 <P>
31350 <UL>
31351 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31352 </UL><P>
31353 <End of help on this topic>
31354 </BODY>
31355 </HTML>
31356 ====== h_config_disable_index_locale_dates =====
31357 <HTML>
31358 <HEAD>
31359 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
31360 </HEAD>
31361 <BODY>
31362 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
31364 This feature affects the display of dates in the MESSAGE INDEX.
31365 Normally an attempt is made to localize the dates
31366 used in the MESSAGE INDEX display to your locale.
31367 This is controlled with the
31368 LC_TIME locale setting on a UNIX system.
31369 On Windows the Regional Options control panel may be used to set the date format.
31370 At the programming level, Alpine is using the strftime routine
31371 to print the parts of a date.
31372 <P>
31373 If this feature is set, dates are displayed in English and
31374 with the conventions of the United States.
31375 <P>
31377 <UL>
31378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31379 </UL><P>
31380 <End of help on this topic>
31381 </BODY>
31382 </HTML>
31383 ====== h_config_auto_open_unread =====
31384 <HTML>
31385 <HEAD>
31386 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
31387 </HEAD>
31388 <BODY>
31389 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
31391 This feature controls the behavior of the TAB key when traversing folders
31392 in the optional
31393 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
31394 collection or in optional <!--#echo var="VAR_news-collections"-->.
31395 <P>
31396 When the TAB
31397 (<A HREF="h_common_nextnew">NextNew</A>)
31398 key is pressed, and there
31399 are no more unseen messages in the current (incoming message or news)
31400 folder, Alpine will search the list of folders in the current collection for
31401 one containing New or Recent (new since the last time the folder was
31402 opened) messages.
31403 This behavior may be modified slightly with the
31404 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31405 feature that causes Alpine to look for Unseen messages instead of Recent
31406 messages.
31407 Normally, when such a folder is found, Alpine will ask
31408 whether you wish to open the folder. If this feature is set, Alpine will
31409 automatically open the folder without prompting.
31410 <P>
31411 This feature also affects some other similar situations.
31412 If you have a
31413 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31414 that is equal to one of the "separate-" values, and you are
31415 viewing a thread; then when you type the NextNew command and are at the
31416 end of the current thread you will automatically go to the next thread
31417 if this feature is set.
31418 By default, you would be asked if you want to view the next thread.
31419 You will also be asked at times whether or not you want to view the next
31420 thread after you delete the last message in the thread.
31421 Setting this feature will also cause that question to be skipped.
31422 <P>
31424 <UL>
31425 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31426 </UL><P>
31427 <End of help on this topic>
31428 </BODY>
31429 </HTML>
31430 ====== h_config_auto_include_reply =====
31431 <HTML>
31432 <HEAD>
31433 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31434 </HEAD>
31435 <BODY>
31436 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31438 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31439 will ask whether you wish to include the original message in your reply.
31440 If this feature is set and the feature
31441 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31442 is <EM>not</EM> set, then the original message will be included in the reply
31443 automatically, without prompting.
31444 <P>
31445 <End of help on this topic>
31446 </BODY>
31447 </HTML>
31448 ====== h_config_select_in_bold =====
31449 <HTML>
31450 <HEAD>
31451 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31452 </HEAD>
31453 <BODY>
31454 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31456 This feature controls an aspect of Alpine's
31457 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31458 commands; in
31459 particular, the Select and WhereIs commands. Select and WhereIs (with the
31460 ^X subcommand) will search the current folder for messages meeting a
31461 specified criteria, and "tag" the resulting messages with an
31462 "X" in the
31463 first column of the applicable lines in the MESSAGE INDEX. If this feature
31464 is set, instead of using the "X" to denote a selected message,
31465 Alpine will
31466 attempt to display those index lines in boldface. Whether this is
31467 preferable to the "X" will depend on personal taste and the type of
31468 terminal being used.
31469 <P>
31470 <UL>
31471 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31472 </UL><P>
31473 <End of help on this topic>
31474 </BODY>
31475 </HTML>
31476 ====== h_config_alt_auth =====
31477 <HTML>
31478 <HEAD>
31479 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31480 </HEAD>
31481 <BODY>
31482 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31484 This feature affects how Alpine connects to IMAP servers.
31485 It's utility has largely been overtaken by events,
31486 but it may still be useful in some circumstances.
31487 If you only connect to modern IMAP servers that support
31488 "TLS" you can ignore this feature.
31490 <P>
31491 Details:
31493 <P>
31494 By default, Alpine will attempt to connect to an IMAP server on the
31495 normal IMAP service port (143), and if the server offers "Transport Layer
31496 Security" (TLS) and Alpine has been compiled with encryption capability,
31497 then a secure (encrypted) session will be negotiated.
31499 <P>
31500 With this feature enabled, before connecting on the normal IMAP port, Alpine
31501 will first attempt to connect to an alternate IMAP service port (993) used
31502 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31503 (SSL) method.
31504 If the SSL attempt fails, Alpine will then try the default
31505 behavior described in the previous paragraph.
31507 <P>
31508 TLS negotiation on the normal port is preferred, and supersedes the use of
31509 SSL on port 993, but older servers may not provide TLS support.
31510 This feature may be convenient when accessing IMAP servers that do not support
31511 TLS, but do support SSL connections on port 993.
31512 However, it is important to understand that with this feature enabled,
31513 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
31514 but it will proceed to make an insecure connection if that is the only
31515 option offered by the server, or if the Alpine in question has been built
31516 without encryption capability.
31518 <P>
31519 Note that this feature specifies a per-user (or system-wide) default
31520 behavior, but host/folder specification flags may be used to control the
31521 behavior of any specific connection.
31522 This feature interacts with some of
31523 the possible host/folder path specification flags as follows:
31525 <P>
31526 The <SAMP>/tls</SAMP> host flag, for example,
31528 <P>
31529 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
31530 <P>
31531 will over-ride this feature for the specified host by bypassing the
31532 SSL connection attempt.
31533 Moreover, with <SAMP>/tls</SAMP> specified,
31534 the connection attempt will fail if the
31535 service on port 143 does not offer TLS support.
31537 <P>
31538 The <SAMP>/ssl</SAMP> host flag, for example,
31540 <P>
31541 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
31542 <P>
31543 will insist on an SSL connection for the specified host,
31544 and will fail if the SSL service on port 993 is not available.
31545 Alpine will not subsequently retry a connection
31546 on port 143 if <SAMP>/ssl</SAMP> is specified.
31548 <P>
31549 <UL>
31550 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31551 </UL><P>
31552 <End of help on this topic>
31553 </BODY>
31554 </HTML>
31555 ====== h_config_file_dir ======
31556 <HTML>
31557 <HEAD>
31558 <TITLE>OPTION: File Directory</TITLE>
31559 </HEAD>
31560 <BODY>
31561 <H1>OPTION: File Directory</H1>
31563 PC-Alpine only.
31564 <P>
31565 This value affects the Composer's "^J Attach" command,
31566 the Attachment Index Screen's "S Save" command, and the
31567 Message Index's "E Export" command.
31569 <P>
31570 Normally, when a filename is supplied that lacks a leading "path"
31571 component, Alpine assumes the file exists in the user's home directory.
31572 Under Windows operating systems, this definition isn't always clear. This
31573 feature allows you to explictly set where Alpine should look for files
31574 without a leading path.
31576 <P>
31577 NOTE: this feature's value is ignored if either
31578 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
31579 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
31581 <P>
31582 <UL>
31583 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31584 </UL><P>
31585 <End of help on this topic>
31586 </BODY>
31587 </HTML>
31588 ====== h_config_quote_all_froms =====
31589 <HTML>
31590 <HEAD>
31591 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
31592 </HEAD>
31593 <BODY>
31594 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
31596 This feature controls an aspect of the Save command (and also the way
31597 outgoing messages are saved to an FCC folder). If set, Alpine will add
31598 a leading ">" character in front of message lines beginning with "From"
31599 when they are saved to another folder, including lines syntactically
31600 distinguishable from the type of message separator line commonly used on
31601 Unix systems.
31603 <P>
31604 The default behavior is that a ">" will be prepended only to lines
31605 beginning with "From " that might otherwise be confused with a message
31606 separator line on Unix systems. If pine is the only mail program you use,
31607 this default is reasonable. If another program you use has trouble
31608 displaying a message with an unquoted "From " saved by Alpine, you should
31609 enable this feature. This feature only applies to the common Unix mailbox
31610 format that uses message separator lines beginning with "From ". If
31611 Alpine has been configured to use a different mailbox format (possibly
31612 incompatible with other mail programs), then this issue does not arise,
31613 and the feature is irrelevant.
31615 <P>
31616 <End of help on this topic>
31617 </BODY>
31618 </HTML>
31619 ====== h_config_normal_color =====
31620 <HTML>
31621 <HEAD>
31622 <TITLE>OPTION: Normal Color</TITLE>
31623 </HEAD>
31624 <BODY>
31625 <H1>OPTION: Normal Color</H1>
31627 Sets the color Alpine normally uses.
31628 The foreground color is the color of the actual character and the
31629 background color is the color of the area behind the character.
31630 By default this color is black characters on a white background.
31631 <P>
31632 <A HREF="h_color_setup">Descriptions of the available commands</A>
31633 <P>
31634 Look <A HREF="h_edit_nav_cmds">here</A>
31635 to see the available Editing and Navigation commands.
31636 <P>
31637 <End of help on this topic>
31638 </BODY>
31639 </HTML>
31640 ====== h_config_reverse_color =====
31641 <HTML>
31642 <HEAD>
31643 <TITLE>OPTION: Reverse Color</TITLE>
31644 </HEAD>
31645 <BODY>
31646 <H1>OPTION: Reverse Color</H1>
31648 Sets the color Alpine uses for reverse video characters.
31649 The foreground color is the color of the actual character and the
31650 background color is the color of the area behind the character.
31651 <P>
31652 <A HREF="h_color_setup">Descriptions of the available commands</A>
31653 <P>
31654 Look <A HREF="h_edit_nav_cmds">here</A>
31655 to see the available Editing and Navigation commands.
31656 <P>
31657 <End of help on this topic>
31658 </BODY>
31659 </HTML>
31660 ====== h_config_title_color =====
31661 <HTML>
31662 <HEAD>
31663 <TITLE>OPTION: Title Color</TITLE>
31664 </HEAD>
31665 <BODY>
31666 <H1>OPTION: Title Color</H1>
31668 Sets the color Alpine uses for the titlebar (the top line on the screen).
31669 The foreground color is the color of the actual character and the
31670 background color is the color of the area behind the character.
31671 By default, the Title Color is black characters on a yellow background.
31672 <P>
31673 The actual titlebar color may be different from the Title Color if
31674 the option
31675 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
31676 is set to some value other than the default.
31677 It may also be different if the current folder is closed and the
31678 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
31679 color is set to something different from the Title Color.
31680 <P>
31681 <A HREF="h_color_setup">Descriptions of the available commands</A>
31682 <P>
31683 Look <A HREF="h_edit_nav_cmds">here</A>
31684 to see the available Editing and Navigation commands.
31685 <P>
31686 <End of help on this topic>
31687 </BODY>
31688 </HTML>
31689 ====== h_config_titleclosed_color =====
31690 <HTML>
31691 <HEAD>
31692 <TITLE>OPTION: Title Closed Color</TITLE>
31693 </HEAD>
31694 <BODY>
31695 <H1>OPTION: Title Closed Color</H1>
31697 Sets the color Alpine uses for the titlebar (the top line on the screen)
31698 when the current folder is closed.
31699 The foreground color is the color of the actual character and the
31700 background color is the color of the area behind the character.
31701 By default, the Title Color Closed Color is white characters on a red background.
31702 <P>
31703 By setting this color to something noticeable you will be alerted to the
31704 fact that the current folder is closed, perhaps unexpectedly.
31705 <P>
31706 <End of help on this topic>
31707 </BODY>
31708 </HTML>
31709 ====== h_config_status_color =====
31710 <HTML>
31711 <HEAD>
31712 <TITLE>OPTION: Status Color</TITLE>
31713 </HEAD>
31714 <BODY>
31715 <H1>OPTION: Status Color</H1>
31717 Sets the color Alpine uses for status messages written to the message
31718 line near the bottom of the screen.
31719 The foreground color is the color of the actual character and the
31720 background color is the color of the area behind the character.
31721 By default, the Status Color is the same as the Reverse Color.
31722 <P>
31723 <A HREF="h_color_setup">Descriptions of the available commands</A>
31724 <P>
31725 Look <A HREF="h_edit_nav_cmds">here</A>
31726 to see the available Editing and Navigation commands.
31727 <P>
31728 <End of help on this topic>
31729 </BODY>
31730 </HTML>
31731 ====== h_config_index_opening_color =====
31732 <HTML>
31733 <HEAD>
31734 <TITLE>OPTION: Index Opening Color</TITLE>
31735 </HEAD>
31736 <BODY>
31737 <H1>OPTION: Index Opening Color</H1>
31739 With some setups the text of the subject is followed
31740 by the opening text of the message if there is any room available in the index line.
31741 If you have configured your
31742 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31743 to include one of the Subject tokens that causes this behavior
31744 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
31745 this opening text with this option.
31746 This coloring takes place for all but the current index line, and the Opening
31747 Color appears to be in front of any color from an Index Color Rule.
31748 <P>
31749 By default the Index Opening Color is gray characters on a white background.
31751 <P>
31752 <A HREF="h_color_setup">Descriptions of the available commands</A>
31753 <P>
31754 Look <A HREF="h_edit_nav_cmds">here</A>
31755 to see the available Editing and Navigation commands.
31756 <P>
31757 <End of help on this topic>
31758 </BODY>
31759 </HTML>
31760 ====== h_config_index_pri_color =====
31761 <HTML>
31762 <HEAD>
31763 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
31764 </HEAD>
31765 <BODY>
31766 <H1>OPTION: Index Priority Symbol Colors</H1>
31768 The X-Priority header is a non-standard header that is used in a
31769 somewhat standard way by many mail programs.
31770 Alpine expects the value of this header to be a digit with a value
31771 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
31772 Alpine can be made to display an indication of this priority in
31773 messages by use of one of the tokens
31774 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
31775 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
31776 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31778 <P>
31779 You may set the color used to draw these tokens by use of the colors
31780 Index High Priority Symbol Color and Index Low Priority Symbol Color.
31781 This coloring takes place for all but the current index line, and the Priority
31782 Color appears to be in front of any color from an Index Color Rule.
31783 If the priority has a value of 1 or 2 the High Priority color will be
31784 used,
31785 and if the value is 4 or 5 the Low Priority color will be used.
31786 <P>
31787 If you don't set these colors the index line will be colored in the same color as
31788 the bulk of the index line.
31790 <P>
31791 <A HREF="h_color_setup">Descriptions of the available commands</A>
31792 <P>
31793 Look <A HREF="h_edit_nav_cmds">here</A>
31794 to see the available Editing and Navigation commands.
31795 <P>
31796 <End of help on this topic>
31797 </BODY>
31798 </HTML>
31799 ====== h_config_index_subject_color =====
31800 <HTML>
31801 <HEAD>
31802 <TITLE>OPTION: Index Subject Color</TITLE>
31803 </HEAD>
31804 <BODY>
31805 <H1>OPTION: Index Subject Color</H1>
31807 You may set the color used to draw the Subject part of the index line.
31808 This coloring takes place for all but the current index line, and the Subject
31809 Color appears to be in front of any color from an Index Color Rule.
31810 <P>
31811 If you don't set this color it will be colored in the same color as
31812 the bulk of the index line.
31814 <P>
31815 <A HREF="h_color_setup">Descriptions of the available commands</A>
31816 <P>
31817 Look <A HREF="h_edit_nav_cmds">here</A>
31818 to see the available Editing and Navigation commands.
31819 <P>
31820 <End of help on this topic>
31821 </BODY>
31822 </HTML>
31823 ====== h_config_index_from_color =====
31824 <HTML>
31825 <HEAD>
31826 <TITLE>OPTION: Index From Color</TITLE>
31827 </HEAD>
31828 <BODY>
31829 <H1>OPTION: Index From Color</H1>
31831 You may set the color used to draw the From part of the index line.
31832 This coloring takes place for all but the current index line, and the From
31833 Color appears to be in front of any color from an Index Color Rule.
31834 <P>
31835 If you don't set this color it will be colored in the same color as
31836 the bulk of the index line.
31838 <P>
31839 <A HREF="h_color_setup">Descriptions of the available commands</A>
31840 <P>
31841 Look <A HREF="h_edit_nav_cmds">here</A>
31842 to see the available Editing and Navigation commands.
31843 <P>
31844 <End of help on this topic>
31845 </BODY>
31846 </HTML>
31847 ====== h_config_index_arrow_color =====
31848 <HTML>
31849 <HEAD>
31850 <TITLE>OPTION: Index Arrow Color</TITLE>
31851 </HEAD>
31852 <BODY>
31853 <H1>OPTION: Index Arrow Color</H1>
31855 If you have configured your
31856 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31857 to include the "ARROW" token, you may set the color of
31858 the arrow displayed with this option.
31859 If you don't set the color it will be colored in the same color as
31860 the bulk of the index line.
31862 <P>
31863 <A HREF="h_color_setup">Descriptions of the available commands</A>
31864 <P>
31865 Look <A HREF="h_edit_nav_cmds">here</A>
31866 to see the available Editing and Navigation commands.
31867 <P>
31868 <End of help on this topic>
31869 </BODY>
31870 </HTML>
31871 ====== h_config_index_color =====
31872 <HTML>
31873 <HEAD>
31874 <TITLE>OPTION: Index Colors</TITLE>
31875 </HEAD>
31876 <BODY>
31877 <H1>OPTION: Index Colors</H1>
31879 You may add color to the single character symbols that give the status
31880 of each message in the MESSAGE INDEX.
31881 By default the characters "+", "*", "D",
31882 "A", and "N" show up near the left hand side of the
31883 screen depending on whether the message is addressed to you, and whether
31884 the message is marked Important, is Deleted, is Answered, or is New.
31885 The color for each of those characters may be specified by setting the
31886 "Index-to-me" Symbol Color,
31887 the "Index-important" Symbol Color,
31888 the "Index-deleted" Symbol Color,
31889 the "Index-answered" Symbol Color,
31890 and the "Index-new" Symbol Color.
31891 There are also two other symbol colors called "Index-recent"
31892 and "Index-unseen".
31893 These two colors will only be used if you have configured your
31894 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31895 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
31896 <P>
31897 The default colors for these symbols are:
31898 <TABLE>
31899 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
31900 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
31901 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
31902 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
31903 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
31904 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
31905 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
31906 </TABLE>
31907 <P>
31908 Besides coloring the message status symbols, you may also color the
31909 entire index line.
31910 This is done by using the
31911 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
31912 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
31913 When the entire line is colored that color will be "behind" the
31914 status symbol colors talked about in the paragraph above.
31915 <P>
31916 You may also color
31917 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
31918 in the index using the
31919 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
31920 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
31921 the Subject using
31922 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
31923 the From field using
31924 <A HREF="h_config_index_from_color">Index From Color</A>;
31925 and the
31926 <A HREF="h_config_index_opening_color">Index Opening</A> text.
31927 <P>
31928 <A HREF="h_color_setup">Descriptions of the available commands</A>
31929 <P>
31930 Look <A HREF="h_edit_nav_cmds">here</A>
31931 to see the available Editing and Navigation commands.
31932 <P>
31933 <End of help on this topic>
31934 </BODY>
31935 </HTML>
31936 ====== h_config_metamsg_color =====
31937 <HTML>
31938 <HEAD>
31939 <TITLE>OPTION: Meta-Message Color</TITLE>
31940 </HEAD>
31941 <BODY>
31942 <H1>OPTION: Meta-Message Color</H1>
31944 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
31945 that aren't part of the message itself.
31946 For example, an attachment that isn't shown might produce a meta
31947 message something like:
31948 <P>
31949 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
31950 <P>
31951 If you set the
31952 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
31953 option you might see
31954 <P>
31955 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
31956 <P>
31957 Warnings about suspicious looking URLs in HTML will also be colored
31958 with this color.
31959 <P>
31960 The foreground color is the color of the actual character and the
31961 background color is the color of the area behind the character.
31962 By default, the Meta-Message Color is black characters on a yellow background.
31963 <P>
31964 <A HREF="h_color_setup">Descriptions of the available commands</A>
31965 <P>
31966 Look <A HREF="h_edit_nav_cmds">here</A>
31967 to see the available Editing and Navigation commands.
31968 <P>
31969 <End of help on this topic>
31970 </BODY>
31971 </HTML>
31972 ====== h_config_keylabel_color =====
31973 <HTML>
31974 <HEAD>
31975 <TITLE>OPTION: KeyLabel Color</TITLE>
31976 </HEAD>
31977 <BODY>
31978 <H1>OPTION: KeyLabel Color</H1>
31980 Sets the color Alpine uses for the labels of the keys in the two-line
31981 menu at the bottom of the screen.
31982 For example, some of the screens have a "P PrevMsg" command.
31983 This option sets the color used when displaying "PrevMsg".
31984 The foreground color is the color of the actual character and the
31985 background color is the color of the area behind the character.
31986 By default, the KeyLabel Color is the same as the Normal Color.
31987 <P>
31988 WARNING: Some terminal emulators have the property that the screen will scroll
31989 down one line whenever a character is written to the character cell in the
31990 lower right corner of the screen.
31991 Alpine can usually avoid writing a character in that corner of the screen.
31992 However, if you have defined a KeyLabel Color then Alpine does have to write
31993 a character in that cell in order to color the cell correctly.
31994 If you find that your display sometimes scrolls up a line this could be
31995 the problem.
31996 The most obvious symptom is probably that the titlebar at the top of the
31997 screen scrolls off the screen.
31998 Try setting KeyLabel Color to Default to see if that fixes the problem.
31999 <P>
32000 <A HREF="h_color_setup">Descriptions of the available commands</A>
32001 <P>
32002 Look <A HREF="h_edit_nav_cmds">here</A>
32003 to see the available Editing and Navigation commands.
32004 <P>
32005 <End of help on this topic>
32006 </BODY>
32007 </HTML>
32008 ====== h_config_keyname_color =====
32009 <HTML>
32010 <HEAD>
32011 <TITLE>OPTION: KeyName Color</TITLE>
32012 </HEAD>
32013 <BODY>
32014 <H1>OPTION: KeyName Color</H1>
32016 Sets the color Alpine uses for the names of the keys in the two-line
32017 menu at the bottom of the screen.
32018 For example, some of the screens have a "P PrevMsg" command.
32019 This option sets the color used when displaying the "P".
32020 The foreground color is the color of the actual character and the
32021 background color is the color of the area behind the character.
32022 By default, the KeyName Color is the same as the Reverse Color.
32023 <P>
32024 <A HREF="h_color_setup">Descriptions of the available commands</A>
32025 <P>
32026 Look <A HREF="h_edit_nav_cmds">here</A>
32027 to see the available Editing and Navigation commands.
32028 <P>
32029 <End of help on this topic>
32030 </BODY>
32031 </HTML>
32032 ====== h_config_slctbl_color =====
32033 <HTML>
32034 <HEAD>
32035 <TITLE>OPTION: Selectable Item Color</TITLE>
32036 </HEAD>
32037 <BODY>
32038 <H1>OPTION: Selectable Item Color</H1>
32040 Sets the color Alpine uses for selectable items, such as URLs.
32041 The foreground color is the color of the actual character and the
32042 background color is the color of the area behind the character.
32043 By default, the Selectable Item Color is the same as the Normal Color,
32044 except that it is bold.
32045 <P>
32046 <A HREF="h_color_setup">Descriptions of the available commands</A>
32047 <P>
32048 Look <A HREF="h_edit_nav_cmds">here</A>
32049 to see the available Editing and Navigation commands.
32050 <P>
32051 <End of help on this topic>
32052 </BODY>
32053 </HTML>
32054 ====== h_config_quote_color =====
32055 <HTML>
32056 <HEAD>
32057 <TITLE>OPTION: Quote Colors</TITLE>
32058 </HEAD>
32059 <BODY>
32060 <H1>OPTION: Quote Colors</H1>
32062 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
32063 screen.
32064 If a line begins with a > character (or space followed by >)
32065 it is considered a quote.
32066 That line will be given the Quote1 Color (first level quote).
32067 If there is a second level of quoting then the Quote2 Color will be used.
32068 Alpine considers there to be a second level of quoting if that first > is
32069 followed by another > (or space followed by >).
32070 If there are characters other than whitespace and > signs, then it isn't
32071 considered another level of quoting.
32072 Similarly, if there is a third level of quoting the Quote3 Color will be
32073 used.
32074 If there are more levels after that the Quote Colors are re-used.
32075 If you define all three colors then it would repeat like Color1, Color2, Color3,
32076 Color1, Color2, Color3, ...
32077 If you only define the first two it would be
32078 Color1, Color2, Color1, Color2, ...
32079 If you define only the Quote1 Color, then the entire quote would be that
32080 color regardless of the quoting levels.
32081 By default, the Quote1 Color is black characters on a greenish-blue background;
32082 the Quote2 Color is black characters on a dull yellow background; and
32083 the Quote3 Color is black characters on a green background.
32084 <P>
32085 <A HREF="h_color_setup">Descriptions of the available commands</A>
32086 <P>
32087 Look <A HREF="h_edit_nav_cmds">here</A>
32088 to see the available Editing and Navigation commands.
32089 <P>
32090 <End of help on this topic>
32091 </BODY>
32092 </HTML>
32093 ====== h_config_folder_color =====
32094 <HTML>
32095 <HEAD>
32096 <TITLE>OPTION: Folder Color</TITLE>
32097 </HEAD>
32098 <BODY>
32099 <H1>OPTION: Folder Color</H1>
32101 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
32102 screen. By default, the Folder Color is the normal text color.
32104 <P>
32105 If you set a color for this feature, other than the normal color
32106 (the default), or a color for
32107 <A HREF="h_config_directory_color">Directory Color</A>, then directories
32108 will be colored according to the color specified in the
32109 <A HREF="h_config_directory_color">Directory Color</A> option. In this
32110 case, the color will be the only indication that the colored name
32111 refers to a directory. The normal behavior is that Alpine
32112 indicates that a name refers to a directory by appending a
32113 separator (like "/" or ".") to the name of
32114 the folder.
32116 <P>
32117 If a folder is a directory, then the folder name will be painted
32118 according to the color defined by this variable, and a separator
32119 indicator (like "/" or ".") will be added
32120 to the name. That
32121 indicator will be painted according to the color defined in the
32122 <A HREF="h_config_directory_color">Directory Color</A> option.
32124 <P>
32125 <End of help on this topic>
32126 </BODY>
32127 </HTML>
32128 ====== h_config_directory_color =====
32129 <HTML>
32130 <HEAD>
32131 <TITLE>OPTION: Directory Color</TITLE>
32132 </HEAD>
32133 <BODY>
32134 <H1>OPTION: Directory Color</H1>
32136 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
32137 screen. By default, the Folder Color is the normal text color.
32138 <P>
32139 If you set a color for this feature, other than the normal color
32140 (the default), or a color for
32141 <A HREF="h_config_folder_color">Folder Color</A>, then folders
32142 will be colored according to the color specified in the
32143 <A HREF="h_config_folder_color">Folder Color</A> option. In this
32144 case, the color will be the only indication that the colored name
32145 refers to a directory. The normal behavior is that Alpine
32146 indicates that a name refers to a directory by appending a
32147 separator (like "/" or ".") to the name of
32148 the folder.
32149 <P>
32150 If a folder is a directory, then the folder name will be painted
32151 according to the color defined by the option
32152 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
32153 indicator (like "/" or ".") will be added
32154 after the name. That
32155 indicator will be painted according to the color defined in this
32156 option.
32157 <P>
32158 <End of help on this topic>
32159 </BODY>
32160 </HTML>
32161 ====== h_config_folder_list_color =====
32162 <HTML>
32163 <HEAD>
32164 <TITLE>OPTION: Folder-List Color</TITLE>
32165 </HEAD>
32166 <BODY>
32167 <H1>OPTION: Folder-List Color</H1>
32169 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
32170 screen. By default, the Folder-List Color is the normal text color.
32171 <P>
32172 This text refers to the informative text that Alpine displays so you
32173 can recognize each collection. The color of the content of each collection
32174 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
32175 and <A HREF="h_config_directory_color">Directory Color</A>.
32176 <P>
32177 Unlike the options
32178 <A HREF="h_config_folder_color">Folder Color</A>
32179 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
32180 this option does not affect the way that Alpine reports folders,
32181 directories and folders that are directories.
32182 <P>
32183 <End of help on this topic>
32184 </BODY>
32185 </HTML>
32186 ====== h_config_incunseen_color =====
32187 <HTML>
32188 <HEAD>
32189 <TITLE>OPTION: Incoming Unseen Color</TITLE>
32190 </HEAD>
32191 <BODY>
32192 <H1>OPTION: Incoming Unseen Color</H1>
32194 If the option
32195 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
32196 is turned on it is possible to highlight the folders that contain
32197 unseen messages by coloring them with this color.
32198 By default, this is the same as the Normal Color and no highlighting is done.
32199 <P>
32200 Usually the "current" folder (the folder the cursor is on)
32201 is highlighted using reverse video.
32202 If the current folder is colored because it contains unseen messages then
32203 the color used to show that it is also the current folder is controlled
32204 by the
32205 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
32206 feature at the top of the SETUP COLOR screen.
32207 <P>
32208 <A HREF="h_color_setup">Descriptions of the available commands</A>
32209 <P>
32210 Look <A HREF="h_edit_nav_cmds">here</A>
32211 to see the available Editing and Navigation commands.
32212 <P>
32213 <End of help on this topic>
32214 </BODY>
32215 </HTML>
32216 ====== h_config_signature_color =====
32217 <HTML>
32218 <HEAD>
32219 <TITLE>OPTION: Signature Color</TITLE>
32220 </HEAD>
32221 <BODY>
32222 <H1>OPTION: Signature Color</H1>
32224 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
32225 screen. According to USENET conventions, the signature is defined as the
32226 paragraph following the "sigdashes", that is, the special line
32227 consisting of the three characters
32228 "-- " (i.e., dash, dash, and space). Alpine allows for one
32229 empty line right after the sigdashes to be considered as part of the
32230 signature.
32231 By default, the Signature Color is blue characters on a white background.
32232 <P>
32233 <A HREF="h_color_setup">Descriptions of the available commands</A>
32234 <P>
32235 Look <A HREF="h_edit_nav_cmds">here</A>
32236 to see the available Editing and Navigation commands.
32237 <P>
32238 <End of help on this topic>
32239 </BODY>
32240 </HTML>
32241 ====== h_config_prompt_color =====
32242 <HTML>
32243 <HEAD>
32244 <TITLE>OPTION: Prompt Color</TITLE>
32245 </HEAD>
32246 <BODY>
32247 <H1>OPTION: Prompt Color</H1>
32249 Sets the color Alpine uses for confirmation prompts and questions that
32250 appear in the status line near the bottom of the screen.
32251 The foreground color is the color of the actual character and the
32252 background color is the color of the area behind the character.
32253 By default, the Prompt Color is the same as the Reverse Color.
32254 <P>
32255 <A HREF="h_color_setup">Descriptions of the available commands</A>
32256 <P>
32257 Look <A HREF="h_edit_nav_cmds">here</A>
32258 to see the available Editing and Navigation commands.
32259 <P>
32260 <End of help on this topic>
32261 </BODY>
32262 </HTML>
32263 ====== h_config_header_general_color =====
32264 <HTML>
32265 <HEAD>
32266 <TITLE>OPTION: Header General Color</TITLE>
32267 </HEAD>
32268 <BODY>
32269 <H1>OPTION: Header General Color</H1>
32271 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
32272 screen.
32273 The foreground color is the color of the actual character and the
32274 background color is the color of the area behind the character.
32275 By default, this is the same as the Normal Color.
32276 <P>
32277 It is also possible to set the colors for specific header fields, for
32278 example the Subject, using
32279 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
32280 If both a Header General Color and a specific Viewer Header Color are set
32281 the specific color will override the general color, as you would expect.
32282 <P>
32283 <A HREF="h_color_setup">Descriptions of the available commands</A>
32284 <P>
32285 Look <A HREF="h_edit_nav_cmds">here</A>
32286 to see the available Editing and Navigation commands.
32287 <P>
32288 <End of help on this topic>
32289 </BODY>
32290 </HTML>
32291 ====== h_config_incol =====
32292 <HTML>
32293 <HEAD>
32294 <TITLE>Index Line Color</TITLE>
32295 </HEAD>
32296 <BODY>
32297 <H1>Index Line Color</H1>
32299 This option is used to set the color of a line in the index when the
32300 message for that line matches the Pattern.
32301 This colors the whole index line, except possibly the status letters,
32302 which may be colored separately using the
32303 <A HREF="h_color_setup">Setup Kolor</A> screen.
32304 The foreground color is the color of the actual characters and the
32305 background color is the color of the area behind the characters.
32306 <P>
32307 <A HREF="h_color_setup">Descriptions of the available commands</A>
32308 <P>
32309 Look <A HREF="h_edit_nav_cmds">here</A>
32310 to see the available Editing and Navigation commands.
32311 <P>
32312 <End of help on this topic>
32313 </BODY>
32314 </HTML>
32315 ====== h_config_usetransparent_color =====
32316 <HTML>
32317 <HEAD>
32318 <TITLE>OPTION: Use Transparent Color</TITLE>
32319 </HEAD>
32320 <BODY>
32321 <H1>OPTION: Use Transparent Color</H1>
32323 This is a special color supported by some terminal emulators.
32324 It is intended to result in the default foreground or background color
32325 from the terminal emulator.
32326 This is the color the terminal was displaying characters in before you started Alpine.
32327 The reason it is called Transparent is because you could set the foreground color
32328 to some specific color, like Red, and then set the background color to the
32329 Transparent Color. If it works as expected, the background color from the terminal
32330 window in which Alpine is running will show through but with the Red characters
32331 in the foreground.
32332 <P>
32333 <A HREF="h_color_setup">Descriptions of the available commands</A>
32334 <P>
32335 Look <A HREF="h_edit_nav_cmds">here</A>
32336 to see the available Editing and Navigation commands.
32337 <P>
32338 <End of help on this topic>
32339 </BODY>
32340 </HTML>
32341 ====== h_config_usenormal_color =====
32342 <HTML>
32343 <HEAD>
32344 <TITLE>OPTION: Use Normal Color</TITLE>
32345 </HEAD>
32346 <BODY>
32347 <H1>OPTION: Use Normal Color</H1>
32349 When you use this color value, the actual color used will be the same
32350 as the corresponding Normal Color.
32351 For example if your Normal Color is black on white and you set both
32352 the foreground and background colors here to use the Normal Color, you'll
32353 get black on white. If you later change the Normal Color to red on blue
32354 this color will also change to red on blue.
32355 <P>
32356 <A HREF="h_color_setup">Descriptions of the available commands</A>
32357 <P>
32358 Look <A HREF="h_edit_nav_cmds">here</A>
32359 to see the available Editing and Navigation commands.
32360 <P>
32361 <End of help on this topic>
32362 </BODY>
32363 </HTML>
32364 ====== h_config_usenone_color =====
32365 <HTML>
32366 <HEAD>
32367 <TITLE>OPTION: Use None Color</TITLE>
32368 </HEAD>
32369 <BODY>
32370 <H1>OPTION: Use None Color</H1>
32372 This is a special color that simply means to leave the color alone.
32373 It is useful for Index symbols and for Keyword Colors used in the Subject
32374 field of an index line.
32375 The most likely use is to set an explicit foreground color and then set
32376 the background color to the None Color.
32377 That will cause the symbol or keyword to be drawn in the foreground color
32378 with a background equal to whatever color the rest of the index line is already
32379 drawn in.
32380 You will see no visible effect unless you have assigned Indexcolor Rules to
32381 color index lines or you have set an actual color for the Reverse Color.
32382 <P>
32383 <A HREF="h_color_setup">Descriptions of the available commands</A>
32384 <P>
32385 Look <A HREF="h_edit_nav_cmds">here</A>
32386 to see the available Editing and Navigation commands.
32387 <P>
32388 <End of help on this topic>
32389 </BODY>
32390 </HTML>
32391 ====== h_config_dflt_color =====
32392 <HTML>
32393 <HEAD>
32394 <TITLE>OPTION: Default Color</TITLE>
32395 </HEAD>
32396 <BODY>
32397 <H1>OPTION: Default Color</H1>
32399 Setting default will cause the color to be the default color.
32400 Unsetting default is normally done by choosing a color, but in some cases
32401 you may want to declare the current default color to be your non-default
32402 choice.
32403 For example, the default Keyname Color is the same as the Reverse Color.
32404 Whenever the Reverse Color changes the Keyname Color will also change, unless
32405 you've changed it or unset the default box.
32406 <P>
32407 <A HREF="h_color_setup">Descriptions of the available commands</A>
32408 <P>
32409 Look <A HREF="h_edit_nav_cmds">here</A>
32410 to see the available Editing and Navigation commands.
32411 <P>
32412 <End of help on this topic>
32413 </BODY>
32414 </HTML>
32415 ====== h_config_bold_slctbl =====
32416 <HTML>
32417 <HEAD>
32418 <TITLE>OPTION: Bold</TITLE>
32419 </HEAD>
32420 <BODY>
32421 <H1>OPTION: Bold</H1>
32423 The color for this particular section may have the Bold attribute turned
32424 on or off.
32425 Setting bold will cause the characters to be bold.
32426 <P>
32427 <A HREF="h_color_setup">Descriptions of the available commands</A>
32428 <P>
32429 Look <A HREF="h_edit_nav_cmds">here</A>
32430 to see the available Editing and Navigation commands.
32431 <P>
32432 <End of help on this topic>
32433 </BODY>
32434 </HTML>
32435 ====== h_config_kw_color =====
32436 <HTML>
32437 <HEAD>
32438 <TITLE>OPTION: Keyword Colors</TITLE>
32439 </HEAD>
32440 <BODY>
32441 <H1>OPTION: Keyword Colors</H1>
32443 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32444 Keywords are displayed as part of the Subject by default.
32445 They are also displayed as part of the Subject if the tokens
32446 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32447 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32448 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32449 screen by using the "KEY" or "KEYINIT" tokens.
32450 <P>
32451 For example, you might have set up a Keyword
32452 "Work" using the
32453 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32454 You could cause that Keyword to show up as a special color
32455 by setting up the Keyword Color using this option, and then including it
32456 in the MESSAGE INDEX screen using one of the tokens listed above in the
32457 <!--#echo var="VAR_index-format"-->.
32458 <P>
32459 <A HREF="h_color_setup">Descriptions of the available commands</A>
32460 <P>
32461 Look <A HREF="h_edit_nav_cmds">here</A>
32462 to see the available Editing and Navigation commands.
32463 <P>
32464 <End of help on this topic>
32465 </BODY>
32466 </HTML>
32467 ====== h_config_customhdr_color =====
32468 <HTML>
32469 <HEAD>
32470 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32471 </HEAD>
32472 <BODY>
32473 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32475 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32476 For example, you may set the color of the Subject header or the From header.
32477 The foreground color is the color of the actual character and the
32478 background color is the color of the area behind the character.
32479 <P>
32480 In addition to setting the colors for particular headers (like the Subject)
32481 you may also set a color to be used for all headers unless overridden by a
32482 more specific Viewer Header Color.
32483 To do this use the
32484 <A HREF="h_config_header_general_color">Header General Color</A>.
32485 <P>
32486 For Header Colors,
32487 there is an additional line on the
32488 screen labeled "Pattern to match".
32489 If you leave that blank, then the whole field for that header will
32490 be colored.
32491 However, if you give a pattern to match, the coloring will only take place
32492 if there is a match for that pattern in the value of the field.
32493 For example, if you are working on a color for the Subject header and
32494 you fill in a pattern of "important", then only Subjects that
32495 contain the word "important" will be colored.
32496 <P>
32497 If the pattern you enter is a comma-separated list of patterns, then coloring
32498 happens if any of those patterns matches.
32499 <P>
32500 <A HREF="h_color_setup">Descriptions of the available commands</A>
32501 <P>
32502 Look <A HREF="h_edit_nav_cmds">here</A>
32503 to see the available Editing and Navigation commands.
32504 <P>
32505 <End of help on this topic>
32506 </BODY>
32507 </HTML>
32508 ====== h_config_indextoken_color =====
32509 <HTML>
32510 <HEAD>
32511 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
32512 </HEAD>
32513 <BODY>
32514 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
32516 This option allows you to set up the color in which any token, not specified by the
32517 previous options, will be colored in the MESSAGE INDEX screen.
32518 <P>
32519 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
32520 a token that can be used in the index format.
32521 The list of available tokens is <A HREF="h_index_tokens">here</A>.
32522 <P>
32523 If you fail to enter a valid token your entry will be ignored, and you will be asked to
32524 enter a new one. Once you have entered a valid token, a line will be added to the
32525 configuration screen that you can use to set up the colors in which that token will
32526 be painted. This is done in the same way that you configure colors for other
32527 variables.
32529 <A HREF="h_color_setup">Descriptions of the available commands</A>
32530 <P>
32531 Look <A HREF="h_edit_nav_cmds">here</A>
32532 to see the available Editing and Navigation commands.
32533 <P>
32534 <End of help on this topic>
32535 </BODY>
32536 </HTML>
32537 ====== h_config_customhdr_pattern =====
32538 <HTML>
32539 <HEAD>
32540 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
32541 </HEAD>
32542 <BODY>
32543 <H1>OPTION: Viewer Header Color Pattern</H1>
32545 If you leave this blank, then the whole field for the header will
32546 be colored.
32547 If you give a pattern to match, the coloring will only take place
32548 if there is a match for that pattern in the value of the field.
32549 For example, if you are working on a color for the Subject header and
32550 you fill in a pattern of "important", then only Subjects that
32551 contain the word "important" will be colored.
32552 <P>
32553 For address headers (like From and To) and for the Newsgroups header,
32554 a pattern match will cause only the matched addresses or newsgroups to be
32555 colored.
32556 If there is no pattern to match, then all of the addresses or newsgroups
32557 in the relevant header will be colored.
32558 <P>
32559 The matching pattern may be a comma-separated list of patterns to match
32560 instead of a single pattern.
32561 For example, you could use the pattern "important,urgent" which would
32562 cause a match if either the word "important" or the word
32563 "urgent" appeared in the value of the header.
32564 You could list several comma-separated email addresses in the Header
32565 From Color pattern so that those addresses will be colored when any of
32566 them appear in the From header.
32567 <P>
32568 To add a new matching pattern or change the existing pattern use the
32569 <!--chtml if pinemode="function_key"-->
32570 "F4"
32571 <!--chtml else-->
32572 "C"
32573 <!--chtml endif-->
32574 "Change" command that is available when the "Pattern to
32575 match" line is highlighted.
32576 The
32577 <!--chtml if pinemode="function_key"-->
32578 "F10"
32579 <!--chtml else-->
32580 "D"
32581 <!--chtml endif-->
32582 "Delete" command may be used to quickly remove all patterns
32583 for a particular header.
32584 <P>
32585 <End of help on this topic>
32586 </BODY>
32587 </HTML>
32588 ====== h_color_setup =====
32589 <HTML>
32590 <HEAD>
32591 <TITLE>SETUP COLOR COMMANDS</TITLE>
32592 </HEAD>
32593 <BODY>
32594 <H1>SETUP COLOR COMMANDS</H1>
32595 <!--chtml if pinemode="function_key"-->
32596 <PRE>
32597 Available Commands -- Group 1
32598 -------------------------------
32599 F1 Display this help text
32600 F2 Show other available commands
32601 F3 Exit to MAIN MENU
32602 F4 Select the highlighted foreground or background color
32603 F5 Move to previous line
32604 F6 Move to next line
32605 F7 Previous page
32606 F8 Next page
32607 F9 Add a config section for a header field
32608 F10 Restore all default colors (for all sections)
32609 F11 Print color configuration screen
32610 F12 Whereis (search for word)
32612 Available Commands -- Group 2
32613 -------------------------------
32614 F1 Display this help text
32615 F2 Show other available commands
32616 F5 Delete config section for highlighted header field
32617 F6 Shuffle the order of Header Color sections
32618 </PRE>
32619 <!--chtml else-->
32620 <PRE>
32621 General commands
32622 -------------------------------------------------
32623 ? Display this help text E Exit back to MAIN MENU
32624 P Previous Line N Next Line
32625 - Previous page Spc (space bar) Next page
32626 W WhereIs (search for word) % Print color configuration screen
32628 Color Setup Commands
32629 ------------------------------------------------
32630 * Select the highlighted foreground or background color
32631 A Add a config section for a header field
32632 D Delete config section for highlighted header field
32633 R Restore all default colors (for all sections)
32634 $ Shuffle the order of Header Color sections
32635 </PRE>
32636 <!--chtml endif-->
32638 <H2>Description of the Setup Color Screen</H2>
32640 From this screen you may turn on color and set the colors of
32641 various parts of the Alpine display.
32642 For help on turning on color move your cursor into the Color Style section
32643 at the top of the Setup Color screen and ask for help.
32645 <P>
32646 There are several sections in the Setup Color Screen.
32647 At the top are some settings that handle the style of color used
32648 with your terminal emulator (UNIX only), and some settings that
32649 control how the current indexline and the titlebar are colored.
32650 After that comes a long section called GENERAL COLORS that allows
32651 you to set the color of many elements in the Alpine screens.
32652 For example, the color of the titlebar, status messages,
32653 selectable links, quotes and signatures in messages, and so on.
32654 After that is a section called INDEX COLORS that allows you to
32655 set the colors of various pieces of the displayed index lines in
32656 the MESSAGE INDEX screen.
32657 The next section is HEADER COLORS. This is for coloring headers of
32658 messages in the MESSAGE TEXT screen in just about any way you would like.
32659 Finally, the KEYWORD COLORS section allows you to highlight
32660 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32661 in the MESSAGE INDEX screen.
32663 <P>
32664 To change a color, highlight the color you want to change (for example,
32665 the Status Color) by moving
32666 the cursor into it.
32667 You may want to read the help text for the color to see a brief desription
32668 of what you are coloring.
32669 Then press "C" for Change to set the color to something new.
32670 That will put you into a screen with two columns of colors, one for
32671 the foreground color and one for the background color.
32672 The foreground color is just the color you want the actual characters
32673 to be and the background color is the color of the rest of the rectangle
32674 behind the characters.
32675 Select the foreground and background colors desired by using the Next and
32676 Prev keys to highlight the color, and the * command to select it.
32677 <P>
32678 To set a color to its default value, set the X in the Default line at
32679 the bottom of the list of colors.
32680 <P>
32682 The HEADER COLORS section is a little bit different from the others.
32683 Besides coloring the specific fields that Alpine knows about, you may also
32684 color specific header fields when viewing a message in the MESSAGE TEXT
32685 screen.
32686 For example, you may color the Subject header a particular color.
32687 There are a few commands for use with headers.
32688 The "AddHeader" command adds a section to the color
32689 configuration screen that allows you to set the color for that header.
32690 You'll be asked for the name of the header field you want to color.
32691 If you wanted to color the Subject, you would answer
32692 with the word "subject".
32693 Once you've added a header field, the color setting works just like the
32694 other color fields, except that there is an additional line on the
32695 configuration screen labeled "Pattern to match".
32696 If you leave that blank, then the whole field for that header will always
32697 be colored.
32698 However, if you give a pattern to match, the coloring will only take place
32699 if there is a match for that pattern in the value of the field.
32700 For example, if you are working on a color for the Subject header and
32701 you fill in a pattern of "important", then only Subjects that
32702 contain the word "important" will be colored.
32703 <P>
32704 The "DeleteHdr" command removes a header section from the
32705 configuration altogether.
32706 The "Shuffle" command changes the order of header sections.
32707 This is only necessary if you use header sections with pattern fields.
32708 For example, if you have two Subject sections, one with one pattern and
32709 another with another pattern, and the subject for a particular message
32710 happens to match both, then the color from the first match is used.
32711 <P>
32713 The command "RestoreDefs" will restore all of the default colors.
32714 Each section will change to the default value used for that section when
32715 color is first enabled.
32716 When you restore all default colors the color settings for the Header Colors
32717 will be unset (since that's the default), but the header fields you've
32718 added will remain so that you may easily reset them.
32719 In order to get rid of them completely you'd have to use
32720 the "DeleteHdr" command.
32722 <P>
32723 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
32724 may be set with matching rules and that is configured separately from
32725 the rest of the color settings described here.
32726 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
32727 instead of in the Setup/Kolor section.
32729 <P><UL>
32730 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32731 </UL><P>
32732 <End of help on this topic>
32733 </BODY>
32734 </HTML>
32735 ====== h_config_news_uses_recent ======
32736 <HTML>
32737 <HEAD>
32738 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
32739 </HEAD>
32740 <BODY>
32741 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
32743 This feature causes certain messages to be marked as "New" in the
32744 MESSAGE INDEX of newsgroups.
32745 This feature is set by default.
32747 <P>
32749 When opening a newsgroup, Alpine will consult your "newsrc" file and
32750 determine the last message you have previously disposed of via the "D"
32751 key. If this feature is set, any subsequent messages will be shown in the
32752 Index with an "N", and the first of these messages will be highlighted.
32753 Although this is only an approximation of true "New" or "Unseen"
32754 status, it provides a useful cue to distinguish more-or-less recent
32755 messages from those you have seen previously, but are not yet ready to
32756 mark deleted.
32758 <P>
32760 Background: your "newsrc" file (used to store message status information
32761 for newsgroups) is only capable of storing a single flag, and Alpine uses
32762 this to record whether or not you are "done with" a message, as
32763 indicated by marking the message as "Deleted". Unfortunately, this
32764 means that Alpine has no way to record exactly which messages you have
32765 previously seen, so it normally does not show the "N" status flag for
32766 any messages in a newsgroup. This feature enables a starting
32767 *approximation* of seen/unseen status that may be useful.
32768 <P>
32769 <End of help on this topic>
32770 </BODY>
32771 </HTML>
32772 ====== h_config_expose_hidden_config =====
32773 <HTML>
32774 <HEAD>
32775 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
32776 </HEAD>
32777 <BODY>
32778 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
32780 If set, this causes configuration options and features that are normally
32781 hidden from view to be editable in the Setup/Config screen.
32783 <P>
32784 The purpose of this feature is to allow you to change configuration
32785 features and variables that are normally hidden.
32786 This is particularly useful if you are using a remote configuration,
32787 where it is difficult to edit the contents manually, but it may also be used
32788 on a local pinerc configuration file.
32789 <P>
32790 If set, several configuration variables and features that are normally
32791 hidden from view will show up in the Setup/Configuration screen.
32792 They will be at the bottom of the configuration screen.
32793 You can find them by searching for the words "hidden configuration".
32794 <P>
32796 Note that this is an advanced feature that should be used with care.
32797 The reason that this part of the configuration is normally hidden is because
32798 there is a significant potential for causing problems if you change these
32799 variables.
32800 If something breaks after a change try changing it back to see if that is
32801 what is causing the problem.
32802 There are also some variables that are normally hidden because they are
32803 manipulated through Alpine in other ways.
32804 For example, colors are normally set using the Setup/Kolors screen and
32805 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
32806 the Setup/AddressBooks screen, so there is little reason to edit these directly.
32807 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
32808 the Add, Delete, and Rename commands in the FOLDER LIST screen,
32809 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
32810 internally by Alpine and not set directly by the user.
32811 <P>
32812 <UL>
32813 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32814 </UL><P>
32815 <End of help on this topic>
32816 </BODY>
32817 </HTML>
32818 ====== h_config_disable_signature_edit =====
32819 <HTML>
32820 <HEAD>
32821 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
32822 </HEAD>
32823 <BODY>
32824 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
32826 If set, this disables the editing of signature files from within
32827 the Setup/Config screen.
32828 <P>
32829 <UL>
32830 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32831 </UL><P>
32832 <End of help on this topic>
32833 </BODY>
32834 </HTML>
32835 ====== h_config_disable_roles_templateedit =====
32836 <HTML>
32837 <HEAD>
32838 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
32839 </HEAD>
32840 <BODY>
32841 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
32843 If set, this disables the editing of template files within the
32844 Role setup screen.
32845 <P>
32846 <UL>
32847 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32848 </UL><P>
32849 <End of help on this topic>
32850 </BODY>
32851 </HTML>
32852 ====== h_config_disable_roles_sigedit =====
32853 <HTML>
32854 <HEAD>
32855 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
32856 </HEAD>
32857 <BODY>
32858 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
32860 If set, this disables the editing of signature files within the
32861 Role setup screen.
32862 <P>
32863 <UL>
32864 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32865 </UL><P>
32866 <End of help on this topic>
32867 </BODY>
32868 </HTML>
32869 ====== h_config_disable_roles_setup =====
32870 <HTML>
32871 <HEAD>
32872 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
32873 </HEAD>
32874 <BODY>
32875 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
32877 If set, this disables the Setup/Rules/Roles command.
32878 <P>
32879 <UL>
32880 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32881 </UL><P>
32882 <End of help on this topic>
32883 </BODY>
32884 </HTML>
32885 ====== h_config_disable_pipes_in_templates =====
32886 <HTML>
32887 <HEAD>
32888 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
32889 </HEAD>
32890 <BODY>
32891 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
32893 By default, if a template file name is followed by a vertical bar (|) then
32894 that causes the file to be executed to produce the text for the template.
32895 If this feature is set, then this is not allowed.
32896 <P>
32897 <UL>
32898 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32899 </UL><P>
32900 <End of help on this topic>
32901 </BODY>
32902 </HTML>
32903 ====== h_config_disable_pipes_in_sigs =====
32904 <HTML>
32905 <HEAD>
32906 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
32907 </HEAD>
32908 <BODY>
32909 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
32911 By default, if a signature file name is followed by a vertical bar (|) then
32912 that causes the file to be executed to produce the text for the signature.
32913 If this feature is set, then this is not allowed.
32914 <P>
32915 <UL>
32916 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32917 </UL><P>
32918 <End of help on this topic>
32919 </BODY>
32920 </HTML>
32921 ====== h_config_disable_password_cmd =====
32922 <HTML>
32923 <HEAD>
32924 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
32925 </HEAD>
32926 <BODY>
32927 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
32929 If set, then the Setup/Newpassword command is disabled.
32930 <P>
32931 <UL>
32932 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32933 </UL><P>
32934 <End of help on this topic>
32935 </BODY>
32936 </HTML>
32937 ====== h_config_disable_password_caching =====
32938 <HTML>
32939 <HEAD>
32940 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
32941 </HEAD>
32942 <BODY>
32943 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
32945 Normally, loginname/password combinations are cached in Alpine so that
32946 you do not have to enter the same password more than once in a session.
32947 A disadvantage to this approach is that the password must be stored in
32948 the memory image of the running Alpine in order that it can be re-used.
32949 In the event that Alpine crashes and produces a core dump, and that core
32950 dump is readable by others, the loginname and password could be read
32951 from the core dump.
32952 <P>
32953 If this feature is set, then the passwords will not be cached and you
32954 will have to retype the password whenever Alpine needs it.
32955 Even with this feature set there is still some chance that the core
32956 file will contain a password, so care should be taken to make the
32957 core files unreadable.
32958 <P>
32959 NOTE: If PASSFILE caching is enabled, this does not disable it.
32960 That is a separate and independent feature.
32961 <UL>
32962 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32963 </UL><P>
32964 <End of help on this topic>
32965 </BODY>
32966 </HTML>
32967 ====== h_config_disable_password_file_saving =====
32968 <HTML>
32969 <HEAD>
32970 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE>
32971 </HEAD>
32972 <BODY>
32973 <H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1>
32975 This feature changes the behavior of Alpine when a login name and password combination
32976 for a specific server is not found in the password file. The default behavior is that
32977 Alpine will ask the user if they wish to save this information in the password file for future
32978 use. It is assumed that if a user created a password file it is because they intend
32979 to use it, but in some instances a user might want to save some passwords and not others.
32980 In this case, enabling this feature will make Alpine not add any more passwords to the
32981 password file and will only use the passwords that it already saved. If you wish to allow
32982 Alpine to save more passwords in the password file, disable this feature.
32983 <P>
32984 <UL>
32985 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32986 </UL><P>
32987 <End of help on this topic>
32988 </BODY>
32989 </HTML>
32990 ====== h_config_disable_kb_lock =====
32991 <HTML>
32992 <HEAD>
32993 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
32994 </HEAD>
32995 <BODY>
32996 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
32998 If set, then the Keyboard Lock command is removed from the MAIN MENU.
32999 <P>
33000 <UL>
33001 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33002 </UL><P>
33003 <End of help on this topic>
33004 </BODY>
33005 </HTML>
33006 ====== h_config_disable_config_cmd =====
33007 <HTML>
33008 <HEAD>
33009 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
33010 </HEAD>
33011 <BODY>
33012 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
33014 If set, then the Setup/Config screen is disabled.
33015 <P>
33016 <UL>
33017 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33018 </UL><P>
33019 <End of help on this topic>
33020 </BODY>
33021 </HTML>
33022 ====== h_config_allow_chg_from =====
33023 <HTML>
33024 <HEAD>
33025 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
33026 </HEAD>
33027 <BODY>
33028 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
33030 This feature affects Alpine's handling of the "From:" header field
33031 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
33032 option.
33033 <P>
33034 If this feature is set then the From line can be changed just like
33035 all the other header fields that can be changed.
33036 This feature defaults to <EM>ON</EM>.
33037 <P>
33038 Even with this feature turned ON (the default) you will not be able
33039 to change the From header unless you add it to your list of
33040 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
33041 You may also want to change the
33042 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
33043 if you want the From header to always show up in the composer without
33044 having to type the Rich Headers command first.
33045 <P>
33046 Note that many sites restrict the use of this feature in order to
33047 reduce the chance of falsified addresses and misdirected mail.
33048 If you want to change the value of what gets included in the From header
33049 in messages you send
33050 look <A HREF="h_config_change_your_from">here</A> for a description.
33051 <P>
33052 <UL>
33053 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33054 </UL><P>
33055 <End of help on this topic>
33056 </BODY>
33057 </HTML>
33058 ====== h_config_disable_collate =====
33059 <HTML>
33060 <HEAD>
33061 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
33062 </HEAD>
33063 <BODY>
33064 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
33066 This is a hard to understand feature that should only be used in rare cases.
33067 Normally, the C function call
33068 <P>
33069 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
33070 <P>
33071 is used by Alpine.
33072 If you want to try turning it off,
33073 setting this feature will turn it off.
33074 This part of the locale has to do with the sort order
33075 of characters in your locale.
33076 <P>
33077 <UL>
33078 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33079 </UL><P>
33080 <End of help on this topic>
33081 </BODY>
33082 </HTML>
33083 ====== h_config_quell_attach_extra_prompt =====
33084 <HTML>
33085 <HEAD>
33086 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
33087 </HEAD>
33088 <BODY>
33089 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
33091 By default, when you attempt to view an attachment externally
33092 from the "Attachment View" screen, you are asked if you
33093 really want to view the selected attachment.
33095 <P>
33096 If this feature is set, you will <B>not</B> be prompted to confirm
33097 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
33098 prompt. This feature was added for those wanting to preserve that
33099 behavior (along with
33100 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
33102 <P>
33103 <UL>
33104 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33105 </UL><P>
33106 <End of help on this topic>
33107 </BODY>
33108 </HTML>
33109 ====== h_config_quell_attach_ext_warn =====
33110 <HTML>
33111 <HEAD>
33112 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
33113 </HEAD>
33114 <BODY>
33115 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
33117 <P>
33118 This feature suppresses the extra warning you can get when trying
33119 to view an attachment for which there is no mime-type match. Turning
33120 on this feature will just run the program according to extension
33121 instead of first warning the user that it will run according to the
33122 file's extension.
33123 <P>
33124 This feature can be used along side
33125 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
33126 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
33127 <P>
33128 <UL>
33129 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33130 </UL><P>
33131 <End of help on this topic>
33132 </BODY>
33133 </HTML>
33134 ====== h_config_mailcap_params =====
33135 <HTML>
33136 <HEAD>
33137 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
33138 </HEAD>
33139 <BODY>
33140 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
33142 If set, this will allow mailcap named parameter substitution to occur
33143 in mailcap entries.
33144 By default, this is turned off to prevent security problems that may occur
33145 with some incorrect mailcap configurations.
33146 For more information, see RFC1524 and look for "named parameters" in the
33147 text of the RFC.
33148 <P>
33149 <UL>
33150 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33151 </UL><P>
33152 <End of help on this topic>
33153 </BODY>
33154 </HTML>
33155 ====== h_config_disable_shared =====
33156 <HTML>
33157 <HEAD>
33158 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
33159 </HEAD>
33160 <BODY>
33161 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
33163 If this feature is set, the automatic search for namespaces "ftp",
33164 "imapshared", and "imappublic" by the underlying library
33165 will be disabled.
33166 The reason this feature exists is because there are some implementations
33167 of system password lookup routines that are very slow when presented with
33168 a long loginname that does not exist.
33169 This feature could be set to prevent the delay at startup time when the
33170 names above are searched for in the password file.
33171 <P>
33172 <UL>
33173 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33174 </UL><P>
33175 <End of help on this topic>
33176 </BODY>
33177 </HTML>
33178 ====== h_config_hide_nntp_path =====
33179 <HTML>
33180 <HEAD>
33181 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
33182 </HEAD>
33183 <BODY>
33184 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
33186 Normally the Path header that Alpine generates when posting to a newsgroup
33187 contains the name of the computer from which the message is being sent and
33188 the user name.
33189 Some believe that this information is used by spammers.
33190 If this feature is set, that information will be replaced with the text
33191 <P>
33192 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
33193 <P>
33194 instead.
33195 <P>
33196 It should be noted that many servers being connected to will still reveal
33197 the information that this feature attempts to protect.
33198 <P>
33199 <UL>
33200 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33201 </UL><P>
33202 <End of help on this topic>
33203 </BODY>
33204 </HTML>
33205 ====== h_config_no_bezerk_zone =====
33206 <HTML>
33207 <HEAD>
33208 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
33209 </HEAD>
33210 <BODY>
33211 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
33213 POSIX mandates a timezone in UNIX mailbox format folder delimiters
33214 (the line that begins with From <SPACE>).
33215 Some versions of Berkeley mail have trouble with this, and don't recognize
33216 the line as a message delimiter.
33217 If this feature is set, the timezone will be left off the delimiter line.
33218 <P>
33219 <UL>
33220 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33221 </UL><P>
33222 <End of help on this topic>
33223 </BODY>
33224 </HTML>
33225 ====== h_config_quell_domain_warn =====
33226 <HTML>
33227 <HEAD>
33228 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
33229 </HEAD>
33230 <BODY>
33231 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
33233 When your configuration is set up so that your domain name contains no dots,
33234 it is usually a configuration error.
33235 By default, Alpine will warn you about this when you start it up.
33236 You will see a warning message that looks like
33238 <P>
33239 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
33241 <P>
33242 If this feature is set, the warning is turned off.
33243 <P>
33244 <UL>
33245 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33246 </UL><P>
33247 <End of help on this topic>
33248 </BODY>
33249 </HTML>
33250 ====== h_config_quell_imap_env =====
33251 <HTML>
33252 <HEAD>
33253 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
33254 </HEAD>
33255 <BODY>
33256 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
33258 In the MESSAGE INDEX screen, if the open folder is being accessed
33259 using IMAP, Alpine normally tries to paint the index lines on the screen
33260 as soon as the information arrives from the IMAP server.
33261 This means that the index information makes it onto the screen more quickly
33262 than it otherwise would.
33263 This sometimes results in behavior that bothers some users.
33264 For example, when paging to a new page of the index, it may be possible for
33265 the lines to be painted on the screen in a random order, rather than from
33266 top to bottom.
33267 <P>
33269 Setting this feature causes Alpine to wait for all of the information
33270 to be gathered before it paints the index screen.
33271 Once it collects all of the information, the screen will be painted quickly
33272 from top to bottom.
33273 <P>
33274 <UL>
33275 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33276 </UL><P>
33277 <End of help on this topic>
33278 </BODY>
33279 </HTML>
33280 ====== h_config_quell_news_env =====
33281 <HTML>
33282 <HEAD>
33283 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
33284 </HEAD>
33285 <BODY>
33286 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
33288 In the MESSAGE INDEX screen, if the open folder is being accessed
33289 using NNTP (News), Alpine normally tries to paint the index lines on the screen
33290 as soon as the information arrives from the NNTP server.
33291 This means that the index information makes it onto the screen more quickly
33292 than it otherwise would.
33293 This sometimes results in behavior that bothers some users.
33294 For example, when paging to a new page of the index, it may be possible for
33295 the lines to be painted on the screen in a random order, rather than from
33296 top to bottom.
33297 <P>
33299 Setting this feature causes Alpine to wait for all of the information
33300 to be gathered before it paints the index screen.
33301 Once it collects all of the information, the screen will be painted quickly
33302 from top to bottom.
33303 <P>
33304 <UL>
33305 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33306 </UL><P>
33307 <End of help on this topic>
33308 </BODY>
33309 </HTML>
33310 ====== h_config_quell_content_id =====
33311 <HTML>
33312 <HEAD>
33313 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
33314 </HEAD>
33315 <BODY>
33316 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
33318 This feature changes the behavior of Alpine when sending messages.
33319 It is intended to work around a bug in Microsoft's Outlook XP mail user
33320 agent.
33321 As of this writing, Microsoft has acknowledged the bug but
33322 has not added it to the Knowledge Base.
33323 We have been told that there will be a post-SP1 hotfix for Outlook XP.
33324 This particular bug has bug fix number OfficeQFE:4781.
33325 The nature of the bug is that messages with attachments that
33326 contain a Content-ID header (which standard Alpine attachments do)
33327 do not show the attachment indicator (a paperclip) when viewed with
33328 Outlook XP.
33329 So the user has no indication that the message contains an attachment.
33331 <P>
33332 If this feature is set then Alpine will remove most Content-ID headers
33333 before sending a message.
33334 If an attachment is of type MESSAGE, then the existing Content-ID headers
33335 inside the message will be left intact.
33336 This would only happen with Alpine if a message was forwarded as an attachment
33337 or if a message with a message attached was forwarded.
33338 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
33339 the Content-ID headers of the alternative parts will not be removed.
33341 <P>
33342 Because the Content-ID header is a standard part of MIME it is possible
33343 that setting this feature will break something.
33344 For example, if an attachment has a Content-ID header that is necessary
33345 for the correct functioning of that attachment, it is possible that Alpine
33346 may remove that header when the attachment is forwarded.
33347 However, it seems fairly safe at this time.
33349 <P>
33350 <UL>
33351 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33352 </UL><P>
33353 <End of help on this topic>
33354 </BODY>
33355 </HTML>
33356 ====== h_config_winpos_in_config =====
33357 <HTML>
33358 <HEAD>
33359 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
33360 </HEAD>
33361 <BODY>
33362 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
33364 PC-Alpine only.
33365 <P>
33367 Normally, PC-Alpine will store its window size and position in the
33368 Windows Registry.
33369 This is convenient if you want to use the same remote
33370 configuration from more than one PC.
33371 If you use multiple configuration files to start PC-Alpine, you may want
33372 to store the window size and position in the configuration file instead
33373 of in the Registry.
33374 Setting this feature causes the value to be stored in
33375 <A HREF="h_config_window_position">Window-Position</A>.
33377 <P>
33378 <UL>
33379 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33380 </UL><P>
33381 <End of help on this topic>
33382 </BODY>
33383 </HTML>
33384 ====== h_config_quell_ssl_largeblocks =====
33385 <HTML>
33386 <HEAD>
33387 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
33388 </HEAD>
33389 <BODY>
33390 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
33392 PC-Alpine only.
33393 <P>
33394 This feature changes the behavior of fetching messages
33395 and attachments so that the message data is fetched in chunks no larger
33396 than 12K bytes.
33397 This works around a bug in Microsoft's SSL/TLS support.
33398 Some versions of Microsoft SSL are not able to read full-sized (16K)
33399 SSL/TLS packets.
33400 Some servers will send such packets and this will
33401 cause PC-Alpine to crash with the error
33403 <P>
33404 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
33406 <P>
33407 Microsoft is aware of the problem and has developed a hotfix for it, it is
33408 discussed in article 300562 in the Microsoft Knowledge Base.
33409 <P>
33410 <UL>
33411 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33412 </UL><P>
33413 <End of help on this topic>
33414 </BODY>
33415 </HTML>
33416 ====== h_config_quell_partial =====
33417 <HTML>
33418 <HEAD>
33419 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
33420 </HEAD>
33421 <BODY>
33422 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
33424 Partial fetching is a feature of the IMAP protocol.
33425 By default, Alpine
33426 will use partial fetching when copying the contents of a message or attachment
33427 from the IMAP server to Alpine.
33428 This means that the fetch will be done in many
33429 small chunks instead of one big chunk. The main benefit of this approach is
33430 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33431 to stop the fetch early. In some cases partial fetching may cause a performance
33432 problem so that the fetching of data takes significantly longer when partial
33433 fetching is used. Turning on this feature will turn off partial fetching.
33434 <P>
33435 <UL>
33436 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33437 </UL><P>
33438 <End of help on this topic>
33439 </BODY>
33440 </HTML>
33441 ====== h_config_quell_personal_name_prompt =====
33442 <HTML>
33443 <HEAD>
33444 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33445 </HEAD>
33446 <BODY>
33447 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33449 PC-Alpine only. This feature quells the prompting for a
33450 <A HREF="h_config_pers_name">personal name</A>. This
33451 prompt normally happens before composing a message, and only happens when
33452 there is no personal name already set.
33453 <P>
33454 <UL>
33455 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33456 </UL><P>
33457 <End of help on this topic>
33458 </BODY>
33459 </HTML>
33460 ====== h_config_quell_user_id_prompt =====
33461 <HTML>
33462 <HEAD>
33463 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33464 </HEAD>
33465 <BODY>
33466 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33468 PC-Alpine only. This feature quells the prompting for a
33469 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33470 if the information can be obtained from the login name used
33471 to open the INBOX. Normally, this prompt happens before composing
33472 a message, and only happens when there is no user-id already set
33473 in the configuration.
33474 <P>
33475 With this feature set, composing a message is only possible after
33476 establishing a connection to the INBOX.
33477 <P>
33478 <UL>
33479 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33480 </UL><P>
33481 <End of help on this topic>
33482 </BODY>
33483 </HTML>
33484 ====== h_config_save_aggregates =====
33485 <HTML>
33486 <HEAD>
33487 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33488 </HEAD>
33489 <BODY>
33490 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33492 This feature will optimize an aggregate copy operation, if
33493 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33494 list of the messages to be copied.
33495 This feature is set by default.
33496 This may reduce network traffic and elapsed time for the Save.
33497 <EM>However, many IMAP servers (including the UW IMAP server) do
33498 not preserve the order of messages when this optimization is applied.</EM>
33499 If this feature is not set,
33500 Alpine will copy each message individually and the order of the messages
33501 will be preserved.
33502 <P>
33503 <UL>
33504 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33505 </UL><P>
33506 <End of help on this topic>
33507 </BODY>
33508 </HTML>
33509 ====== h_config_use_system_translation =====
33510 <HTML>
33511 <HEAD>
33512 <TITLE>FEATURE: Use System Translation</TITLE>
33513 </HEAD>
33514 <BODY>
33515 <H1>FEATURE: Use System Translation</H1>
33517 UNIX Alpine only.
33518 <P>
33519 Alpine normally uses its own internal software to convert between the multi-byte
33520 representation of characters and the Unicode representation of those
33521 same characters.
33522 It converts from the multi-byte characters your keyboard produces to Unicode,
33523 and from Unicode to the multi-byte characters your display expects.
33524 Alpine also uses its own internal software to decide how much space on
33525 the screen a particular Unicode character will occupy.
33527 <P>
33528 Setting this feature tells Alpine to use the system-supplied routines to
33529 perform these tasks instead.
33530 In particular there are three tasks and three system routines that will
33531 be used for these tasks.
33533 <P>
33534 To convert from multi-byte to Unicode the routine
33536 <P>
33537 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
33538 <P>
33540 is used.
33541 To convert from Unicode to multi-byte the routine
33543 <P>
33544 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
33545 <P>
33547 is used.
33548 And to find the screen width a particular Unicode character will
33549 occupy the routine used is
33551 <P>
33552 <CENTER><SAMP>wcwidth</SAMP></CENTER>
33553 <P>
33555 This feature has been only lightly tested.
33556 The internal routines should normally be used unless you run into
33557 a problem that you think may be solved by using the system routines.
33558 Note that your environment needs to be set up for these
33559 routines to work correctly.
33560 In particular, the LANG or LC_CTYPE variable in your environment will
33561 need to be set.
33563 <P>
33564 <UL>
33565 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33566 </UL><P>
33567 <End of help on this topic>
33568 </BODY>
33569 </HTML>
33570 ====== h_config_suspend_spawns =====
33571 <HTML>
33572 <HEAD>
33573 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
33574 </HEAD>
33575 <BODY>
33576 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
33578 This feature affects Alpine's behavior when process suspension is enabled
33579 and then activated via the Ctrl-Z key. Alpine suspension allows one to
33580 temporarily interact with the operating system command "shell"
33581 without
33582 quitting Alpine, and then subsequently resume the still-active Alpine session.
33583 <P>
33585 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
33586 is set and subsequently the Ctrl-Z key
33587 is pressed, Alpine will normally suspend itself and return temporary control
33588 to Alpine's parent shell process. However, if this feature is set, Alpine
33589 will instead create an inferior subshell process. This is useful when the
33590 parent process is not intended to be used interactively. Examples include
33591 invoking Alpine via the -e argument of the Unix "xterm" program,
33592 or via a menu system.<P>
33594 Note that one typically resumes a suspended Alpine by entering the Unix
33595 "fg" command, but if this feature is set, it will be necessary to
33596 enter the "exit" command instead.
33597 <P>
33598 <UL>
33599 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33600 </UL><P>
33601 <End of help on this topic>
33602 </BODY>
33603 </HTML>
33604 ====== h_config_8bit_smtp =====
33605 <HTML>
33606 <HEAD>
33607 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
33608 </HEAD>
33609 <BODY>
33610 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
33612 This feature affects Alpine's behavior when sending mail.
33613 By default, this feature is set.
33614 Internet standards
33615 require that all electronic mail messages traversing the global Internet
33616 consist of 7bit ASCII characters unless a pair of cooperating mail
33617 transfer agents explicitly agree to allow 8bit messages. In general,
33618 then, exchanging messages in non-ASCII characters requires MIME encoding.
33619 <P>
33620 However, there are now Internet standards that allow for unencoded 8bit
33621 exchange of messages between cooperating systems. When this feature is set
33622 Alpine will try to negotiate unencoded 8bit transmission during the
33623 sending process. Should the negotiation fail, Alpine will fall back to its
33624 ordinary encoding rules.
33625 <P>
33626 Note, this feature relies on your system's mail transport agent or
33627 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
33628 having the negotiation mechanism introduced in
33629 "Extended SMTP" (ESMTP) and the specific extension called
33630 "8BITMIME".
33631 <P>
33632 ESMTP allows for graceful migration to upgraded mail transfer agents, but
33633 it is possible that this feature might cause problems for some servers.
33634 <P><UL>
33635 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33636 </UL>
33637 <P><End of help on this topic>
33638 </BODY>
33639 </HTML>
33640 ====== h_config_8bit_nntp =====
33641 <HTML>
33642 <HEAD>
33643 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
33644 </HEAD>
33645 <BODY>
33646 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
33648 This feature affects Alpine's behavior when posting news.
33650 <P>
33652 The Internet standard for exchanging USENET news messages (RFC-1036)
33653 specifies that USENET messages should conform to Internet mail standards
33654 and contain only 7bit characters, but much of the news transport software
33655 in use today is capable of successfully sending messages containing 8bit
33656 characters. Hence, many people believe that it is appropriate to send 8bit
33657 news messages without any MIME encoding.
33659 <P>
33661 Moreover, there is no Internet standard for explicitly negotiating 8bit
33662 transfer, as there is for Internet email. Therefore, Alpine provides the
33663 option of posting unencoded 8bit news messages, though not as the default.
33664 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
33665 postings that contain 8bit characters.
33667 <P>
33669 Note, articles may cross a path or pass through news transport software
33670 that is unsafe or even hostile to 8bit characters. At best this will only
33671 cause the posting to become garbled. The safest way to transmit 8bit
33672 characters is to leave Alpine's MIME encoding turned on, but recipients
33673 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
33674 messages.
33675 <P>
33676 <End of help on this topic>
33677 </BODY>
33678 </HTML>
33679 ====== h_config_mark_for_cc =====
33680 <HTML>
33681 <HEAD>
33682 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
33683 </HEAD>
33684 <BODY>
33685 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
33687 This feature affects Alpine's MESSAGE INDEX display.
33688 By default, a '+' is displayed in the first column if the
33689 message is addressed directly to you.
33690 When this feature is set and the message is not addressed to you, then a
33691 '-' character is displayed if the message is instead Cc'd directly
33692 to you.
33694 <P>
33695 <UL>
33696 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33697 </UL><P>
33698 <End of help on this topic>
33699 </BODY>
33700 </HTML>
33701 ====== h_config_tab_uses_unseen =====
33702 <HTML>
33703 <HEAD>
33704 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
33705 </HEAD>
33706 <BODY>
33707 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
33709 This feature affects Alpine's behavior when using the TAB
33710 <A HREF="h_common_nextnew">NextNew Command</A>
33711 to move from one folder to the next.
33712 Alpine's usual behavior is to search for folders
33713 with <EM>Recent</EM> messages in them.
33714 Recent messages are messages that have arrived since the last time the
33715 folder was opened.
33717 <P>
33718 Setting this feature causes Alpine to search for <EM>Unseen</EM>
33719 messages instead of Recent messages.
33720 Unseen messages remain Unseen until you view them (or flag then as Seen with
33721 the <A HREF="h_common_flag">Flag Command</A>).
33722 Setting this feature allows you to locate messages you have not read
33723 instead of only recently received messages.
33724 When this feature is set, the feature
33725 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
33726 will have no effect, so the checking may be slower.
33728 <P>
33729 Another reason why you might want to use this feature is that Alpine sometimes
33730 opens folders implicitly behind the scenes, and this clears the
33731 Recent status of all messages in the folder.
33732 One example where this happens is when Saving or filtering a
33733 message to another folder.
33734 If that message has some <A HREF="h_config_keywords">keywords</A>
33735 set, then because of some shortcomings
33736 in the IMAP specification, the best way to ensure that those keywords are
33737 still set in the saved copy of the message is to open the folder and
33738 set the keywords explicitly.
33739 Because this clears the Recent status of all messages in that folder the
33740 folder will not be found by the NextNew command unless this feature is set.
33742 <P>
33743 <End of help on this topic>
33744 </BODY>
33745 </HTML>
33746 ====== h_config_tab_new_only =====
33747 <HTML>
33748 <HEAD>
33749 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
33750 </HEAD>
33751 <BODY>
33752 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
33754 This feature affects Alpine's behavior when using the TAB key to move from
33755 one message to the next. Alpine's usual behavior is to select the next
33756 unread message or message flagged as "Important".
33758 <P>
33760 Setting this feature causes Alpine to skip the messages flagged as important,
33761 and select unread messages exclusively. Tab behavior when there are no
33762 new messages left to select remains unchanged.
33763 <P>
33764 <End of help on this topic>
33765 </BODY>
33766 </HTML>
33767 ====== h_config_warn_if_subj_blank =====
33768 <HTML>
33769 <HEAD>
33770 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
33771 </HEAD>
33772 <BODY>
33773 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
33775 This feature affects Alpine's behavior when you send a message being
33776 composed.
33777 If this option is set, Alpine will check to see if the message about to be sent
33778 has a subject or not.
33779 If not, you will be asked if you want to send the message anyway.
33780 <P>
33782 <UL>
33783 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33784 </UL><P>
33785 <End of help on this topic>
33786 </BODY>
33787 </HTML>
33788 ====== h_config_warn_if_fcc_blank =====
33789 <HTML>
33790 <HEAD>
33791 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
33792 </HEAD>
33793 <BODY>
33794 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
33796 This feature affects Alpine's behavior when you send a message being
33797 composed.
33798 If this option is set, Alpine will check to see if the message about to be sent
33799 has an Fcc or not.
33800 If not, you will be asked if you want to send the message anyway.
33801 <P>
33803 <UL>
33804 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33805 </UL><P>
33806 <End of help on this topic>
33807 </BODY>
33808 </HTML>
33809 ====== h_config_warn_if_no_to_or_cc =====
33810 <HTML>
33811 <HEAD>
33812 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
33813 </HEAD>
33814 <BODY>
33815 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
33817 This feature affects Alpine's behavior when you send a message being
33818 composed.
33819 If this option is set, Alpine will check to see if the message about to be sent
33820 has either a To address, a Cc address, or a Newsgroup.
33821 If none of these is set,
33822 you will be asked if you want to send the message anyway.
33823 <P>
33825 This feature is closely related to
33826 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
33827 Alpine will normally ask if you want to copy a message only to the Fcc.
33828 This feature also applies to cases where there is a Bcc but still no To, Cc,
33829 or Newsgroup.
33830 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
33831 message with only an Fcc, then you won't be asked about sending with
33832 a blank To and Cc and Newsgroups header even if this feature is set.
33833 Similarly, if you have already been asked if you want to send to the Fcc
33834 only and you have answered Yes, then you won't be asked again about sending with
33835 blank To, Cc, and Newsgroups headers even if this feature is set.
33836 <P>
33838 <UL>
33839 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33840 </UL><P>
33841 <End of help on this topic>
33842 </BODY>
33843 </HTML>
33844 ====== h_config_quell_dead_letter =====
33845 <HTML>
33846 <HEAD>
33847 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
33848 </HEAD>
33849 <BODY>
33850 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
33852 This feature affects Alpine's behavior when you cancel a message being
33853 composed. Alpine's usual behavior is to write the canceled message to
33854 a file named
33855 <!--chtml if pinemode="os_windows"-->
33856 "DEADLETR",
33857 <!--chtml else-->
33858 "dead.letter" in your home directory,
33859 <!--chtml endif-->
33860 overwriting any previous message. Under
33861 some conditions (some routine), this can introduce a noticeable delay.
33862 Setting this feature will cause Alpine NOT to write canceled compositions
33863 into the file.
33864 <P>
33865 NOTE: Enabling this feature means NO record of canceled messages is
33866 maintained.
33867 <P>
33868 This feature affects the newer option
33869 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
33870 number of dead letter files to keep around.
33871 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
33872 <P>
33873 <UL>
33874 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33875 </UL><P>
33876 <End of help on this topic>
33877 </BODY>
33878 </HTML>
33879 ====== h_config_quell_beeps =====
33880 <HTML>
33881 <HEAD>
33882 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
33883 </HEAD>
33884 <BODY>
33885 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
33887 This feature affects Alpine's behavior when it displays status message
33888 (e.g., Error complaints, New mail warnings, etc). Setting this feature
33889 will not affect the display of such messages, but will cause those that
33890 emit a beep to become silent.
33892 <P>
33893 <UL>
33894 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33895 </UL><P>
33896 <End of help on this topic>
33897 </BODY>
33898 </HTML>
33899 ====== h_config_suppress_user_agent =====
33900 <HTML>
33901 <HEAD>
33902 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
33903 </HEAD>
33904 <BODY>
33905 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
33907 If this feature is set then Alpine will not generate a
33908 <CODE>User-Agent</CODE> header in outgoing messages.
33909 <P>
33910 <UL>
33911 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33912 </UL><P>
33913 <End of help on this topic>
33914 </BODY>
33915 </HTML>
33916 ====== h_config_quell_lock_failure_warnings =====
33917 <HTML>
33918 <HEAD>
33919 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
33920 </HEAD>
33921 <BODY>
33922 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
33924 This feature affects Alpine's behavior when it encounters a problem
33925 acquiring a mail folder lock. Typically, a secondary file associated
33926 with the mail folder being opened is created as part of the locking
33927 process. On some systems, such file creation has been administratively
33928 precluded by the system configuration.
33929 <P>
33930 Alpine issues a warning when such failures occur, which can become bothersome
33931 if the system is configured to disallow such actions. Setting this
33932 feature causes Alpine to remain silent when this part of lock creation fails.
33933 <P>
33934 WARNING: systems that have been configured in a way that precludes locking
33935 introduce some risk of mail folder corruption when more than one program
33936 attempts to modify the mail folder. This is most likely to occur to one's
33937 INBOX or other incoming message folder.
33938 <P>
33939 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
33940 <P>
33941 <UL>
33942 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33943 </UL><P>
33944 <End of help on this topic>
33945 </BODY>
33946 </HTML>
33947 ====== h_config_enable_role_take ======
33948 <HTML>
33949 <HEAD>
33950 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
33951 </HEAD>
33952 <BODY>
33953 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
33955 Normally, the Take command takes addresses from a message and helps you
33956 put them into your Address Book.
33957 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
33958 you may find it useful
33959 to be able to Take information from a message's headers and put it into
33960 a new Rule.
33961 When this feature is set, you will be given an extra prompt that gives
33962 you the choice to Take into the Address Book or Take into a rule.
33963 <P><UL>
33964 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33965 </UL>
33966 <P>
33967 <End of help on this topic>
33968 </BODY>
33969 </HTML>
33970 ====== h_config_enable_take_export ======
33971 <HTML>
33972 <HEAD>
33973 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
33974 </HEAD>
33975 <BODY>
33976 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
33978 Normally, the Take command takes addresses from a message and helps you
33979 put them into your Address Book.
33980 When this feature is set, you will be given an extra prompt that gives you
33981 the choice to Take addresses into a file instead of your Address
33982 Book.
33983 Only the user@domain_name part of the address is put in the file.
33984 <P><UL>
33985 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33986 </UL>
33987 <P>
33988 <End of help on this topic>
33989 </BODY>
33990 </HTML>
33991 ====== h_config_quell_folder_internal_msg ======
33992 <HTML>
33993 <HEAD>
33994 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
33995 </HEAD>
33996 <BODY>
33997 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
33999 This feature determines whether or not Alpine will create
34000 "pseudo messages" in folders that are in standard Unix or
34001 MMDF format. <P>
34003 Alpine will normally create these pseudo messages when they are not already
34004 present in a standard Unix or MMDF folder. Their purpose is to record
34005 certain mailbox state data needed for correct IMAP and POP server
34006 operation, and also for Alpine to be able to mark messages as Answered when
34007 the Reply has been postponed.<P>
34009 Sites that do not use IMAP/POP for remote mail access, and that need to
34010 support mail tools that are adversely affected by the presence of the
34011 pseudo-messages (e.g. some mail notification tools) may enable this
34012 feature to tell Alpine not to create them. Note that Alpine's
34013 "Answered" flag
34014 capability will be adversely affected if this is done.<P>
34016 Note too that, even if this feature is enabled, Alpine will not remove
34017 pseudo-messages when it encounters them (e.g. those created by UW's imapd
34018 or ipopd servers.) This feature has no effect on folders that are not in
34019 standard Unix or MMDF format, as pseudo-messages are not needed in the
34020 other formats to record mailbox state information.
34021 <P><UL>
34022 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34023 </UL>
34024 <P>
34025 <End of help on this topic>
34026 </BODY>
34027 </HTML>
34028 ====== h_config_mulnews_as_typed ======
34029 <HTML>
34030 <HEAD>
34031 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
34032 </HEAD>
34033 <BODY>
34034 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
34036 This feature will be of little use to most users.
34037 It has no effect unless the feature
34038 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
34039 is set.
34041 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
34042 then the setting of this feature may have an effect on the names of the
34043 newsrc files used.
34044 Normally, the name of the news server will be canonicalized before it is
34045 used in the newsrc file name.
34046 For example, if you type the news server name
34048 <P>
34049 <CENTER><SAMP>servername</SAMP></CENTER>
34050 <P>
34052 it is likely that the canonical name will be something like
34054 <P>
34055 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34056 <P>
34058 Or it may be the case that
34060 <P>
34061 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34062 <P>
34064 is really an alias (a DNS CNAME) for
34066 <P>
34067 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
34068 <P>
34070 If this feature is not set, then the canonicalized names will be used.
34071 If this feature is set, then the name you typed in (or put in your
34072 configuration) will be used.
34074 <P><UL>
34075 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34076 </UL>
34077 <P>
34078 <End of help on this topic>
34079 </BODY>
34080 </HTML>
34081 ====== h_config_quell_empty_dirs ======
34082 <HTML>
34083 <HEAD>
34084 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
34085 </HEAD>
34086 <BODY>
34087 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
34089 This feature causes Alpine to remove from the display any directories
34090 that do not contain at least one file or directory. This can be useful
34091 to prevent overly cluttered folder lists when a collection is stored on
34092 a server that treats all names as both a folder and a directory.
34094 <P>
34095 Note, enabling this feature can cause surprising behavior! For example,
34096 you can still use Add to create a directory, but unless you immediately
34097 enter that directory and create a folder, that newly created directory
34098 may not be displayed next time you enter the folder list.
34100 <P>
34101 The description above is not quite correct.
34102 Only directories which potentially may hold messages are hidden if empty.
34103 That is, a directory which is really just a directory and is not selectable
34104 as a folder will not be hidden.
34105 Such directories can occur on servers that treat most names as both a folder
34106 and a directory.
34107 These directories are typically created implicitly when a folder is created
34108 inside a directory that does not yet exist.
34110 <P>
34111 <UL>
34112 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34113 </UL><P>
34114 <End of help on this topic>
34115 </BODY>
34116 </HTML>
34117 ====== h_config_termcap_wins =====
34118 <HTML>
34119 <HEAD>
34120 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
34121 </HEAD>
34122 <BODY>
34123 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
34125 This feature may affect Alpine's low-level input routines. Termcap (or
34126 terminfo, depending on how your copy of Alpine was compiled and linked)
34127 is the name of the database that describes terminal capabilities. In
34128 particular, it describes the sequences of characters that various keys
34129 will emit.
34131 <P>
34132 An example would be the Up Arrow key on the keyboard. Up
34133 Arrow is not a distinct character on most Unix systems. When you press
34134 the Up Arrow key a short sequence of characters are produced. This
34135 sequence is supposed to be described in the termcap database by the
34136 "ku" capability (or by the "kcuu1" capability if you
34137 are using terminfo instead of termcap).
34139 <P>
34140 By default, Alpine defines some terminal
34141 escape sequences that are commonly used. For example, the sequence
34142 "ESC O A" is recognized as an Up Arrow key. The sequence
34143 "ESC [ A"
34144 is also recognized as an Up Arrow key. These are chosen because common
34145 terminals like VT100's or ANSI standard terminals produce these
34146 sequences when you press the Up Arrow key.
34148 <P>
34149 If your system's termcap
34150 (terminfo) database assigns some other function to the sequence
34151 "ESC O A"
34152 it is usually ignored by Alpine. Also, if your termcap (terminfo)
34153 database assigns a sequence that doesn't begin with an escape
34154 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
34155 This usually works fine
34156 because most terminals emit the escape sequences that Alpine has defined
34157 by default. We have also found that it is usually better to have these
34158 defaults take precedence over the definitions contained in the database
34159 because the defaults are more likely to be correct than the database.
34161 <P>
34162 There are some terminals where this breaks down. If you want Alpine to
34163 believe the definitions given in your termcap (terminfo) database in
34164 preference to the defaults the Alpine itself sets up, then you may turn
34165 this feature on. Then, sequences of characters that are defined in
34166 both termcap (terminfo) and in Alpine's set of defaults will be
34167 interpreted the way that termcap (terminfo) says they should be
34168 interpreted. Also, if your terminal capabilities database assigns a
34169 sequence that doesn't begin with escape, it will not be ignored.
34171 <P>
34172 <UL>
34173 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34174 </UL><P>
34175 <End of help on this topic>
34176 </BODY>
34177 </HTML>
34178 ====== h_config_cruise_mode =====
34179 <HTML>
34180 <HEAD>
34181 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
34182 </HEAD>
34183 <BODY>
34184 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
34186 This feature affects Alpine's behavior when you hit the
34187 "Space Bar" at
34188 the end of a displayed message. Typically, Alpine complains that the end
34189 of the text has already been reached. Setting this feature causes such
34190 keystrokes to be interpreted as if the "Tab" key had been hit, thus
34191 taking you to the next "interesting" message,
34192 or scanning ahead to the
34193 next incoming folder with "interesting" messages.
34195 <P>
34196 <UL>
34197 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34198 </UL><P>
34199 <End of help on this topic>
34200 </BODY>
34201 </HTML>
34202 ====== h_config_cruise_mode_delete =====
34203 <HTML>
34204 <HEAD>
34205 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
34206 </HEAD>
34207 <BODY>
34208 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
34210 This feature modifies the behavior of Alpine's
34211 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
34212 Setting this feature causes Alpine to implicitly delete read
34213 messages when it moves on to display the next "interesting" message.
34214 <P>
34215 NOTE: Beware when enabling this feature AND the
34216 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
34217 feature.
34218 <P>
34219 <UL>
34220 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34221 </UL><P>
34222 <End of help on this topic>
34223 </BODY>
34224 </HTML>
34225 ====== h_config_slash_coll_entire =====
34226 <HTML>
34227 <HEAD>
34228 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
34229 </HEAD>
34230 <BODY>
34231 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
34233 The slash (/) command is available from the MESSAGE INDEX screen when
34234 the folder is sorted by either Threads or OrderedSubject, and the
34235 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
34236 is set to something other than "none".
34237 Normally, the slash command Collapses or Expands the subthread that
34238 starts at the currently highlighted message, if any.
34239 If this option is set, then the slash command Collapses or Expands the
34240 <EM>entire</EM> current thread instead of just the subthread.
34241 The current thread is simply the top-level thread that contains the
34242 current message.
34244 <P>
34245 <UL>
34246 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34247 </UL><P>
34248 <End of help on this topic>
34249 </BODY>
34250 </HTML>
34251 ====== h_config_color_thrd_import =====
34252 <HTML>
34253 <HEAD>
34254 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
34255 </HEAD>
34256 <BODY>
34257 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
34259 This option affects only the THREAD INDEX screen.
34260 Whether or not you ever see a THREAD INDEX screen depends on the setting
34261 of the configuration option
34262 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
34263 and on the sort order of the index.
34265 <P>
34266 If a message within a thread is flagged as Important
34267 and this option is set, then
34268 the entire line in the THREAD INDEX will be colored the color of the
34269 Index-important Symbol, which can be set using the
34270 <A HREF="h_color_setup">Setup Kolor</A> screen.
34272 <P>
34273 <UL>
34274 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34275 </UL><P>
34276 <End of help on this topic>
34277 </BODY>
34278 </HTML>
34279 ====== h_config_allow_goto =====
34280 <HTML>
34281 <HEAD>
34282 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
34283 </HEAD>
34284 <BODY>
34285 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
34287 This feature modifies the behavior of Alpine's file browser. Setting this
34288 feature causes Alpine to offer the "G Goto" command in the file browser.
34289 That is the default.
34291 <P>
34293 The Goto command allows you to explicitly type in the desired directory.
34294 <P>
34295 <End of help on this topic>
34296 </BODY></HTML>
34297 ====== h_config_add_ldap =====
34298 <HTML>
34299 <HEAD>
34300 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
34301 </HEAD>
34302 <BODY>
34303 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
34305 If both the Directory option
34306 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
34307 and this feature are set,
34308 then when an implicit directory lookup is done from the
34309 composer you will automatically be prompted to add the result of the
34310 directory lookup to your address book.
34311 <P>
34312 <UL>
34313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34314 </UL><P>
34315 <End of help on this topic>
34316 </BODY>
34317 </HTML>
34318 ===== h_patterns_compat_behavior =====
34319 <HTML>
34320 <HEAD>
34321 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
34322 </HEAD>
34323 <BODY>
34324 <H1>Rules Behavior Changes in Pine 4.50</H1>
34326 In Alpine, Rules that contain unrecognized elements
34327 are ignored.
34328 In most cases, the unrecognized elements will be something that was
34329 added as a new Rules feature in a later version of Alpine.
34330 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
34331 ignore rules that contained unrecognized elements.
34332 For example, a new element of Rules that was added in Pine 4.50 is
34333 Age interval.
34334 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
34335 all messages older than a week red.
34336 Now, if you run Pine 4.44 using that same configuration file, it will not
34337 recognize the Age interval and so will just ignore it.
34338 That means that all messages will match that rule so all messages will
34339 be colored red when using Pine version 4.44.
34341 <P>
34342 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
34343 However, since the behavior still exists in versions prior to Pine 4.50 and
34344 since Filtering is a potentially destructive operation, another measure
34345 was taken to attempt to avoid unintentional Filtering of messages.
34346 The first time that you run Alpine or a Pine that is version 4.50 or greater,
34347 the rules in your Filters configuration variable ("Patterns-Filters")
34348 will be copied to a new Filters configuration variable
34349 with a different name ("Patterns-Filters2").
34350 From then on, Alpine will continue to use the new
34351 variable.
34352 Of course, Pine version 4.44 or lower will continue to use the old
34353 variable.
34354 That means that if you are using Alpine
34355 and also using a version of Pine that is older than 4.50, they will not
34356 share the configuration information about Filters.
34357 If you make a change in one version you won't see it in the other version.
34359 <P>
34360 Since Scoring can be used to trigger Filtering, the same thing has been
34361 done for Score rules.
34362 The old configuration variable name is ("Patterns-Scores")
34363 and the new name is ("Patterns-Scores2").
34364 The same is not true of Role, Indexcolor, and Other rules that are
34365 thought to be less harmful when a mistake is made.
34367 <P>
34368 <End of help on this topic>
34369 </BODY>
34370 </HTML>
34371 ======= h_config_filt_opts_sentdate =======
34372 <HTML>
34373 <HEAD>
34374 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
34375 </HEAD>
34376 <BODY>
34377 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
34379 By default, the Age interval of a Pattern uses a message's time of
34380 arrival to compute the age of the message.
34381 If this feature is set, the date in the message's Date header will
34382 be used instead.
34383 <P>
34384 <End of help on this topic>
34385 </BODY>
34386 </HTML>
34387 ======= h_config_filt_opts_notdel =======
34388 <HTML>
34389 <HEAD>
34390 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
34391 </HEAD>
34392 <BODY>
34393 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
34395 If this option is set then a message will be moved into the
34396 specified folder only if it is not marked for deletion.
34397 This is useful if you have multiple Alpine sessions running
34398 simultaneously and you don't want messages to be filtered into a
34399 folder more than once.
34400 It is also useful if you want to filter
34401 only the "undeleted" messages in a newsgroup into a folder.
34402 This method is not foolproof.
34403 There may be cases where a message
34404 gets marked deleted and so it is never filtered into the folder.
34405 For example, if you deleted it in another Alpine session or another mail
34406 program that didn't use the filtering rule.
34407 <P>
34408 This option has no effect if the Filter Action is not set to Move.
34409 <P>
34410 <End of help on this topic>
34411 </BODY>
34412 </HTML>
34413 ======= h_config_filt_opts_nonterm =======
34414 <HTML>
34415 <HEAD>
34416 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
34417 </HEAD>
34418 <BODY>
34419 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
34421 If this option is set then this is a non-terminating rule.
34422 Usually, for each message, Alpine searches through the Filter Rules until
34423 a match is found and then it performs the action associated with that rule.
34424 Rules following the match are not considered.
34425 If this option is set then the search for matches will continue at the next
34426 rule.
34427 <P>
34428 If a non-terminating rule matches then the actions associated with
34429 that rule, except for any implied deletion of the message, are performed
34430 before the match for the next rule is checked.
34431 For example, if the non-terminating rule sets the Important status, then that
34432 status will be set when the next rule is considered.
34433 However, if the non-terminating rule Moves the message, the message will
34434 actually be copied instead of copied and deleted so that it is still there
34435 for the next rule.
34436 A moved message is deleted after all the relevant rules have been checked.
34437 The name of the "Move" action is confusing in this case because
34438 a single message can be moved to more than one folder.
34439 It turns the Move into a Copy instead, but it is still followed by a deletion
34440 at the end.
34441 <P>
34442 This option may be useful if you want to have a single message filtered to
34443 two different folders because it matches two different Patterns.
34444 For example, suppose you normally filter messages to a particular mailing
34445 list into one folder, and messages addressed directly to you into a second
34446 folder.
34447 If a message is sent to both you and the list (and you can tell that by
34448 looking at the headers of the message) this option may give you a convenient
34449 way to capture a copy to each folder.
34450 (It may also cause you to capture two copies to each folder,
34451 depending on whether your mail system delivers one or two copies of the
34452 message to you and on how the list works.)
34453 <P>
34454 <End of help on this topic>
34455 </BODY>
34456 </HTML>
34457 ===== h_mainhelp_smime ======
34458 <HTML>
34459 <HEAD>
34460 <TITLE>S/MIME Overview</TITLE>
34461 </HEAD>
34462 <BODY>
34463 <H1>S/MIME Overview</H1>
34465 S/MIME is a standard for the public key encryption and signing of email.
34466 UNIX Alpine contains a basic implementation of S/MIME based on
34467 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries.
34468 To check if this version of Alpine supports S/MIME look at
34469 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34470 for "S/MIME" under the "Encryption" heading.
34471 <P>
34472 Some limitations:
34473 <UL>
34474 <LI> There is no PC-Alpine implementation.
34475 <LI> There is no provision for checking for CRLs
34476 (Certificate Revocation Lists) in Alpine.
34477 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34478 <LI> There is no mechanism available for feeding either an entire incoming
34479 or an entire outgoing message to an external
34480 filter and using that external filter to do S/MIME or PGP processing.
34481 <LI> Because the implementation currently uses OpenSSL, there is only a very
34482 limited integration with the Mac OS Keychain (the storing and access of
34483 public certificates).
34484 </UL>
34485 <P>
34486 The S/MIME configuration screen is reached by going to the Main Menu and typing
34487 the "S Setup" command followed by "M S/MIME".
34488 <P>
34490 <H2>S/MIME BASICS</H2>
34492 In order to digitally sign messages you send you must have a public/private key-pair.
34493 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34494 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34495 users or a company which provides certificates for its workers.
34496 These certificates are bound to an email address, so the identity being verified is the
34497 email address not a person's name.
34498 <P>
34499 Mail is signed by using the sender's private key, which only the owner of the private key
34500 has access to.
34501 The signature is verified using the signer's public key, which anyone can
34502 have access to.
34503 With Alpine, the first time you receive a signed message the public key of the
34504 sender will be stored for future use.
34506 <P>
34507 Mail is encrypted using the recipient's public key and decrypted by
34508 the recipient with their private key.
34510 <P>
34511 You need a key of your own in order to sign outgoing messages and to have others
34512 encrypt messages sent to you.
34513 You do not need a key of your own to verify signed messages sent by others or to
34514 encrypt messages sent to others.
34516 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
34518 By default UNIX Alpine stores the certificates it uses in a directory in your
34519 home directory.
34520 The directory name is
34521 <P>
34522 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
34523 <P>
34524 Within that directory are three subdirectories.
34525 Each of the three subdirectories contains files with PEM-encoded contents,
34526 the default format for OpenSSL.
34527 The "<SAMP>public</SAMP>" directory contains public certificates.
34528 The files within that directory have names that are email addresses with the
34529 suffix "<SAMP>.crt</SAMP>" appended.
34530 An example filename is
34531 <P>
34532 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34533 <P>
34534 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
34535 your private key.
34536 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
34537 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
34538 Authorities that you want to trust but that aren't contained in the set of system CAs.
34539 Those files may have arbitrary names as long as they end with the
34540 suffix "<SAMP>.crt</SAMP>".
34542 <H2>HOW TO SIGN AND ENCRYPT</H2>
34544 If you have a certificate you may sign outgoing messages.
34545 After typing the Ctrl-X command to send a message you will see the prompt
34546 <P>
34547 <CENTER><SAMP>Send message?</SAMP></CENTER>
34548 <P>
34549 Available subcommands include "G Sign" and "E Encrypt".
34550 Typing the "G" command will change the prompt to
34551 <P>
34552 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
34553 <P>
34554 Typing the "E" command will change the prompt to
34555 <P>
34556 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
34557 <P>
34558 You may even type both to get
34559 <P>
34560 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
34561 <P>
34563 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
34565 The reading of a signed message should not require any special action on
34566 your part.
34567 There should be an editorial addition at the start of the message which
34568 says either
34569 <P>
34570 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
34571 <P>
34572 or
34573 <P>
34574 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
34575 <P>
34576 If an encrypted message is sent to you the encrypted text will not
34577 be shown.
34578 You will have to type the "Ctrl-D Decrypt" command (from the screen where
34579 you are viewing the message) and supply your passphrase when asked.
34580 <P>
34581 For a signed or encrypted message there is also a "Ctrl-E Security" command
34582 which gives you some information about the certificate used to sign or encrypt the message.
34584 <H2>MISCELLANEOUS</H2>
34586 If you have access to a private certificate in the PKCS12 format, which
34587 would sometimes be in a file with a ".p12" extension, then you can
34588 use the following commands to generate private keys, public and certificate
34589 authorities certificates. In the examples below, we assume that the
34590 certificate in the p12 format is called "certificate.p12", and
34591 that your email address is "your@address.com".
34593 <P>
34594 In order to create a private key use the command
34595 <P>
34596 <CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER>
34597 <P>
34598 In order to create a public certificate use the command
34599 <P>
34600 <CENTER><SAMP>
34601 openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt
34602 </SAMP></CENTER>
34603 <P>
34604 In order to create a certificate authority certificate use the command
34605 <P>
34606 <CENTER><SAMP>
34607 openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt
34608 </SAMP></CENTER>
34610 <P> If the previous command produces an empty file, it means that the
34611 certificate authority was not included in the .p12 file, so you will have
34612 to get it from some other sources. You will need these certificates, so
34613 that you can validate correctly signatures.
34615 <P>
34616 After you have exported these certificates and keys, you can use the import
34617 command in Alpine, from the S/MIME configuration screen,
34618 to import these certificates into Alpine. They will be available for use
34619 as soon as you import them.
34620 <P>
34621 <End of help on this topic>
34622 </BODY>
34623 </HTML>
34624 ====== h_config_smime_pubcertdir =====
34625 <HTML>
34626 <HEAD>
34627 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
34628 </HEAD>
34629 <BODY>
34630 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
34632 UNIX Alpine only.
34633 <P>
34634 If the option
34635 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
34636 is set then this option will have no effect.
34637 <P>
34638 Normally, Public Certificates for use with S/MIME will be stored in the directory
34639 which is the value of this option.
34640 Those certificates will be stored in PEM format, one certificate per file.
34641 The name of the file for the certificate corresponding to
34642 <P>
34643 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34644 <P>
34645 should be
34646 <P>
34647 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
34648 <P>
34649 For example, a file for user@example.com would be in the file
34650 <P>
34651 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34652 <P>
34653 in this directory.
34654 <P>
34655 Use the Setup/SMIME screen to modify this variable.
34656 <P>
34657 Typically, the public certificates that you have will come from S/MIME signed
34658 messages that are sent to you.
34659 Alpine will extract the public certificate from the signed message and store
34660 it in the certificates directory.
34661 These PEM format public certificates look something like:
34662 <PRE>
34663 -----BEGIN CERTIFICATE-----
34664 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
34665 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
34666 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
34667 ...
34668 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
34669 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
34670 -----END CERTIFICATE-----
34671 </PRE>
34672 <P>
34673 <UL>
34674 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34675 </UL><P>
34676 <P>
34677 <UL>
34678 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34679 </UL><P>
34680 <End of help on this topic>
34681 </BODY>
34682 </HTML>
34683 ====== h_config_smime_pubcertcon =====
34684 <HTML>
34685 <HEAD>
34686 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
34687 </HEAD>
34688 <BODY>
34689 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
34691 UNIX Alpine only.
34692 <P>
34693 If this option is set it will be used instead of
34694 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
34695 <P>
34696 This option gives you a way to store certificates remotely on an IMAP server
34697 instead of storing the certificates one per file locally.
34698 In order to do that you just give this option a remote folder name for a folder
34699 which does not yet exist.
34700 The name is similar to the name you might use for a remote configuration file.
34701 A remote folder name might look something like:
34702 <P>
34703 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
34704 <P>
34705 See
34706 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34707 about the syntax of folder names.
34708 <P>
34709 Use the Setup/SMIME screen to modify this variable.
34710 <P>
34711 <UL>
34712 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34713 </UL><P>
34714 <P>
34715 <UL>
34716 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34717 </UL><P>
34718 <End of help on this topic>
34719 </BODY>
34720 </HTML>
34721 ====== h_config_smime_privkeydir =====
34722 <HTML>
34723 <HEAD>
34724 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
34725 </HEAD>
34726 <BODY>
34727 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
34729 UNIX Alpine only.
34730 <P>
34731 In order to sign outgoing S/MIME messages you will need a
34732 personal digital ID certificate.
34733 You will usually get such a certificate from a certificate authority such as
34734 Thawte or CAcert.
34735 (In order to encrypt outgoing messages you don't need a personal digital ID, you
34736 need the public certificate of the recipient instead.)
34737 If the option
34738 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
34739 is set then this option will have no effect.
34740 <P>
34741 Normally, Private Keys for use with S/MIME will be stored in the directory
34742 which is the value of this option.
34743 Those certificates will be stored in PEM format, one certificate per file.
34744 The name of the file for the certificate corresponding to your
34745 <P>
34746 <CENTER><SAMP>emailaddress</SAMP></CENTER>
34747 <P>
34748 should be
34749 <P>
34750 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
34751 <P>
34752 For example, if your address is user@example.com the name of the file would be
34753 <P>
34754 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
34755 <P>
34756 in this directory.
34757 <P>
34758 Use the Setup/SMIME screen to modify this variable.
34759 <P>
34760 Typically, the private key that you have will come from a Certificate
34761 Authority.
34762 The private key should be stored in a PEM format file that
34763 looks something like:
34764 <PRE>
34765 -----BEGIN RSA PRIVATE KEY-----
34766 Proc-Type: 4,ENCRYPTED
34767 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
34769 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
34770 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
34771 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
34772 ...
34773 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
34774 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
34775 -----END RSA PRIVATE KEY-----
34776 </PRE>
34777 <P>
34778 <UL>
34779 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34780 </UL><P>
34781 <P>
34782 <UL>
34783 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34784 </UL><P>
34785 <End of help on this topic>
34786 </BODY>
34787 </HTML>
34788 ====== h_config_smime_privkeycon =====
34789 <HTML>
34790 <HEAD>
34791 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
34792 </HEAD>
34793 <BODY>
34794 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
34796 UNIX Alpine only.
34797 <P>
34798 If this option is set it will be used instead of
34799 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
34800 <P>
34801 This option gives you a way to store keys remotely on an IMAP server
34802 instead of storing the keys one per file locally.
34803 In order to do that you just give this option a remote folder name for a folder
34804 which does not yet exist.
34805 The name is similar to the name you might use for a remote configuration file.
34806 A remote folder name might look something like:
34807 <P>
34808 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
34809 <P>
34810 See
34811 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34812 about the syntax of folder names.
34813 <P>
34814 Use the Setup/SMIME screen to modify this variable.
34815 <P>
34816 <UL>
34817 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34818 </UL><P>
34819 <P>
34820 <UL>
34821 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34822 </UL><P>
34823 <End of help on this topic>
34824 </BODY>
34825 </HTML>
34826 ====== h_config_smime_cacertdir =====
34827 <HTML>
34828 <HEAD>
34829 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
34830 </HEAD>
34831 <BODY>
34832 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
34834 UNIX Alpine only.
34835 <P>
34836 If the option
34837 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
34838 is set then this option will have no effect.
34839 <P>
34840 CACert is a shorthand name for certification authority certificate.
34841 Normally Alpine will use the CACerts that are located in the standard system
34842 location for CACerts.
34843 It may be the case that one of your correspondents has a Digital ID which has
34844 been signed by a certificate authority that is not in the regular set of system certificate
34845 authorities.
34846 You may supplement the system list by adding further certificates of your own.
34847 These should be stored in the directory
34848 which is the value of this option.
34849 The certificates will be stored in PEM format, one certificate per file.
34850 The names of the files can be anything ending in ".crt".
34851 <P>
34852 Use the Setup/SMIME screen to modify this variable.
34853 <P>
34854 These PEM format CA certificates look very similar to your public
34855 certificates for particular email addresses
34856 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
34857 <P>
34858 <UL>
34859 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34860 </UL><P>
34861 <P>
34862 <UL>
34863 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34864 </UL><P>
34865 <End of help on this topic>
34866 </BODY>
34867 </HTML>
34868 ====== h_config_smime_cacertcon =====
34869 <HTML>
34870 <HEAD>
34871 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
34872 </HEAD>
34873 <BODY>
34874 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
34876 UNIX Alpine only.
34877 <P>
34878 If this option is set it will be used instead of
34879 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
34880 <P>
34881 This option gives you a way to store certificates remotely on an IMAP server
34882 instead of storing the certificates one per file locally.
34883 In order to do that you just give this option a remote folder name for a folder
34884 which does not yet exist.
34885 The name is similar to the name you might use for a remote configuration file.
34886 A remote folder name might look something like:
34887 <P>
34888 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
34889 <P>
34890 See
34891 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
34892 about the syntax of folder names.
34893 <P>
34894 Use the Setup/SMIME screen to modify this variable.
34895 <P>
34896 <UL>
34897 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34898 </UL><P>
34899 <P>
34900 <UL>
34901 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34902 </UL><P>
34903 <End of help on this topic>
34904 </BODY>
34905 </HTML>
34906 ========== h_config_smime_sign_by_default ==========
34907 <HTML>
34908 <HEAD>
34909 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
34910 </HEAD>
34911 <BODY>
34912 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
34914 UNIX Alpine only.
34915 <P>
34916 This feature only has an effect if your version of Alpine includes
34917 support for S/MIME.
34918 It affects Alpine's behavior when you send a message.
34919 If this option is set, the "Sign" option will default to ON when sending messages.
34920 <P>
34921 Only the default value is affected.
34922 In any case, you may still toggle the Signing option on or off before sending
34923 with the "G Sign" command (provided you have a personal digital ID
34924 certificate).
34925 <P>
34926 <UL>
34927 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34928 </UL><P>
34929 <P>
34931 <UL>
34932 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34933 </UL><P>
34934 <End of help on this topic>
34935 </BODY>
34936 </HTML>
34937 ========== h_config_smime_use_cert_store ==========
34938 <HTML>
34939 <HEAD>
34940 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE>
34941 </HEAD>
34942 <BODY>
34943 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1>
34945 UNIX Alpine only.
34946 <P>
34947 This feature only has an effect if your version of Alpine includes
34948 support for S/MIME.
34949 It affects Alpine's behavior when you validate a message, and should
34950 not be disabled, unless you are performing a test.
34951 <P>
34952 There are two important aspects of validation: validation of the message
34953 (that is, the message was not modified after it was sent)
34954 as well as validation of the identity of the sender. This option has to
34955 do with the latter.
34956 <P>
34957 In order to validate that the message came from the sender in the message
34958 and not an impersonator, Alpine can
34959 either use the certificates that come in the message, or the ones that
34960 you have personally stored. If this feature is enabled (the default) then
34961 Alpine will use certificates that you have already saved in your store
34962 and not those that come in the message to validate the sender of the
34963 message. In particular, the first time that you receive a signed message
34964 from a sender, and their certificate does not validate against your
34965 store, then you will be asked if you wish to save such certificate. If
34966 you do not wish to save the certificate, then Alpine will fail to validate
34967 the signature of the message. Otherwise, Alpine will proceed to validate
34968 the signature of the message. This behavior helps you prevent against impersonation, because
34969 it is assumed that you trust the certificates that you have saved, and
34970 might not trust those that came with the message that you are validating.
34971 <P>
34972 <UL>
34973 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
34974 </UL><P>
34975 <P>
34977 <UL>
34978 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34979 </UL><P>
34980 <End of help on this topic>
34981 </BODY>
34982 </HTML>
34983 ========== h_config_smime_pubcerts_in_keychain ==========
34984 <HTML>
34985 <HEAD>
34986 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
34987 </HEAD>
34988 <BODY>
34989 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
34991 UNIX Alpine only.
34992 <P>
34993 If this feature is set the Mac OS X default keychain will be used as the place
34994 to store public certificates instead of a
34995 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
34996 or a
34997 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
34998 <P>
34999 <UL>
35000 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35001 </UL><P>
35002 <P>
35003 <UL>
35004 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35005 </UL><P>
35006 <End of help on this topic>
35007 </BODY>
35008 </HTML>
35009 ========== h_config_smime_dont_do_smime ==========
35010 <HTML>
35011 <HEAD>
35012 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
35013 </HEAD>
35014 <BODY>
35015 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
35017 UNIX Alpine only.
35018 <P>
35019 Setting this feature turns off all of Alpine's S/MIME support.
35020 You might want to set this if you are having trouble due to the S/MIME support.
35021 <P>
35022 <UL>
35023 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35024 </UL><P>
35025 <P>
35027 <UL>
35028 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35029 </UL><P>
35030 <End of help on this topic>
35031 </BODY>
35032 </HTML>
35033 ========== h_config_smime_encrypt_by_default ==========
35034 <HTML>
35035 <HEAD>
35036 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
35037 </HEAD>
35038 <BODY>
35039 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
35041 UNIX Alpine only.
35042 <P>
35043 This feature only has an effect if your version of Alpine includes
35044 support for S/MIME.
35045 It affects Alpine's behavior when you send a message.
35046 If this option is set, the "Encrypt" option will default to ON when sending messages.
35047 <P>
35048 Only the default value is affected.
35049 In any case, you may still toggle the Encrypt option on or off before sending
35050 with the "E Encrypt" command (provided you have a the public digital ID
35051 for the recipient).
35052 <P>
35053 <UL>
35054 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35055 </UL><P>
35056 <P>
35058 <UL>
35059 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35060 </UL><P>
35061 <End of help on this topic>
35062 </BODY>
35063 </HTML>
35064 ========== h_config_smime_remember_passphrase ==========
35065 <HTML>
35066 <HEAD>
35067 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
35068 </HEAD>
35069 <BODY>
35070 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
35072 UNIX Alpine only.
35073 <P>
35074 This feature only has an effect if your version of Alpine includes
35075 support for S/MIME.
35076 If this option is set, you will only have to enter your passphrase for your private key
35077 once during an Alpine session.
35078 <P>
35079 <UL>
35080 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35081 </UL><P>
35082 <P>
35084 <UL>
35085 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35086 </UL><P>
35087 <End of help on this topic>
35088 </BODY>
35089 </HTML>
35090 ====== h_config_smime_transfer_pub_to_con =====
35091 <HTML>
35092 <HEAD>
35093 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
35094 </HEAD>
35095 <BODY>
35096 <H1>S/MIME: Transfer Public Certs to Container</H1>
35098 UNIX Alpine only.
35099 <P>
35100 The Transfer command will copy the public certificates in your configured
35101 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35102 to the container in your configured
35103 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35104 This might be useful if you decide to switch from using a cert directory to a cert
35105 container.
35106 <P>
35107 Warning: Any previous contents in the container will be lost.
35108 <P>
35109 <UL>
35110 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35111 </UL><P>
35112 <P>
35113 <UL>
35114 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35115 </UL><P>
35116 <End of help on this topic>
35117 </BODY>
35118 </HTML>
35119 ====== h_config_smime_transfer_pub_to_dir =====
35120 <HTML>
35121 <HEAD>
35122 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
35123 </HEAD>
35124 <BODY>
35125 <H1>S/MIME: Transfer Public Certs to Directory</H1>
35127 UNIX Alpine only.
35128 <P>
35129 The Transfer command will copy the public certificates in your configured
35130 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35131 to the directory in your configured
35132 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35133 This might be useful if you decide to switch from using a cert container to a cert
35134 directory.
35135 <P>
35136 <UL>
35137 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35138 </UL><P>
35139 <P>
35140 <UL>
35141 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35142 </UL><P>
35143 <End of help on this topic>
35144 </BODY>
35145 </HTML>
35146 ====== h_config_smime_transfer_priv_to_con =====
35147 <HTML>
35148 <HEAD>
35149 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
35150 </HEAD>
35151 <BODY>
35152 <H1>S/MIME: Transfer Private Keys to Container</H1>
35154 UNIX Alpine only.
35155 <P>
35156 The Transfer command will copy the private keys in your configured
35157 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35158 to the container in your configured
35159 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35160 This might be useful if you decide to switch from using a key directory to a key
35161 container.
35162 <P>
35163 Warning: Any previous contents in the container will be lost.
35164 <P>
35165 <UL>
35166 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35167 </UL><P>
35168 <P>
35169 <UL>
35170 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35171 </UL><P>
35172 <End of help on this topic>
35173 </BODY>
35174 </HTML>
35175 ====== h_config_smime_transfer_priv_to_dir =====
35176 <HTML>
35177 <HEAD>
35178 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
35179 </HEAD>
35180 <BODY>
35181 <H1>S/MIME: Transfer Private Keys to Directory</H1>
35183 UNIX Alpine only.
35184 <P>
35185 The Transfer command will copy the private keys in your configured
35186 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35187 to the directory in your configured
35188 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35189 This might be useful if you decide to switch from using a key container to a key
35190 directory.
35191 <P>
35192 <UL>
35193 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35194 </UL><P>
35195 <P>
35196 <UL>
35197 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35198 </UL><P>
35199 <End of help on this topic>
35200 </BODY>
35201 </HTML>
35202 ====== h_config_smime_transfer_cacert_to_con =====
35203 <HTML>
35204 <HEAD>
35205 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
35206 </HEAD>
35207 <BODY>
35208 <H1>S/MIME: Transfer CA Certs to Container</H1>
35210 UNIX Alpine only.
35211 <P>
35212 The Transfer command will copy the CA certificates in your configured
35213 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
35214 to the container in your configured
35215 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35216 This might be useful if you decide to switch from using a CA cert directory to a CA cert
35217 container.
35218 <P>
35219 Warning: Any previous contents in the container will be lost.
35220 <P>
35221 <UL>
35222 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35223 </UL><P>
35224 <P>
35225 <UL>
35226 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35227 </UL><P>
35228 <End of help on this topic>
35229 </BODY>
35230 </HTML>
35231 ====== h_config_smime_transfer_cacert_to_dir =====
35232 <HTML>
35233 <HEAD>
35234 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
35235 </HEAD>
35236 <BODY>
35237 <H1>S/MIME: Transfer CA Certs to Directory</H1>
35239 UNIX Alpine only.
35240 <P>
35241 The Transfer command will copy the CA certificates in your configured
35242 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35243 to the directory in your configured
35244 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35245 This might be useful if you decide to switch from using a CA cert container to a CA cert
35246 directory.
35247 <P>
35248 <UL>
35249 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35250 </UL><P>
35251 <P>
35252 <UL>
35253 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35254 </UL><P>
35255 <End of help on this topic>
35256 </BODY>
35257 </HTML>
35258 ====== h_config_smime_transfer_pubcon_to_key =====
35259 <HTML>
35260 <HEAD>
35261 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35262 </HEAD>
35263 <BODY>
35264 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35266 Mac OS X Alpine only.
35267 <P>
35268 The Transfer command will copy the public certificates in your configured
35269 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35270 to your default Mac OS X Keychain.
35271 This might be useful if you decide to switch from using a cert container to using
35272 the Keychain to store your public certs, which you may do by using the
35273 feature
35274 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
35275 <P>
35276 <UL>
35277 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35278 </UL><P>
35279 <P>
35280 <UL>
35281 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35282 </UL><P>
35283 <End of help on this topic>
35284 </BODY>
35285 </HTML>
35286 ====== h_config_smime_transfer_pubkey_to_con =====
35287 <HTML>
35288 <HEAD>
35289 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35290 </HEAD>
35291 <BODY>
35292 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35294 UNIX Alpine only.
35295 <P>
35296 The Transfer command will copy the public certificates in your configured
35297 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35298 to your default Mac OS X Keychain.
35299 This might be useful if you decide to switch from using a cert container to using
35300 the Keychain to store your public certs.
35301 <P>
35302 <UL>
35303 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35304 </UL><P>
35305 <P>
35306 <UL>
35307 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35308 </UL><P>
35309 <End of help on this topic>
35310 </BODY>
35311 </HTML>
35312 ====== h_config_smime_public_certificates =====
35313 <HTML>
35314 <HEAD>
35315 <TITLE>S/MIME: Manage Public Certificates</TITLE>
35316 </HEAD>
35317 <BODY>
35318 <H1>S/MIME: Manage Public Certificates</H1>
35320 UNIX Alpine only.
35321 <P>
35322 This menu item allows you to manage your public certificates, this
35323 may include your own public certificate, but it normally includes
35324 certificates of people you correspond with. These certificates are
35325 saved by Alpine automatically when they are found in signed messages
35326 that you receive. This interface allows you to manage them, by
35327 giving you the option to delete them, or trust them (in the case
35328 of self-signed certificates).
35330 <P>
35331 Please note that Alpine will not validate a message that was sent to you
35332 using a self-signed certificate, unless you decide to trust that certificate.
35333 Internally, a certificate is trusted by copying it to the
35334 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
35335 collection. If you decide that you want to stop trusting a self-signed
35336 certificate, you must delete such certificate from such collection.
35337 <P>
35338 The <B>I</B> Import command available in this screen allows you to
35339 import a command to this collection.
35340 <P>
35341 <UL>
35342 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35343 </UL><P>
35344 <P>
35345 <UL>
35346 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35347 </UL><P>
35348 <End of help on this topic>
35349 </BODY>
35350 </HTML>
35351 ====== h_config_smime_private_keys =====
35352 <HTML>
35353 <HEAD>
35354 <TITLE>S/MIME: Manage Private Keys</TITLE>
35355 </HEAD>
35356 <BODY>
35357 <H1>S/MIME: Manage Private Keys</H1>
35359 UNIX Alpine only.
35360 <P>
35361 This option allows you to manage your private key. Normally a person has only
35362 one key, in the same way that a person only has one valid passport, or ID card,
35363 at any given time. This option allows you to manage private keys. You can
35364 delete them or import them. Additionally, you can view information
35365 about your public certificate, such as the issuer and the dates of validity
35366 of such certificate, among others.
35368 <P>
35369 If you have more than one e-mail address for which you want to use the
35370 same private key, you must add all those addresses to the private key at
35371 the moment that the key is generated. When you receive a signed message using
35372 a key generated for several e-mail addresses, Alpine will save a
35373 certificate for each e-mail address included in such certificate.
35374 <P>
35375 The <B>I</B> Import command available in this screen allows you to
35376 import a command to this collection.
35377 <P>
35378 <UL>
35379 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35380 </UL><P>
35381 <P>
35382 <UL>
35383 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35384 </UL><P>
35385 <End of help on this topic>
35386 </BODY>
35387 </HTML>
35388 ====== h_config_smime_certificate_authorities =====
35389 <HTML>
35390 <HEAD>
35391 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
35392 </HEAD>
35393 <BODY>
35394 <H1>S/MIME: Manage Certificate Authorities</H1>
35396 UNIX Alpine only.
35397 <P>
35398 This collection contains certificates that are needed to validate the
35399 certificate of another person, and therefore contains certificates that
35400 you trust. Typically a certificate is signed by another entity, called a
35401 certificate authority. This option allows you to manage which certificates
35402 you trust, allowing you to import them and to delete them or view information
35403 about each certificate, such as the issuer and the dates of validity
35404 of such certificate.
35405 <P>
35406 The <B>I</B> Import command available in this screen allows you to
35407 import a command to this collection.
35408 <P>
35409 <UL>
35410 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35411 </UL><P>
35412 <P>
35413 <UL>
35414 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35415 </UL><P>
35416 <End of help on this topic>
35417 </BODY>
35418 </HTML>
35419 ====== h_certificate_information =====
35420 <HTML>
35421 <HEAD>
35422 <TITLE>S/MIME: Certificate Information Screen</TITLE>
35423 </HEAD>
35424 <BODY>
35425 <H1>S/MIME: Certificate Information Screen</H1>
35427 UNIX Alpine only.
35428 <P>
35429 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
35430 such as its owner, e-mail address, issuer, and interval of validity,
35431 among others.
35432 <P>
35433 In the case of public certificates, this screen shows you if there was a
35434 failure when attempting to validate such message. If the certificate is
35435 self-signed, then the <B>T</B> Trust command will be available, which
35436 you can use to trust such certificate and make Alpine not fail validating
35437 signatures signed with such certificate.
35438 <P>
35439 You can also mark a certificate deleted, with the <B>D</B> command, or
35440 remove the deleted mark with the <B>U</B> undelete command.
35441 <P>
35442 In the case of your private key, Alpine shows you the information
35443 from your public key. Additionally, Alpine allows you to see public
35444 and private information about your key, with the <B>B</B> and
35445 <B>R</B> commands respectively.
35446 <UL>
35447 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35448 </UL><P>
35449 <P>
35450 <UL>
35451 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35452 </UL><P>
35453 <End of help on this topic>
35454 </BODY>
35455 </HTML>
35456 ====== h_config_smime_manage_public_menu =====
35457 <HTML>
35458 <HEAD>
35459 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
35460 </HEAD>
35461 <BODY>
35462 <H1>S/MIME: Commands that Manage Public Certificates</H1>
35464 UNIX Alpine only.
35465 <P>
35466 This screen allows you to manage your public certificates.
35467 <P>
35468 The format of this screen is as follows. There are five fields: The
35469 leftmost field is normally empty, but it could contain the letter
35470 "D" to indicate that that certificate has been marked for
35471 deletion. The next field is the e-mail address of the owner of the
35472 certificate, shown in its entirety. The third and fourth field are the
35473 first and last day validity for that certificate, respectively. The date
35474 is displayed in the user's locale unless the option
35475 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>
35476 is set. In this case, the month, day and year are represented by two
35477 digits, and the format used is mm/dd/yy. Finally, the fifth
35478 field is what can be displayed of the MD5 hash of the certificate. You can
35479 use any of the last three fields to distinguish between two certificates
35480 for the same owner.
35481 <P>
35482 Available commands in this screen and a short description of what they
35483 do follows.
35484 <UL>
35485 <LI> <B>I</B> Imports a public certificate to this collection.
35486 <LI> <B>V</B> View information about a certificate such as the name of the person the
35487 certificate was issued to, its dates of validity, and validity status.
35488 <LI> <B>D</B> Marks a certificate deleted.
35489 <LI> <B>U</B> Removes the deletion mark on a certificate.
35490 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35491 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
35492 trust a certificate by copying it to the collection of trusted certificates.
35493 </UL>
35494 <P>
35495 All commands provide feedback to let you know about their success or failure.
35496 <P>
35497 <UL>
35498 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35499 </UL><P>
35500 <P>
35501 <UL>
35502 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35503 </UL><P>
35504 <End of help on this topic>
35505 </BODY>
35506 </HTML>
35507 ====== h_config_smime_manage_private_menu =====
35508 <HTML>
35509 <HEAD>
35510 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
35511 </HEAD>
35512 <BODY>
35513 <H1>S/MIME: Commands that Manage Private Keys</H1>
35515 UNIX Alpine only.
35516 <P>
35517 This screen allows you to manage your private key.
35518 <P>
35519 The format of this screen is as follows. There are five fields: The
35520 leftmost field is normally empty, but it could contain the letter
35521 "D" to indicate that that certificate has been marked for
35522 deletion. The next field is the e-mail address of the owner of the
35523 certificate, shown in its entirety. The third field is the first day of
35524 validity for that certificate; the fourth field in the last day that that
35525 certificate is valid, and the fifth field is what can be displayed of the
35526 MD5 hash of the public certificate corresponding to this private key. You
35527 can use any of the last three fields to distinguish between two
35528 certificates for the same owner.
35529 <P>
35530 Available commands and a short description of what they do follows.
35531 <UL>
35532 <LI> <B>I</B> Imports a new public key to this collection.
35533 <LI> <B>V</B> View information about the public certificate corresponding to this
35534 key.
35535 <LI> <B>D</B> Marks a key to be deleted.
35536 <LI> <B>U</B> Removes the deletion mark on a key.
35537 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
35538 Note that expunging a private key does not remove the public key, which must
35539 be removed separately.
35540 </UL>
35541 <P>
35542 All commands provide feedback to let you know about their success or failure.
35543 <P>
35544 <UL>
35545 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35546 </UL><P>
35547 <P>
35548 <UL>
35549 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35550 </UL><P>
35551 <End of help on this topic>
35552 </BODY>
35553 </HTML>
35554 ====== h_config_smime_manage_cacerts_menu =====
35555 <HTML>
35556 <HEAD>
35557 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
35558 </HEAD>
35559 <BODY>
35560 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
35562 UNIX Alpine only.
35563 <P>
35564 This screen allows you to manage your collection of certificates that you
35565 trust.
35566 <P>
35567 The format of this screen is as follows. There are five fields: The
35568 leftmost field is normally empty, but it could contain the letter
35569 "D" to indicate that that certificate has been marked for
35570 deletion. The next field is the e-mail address of the owner of the
35571 certificate, shown in its entirety. The third field is the first day of
35572 validity for that certificate; the fourth field in the last day that that
35573 certificate is valid, and the fifth field is what can be displayed of the
35574 MD5 hash of the certificate. You can use any of the last three fields to
35575 distinguish between two certificates for the same owner.
35576 <P>
35577 Available commands and a short description of what they do follows.
35578 <UL>
35579 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
35580 done by reading the certificate and validating it. Once a certificate
35581 is found to be valid, it is saved, adding the extension ".crt"
35582 to the certificate, if necessary.
35583 <LI> <B>V</B> View information about this certificate, such as its issuer
35584 and validity dates.
35585 <LI> <B>D</B> Marks a certificate to be deleted.
35586 <LI> <B>U</B> Removes the deletion mark on a certificate.
35587 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35588 </UL>
35589 <P>
35590 All commands provide feedback to let you know about their success or failure.
35591 <P>
35592 <UL>
35593 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35594 </UL><P>
35595 <P>
35596 <UL>
35597 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35598 </UL><P>
35599 <End of help on this topic>
35600 </BODY>
35601 </HTML>
35602 ====== h_config_lame_list_mode =====
35603 <HTML>
35604 <HEAD>
35605 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
35606 </HEAD>
35607 <BODY>
35608 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
35610 This feature modifies the method Alpine uses to ask your IMAP
35611 server for folder names to display in the FOLDER LIST screen.
35612 It is intended to compensate for a small set of IMAP servers that
35613 are programmed to ignore a part of the request, and thus respond
35614 to Alpine's query with nonsensical results.
35615 <P>
35617 If you find that Alpine is erroneously displaying blank folder lists,
35618 try enabling this feature.
35619 <P>
35621 NOTE: Enabling this feature has consequences for the Goto and Save
35622 commands. Many servers allow access to folders outside the area
35623 reserved for your personal folders via some reserved character,
35624 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
35625 allows, at the Goto and Save prompts, quick access to folders
35626 outside your personal folder collection without requiring a specific
35627 collection definition. This behavior will generally not be available
35628 when this feature is enabled.
35630 <P>
35631 <UL>
35632 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35633 </UL><P>
35634 <End of help on this topic>
35635 </BODY>
35636 </HTML>
35637 ====== h_config_enable_mulnewsrcs =====
35638 <HTML>
35639 <HEAD>
35640 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
35641 </HEAD>
35642 <BODY>
35643 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
35645 This feature makes it so Alpine can use multiple newsrcs based on
35646 the news server being connected to, which allows for separate lists
35647 of subscribed-to newsgroups. When this feature is not set, there is only
35648 one list of newsgroups.
35649 <P>
35650 Under this feature, the name of a newsrc is based on the news server.
35651 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
35652 is set to ".newsrc", and the news server you are connecting to is
35653 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
35654 Setting this feature for the first time will allow for the option of using
35655 your old newsrc the next time you read news.
35656 <P>
35657 If this feature is set, then the feature
35658 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
35659 also may affect the name of the newsrc file that is used.
35660 <P>
35661 <UL>
35662 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35663 </UL><P>
35664 <End of help on this topic>
35665 </BODY>
35666 </HTML>
35667 ======= h_ab_export_vcard =======
35668 <HTML>
35669 <HEAD>
35670 <TITLE>Address Book Export Format</TITLE>
35671 </HEAD>
35672 <BODY>
35673 <H1>Address Book Export Format</H1>
35675 You are exporting address book data from Alpine to a file outside of Alpine.
35676 You are being asked to choose the format of the export.
35677 Here are the choices:
35679 <DL>
35680 <DT><EM>A</EM>ddress List</DT>
35681 <DD>
35682 The addresses from the address book entries you are saving
35683 from will be saved one address per line.
35684 Address book lists (those with more than one address) will have
35685 all of their addresses saved separately.
35686 </DD>
35688 <DT><EM>V</EM>Card</DT>
35689 <DD>
35690 The entries will be saved in
35691 <A HREF="h_whatis_vcard">vCard</A> format.
35692 </DD>
35694 <DT><EM>T</EM>ab Separated</DT>
35695 <DD>
35696 The entries will be saved in tab-separated columns.
35697 There will be just 4 columns of data that correspond to Alpine's
35698 Nickname field, Full Name field, Address field, and Comment field.
35699 It might prove useful to Select only the Simple, non-List address book
35700 entries before Saving.
35701 </DD>
35703 <DT><EM>^C</EM> Cancel</DT>
35704 <DD>
35705 Cancel out of the Save.
35706 </DD>
35708 </DL>
35711 <P>
35712 <End of help on this topic>
35713 </BODY>
35714 </HTML>
35715 ====== h_config_predict_nntp_server =====
35716 <HTML>
35717 <HEAD>
35718 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
35719 </HEAD>
35720 <BODY>
35721 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
35723 This feature allows Alpine to assume that the open NNTP server at the
35724 time of composition is the NNTP server to which the message should be
35725 posted. This is especially recommended when there are multiple News
35726 collections. If this feature is not set, Alpine will try to post to the first server in
35727 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
35728 this feature also negates the need to add News collection servers to
35729 the <!--#echo var="VAR_nntp-server"--> variable.
35730 <P>
35731 This feature can be especially handy when used in conjunction with
35732 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
35733 <P>
35734 <UL>
35735 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35736 </UL><P>
35737 <End of help on this topic>
35738 </BODY>
35739 </HTML>
35740 ====== h_config_nntp_search_uses_overview =====
35741 <HTML>
35742 <HEAD>
35743 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
35744 </HEAD>
35745 <BODY>
35746 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
35748 This feature should probably be turned on unless it causes trouble.
35749 The results of the NNTP overview command (XOVER) may be used to help
35750 with some searches in news groups.
35751 It should result in quicker response time.
35752 Turning this feature on apparently causes search results which are
35753 different from what you would get with the feature turned off on some
35754 servers.
35755 <P>
35756 <UL>
35757 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35758 </UL><P>
35759 <End of help on this topic>
35760 </BODY>
35761 </HTML>
35762 ====== h_config_thread_sorts_by_arrival =====
35763 <HTML>
35764 <HEAD>
35765 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
35766 </HEAD>
35767 <BODY>
35768 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
35770 This feature affects how a threading sort arranges threads. The default way
35771 to arrange threads is by the date of the earliest message in the thread.
35772 This feature arranges threads by the last message to arrive in a thread.
35773 <P>
35774 This feature causes old threads that get recent messages to sort to the bottom,
35775 where previously a message arrival to a thread would not rearrange the order of
35776 that thread.
35777 <P>
35778 <UL>
35779 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35780 </UL><P>
35781 <End of help on this topic>
35782 </BODY>
35783 </HTML>
35784 ====== h_config_textplain_int =====
35785 <HTML>
35786 <HEAD>
35787 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
35788 </HEAD>
35789 <BODY>
35790 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
35792 This feature modifies the method Alpine uses to display Text/Plain
35793 MIME attachments from the Attachment Index screen. Normally, the
35794 "View" command searches for any externally defined (usually
35795 via the
35796 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
35797 and displays the selected text within that viewer.
35799 <P>
35800 Enabling this feature causes Alpine to ignore any external viewer
35801 settings and always display text with Alpine's internal viewer.
35803 <P>
35804 <UL>
35805 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35806 </UL><P>
35807 <End of help on this topic>
35808 </BODY>
35809 </HTML>
35810 ====== h_config_wp_columns =====
35811 <HTML>
35812 <HEAD>
35813 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
35814 </HEAD>
35815 <BODY>
35816 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
35818 Web Alpine only.
35819 <P>
35820 This configuration setting specifies the number of horizontal characters
35821 used to format various WebAlpine pages. Smaller values will tend to reduce
35822 the amount of horizontal scrolling required to view pages within narrow
35823 browsers, such as those found on PDAs, and larger values will tend to
35824 spread more information across the page.
35826 <P>
35827 The Message List page uses the width to determine how many characters
35828 to assign each field. Note, a smaller value may result in a disproportionate
35829 amount of blank space between fields on each line. Similarly, a large
35830 value may result in cramped fields or horizontal scrolling.
35832 <P>
35833 The Message View page uses this value to determine when to wrap lines
35834 in displayed message text. Note, a smaller value may result in jagged
35835 right margins or confusing quoting. A larger value may cause lines of text to
35836 run beyond the browser's right edge, requiring horizontal scrolling.
35838 <P>
35839 <UL>
35840 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35841 </UL><P>
35842 <End of help on this topic>
35843 </BODY>
35844 </HTML>
35845 ====== h_config_wp_state =====
35846 <HTML>
35847 <HEAD>
35848 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
35849 </HEAD>
35850 <BODY>
35851 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
35853 Web Alpine only.
35854 <P>
35855 Various aspects of cross-session state.
35857 <P>
35858 <UL>
35859 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35860 </UL><P>
35861 <End of help on this topic>
35862 </BODY>
35863 </HTML>
35864 ====== h_config_wp_aggstate =====
35865 <HTML>
35866 <HEAD>
35867 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
35868 </HEAD>
35869 <BODY>
35870 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
35872 Web Alpine only.
35873 <P>
35874 Aggregate operations tab state.
35876 <P>
35877 <UL>
35878 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35879 </UL><P>
35880 <End of help on this topic>
35881 </BODY>
35882 </HTML>
35883 ====== h_config_wp_indexlines =====
35884 <HTML>
35885 <HEAD>
35886 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
35887 </HEAD>
35888 <BODY>
35889 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
35891 Web Alpine only.
35892 <P>
35893 Number of index lines in table.
35895 <P>
35896 <UL>
35897 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35898 </UL><P>
35899 <End of help on this topic>
35900 </BODY>
35901 </HTML>
35902 ====== h_config_wp_indexheight =====
35903 <HTML>
35904 <HEAD>
35905 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
35906 </HEAD>
35907 <BODY>
35908 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
35910 Web Alpine only.
35911 <P>
35912 Index table row height.
35914 <P>
35915 <UL>
35916 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35917 </UL><P>
35918 <End of help on this topic>
35919 </BODY>
35920 </HTML>
35921 ====== h_config_rss_news =====
35922 <HTML>
35923 <HEAD>
35924 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
35925 </HEAD>
35926 <BODY>
35927 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
35929 Web Alpine only.
35930 <P>
35931 RSS News feed.
35933 <P>
35934 <UL>
35935 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35936 </UL><P>
35937 <End of help on this topic>
35938 </BODY>
35939 </HTML>
35940 ====== h_config_rss_weather =====
35941 <HTML>
35942 <HEAD>
35943 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
35944 </HEAD>
35945 <BODY>
35946 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
35948 Web Alpine only.
35949 <P>
35950 RSS Weather feed.
35952 <P>
35953 <UL>
35954 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35955 </UL><P>
35956 <End of help on this topic>
35957 </BODY>
35958 </HTML>
35959 ====== h_config_send_confirms_only_expanded =====
35960 <HTML>
35961 <HEAD>
35962 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
35963 </HEAD>
35964 <BODY>
35965 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
35967 This Web Alpine option specifies whether or not a Send confirmations
35968 happens when a composed message is readied for sending or not. The
35969 default behavior is to not confirm that the nicknames were expanded to
35970 the intended addresses.
35972 <P>
35973 <UL>
35974 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35975 </UL><P>
35976 <End of help on this topic>
35977 </BODY>
35978 </HTML>
35979 ====== h_config_enable_jump_command =====
35980 <HTML>
35981 <HEAD>
35982 <TITLE>FEATURE: enable-jump-command</TITLE>
35983 </HEAD>
35984 <BODY>
35985 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
35987 This Web Alpine option specifies whether or not a Jump command is
35988 offered in the Message List and Message View pages. The command is
35989 implemented as an input field in the left column of the List and View
35990 screens.
35992 <P>
35993 When enabled and a number is entered in the input field while the
35994 Message List is displayed, the Message List is reframed with the
35995 specified message. While viewing a message, the message associated
35996 with the specified message number is displayed.
35998 <P>
35999 <UL>
36000 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36001 </UL><P>
36002 <End of help on this topic>
36003 </BODY>
36004 </HTML>
36005 ====== h_config_enable_newmail_sound =====
36006 <HTML>
36007 <HEAD>
36008 <TITLE>FEATURE: enable-newmail-sound</TITLE>
36009 </HEAD>
36010 <BODY>
36011 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
36013 This Web Alpine option specifies whether or not a sound file is sent
36014 to the web browser along with the newmail notification message.
36017 <P>
36018 <UL>
36019 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36020 </UL><P>
36021 <End of help on this topic>
36022 </BODY>
36023 </HTML>
36024 ====== h_config_render_html_internally =====
36025 <HTML>
36026 <HEAD>
36027 <TITLE>FEATURE: render-html-internally</TITLE>
36028 </HEAD>
36029 <BODY>
36030 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
36032 By default, Web Alpine will pass cleansed HTML text you receive in messages
36033 to the browser for display (rendering). This feature causes Web Alpine to convert
36034 the HTML text into plain text in the same way Unix and PC-Alpine do.
36037 <P>
36038 <UL>
36039 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36040 </UL><P>
36041 <End of help on this topic>
36042 </BODY>
36043 </HTML>
36044 ====== h_config_role_undo =====
36045 Yes, remember changes and exit back to list of roles; No, discard changes
36046 made in this screen; ^C, cancel exit and stay in this config screen.
36047 ====== h_exit_editor =====
36048 S, save changes and exit from the editor; D, do not save changes but
36049 do exit from the editor; or ^C, cancel exit and stay in the editor.
36050 ====== h_config_undo =====
36051 Yes, save changes and exit; No, exit without saving any changes made since
36052 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
36053 ====== h_os_index_whereis =====
36054 Enter ^V or ^Y to go immediately to the last or first message in the index.
36055 Or, enter the match string followed by RETURN.
36056 ====== h_os_index_whereis_agg =====
36057 Enter ^V or ^Y to go immediately to the last or first message in the index,
36058 Or, enter the match string followed by RETURN (or ^X to select all matches).
36059 =========== h_oe_add_full ==================
36060 Type the full name of the person being added and press the RETURN key.
36061 Press ^C to cancel addition.
36062 =========== h_oe_add_nick ==================
36063 Type a short nickname and press RETURN. A nickname is a short easy-to-
36064 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
36065 ========== h_oe_add_addr ================
36066 Type the e-mail address and press RETURN.
36067 Press ^C to cancel addition.
36068 ========== h_oe_crlst_full ==============
36069 Type a long name or description for the list that you are creating and
36070 press RETURN. Press ^C to cancel creation of list.
36071 =========== h_oe_crlst_nick =============
36072 Type a nickname (short, easy-to-remember name or single word) for the list
36073 you are creating and press RETURN. Press ^C to cancel.
36074 ========== h_oe_crlst_addr ==============
36075 Type an e-mail address, or a nickname already in the address book that you
36076 want to be part of this list and press RETURN.
36077 ========== h_oe_adlst_addr =============
36078 Type an e-mail address or a nickname already in the address book that you
36079 want to add to this list and press RETURN.
36080 ========== h_oe_editab_nick ============
36081 Change the nickname using the arrow keys and delete key. Press RETURN
36082 when done. Press ^C to cancel editing and leave the nickname as it was.
36083 ========== h_oe_editab_full ============
36084 Change the full name using the arrow keys and delete key. Press RETURN
36085 when done. Press ^C to cancel editing and leave the full name as it was.
36086 ========== h_oe_editab_addr ============
36087 Change the address using the arrow keys and delete key. Press RETURN
36088 when done. Press ^C to cancel editing and leave the address as it was.
36089 ========== h_oe_editab_fcc ============
36090 Change the fcc using the arrow keys and delete key. Press RETURN when
36091 done. Press ^C to cancel editing and leave the fcc as it was.
36092 ========== h_oe_editab_comment ============
36093 Change the comment field using the arrow keys and delete key. Press RETURN
36094 when done. Press ^C to cancel editing and leave the comment as it was.
36095 ====== h_ab_forward =====
36096 Yes, expand nicknames and qualify local names with your current domain name;
36097 No, leave nicknames and local names as is; ^C, cancel.
36098 ========== h_ab_export ==========
36099 Type the name of a file to write the addresses into and
36100 press RETURN. You may also specify an absolute path. Use ^C to cancel.
36101 ========== h_ab_edit_a_field ==========
36102 Edit any of the fields of the currently selected entry by typing one of the
36103 letters at the bottom of the screen. Press ^C to cancel edit.
36104 ====== h_ab_del_data_revert =====
36105 Press B to completely delete addrbook and revert to default, C to delete config
36106 and revert while leaving data, or D to only delete data (make it empty).
36107 ====== h_ab_del_data_modify =====
36108 Press B to completely delete addrbook, C to delete configuration while leaving
36109 data, or D to delete data (make it empty) but leave config. ^C to cancel.
36110 ====== h_ab_del_config_modify =====
36111 Yes, remove this address book from my configuration.
36112 No, make no changes now.
36113 ====== h_ab_del_config_revert =====
36114 Yes, remove this address book from my config and revert to default.
36115 No, make no changes now.
36116 ====== h_ab_del_default =====
36117 Yes, remove this default address book from my configuration.
36118 No, make no changes now.
36119 ====== h_ab_really_delete =====
36120 Yes, delete the actual contents of the address book, not just the
36121 configuration. No, don't delete the data after all, cancel and start over.
36122 ====== h_ab_del_ignore =====
36123 Press I to ignore all the default address books for this category. Press R to
36124 remove this one address book and add the others to your personal list.
36125 ====== h_ab_del_dir_ignore =====
36126 Press I to ignore all the default directory servers for this category.
36127 Press R to remove this one server and add the others to your personal list.
36128 ====== h_ab_copy_dups =====
36129 Yes, overwrite the existing entry.
36130 No, skip duplicates but save the rest. Press ^C to cancel.
36131 ====== h_confirm_cancel =====
36132 Type C to Confirm that you want to abandon the message you are composing.
36133 Type N or ^C to cancel out of the cancel and keep composing.
36134 ====== h_ab_text_or_vcard =====
36135 Text, start composer with displayed text already included.
36136 VCard, start composer with address book entry attached as a vCard. ^C cancels.
36137 ====== h_ab_backup_or_ldap =====
36138 Backup, copy email address from entry and allow editing of it.
36139 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
36140 ====== h_ldap_text_or_vcard =====
36141 Text: export displayed text for selected entry. Address: export only the
36142 email address. VCard: export entry in vCard format. ^C cancels.
36143 ====== h_ab_save_exp =====
36144 Save, save entry or entries to an address book.
36145 Export, save to file outside of pine. ^C cancels save.
36146 ====== h_ab_add =====
36147 A, add a brand new entry to this address book.
36148 E, edit the entry that is currently highlighted. ^C to cancel.
36149 ====== h_ab_shuf =====
36150 U, swap order of highlighted address book and the one above it.
36151 D, swap order of highlighted address book and the one below it. ^C to cancel.
36152 ====== h_ab_shuf_up =====
36153 U, swap order of highlighted address book and the one above it.
36154 Press ^C to cancel.
36155 ====== h_ab_shuf_down =====
36156 D, swap order of highlighted address book and the one below it.
36157 Press ^C to cancel.
36158 ====== h_folder_prop =====
36159 Count is # of messages in the folder, Unseen means messages that have not
36160 been read, New means messages that were Recently added to the folder.
36161 ====== h_role_shuf =====
36162 U, swap order of highlighted rule and the one above it.
36163 D, swap order of highlighted rule and the one below it. ^C to cancel.
36164 ====== h_role_shuf_up =====
36165 U, swap order of highlighted rule and the one above it.
36166 Press ^C to cancel.
36167 ====== h_role_shuf_down =====
36168 D, swap order of highlighted rule and the one below it.
36169 Press ^C to cancel.
36170 ====== h_incoming_shuf =====
36171 B, swap order of highlighted directory and the one before it.
36172 F, swap order of highlighted directory and the one after it. ^C to cancel.
36173 ====== h_incoming_shuf_up =====
36174 B, swap order of highlighted directory and the one before it.
36175 Press ^C to cancel.
36176 ====== h_incoming_shuf_down =====
36177 F, swap order of highlighted directory and the one after it.
36178 Press ^C to cancel.
36179 ====== h_dir_shuf =====
36180 U, swap order of highlighted directory and the one above it.
36181 D, swap order of highlighted directory and the one below it. ^C to cancel.
36182 ====== h_dir_shuf_up =====
36183 U, swap order of highlighted directory and the one above it.
36184 Press ^C to cancel.
36185 ====== h_dir_shuf_down =====
36186 D, swap order of highlighted directory and the one below it.
36187 Press ^C to cancel.
36188 ====== h_hdrcolor_shuf =====
36189 U, swap order of highlighted Header Color and the one above it.
36190 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
36191 ====== h_hdrcolor_shuf_up =====
36192 U, swap order of highlighted Header Color and the one above it.
36193 Press ^C to cancel.
36194 ====== h_hdrcolor_shuf_down =====
36195 D, swap order of highlighted Header Color and the one below it.
36196 Press ^C to cancel.
36197 ========== h_oe_editab_al ============
36198 Change the address using the arrow keys and delete key. Press RETURN
36199 when done. Press ^C to cancel editing and leave the address as it was.
36200 ========== h_dir_comp_search ===============
36201 Type a string to look for just like you would in the composer. Your configured
36202 rules for the servers with the implicit flag set will be used.
36203 ========== h_oe_searchab ===============
36204 Type the word or name you want to search for and press RETURN. If you press
36205 RETURN without entering anything the word in [] will be searched for.
36206 ========== h_oe_chooseabook ==========
36207 Choose the address book you want to save the new entry in.
36208 Use ^N or ^P to change address books. ^C to cancel.
36209 ========== h_oe_takeaddr ==========
36210 Edit the e-mail address using the arrow and delete keys. Press RETURN
36211 when done. Press ^C to cancel adding this entry to the address book.
36212 ========== h_oe_take_replace ==========
36213 Press R to replace the old entry with this new data. You will still have
36214 another chance to cancel. N to enter another nickname. ^C to cancel now.
36215 ========== h_oe_take_replace_or_add ==========
36216 Press R to replace the old entry. Press A to add the selected addresses to
36217 the old existing list. N to enter another nickname. ^C to cancel now.
36218 ========== h_oe_takename ==========
36219 Edit the full name to be correct using the arrow and delete keys. Press RETURN
36220 when done. Press ^C to cancel adding this entry to the address book.
36221 ========== h_oe_takenick ==========
36222 Type a nickname (short easy-to-remember name, initials or single word) for this
36223 entry in the address book and press RETURN. Press ^C to cancel addition.
36224 ========== h_oe_jump ==========
36225 Type the message number you want to jump to and press RETURN. The word "end"
36226 represents the last message. Press ^C to cancel jumping to another message.
36227 ========== h_oe_jump_thd ==========
36228 Type the thread number you want to jump to and press RETURN. The word "end"
36229 represents the last thread. Press ^C to cancel jumping to another thread.
36230 ========== h_oe_debuglevel ==========
36231 Higher number shows more debugging details.
36232 Press ^C if you want to cancel the change.
36233 ========== h_oe_broach ==========
36234 Type the name of the folder you want to open and press RETURN. Press ^P/^N
36235 to go to the previous/next collections in the list. Press ^C to cancel goto.
36236 ========== h_oe_foldsearch ==========
36237 Type the text you want to search for in foldernames and press RETURN. If you
36238 press RETURN without entering anything, any text in [] will be searched for.
36239 ========== h_oe_foldrename ==========
36240 Change the old name of the folder to the new name using the arrow and
36241 delete keys and press RETURN. Press ^C to cancel rename.
36242 ========== h_oe_login ==========
36243 Enter your login name for the host you are opening the mailbox on. Just press
36244 RETURN to use your login from this host as is, or edit it with delete key.
36245 ========== h_oe_passwd ==========
36246 Type your password for the host and login shown as part of the prompt.
36247 Press ^C to cancel opening folder.
36248 ========== h_oe_choosep ==========
36249 Enter the number associated with the printer you want to select. Press ^C to
36250 cancel the printer selection. The current selection is highlighted.
36251 ========== h_oe_customp ==========
36252 Type the name of the Unix print command and press RETURN. Press ^C to
36253 cancel the printer selection.
36254 ========== h_oe_searchview ==========
36255 Type the word or name you want to search for and press RETURN. If you press
36256 RETURN without entering anything the word in [] will be searched for.
36257 ========== h_oe_keylock ==========
36258 The keyboard is in use and locked by another user. Only that user can
36259 unlock this keyboard by typing the password.
36260 ========== h_wt_expire ==========
36261 At the beginning of each month Alpine offers to rename your current sent-mail
36262 folder to one named for the month so you have a sent-mail folder for each month
36263 ========== h_wt_delete_old ==========
36264 It is the beginning of the month, and we need to conserve disk
36265 space. Please delete any sent-mail that you do not need.
36266 ========== h_select_sort ==========
36267 Select the order for sorting the index by typing the capitalized letter.
36268 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
36269 ========== h_no_F_arg ============
36270 Enter name of file to be opened.
36272 ========== h_sticky_personal_name ==========
36273 Type in your name as you want it to appear on outgoing email. This entry
36274 will be saved into your Alpine configuration file.
36275 ========== h_sticky_inbox ============
36276 INBOX syntax is usually {complete.machine.name}INBOX
36277 This entry will be saved in your Alpine configuration file.
36278 ========== h_sticky_smtp ============
36279 The name of the computer on your campus that relays your outgoing email
36280 to the Internet. This entry will be saved in your Alpine configuration file.
36281 ========== h_sticky_user_id ==========
36282 The username or login-id part of your email address. This entry will be
36283 saved in your Alpine configuration file.
36284 ========== h_sticky_domain ==========
36285 The domain part of your email address, NOT the name of your PC. This
36286 entry will be saved in your Alpine configuration file.
36287 ========== h_bounce =========
36288 Enter the address or nickname of the intended recipient. Alpine will resend
36289 the message, which will retain the original author's From: address.
36290 ========== h_incoming_add_folder_nickname =========
36291 Enter an (optional) nickname that will be used in lieu of the actual
36292 host and folder names in the FOLDER LIST display.
36293 ========== h_anon_forward ==========
36294 Enter the address of your intended recipient, or ^C to cancel.
36295 Example: jsmith@somewhere.edu
36296 ========== h_news_subscribe ==========
36297 Enter the name of the newsgroup to which you wish to subscribe,
36298 or ^C to cancel. Example: comp.mail.pine
36299 ========== h_pipe_msg ==========
36300 Enter the name of the Unix command to which you wish to send this
36301 message, or ^C to cancel.
36302 ========== h_pipe_attach ==========
36303 Enter the name of the Unix command to which you wish to send this
36304 attachment, or ^C to cancel.
36305 ========== h_select_by_num ==========
36306 Enter a list of message numbers (or number ranges), or ^C to cancel. The word
36307 "end" represents the last message. Example: 2-5,7-9,11,19,35-end
36308 ========== h_select_by_thrdnum ==========
36309 Enter a list of thread numbers (or number ranges), or ^C to cancel. The word
36310 "end" represents the last thread. Example: 2-5,7-9,11,19,35-end
36311 ========== h_select_txt_from ==========
36312 Messages with From: headers containing the entered string will be selected.
36313 ^C to cancel. ^G again to see original options.
36314 ========== h_select_txt_not_from ==========
36315 Messages without From: headers containing the entered string will be selected.
36316 ^C to cancel. ^G again to see original options.
36317 ========== h_select_txt_to ==========
36318 Messages with To: headers containing the entered string will be selected.
36319 ^C to cancel. ^G again to see original options.
36320 ========== h_select_txt_not_to ==========
36321 Messages without To: headers containing the entered string will be selected.
36322 ^C to cancel. ^G again to see original options.
36323 ========== h_select_txt_cc ==========
36324 Messages with Cc: headers containing the entered string will be selected.
36325 ^C to cancel. ^G again to see original options.
36326 ========== h_select_txt_not_cc ==========
36327 Messages without Cc: headers containing the entered string will be selected.
36328 ^C to cancel. ^G again to see original options.
36329 ========== h_select_txt_subj ==========
36330 Messages with Subject: headers containing the entered string will be selected.
36331 ^C to cancel. ^X enters Subject: line of current message.
36332 ========== h_select_txt_not_subj ==========
36333 Messages without Subject headers containing the entered string will be selected.
36334 ^C to cancel. ^X enters Subject: line of current message.
36335 ========== h_select_txt_all ==========
36336 All messages containing the entered string will be selected. Headers and body,
36337 but not encoded attachments, will be compared. Enter ^C to cancel.
36338 ========== h_select_txt_not_all ==========
36339 All messages that don't contain the entered string will be selected. Headers
36340 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
36341 ========== h_select_txt_body ==========
36342 All messages containing the entered string will be selected. Body text, but
36343 not headers or encoded attachments, will be compared. ^C to cancel.
36344 ========== h_select_txt_not_body ==========
36345 All messages that don't contain the entered string will be selected. Body
36346 text, but not headers or encoded attachments, will be compared. ^C to cancel.
36347 ========== h_select_txt_recip ==========
36348 Messages with Cc: or To: headers containing the entered string will be selected.
36349 ^C to cancel. ^G again to see original options.
36350 ========== h_select_txt_not_recip ==========
36351 Messages without Cc: or To: headers containing the string will be selected.
36352 ^C to cancel. ^G again to see original options.
36353 ========== h_select_txt_partic ==========
36354 Messages with Cc, To, or From headers containing the string will be selected.
36355 ^C to cancel. ^G again to see original options.
36356 ========== h_select_txt_not_partic ==========
36357 Messages without Cc, To, or From headers containing the string will be selected.
36358 ^C to cancel. ^G again to see original options.
36359 ========== h_select_date ==========
36360 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
36361 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
36362 ========== h_attach_index_whereis ==========
36363 Enter some text that appears in the Attachment Index entry for the desired
36364 attachment. The first attachment containing that text will be highlighted.
36365 ========== h_kb_lock ==========
36366 Keystrokes entered here (up to a RETURN) comprise a password that must
36367 be entered again later in order to unlock the keyboard.
36368 ========== h_compose_default ==========
36369 N, compose a new message. R, set a role.
36370 ^C to cancel.
36371 ========== h_untranslatable ==========
36372 Send using UTF-8 character set; Send but replace untranslatable characters
36373 with question marks; return to the composer; or cancel message altogether.
36374 ========== h_compose_intrptd ==========
36375 N, compose a new msg. I, continue interrupted msg. R, set a role.
36376 ^C to cancel.
36377 ========== h_compose_postponed ==========
36378 N, compose a new message. P, continue postponed msg. R, set a role.
36379 ^C to cancel.
36380 ========== h_compose_intrptd_postponed ==========
36381 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36382 R, set a role. ^C to cancel.
36383 ========== h_compose_form ==========
36384 N, compose a new message. F, use form letter. R, set a role.
36385 ^C to cancel.
36386 ========== h_compose_intrptd_form ==========
36387 N, compose a new msg. I, continue interrupted msg. F, use form letter.
36388 R, set a role. ^C to cancel.
36389 ========== h_compose_postponed_form ==========
36390 N, compose a new message. P, continue postponed msg. F, use form letter.
36391 R, set a role. ^C to cancel.
36392 ========== h_compose_intrptd_postponed_form ==========
36393 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36394 F, use form letter. R, set a role. ^C to cancel.
36395 ========== h_config_context_del_except ==========
36396 If you delete the last exceptional collection you can only add it back by
36397 manually editing the exceptions config file.
36398 ========== h_config_whereis ==========
36399 To move quickly to a particular line, enter a search string or
36400 ^C to cancel.
36401 ========== h_config_edit_scorei ==========
36402 Enter interval in the form (min,max). -INF and INF may be used to represent
36403 -infinity and infinity. ^C to cancel change. RETURN to accept change.
36404 ========== h_config_add ==========
36405 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
36406 pressing RETURN sets the Empty Value (this turns off any global default).
36407 ========== h_config_add_custom_color ==========
36408 Enter a header fieldname. For example, "subject" or "from".
36410 ========== h_config_add_pat_hdr ==========
36411 Enter a header fieldname. For example, "reply-to" or "organization" or
36412 any fieldname you want that isn't included already.
36413 ========== h_config_print_opt_choice ==========
36414 You may edit either the initialization string (characters printed before
36415 printing starts) or the trailer string. Choose one or ^C to cancel.
36416 ========== h_config_print_init ==========
36417 Enter a C-style string for this. You may use common backslash escapes like
36418 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
36419 ========== h_config_change ==========
36420 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
36421 delete current (highlighted) character, etc. Enter ^C to cancel change.
36422 ========== h_config_replace_add ==========
36423 Replace ignores the current default, Add places the current default in your
36424 editing buffer as if you had typed it in.
36425 ========== h_config_insert_after ==========
36426 Enter a nickname for this print command. (InsertBefore puts the new item
36427 before the current line, InsertAfter puts it after the current line.)
36428 ========== h_config_print_cmd ==========
36429 Enter command to be executed for the printer. Use normal editing keys
36430 to modify, ^C to cancel, carriage return to accept current value.
36431 ========== h_config_role_del ==========
36432 Answering Yes will remove this rule completely from your rules list.
36433 ========== h_config_role_addfile ==========
36434 Type the name of a file to add to your configuration. You don't need to
36435 use a file, you may add rules directly (with Add) without using a file.
36436 ========== h_config_role_delfile ==========
36437 Answering Yes will remove this rule file completely from your rules list.
36438 The rules data file itself will not be removed.
36439 ========== h_config_print_del ==========
36440 Answering Yes will remove this printer completely from your printer list.
36441 ========== h_config_print_name_cmd ==========
36442 You may edit the Nickname of this printer, the Command to be executed when
36443 printing, or change the Options associated with this printer.
36444 ========== h_send_check_fcc ==========
36445 Yes, send message without an Fcc.
36446 No, return to composer.
36447 ========== h_send_check_subj ==========
36448 Yes, send message without a Subject.
36449 No, return to composer.
36450 ========== h_send_check_to_cc ==========
36451 Yes, send message without a To address, or a Cc address, or a Newsgroup.
36452 No, return to composer.
36453 ========== h_send_fcc_only ==========
36454 Yes, copy message to Fcc only and send to NO recipients.
36455 No, return to composer.
36456 ========== h_send_prompt ==========
36457 Yes, send the message.
36458 No or ^C, return to composer.
36459 ========== h_send_prompt_flowed ==========
36460 Yes, send the message. No or ^C, return to composer.
36461 What's Flowed? See Do Not Send Flowed Text in config screen.
36462 ========== h_send_prompt_dsn ==========
36463 Yes, send the message. No or ^C, return to composer.
36464 What's DSNOpts? See Enable Delivery Status Notification in config screen.
36465 ========== h_send_prompt_dsn_flowed ==========
36466 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
36467 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
36468 ========== h_role_confirm ==========
36469 Yes, use displayed role. No, compose without a role.
36470 ^C, cancel the message. ^T, select a role from your other eligible roles.
36471 ========== h_norole_confirm ==========
36472 Return, compose without a role.
36473 ^C, cancel the message. ^T, select a role from your eligible roles.
36474 ========== h_custom_print ==========
36475 Enter a Unix command that accepts its data on standard input.
36476 Alpine will display any information the command sends to standard output.
36477 ========== h_convert_abooks_and_sigs ==========
36478 You will be given the opportunity to convert address books and signature files
36479 to remote configurations.
36480 ========== h_convert_abooks ==========
36481 You will be given the opportunity to convert address books to remote
36482 configurations.
36483 ========== h_flag_keyword ==========
36484 Enter the name of the keyword you want to add for this folder.
36485 No spaces, parentheses, braces, percents or asterisks are allowed.
36486 ========== h_select_keyword ==========
36487 Enter the keyword you want to match, or use ^T to select a keyword from a list
36488 of possible keywords for this folder. Use ! to look for non-matches instead.
36489 ========== h_type_keyword ==========
36490 Enter the keyword you want to add. You may add a nickname in the next step.
36491 No spaces, parentheses, braces, percents or asterisks are allowed.
36492 ========== h_type_keyword_nickname ==========
36493 Enter an optional nickname for the keyword you want to add.
36494 Type Carriage return to use the keyword name instead of a nickname.
36495 ========== h_convert_sigs ==========
36496 You will be given the opportunity to convert signature files to remote
36497 configurations.
36498 ========== h_convert_abook ==========
36499 Yes is fairly safe. You will be ADDing a remote address book that is a copy
36500 of the current address book. The current abook won't be removed automatically.
36501 ========== h_convert_sig ==========
36502 Answering Yes copies the contents of the signature file into your Alpine
36503 configuration file. After that, the contents of the file will not be used.
36504 ========== h_save_addman ==========
36505 Enter the simple name of the folder you want to add. Carriage return to
36506 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
36507 ========== h_reopen_folder ==========
36508 Yes reopens the folder, as if you were starting over. This uncovers new mail.
36509 No leaves the folder index as it was without discovering new mail.
36510 ========== h_convert_pinerc_server ==========
36511 This is the name of the host (computer) where the remote Alpine configuration
36512 will be stored. This should be an IMAP server that you have permission to use.
36513 ========== h_convert_pinerc_folder ==========
36514 Enter the correct remote folder name. This folder is special and should
36515 contain only configuration data. It shouldn't contain other mail messages.
36516 ========== h_role_compose ==========
36517 Compose a New message, Reply to current message, Forward current message, or
36518 Bounce message. Then you will be asked to choose one of your Roles to be used.
36519 ========== h_save_size_changed ==========
36520 The reported size of a message is not the same as the actual size. Answer Yes
36521 to continue and hope for the best or No to Cancel the entire Save.
36522 ========== h_select_by_larger_size ==========
36523 Enter a number or ^C to cancel. All messages greater than this many characters
36524 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36525 ========== h_select_by_smaller_size ==========
36526 Enter a number or ^C to cancel. All messages less than this many characters
36527 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
36528 ========== h_preserve_field ==========
36529 Use 'p' to toggle between preserving or not preserving the original To:
36530 and Cc: fields of the message. Enter ^C to cancel message.