1 # $Id: pine.hlp 1266 2009-07-14 18:39:12Z hubert@u.washington.edu $
3 # T H E A L P I N E M E S S A G E S Y S T E M
5 #/* ========================================================================
6 # * Copyright 2013-2017 Eduardo Chappa
7 # * Copyright 2006-2008 University of Washington
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
13 # * http://www.apache.org/licenses/LICENSE-2.0
15 # * ========================================================================
18 Help text for the Alpine mailer
20 This file is in a format created to be turned into text strings in a C
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.
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
44 1a) Default and function key bindings are separated like this:
46 <!--chtml if pinemode="function_key"-->
47 Function key bindings here
49 Default key bindings here
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
60 Text displayed when HTML viewed outside pine (using chtml aware server)
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
69 Text displayed otherwise
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:
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
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
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:
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 222 2017-09-29 23:39:51
144 ============= h_news =================
147 <TITLE>RELEASE NOTES for Alpine</TITLE>
150 <H1>Alpine Release Notes</H1>
152 Version <!--#echo var="ALPINE_VERSION"--> (<!--#echo var="ALPINE_REVISION"-->)
154 <!--chtml if pinemode="running"-->
155 (built <!--#echo var=ALPINE_COMPILE_DATE-->)
159 <BR>Copyright 2013-2017 Eduardo Chappa
160 <BR>Copyright 2006-2008 University of Washington
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
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.
183 <LI> NTLM authentication support with the ntlm library, in Unix systems.
184 Based on code provided by Maciej W. Rozycki.
188 Bugs that have been addressed include:
190 <LI> Crash when attempting to bounce a message due to lack of space in
191 allocated space for key menu array. Reported by David Sewell.
193 <LI> Crash when a CA certificate failed to load, and user attempted to
194 view certificate information of other certificate authorities.
196 <LI> Deactivate some color code from Pico (as standalone editor in the
197 windows version) until I find a way to activate it again. This is
198 not critical and it is not something that PC-Pico must have (some
199 of it already exists in other ways, like color support, what does
200 not exist is the more complex code that Unix-Pico has with color
201 codes for specific colors.)
203 <LI> Update build.bat file to add /DWINVER=0x0501 so that Alpine can
204 build when using Visual Studio 2017. Fix contributed by
205 Ulf-Dietrich Braunmann.
209 Version 2.21 addresses bugs found in previous releases and has several
215 <LI> PC-Alpine: New configuration option "Aspell Dictionaries" allows a
216 user to choose the dictionary used to spell check, in case the user
217 communicates in more than one language. Examples of values for the
218 variable are "en_US" or "de_DE", etc. Only the first 10
219 dictionaries are offered.
221 <LI> Unix-Alpine: Connect securely to a LDAP server on a secure port.
222 Based on a contribution by Wang Kang.
224 <LI> Colors configured in Alpine are inherited in the composer.
226 <LI> When Alpine is compiled with password file and SMIME support
227 the password file is encrypted using a private key/public
228 certificate pair. If one such pair cannot be found, one will be
229 created. <A HREF="h_password_file_support">Learn more</A>.
231 <LI> Alpine builds with any version of OpenSSL greater than or equal
232 to 1.0.0c. This includes version 1.1.0. Alpine also builds with
235 <LI> New SHORTSUBJECT, SHORTSUBJKEY and SHORTSUBJKEYINIT token for index
236 format, which removes text in the SUBJECT between "[" and
239 <LI> New SMARTTIME24 token for index screen. It is close to SMARTDATETIME
240 but it differns in that it gives the time in which the message was
241 sent for messages that are less than a week old. it uses a 24 hour
244 <LI> Alpine will include attachments when forwarding some
245 multipart/alternative messages for which it did not use to include
248 <LI> New configuration option
249 <a href="h_config_alt_reply_menu"><!--#echo var="FEAT_alternate-reply-menu"--></a>
250 which adds more ways to control features and variables when you
251 start to reply to a message.
253 <LI> Added support for RFC 2971 - IMAP ID extension.
255 <LI> Add configuration <A href="h_config_ignore_size"><!--#echo var="FEAT_ignore-size-changes"--></A>
256 that allows users to ignore errors in the computation of the size
257 of a message from defective servers.
259 <LI> SMIME: Upgrade the default signature digest from sha1 to sha-256, since
260 clients such as Thunderbird do not validate signatures that use sha1 digest.
262 <LI> Add the configuration variable "default-directories", which is called
263 <A href="h_config_history"><!--#echo var="VAR_default-directories"--></A>
264 variable saves a list of directories that are readily accessible
265 for save or export of attachments. This makes it easier to save
266 attachments in directories that are hard to navigate to, or that
267 are accessed frequently.
269 <LI> When a filename is attached and its name is encoded, the save
270 attachment command will offer to save the file in the encoded form.
271 This might work for some users, but the save command will have a
272 subcommand ^N to decode the file name and save the file with the
275 <LI> The TAB key allows autocomplete in the Fcc field in the composer headers,
276 as well as autocompletes automatically when only one possibility exists
277 for the ^J attach command.
279 <LI> Add support for the "TYPE" and "VALUE" attributes of
282 <LI> Ignore message from smtp server after a successful authentication
285 <LI> When a message is saved in the Form Letter folder, add the ability
286 to save the role being used to compose such message so that settings
287 such as the SMTP server set in the role can be used when sending
288 such form message. Suggested and patched by Frank Doepper.
290 <LI> If SSLDIR is defined somehow, do not disable S/MIME if the
291 SSLCERTSDIR is not found.
293 <LI> When Alpine sends an attachment, it will set the boundary attribute
294 in lower case, as some SMTP servers, such as those of libero.it
295 reject messages if the boundary attribute is in uppercase.
297 <LI> Add the ability to change the private key and certificates used
298 to encrypt a password file in the SMIME setup configuration screen.
299 <A HREF="h_config_smime_password_file_certificates">Learn more</A>
301 <LI> SMIME: The ctrl-E command that gives information on the certificate
302 is only available for messages that have a signed or encrypted
305 <LI> SMIME: If a message contains a RFC822 attachment that is
306 signed/decrypted add the ability to view its SMIME information.
308 <LI> SMIME: Certificate information in the S/MIME screen is available
309 for certificates stored in a container.
311 <LI> SMIME: Offer the common name of the person, instead of the name of
312 file containing the certificate, as the name to be displayed in the
313 certificate management screen for certificate authorities.
314 Suggested by Matthias Rieber.
316 <LI> SMIME: Management of several alternate name (SAN) certificates is
317 improved. When importing a SAN certificate, also import a certificate
318 for the filename, besides for the e-mail addresses in the
319 certificate. Suggested by Matthias Rieber.
321 <LI> SMIME: add full year when displaying information about a certificate
322 in the certificate management screen. Suggested by Matthias Rieber.
324 <LI> SMIME: sort certificates by some type of alphabetical order in the
327 <LI> SMIME: Alpine will ask users if they wish to save S/MIME
328 certificates included in signatures, when the option "Validate
329 Using Certificate Store Only" is enabled. If the user does not wish
330 to save it, validation will fail.
332 <LI> HTML: Add support for decoding entities in hexadecimal notation.
333 Suggested by Tulipánt Gergely.
335 <LI> The "#" command, when used as part of an aggregate
336 operation will allow users to select the role used in either
337 replying, forwarding or replying to the group of selected messages,
338 Suggested by Hisashi T Fujinaka.
340 <LI> If the charset of a message can not be determined, use the value set
341 in the <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A> for its value.
343 <LI> Resizing setup screen will redraw screen.
345 <LI> Unix Alpine only. Experimental: If Alpine/Pico finds a UCS4 code
346 in the width ambiguous zone, it will use other means to determine
347 the width, such as call wcwidth.
349 <LI> Pico: Code reorganization in the search command to make it easier to
350 add subcommands of the search command.
352 <LI> Pico: Search command can do a case sensitive match. Use the Ctrl-^
353 subcommand of the search command to bring this choice into view.
355 <LI> Pico: Add the ability to search for strings in the beginning or end
356 of a line. Use the Ctrl-^ subcommand of the search command to bring
357 this choice into view.
359 <LI> For a multipart/alternative message, the Take Address command will
360 work on the part that is being read.
362 <LI> When sending a message, allow for 512 characters of consecutive
363 non-white space before folding the subject line.
365 <LI> Make sure titlebar (the line at the top of the screen) always
366 contains the name of the folder/newsgroup that is open, if this
369 <LI> The feature <a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
370 will also scramble the name, version and operating system in the
371 message-id header. Based on a contribution by Dennis Davis, which
372 is itself based on a contribution by Mark Hills.
374 <LI> Change in logic in imap_set_password function to make Alpine ask if
375 a user wants to save a password before reading the password file.
377 <LI> When exporting all parts of a message, if two attachments have the same
378 name, do not overwrite a file more than once, but instead add a counter
379 number to the filename to make a new file that does not exist in the file
382 <LI> Add the Control-R subcommand to the save command for attachments.
383 This subcommand toggles if the saving will be done in binary mode
384 for text attachments. When a user saves an attachment using binary
385 mode it will be saved as it was sent, otherwise the attachment will
386 be transformed to UTF-8 for further transformation through internal
387 and user defined filters for saving.
389 <LI> Add command line argument -smimedir, which allows to specify
390 the default path for a directory that contains the public, private,
391 and ca directories. This is useful in case a user has a backup of
392 old certificates that cannot be installed in the ~/.alpine-smime
395 <LI> Reimplementation of the code that allows the .pinerc file to be a
396 symbolic link by Kyle George from tcpsoft.com to use realpath.
398 <LI> When saving an attachment, the "^T" command leads to a screen where the
399 "A" command can be used to add a file. A directory can be added by
400 pressing "^X" after the "A" command. Added after a suggestion by
403 <LI> When saving an attachment, the ^Y and ^V commands allow a user to
404 scroll through the history of directories used to save attachments,
405 while preserving the given name of the file. Suggested by Peter
408 <LI> SMIME: Turn off automatic signing and encrypting of a message when
409 bouncing. Suggested after a discussion with Matthias Rieber.
411 <LI> When messages are selected, warn the user if a message that is not
412 selected will be bounced, or if not all selected messages will be
413 bounced. Suggested by Ulf-Dietrich Braumann.
415 <LI> The bounce command adds a subcommand to choose a role.
417 <LI> When selecting messages by number, the "." character can
418 be used to specify the message on which the cursor is on.
420 <LI> When Alpine opens an attachment, it sometimes changes the extension
421 of the file that is being opened and replaces it by another for the
422 same mime type. If Alpine finds that the extension of the file
423 corresponds with the mime type, according to the mime-types file,
424 then it will keep it, and no substitution will be made.
426 <LI> Set no restrictions on the length of encoded subjects, but encode
427 words in length of no more than 75 characters.
432 Bugs that have been addressed include:
434 <LI> SMIME: Crash when a certificate has an invalid date of validity. Also
435 Alpine will use the function ASN1_TIME_print to determine the date
436 of validity. Reported by Ben Stienstra.
438 <LI> SMIME: Crash when attempting to unlock the password file and an
439 incorrect password is entered.
441 <LI> SMIME: Crash when checking the signature of a message that contains
442 a RFC822 attached message. Reported by Holger Trapp and Björn
445 <LI> SMIME: Cancelling entering password to unlock key will not reprompt.
447 <LI> SMIME: fix a bug that did not allow users to transfer certificates to
448 remote containers. Reported by Matthias Rieber.
450 <LI> SMIME: certificates included in messages were not being transferred
451 to a remote container.
453 <LI> SMIME: Crash if public certificates are located in an inaccessible
454 remote server and the private key is not available.
456 <LI> SMIME: Alpine does not remove temporary files created when adding a
457 CA certificate to a container. Reported by Holger Trapp.
459 <LI> SMIME: When reading a local certificate, Alpine converts the name
460 of the certificate to lowercase, which may make Alpine not be able
461 to read such certificate. Reported by Dennis Davis.
463 <LI> SMIME: If the option "Remember S/MIME Passphrase" is disabled, then
464 entering a password to read an encrypted message will make Alpine
465 forget the key and not ask the password to unlock it again in case
466 it is necessary to unlock it again. Reported by Ulf-Dietrich
469 <LI> Alpine would use freed memory while trying to compute the color
470 of the titlebar. This happened when trying to continue a postponed
473 <LI> Alpine failed to read an encrypted password file if too many
474 passwords were saved in the password file.
476 <LI> When selecting messages while in Threaded Index Screen, some
477 messages other than top of threads could appear in the index, making
478 Alpine display messages "out of the screen."
480 <LI> The index format would be chopped at the position of an unrecognized
481 token, instead of skipping the token as intended.
483 <LI> Work in progress: Avoid calling non-safe functions when Alpine
484 receives a signal. See bug report
485 <A HREF="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825772">here.</A>
487 <LI> Crash when attempting to read a message after a bounce command.
488 In order to produce a crash one needed to use the ^T subcommand and
489 do a search in a LDAP directory. The crash is produced by changes
490 to the text in the title bar. Reported by Heinrich Mislik in the
493 <LI> HTML messages that contain UTF-8 may wrap at the wrong position,
494 making Alpine not display the correct character at the position
495 that wrapping is done. Reported by Wang Kang.
497 <LI> Pico: Searching for a string that is too long causes Pico to crash
500 <LI> Fix vulnerability in regex library. This only affects those who use
501 this library, such as the windows version of Alpine. See
502 <A HREF="http://www.kb.cert.org/vuls/id/695940">http://www.kb.cert.org/vuls/id/695940</A>
505 <LI> Alpine would not set include and lib paths for OpenSSL if this was
506 installed in /usr/local/ssl.
508 <LI> If the .pinerc file is a symbolic link, Alpine might not write its
509 contents when saving its configuration.
511 <LI> The _INIT_ token does not skip over non-alphanumeric characters in
512 the name. Reported by Andreas Fehr.
514 <LI> When opening an INBOX folder in a context different from the
515 incoming folders collection, from the command line, Alpine would
516 open the INBOX folder from the incoming folders collection.
518 <LI> Mismatch in size of UCS and CELL caused a corruption in the
519 content of a pointer, which made the speller in PC-Alpine get the
520 content of a word incorrectly.
522 <LI> Skip testing openssl compatibility version when cross-compilation
523 is detected. Fix contributed by Antti Seppälä
525 <LI> Alpine fails to remove temporary files used during a display or sending
526 filter. Fix contributed by Phil Brooke.
528 <LI> When the index is in zoomed state, adding new messages to the
529 selection would not show those messages if those messages are on
530 top of the current message in the top of the screen. Reported by
531 Ulf-Dietrich Braumann. In addition, when the user scrolls through
532 the index, this scroll smoothly, without jumping pages. Reported
535 <LI> Crash when reviewing history of saving attachments.
537 <LI> Crash when canceling a goto command on a local collection that has
538 not been expanded and attempting to expand such collection.
540 <LI> Crash in Pico when forwarding messages that contain a direction mark
541 at the end of a line. Reported by James Mingo.
543 <LI> Solve compilation errors when Alpine is built with Visual Studio 2015.
548 Version 2.20 addresses bugs found in previous releases and has several
556 <LI> Upgrade UW-IMAP to Panda IMAP from
557 <A HREF="https://github.com/jonabbey/panda-imap">https://github.com/jonabbey/panda-imap</A>.
558 <LI> S/MIME: Add screen to manage certificates.
559 <LI> S/MIME: Signatures are validated using the user's certificates instead
560 of the ones included in the message. Behavior can be disabled by
561 disabling the option <A href="h_config_smime_use_cert_store">
562 <!--#echo var="FEAT_smime-use-storey-only"--></A>, which is enabled
564 <LI> S/MIME: sign messages using intermediate certificates when needed
566 <LI> S/MIME: validation of certificates for servers that modify signed
568 <LI> S/MIME: signed and encrypted messages will be signed first and
569 encrypted second, so that they can be decoded by other clients.
570 <LI> S/MIME: add the sender certificate to the list of certificates in
571 encrypted messages to make it possible for the sender to decrypt
572 the message they sent.
573 <LI> S/MIME: When transferring certificates to a local container, create
574 container with default names PublicContainer, PrivateContainer and
575 CAContainer, as appropriate for these files, unless the user has
576 provided some other names.
577 <LI> S/MIME: Forwarding a message will include the signed part as part
578 of the text and not as a multipart message, just as the reply
580 <LI> HTML: Style tag in body of html message causes Alpine to not write
581 its content until a new </style>
582 <LI> HTML: <BR>, <BR />, and <BR/> are considered
583 the same inline tag; the same is valid for the <HR> tag.
584 <LI> Add support to selective expunge through a subcommand of the
585 select-apply commands. Read more in the <A
586 HREF="h_index_cmd_expunge">help</A> for the expunge command.
587 <LI> Pico: New subcommand of the search command, allows to reverse the
589 <LI> Unix Alpine: If a password file is defined, and S/MIME is enabled,
590 the key and certificate used to encrypt the password file are saved
591 in the ~/.alpine-smime/.pwd directory, or in the directory specified
592 by the -pwdcertdir command line option.
593 <A HREF="h_password_file_support">Learn more</A>.
594 <LI> Add /tls1, /tls1_1, /tls1_2 and /dtls1 to the definition of a
595 server to use different ways to connect using ssl, for
596 example {server.com/tls1} will attempt to connect to
597 server.com at the ssl imap port (port 993) and establish a
598 connection using TLSv1. These flags can be used in
599 conjunction with the /ssl flag, the ssl flag is redundant.
600 Conversely, however, the /ssl flag does not imply any of
601 these flags; the /ssl flag means SSLv3 or, if not available,
602 SSLv2 in the SSL port.
603 <LI> Alpine does not attempt to automatically reopen a collection
604 that was not opened due to cancellation by the user.
605 Instead, the user must try to open it explicitly.
606 <LI> Alpine searches for a certificate that matches an email address in
607 all addresses in a certificate (instead of just the first
608 one) but when it tries to unlock the certificate, it asks
609 for the password for the first email address in that
611 <LI> Style tag in body of html message causes Alpine to not write its content
612 until a new </style>
613 <LI> Experimental: Write the content-type of a message in
614 lowercase, as some non-compliant servers do not understand
615 uppercase content-type, such as those of GMX.de.
616 <LI> Experimental: Do not send the RSET command before attempting
617 to send a message, as this causes a delay in some evily managed
619 <LI> Opening a folder updates recent count in maildrops (this
620 already works for other types of folders)
621 <LI> Automatically redraw screen after opening an attachment
622 instead of simply clearing it.
623 <LI> Pico: Justification works without need of a predefined quote
624 string. This allows justification of blocks of text that are
625 indented with spaces.
626 <LI> Decode the name of attachment names, so they can be written as part
627 of the description of the part.
628 <LI> Check bounds and tie strings off to improve security. Contributed
630 <LI> Replace tabs by spaces in From and Subject fields to control for
631 size in screen of these fields. Change only in index screen display.
632 <LI> Aggregate operations allows bouncing a list of messages using a role.
633 Suggested by Ulf-Dietrich Braumann.
634 <LI> Disable saving new passwords to the password file. Implemented
635 by Louis Raphael from dpslabs.com. <A HREF="h_config_disable_password_file_saving">Learn more.</A>
636 <LI> Makefile: Add $(LIBINTL) to the flags to link rpdump, rpload,
637 alpined and alpineldap because MAC OSX 10.8 x86_64 needs it. Reported by
643 Bugs that have been addressed include:
645 <LI> Fix _INIT_ token for reply quote string to include support for 8-bit
646 in personal names. Reported by Lev Gorenstein.
647 <LI> When writing the .pinerc file, lines were truncated if they were longer
648 than 10,000 characters. This could cause data corruption, so now lines
649 are allowed to be of any length.
650 <LI> In Unix Alpine (but not in MAC OSX) fix a problem that made Alpine
651 remove attachments before they were open by a mailcap viewer. It
652 requires that the user has an equivalent to a command such as "ps
653 auxww" to list the list of processes, and check if there is any
654 program using the attachment. The default is "/bin/ps auxww", but
655 it can be changed at compile time with the option --with-ps-cmd.
656 See the help of the variable
657 <a href="h_config_psleep"><!--#echo var="VAR_mailcap-check-interval"--></a>
658 for more information.
659 <LI> S/MIME: signed messages that contained an attachment would not validate.
660 <LI> S/MIME: signed and encrypted messages from Thunderbird would not
661 validate. Thanks to Andreas Schamanek for testing, debugging and
662 advising during the process of fixing this problem.
663 <LI> S/MIME: Forwarding messages with multipart content-type failed to be signed
664 with "Error writing pipe" message. Reported by Andreas Schamanek
666 <LI> S/MIME: Certificates are lost when using a pinerc file outside of the
668 <LI> S/MIME: Accessing the S/MIME configuration screen would deinitialize
669 SMIME making it not possible to sign or encrypt messages.
670 <LI> S/MIME: Forwarding a signed message might make the body contain mime
671 information that is not part of the body, and hence making the body
672 of the message seem wrong.
673 <LI> S/MIME Alpine would compute incorrectly the signature of a message
674 that contains 8bit if the option "Enable 8bit ESMTP Negotiation" is
675 enabled, the message contains 8bit characters and the smtp server
676 supports 8bit sending.
677 <LI> When replying to several messages, subject will be decoded first,
678 and then stripped from re/fwd before they are compared to determine
679 the subject of the replied message.
680 <LI> Crash when tcp connection to NNTP server was lost after connection
681 had been established, but lost immediately afterwards.
682 <LI> Crash with message "lock when already locked", when painting
683 an index was based on scores that needed information from a remote
684 addressbook in the same server as the folder opened. Reported by
686 <LI> Crash in message/rfc822 attachments encoded in base64.
687 <LI> Postponed messages whose content-type is text/html, text/enriched and
688 text/richtext are sent with that content-type, even though, after
689 resuming composition, Alpine had changed its type to text/plain.
690 <LI> Alpine cannot handle correctly some characters in the Windows-1256
691 character set, which might lead to a crash or a corruption in the
692 screen. Work was done to contain the bug. A more complete fix will
693 be done in a future release. Reported by Professor Robert Funnell.
694 <LI> WebAlpine: add _GNU_SOURCE to make pubcookie build.
695 <LI> WebAlpine: fail to build with debug disabled. Fix from Sam Hathaway.
696 <LI> Save command did not warn of existence of a message with a deleted
697 attachment in an aggregate save, unless cursor was positioned on a message
698 with a deleted attachment. Reported by Florian Herzig.
699 <LI> Transformation of UTF-8 to MUTF7 was not being done when creating a folder
701 <LI> DATE tokens were not internally transformed to UTF-8, which made their
702 values not appear complete in the screen. Reported by Werner Scheinast.
703 <LI> Fixes to configure script so that it will not require PAM for every system.
704 <LI> Fix to configure script so that it will use CPPFLAGS instead of
705 CPPCFLAGS, and so the --with-ssl-include-dir option take effect
706 during the build. Fix by Ulf-Dietrich Braumann.
707 <LI> Fix in WebAlpine: do not use deprecated dereference in pointer,
708 needs to use tcl_getstringresult() instead. Reported by
709 Ulf-Dietrich Braumann.
710 <LI> Quoted string in URL Viewers configuration variable were not
711 unquoted before passing to viewer.
712 <LI> Fix in configure script to detect location of tcl library; add
713 /usr/local in FreeBSD and fix a bug in configure script that used
714 $alpine_TCLINC instead of $alpine_TCLINC/tcl.h. Reported and fixed
716 <LI> Move SSL configurations from UW-IMAP to configure script, and
717 update OpenSSL configuration for Mac OS X.
718 <LI> Remove -lregex from linker flags when building --with-supplied-regex.
719 <LI> When the download of an attachment is interrumpted, Alpine stills
720 caches what was downloaded, making the download incomplete for
721 subsequent calls of Alpine attempting to open the attachment. In the
722 future, Alpine will not cache any downloaded part of the attachment
723 when it is interrupted.
729 Version 2.11 addresses bugs found in previous releases and has a few
737 <LI> Alpine requires version 1.0.0c of Openssl to build.
738 <LI> Increase encryption of S/MIME encrypted messages.
739 <LI> Pico: Improvements in justification of paragraphs: lines that begin
740 with a quote string, followed by a space were considered individual paragraphs,
741 now they are considered part of a paragraph. Based on earlier joint work
743 <LI> Unix Alpine: Allow local .pinerc file to be a symbolic link.
744 <LI> Experimental extended support of recognition of UTF-8 in urls based on
745 information from <A HREF="http://url.spec.whatwg.org">http://url.spec.whatwg.org</A>.
746 <LI> Added recognition of ws and wss URIs.
747 <LI> Add ability to <A HREF="h_config_folder_color">color folder names</A>,
748 <A HREF="h_config_directory_color">directory names</A>,
749 and <A HREF="h_config_folder_list_color">text</A> in the FOLDER SCREEN.
750 <LI> Add the ability to <A HREF="h_config_indextoken_color">color any token</A>
751 used in the display of the INDEX SCREEN.
752 <LI> New option <A HREF="h_config_preserve_field"><!--#echo var="FEAT_preserve-original-fields"--></A>
753 that adds the ability to preserve To: and Cc: fields when replying to a
754 message, as specified by original sender.
755 <LI> Add a _SILENT_ token to the <A HREF="h_config_display_filters">list of tokens</A>
756 for a display filter, so that Alpine will not redraw the screen when it is unnecessary.
757 <LI> Quota command includes subcommands for printing, forwarding, etc.
761 Bugs that have been addressed include:
764 <LI> Crash when a non-compliant SMTP server closes a connection without a QUIT command.
765 <LI> Crash when resizing the screen in a configuration screen.
766 <LI> Do not bail out during a tcp timeout, instead close connection and avoid crash.
767 <LI> Do not use a shell to open a browser.
768 <LI> Configure script did not test for crypto or pam libraries.
769 <LI> Configure script attempted to build web component, even if header file tcl.h was not present.
770 <LI> Change Cygwin directory separator to "/".
771 <LI> Alpine could set List- headers, contrary to RFC 2369.
775 Version 2.10 addresses bugs found in previous releases and has a few
783 <LI> Quota report for IMAP folders that support it (press the "@" command in the index screen of such folder).
784 <LI> Search a folder for the content of any header with the ";" command.
785 <LI> Foreign characters are decoded correctly in IMAP folder names.
786 <LI> Question about breaking connection to slow servers includes their name.
787 <LI> Internal x-alpine-help: resource locator for sending links to internal help.
788 <LI> OpenSuse: Alpine find location of OpenSSL certificates.
789 <LI> Cygwin: Alpine builds without need of patch.
790 <LI> Recognition of proper mime type for docx, xlsx, and pptx files.
791 <LI> When composing a message, Alpine will create a new thread when the subject is erased.
792 <LI> Add support for strong encryption of password file when S/MIME is built in.
796 Bugs that have been addressed include:
800 <LI> Alpine will close a folder after confirming with user their intention and not reopen it.
801 <LI> Double allocation of memory in Pico.
802 <LI> Alpine does not give warning of message sent and posted upon receipt by email of message posted in newsgroup.
803 <LI> Handling of STYLE html parameter may make Alpine not display the content of a message.
804 <LI> Not recognition of environment variables in some options.
805 <LI> Not display of login prompt during initial keystrokes.
806 <LI> justification of long urls breaks them.
807 <LI> Incorrect New Mail message when envelope is not available.
808 <LI> Incorrect display of PREFDATE, PREFDATETIME and PREFTIME tokens.
809 <LI> Crash when resizing the screen after display of LDAP search.
810 <LI> Crash when redrawing screen while opening a remote folder collection.
811 <LI> Infinite loop in scrolltool function during notification of new mail.
812 <LI> No repaint of the screen after midnight was done when the SMARTDATE token is used in the index screen.
813 <LI> No display of signed and encrypted S/MIME messages.
814 <LI> Alpine will not build with OpenSSL.
815 <LI> Crash for double locking in calls to c-client.
816 <LI> Bad recognition of mime-encoded text may make Alpine not print the subject of a message.
817 <LI> Ignore the references header when threading messages
818 <LI> No update of colors in index screen after update to addressbook.
822 Version 2.01 addresses bugs found in previous releases and has a few
830 <LI> Fixed non-ASCII web alpine handling
831 <LI> Added web alpine help.
832 <LI> Allow web alpine inbox on second IMAP server.
833 <LI> Allow web alpine config reset after bad inbox-path gets set.
834 <LI> Added web alpine ability to create group contact from contact list members.
835 <LI> Backed out web alpine coercing of default sort-key of arrival to date/reverse.
836 <LI> Tidied up web alpine script layout.
837 <LI> Fixed web alpine status message ordering
838 <LI> Added web alpine Fcc setting via Contacts in Compose
839 <LI> Fixed web alpine autodraft attachment issues
840 <LI> Fixed web alpine problems with recent count maintenance
841 <LI> Fixed web alpine newmail arrival display in message list
842 <LI> Added web alpine confirmation to folder create for Move/Copy
843 <LI> Added web alpine user-domain support
844 <LI> Fixed web alpine to support INBOX-within-a-collection deletion
848 Bugs that have been addressed include:
852 <LI> In web alpine fixed delete all selected within a search result to reorient
853 correctly to whole-mailbox message list.
854 <LI> Fixed web alpine delete in view page to be sensitive to sort
855 <LI> Fixed web alpine open of folder within directory from folder manager page.
856 <LI> Fixed web alpine open of folder within directory from left column's recent cache.
857 <LI> Fixed web alpine problems with spaces in special folder names like Drafts
858 <LI> Fixed web alpine adding contacts from message list and view
859 <LI> Fixed web alpine create of non-existent fcc
860 <LI> Remove mistakenly left debugger statement in web alpine javascript.
861 <LI> Some UNIX alpine build problems fixed
862 <LI> Crash in pico and pilot when nl_langinfo returned something unrecognizable
863 or NULL. Add recognition of "646" to nl_langinfo wrapper. This is returned
864 by locale charmap call on some Solaris 8 systems.
865 <LI> MacOS Keychain logins were not working correctly with generic host names, like
866 imap.gmail.com, as opposed to specific instances like rx-in-209.google.com, causing
867 new password requests when not needed
868 <LI> Possible crash in WhereIs command while in FOLDER LIST when cursor is located on the
869 last folder in the list
870 <LI> Change to S/MIME get_x509_subject_email so that X509v3 alternative names are
871 looked for along with the email address
872 <LI> Changes to configure to get spellcheck options with work with arguments.
873 <LI> Add change from Mark Crispin of panda.com to at least minimally handle non-ascii hostname
874 returned by gethostname (iPhone can do this)
875 <LI> Fixed a bug that prevents a filter that moves a message into a local folder
876 from also setting the DELETE flag in that moved message. Fix from Eduardo Chappa.
877 <LI> Changed size of shellpath in open_system_pipe from 32 to MAXPATH. Fix from
878 Jake Scott of marganstanley.com.
879 <LI> Buffer overflow bug in c-client's tmail/dmail, fix from Mark Crispin. This
880 is not used in alpine.
881 <LI> Imapd server crash from unguarded fs_give in IDLE code, fix from Crispin.
882 Apparently this causes RIM Blackberry BIS service problems. This is not
884 <LI> Tmail uninitialized pointer fix from Neil Hoggarth. Not used in alpine.
885 <LI> Buffer overflow possibility in RFC822BUFFER routines in c-client library.
886 Fix from Ludwig Nussel of SUSE and from Crispin.
887 <LI> Include whole filename in export filename history
888 <LI> Fix display bug in pico when Replace command is canceled. Fix from Eduardo Chappa.
893 addressed bugs found in previous releases and had a few additions as well.
899 <LI> Redesigned Web Alpine interface
900 <LI> Experimental <A HREF="h_mainhelp_smime">S/MIME support</A> added
901 in UNIX versions of Alpine
902 <LI> Attempt to include the attachment filename as part of the name of the
903 temporary file used when viewing an attachment with an external program.
904 Add some randomness to that filename to make it hard to predict the filename.
905 Add a filename extension, usually derived from the type/subtype, to the
906 temporary filename. This was previously done only on Windows and MacOS X.
907 <LI> Enhance address completion in the composer (TAB command) so that it looks
908 through nicknames, fullnames, and addresses from the address book; addresses
909 from the message being viewed, if any; and the results from
910 <A HREF="h_direct_config">LDAP Directory Server</A>
911 lookups for all of the defined directory servers that have the
912 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
914 <LI> Make the default character set setting more liberal in what it will accept
915 from the UNIX nl_langinfo call and the various values of LANG seen in the wild
916 <LI> Remove the Alpine revision number from the titlebar in released versions
917 while leaving it there in snapshot versions
918 <LI> Add a <A HREF="h_config_quell_asterisks">feature</A> to suppress the
919 display of asterisks when you type a password for Alpine
920 <LI> Add line wrapping when displaying <EM>PRE</EM> formatted sections of HTML
922 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
923 feature is turned on convert not only the dates in the index screen but also
924 the dates in the MESSAGE VIEW
928 Bugs addressed in the 2.00 release included:
932 <LI> Crash when using tab-completion for selecting a Save filename
933 <LI> Make Web Alpine help text images relative for more portability
934 <LI> Fixed attach save of html parts in Web Alpine
935 <LI> Viewing, printing, exporting, replying, and bouncing of message
936 digests was broken. Replying and bouncing should not have been
937 allowed at all for digests. It would be nice to have a more standard
938 index-like view of a message digest but that has not been addressed
939 with this minor bug fix.
940 <LI> Adjust wrapping of HTML messages so that the margins specified by
941 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
942 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>
943 are observed correctly
944 <LI> Interrupt of WhereIs command in index was broken
945 <LI> The <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
946 option did not work correctly interpreting unknown characters in message headers
947 <LI> Long address lines could cause blank continuation lines
948 <LI> Save to a local default INBOX failed if the primary collection was also local,
949 which it is by default. The save went to ~/mail/inbox instead.
950 <LI> Make a default save folder of "inbox" always mean the real
951 inbox, not the inbox in the primary collection
952 <LI> Address book entries with lots of addresses would be truncated when
953 entered in the composer with a screen size wider than 270 or so charcters
954 <LI> Some fields in the index screen were truncated when the screen width was
955 wider than 256 characters
956 <LI> Crash when TABing to next folder, the next folder with new mail is a POP
957 folder, and there is a more than 10 minute pause between typing the TAB
963 addressed bugs found in previous releases and had a few additions as well.
969 <LI> Add the possibility of setting a default role
970 (see <A HREF="h_role_select">Roles Screen</A>)
971 which may be convenient if your work flow involves acting in one
972 role for a while then switching to another role and staying in the
973 new role for another period of time
974 <LI> When Saving and the IMAP server problem "Message to save shrank!"
975 is encountered, ask the user if he or she wants to continue with the
976 risky Save anyway instead of aborting. This may be helpful if your
977 IMAP server is broken in this way but be aware that it is possible there
978 was a real error instead of just a broken server implementation.
979 <LI> Some configure adjustments for Kerberos detection and
980 for SCO OpenServer 5 support
981 <LI> Hide INBOX in a collection if it also appears as an
982 <A HREF="h_config_enable_incoming">Incoming Folder</A>
983 <LI> Show asterisks for feedback when the user is typing a password
984 <LI> Performance improvement for threading of large folders
985 <LI> Previously, the search used to find
986 Pattern matches containing To patterns searched for both To
987 and Resent-To headers. The relatively complicated search this
988 produces causes problems when using some deficient IMAP servers.
989 Now the default is to look only for To headers and ignore the
990 presence of Resent-To. The previous behavior may be restored
991 with the <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> feature.
993 <A HREF="h_config_unk_char_set"><!--#echo var="VAR_unknown-character-set"--></A>
994 to help with reading malformed unlabeled messages
995 <LI><A HREF="h_config_suppress_user_agent"><!--#echo var="FEAT_suppress-user-agent-when-sending"--></A> option added
996 <LI> Map some Shift-LeftArrow escape sequences to LeftArrow
997 <LI> Add feature <A HREF="h_config_warn_if_fcc_blank"><!--#echo var="FEAT_warn-if-blank-fcc"--></A>
1001 Bugs addressed in the 1.10(962) release included:
1005 <LI> Crash when encountering certain errors from an SMTP server
1006 <LI> Crash in composer caused by overflow in replace_pat()
1007 <LI> Hang when authenticating to an SMTP server that fails with a
1008 "connection disconnected" error
1009 <LI> Bug in handling of trailing tab character in flowed text
1010 <LI> Security enhancement for mailcap parameter substitution
1011 <LI> <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>
1012 did not work if the message being replied to was not flowed text
1013 and <A HREF="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></A>
1015 <LI> Don't allow printer to be changed through hidden config screen
1016 if system administrator didn't want it to be allowed
1017 <LI> Attempts are sometimes made to set the Forwarded flag when alpine
1018 should know that it won't work, causing error messages to appear
1019 <LI> A <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
1020 of double-quote double-quote didn't work right
1021 <LI> Quoting wasn't being done to protect special characters from the
1023 <A HREF="h_config_browser"><!--#echo var="VAR_url-viewers"--></A>
1025 <LI> On MacOS X message attachments should be shown internally instead of
1026 being shown using the Mail application
1027 <LI> When replying to a message with a charset of X-UNKNOWN Alpine would
1028 sometimes set the outgoing charset to X-UNKNOWN, making the result
1030 <LI> When the sending of a message failed lines with leading spaces had one
1031 additional space inserted in each of those lines when the user
1032 was returned to the composer
1033 <LI> The <A HREF="h_index_cmd_whereis">WhereIs</A> command missed some index lines
1034 that contained non-ascii characters because it was truncating the
1035 line being searched so that it was shorter than what was visible on
1037 <LI> When composing, an attachment with a long name that causes wrapping in
1038 just the wrong place would generate an error and cause the send
1039 of the attachment to fail
1040 <LI> After calling the file browser to attach a file in the composer, a resize
1041 of the window when back in the composer would redraw the last screen that
1042 had been shown in the browser instead of the current composer screen
1043 <LI> Possible crash in index screen when encountering unparseable addresses
1044 or when using one of the PRIORITY tokens or the HEADER token in the
1045 <a href="h_config_index_format"><!--#echo var="VAR_index-format"--></a>
1046 <LI> Problems with Header Color editing if the configuration option
1047 <a href="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></a>
1048 was inadvertently changed to the Empty Value in the hidden config screen
1049 <LI> When resuming the final postponed message from an Exchange server the user
1050 could get a certificate validation failure because alpine was trying
1051 to validate the canonical name of the folder instead of the name the
1053 <LI> Windows line endings in a mimetypes file on a Unix system cause a
1054 failure to find a match
1055 <LI> Make matching of extension names case independent in mimetypes files
1056 <LI> Windows dialog boxes for entering text were not working correctly
1057 <LI> Replying to or Forwarding multipart/alternative messages which had a
1058 single text/html part did not work well
1059 <LI> Printing the print confirmation page caused a crash
1060 <LI> A To line with a long, quoted personal name could display incorrectly
1061 if it was close to the same width as the screen
1062 <LI> When <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
1063 and <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
1064 are turned on hide (0/0) when the folder is empty
1065 <LI> Folder completion while Saving didn't work if the collection being
1066 saved to was the local home directory
1071 was an evolutionary release based on
1072 <A HREF="http://www.washington.edu/pine/">Pine</A>, which was also
1073 developed at the University of Washington.
1074 It is upwards-compatible for existing Pine users.
1080 <LI> Ground-up reorganization of source code around addition
1081 of "pith/" core routine library.
1082 <LI> Fundamental improvement in Alpine's internal text handling, which
1083 is now based exclusively on Unicode. This allows displaying incoming
1084 messages and producing outgoing messages in many different languages.
1085 <LI> Ground-up reorganization of build and install procedures
1086 based on GNU Build System's autotools. NOTE, the included IMAP library
1087 build is not based on autotools, so some features will not work. However,
1088 it should get built automatically during the Alpine build process.
1089 <LI> Web-based version included built on TCL designed to run under
1090 a suitable CGI-supporting web server such as Apache.
1095 Details on changes in previous (prerelease) versions of Alpine
1096 may be found at the following URL:
1098 <CENTER><SAMP><A HREF="http://alpine.freeiz.com/alpine/release/">http://alpine.freeiz.com/alpine/release/</A></SAMP></CENTER>
1103 <H2>Getting Help</H2>
1105 <DT>Online Help</DT>
1107 Every Alpine screen and command has associated help text
1108 accessible via the "?" key (or Ctrl-G in text-input contexts).
1113 The most current source of information about Alpine,
1114 including new version availability, is the web page at
1116 <CENTER><SAMP><A HREF="http://alpine.freeiz.com/alpine/">http://alpine.freeiz.com/alpine/</A></SAMP></CENTER>
1120 Frequently Asked Questions (and answers) may be found at the following
1123 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/faq/">http://www.washington.edu/alpine/faq/</A></SAMP></CENTER>
1128 <H2>Additional Information</H2>
1130 General Alpine configuration information can be found
1131 <A HREF="h_news_config">here</A>.
1133 This is revision (<!--#echo var="ALPINE_REVISION"-->) of the Alpine software.
1134 Alpine mailbox and <A HREF="https://github.com/jonabbey/panda-imap/">IMAP</A> server
1135 access is provided by the IMAP Toolkit Environment (c-client library)
1136 version <!--#echo var="C_CLIENT_VERSION"-->.
1138 Alpine was developed until 2009 by the Office of Computing
1139 & Communications at the University of Washington in Seattle.
1140 Since then, the effort of developing Alpine has been continued by
1141 a community of volunteers who make good software even better!
1144 Alpine Copyright 2013-2017 Eduardo Chappa,
1145 <BR> Copyright 2006-2008 University of Washington.
1148 Additional legal notices can be found <A HREF="h_news_legal">here</A>,
1149 or instead you can find the Apache License, version 2.0 at the web URL:
1152 <CENTER><A HREF="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</A></CENTER>
1155 <End of Release Notes>
1158 ====== h_password_file_support ======
1161 <TITLE>Encryption for Password File Support Explained</TITLE>
1164 <H1>Encryption for Password File Support Explained</H1>
1168 <LI><A HREF="#content">Explanation</A>
1169 <LI><A HREF="#example_existing_key">Example of Use of Existing Key and Certificate</A>
1170 <LI><A HREF="#example_self_signed">Example of Creating Master Password</A>
1173 <P><A NAME="content">Unix Alpine Only.</A>
1175 <P> If your version of Alpine has been built with password file support
1176 then you can use a special file to save your passwords, and avoid typing
1177 them every time you open a connection to a remote server.
1179 <P> If, in addition, your version of Alpine was built with SMIME support, then your
1180 password file will be encrypted with a strong key. There are two ways in
1181 which this can happen: Alpine will either use a matching private key and
1182 public certificate pair that you already own, or it will create one for
1183 you, just for purposes of encrypting this file. We describe both processes
1186 <P> Initially, Alpine will scan your public and private directories for a
1187 certificate/private key pair that works. Alpine will pick the first pair
1188 that it finds that matches.
1190 <P> Once a pair has been chosen, it will be copied to the directory
1191 ~/.alpine-smime/.pwd, and from then on, Alpine will use the pair found in
1192 that directory. The first time this process is done, this directory will
1193 be created, a key/certificate pair will be copied to it, from then on
1194 this pair will be used to encrypt and decrypt your password file.
1196 <P> If you want to use a specific key and certificate pair to encrypt
1197 your password file, you can create the directory ~/.alpine-smime/.pwd
1198 manually, and then create your preferred key/certificate pair there.
1199 Alpine will use this key regardless of if it has expired, or if it is
1200 self-signed. These issues do not affect the encryption or decryption
1201 of the password file.
1203 <P> If you prefer not to use the directory ~/.alpine-smime/.pwd to save
1204 your key/certificate pair, you can specify a different one with the
1205 -pwdcertdir command line option in Alpine. If the directory specified by
1206 this option is not found Alpine will fail to encrypt and decrypt your
1207 password file. However if it exists, Alpine will search for a
1208 key/certificate pair in that
1209 directory, and if it does not find one, it will create one and save it
1212 <P> Alpine does not care about the names of the key and certificates in
1213 this directory, but the private key must have ".key" extension
1214 and your public certificate must have the ".crt" extension. The
1215 name of the private key will be used in the prompt when you are asked
1216 to unlock your key to decrypt your password.
1218 <P> If Alpine cannot find a suitable private key and public certificate
1219 pair to encrypt your password, it will create one. You will be asked to
1220 create a "Master Password" to protect such key. At this moment
1221 there are no restrictions on passwords, other than they have to be at
1222 least 8 characters long, but future versions of Alpine will include
1223 functionality to restrict master passwords, as set up by the administrator
1224 of the system in the pine.conf.fixed file.
1226 <P><A NAME="example_existing_key"><B>Example of Use of Existing Key and Certificate</B></A>
1228 <P>Assume you have a private key called peter@address.com.key in your,
1229 ~/.alpine-smime/private directory, and a public certificate called
1230 peter@address.com.crt in your ~/.alpine-smime/public directory, and these
1231 are your only key/certificate pair.
1233 <P> When Alpine starts for the first time, without command line options,
1234 it will check if the directory ~/.alpine-smime/.pwd exists, and if not,
1235 it will create it. Then it will go through your keys and certificates and
1236 find a pair that it can use, and copy the files peter@address.com.key,
1237 and peter@address.com.crt to the ~/.alpine-smime/.pwd directory. Alternatively
1238 you can do the same by copying these files by yourself. This can be done
1239 with the sequence of commands
1242 mkdir ~/.alpine-smime/.pwd
1243 cp ~/.alpine-smime/private/peter@address.com.key ~/.alpine-smime/.pwd
1244 cp ~/.alpine-smime/public/peter@address.com.crt ~/.alpine-smime/.pwd
1247 <P> When Alpine starts, you will be asked the password to unlock your
1248 private key with the prompt.
1251 Enter password of key <peter@address.com> to unlock password file:
1254 <P> If you prefer to use different names for your private and public keys
1255 in the ~/.alpine-smime/.pwd directory, you can do so, but you must
1256 preserve the extension of the files. For example, you can use the names
1257 private_key.key and public_cert.crt instead. In this case, the prompt you
1258 will see when you are asked to unlock your private key will read
1261 Enter password of key <private_key> to unlock password file:
1264 <P>Observe that you do not need to use an existing key/certificate pair,
1265 and that you can create a new private key/public certificate pair to
1266 encrypt and decrypt your password file. Alpine provides a mechanism to
1267 change the encryption key for this file in the S/MIME configuration
1270 <P><A NAME="example_self_signed"><B>Example of Creating Master Password</B></A>
1272 <P> If Alpine cannot find a suitable private key and public certificate pair
1273 to encrypt your password file, it will create one. When doing so, it will
1274 start the process with the following warning:
1277 Creating a Master Password for your Password file.
1280 <P> Then Alpine will ask you to enter your Master Password:
1283 Create master password (attempt 1 of 3):
1286 <P> Once you enter this password, and it validates according to system policy,
1287 you will be asked to confirm this password.
1290 Confirm master password (attempt 1 of 3):
1293 <P> If you input the same password, then Alpine will set that as your
1294 Master Password, and you will use this password to unlock your key in the
1297 <P> If you would like to switch your Master Password in the future, you can
1298 do so by creating a new public key and public certificate pair. You can do
1299 so in the S/MIME configuration screen, in the "Manage Key and
1300 Certificate for Password File" section, simply enter your current
1301 password to unlock your current key and then press "C" to create
1308 ====== h_tls_failure_details ======
1311 <TITLE>Certificate Validation Details</TITLE>
1314 <H1>Certificate Validation Details</H1>
1316 This screen gives details as to why the certificate validation failed: the
1317 name of the desired server system; the reason for failure; and the name on
1318 the certificate. This is primarily of interest to experts.
1324 ====== h_tls_failure ======
1327 <TITLE>TLS or SSL Failure</TITLE>
1330 <H1>TLS or SSL Failure</H1>
1332 An attempt was made to establish a secure, encrypted connection to the
1333 server system using either Transport Layer Security (TLS) or the older
1334 Secure Sockets Layer (SSL). This attempt failed.
1337 You should contact your server system management for more assistance.
1338 The problem is probably at the server system and not in Alpine or your local
1339 system. The text in this screen may be helpful for the server system
1340 management in debugging the problem,
1346 ====== h_tls_validation_failure ======
1349 <TITLE>TLS and SSL Certificate Validation Failures</TITLE>
1352 <H1>TLS and SSL Certificate Validation Failures</H1>
1354 An attempt was made to establish a secure, encrypted connection to the
1355 server system using either Transport Layer Security (TLS) or the older
1356 Secure Sockets Layer (SSL).
1359 An important part of this procedure is server certificate validation. A
1360 server certificate is an "electronic identification card" for the server
1361 system that is signed by a well-known certificate authority (CA). Alpine
1362 compares the server system identity in the server certificate with the
1363 name of the server system to which it is trying to connect. Alpine also
1364 verifies that the CA signature is authentic.
1367 Some common failure conditions are:
1371 <LI> [UNIX Alpine] Self signed certificate. This means that the server system
1372 signed its own certificate. This does not necessarily indicate anything
1373 bad; the server operators may simply have elected to not purchase a
1374 signed certificate from a certificate authority.
1376 <LI> [UNIX Alpine] Unable to get local issuer certificate. This means that
1377 the signature on the server system is from an unknown certificate authority.
1378 It can also mean that no certificate authority certificates have been
1379 installed on the local UNIX system.
1381 <LI> [PC Alpine] Self-signed certificate or untrusted authority. This is
1382 the same as either of the above two conditions in UNIX Alpine. Note that
1383 Windows systems typically have a full set of certificate authority
1384 certificates installed, so it is more likely to be a self-signed
1385 certificate than an unknown certificate authority.
1387 <LI> Server name does not match certificate. This means that the server
1388 presented a proper signed certificate for a name other than the desired
1393 Any of these conditions can indicate that you are being attacked and have
1394 been directed to an imposter server that will record your password and
1395 your private mail messages. It can also mean something innocuous.
1398 If you are certain that the problem is innocuous, you can append the
1402 <CENTER><SAMP>/novalidate-cert</SAMP></CENTER>
1405 to the server system name where it appears in your configuration (e.g. the
1406 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>,
1407 a folder-collection, or a news or SMTP server). This will
1408 disable certificate validation. On the other hand, if you are attacked,
1409 you will get no warning if you do this.
1412 <End of Cert Validation Failures help>
1415 ====== h_release_tlscerts ======
1418 <TITLE>TLS and SSL usage note</TITLE>
1421 <H1>TLS and SSL usage note</H1>
1424 When using Alpine from Unix or Windows 2000,
1425 server certificates must be signed by a trusted certificate authority.
1426 You may relax this requirement (at the cost of some security) by using
1428 <A HREF="h_folder_server_syntax">NoValidate-Cert</A>
1429 modifier in the mailbox name.
1432 <CENTER><SAMP>{foo.example.com/novalidate-cert}INBOX</SAMP></CENTER>
1435 The fully-qualified host name of the server should be used
1436 so that it matches the host name in the server certificate.
1438 Here is an example of a host specification that directs Alpine to use
1439 the SSL port (993) and an encrypted data stream.
1441 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
1443 <End of TLS usage help>
1446 ====== h_news_config ======
1449 <TITLE>Alpine Configuration</TITLE>
1452 <H1>Alpine Configuration</H1>
1454 <H2>Using Environment Variables</H2>
1456 The values of Alpine configuration options may include environment variables
1457 that are replaced by the value of the variable at the time Alpine is run
1458 (and also at the time the config option is changed).
1459 The syntax to use environment variables is a subset of the common Unix
1460 shell dollar-syntax.
1463 <P><CENTER><SAMP>$VAR</SAMP></CENTER><P>
1465 appears in the value of an Alpine configuration option it is looked up in the
1466 environent (using getenv("VAR")) and its
1467 looked-up value replaces the <SAMP>$VAR</SAMP> part of the option value.
1468 To include a literal dollar sign you may precede the dollar sign with another
1470 In other words, if the text
1472 <P><CENTER><SAMP>$$text</SAMP></CENTER><P>
1474 is the value of a configuration option, it will be expanded to
1476 <P><CENTER><SAMP>$text</SAMP></CENTER><P>
1478 and no environment lookup will be done.
1479 For Unix Alpine it will also work to use a backslash character to
1480 escape the special meaning of the dollar sign, but $$ is preferable since
1481 it works for both PC-Alpine and Unix Alpine, allowing the configuration option
1482 to be in a shared configuration file.
1485 This all sounds more complicated than it actually is.
1486 An example may make it clearer.
1487 Unfortunately, the way in which environment variables are set is OS-dependent
1488 and command shell-dependent.
1489 In some Unix command shells you may use
1491 <P><CENTER><SAMP>PERSNAME="Fred Flintstone"</SAMP></CENTER><P>
1492 <CENTER><SAMP>export PERSNAME</SAMP></CENTER><P>
1494 Now, if you use Alpine's Setup/Config screen to set
1496 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=$PERSNAME</SAMP></CENTER><P>
1498 the <SAMP>$PERSNAME</SAMP> would be replaced by <SAMP>Fred Flintstone</SAMP>
1499 so that this would be equivalent to
1501 <P><CENTER><SAMP><!--#echo var="VAR_personal-name"-->=Fred Flintstone</SAMP></CENTER><P>
1503 Note, environment variable substitution happens after configuration
1504 options that are lists are split into the separate elements of the list,
1505 so a single environment variable can't contain a list of values.
1508 The environment variable doesn't have to be the only thing
1509 after the equal sign.
1510 However, if the name of the variable is not at the end of the line or
1511 followed by a space (so that you can tell where the variable name ends),
1512 it must be enclosed in curly braces like
1514 <P><CENTER><SAMP>${VAR}</SAMP></CENTER><P>
1516 It is always ok to use the braces even if you don't need to.
1518 It is also possible to set a default value for an environment variable.
1519 This default value will be used if the environment variable is not
1520 set (that is, if getenv("VAR") returns NULL).
1521 The syntax used to set a default value is
1523 <P><CENTER><SAMP>${VAR:-default value}</SAMP></CENTER><P>
1525 If the config file contains
1527 <P><CENTER><SAMP>personal-name=${VAR:-Fred Flintstone}</SAMP></CENTER><P>
1529 then when Alpine is run <SAMP>VAR</SAMP> will be looked up in the environment.
1530 If <SAMP>VAR</SAMP> is found then <SAMP>personal-name</SAMP> will have
1531 the value that <SAMP>VAR</SAMP> was set to, otherwise,
1532 <SAMP>personal-name</SAMP> will be set to <SAMP>Fred Flintstone</SAMP>,
1534 (Note that the variable is called "personal-name" in the config
1535 file but is displayed in the config screen as
1536 "<!--#echo var="VAR_personal-name"-->".
1537 In general, the value that goes into a config file is never exactly the
1538 same as the value you see on the screen.)
1541 An example where an environment variable might be useful is the
1542 variable <SAMP>Inbox-Path</SAMP> in the global configuration file.
1543 Suppose most users used the server
1545 <P><CENTER><SAMP>imapserver.example.com</SAMP></CENTER><P>
1547 but that there were some exceptions who used
1549 <P><CENTER><SAMP>altimapserver.example.com</SAMP></CENTER><P>
1551 In this case, the system manager might include the following line in
1552 the systemwide default Alpine configuration file
1554 <P><CENTER><SAMP>Inbox-Path=${IMAPSERVER:-imapserver.example.com}</SAMP></CENTER><P>
1556 For the exceptional users adding
1558 <P><CENTER><SAMP>IMAPSERVER=altimapserver.example.com</SAMP></CENTER><P>
1560 to their environment should work.
1562 Another example might be the case where a user has to use a different
1563 SMTP server from work and from home.
1564 The setup might be something as simple as
1566 <P><CENTER><SAMP>smtp-server=$SMTP</SAMP></CENTER><P>
1568 or perhaps a default value could be given.
1569 Note that, as mentioned above, the variable <SAMP>SMTP</SAMP> cannot contain
1570 a list of SMTP servers.
1573 <H2>Configuration precedence</H2>
1575 There are several levels of Alpine configuration. Configuration values at
1576 a given level override corresponding values at lower levels. In order of
1577 increasing precedence:
1580 <LI> built-in defaults
1582 <!--chtml if pinemode="os_windows"-->
1583 config file from command line or provided
1584 by "PINECONF" environment variable
1588 <LI> personal configuration file
1589 <LI> personal exceptions configuration file
1590 <LI> command-line options
1591 <!--chtml if pinemode="os_windows"--><!--chtml else-->
1592 <LI> system-wide pine.conf.fixed file<!--chtml endif-->
1595 The values in both the personal configuration file and the
1596 <A HREF="h_config_exceptions">exceptions</A>
1597 configuration file may be set using the Setup command.
1598 Setup/Config is the command to change most of the personal configuration
1600 The other Setup subcommands are also used to change the configuration,
1601 for example, Setup/AddressBook, Setup/Rules, and so on.
1602 Changing the personal exceptions configuration is very similar.
1603 To change a value in the Config screen you would use the command
1604 Setup/eXceptions/Config.
1605 Likewise for the other Setup subcommands (Setup/eXceptions/Rules and so on).
1607 There are a couple exceptions to the rule that configuration values are replaced
1608 by the value of the same option in a higher-precedence file.
1609 The Feature-List variable has values that are additive, but can be
1610 negated by prepending "no-" in front of an individual feature name.
1611 So for features, each individual feature's value is replaced by the value
1612 of the same feature in a higher-precedence file.
1613 Note that this is done automatically for you when you change these values via
1614 the Setup/Config command.
1615 The other exception to the <EM>replace</EM> semantics happens when you
1616 use <A HREF="h_config_inheritance">configuration inheritance</A>
1620 <H2>File name defaults</H2>
1624 <BR> <exe dir> = directory where pine.exe found.
1625 <BR> <pinerc dir> = directory where pinerc found.
1626 <BR> # = default file name is overridable in pinerc.
1627 <BR> $HOME, if not explicitly set, defaults to root of the current drive.
1628 <BR> $MAILCAPS, if set, is used in lieu of the default mailcap search paths.
1629 <BR> + between the mailcap paths implies that the two files are combined.
1630 <BR> ; between other default paths implies that the first one found is used.
1632 Alpine looks for most support files in the same directory it finds its
1633 personal configuration file (pinerc). The -p command-line flag may be
1634 used to specify a particular path name for the pinerc file. If a
1635 pinerc file does not exist, it will be created (if directory permissions
1636 allow). In PC-Alpine, if -p or $PINERC are not defined, Alpine will look
1637 in $HOME\PINE and the directory containing the PINE.EXE. If a PINERC
1638 file does not exist in either one, it will create one in the first of those
1639 two directories that is writable. In detail:
1644 executable <DOS search path>\pine.exe
1645 help index <exe dir>\pine.ndx
1646 help text <exe dir>\pine.hlp
1648 pers config $PINERC ; $HOME\pine\PINERC ; <exe dir>\PINERC
1649 except config $PINERCEX ; $HOME\pine\PINERCEX ; <exe dir>\PINERCEX
1650 global cfg $PINECONF
1652 debug <pinerc dir>\pinedebg.txtN
1653 crash <pinerc dir>\pinecrsh.txt
1654 signature# <pinerc dir>\pine.sig
1655 addressbook# <pinerc dir>\addrbook
1656 mailcap# <pinerc dir>\mailcap + <exe dir>\mailcap
1657 mimetypes# <pinerc dir>\mimetype + <exe dir>\mimetype
1658 newsrc# $HOME\newsrc (if exists, else) <pinerc dir>\newsrc
1659 sentmail# $HOME\mail\sentmail.mtx
1660 postponed# $HOME\mail\postpond.mtx
1661 interrupted $HOME\mail\intruptd
1665 executable <Unix search path>/pine
1666 persnl cfg ~/.pinerc
1667 except cfg ~/.pinercex
1668 global cfg <!--#echo var="PINE_CONF_PATH"-->
1669 fixed cfg <!--#echo var="PINE_CONF_FIXED_PATH"-->
1670 local help <!--#echo var="PINE_INFO_PATH"-->
1672 interrupted ~/.pine-interrupted-mail
1673 debug ~/.pine-debugN
1676 signature# <pinerc dir>/.signature
1677 addressbook# <pinerc dir>/.addressbook
1678 postponed# ~/mail/postponed-msgs
1679 sentmail# ~/mail/sent-mail
1680 mailcap# ~/.mailcap + /etc/mailcap
1681 + /usr/etc/mailcap + /usr/local/etc/mailcap
1682 mimetypes# ~/.mime.types + /etc/mime.types + /usr/local/lib/mime.types
1684 news-spool varies across Unix flavors, e.g. /var/spool/news or /usr/spool/news
1685 active-news varies across Unix flavors, e.g. /usr/lib/news/active
1686 lock files /tmp/.<!--#echo var="MAIL_SPOOL_LOCK_PATH"-->
1687 inbox <!--#echo var="MAIL_SPOOL_PATH"-->
1688 password /etc/passwd
1690 Unix Alpine and PC-Alpine:
1692 .ab* remote addressbook support files
1693 a[1-9]* temporary (while Alpine is running) addressbook files
1698 <H2>Mailcap files</H2>
1700 Alpine honors the mailcap configuration system for specifying external
1701 programs for handling attachments. The mailcap file maps MIME attachment
1702 types to the external programs loaded on your system that can display
1703 and/or print the file. A sample mailcap file comes bundled with the Alpine
1704 distribution. It includes comments that explain the syntax you need to
1705 use for mailcap. With the mailcap file, any program (mail readers,
1706 newsreaders, WWW clients) can use the same configuration for handling
1710 <H2>MIME-Types files</H2>
1712 Alpine uses mime-types files (.mime.types or MIMETYPE) to determine
1713 what Content-Type to use for labeling an attached file, based on
1714 the file extension. That is, this file provides a mapping between
1715 filename extensions and MIME content-types.
1718 <H2>Environment variables</H2>
1720 PC-Alpine uses the following environment variables:
1723 <DD>Optional path to pinerc file.</DD>
1725 <DD>Optional path to personal exceptions configuration file.</DD>
1727 <DD>Optional path to global pine config file.</DD>
1729 <DT>TMPDIR, TMP, or TEMP</DT>
1732 <DD>A <B>semicolon</B> delimited list of path names to mailcap files.</DD>
1733 <DT>USER_DICTIONARY</DT>
1734 <DD>Used to specify the file to contain the user's spell check
1735 dictionary. The default is <SAMP>DICT.U</SAMP> in the same
1736 directory as the <SAMP>SPELL32.DLL</SAMP></DD>
1739 Unix Alpine uses the following environment variables:
1742 <DD>Tells Alpine what kind of terminal is being used.</DD>
1744 <DD>Determines if Alpine will try to display IMAGE attachments.</DD>
1746 <DD>If not set, default is "/bin/sh".</DD>
1747 <DT>TMPDIR, TMP, or TEMP</DT>
1749 <DD>A <B>colon</B> delimited list of path names to mailcap files.</DD>
1751 <!--chtml if pinemode="os_windows"-->
1753 <H2>Common PC-Alpine Configuration Problems</H2>
1755 <H3>Configuration settings aren't being saved</H3>
1757 <P>This problem can happen if you run pine from one directory and
1758 then decide to move your pine directory to another location. PC-Alpine
1759 stores certain variables, including the configuration location, in the
1760 Windows Registry (which you shouldn't ever need to manually edit). There
1761 are a couple of ways to go about removing or resetting the values in the
1765 1) Run PC-Alpine's registry value deletion command. This can be done by
1766 running: "<your pine directory>\pine.exe -registry clear" from the DOS
1767 prompt. You could create a shortcut to pine.exe and change the "Target"
1768 value to the above command.
1771 2) Tell PC-Alpine where to look for the configuration file. Configuration
1772 information is stored in a file called the PINERC. With the "-p PINERC"
1773 option, you can tell PC-Alpine the location of your pinerc. An example of
1774 this would be to run: "<your pine directory>\pine.exe -p C:\pine\mypinerc".
1775 Again, you can use the DOS prompt or the shortcut method explained in (1).
1778 Additionally, there is the "-registry set" option, which will actively
1779 set registry values to the current setting, and is therefore useful with
1780 the "-p PINERC" option.
1784 <End of Configuration Notes>
1787 ====== h_news_legal ======
1790 <TITLE>Alpine Legal Notices</TITLE>
1794 <H1>Alpine Legal Notices</H1>
1796 Alpine and its constituent programs are covered by the Apache License Version 2.0.
1800 <End of Alpine Legal Notices>
1803 ===== h_info_on_mbox =====
1806 <TITLE>Information on mbox driver</TITLE>
1809 <H1>Information on "Missing Mail" and the "mbox" driver</H1>
1811 Beginning with Pine 4.00 (Pine came before Alpine)
1812 a new INBOX access method is
1813 available as part of the standard configuration. It is called the
1814 "mbox" driver and it works like this:<P>
1818 If the file "mbox" exists in the user's home directory, and
1819 is in Unix mailbox format, then when INBOX is opened this file will be
1820 selected as INBOX instead of the mail spool file. Messages will be
1821 automatically transferred from the mail spool file into the mbox
1826 The advantage of this method is that, after new mail has been copied
1827 from the system mail spool, all subsequent access is confined to the
1828 user's home directory, which is desirable on some systems. However, a
1829 possible disadvantage is that mail tools other than those from the
1830 University of Washington will not know to look for mail in the user's
1831 mbox file. For example, POP or IMAP servers other than those from the
1832 University of Washington, and many "new mail notification"
1833 programs may not work as expected with this driver enabled.<P>
1835 To disable this behavior, either remove/rename the "mbox"
1836 file or find the <A HREF="h_config_disable_drivers"><!--#echo var="VAR_disable-these-drivers"--></A>
1837 option in Setup/Config
1838 and add "mbox" to it:
1840 <CENTER><SAMP><!--#echo var="VAR_disable-these-drivers"-->=mbox</SAMP></CENTER>
1842 <End of help on this topic>
1845 ===== h_info_on_locking =====
1848 <TITLE>FAQs on Alpine Locking</TITLE>
1851 <H1>What Systems Managers Need to Know about Alpine File Locking</H1>
1853 There is an extensive section on locking in the Alpine technical notes;
1854 this information is intended to provide answers to some common questions:<P>
1856 <LI> Why did locking change in Pine 4.00?<BR>
1857 The actual locking mechanisms did not change in 4.00.
1858 What changed is that when one particular locking mechanism used by Alpine
1859 fails, Alpine now issues a warning message. Prior to Pine 4.00, the locking
1860 failure would occur, but no warning was issued.<P>
1862 <LI> Is this what the "Mailbox vulnerable" message is about?<BR>
1863 Yes. It means that Alpine was unable to create a lockfile in the
1864 spool directory, generally because of overly restrictive protections on the
1865 spool directory. The correct permissions on the spool directory for
1866 running Alpine are 1777, i.e. read-write-execute permission for everyone,
1867 with the sticky-bit set, so only owners of a file can delete them.<P>
1869 <LI> Why does Alpine require that the mail spool directory have 1777
1871 Alpine was designed to run without special privileges. This means that in
1872 order to create a lockfile in the spool directory, it is necessary to have
1873 the spool directory permissions be world-writable.<P>
1875 <LI> Can't you create the lockfile somewhere else?<BR>
1876 No. The lockfile in question must be in the mail spool directory, because
1877 that's where the mail delivery program expects to find it, and the purpose
1878 of the file is to coordinate access between the mail client (Alpine) and the
1879 mail delivery program.<P>
1881 <LI> Isn't having the spool directory world-writable a big security risk?<BR>
1882 No. Remember that the individual mail files in the spool directory are
1883 NOT world-writable, only the containing directory. Setting the "sticky
1884 bit" -- indicated by the "1" before the "777" mode
1885 -- means that only the owner of the file (or root) can delete files in the
1886 directory. So the only bad behavior that is invited by the 1777 mode is that
1888 create a random file in the spool directory. If the spool directory is
1889 under quota control along with home directories, there is little incentive
1890 for anyone to do this, and even without quotas a periodic scan for
1891 non-mail files usually takes care of the problem. <P>
1893 <LI> Why not run Alpine as setgid mail?<BR>
1894 Alpine was never designed to run with privileges, and to do so introduces a
1895 significant security vulnerability. For example, if a user suspends Alpine,
1896 the resulting shell will have group privileges. This is one example of
1897 why we strongly recommend against running Alpine as a privileged program.
1898 In addition, a "privileged mailer " paradigm would mean that normal
1900 could not test Alpine versions or other mailers that had not been installed
1901 by the system administrators.<P>
1904 <LI> Are there any alternatives to creating .lock files in the spool dir?<BR>
1905 There are, but they all have different sets of tradeoffs, and not all will
1906 work on all systems. Some examples:<UL>
1907 <LI> Use lock system calls. Works fine on a few systems, provided mail
1908 spool is local. Doesn't work reliably if NFS is used.
1909 Doesn't work unless <B>all</B> the mail programs accessing the spool dir
1911 <LI> Deliver mail to user's home directory. An excellent solution, highly
1912 recommended -- but one which is incompatible with some "legacy"
1913 mail tools that always look in the spool directory for the mail.
1916 <LI> Are these spool directory lock files the only kinds of locks used by
1918 No. Alpine also creates lockfiles in the /tmp directory. For normal Unix
1919 mailbox format folders, these are used to coordinate access between
1920 multiple Alpine sessions. <P>
1923 <A HREF="h_config_quell_lock_failure_warnings">"<!--#echo var="FEAT_quell-lock-failure-warnings"-->"</A> feature added in Pine 4.01?<BR>
1924 This is for people who are content to live dangerously, or who have
1925 specific knowledge that the spool directory lockfiles are superfluous on
1926 their system (because both Alpine and the mail delivery program are using
1927 system call file locking in a context that works reliably, e.g. not NFS.)<P>
1929 <LI> Where can I find more details on how Alpine locking works?<BR>
1930 See the Alpine Technical Notes.<P>
1934 <End of help on this topic>
1937 ===== h_finding_help ====
1940 <TITLE>Finding more information and requesting help</TITLE>
1943 <H1>Places to Look for More Answers</H1>
1944 If you have questions about or problems with Alpine that you cannot resolve
1945 after consulting the program's internal, context-sensitive help screens, here
1946 are additional information resources that you may find helpful:
1949 <LI> Alpine's top-level <A HREF="main_menu_tx">MAIN MENU HELP</A>.<P>
1951 <LI> Alpine's <A HREF="h_help_index">Help Index</A>.<P>
1953 <LI> Alpine's internal <A HREF="h_news">Release Notes</A>. They contain a
1954 listing of changes in Alpine <!--#echo var="ALPINE_VERSION"-->
1955 since the last version, which may be useful for you to be aware of,
1956 <B>especially</B> if a "problem" you are encountering is actually
1957 a change in the way an aspect of Alpine works. There, you will also find notes
1958 on Alpine configuration.<P>
1960 <LI> The main site for Alpine contains information on configuring and solving problems
1961 with Alpine, it can be found at
1963 <CENTER><A HREF="http://alpine.freeiz.com/alpine/">http://alpine.freeiz.com/alpine/</A></CENTER>
1965 <LI> The Alpine Information Center (maintained by the University of
1966 Washington) World Wide Web site contains, among other things
1968 <LI>a collection of Frequently Asked Questions (and answers!) about Alpine
1969 <LI>an overview of the basics for beginning Alpine users
1970 <LI>Technical Notes for systems administrators
1971 <LI>archives (including a searchable index) of the alpine-info
1972 mailing list, on which matters of interest to systems/email administrators,
1973 developers, trainers, user support personnel, and others involved with Alpine
1974 messaging on a "technical" level are discussed.
1976 The Alpine Information Center can be accessed with a WWW browser at:<P>
1977 <CENTER><A HREF="http://www.washington.edu/alpine/">http://www.washington.edu/alpine/</A></CENTER>
1980 <H1>Requesting help</H1>
1981 If the internal help, the Release Notes, the Alpine Information Center, and your
1982 local online and print resources do not help you resolve a problem, please
1983 start by contacting your local computer support staff and asking for help.
1985 This is especially true if:
1987 <li>You suddenly have trouble sending or receiving mail.
1988 <li>You receive a "disk quota exceeded" message.
1989 <li>You have forgotten your password.
1990 <li>You think your account may have been compromised.
1991 <li>You need help viewing an attachment.
1992 <li>You need to know how to configure your:
1993 <A HREF="h_config_nntp_server">NNTP (news) server</A>,
1994 <A HREF="h_config_smtp_server">SMTP (sending mail) server</A>,
1995 <A HREF="h_config_ldap_server">LDAP (directory lookup) server</A>, or
1996 <A HREF="h_config_inbox_path">INBOX (incoming mail) path</A>.
1997 <li>You want to know what alternative editors or spellcheckers you may be able to use.
1998 <li>You want to block email from a particular person.
1999 <li>You're going on vacation and need to autorespond to incoming mail.
2000 <li>You want to automatically file or filter incoming messages.
2003 In all of these cases,
2004 you should contact <B>your</B> support staff, because <B>only they</B>
2005 will be able to assist you effectively. Your support staff may be, depending on who
2006 provides you with the email account you use Alpine with, for example:<UL>
2007 <LI> the computing help desk of (a department of) your university, school,
2009 <LI> the customer service center of your Internet Service Provider; or
2010 <LI> the friendly volunteer helpers of your Freenet; or
2011 <LI> the person who setup your computer and internet connection.
2014 Due to the large number of Alpine installations worldwide, and because we
2015 receive no funding for it, the University of Washington <B>cannot provide
2016 individual support services outside the University of Washington</B>.
2018 If you have no local computing support to turn to, the worldwide <b>comp.mail.pine</b>
2019 newsgroup can be a valuable source of information and assistance for Alpine
2022 For systems/email administrators, developers, trainers, user support
2023 personnel, and others involved with Alpine messaging on a "technical"
2024 level, the mailing list alpine-info is available; for information on
2025 subscribing and posting to it, see
2027 <CENTER><A HREF="http://www.washington.edu/alpine/alpine-info/subscribing.html">http://www.washington.edu/alpine/alpine-info/subscribing.html</A></CENTER>
2030 Regardless of whom you are asking for help with Alpine, remember
2031 to provide as much detail as you can about the
2032 nature of any problem you are encountering, such as
2034 <LI>when it first occurred;
2035 <LI>what, if anything, happened that might have brought it about;
2036 <LI>whether it still persists;
2037 <LI>whether it is reproducible, and if so, how;
2038 <LI>what, if anything, you already tried to solve it.
2040 It may also be helpful if you specify what version of Alpine you are using
2041 <!--chtml if pinemode="running"-->
2042 -- this is <!--#echo var="ALPINE_VERSION"--> --
2044 and on what system, and when the copy of Alpine you are using was created
2045 <!--chtml if pinemode="running"-->
2046 -- for this copy: <!--#echo var=ALPINE_COMPILE_DATE-->
2049 <!--chtml if pinemode="running"-->
2051 When the Alpine program you are currently using was installed, a support
2052 contact email address may have been set up; in that case, you can simply select
2053 this link now to send a message to it:<BR>
2054 <A HREF="X-Alpine-Gripe:_LOCAL_ADDRESS_?local"><!--#echo var="_LOCAL_FULLNAME_"--></A><P>
2056 <!--chtml if [ -r PINE_INFO_PATH ]-->
2057 <HR WIDTH="75%">Local Support Contacts:<P>
2058 <!--#include file="PINE_INFO_PATH"-->
2062 <End of help on this topic>
2065 ===== new_user_greeting ======
2068 <TITLE>NEW USER GREETING</TITLE>
2071 <CENTER><<<This message will appear only once>>></CENTER>
2073 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
2074 We hope you will explore Alpine's many capabilities. From the MAIN MENU,
2075 select Setup/Config to see many of the options available to you. Also note
2076 that all screens have context-sensitive help text available.<P>
2077 <!--chtml if pinemode="phone_home"-->
2079 This software was originally created and maintained as a public
2080 service by the University of Washington until 2009; updates are made
2081 available as a public service of the Alpine community. It is always
2082 helpful to have an idea of how many users are using Alpine. Are you
2083 willing to be counted as an Alpine user? Pressing
2084 <A HREF="X-Alpine-Phone-Home:">Return</A>
2085 will send an anonymous (meaning, your real email address will not be revealed)
2086 message to the Alpine developers for purposes of tallying.
2088 <!--To Exit this screen and continue your Alpine session press "E".-->
2090 To Exit this screen and continue your Alpine session press "Return".
2094 ===== new_alpine_user_greeting ======
2097 <TITLE>NEW ALPINE USER GREETING</TITLE>
2100 <CENTER><<<This message will appear only once>>></CENTER>
2102 <H1>Welcome to Alpine ... a Program for Internet News and Email</H1>
2103 Your Alpine configuration file indicates that you may have used Pine before
2105 If you are familiar with the way Pine works, you should be comfortable
2107 Your Pine configuration file is automatically used for Alpine.
2108 The Release Notes may be viewed by pressing
2109 "R" now or while in the MAIN MENU.
2111 <!--chtml if pinemode="phone_home"-->
2113 This software was originally created and maintained as a public
2114 service by the University of Washington until 2009; updates are made
2115 available as a public service of the Alpine community. It is always
2116 helpful to have an idea of how many users are using Alpine. Are you
2117 willing to be counted as an Alpine user? Pressing
2118 <A HREF="X-Alpine-Phone-Home:">Return</A>
2119 will send an anonymous (meaning, your real email address will not be revealed)
2120 message to the Alpine developers for purposes of tallying.
2122 <!--To Exit this screen and continue your Alpine session press "E".-->
2124 To Exit this screen and continue your Alpine session press "Return".
2128 ===== new_version_greeting ======
2131 <TITLE>NEW VERSION GREETING</TITLE>
2134 <CENTER><<<This message will appear only once>>></CENTER>
2136 <H1>Welcome to Alpine version <!--#echo var="ALPINE_VERSION"-->!</H1>
2137 Your Alpine configuration file indicates that you may not have used
2138 this version of Alpine before. This version's significant changes are
2139 documented in the Release Notes, which may be viewed by pressing
2140 "R" now or while in the MAIN MENU.
2142 <!--chtml if pinemode="phone_home"-->
2144 This software was originally created and maintained as a public
2145 service by the University of Washington until 2009; updates are made
2146 available as a public service of the Alpine community. It is always
2147 helpful to have an idea of how many users are using Alpine. Are you
2148 willing to be counted as an Alpine user? Pressing
2149 <A HREF="X-Alpine-Phone-Home:">Return</A>
2150 will send an anonymous (meaning, your real email address will not be revealed)
2151 message to the Alpine developers for purposes of tallying.
2153 <!--To Exit this screen and continue your Alpine session press "E".-->
2155 To Exit this screen and continue your Alpine session press "Return".
2160 ===== main_menu_tx ======
2163 <TITLE>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</TITLE>
2166 <H1>GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</H1>
2168 Version <!--#echo var="ALPINE_VERSION"-->
2169 <!--chtml if pinemode="running"-->
2170 <BR>(built <!--#echo var=ALPINE_COMPILE_DATE-->)
2173 <CENTER>Copyright 2013-2017 Eduardo Chappa,
2174 <BR>Copyright 2006-2008 University of Washington.
2178 When you are viewing a help screen, there may be links to
2179 other topics highlighted (in Reverse video) in the text.
2181 The word "Introduction" in the TABLE OF CONTENTS below should be
2183 If you type carriage return (or V for View Link, see the commands at the
2184 bottom of the screen) you will be taken to a new help screen to view the
2186 The commands at the bottom of the screen should then include
2187 "P Prev Help".
2188 If you type "P" you will end up back here.
2189 If you type "E" for Exit, you will be back out of help and returned
2190 to the place you were in Alpine when you entered Help.
2191 In this case, you would go back to the MAIN MENU.
2192 There are also other links that are highlighted in bold (or the color used
2193 by your terminal to display bold).
2194 The items after the Introduction in the TABLE OF CONTENTS are all examples
2196 In order to view those links, you first have to make the link you want
2197 to view the current link.
2198 The "NextLink" and "PrevLink" commands
2199 (see bottom of screen) can do that for you.
2202 <H2>TABLE OF CONTENTS</H2>
2204 <LI> <A HREF="h_mainhelp_intro">Introduction</A>
2205 <LI> <A HREF="h_mainhelp_pinehelp">Alpine Help</A>
2206 <!--chtml if [ -r PINE_INFO_PATH ]-->
2207 <LI> <A HREF="h_mainhelp_localsupport">Local Support Contacts</A>
2209 <LI> <A HREF="h_mainhelp_cmds">Giving Commands in Alpine</A>
2210 <LI> <A HREF="h_mainhelp_config">Alpine Configuration</A>
2211 <LI> <A HREF="h_mainhelp_status">Titlebar Line</A>
2212 <LI> <A HREF="h_mainhelp_mainmenu">Main Menu</A>
2213 <LI> <A HREF="h_mainhelp_index">Index of Messages</A>
2214 <LI> <A HREF="h_mainhelp_reading">Reading Messages</A>
2215 <LI> <A HREF="h_mainhelp_composing">Composing Messages</A>
2216 <LI> <A HREF="h_mainhelp_readingnews">Reading News</A>
2217 <LI> <A HREF="h_mainhelp_abooks">Address Books</A>
2218 <LI> <A HREF="h_mainhelp_ldap">LDAP Directories</A>
2219 <LI> <A HREF="h_mainhelp_folders">Folders</A>
2220 <LI> <A HREF="h_mainhelp_collections">Collection Lists</A>
2221 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
2222 <LI> <A HREF="h_mainhelp_color">Color Setup</A>
2223 <LI> <A HREF="h_mainhelp_filtering">Filtering</A>
2224 <LI> <A HREF="h_mainhelp_roles">Roles</A>
2225 <LI> <A HREF="h_mainhelp_patterns">Patterns</A>
2226 <LI> <A HREF="h_mainhelp_keywords">Keywords (or Flags, or Labels)</A>
2227 <LI> <A HREF="h_mainhelp_mouse">Using a Mouse</A>
2228 <LI> <A HREF="h_mainhelp_cmdlineopts">Command Line Options</A>
2229 <LI> <A HREF="h_mainhelp_securing">Securing Your Alpine Session</A>
2230 <LI> <A HREF="h_mainhelp_smime">S/MIME</A>
2231 <LI> <A HREF="h_mainhelp_problems">Reporting Problems</A>
2232 <LI> <A HREF="X-Alpine-Config:">Show Supported Options in this Alpine</A>
2233 <LI> <A HREF="h_help_index">Index to Alpine's Online Help</A>
2237 <End of help on this topic>
2240 ===== h_mainhelp_intro ======
2243 <TITLE>Introduction</TITLE>
2246 <H1>Introduction</H1>
2248 Alpine is an "Alternatively Licensed Program for Internet
2249 News and Email" produced until 2009 by the University of Washington.
2250 It is intended to be an easy-to-use program for
2251 sending, receiving, and filing Internet electronic mail messages and
2252 bulletin board (Netnews/Usenet) messages. Alpine supports the following
2253 Internet protocols and specifications: SMTP (Simple Mail Transport Protocol),
2254 NNTP (Network News Transport Protocol), MIME (Multipurpose Internet Mail
2255 Extensions), IMAP (Internet Message Access Protocol), and LDAP (Lightweight
2256 Directory Access Protocol).<p>
2258 Although originally designed for inexperienced email users, Alpine has
2259 evolved to support many advanced features. There are an ever-growing
2260 number of configuration and personal-preference options, though which of
2261 them are available to you is determined by your local system managers.
2263 <H2>WHAT ALPINE DOES...</H2>
2265 Alpine is a "mail user agent" (MUA), which is a program that
2267 compose and read messages using Internet mail standards. (Whether you
2268 can correspond with others on the Internet depends on whether or not your
2269 computer is connected to the Internet.) Alpine also allows reading and
2270 posting messages on the Internet "net news" system, provided
2271 that your site operates a suitable news server.
2273 <H2>WHAT ALPINE DOES NOT DO...</H2>
2275 A "mail user agent" such as Alpine is just one part of a
2276 messaging system. Here are some things that are <B>not</B> done by Alpine,
2277 but require other programs:<P>
2279 <LI> Actual relaying of email... which is done by "message transfer
2281 <LI> Vacation messages... automatically responding to incoming messages
2282 <LI> Anything to do with "talk"... which has nothing to do with
2284 <LI> Anything to do with "irc"... which has nothing to do with email.
2285 <LI> List processing... resending one message to a list of recipients.
2289 <End of help on this topic>
2293 ===== h_mainhelp_pinehelp ======
2296 <TITLE>Alpine Help</TITLE>
2299 <H1>Alpine Help</H1>
2301 Alpine help is generally context-sensitive. In other words, each Alpine screen you
2302 use will have its own help text, explaining the choices available for that
2303 screen. This general help section, on the other hand, attempts to give an
2304 overall picture of what Alpine is capable of doing, as well as pointers to
2305 additional help sections about specific topics.<p>
2307 Much of the help text contains links to further help topics, similar to
2308 how the World Wide Web works.
2309 You may choose a link to view using the "NextLink" and
2310 "PrevLink" commands to change the link that is highlighted.
2311 The "View Link" command will then show you the highlighted link.
2312 Similar to the Back button in a web browser, the "Prev Help" command
2313 will return you to where you were before viewing the link, and "Exit Help"
2314 will return you to the location in Alpine before you asked for help.
2315 For example, if you are reading this text in Alpine you may return to the
2316 help table of contents with the "Prev Help" command or you may view the
2317 Release notes link in the next paragraph and then return here with
2318 "Prev Help".
2321 In addition to this general help on Alpine, <A HREF="h_news">Release Notes</A>
2322 on the current Alpine version are also available from the MAIN MENU: Press
2323 <!--chtml if pinemode="function_key"-->
2328 to browse the release notes. These include changes since the last release,
2329 configuration information, the history of the Alpine
2330 project, credits, and legal notices.
2332 Alpine releases are available via the world wide web at
2335 HREF="http://alpine.freeiz.com/alpine/release/">http://alpine.freeiz.com/alpine/release/</A></SAMP
2339 If you would like to print <EM>all</EM> of Alpine's internal help text
2340 (not recommended) for a little light bedtime reading, then press
2341 <!--chtml if pinemode="function_key"-->
2346 now. (This assumes that the
2347 copy of Alpine you are using has been properly configured for printing
2350 <End of help on this topic>
2353 ===== h_mainhelp_localsupport ======
2356 <TITLE>Local Support Contacts</TITLE>
2359 <H1>Local Support Contacts</H1>
2361 <!--chtml if [ -r PINE_INFO_PATH ]-->
2362 <!--#include file="PINE_INFO_PATH"-->
2364 No Local Support Contacts configured.
2368 <End of help on this topic>
2372 ===== h_mainhelp_cmds ======
2375 <TITLE>Giving Commands in Alpine</TITLE>
2378 <H1>Giving Commands in Alpine</H1>
2380 Unless configured otherwise
2381 (<A HREF="h_config_blank_keymenu"><!--#echo var="FEAT_disable-keymenu"--></A>)
2382 the bottom two lines of the screen are always used to list the
2383 commands you can give. You press the keys that are highlighted to give
2384 the command. The commands for getting help and going back to the main
2385 menu are always present (except when viewing help as you are now).
2386 <!--chtml if pinemode="function_key"-->
2389 Pressing O (meaning "Other Commands") changes the keys
2390 you see at the bottom of any screen. In some cases there are 3 or
2392 sets of keys that can be seen by using the O key. <EM>All commands are
2393 active</EM>, even if they are not currently showing at the bottom of your
2394 screen. In other words, you <EM>never</EM> need to press the O key, except to
2395 remind yourself of the proper key to press to perform an operation.
2397 <H2>Control Key Commands</H2>
2398 When composing mail, and in a few other places, in Alpine you
2399 have to use Control keys. This means pressing the Control key (usually labeled
2400 "Ctrl") and the
2401 letter indicated at the same time. Usually, this is shown with a
2402 "^" in front of the letter. On some systems, certain control
2403 characters are intercepted before they get to Alpine. As a work-around,
2404 you can press the ESCAPE key twice followed by the desired key. For
2405 example, if Ctrl-O (^O) does not work on your system, try typing
2406 "ESC ESC O".
2408 <H2>Paging Up and Down</H2>
2409 The "+" and "-" keys are used for
2410 moving to the next or previous page. The space bar is a synonym for
2411 "+". You may also use Ctrl-V to page down and Ctrl-Y to page
2412 up as you do in the message composer. On screens with a WhereIs (search)
2413 command, W or Ctrl-W followed by Ctrl-V will move to the bottom of the
2414 message or list, and W or Ctrl-W followed by Ctrl-Y will move to the top
2415 of the message or list.
2418 The return key is usually a synonym for a frequently used
2419 command. When viewing a message, there is currently not a default
2420 command, so RETURN does nothing; when in the index, it is synonymous with
2421 "view msg". In the key menu at the bottom of the screen, whatever is
2422 enclosed in square brackets [] is the same as the return key.
2424 <H2>Control Keys Not Used By Alpine</H2>
2425 Most commands in Alpine are single letters, with -- we hope -- some mnemonic
2426 value, but in places where Alpine is expecting text input, e.g. in the composer or
2427 at prompts for file/folder names, control keys must be used for editing and
2428 navigation functions.
2431 Alpine has used nearly all the control keys available. There are, however,
2432 certain control keys that are reserved by other programs or for technical
2433 reasons. Alpine does not use any of these keys:
2435 <DT>Ctrl-S</DT> <DD>Used by Unix as "stop output"</DD>
2436 <DT>Ctrl-Q</DT> <DD>Used by Unix as "resume output"</DD>
2437 <DT>Ctrl-]</DT> <DD>Often used by Telnet as escape key</DD>
2440 Note: Ctrl-S and Ctrl-Q can be subject to
2441 <A HREF="h_special_xon_xoff">special handling</A>.
2443 In addition, while the ESC key alone is not used for command input,
2444 Alpine will recognize two consecutive ESC key presses followed by a letter
2445 key as a substitute for control key input. For example, the control key
2446 <SAMP>Ctrl-X</SAMP> can alternatively be entered using the
2447 three keystrokes: <SAMP>ESC ESC x</SAMP>.
2448 This is useful if the communication program you are using
2449 (e.g. Telnet) has its own, conflicting, idea of what certain control
2453 <H2>Repainting the Screen</H2>
2454 Sometimes what is displayed on the screen will be
2455 incorrect due to noise on the phone line or other causes and you will want
2456 to repaint the whole screen to make it correct. You can use the Ctrl-L
2457 command to do this. It never hurts to do it when in doubt.
2460 <End of help on this topic>
2463 ===== h_mainhelp_status ======
2466 <TITLE>Titlebar Line</TITLE>
2469 <H1>Titlebar Line</H1>
2471 The top line of the screen is Alpine's titlebar line. It will always display
2472 the current version of Alpine and will also convey information about the
2473 status of the program. This is where you look to find out what
2474 collection, folder and message number is active and where you are in Alpine.
2477 If the titlebar line says "READONLY" it means that the open folder
2478 (typically your INBOX) is "locked" by another mail session --
2479 most likely a more recent session of Alpine has taken the INBOX lock.
2482 If the titlebar line says "CLOSED" it means that you are trying to
2484 folder on a remote mail server, and for some reason, communication with
2485 the mail server has either been lost, or never successfully established.
2486 This can be a result of trying to open a non-existent folder, or one
2487 stored on an invalid or non-operational server, or it can mean that Alpine
2488 has been suspended for more that 30 minutes while accessing a remote mail
2492 <End of help on this topic>
2495 ===== h_mainhelp_mainmenu ======
2498 <TITLE>Main Menu</TITLE>
2503 The Main Menu lists Alpine's main options.
2504 The key or keys you must type to enter your
2505 choice are to the left of each option or command name.
2506 You can type either uppercase or lowercase letters,
2507 and you should not press <Return> after typing the
2508 letter (unless you are specifically asking for the default,
2509 highlighted command).
2512 From the Main Menu you can choose to read online help, write (compose) and
2513 send a message, look at an index of your mail messages, open or maintain
2514 your mail folders, update your address book, configure Alpine, and quit Alpine.
2515 There are additional options listed at
2516 the bottom of the screen as well.
2519 The Help command usually returns context-sensitive help information.
2520 However, in the Main Menu you get the most general help, which includes
2521 a Table of Contents.
2522 The last entry in the Table of Contents is an Index of help topics,
2523 so this is a good place to go if you are having trouble finding how
2526 <H2>Main Menu Commands</H2>
2527 The Alpine main menu lists the most common Alpine functions. A <a
2528 href="h_main_menu_commands">full list of these
2529 commands</a> and what they do is available.
2531 <End of help on this topic>
2534 ===== h_mainhelp_abooks ======
2537 <TITLE>Address Books</TITLE>
2540 <H1>Address Books</H1>
2543 As you use email, you can build a list of your regular email correspondents
2545 Address Book. At the Alpine MAIN MENU, press A to see the Address Book List
2547 personal address book will be highlighted. Press <Return> to view it.
2548 You can use the address book to store email addresses for individuals or
2549 groups, to create easily
2550 remembered "nicknames" for these addresses, and to quickly retrieve an email
2551 address when you are composing a message.
2553 There are two ways to add addresses to your address book: you can add them
2554 manually or take them from messages (by pressing T to access the Take command).
2555 With either method, you specify nicknames for your correspondents. A single
2556 address book entry (or nickname) can point to just one email address, or, it can
2557 point to more than one. When it points to more than one, it is called a
2558 distribution list. Each distribution list has a nickname, a full name, and a
2559 list of addresses. These
2560 addresses may be actual addresses, other nicknames in your address book, or
2565 Additional information is available in Alpine's online help:
2567 <li><a href="h_abook_opened">The Alpine Address Book</a></li>
2570 <End of help on this topic>
2573 ===== h_mainhelp_ldap ======
2581 LDAP (Lightweight Directory Access Protocol) is a standard means of accessing
2582 an organization's shared
2583 directories. Essentially, using LDAP, Alpine is able to find email addresses in
2585 books, rather like the White Pages provided by the phone company. As an Alpine
2587 necessary to know much about how this works, only how to use it and how to
2591 More information on configuring LDAP is available in Alpine's online help:
2593 <li><a href="h_direct_config">Setup LDAP Directory Servers</a></li>
2596 Additional help on using LDAP in Alpine is also available:
2598 <li><a href="h_ldap_view">LDAP Response View Explained</a></li>
2601 <End of help on this topic>
2604 ===== h_mainhelp_index ======
2607 <TITLE>Index of Messages</TITLE>
2610 <H1>Index of Messages</H1>
2612 In Alpine's message index, the selected message is highlighted. The first
2613 column on the left is blank, shows a "+" if the message was
2614 sent directly to you (i.e., it is not a
2615 copy or from a list), or a "-" if you were explicitly Cc'd.
2617 The second column may be blank, or it may contain:
2619 <li>"N" if the message is new (unread), </li>
2620 <li>"A" if you have answered the message (using the Reply command), </li>
2621 <li>"D" if you have marked the message for deletion.</li>
2625 Note: If you answer a message as well as mark it deleted (in either order),
2626 you will only see the "D".
2629 The rest of the columns in the message line show you the message
2630 number, date sent, sender, size, and subject. For details, press ? (Help).
2631 The behavior and appearance of the Index screen is highly configurable.
2632 In the Setup/Config screen search (with the WhereIs command) for options
2633 that contain the words "index" or "thread" to see
2634 many of the configuration possibilities.
2636 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
2637 option may be used to configure the look of the standard MESSAGE INDEX lines
2638 in many different ways.
2639 Find <!--#echo var="VAR_index-format"--> in the Setup/Config screen and
2640 read the help text there for more information.
2642 Most of the commands you need to handle your messages are visible at the
2643 bottom of the screen, and you can press O (OTHER CMDS) to see additional
2644 commands that are available.
2645 You do not need to see these "other commands"
2646 on the screen to use them. That is, you never need to press O as a prefix
2647 for any other command.
2650 Additional information is available in Alpine's online help:
2652 <li><a href="h_mail_index">Message Index Commands</a></li>
2655 <End of help on this topic>
2658 ===== h_mainhelp_reading ======
2661 <TITLE>Reading Messages</TITLE>
2664 <H1>Reading Messages</H1>
2666 The message text screen shows you the text of the message along with
2667 its header. If a message has attachments, those will be listed (but not
2668 displayed) also. The titlebar line displays information about the currently
2669 open message, folder and collection. You see the name of the collection
2670 (if there is one) in angle brackets, then the name of the folder, then the
2671 message number and finally the position within the current message (in
2672 percent). If the message is marked for deletion
2673 "DEL" will appear in the
2674 upper right as well.
2677 As with every Alpine screen, the bottom two lines show you the commands
2680 <P>Additional information is available in Alpine's online help:
2682 <li><a href="h_mail_view">Message Text Screen</a></li>
2683 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a></li>
2684 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a></li>
2687 <End of help on this topic>
2690 ===== h_mainhelp_composing ======
2693 <TITLE>Composing Messages</TITLE>
2696 <H1>Composing Messages</H1>
2698 To write a message, press C (Compose). You see the Compose Message
2699 screen, which is divided into two parts: the header area and the message
2700 text area. The header area is where information on the recipient (the To:
2701 field) and the subject line go, while the message text area contains the
2702 actual text of the email message. Different commands are available to you
2703 when your cursor is in different areas on this screen. To see additional
2704 help on commands in either the message text or header area, type
2705 <Control>G (Get help).
2708 To move around, use the arrow keys or Ctrl-N (Next line) and Ctrl-P
2709 (Previous line); to correct typing errors, use <Backspace> or <Delete>.
2711 <P>The following information from Alpine's online help may prove useful:
2713 <li><a href="h_composer_to">Message Header Commands</a></li>
2714 <li><a href="h_compose_richhdr">Rich Header Command</a></li>
2715 <li><a href="h_composer">Composer Commands</a></li>
2716 <li><a href="h_edit_nav_cmds">Composer Editing Commands</a></li>
2717 <li><a href="h_config_change_your_from">Changing your From Address</a></li>
2718 <li><a href="h_compose_send">Send Command</a></li>
2719 <li><a href="h_compose_spell">Spell Check Command</a></li>
2722 <End of help on this topic>
2725 ===== h_mainhelp_collections ======
2728 <TITLE>Collection Lists</TITLE>
2731 <H1>Collection Lists</H1>
2733 Collection lists are Alpine's way of organizing groups of folders. Each
2734 "collection" can reside on a different server, for example, and contain a
2735 different group of mail folders.
2738 For more information on this, see:
2740 <li><a href="h_what_are_collections">Folder Collections Explained</a></li>
2743 Additional information relating to collection lists is also available in
2747 <li><a href="h_collection_maint">Setup Collection List Screen</a></li>
2748 <li><a href="h_collection_screen">Collection List Screen</a></li>
2751 <End of help on this topic>
2754 ===== h_mainhelp_folders ======
2757 <TITLE>Folders</TITLE>
2762 Messages can quickly accumulate in your INBOX folder. If you use email
2763 often, you soon could have hundreds. You need to delete messages you do
2764 not want, and you can use folders to organize messages you wish to save. A
2765 folder is a collection of one or more messages that are stored (just like
2766 the messages in your INBOX) so you can access and manage them.
2769 You can organize your email messages into different folders by topic,
2770 correspondent, date, or any other category that is meaningful to you. You
2771 can create your own folders, and Alpine automatically provides three:
2773 <li>The INBOX folder: messages sent to you are listed in this folder.
2774 When you first start Alpine and go to the Message Index screen, you are
2775 looking at the list of messages in your INBOX folder. Every incoming
2776 message remains in your INBOX until you delete it or save it in another
2778 <li>The sent-mail folder: copies of messages you send are stored in this
2780 convenient if you cannot remember whether you actually sent a message and want
2782 if you want to send a message again.</li>
2783 <li>The saved-messages folder: copies of messages you save are stored in this
2785 unless you choose to save them to other folders you create yourself.</li>
2789 More information about folders is available in Alpine's online help:
2791 <li><a href="h_folder_open">Explanation of Folder Selection</a></li>
2792 <li><a href="h_folder_maint">Help for Folder List</a></li>
2793 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a></li>
2794 <li><a href="h_folder_fcc">Folder Select for Fcc ("sent-mail")
2796 <li><a href="h_folder_save">Folder Select for Save Explained</a></li>
2799 <End of help on this topic>
2802 ===== h_mainhelp_color ======
2805 <TITLE>Color</TITLE>
2810 If the terminal emulator you are using is capable of displaying color or if
2811 you are using PC-Alpine, then it is possible to set up Alpine so that various
2812 parts of the display will be shown in colors you configure. This is done
2813 using the Setup Color screen, available from the MAIN MENU by selecting
2814 the Setup command followed by "K" for Kolor (because "C"
2815 stands for Config in this context).
2818 For example, you may color things like the titlebar, the current item,
2819 the keymenu, and the status messages.
2820 You may also color lines in the index, and headers and quoted text in the
2821 MESSAGE TEXT screen.
2822 You use the Color Setup screen for configuring most of this, but you must
2823 use the IndexColor setup for coloring whole index lines.
2824 These are available from the MAIN MENU under Setup/Kolor and Setup/Rules/IndexColor.
2827 The following entries in Alpine's online help provide additional information
2828 about how to use color:
2830 <LI> <A HREF="h_color_setup">Color Setup screen</A>
2831 <LI> <A HREF="h_rules_incols">Index Line Color</A>
2832 <LI> <A HREF="h_config_quote_color">quoted text</A> in message view
2833 <LI> <A HREF="h_config_customhdr_pattern">text associated with user-defined headers</A> in message view
2836 <End of help on this topic>
2839 ===== h_mainhelp_mouse ======
2842 <TITLE>Using a Mouse</TITLE>
2845 <H1>Using a Mouse</H1>
2847 If you are using PC-Alpine mouse support is turned on automatically.
2848 If you are using UNIX Alpine within an X terminal window or within
2849 a terminal emulator that supports an xterm-style mouse, then you may
2850 turn on support for the mouse with the feature
2851 <A HREF="h_config_enable_mouse"><!--#echo var="FEAT_enable-mouse-in-xterm"--></A>.
2852 For UNIX Alpine you will also need to set the $DISPLAY environment variable.
2854 PC-Alpine offers considerable mouse support. You can view what is
2855 "clickable" by dragging your mouse over any screen; when the
2856 arrow cursor changes into a hand, you found something. Mouse-click
2857 possibilities include navigating between screens and folders and
2858 double-clicking on hyperlinks to open your Web browser.
2859 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
2860 screen. Examples of right-click options include "copy" after
2861 selecting text to copy and "View in New Window" when you click
2862 on a particular message in the Message Index. The menu choices available
2863 to you will vary based upon what screen is open, where on the screen your
2864 cursor is located, and even what action you have already taken.
2865 Within a folder, you may set the "Important" flag on any
2868 X terminal mouse support is more limited but still quite powerful.
2869 As with PC-Alpine, clicking on any of the commands in the keymenu at
2870 the bottom of the screen will execute that command as if you typed it.
2871 Double-clicking on a link, for example the link to the
2872 <!--#echo var="FEAT_enable-mouse-in-xterm"--> feature in the paragraph above,
2873 will take you to that link.
2874 Double-clicking on an index line will view the message, and so on.
2876 <End of help on this topic>
2879 ===== h_mainhelp_keywords ======
2882 <TITLE>Keywords</TITLE>
2887 Within a folder, you may set the "Important" flag on any
2889 This doesn't have any system-defined meaning and is only called
2890 the Important flag because many users use it to signify that a message
2891 is important to them in some way.
2893 You may also define your own set of keywords.
2894 You might know these as user defined flags or as labels.
2895 These are similar to the Important flag but you choose the names for yourself.
2897 Alpine will only display keywords that
2898 have been added by you in the Flag Details screen or
2899 that have been configured by you using the Setup/Config option
2900 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
2901 Keywords set by other means (for example, by another email client) will not
2902 show up in Alpine unless you configure Alpine to know about them.
2903 They will show up in the Flag Details screen, but will not show up, for example,
2907 The following entries in Alpine's online help provide additional information
2908 about how to use keywords:
2910 <li><A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--> config option</A></li>
2911 <li><A HREF="h_common_flag">Flag command to set keywords</A></li>
2914 <End of help on this topic>
2917 ===== h_mainhelp_roles ======
2920 <TITLE>Roles</TITLE>
2925 You may play different roles depending on who you are replying to. For
2926 example, if you are replying to a message addressed to help-desk you may
2927 be acting as a Help Desk Worker. That role may require that you use a
2928 different return address and/or a different signature.
2931 To configure roles, go to the MAIN MENU and use the Setup command
2932 followed by "Rules" and then "Roles".
2933 The following entries in Alpine's online help provide additional information
2937 <li><a href="h_rules_roles">Setup Roles Screen</a></li>
2938 <li><a href="h_role_select">Roles Screen</a></li>
2941 <End of help on this topic>
2944 ===== h_mainhelp_filtering ======
2947 <TITLE>Filtering</TITLE>
2952 The software that actually delivers mail (the stuff that happens
2953 before Alpine is involved) for you is in a better position to do mail filtering
2955 If possible, you may want to look into using that sort of mail filtering to
2956 deliver mail to different folders, delete it, or forward it.
2957 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
2960 Filtering is a way to automatically move certain messages from one folder
2961 to another or to automatically delete messages.
2962 You may also automatically set the state (Important, New, Deleted, Answered) of messages
2963 and set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
2964 Alpine doesn't have the ability to forward mail to another address or
2965 to deliver vacation messages.
2968 To configure filtering, go to the MAIN MENU and use the Setup command
2969 followed by "Rules" and then "Filters".
2970 The following entries in Alpine's online help provide additional information
2971 about how to use filtering:
2973 <LI> <A HREF="h_rules_filter">Filtering Setup screen</A>
2976 <End of help on this topic>
2979 ===== h_mainhelp_patterns ======
2982 <TITLE>Patterns</TITLE>
2987 Patterns are used with Roles, Filtering, Index Coloring,
2988 Scoring, Other Rules, and Search Rules, so it may help you to understand exactly how Patterns work.
2989 The following entries in Alpine's online help provide information
2990 about using Patterns:
2992 <LI> <A HREF="h_rule_patterns">Patterns</A>
2995 <End of help on this topic>
2998 ===== h_mainhelp_cmdlineopts ======
3001 <TITLE>Command Line Options</TITLE>
3004 <H1>Command Line Options</H1>
3006 Alpine accepts a number of command line arguments, allowing you, for
3007 example, to start Alpine and immediately access a particular folder.
3008 Many of these arguments overlap with options in the Alpine configuration file.
3009 If there is a difference, then an option set on the command line takes
3011 Alpine expects command line arguments (other than addresses) to be
3012 preceded by a "-" (dash) as normally used by UNIX programs.
3013 A <a href="h_command_line_options">full list</a> of command line
3014 possibilities is available.
3016 <End of help on this topic>
3019 ===== h_mainhelp_config ======
3022 <TITLE>Alpine Configuration</TITLE>
3025 <H1>Alpine Configuration</H1>
3027 Unless it has been administratively disabled, the Setup command on the
3028 MAIN MENU has several subcommands that allow you to modify Alpine's behavior.
3029 The possible subcommands are for general Configuration settings,
3030 Printer settings, Changing your Password, Signature setup,
3031 AddressBook setup, Collection Lists setup, Rules (including Roles, Filters,
3032 Scores, Search, Indexcolor, and Other rules), LDAP Directory setup,
3033 and Color configuration.
3034 In particular, the "Config" subcommand has many features you may
3035 set or unset and many other configuration variables that may be set to change
3036 the way Alpine works.
3037 Every one of the hundreds of options available in that configuration settings
3038 screen has help text associated with it.
3039 You may read that text by moving the cursor to highlight the option and then
3040 typing the Help command.
3042 These settings are stored in your personal
3043 "pinerc" configuration file (or, optionally, they may be stored
3044 <A HREF="h_config_remote_config">remotely</A>),
3045 but on shared systems these settings
3046 may be over-ridden by a system-wide control file (due to local site
3047 security or support policies). A global pine configuration file can also
3048 be used to set default values for all Alpine users on a particular system.
3049 Power users may be interested in splitting their personal configuration
3050 data into two pieces, a generic piece and
3051 <A HREF="h_config_exceptions">exceptions</A> which apply to
3052 a particular platform.
3053 They may also be interested in <A HREF="h_config_inheritance">configuration inheritance</A>.
3054 General Alpine configuration information can be found
3055 <A HREF="h_news_config">here</A>.
3057 <End of help on this topic>
3060 ===== h_mainhelp_aggops ======
3063 <TITLE>Aggregate Operations</TITLE>
3066 <H1>Aggregate Operations</H1>
3068 When you are in the MESSAGE INDEX, the available commands
3069 (for example, Delete, Undelete, Save, Reply, and so on)
3070 normally act on a single message.
3071 So, for example, if you press the Delete command, the currently highlighted
3072 message is marked Deleted.
3073 These commands that normally act on a single message may be applied to
3074 several messages at once instead.
3076 By default this feature is turned on, but it could be administratively turned
3077 off to reduce complexity.
3079 <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>
3080 in the Setup/Config screen is used to turn it off or on.
3081 When this feature is turned on, the four commands "Select",
3082 "SelectCur", "ZoomMode", and "Apply"
3084 The two selection commands allow you to mark a set of
3085 messages as being "selected".
3086 The "ZoomMode" command will toggle between
3087 displaying only the selected messages and displaying all the messages.
3088 The "Apply" command allows you to
3089 apply one of the regular MESSAGE INDEX commands to all of the selected
3090 messages instead of to only the highlighted message.
3092 An example aggregate operation would be to catch up when reading
3094 That is, get rid of all the messages in the news group so that you can
3096 The easiest way to do this in Alpine is to use aggregate operations.
3097 You want to Delete all of the messages in the group.
3098 You could start at the top and type "D" once for every message.
3099 A much faster method is to first Select all of the messages in the group,
3100 and then Delete all of them.
3101 This would take four keystrokes:
3103 <CENTER><SAMP>; a (to select all messages)</SAMP></CENTER>
3105 <CENTER><SAMP>a d (to delete all selected messages)</SAMP></CENTER>
3107 Another use of Select is to use it for searching for a particular message
3108 or set of messages in a large folder.
3109 You may know that the message was From a certain user.
3110 You could select all messages from that user to start, and use Zoom to
3111 look at only those messages.
3112 If there were still too many messages to look at you could Narrow the
3113 set of messages further by selecting from all of those messages only
3114 the ones that were after a certain date, or contained a particular phrase
3115 in the Subject, or were too a particular address, and so on.
3116 That may be the end of what you are doing, or you may want to use Apply to
3117 Save or Forward or Print all of the selected messages.
3119 Some related help topics are
3121 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
3122 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
3123 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
3124 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
3125 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
3126 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
3129 <End of help on this topic>
3132 ===== h_mainhelp_readingnews ======
3135 <TITLE>Reading News</TITLE>
3138 <H1>Reading News</H1>
3141 Alpine can read and post to Internet (or USENET) newsgroups, using the same
3142 commands as for mail. Similar to mailing lists but existing on a larger scale,
3143 Usenet newsgroups allow groups of people with common interests to discuss
3144 particular topics. You might find newsgroups related to your career, or you
3145 might wish to check out the online discussion among the fans of your favorite
3148 <H2>Configuring Alpine for Reading News</H2>
3149 Alpine often arrives
3150 pre-configured by your system administrator to automatically access the
3151 newsgroups offered by your organization, Internet Service Provider, or
3152 school. PC-Alpine users, and those attempting to customize Unix Alpine, will
3153 need additional details on <a href="h_configuring_news">how to
3154 configure Alpine to read news</a>.
3156 <H2>Accessing Newsgroups</H2>
3157 The first step in reading news is to access the newsgroups collections
3158 screen from Alpine. If everything is configured properly, you should be able
3159 to do this by first typing L (folder List), then selecting the folder
3160 collection listed as "News." The actual name of this collection may differ
3161 from system to system.
3163 <H2>Subscribing to Newsgroups</H2>
3165 Once you have accessed the news collection, you need to subscribe to a
3166 newsgroup that interests you. Subscribing to a newsgroup means that Alpine
3167 will keep a record of the newsgroups in which you are interested and which
3168 articles in those newsgroups have been read.
3170 <H2>Using Newsgroups</H2>
3171 Alpine uses the similar commands to read news as to read mail. For example,
3172 the D command marks messages as Deleted (or "Dismissed," if you prefer),
3173 and the R command Replies to a news posting. Basically, Alpine allows you to
3174 read news as if it were mail, so you don't need to change the way you
3175 interact with Alpine.
3177 There is also additional Alpine help available on
3178 <A HREF="h_reading_news">how to use Alpine to read news</A>.
3180 <End of help on this topic>
3183 ===== h_mainhelp_securing ======
3186 <TITLE>Securing your Alpine Session</TITLE>
3189 <H1>Securing your Alpine Session</H1>
3191 By default, Alpine will attempt to connect to an IMAP server on the normal
3192 IMAP service port (143).
3193 If the Alpine you are using has been built to
3194 support "Transport Layer Security" (TLS)
3195 and "Secure Sockets Layer" (SSL)
3196 (check by clicking <A HREF="X-Alpine-Config:">here</A>),
3197 and the server offers the STARTTLS capability, then a secure (encrypted)
3198 session will be established.
3200 When you are connected to a remote folder the titlebar will contain a plus sign
3201 in the far right column if the connection is encrypted using TLS or SSL.
3202 Similarly, when you are being prompted for a password a plus sign will appear in the prompt
3203 if the connection is encrypted.
3205 <H2>More Information on Alpine with SSL and TLS</H2>
3207 <LI> <A HREF="h_release_tlscerts">TLS and SSL Usage Note</A> </LI>
3208 <LI> <A HREF="h_folder_server_syntax">/SSL</A> option for older servers which support port 993 SSL but not TLS </LI>
3209 <LI> <A HREF="h_config_alt_auth"><!--#echo var="FEAT_try-alternative-authentication-driver-first"--></A> feature </LI>
3210 <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>
3212 <H2>Here are some other security-related features and options</H2>
3215 <LI> <A HREF="h_config_disable_password_caching"><!--#echo var="FEAT_disable-password-caching"--></A> feature to disable password caching </LI>
3216 <LI> <A HREF="h_config_disable_password_file_saving"><!--#echo var="FEAT_disable-password-file-saving"--></A> Disable password file saving</LI>
3217 <LI> <A HREF="h_config_mailcap_params"><!--#echo var="FEAT_enable-mailcap-param-substitution"--></A> feature </LI>
3218 <LI> <A HREF="h_config_disable_auths"><!--#echo var="VAR_disable-these-authenticators"--></A> option </LI>
3221 <End of help on this topic>
3224 ===== h_mainhelp_problems ======
3227 <TITLE>Reporting Problems</TITLE>
3230 <H1>Reporting Problems</H1>
3232 We ask that you first read the relevant help screens and then seek
3233 assistance from your own local support staff. Once you are sure that your
3234 difficulty is not a local configuration problem, you might look at the
3235 help section explaining where to look for
3236 <A HREF="h_finding_help">more information</A> and where to
3241 Eduardo Chappa <chappa@gmx.com>
3245 <End of help on this topic>
3248 ===== h_main_menu_commands ======
3251 <TITLE>MAIN MENU COMMANDS</TITLE>
3254 <H1>MAIN MENU COMMANDS</H1>
3256 <!--chtml if pinemode="function_key"-->
3257 Available Commands --
3258 Group 1 Available Commands -- Group 2<BR>
3259 ------------------------------
3260 --------------------
3262 F1 Show this help text F1 Show this help text<BR>
3263 F2 Show all other available commands F2 Show other commands<BR>
3264 F3 Quit Alpine<BR>
3265 F4 Execute current MAIN MENU command F4 <A
3266 HREF="h_common_compose">Compose</A> a message<BR>
3267 F5 Select previous command up on menu F5 <A
3268 HREF="h_common_folders">FOLDER LIST</A> screen<BR>
3269 F6 Select next command down on menu F6 <A
3270 HREF="h_common_goto">Goto</A> a specified folder<BR>
3271
3272 F7 <A
3273 HREF="h_common_index">MESSAGE INDEX</A> screen<BR>
3274
3275 F8 <A
3276 HREF="h_main_journal">Journal</A> of status messages<BR>
3277 F9 Display <A
3278 HREF="h_main_release_notes">Release Notes</A> notes F9 <A
3279 HREF="h_main_setup">SETUP</A> menus<BR>
3281 HREF="h_main_kblock">Lock Keyboard</A> F10 <A
3282 HREF="h_main_addrbook">ADDRESS BOOK</A> screen<BR>
3283
3285 HREF="h_common_role">Compose message using a role</a><BR>
3287 General Alpine Commands Main Menu Screen Commands<BR>
3288 --------------------- --------------------------<BR>
3289 ? Show Help Text O Show all Other available commands<BR>
3290 C <A
3291 HREF="h_common_compose">Compose</A> a message P Select Previous command up on menu<BR>
3292 I <A
3293 HREF="h_common_index">MESSAGE INDEX</A> screen N Select Next command down on menu<BR>
3294 L <A
3295 HREF="h_common_folders">FOLDER LIST</A> screen R Display Alpine <A HREF="h_main_release_notes">Release Notes</A><BR>
3296 A <A
3297 HREF="h_main_addrbook">ADDRESS BOOK</A> screen K <A
3298 HREF="h_main_kblock">Lock Keyboard</A><BR>
3299 S <A
3300 HREF="h_main_setup">SETUP</A> functions G <A
3301 HREF="h_common_goto">Goto</A> a specified folder<BR>
3302 Q Quit Alpine J <A HREF="h_main_journal">Journal</A> of status messages<BR>
3303 # <A
3304 HREF="h_common_role">Compose message using a role</a><BR>
3310 <LI>For help on a particular command, highlight the bold text associated
3311 with it above and hit Return.
3312 <LI> The availability of certain commands (e.g. some of the options under
3313 SETUP) is determined by Alpine configuration files and system capabilities.
3314 At some sites, certain commands may not be available due to security or
3318 <End of help on this topic>
3322 ===== h_command_line_options ======
3325 <TITLE>COMMAND LINE OPTIONS</TITLE>
3328 <H1>COMMAND LINE OPTIONS</H1>
3329 Possible starting arguments for Alpine:
3333 <DT> <EM>[addresses]</EM>
3335 <DD> Send-to: If you give <EM>Alpine</EM> an argument or arguments which
3336 do not begin with a dash, <EM>Alpine</EM> treats them as email addresses.
3337 <EM>Alpine</EM> will startup in
3338 the composer with a message started to the addresses specified.
3339 Once the message is sent, the <EM>Alpine</EM> session closes.
3340 Standard input redirection is allowed.
3341 Separate multiple addresses with a space between them.
3342 Addresses are placed in the "To" field only.
3345 <DT> < <EM>file</EM>
3347 <DD> <EM>Alpine</EM> will startup in the composer with <EM>file</EM> read
3348 into the body of the message.
3349 Once the message is sent, the <EM>Alpine</EM> session closes.
3352 <DT> -attach <EM>file</EM>
3354 <DD> Go directly into composer with given file attached.
3357 <DT> -attachlist <EM>file-list</EM>
3359 <DD> Go directly into composer with given files attached.
3360 This must be the last option on the command line.
3363 <DT> -attach_and_delete <EM>file</EM>
3365 <DD> Go directly into composer with given file attached, delete when finished.
3368 <DT> -aux <EM>local_directory</EM>
3370 <DD> <EM>PC-Alpine</EM> only.
3371 This tells <EM>PC-Alpine</EM> the local directory to use for storing auxiliary
3372 files, like debug files, address books, and signature files. The pinerc may
3378 <DD> If the personal configuration file doesn't already exist, exit.
3379 This might be useful if the configuration file is accessed using some
3380 remote filesystem protocol. If the remote mount is missing this will cause
3381 <EM>Alpine</EM> to quit instead of creating a new pinerc.
3386 <DD> When used with the <CODE>-f</CODE> option, apply the <EM>n</EM>th context.
3387 This is used when there are multiple folder collections (contexts) and you
3388 want to open a folder not in the primary collection.
3393 <DD> Configuration: Prints a sample system configuration file to the
3394 screen or standard output. To generate an initial system configuration
3398 pine -conf > <!--#echo var="PINE_CONF_PATH"-->
3402 To generate a system configuration file using settings from an old
3403 system configuration file, execute
3406 pine -P old-pine.conf -conf > <!--#echo var="PINE_CONF_PATH"-->
3409 A system configuration file is not required.
3412 <DT> -copy_abook <<EM>local_abook_file</EM>> <<EM>remote_abook_folder</EM>>
3414 <DD> Copy an address book file to a remote address book folder.
3415 If the remote folder doesn't exist, it will be created.
3416 If it exists but the first message in the folder isn't a remote address
3417 book header message, the copy will be aborted.
3418 This flag will not usually be used by a user.
3419 Instead, the user will create a remote address book from within <EM>Alpine</EM>
3420 and copy entries from the local address book by using aggregate Save in
3421 the address book screen.
3424 <DT> -copy_pinerc <<EM>local_pinerc_file</EM>> <<EM>remote_pinerc_folder</EM>>
3426 <DD> Copy a pinerc configuration file to a remote pinerc folder.
3427 If the remote folder doesn't exist, it will be created.
3428 If it exists but the first message in the folder isn't a remote pinerc
3429 header message, the copy will be aborted.
3430 This flag may be useful to users who already have a local pinerc file and
3431 would like to convert it to a remote pinerc folder and use that instead.
3432 This gives a way to bootstrap that conversion without having to manually
3433 reset all of the variables in the remote pinerc folder.
3436 <DT> -d <EM>debug-level</EM>
3438 <DD> Debug Level: Sets the level of debugging information written by
3440 <EM>debug-level</EM> can be set to any integer 0-9.
3441 A debug level of 0 turns off debugging for the session.
3442 (Actually there are some levels higher than 9, but you probably don't
3446 <DT> -d <EM>keywords</EM>
3448 <DD> You may use a more detailed version of the debugging flag to set
3449 the debug level in separate parts of <EM>Alpine</EM>.
3450 The possibilities are flush, timestamp, imap=0..4, tcp, numfiles=0..31, and
3452 <EM>Flush</EM> causes debugging information to be flushed immediately to
3453 the debug file as it is written.
3454 <EM>Verbose</EM> is the general debugging verbosity level.
3455 <EM>Timestamp</EM> causes timestamps to be added to the debug file, which
3456 is useful when you are trying to figure out what is responsible for delays.
3457 <EM>Numfiles</EM> sets the number of debug files saved.
3458 <EM>Imap</EM> sets the debug level for the debugging statements related
3459 to the conversation with the IMAP server, and more generally, for the
3460 debugging related to <EM>Alpine</EM>'s interaction with the C-Client library.
3461 <EM>Tcp</EM> turns on some TCP/IP debugging.
3464 <DT> -f <EM>folder</EM>
3466 <DD> Startup folder: <EM>Alpine</EM> will open this folder in place
3467 of the standard INBOX.
3470 <DT> -F <EM>file</EM>
3472 <DD> Open named text file for viewing and forwarding.
3477 <DD> Help: Prints the list of available command-line arguments to the
3483 <DD> <EM>Alpine</EM> will start up in the FOLDER INDEX
3484 screen instead of the MAIN MENU.
3487 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"-->=i</EM>.
3490 <DT> -I <EM>a,b,c,...</EM>
3492 <DD> Initial Keystrokes: <EM>Alpine</EM> will execute this comma-separated
3493 sequence of commands upon startup.
3494 This allows users to get <EM>Alpine</EM> to start in any
3495 of its menus/screens.
3496 You cannot include any input to the composer in the initial keystrokes.
3497 The key <Return> is represented by a ``CR'' in
3498 the keystroke list; the spacebar is designated by the letters ``SPACE''.
3499 Control keys are two character sequences beginning with ``^'', such as
3501 A tab character is ``TAB''.
3502 Function keys are ``F1'' - ``F12'' and the arrow keys are ``UP'',
3503 ``DOWN'', ``LEFT'', and ``RIGHT''.
3504 A restriction is that you can't mix function keys and character keys in this
3505 list even though you can, in some cases, mix them when running <EM>Alpine</EM>.
3506 A user can always use only <EM>character</EM> keys in the startup list even
3507 if he or she is using <EM>function</EM> keys normally, or vice versa.
3508 If an element in this list is a string of characters surrounded by double
3509 quotes (") then it will be expanded into the individual characters in
3510 the string, excluding the double quotes.
3513 Configuration equivalent: <EM><!--#echo var="VAR_initial-keystroke-list"--></EM>
3518 <DD> For <EM>PC-Alpine</EM> only, this option prompts the user for
3519 some basic information to help with getting properly set up.
3524 <DD> Function-Key Mode: When invoked in this way, <EM>Alpine</EM> expects
3525 the input of commands to be function-keys.
3526 Otherwise, commands are linked to the regular character keys.
3529 Configuration equivalent: <EM><!--#echo var="FEAT_use-function-keys"--></EM> included in
3530 <EM>Feature-List</EM>.
3535 <DD> Message-Number: When specified, <EM>Alpine</EM> starts up in the
3536 FOLDER INDEX screen with the current message being the specified
3542 <DD> <EM>PC-Alpine</EM> only.
3543 This tells <EM>PC-Alpine</EM> not to display the splash screen upon startup.
3544 This may be helpful for certain troubleshooting or terminal server scenarios.
3547 <DT> -o <EM>folder</EM>
3549 <DD> Opens the INBOX (or a folder specified via the -f argument) ReadOnly.
3552 <DT> -p <EM>pinerc</EM>
3554 <DD> Uses the named file as the personal configuration file instead of
3555 <EM>~/.pinerc</EM> or the default PINERC search sequence <EM>PC-Alpine</EM> uses.
3556 Alpinerc may be either a local file or a remote configuration folder.
3559 <DT> -P <EM>pinerc</EM>
3561 <DD> Uses the named file as the system wide configuration file instead of
3562 <EM><!--#echo var="PINE_CONF_PATH"--></EM> on UNIX, or nothing on <EM>PC-Alpine</EM>.
3563 Alpinerc may be either a local file or a remote configuration folder.
3566 <DT> -passfile <EM>passfile</EM>
3568 <DD> This tells <EM>Alpine</EM> what file should be used as the password file.
3569 This should be a fully-qualified filename.
3572 <DT> -pinerc <EM>file</EM>
3574 <DD> Output fresh pinerc configuration to <EM>file</EM>, preserving the
3575 settings of variables that the user has made.
3576 Use <EM>file</EM> set to ``-'' to make output go to standard out.
3581 <DD> Restricted Mode: For UNIX <EM>Alpine</EM> only.
3582 <EM>Alpine</EM> in restricted mode can only send email to itself.
3583 Save and export are limited.
3586 <DT> -registry <EM>cmd</EM>
3588 <DD> For <EM>PC-Alpine</EM> only, this option affects the values of
3589 <EM>Alpine</EM>'s registry entries.
3590 Possible values for <EM>cmd</EM> are set, clear, and dump.
3591 <EM>Set</EM> will always reset <EM>Alpine</EM>'s registry
3592 entries according to its current settings.
3593 <EM>Clear</EM> will clear the registry values.
3594 <EM>Clearsilent</EM> will clear the registry values without any dialogs.
3595 <EM>Dump</EM> will display the values of current registry settings.
3596 Note that the dump command is currently disabled.
3597 Without the -registry option, <EM>PC-Alpine</EM> will write values into
3598 the registry only if there currently aren't any values set.
3601 <DT> -sort <EM>key</EM>
3603 <DD> Sort-Key: Specifies the order messages will be displayed in for the
3604 FOLDER INDEX screen.
3605 <EM>Key</EM> can have the following values:
3606 arrival, date, subject, orderedsubj, thread, from, size, score, to, cc,
3607 arrival/reverse, date/reverse, subject/reverse, orderedsubj/reverse, thread/reverse,
3608 from/reverse, size/reverse, score/reverse, to/reverse, and cc/reverse.
3609 The default value is "arrival".
3610 The <EM>key</EM> value reverse is equivalent to arrival/reverse.
3613 Configuration equivalent: <EM><!--#echo var="VAR_sort-key"--></EM>.
3618 <DD> For <EM>PC-Alpine</EM> only, this option removes references to Alpine
3619 in Windows settings. The registry settings are removed and
3620 the password cache is cleared.
3623 <DT> -url <EM>url</EM>
3625 <DD> Open the given URL.
3630 <DD> Version: Print version information to the screen.
3633 <DT> -x <EM>exceptions_config</EM>
3635 <DD> Configuration settings in the exceptions configuration override your normal
3637 <EM>Exceptions_config</EM> may be either a local file or a remote Alpine configuration folder.
3642 <DD> Enable Suspend: When run with this flag, the key sequence ctrl-z
3643 will suspend the <EM>Alpine</EM> session.
3646 Configuration equivalent: <EM><!--#echo var="FEAT_enable-suspend"--></EM> included in
3647 <EM>Feature-List</EM>.
3650 <DT> -<EM>option</EM>=<EM>value</EM>
3652 <DD> Assign <EM>value</EM> to the config option <EM>option</EM>.
3653 For example, <EM>-signature-file=sig1</EM> or
3654 <EM>-Feature-List=signature-at-bottom</EM>.
3655 Note: Feature-List values are
3656 additive and features may be preceded with no- to turn them off.
3657 Also, as a special case, the "Feature-List=" part of that may be
3658 omitted. For example, <EM>-signature-at-bottom</EM> is equivalent to
3659 <EM>-Feature-List=signature-at-bottom</EM>.
3664 <End of help on this topic>
3667 ===== h_configuring_news ======
3670 <TITLE>CONFIGURING NEWS</TITLE>
3673 <H1>CONFIGURING NEWS</H1>
3674 Alpine can access news folders in any one of three different ways:
3676 <DT>REMOTE NNTP</DT>
3677 <DD>Using the Network News Transport Protocol (NNTP) to
3678 access news on a remote news server. In this case the newsrc file is
3679 stored on the machine where Alpine is running.
3682 To specify a remote news-collection accessed via NNTP use the
3683 SETUP/collectionList screen's "Add" command. Set the
3684 Server: value to the NNTP server's hostname appended with the
3685 communication method "/service=NNTP", and set the Path:
3686 value to the "#news." namespace (without the quotes). See
3687 the "<A HREF="h_composer_cntxt_server">Server:</A>" field's
3688 help text for a more complete explanation of access method, and the
3689 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3690 text for a more complete explanation of "namespace".
3692 Instead of specifying a news-collection, you may simply set the
3693 <A HREF="h_config_nntp_server">NNTP Server</A>
3694 option, which will cause Alpine to create a default news-collection for you.
3695 Another NNTP option that may be of interest is
3696 <A HREF="h_config_nntprange"><!--#echo var="VAR_nntp-range"--></A>.
3698 <DT>REMOTE IMAP</DT>
3699 <DD>Using the Internet Message Access Protocol (IMAP) to
3700 access news on a remote news server. In this case, your newsrc file is
3701 stored on the news server, in your home directory, so you must have an
3702 account on the news server, but you would be running Alpine on a different
3703 machine. The news server must be running an IMAPd server process.
3706 To specify a remote news-collection accessed via IMAP use the
3707 SETUP/collectionList screen's "Add" command. Set the
3708 Server: value to the IMAP server's hostname, and set the Path: value
3709 to the "#news." namespace (without the quotes). See the
3710 "<A HREF="h_composer_cntxt_path">Path:</A>" field's help
3711 text for a more complete explanation of "namespace".
3716 <DD>Using local file access to the news database. In this
3717 case, your newsrc file is stored on the news server, in your home
3718 directory, so you must have an account on the news server, and you would
3719 be running Alpine on the same machine.
3722 To specify a local news-collection use the SETUP/collectionList
3723 screen's "Add" command. Leave the Server: value blank, and
3724 set the Path: value to the "#news." namespace (without the
3725 quotes). See the "<A HREF="h_composer_cntxt_path">Path:</A>"
3726 field's help text for a more complete explanation of "namespace".
3733 NOTE: Should no news-collection be defined as above, Alpine will
3734 automatically create one using the Setup/Config screen's
3735 "<!--#echo var="VAR_nntp-server"-->" variable's value if defined. The collection
3736 will be created as a "Remote NNTP" as described above.
3740 If you are a PC-Alpine user, either option 1 (NNTP) or option 2 (IMAP) is
3741 possible. If you don't have an account on the news server, or if the news
3742 server is not running an IMAP daemon, then you must use NNTP. (If you are not
3743 sure, ask your service provider, university, or company for help.) In
3744 this case, your Unix .newsrc file can be transferred to your PC. A good
3745 place to put it would be in the same directory as your PINERC file, under
3746 the name NEWSRC, but you can
3747 <A HREF="h_config_newsrc_path">specify a different location</A>
3748 via Alpine's Setup/Config screen.
3751 Other configuration features related to news are
3752 <A HREF="h_config_8bit_nntp"><!--#echo var="FEAT_enable-8bit-nntp-posting"--></A>.
3753 <A HREF="h_config_compose_news_wo_conf"><!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></A>,
3754 <A HREF="h_config_news_uses_recent"><!--#echo var="FEAT_news-approximates-new-status"--></A>,
3755 <A HREF="h_config_news_cross_deletes"><!--#echo var="FEAT_news-deletes-across-groups"--></A>,
3756 <A HREF="h_config_news_catchup"><!--#echo var="FEAT_news-offers-catchup-on-close"--></A>,
3757 <A HREF="h_config_post_wo_validation"><!--#echo var="FEAT_news-post-without-validation"--></A>,
3758 <A HREF="h_config_read_in_newsrc_order"><!--#echo var="FEAT_news-read-in-newsrc-order"--></A>, and
3759 <A HREF="h_config_quell_post_prompt"><!--#echo var="FEAT_quell-extra-post-prompt"--></A>.
3762 <End of help on this topic>
3765 ===== h_reading_news ======
3768 <TITLE>READING NEWS</TITLE>
3771 <H1>READING NEWS</H1>
3773 Alpine uses almost the same commands for manipulating news folders as for
3774 mail folders. This means, for example, that when you are done with a
3775 message, you would use "D" to mark it as Deleted (or Dismissed,
3776 if you prefer.) This "mail-like" behavior differs from that of
3777 most newsreaders, wherein a message is implicitly dismissed after you have
3778 looked at it once. We strongly believe that Alpine should offer as much
3779 consistency as possible between mail and news, so the mail paradigm --
3780 wherein a message does not magically disappear without explicit action by
3781 the user -- is used for news as well. <P>
3783 If you answer a message in a news folder, the index view will show the
3784 "A" flag as usual; but the industry standard file Alpine uses to
3785 keep track of what news as been read has no way of storing this flag, so
3786 it will not be preserved across sessions. The Deleted flag is the only
3787 one that is preserved when you leave and then return to a newsgroup. As an
3788 additional note on replies, when you Reply to a newsgroup message and say
3789 you want to reply to all recipients, Alpine will ask if you want to post the
3790 message to all the newsgroups listed in the original message. <P>
3792 If you would like Alpine to mark more-or-less recent news messages as
3793 "New", then set the
3794 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
3795 feature (which is set by default). This will cause messages after the last one you have marked as
3796 Deleted to appear with "N" status in the MESSAGE INDEX. The
3797 "N" status often makes it easier to distinguish later news
3798 articles from those you've previously seen, but not yet disposed of via
3799 the "D" key. Note that this is an approximation, not an exact
3800 record of which messages you have not seen.
3803 A frequent operation in news-reading is "catching up" -- that
3804 is, getting rid of all the messages in the newsgroup so that you can
3805 "start fresh." The easiest way to do this in Alpine is via the
3806 Select command. You would enter the following four keystrokes:
3807 <tt>;aad</tt> to select all messaged, and then apply the delete (or
3808 dismiss) command to all of them.
3811 There are also additional details on
3812 <A HREF="h_configuring_news">configuring news</a>.
3815 <End of help on this topic>
3818 ====== h_help_index ======
3821 <TITLE>Help Index</TITLE>
3826 <li><a href="h_mainhelp_abooks">Address Books</a></li>
3827 <li><a href="h_abook_top">ADDRESS BOOK LIST COMMANDS</a>
3828 <li><a href="h_main_addrbook">Address Book Command</a>
3829 <li><a href="h_abook_view">Address Book View Explained</a>
3830 <li><a href="h_compose_addrcomplete">Address Completion</a>
3831 <li><a href="h_abook_select_listmode">Address Listmode Selection from Composer Explained</a>
3832 <li><a href="h_abook_select_checks">Address Selection from Composer Explained</a>
3833 <li><a href="h_composer_abook_comment">Addressbook Comment Explained</a>
3834 <li><a href="h_composer_abook_fcc">Addressbook Fcc Explained</a>
3835 <li><a href="h_composer_abook_add_folder">Addressbook Folder Name Field Explained</a>
3836 <li><a href="h_composer_abook_full">Addressbook Fullname Explained</a>
3837 <li><a href="h_composer_abook_add_nick">Addressbook NickName Field Explained</a>
3838 <li><a href="h_composer_abook_nick">Addressbook Nickname Explained</a>
3839 <li><a href="h_abook_select_addr">Addressbook Selection Explained</a>
3840 <li><a href="h_abook_select_top">Addressbook Selection Navigation Explained</a>
3841 <li><a href="h_composer_abook_add_server">Addressbook Server Name Field Explained</a>
3842 <li><a href="h_mainhelp_aggops">Aggregate Operations</a>
3843 <li><a href="h_mainhelp_config">Alpine Configuration</a>
3844 <li><a href="h_mainhelp_pinehelp">Alpine Help</a>
3845 <li><a href="h_news_legal">Alpine Legal Notices</a>
3846 <li><a href="h_compose_alted">Alt Editor Command</a>
3847 <li><a href="h_index_cmd_apply">Apply Command</a>
3848 <li><a href="h_attachment_screen">Attachment Index Screen Explained</a>
3849 <li><a href="h_mail_text_att_view">Attachment View Screen Explained</a>
3850 <li><a href="h_mainhelp_filtering">Blocking Messages</a>
3851 <li><a href="h_composer_browse">BROWSER</a>
3852 <li><a href="h_common_bounce">Bounce Command</a>
3853 <li><a href="h_compose_cancel">Cancel Command</a>
3854 <li><a href="h_config_change_your_from">Changing your From Address</a>
3855 <li><a href="h_collection_screen">COLLECTION LIST screen</a>
3856 <li><a href="h_mainhelp_color">Color</a>
3857 <li><a href="h_composer_ctrl_j">COMPOSER ATTACH</a>
3858 <li><a href="h_composer">COMPOSER COMMANDS</a>
3859 <li><a href="h_mainhelp_composing">Composing Messages</a>
3860 <li><a href="h_mainhelp_collections">Collection Lists</a>
3861 <li><a href="h_composer_cntxt_nick">Collection Nickname Explained</a>
3862 <li><a href="h_composer_cntxt_path">Collection Path: Explained</a>
3863 <li><a href="h_composer_cntxt_server">Collection Server: Explained</a>
3864 <li><a href="h_composer_cntxt_view">Collection View: Explained</a>
3865 <li><a href="h_mainhelp_cmdlineopts">Command Line Options</a>
3866 <li><a href="h_common_compose">Compose Command</a>
3867 <li><a href="h_edit_nav_cmds">Composer Editing Commands Explained</a>
3868 <li><a href="h_common_conditional_cmds">Conditional Commands</a>
3869 <li><a href="h_reply_token_conditionals">Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</a>
3870 <li><a href="h_mainhelp_config">Configuration</a>
3871 <li><a href="h_composer_custom_free">CUSTOMIZED HEADER FIELD</a>
3872 <li><a href="h_config_dflt_color">Default Color</a>
3873 <li><a href="h_common_delete">Delete and Undelete Commands</a>
3874 <li><a href="h_composer_qserv_cn">Directory Query Form Explained</a>
3875 <li><a href="h_special_list_commands">Email List Commands Explained</a>
3876 <li><a href="h_composer_search">Explanation of Composer Whereis Command </a>
3877 <li><a href="h_folder_open">Explanation of Folder Selection</a>
3878 <li><a href="h_special_xon_xoff">Explanation of Alpine's XOFF/XON Handling</a>
3879 <li><a href="h_valid_folder_names">Explanation of Valid Folder Names</a>
3880 <li><a href="h_ge_export">Export File Selection</a>
3881 <li><a href="h_ge_allparts">Export Message File Selection</a>
3882 <li><a href="h_index_cmd_expunge">Expunge/Exclude Command</a>
3883 <li><a href="h_info_on_locking">FAQs on Alpine Locking</a>
3884 <li><a href="h_config_allow_chg_from">FEATURE: <!--#echo var="FEAT_allow-changing-from"--></a>
3885 <li><a href="h_config_allow_talk">FEATURE: <!--#echo var="FEAT_allow-talk"--></a>
3886 <li><a href="h_config_alt_compose_menu">FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></a>
3887 <li><a href="h_config_alt_role_menu">FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></a>
3888 <li><a href="h_config_alt_reply_menu">FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></a>
3889 <li><a href="h_config_force_low_speed">FEATURE: <!--#echo var="FEAT_assume-slow-link"--></a>
3890 <li><a href="h_config_auto_read_msgs">FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></a>
3891 <li><a href="h_config_auto_open_unread">FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></a>
3892 <li><a href="h_config_auto_unselect">FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></a>
3893 <li><a href="h_config_auto_unzoom">FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></a>
3894 <li><a href="h_config_auto_zoom">FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></a>
3895 <li><a href="h_config_use_boring_spinner">FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></a>
3896 <li><a href="h_config_check_mail_onquit">FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></a>
3897 <li><a href="h_config_combined_abook_display">FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></a>
3898 <li><a href="h_config_combined_folder_display">FEATURE: <!--#echo var="FEAT_combined-folder-display"--></a>
3899 <li><a href="h_config_combined_subdir_display">FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></a>
3900 <li><a href="h_config_cancel_confirm">FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></a>
3901 <li><a href="h_config_lame_list_mode">FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></a>
3902 <li><a href="h_config_compose_rejects_unqual">FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></a>
3903 <li><a href="h_config_send_filter_dflt">FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></a>
3904 <li><a href="h_config_compose_news_wo_conf">FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></a>
3905 <li><a href="h_config_del_from_dot">FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></a>
3906 <li><a href="h_config_compose_maps_del">FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></a>
3907 <li><a href="h_config_confirm_role">FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></a>
3908 <li><a href="h_config_tab_no_prompt">FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></a>
3909 <li><a href="h_config_dates_to_local">FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></a>
3910 <li><a href="h_config_copy_to_to_from">FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></a>
3911 <li><a href="h_config_del_skips_del">FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></a>
3912 <li><a href="h_config_disable_config_cmd">FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></a>
3913 <li><a href="h_config_disable_index_locale_dates">FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></a>
3914 <li><a href="h_config_disable_kb_lock">FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></a>
3915 <li><a href="h_config_blank_keymenu">FEATURE: <!--#echo var="FEAT_disable-keymenu"--></a>
3916 <li><a href="h_config_disable_password_caching">FEATURE: <!--#echo var="FEAT_disable-password-caching"--></a>
3917 <li><a href="h_config_disable_password_cmd">FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></a>
3918 <li><a href="h_config_disable_pipes_in_sigs">FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></a>
3919 <li><a href="h_config_disable_pipes_in_templates">FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></a>
3920 <li><a href="h_config_disable_regex">FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
3921 <li><a href="h_config_disable_roles_setup">FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></a>
3922 <li><a href="h_config_disable_roles_sigedit">FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></a>
3923 <li><a href="h_config_disable_roles_templateedit">FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></a>
3924 <li><a href="h_config_input_history">FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></a>
3925 <li><a href="h_config_disable_collate">FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></a>
3926 <li><a href="h_config_disable_shared">FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></a>
3927 <li><a href="h_config_disable_signature_edit">FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></a>
3928 <li><a href="h_config_take_fullname">FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></a>
3929 <li><a href="h_config_take_lastfirst">FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></a>
3930 <li><a href="h_config_disable_reset_disp">FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></a>
3931 <li><a href="h_config_disable_sender">FEATURE: <!--#echo var="FEAT_disable-sender"--></a>
3932 <li><a href="h_config_quell_dead_letter">FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></a>
3933 <li><a href="h_config_quell_flowed_text">FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></a>
3934 <li><a href="h_downgrade_multipart_to_text">FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></a>
3935 <li><a href="h_config_8bit_smtp">FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></a>
3936 <li><a href="h_config_8bit_nntp">FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></a>
3937 <li><a href="h_config_enable_agg_ops">FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></a>
3938 <li><a href="h_config_enable_alt_ed">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></a>
3939 <li><a href="h_config_alt_ed_now">FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></a>
3940 <li><a href="h_config_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></a>
3941 <li><a href="h_config_relaxed_arrow_nav">FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></a>
3942 <li><a href="h_config_compose_bg_post">FEATURE: <!--#echo var="FEAT_enable-background-sending"--></a>
3943 <li><a href="h_config_enable_bounce">FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></a>
3944 <li><a href="h_config_cruise_mode">FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></a>
3945 <li><a href="h_config_cruise_mode_delete">FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></a>
3946 <li><a href="h_config_compose_dsn">FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></a>
3947 <li><a href="h_config_enable_dot_files">FEATURE: <!--#echo var="FEAT_enable-dot-files"--></a>
3948 <li><a href="h_config_enable_lessthan_exit">FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></a>
3949 <li><a href="h_config_fast_recent">FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></a>
3950 <li><a href="h_config_enable_flag">FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></a>
3951 <li><a href="h_config_flag_screen_default">FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></a>
3952 <li><a href="h_config_flag_screen_kw_shortcut">FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></a>
3953 <li><a href="h_config_enable_full_hdr_and_text">FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></a>
3954 <li><a href="h_config_enable_full_hdr">FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></a>
3955 <li><a href="h_config_allow_goto">FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></a>
3956 <li><a href="h_config_enable_dot_folders">FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></a>
3957 <li><a href="h_config_enable_incoming">FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></a>
3958 <li><a href="h_config_enable_incoming_checking">FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></a>
3959 <li><a href="h_config_enable_jump">FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></a>
3960 <li><a href="h_config_show_delay_cue">FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></a>
3961 <li><a href="h_config_mailcap_params">FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></a>
3962 <li><a href="h_config_enable_mouse">FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></a>
3963 <li><a href="h_config_enable_view_addresses">FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></a>
3964 <li><a href="h_config_enable_view_attach">FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></a>
3965 <li><a href="h_config_enable_view_arrows">FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></a>
3966 <li><a href="h_config_enable_view_url">FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></a>
3967 <li><a href="h_config_enable_view_web_host">FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></a>
3968 <li><a href="h_config_enable_mulnewsrcs">FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></a>
3969 <li><a href="h_config_enable_xterm_newmail">FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></a>
3970 <li><a href="h_config_enable_newmail_short_text">FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>
3971 <li><a href="h_config_sub_lists">FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></a>
3972 <li><a href="h_config_enable_y_print">FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></a>
3973 <li><a href="h_config_prefix_editing">FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></a>
3974 <li><a href="h_config_enable_search_and_repl">FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></a>
3975 <li><a href="h_config_sigdashes">FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></a>
3976 <li><a href="h_config_new_thread_blank_subject">FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></a>
3977 <li><a href="h_config_can_suspend">FEATURE: <!--#echo var="FEAT_enable-suspend"--></a>
3978 <li><a href="h_config_enable_tab_complete">FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></a>
3979 <li><a href="h_config_enable_take_export">FEATURE: <!--#echo var="FEAT_enable-take-export"--></a>
3980 <li><a href="h_config_enable_role_take">FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></a>
3981 <li><a href="h_config_tray_icon">FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></a>
3982 <li><a href="h_config_enable_pipe">FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></a>
3983 <li><a href="h_config_verbose_post">FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></a>
3984 <li><a href="h_config_expanded_addrbooks">FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></a>
3985 <li><a href="h_config_expanded_distlists">FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></a>
3986 <li><a href="h_config_expanded_folders">FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></a>
3987 <li><a href="h_config_expose_hidden_config">FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></a>
3988 <li><a href="h_config_expunge_manually">FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></a>
3989 <li><a href="h_config_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></a>
3990 <li><a href="h_config_full_auto_expunge">FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></a>
3991 <li><a href="h_config_no_fcc_attach">FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></a>
3992 <li><a href="h_config_force_arrow">FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></a>
3993 <li><a href="h_config_ignore_size">FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></a>
3994 <li><a href="h_config_forward_as_attachment">FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></a>
3995 <li><a href="h_config_preserve_field">FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></a>
3996 <li><a href="h_config_quell_empty_dirs">FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></a>
3997 <li><a href="h_config_hide_nntp_path">FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></a>
3998 <li><a href="h_config_attach_in_reply">FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></a>
3999 <li><a href="h_config_fcc_on_bounce">FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></a>
4000 <li><a href="h_config_include_header">FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></a>
4001 <li><a href="h_config_auto_include_reply">FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></a>
4002 <li><a href="h_config_incoming_checking_total">FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></a>
4003 <li><a href="h_config_incoming_checking_recent">FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></a>
4004 <li><a href="h_config_add_ldap">FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></a>
4005 <li><a href="h_config_maildrops_preserve_state">FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></a>
4006 <li><a href="h_config_mark_fcc_seen">FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></a>
4007 <li><a href="h_config_mark_for_cc">FEATURE: <!--#echo var="FEAT_mark-for-cc"--></a>
4008 <li><a href="h_config_mulnews_as_typed">FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></a>
4009 <li><a href="h_config_news_uses_recent">FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></a>
4010 <li><a href="h_config_news_cross_deletes">FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></a>
4011 <li><a href="h_config_news_catchup">FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></a>
4012 <li><a href="h_config_post_wo_validation">FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></a>
4013 <li><a href="h_config_read_in_newsrc_order">FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></a>
4014 <li><a href="h_config_nntp_search_uses_overview">FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></a>
4015 <li><a href="h_config_thread_sorts_by_arrival">FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></a>
4016 <li><a href="h_config_expunge_inbox">FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></a>
4017 <li><a href="h_config_expunge_stayopens">FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></a>
4018 <li><a href="h_config_pass_c1_control">FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></a>
4019 <li><a href="h_config_pass_control">FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></a>
4020 <li><a href="h_config_predict_nntp_server">FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></a>
4021 <li><a href="h_config_prefer_plain_text">FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></a>
4022 <li><a href="h_config_preopen_stayopens">FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></a>
4023 <li><a href="h_config_preserve_start_stop">FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></a>
4024 <li><a href="h_config_quell_folder_internal_msg">FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></a>
4025 <li><a href="h_config_quell_checks_comp">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></a>
4026 <li><a href="h_config_quell_checks_comp_inbox">FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></a>
4027 <li><a href="h_config_quell_partial">FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></a>
4028 <li><a href="h_config_quell_local_lookup">FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></a>
4029 <li><a href="h_config_ff_between_msgs">FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></a>
4030 <li><a href="h_config_print_from">FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></a>
4031 <li><a href="h_config_print_index">FEATURE: <!--#echo var="FEAT_print-index-enabled"--></a>
4032 <li><a href="h_config_custom_print">FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></a>
4033 <li><a href="h_config_prune_uses_iso">FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></a>
4034 <li><a href="h_config_quell_personal_name_prompt">FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></a>
4035 <li><a href="h_config_quell_ssl_largeblocks">FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></a>
4036 <li><a href="h_config_quell_user_id_prompt">FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></a>
4037 <li><a href="h_config_quit_wo_confirm">FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></a>
4038 <li><a href="h_config_quote_replace_noflow">FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></a>
4039 <li><a href="h_config_next_thrd_wo_confirm">FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></a>
4040 <li><a href="h_config_auto_reply_to">FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></a>
4041 <li><a href="h_config_inbox_no_confirm">FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></a>
4042 <li><a href="h_config_save_aggregates">FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></a>
4043 <li><a href="h_config_save_part_wo_confirm">FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></a>
4044 <li><a href="h_config_save_advances">FEATURE: <!--#echo var="FEAT_save-will-advance"--></a>
4045 <li><a href="h_config_save_wont_delete">FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></a>
4046 <li><a href="h_config_quote_all_froms">FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></a>
4047 <li><a href="h_config_scramble_message_id">FEATURE: <!--#echo var="FEAT_scramble-message-id"--></a>
4048 <li><a href="h_config_select_wo_confirm">FEATURE: <!--#echo var="FEAT_select-without-confirm"--></a>
4049 <li><a href="h_config_auto_fcc_only">FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></a>
4050 <li><a href="h_config_send_wo_confirm">FEATURE: <!--#echo var="FEAT_send-without-confirm"--></a>
4051 <li><a href="h_config_separate_fold_dir_view">FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></a>
4052 <li><a href="h_config_show_cursor">FEATURE: <!--#echo var="FEAT_show-cursor"--></a>
4053 <li><a href="h_config_textplain_int">FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></a>
4054 <li><a href="h_config_select_in_bold">FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></a>
4055 <li><a href="h_config_show_sort">FEATURE: <!--#echo var="FEAT_show-sort"--></a>
4056 <li><a href="h_config_single_list">FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></a>
4057 <li><a href="h_config_sig_at_bottom">FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></a>
4058 <li><a href="h_config_slash_coll_entire">FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></a>
4059 <li><a href="h_config_sort_fcc_alpha">FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></a>
4060 <li><a href="h_config_sort_save_alpha">FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></a>
4061 <li><a href="h_config_always_spell_check">FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></a>
4062 <li><a href="h_config_winpos_in_config">FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></a>
4063 <li><a href="h_config_strip_sigdashes">FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>
4064 <li><a href="h_config_strip_ws_before_send">FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></a>
4065 <li><a href="h_config_quells_asterisks">FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></a>
4066 <li><a href="h_config_quell_attach_ext_warn">FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></a>
4067 <li><a href="h_config_quell_attach_extra_prompt">FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></a>
4068 <li><a href="h_config_no_bezerk_zone">FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></a>
4069 <li><a href="h_config_quell_charset_warning">FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></a>
4070 <li><a href="h_config_quell_content_id">FEATURE: <!--#echo var="FEAT_quell-content-id"--></a>
4071 <li><a href="h_config_quell_post_prompt">FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></a>
4072 <li><a href="h_config_quell_filtering_done_message">FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></a>
4073 <li><a href="h_config_quell_filtering_messages">FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></a>
4074 <li><a href="h_config_quell_full_hdr_reset">FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></a>
4075 <li><a href="h_config_quell_imap_env">FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></a>
4076 <li><a href="h_config_quell_lock_failure_warnings">FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></a>
4077 <li><a href="h_config_quell_domain_warn">FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></a>
4078 <li><a href="h_config_quell_news_env">FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></a>
4079 <li><a href="h_config_quell_host_after_url">FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></a>
4080 <li><a href="h_config_quell_beeps">FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></a>
4081 <li><a href="h_config_quell_tz_comment">FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></a>
4082 <li><a href="h_config_suppress_user_agent">FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></a>
4083 <li><a href="h_config_tab_checks_recent">FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></a>
4084 <li><a href="h_config_tab_uses_unseen">FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></a>
4085 <li><a href="h_config_tab_new_only">FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></a>
4086 <li><a href="h_config_termcap_wins">FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></a>
4087 <li><a href="h_config_color_thrd_import">FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></a>
4088 <li><a href="h_config_alt_auth">FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></a>
4089 <li><a href="h_config_unsel_wont_advance">FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></a>
4090 <li><a href="h_config_use_current_dir">FEATURE: <!--#echo var="FEAT_use-current-dir"--></a>
4091 <li><a href="h_config_use_fk">FEATURE: <!--#echo var="FEAT_use-function-keys"--></a>
4092 <li><a href="h_config_use_reg_start_for_stayopen">FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></a>
4093 <li><a href="h_config_use_resentto">FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></a>
4094 <li><a href="h_config_use_sender_not_x">FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></a>
4095 <li><a href="h_config_suspend_spawns">FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></a>
4096 <li><a href="h_config_use_system_translation">FEATURE: Use System Translation</a>
4097 <li><a href="h_config_vertical_list">FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></a>
4098 <li><a href="h_config_warn_if_fcc_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></a>
4099 <li><a href="h_config_warn_if_subj_blank">FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></a>
4100 <li><a href="h_config_warn_if_no_to_or_cc">FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></a>
4101 <li><a href="h_mainhelp_filtering">Filtering</a>
4102 <li><a href="h_finding_help">Finding more information and requesting help</a>
4103 <li><a href="h_common_flag">Flag Command</a>
4104 <li><a href="h_config_quell_flowed_text">Flowed Text</a>
4105 <li><a href="h_mainhelp_folders">Folders</a>
4106 <li><a href="h_what_are_collections">Folder Collections Explained</a>
4107 <li><a href="h_common_folders">Folder List Command</a>
4108 <li><a href="h_folder_fcc">Folder Select for Fcc Explained</a>
4109 <li><a href="h_folder_save">Folder Select for Save Explained</a>
4110 <li><a href="h_folder_server_syntax">Folder Server Name Syntax</a>
4111 <li><a href="h_config_change_your_from">From Address, Changing</a>
4112 <li><a href="main_menu_tx">GENERAL INFORMATION ON THE ALPINE MESSAGE SYSTEM</a>
4113 <li><a href="h_pine_for_windows">GETTING HELP IN ALPINE</a>
4114 <li><a href="h_common_goto">Goto Command</a>
4115 <li><a href="h_common_hdrmode">HdrMode Command</a>
4116 <li><a href="h_mainhelp_pinehelp">Help</a>
4117 <li><a href="h_special_help_nav">Help Text Navigation Explained</a>
4118 <li><a href="h_folder_maint">Help for Folder List</a>
4119 <li><a href="h_valid_folder_names">IMAP</a>
4120 <li><a href="h_ge_import">Import File Selection</a>
4121 <li><a href="h_mainhelp_index">Index of Messages</a>
4122 <li><a href="h_composer_ins_m">INSERT MESSAGE</a>
4123 <li><a href="h_composer_ins">INSERT TEXT FILE</a>
4124 <li><a href="h_address_format">INTERNET EMAIL ADDRESS FORMAT</a>
4125 <li><a href="h_info_on_mbox">Information on mbox driver</a>
4126 <li><a href="h_mainhelp_intro">Introduction</a>
4127 <li><a href="h_main_journal">Journal Command</a>
4128 <li><a href="h_common_jump">Jump Command</a>
4129 <li><a href="h_compose_justify">Justify Command</a>
4130 <li><a href="h_main_kblock">Keyboard Lock Command</a>
4131 <li><a href="h_mainhelp_keywords">Keywords (or Flags, or Labels)</a>
4132 <li><a href="h_mainhelp_ldap">LDAP</a>
4133 <li><a href="h_config_ldap_opts_tls">LDAP FEATURE: Attempt-TLS-On-Connection</a>
4134 <li><a href="h_config_ldap_opts_nosub">LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</a>
4135 <li><a href="h_config_ldap_opts_rhs">LDAP FEATURE: Lookup-Addrbook-Contents</a>
4136 <li><a href="h_config_ldap_opts_tlsmust">LDAP FEATURE: Require-TLS-On-Connection</a>
4137 <li><a href="h_config_ldap_opts_ldaps">LDAP FEATURE: Require-LDAPS-On-Connection</a>
4138 <li><a href="h_config_ldap_opts_ref">LDAP FEATURE: Save-Search-Criteria-Not-Result</a>
4139 <li><a href="h_config_ldap_opts_impl">LDAP FEATURE: Use-Implicitly-From-Composer</a>
4140 <li><a href="h_config_ldap_binddn">LDAP OPTION: Bind-DN</a>
4141 <li><a href="h_config_ldap_cust">LDAP OPTION: Custom-Search-Filter</a>
4142 <li><a href="h_config_ldap_email_attr">LDAP OPTION: EmailAttribute</a>
4143 <li><a href="h_config_ldap_gn_attr">LDAP OPTION: GivennameAttribute</a>
4144 <li><a href="h_config_ldap_server">LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></a>
4145 <li><a href="h_config_ldap_cn_attr">LDAP OPTION: NameAttribute</a>
4146 <li><a href="h_config_ldap_nick">LDAP OPTION: Nickname</a>
4147 <li><a href="h_config_ldap_port">LDAP OPTION: Port</a>
4148 <li><a href="h_config_ldap_base">LDAP OPTION: Search-Base</a>
4149 <li><a href="h_config_ldap_searchrules">LDAP OPTION: Search-Rule</a>
4150 <li><a href="h_config_ldap_searchtypes">LDAP OPTION: Search-Type</a>
4151 <li><a href="h_config_ldap_size">LDAP OPTION: Sizelimit</a>
4152 <li><a href="h_config_ldap_sn_attr">LDAP OPTION: SurnameAttribute</a>
4153 <li><a href="h_config_ldap_time">LDAP OPTION: Timelimit</a>
4154 <li><a href="h_ldap_view">LDAP Response View Explained</a>
4155 <li><a href="h_maildrop">Mail Drop: What is it?</a>
4156 <li><a href="h_mainhelp_mainmenu">MAIN MENU</a>
4157 <li><a href="h_mail_index">MESSAGE INDEX COMMANDS</a>
4158 <li><a href="h_mail_view">MESSAGE TEXT SCREEN</a>
4159 <li><a href="h_compose_markcutpaste">Mark, Cut and Paste Commands</a>
4160 <li><a href="h_common_index">Message Index Command</a>
4161 <li><a href="h_mainhelp_mouse">Mouse</a>
4162 <li><a href="h_mainhelp_aggops">Multiple Message Operations</a>
4163 <li><a href="new_user_greeting">NEW USER GREETING</a>
4164 <li><a href="new_version_greeting">NEW VERSION GREETING</a>
4165 <li><a href="h_mainhelp_readingnews">News Reading</a>
4166 <li><a href="h_folder_subscribe">Newsgroup Subcribe Screen explained</a>
4167 <li><a href="h_folder_postnews">Newsgroup selecting for Posting explained</a>
4168 <li><a href="h_common_nextnew">NextNew Command</a>
4169 <li><a href="h_abook_select_nick">Nickname Selection Explained</a>
4170 <li><a href="h_mainhelp_readingnews">NNTP</a>
4171 <li><a href="h_config_address_book">OPTION: <!--#echo var="VAR_address-book"--></a>
4172 <li><a href="h_config_abook_formats">OPTION: <!--#echo var="VAR_addressbook-formats"--></a>
4173 <li><a href="h_config_ab_sort_rule">OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></a>
4174 <li><a href="h_config_alt_addresses">OPTION: <!--#echo var="VAR_alt-addresses"--></a>
4175 <li><a href="h_config_active_msg_interval">OPTION: <!--#echo var="VAR_busy-cue-rate"--></a>
4176 <li><a href="h_config_color_style">OPTION: Color Style</a>
4177 <li><a href="h_config_wordseps">OPTION: <!--#echo var="VAR_composer-word-separators"--></a>
4178 <li><a href="h_config_composer_wrap_column">OPTION: <!--#echo var="VAR_composer-wrap-column"--></a>
4179 <li><a href="h_config_index_color_style">OPTION: <!--#echo var="VAR_current-indexline-style"--></a>
4180 <li><a href="h_config_cursor_style">OPTION: Cursor Style</a>
4181 <li><a href="h_config_custom_hdrs">OPTION: <!--#echo var="VAR_customized-hdrs"--></a>
4182 <li><a href="h_config_deadlets">OPTION: <!--#echo var="VAR_dead-letter-files"--></a>
4183 <li><a href="h_config_comp_hdrs">OPTION: <!--#echo var="VAR_default-composer-hdrs"--></a>
4184 <li><a href="h_config_default_fcc">OPTION: <!--#echo var="VAR_default-fcc"--></a>
4185 <li><a href="h_config_def_save_folder">OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></a>
4186 <li><a href="h_config_disable_auths">OPTION: <!--#echo var="VAR_disable-these-authenticators"--></a>
4187 <li><a href="h_config_disable_drivers">OPTION: <!--#echo var="VAR_disable-these-drivers"--></a>
4188 <li><a href="h_config_char_set">OPTION: Display Character Set</a>
4189 <li><a href="h_config_display_filters">OPTION: <!--#echo var="VAR_display-filters"--></a>
4190 <li><a href="h_config_download_cmd">OPTION: <!--#echo var="VAR_download-command"--></a>
4191 <li><a href="h_config_download_prefix">OPTION: <!--#echo var="VAR_download-command-prefix"--></a>
4192 <li><a href="h_config_editor">OPTION: <!--#echo var="VAR_editor"--></a>
4193 <li><a href="h_config_empty_hdr_msg">OPTION: <!--#echo var="VAR_empty-header-message"--></a>
4194 <li><a href="h_config_fcc_rule">OPTION: <!--#echo var="VAR_fcc-name-rule"--></a>
4195 <li><a href="h_config_file_dir">OPTION: File Directory</a>
4196 <li><a href="h_config_folder_spec">OPTION: <!--#echo var="VAR_folder-collections"--></a>
4197 <li><a href="h_config_reopen_rule">OPTION: <!--#echo var="VAR_folder-reopen-rule"--></a>
4198 <li><a href="h_config_fld_sort_rule">OPTION: <!--#echo var="VAR_folder-sort-rule"--></a>
4199 <li><a href="h_config_font_char_set">OPTION: Font Character Set</a>
4200 <li><a href="h_config_font_name">OPTION: Font Name</a>
4201 <li><a href="h_config_font_size">OPTION: Font Size</a>
4202 <li><a href="h_config_font_style">OPTION: Font Style</a>
4203 <li><a href="h_config_form_folder">OPTION: <!--#echo var="VAR_form-letter-folder"--></a>
4204 <li><a href="h_config_glob_addrbook">OPTION: <!--#echo var="VAR_global-address-book"--></a>
4205 <li><a href="h_config_goto_default">OPTION: <!--#echo var="VAR_goto-default-rule"--></a>
4206 <li><a href="h_config_header_general_color">OPTION: Header General Color</a>
4207 <li><a href="h_config_image_viewer">OPTION: <!--#echo var="VAR_image-viewer"--></a>
4208 <li><a href="h_config_inbox_path">OPTION: <!--#echo var="VAR_inbox-path"--></a>
4209 <li><a href="h_config_archived_folders">OPTION: <!--#echo var="VAR_incoming-archive-folders"--></a>
4210 <li><a href="h_config_psleep">OPTION: <!--#echo var="VAR_mailcap-check-interval"--></a>
4211 <li><a href="h_config_incoming_interv">OPTION: <!--#echo var="VAR_incoming-check-interval"--></a>
4212 <li><a href="h_config_incoming_second_interv">OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></a>
4213 <li><a href="h_config_incoming_list">OPTION: <!--#echo var="VAR_incoming-check-list"--></a>
4214 <li><a href="h_config_incoming_timeo">OPTION: <!--#echo var="VAR_incoming-check-timeout"--></a>
4215 <li><a href="h_config_incoming_folders">OPTION: <!--#echo var="VAR_incoming-folders"--></a>
4216 <li><a href="h_config_inc_startup">OPTION: <!--#echo var="VAR_incoming-startup-rule"--></a>
4217 <li><a href="h_config_incunseen_color">OPTION: Incoming Unseen Color</a>
4218 <li><a href="h_config_index_arrow_color">OPTION: Index Arrow Color</a>
4219 <li><a href="h_config_index_color">OPTION: Index Colors</a>
4220 <li><a href="h_config_index_format">OPTION: <!--#echo var="VAR_index-format"--></a>
4221 <li><a href="h_config_index_from_color">OPTION: Index From Color</a>
4222 <li><a href="h_config_index_opening_color">OPTION: Index Opening Color</a>
4223 <li><a href="h_config_index_pri_color">OPTION: Index Priority Symbol Colors</a>
4224 <li><a href="h_config_index_subject_color">OPTION: Index Subject Color</a>
4225 <li><a href="h_config_init_cmd_list">OPTION: <!--#echo var="VAR_initial-keystroke-list"--></a>
4226 <li><a href="h_config_key_char_set">OPTION: Keyboard Character Set</a>
4227 <li><a href="h_config_keylabel_color">OPTION: KeyLabel Color</a>
4228 <li><a href="h_config_keyname_color">OPTION: KeyName Color</a>
4229 <li><a href="h_config_keywords">OPTION: <!--#echo var="VAR_keywords"--></a>
4230 <li><a href="h_config_kw_color">OPTION: Keyword Colors</a>
4231 <li><a href="h_config_kw_braces">OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></a>
4232 <li><a href="h_config_prune_date">OPTION: <!--#echo var="VAR_last-time-prune-questioned"--></a>
4233 <li><a href="h_config_last_vers">OPTION: <!--#echo var="VAR_last-version-used"--></a>
4234 <li><a href="h_config_literal_sig">OPTION: <!--#echo var="VAR_literal-signature"--></a>
4235 <li><a href="h_config_mailcheck">OPTION: <!--#echo var="VAR_mail-check-interval"--></a>
4236 <li><a href="h_config_mailchecknoncurr">OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></a>
4237 <li><a href="h_config_mailcap_path">OPTION: <!--#echo var="VAR_mailcap-search-path"--></a>
4238 <li><a href="h_config_maildropcheck">OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></a>
4239 <li><a href="h_config_maxremstream">OPTION: <!--#echo var="VAR_max-remote-connections"--></a>
4240 <li><a href="h_config_metamsg_color">OPTION: Meta-Message Color</a>
4241 <li><a href="h_config_mimetype_path">OPTION: <!--#echo var="VAR_mimetype-search-path"--></a>
4242 <li><a href="h_config_new_ver_quell">OPTION: <!--#echo var="VAR_new-version-threshold"--></a>
4243 <li><a href="h_config_fifopath">OPTION: NewMail FIFO Path</a>
4244 <li><a href="h_config_newmailwidth">OPTION: <!--#echo var="VAR_newmail-window-width"--></a>
4245 <li><a href="h_config_news_active">OPTION: <!--#echo var="VAR_news-active-file-path"--></a>
4246 <li><a href="h_config_news_spec">OPTION: <!--#echo var="VAR_news-collections"--></a>
4247 <li><a href="h_config_news_spool">OPTION: <!--#echo var="VAR_news-spool-directory"--></a>
4248 <li><a href="h_config_newsrc_path">OPTION: <!--#echo var="VAR_newsrc-path"--></a>
4249 <li><a href="h_config_nntprange">OPTION: <!--#echo var="VAR_nntp-range"--></a>
4250 <li><a href="h_config_nntp_server">OPTION: <!--#echo var="VAR_nntp-server"--></HEAD></a>
4251 <li><a href="h_config_normal_color">OPTION: Normal Color</a>
4252 <li><a href="h_config_opening_sep">OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></a>
4253 <li><a href="h_config_oper_dir">OPTION: <!--#echo var="VAR_operating-dir"--></a>
4254 <li><a href="h_config_pat_old">OPTION: Patterns</a>
4255 <li><a href="h_config_pat_filts">OPTION: <!--#echo var="VAR_patterns-filters2"--></a>
4256 <li><a href="h_config_pat_other">OPTION: <!--#echo var="VAR_patterns-other"--></a>
4257 <li><a href="h_config_pat_roles">OPTION: <!--#echo var="VAR_patterns-roles"--></a>
4258 <li><a href="h_config_pat_scores">OPTION: <!--#echo var="VAR_patterns-scores2"--></a>
4259 <li><a href="h_config_pers_name">OPTION: <!--#echo var="VAR_personal-name"--></a>
4260 <li><a href="h_config_print_cat">OPTION: <!--#echo var="VAR_personal-print-category"--></a>
4261 <li><a href="h_config_print_command">OPTION: <!--#echo var="VAR_personal-print-command"--></a>
4262 <li><a href="h_config_post_char_set">OPTION: <!--#echo var="VAR_posting-character-set"--></a>
4263 <li><a href="h_config_postponed_folder">OPTION: <!--#echo var="VAR_postponed-folder"--></a>
4264 <li><a href="h_config_print_font_char_set">OPTION: Print-Font-Char-Set</a>
4265 <li><a href="h_config_print_font_name">OPTION: Print-Font-Name</a>
4266 <li><a href="h_config_print_font_size">OPTION: Print-Font-Size</a>
4267 <li><a href="h_config_print_font_style">OPTION: Print-Font-Style</a>
4268 <li><a href="h_config_printer">OPTION: Printer</a>
4269 <li><a href="h_config_prompt_color">OPTION: Prompt Color</a>
4270 <li><a href="h_config_pruned_folders">OPTION: <!--#echo var="VAR_pruned-folders"--></a>
4271 <li><a href="h_config_pruning_rule">OPTION: <!--#echo var="VAR_pruning-rule"--></a>
4272 <li><a href="h_config_quote_color">OPTION: Quote Colors</a>
4273 <li><a href="h_config_quote_replace_string">OPTION: <!--#echo var="VAR_quote-replace-string"--></a>
4274 <li><a href="h_config_quote_suppression">OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></a>
4275 <li><a href="h_config_read_message_folder">OPTION: <!--#echo var="VAR_read-message-folder"--></a>
4276 <li><a href="h_config_remote_abook_history">OPTION: <!--#echo var="VAR_remote-abook-history"--></a>
4277 <li><a href="h_config_abook_metafile">OPTION: <!--#echo var="VAR_remote-abook-metafile"--></a>
4278 <li><a href="h_config_remote_abook_validity">OPTION: <!--#echo var="VAR_remote-abook-validity"--></a>
4279 <li><a href="h_config_reply_indent_string">OPTION: <!--#echo var="VAR_reply-indent-string"--></a>
4280 <li><a href="h_config_reply_intro">OPTION: <!--#echo var="VAR_reply-leadin"--></a>
4281 <li><a href="h_config_reverse_color">OPTION: Reverse Color</a>
4282 <li><a href="h_config_rshcmd">OPTION: <!--#echo var="VAR_rsh-command"--></a>
4283 <li><a href="h_config_rsh_open_timeo">OPTION: <!--#echo var="VAR_rsh-open-timeout"--></a>
4284 <li><a href="h_config_rshpath">OPTION: <!--#echo var="VAR_rsh-path"--></a>
4285 <li><a href="h_config_saved_msg_name_rule">OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></a>
4286 <li><a href="h_config_scroll_margin">OPTION: <!--#echo var="VAR_scroll-margin"--></a>
4287 <li><a href="h_config_slctbl_color">OPTION: Selectable Item Color</a>
4288 <li><a href="h_config_sending_filter">OPTION: <!--#echo var="VAR_sending-filters"--></a>
4289 <li><a href="h_config_sendmail_path">OPTION: <!--#echo var="VAR_sendmail-path"--></a>
4290 <li><a href="h_config_signature_color">OPTION: Signature Color</a>
4291 <li><a href="h_config_signature_file">OPTION: <!--#echo var="VAR_signature-file"--></a>
4292 <li><a href="h_config_smtp_server">OPTION: <!--#echo var="VAR_smtp-server"--></a>
4293 <li><a href="h_config_sort_key">OPTION: <!--#echo var="VAR_sort-key"--></a>
4294 <li><a href="h_config_speller">OPTION: <!--#echo var="VAR_speller"--></a>
4295 <li><a href="h_config_aspell_dictionary">OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></a>
4296 <li><a href="h_config_sshcmd">OPTION: <!--#echo var="VAR_ssh-command"--></a>
4297 <li><a href="h_config_ssh_open_timeo">OPTION: <!--#echo var="VAR_ssh-open-timeout"--></a>
4298 <li><a href="h_config_sshpath">OPTION: <!--#echo var="VAR_ssh-path"--></a>
4299 <li><a href="h_config_status_color">OPTION: Status Color</a>
4300 <li><a href="h_config_status_msg_delay">OPTION: <!--#echo var="VAR_status-message-delay"--></a>
4301 <li><a href="h_config_permlocked">OPTION: <!--#echo var="VAR_stay-open-folders"--></a>
4302 <li><a href="h_config_tcp_open_timeo">OPTION: <!--#echo var="VAR_tcp-open-timeout"--></a>
4303 <li><a href="h_config_tcp_query_timeo">OPTION: <!--#echo var="VAR_tcp-query-timeout"--></a>
4304 <li><a href="h_config_tcp_readwarn_timeo">OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></a>
4305 <li><a href="h_config_tcp_writewarn_timeo">OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></a>
4306 <li><a href="h_config_thread_disp_style">OPTION: <!--#echo var="VAR_threading-display-style"--></a>
4307 <li><a href="h_config_thread_exp_char">OPTION: <!--#echo var="VAR_threading-expanded-character"--></a>
4308 <li><a href="h_config_thread_index_style">OPTION: <!--#echo var="VAR_threading-index-style"--></a>
4309 <li><a href="h_config_thread_indicator_char">OPTION: <!--#echo var="VAR_threading-indicator-character"--></a>
4310 <li><a href="h_config_thread_lastreply_char">OPTION: <!--#echo var="VAR_threading-lastreply-character"--></a>
4311 <li><a href="h_config_title_color">OPTION: Title Color</a>
4312 <li><a href="h_config_titleclosed_color">OPTION: Title Closed Color</a>
4313 <li><a href="h_config_titlebar_color_style">OPTION: <!--#echo var="VAR_titlebar-color-style"--></a>
4314 <li><a href="h_config_unk_char_set">OPTION: <!--#echo var="VAR_unknown-character-set"--></a>
4315 <li><a href="h_config_upload_cmd">OPTION: <!--#echo var="VAR_upload-command"--></a>
4316 <li><a href="h_config_upload_prefix">OPTION: <!--#echo var="VAR_upload-command-prefix"--></a>
4317 <li><a href="h_config_browser">OPTION: <!--#echo var="VAR_url-viewers"--></a>
4318 <li><a href="h_config_history">OPTION: <!--#echo var="VAR_default-directories"--></a>
4319 <li><a href="h_config_domain_name">OPTION: <!--#echo var="VAR_use-only-domain-name"--></a>
4320 <li><a href="h_config_user_dom">OPTION: <!--#echo var="VAR_user-domain"--></a>
4321 <li><a href="h_config_user_id">OPTION: <!--#echo var="VAR_user-id"--></a>
4322 <li><a href="h_config_user_input_timeo">OPTION: <!--#echo var="VAR_user-input-timeout"--></a>
4323 <li><a href="h_config_viewer_headers">OPTION: <!--#echo var="VAR_viewer-hdrs"--></a>
4324 <li><a href="h_config_customhdr_pattern">OPTION: Viewer Header Color Pattern</a>
4325 <li><a href="h_config_customhdr_color">OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></a>
4326 <li><a href="h_config_viewer_margin_left">OPTION: <!--#echo var="VAR_viewer-margin-left"--></a>
4327 <li><a href="h_config_viewer_margin_right">OPTION: <!--#echo var="VAR_viewer-margin-right"--></a>
4328 <li><a href="h_config_viewer_overlap">OPTION: <!--#echo var="VAR_viewer-overlap"--></a>
4329 <li><a href="h_config_window_position">OPTION: Window-Position</a>
4330 <li><a href="h_mainhelp_patterns">Patterns</a>
4331 <li><a href="h_config_role_abookfrom">PATTERNS: Address in Address Book</a>
4332 <li><a href="h_config_role_age">PATTERNS: Age Interval</a>
4333 <li><a href="h_config_role_alltextpat">PATTERNS: AllText Pattern</a>
4334 <li><a href="h_config_role_bom">PATTERNS: Beginning of Month</a>
4335 <li><a href="h_config_role_boy">PATTERNS: Beginning of Year</a>
4336 <li><a href="h_config_role_bodytextpat">PATTERNS: BodyText Pattern</a>
4337 <li><a href="h_config_role_cat_cmd">PATTERNS: Categorizer Command</a>
4338 <li><a href="h_config_role_cat_cmd_example">PATTERNS: Categorizer Command Example</a>
4339 <li><a href="h_config_role_ccpat">PATTERNS: Cc Pattern</a>
4340 <li><a href="h_config_role_cat_limit">PATTERNS: Character Limit</a>
4341 <li><a href="h_config_role_charsetpat">PATTERNS: Character Set Pattern</a>
4342 <li><a href="h_config_role_comment">PATTERNS: Comment</a>
4343 <li><a href="h_config_role_fldr_type">PATTERNS: Current Folder Type</a>
4344 <li><a href="h_config_role_cat_status">PATTERNS: Exit Status Interval</a>
4345 <li><a href="h_config_role_arbpat">PATTERNS: Extra Headers Pattern</a>
4346 <li><a href="h_config_role_frompat">PATTERNS: From Pattern</a>
4347 <li><a href="h_config_role_keywordpat">PATTERNS: Keyword Pattern</a>
4348 <li><a href="h_config_role_stat_ans">PATTERNS: Message Answered Status</a>
4349 <li><a href="h_config_role_stat_del">PATTERNS: Message Deleted Status</a>
4350 <li><a href="h_config_role_stat_imp">PATTERNS: Message Important Status</a>
4351 <li><a href="h_config_role_stat_new">PATTERNS: Message New Status</a>
4352 <li><a href="h_config_role_stat_recent">PATTERNS: Message Recent Status</a>
4353 <li><a href="h_config_role_newspat">PATTERNS: News Pattern</a>
4354 <li><a href="h_config_role_nick">PATTERNS: Nickname</a>
4355 <li><a href="h_config_role_particpat">PATTERNS: Participant Pattern</a>
4356 <li><a href="h_config_role_stat_8bitsubj">PATTERNS: Raw 8-bit in Subject</a>
4357 <li><a href="h_config_role_recippat">PATTERNS: Recipient Pattern</a>
4358 <li><a href="h_config_role_scorei">PATTERNS: Score Interval</a>
4359 <li><a href="h_config_role_senderpat">PATTERNS: Sender Pattern</a>
4360 <li><a href="h_config_role_size">PATTERNS: Size Interval</a>
4361 <li><a href="h_config_role_subjpat">PATTERNS: Subject Pattern</a>
4362 <li><a href="h_config_role_topat">PATTERNS: To Pattern</a>
4363 <li><a href="h_config_filt_opts_nonterm">PATTERNS FEATURE: Dont-Stop-Even-if-Rule-Matches</a>
4364 <li><a href="h_config_filt_opts_notdel">PATTERNS FEATURE: Move-Only-if-Not-Deleted</a>
4365 <li><a href="h_config_filt_opts_sentdate">PATTERNS FEATURE: Use-Date-Header-For-Age</a>
4366 <li><a href="h_config_filt_rule_type">PATTERNS FILTER ACTION: Filter Action</a>
4367 <li><a href="h_config_filter_kw_clr">PATTERNS FILTER ACTION: Clear These Keywords</a>
4368 <li><a href="h_config_filt_stat_ans">PATTERNS FILTER ACTION: Set Answered Status</a>
4369 <li><a href="h_config_filt_stat_del">PATTERNS FILTER ACTION: Set Deleted Status</a>
4370 <li><a href="h_config_filt_stat_imp">PATTERNS FILTER ACTION: Set Important Status</a>
4371 <li><a href="h_config_filt_stat_new">PATTERNS FILTER ACTION: Set New Status</a>
4372 <li><a href="h_config_filter_kw_set">PATTERNS FILTER ACTION: Set These Keywords</a>
4373 <li><a href="h_config_incol">PATTERNS INDEXCOLOR ACTION: Index Line Color</a>
4374 <li><a href="h_config_set_index_format">PATTERNS OTHER ACTION: Set Index Format</a>
4375 <li><a href="h_config_perfolder_sort">PATTERNS OTHER ACTION: Set Sort Order</a>
4376 <li><a href="h_config_other_startup">PATTERNS OTHER ACTION: Set Startup Rule</a>
4377 <li><a href="h_config_role_inick">PATTERNS ROLE ACTION: Initialize Values From Role</a>
4378 <li><a href="h_config_role_setfcc">PATTERNS ROLE ACTION: Set Fcc</a>
4379 <li><a href="h_config_role_setfrom">PATTERNS ROLE ACTION: Set From</a>
4380 <li><a href="h_config_role_setlitsig">PATTERNS ROLE ACTION: Set Literal Signature</a>
4381 <li><a href="h_config_role_setotherhdr">PATTERNS ROLE ACTION: Set Other Headers</a>
4382 <li><a href="h_config_role_setreplyto">PATTERNS ROLE ACTION: Set Reply-To</a>
4383 <li><a href="h_config_role_setsig">PATTERNS ROLE ACTION: Set Signature</a>
4384 <li><a href="h_config_role_settempl">PATTERNS ROLE ACTION: Set Template</a>
4385 <li><a href="h_config_role_usenntp">PATTERNS ROLE ACTION: Use NNTP Server</a>
4386 <li><a href="h_config_role_usesmtp">PATTERNS ROLE ACTION: Use SMTP Server</a>
4387 <li><a href="h_config_role_scoreval">PATTERNS SCORE ACTION: Score Value</a>
4388 <li><a href="h_config_role_scorehdrtok">PATTERNS SCORE ACTION: Score Value From Header</a>
4389 <li><a href="h_config_role_composeuse">PATTERNS USE: Compose Use</a>
4390 <li><a href="h_config_role_forwarduse">PATTERNS USE: Forward Use</a>
4391 <li><a href="h_config_role_replyuse">PATTERNS USE: Reply Use</a>
4392 <li><a href="h_pipe_command">Pipe Command SubOptions</a>
4393 <li><a href="h_common_pipe">Pipe Command</a>
4394 <li><a href="h_valid_folder_names">POP</a>
4395 <li><a href="h_common_postpone">Postpone Command</a>
4396 <li><a href="h_common_print">Print Command</a>
4397 <li><a href="h_mainhelp_readingnews">Reading News</a>
4398 <li><a href="h_news">RELEASE NOTES for Alpine</a>
4399 <li><a href="h_mainhelp_roles">Roles</a>
4400 <li><a href="h_role_select">ROLES SCREEN</a>
4401 <li><a href="h_compose_readfile">Read File Command</a>
4402 <li><a href="h_mainhelp_reading">Reading Messages</a>
4403 <li><a href="h_main_release_notes">Release Notes Command</a>
4404 <li><a href="h_common_reply">Reply and Forward Commands</a>
4405 <li><a href="h_compose_richhdr">Rich Header Command</a>
4406 <li><a href="h_common_role">Role Command</a>
4407 <li><a href="h_mainhelp_smime">S/MIME</a>
4408 <li><a href="h_index_cmd_select">Searching for Messages</a>
4409 <li><a href="h_address_display">SEARCH RESULTS INDEX</a>
4410 <li><a href="h_address_select">SEARCH RESULTS INDEX</a>
4411 <li><a href="h_simple_index">SELECT POSTPONED MESSAGE</a>
4412 <li><a href="h_abook_config">SETUP ADDRESS BOOKS SCREEN</a>
4413 <li><a href="h_collection_maint">SETUP COLLECTION LIST screen</a>
4414 <li><a href="h_color_setup">SETUP COLOR COMMANDS</a>
4415 <li><a href="h_direct_config">SETUP LDAP DIRECTORY SERVERS SCREEN</a>
4416 <li><a href="h_rules_roles">SETUP ROLES SCREEN</a>
4417 <li><a href="h_rules_incols">SETUP INDEX COLORS SCREEN</a>
4418 <li><a href="h_rules_filter">SETUP FILTERING SCREEN</a>
4419 <li><a href="h_rules_score">SETUP SCORING SCREEN</a>
4420 <li><a href="h_common_save">Save and Export Commands</a>
4421 <li><a href="h_mainhelp_securing">Securing Your Alpine Session</a>
4422 <li><a href="h_index_cmd_select">Selecting: Select and WhereIs/Select</a>
4423 <li><a href="h_compose_send">Send Command</a>
4424 <li><a href="h_folder_server_syntax">Server Name Syntax</a>
4425 <li><a href="h_main_setup">Setup Command</a>
4426 <li><a href="X-Alpine-Config:">Show Supported Options in this Alpine</a>
4427 <li><a href="h_composer_sigedit">Signature Editor Commands Explained</a>
4428 <li><a href="h_simple_text_view">Simple Text View Screen Explained</a>
4429 <li><a href="h_mainhelp_smime">S/MIME</a>
4430 <li><a href="h_config_smime_dont_do_smime">S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></a>
4431 <li><a href="h_config_smime_encrypt_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></a>
4432 <li><a href="h_config_smime_remember_passphrase">S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></a>
4433 <li><a href="h_config_smime_sign_by_default">S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></a>
4434 <li><a href="h_config_smime_use_cert_store">S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></a>
4435 <li><a href="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></a>
4436 <li><a href="h_config_smime_cacertcon">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></a>
4437 <li><a href="h_config_smime_cacertdir">S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></a>
4438 <li><a href="h_config_smime_privkeycon">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-container"--></a>
4439 <li><a href="h_config_smime_privkeydir">S/MIME OPTION: <!--#echo var="VAR_smime-private-key-directory"--></a>
4440 <li><a href="h_config_smime_pubcertcon">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-container"--></a>
4441 <li><a href="h_config_smime_pubcertdir">S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></a>
4442 <li><a href="h_config_smime_transfer_cacert_to_con">S/MIME: Transfer CA Certs to Container</a>
4443 <li><a href="h_config_smime_transfer_cacert_to_dir">S/MIME: Transfer CA Certs to Directory</a>
4444 <li><a href="h_config_smime_transfer_priv_to_con">S/MIME: Transfer Private Keys to Container</a>
4445 <li><a href="h_config_smime_transfer_priv_to_dir">S/MIME: Transfer Private Keys to Directory</a>
4446 <li><a href="h_config_smime_transfer_pub_to_con">S/MIME: Transfer Public Certs to Container</a>
4447 <li><a href="h_config_smime_transfer_pub_to_dir">S/MIME: Transfer Public Certs to Directory</a>
4448 <li><a href="h_config_smime_public_certificates">S/MIME: Manage Public Certificates</a>
4449 <li><a href="h_config_smime_private_keys">S/MIME: Manage Private Keys</a>
4450 <li><a href="h_config_smime_certificate_authorities">S/MIME: Manage Certificate Authorities</a>
4451 <li><a href="h_index_cmd_sort">Sort Command</a>
4452 <li><a href="h_compose_spell">Spell Check Command</a>
4453 <li><a href="h_common_suspend">Suspend Command</a>
4454 <li><a href="h_compose_addrcomplete">THE MESSAGE COMPOSER'S ADDRESS COMPLETION</a>
4455 <li><a href="h_composer_attachment">THE MESSAGE COMPOSER'S ATTCHMNT FIELD</a>
4456 <li><a href="h_composer_bcc">THE MESSAGE COMPOSER'S BCC FIELD</a>
4457 <li><a href="h_composer_cc">THE MESSAGE COMPOSER'S CC FIELD</a>
4458 <li><a href="h_composer_from">THE MESSAGE COMPOSER'S FROM FIELD</a>
4459 <li><a href="h_composer_lcc">THE MESSAGE COMPOSER'S LCC FIELD</a>
4460 <li><a href="h_composer_news">THE MESSAGE COMPOSER'S NEWSGRPS LINE</a>
4461 <li><a href="h_composer_reply_to">THE MESSAGE COMPOSER'S REPLY-TO FIELD</a>
4462 <li><a href="h_composer_to">THE MESSAGE COMPOSER'S TO FIELD</a>
4463 <li><a href="h_abook_opened">THE ALPINE ADDRESS BOOK</a>
4464 <li><a href="h_abook_select_nicks_take">Take Address Nickname Selection Explained</a>
4465 <li><a href="h_takeaddr_screen">Take Address Screen Explained</a>
4466 <li><a href="h_common_take">TakeAddr Command</a>
4467 <li><a href="h_mainhelp_status">Titlebar Line</a>
4468 <li><a href="h_index_tokens">Tokens for Index and Replying</a>
4469 <li><a href="h_config_usenone_color">Use None Color</a>
4470 <li><a href="h_config_usenormal_color">Use Normal Color</a>
4471 <li><a href="h_config_usetransparent_color">Use Transparent Color</a>
4472 <li><a href="h_whatis_vcard">VCARD EXPLAINED</a>
4473 <li><a href="h_view_cmd_hilite">View Hilite and Next item/Previous item</a>
4474 <li><a href="h_view_cmd_viewattch">ViewAttch Command</a>
4475 <li><a href="h_index_cmd_whereis">WhereIs Command</a>
4476 <li><a href="h_view_cmd_whereis">WhereIs Command</a>
4477 <li><a href="h_index_cmd_zoom">ZoomMode Command</a>
4478 <li><a href="h_config_browser_xterm"><!--#echo var="VAR_url-viewers"--> and X windows applications</a>
4482 <End of Help Index>
4487 ============== h_config_remote_config =============
4490 <TITLE>Remote Configuration</TITLE>
4493 <H1>Remote Configuration</H1>
4495 You may use the command line argument "-p pinerc" to tell
4496 Alpine to use a non-default configuration file.
4497 There are two types of storage for configuration information.
4498 <EM>Local</EM> configuration files are used by default.
4499 These are just regular files on the UNIX system or on the PC.
4500 The file "<CODE>.pinerc</CODE>" is the default for Unix Alpine and the
4501 file "<CODE>PINERC</CODE>" is the default for PC-Alpine.
4502 <EM>Remote</EM> configuration folders are stored on an IMAP server.
4503 The advantage of using a remote configuration is that the same information
4504 may be accessed from multiple platforms.
4505 For example, if you use one computer at work and another at home, the same
4506 configuration could be used from both places.
4507 A configuration change from one place would be seen in both places.
4508 To use a remote configuration you simply give a
4509 <A HREF="h_valid_folder_names">remote folder name</A>
4510 as the argument to the "-p" command line option.
4511 The command line might look something like:
4513 <CENTER><SAMP>pine -p {my.imap.server}remote_pinerc</SAMP></CENTER>
4515 If there are special characters in the command shell you use, you may need to
4516 quote the last argument (to protect the curly braces from the shell).
4517 The command might look like:
4519 <CENTER><SAMP>pine -p "{my.imap.server}remote_pinerc"</SAMP></CENTER>
4521 You should choose a folder name for a folder that does not yet exist.
4522 It will be created containing an empty configuration.
4523 Do not use a folder that you wish to store regular mail messages in.
4525 The Setup/RemoteConfigSetup command will help you convert from a local
4526 configuration to a remote configuration.
4527 It will create a remote configuration for you and copy your current local
4528 configuration to it.
4529 It will also help you convert local address books into remote address books
4530 and local signature files into literal signatures contained in the
4531 remote configuration file.
4533 If the Setup/RemoteConfigSetup command doesn't do what you want, you
4534 may copy a local pinerc file to a remote configuration folder by hand
4535 by using the command line option "-copy_pinerc".
4537 Another command line option, which is somewhat related to remote
4538 configuration, is the option "-x exceptions_config".
4539 The configuration settings in the exceptions configuration override
4540 your default settings.
4541 It may be useful to store the default configuration (the -p argument) remotely
4542 and to have the exceptions configuration stored in a local file.
4543 You might put generic configuration information in the remote configuration
4544 and platform-specific configuration on each platform in the exceptions
4546 The arguments to the "-p" and "-x" options
4547 can be either remote folders or local files.
4549 There is another command line argument that works only with PC-Alpine and
4550 which may prove useful when using a remote configuration.
4551 The option "-aux local_directory" allows you to tell PC-Alpine where
4552 to store your local auxiliary files.
4553 This only has an effect if your configuration file is remote.
4554 Some examples of auxiliary files are debug files, address book files, and
4557 <End of help on this topic>
4560 ============== h_config_exceptions =============
4563 <TITLE>Generic and Exceptional Configuration</TITLE>
4566 <H1>Generic and Exceptional Configuration</H1>
4568 If you use Alpine from more than one platform it may be convenient
4569 to split your configuration information into two pieces, a generic piece
4570 and exceptions that apply to a particular platform.
4571 For example, suppose you use Alpine from home and from work.
4572 Most of your configuration settings are probably the
4573 same in both locations, so those settings belong in the generic settings
4575 However, you may use a different SMTP server and INBOX
4576 from home than you do from work.
4578 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
4580 <A HREF="h_config_inbox_path">"<!--#echo var="VAR_inbox-path"-->"</A>
4582 part of your exceptional configuration so that they could be different in the
4585 The command line option "-x exceptions_config"
4586 may be used to split your configuration into generic and exceptional pieces.
4587 "Exceptions_config" may be either local or remote.
4588 The regular Alpine configuration file will contain the generic data, and
4589 "exceptions_config" will contain the exceptional data.
4591 For Unix Alpine, if you don't have a "-x" command line option,
4592 Alpine will look for the file "<CODE>.pinercex</CODE>"
4593 in the same local directory that the regular config file is located in (usually
4594 the Unix home directory).
4595 If the regular config file is remote (because the command line option
4596 "-p remote_config" was used) then Unix Alpine looks in the Unix home
4597 directory for "<CODE>.pinercex</CODE>".
4598 If the file does not already exist then no exceptions will be used.
4599 You can force exceptions to be used by using the "-x" option or
4600 by creating an empty "<CODE>.pinercex</CODE>" file.
4602 For PC-Alpine, if you don't have a "-x" command line option,
4603 PC-Alpine will use the value of the
4604 environment variable <CODE>$PINERCEX</CODE>.
4605 If that is not set, PC-Alpine will look for
4606 the local file "<CODE>PINERCEX</CODE>"
4607 in the same local directory that the regular config file is located in.
4608 If the regular config file is remote (because the command line option
4609 "-p remote_config" was used) then PC-Alpine looks in the
4610 local directory specified by the "-aux local_directory" command
4611 line argument, or the directory <CODE>$HOME\PINE</CODE>, or
4612 in the <CODE><PINE.EXE </CODE>directory<CODE>></CODE>.
4614 When you have an exception configuration there is a new command
4615 in the Alpine Setup screen, Setup/eXceptions.
4616 It toggles between exceptions and the regular configuration.
4617 This is the usual way to make changes in your exceptional configuration data.
4618 For example, you would type "S" for Setup, "X" for
4619 eXception, then follow that with one of the Setup commands, like "C"
4620 for Config or "K" for Kolor.
4622 For most people, splitting the configuration information into two pieces is
4623 going to be most useful if the generic information is accessed
4624 <A HREF="h_config_remote_config">remotely</A>).
4625 That data will be the same no matter where you access it from and if you
4626 change it that change will show up everywhere.
4627 The exceptional data will most commonly be in a local file, so that the
4628 contents may easily be different on each computing platform used.
4630 If you already have a local configuration file with settings you like
4631 you may find that the command Setup/RemoteConfigSetup is useful
4632 in helping you convert to a remote configuration.
4633 The command line flag "-copy_pinerc"
4636 <End of help on this topic>
4639 ============== h_config_inheritance =============
4642 <TITLE>Configuration Inheritance</TITLE>
4645 <H1>Configuration Inheritance</H1>
4647 Configuration inheritance is a power user feature.
4648 It is confusing and not completely supported by the configuration
4650 We start with an explanation of how configuration works in hopes of making
4651 it easier to describe how inheritance works.
4653 Alpine uses a hierarchy of configuration values from different locations.
4654 There are five ways in which each configuration option (configuration
4655 variable) can be set.
4656 In increasing order of precedence they are:
4659 <LI> the system-wide configuration file.
4661 <LI> the personal configuration file
4663 <LI> the personal exceptions file
4665 <LI> a command line argument
4667 <LI> the system-wide <EM>fixed</EM> configuration file (Unix Alpine only)
4670 The fixed configuration file is normally
4671 <CODE><!--#echo var="PINE_CONF_FIXED_PATH"--></CODE>.
4673 The system-wide configuration file is normally
4674 <CODE><!--#echo var="PINE_CONF_PATH"--></CODE> for Unix Alpine and is normally not
4676 For PC-Alpine, if the environment variable <EM>$PINECONF</EM> is set, that
4677 is used for the system-wide configuration.
4678 This location can be set or changed on the command line with the -P flag.
4679 The system-wide configuration file can be either a local file or a
4680 remote configuration folder.
4682 For Unix Alpine, the personal configuration file is normally the file
4683 <CODE>.pinerc</CODE> in the user's home directory.
4684 This can be changed with the -p command line flag.
4685 For PC-Alpine, the personal configuration file is in
4686 <CODE>$PINERC</CODE> or <CODE><AlpineRC registry value></CODE> or
4687 <CODE>$HOME\PINE\PINERC</CODE> or
4688 <CODE><PINE.EXE </CODE>dir<CODE>>\PINERC</CODE>.
4689 This can be changed with the -p command line flag.
4690 If -p is used, the configuration data may be in a local file or a remote config
4693 For Unix Alpine, the personal exceptions configuration file is named
4694 <CODE>.pinercex</CODE> and is in the same directory as the personal
4695 configuration file, if that configuration file is not remote, and is in
4696 the home directory if the personal configuration file is remote.
4697 If the file exists, then exceptions are turned on.
4698 If it doesn't, then you are not using exceptions.
4699 Alternatively, you may change the location of the exceptions configuration
4700 by using the command line argument "-x <exceptions_config>".
4701 Like the personal configuration data, exceptions_config may be
4702 either local or remote.
4704 For PC-Alpine, the personal exceptions configuration file is named
4705 <CODE>PINERCEX</CODE> and is in the same directory as the personal
4706 configuration file unless the personal configuration file is remote.
4707 In that case, it is in the local directory specfied by the
4708 "-aux local_directory" command line argument.
4709 (In the case that the personal configuration is remote and there is no
4710 "-aux" command line argument, Alpine searches for
4711 a PINERCEX file in the directory <CODE>$HOME\PINE</CODE> and
4712 the directory <CODE><PINE.EXE </CODE>dir<CODE>></CODE>.)
4713 If the file exists, then exceptions are turned on.
4714 If it doesn't, then you are not using exceptions.
4715 You may change the location of the exceptions configuration
4716 by using the command line argument "-x <exceptions_config>".
4718 environment variable <CODE>$PINERCEX</CODE> (if there is no "-x"
4721 To reiterate, the value of a configuration option is taken from the
4722 last location in the list above in which it is set.
4723 Or, thinking about it slightly differently, a default value for an option
4724 is established in the system-wide configuration file (or internally by Alpine
4725 if there is no value in the system-wide file).
4726 That default remains in effect until and unless it is overridden by a value in a
4727 location further down the list, in which case a new "default"
4728 value is established.
4729 As we continue down the list of locations we either retain the
4730 value at each step or establish a new value.
4731 The value that is still set after going through the whole list of
4732 configuration locations is the one that is used.
4734 So, for example, if an option is set in the system-wide configuration
4735 file and in the personal configuration file, but is not set in the
4736 exceptions, on the command line, or in the fixed file; then the value
4737 from the personal configuration file is the one that is used.
4738 Or, if it is set in the system-wide config, in the personal config, not
4739 in the exceptions, but is set on the command line; then the value
4740 on the command line is used.
4742 Finally we get to inheritance.
4743 For configuration options that are lists, like "<!--#echo var="VAR_smtp-server"-->" or
4744 "<!--#echo var="VAR_incoming-folders"-->",
4745 the inheritance mechanism makes it possible to <EM>combine</EM>
4746 the values from different locations instead of <EM>replacing</EM> the value.
4747 This is true of all configuration lists other than the "Feature-List",
4748 for which you may already set whatever you want at
4749 any configuration location (by using the "no-" prefix if
4752 To use inheritance, set the first item in a configuration list to the
4753 token "INHERIT", without the quotes.
4754 If the first item is "INHERIT",
4755 then instead of replacing the default value established so far, the rest of
4756 the list is appended to the default value established so far and that is
4759 Here is an example which may make it clearer. Suppose we have:
4762 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4763 Personal config : smtp-server = INHERIT, mysmtp.home
4764 Exceptions config : smtp-server = <No Value Set>
4765 Command line : smtp-server = <No Value Set>
4766 Fixed config : smtp-server = <No Value Set>
4770 This would result in an effective smtp-server option of
4773 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home
4776 The "INHERIT" token can be used in any of the configuration files
4777 and the effect cascades.
4778 For example, if we change the above example to:
4781 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4782 Personal config : smtp-server = INHERIT, mysmtp.home
4783 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4784 Command line : smtp-server = <No Value Set>
4785 Fixed config : smtp-server = <No Value Set>
4789 This would result in:
4792 smtp-server = smtp1.corp.com, smtp2.corp.com, mysmtp.home, yoursmtp.org
4795 Unset variables are skipped over (the default value is carried forward) so
4799 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4800 Personal config : smtp-server = <No Value Set>
4801 Exceptions config : smtp-server = INHERIT, yoursmtp.org
4802 Command line : smtp-server = <No Value Set>
4803 Fixed config : smtp-server = <No Value Set>
4810 smtp-server = smtp1.corp.com, smtp2.corp.com, yoursmtp.org
4814 If any later configuration location has a value set (for a particular list
4815 option) which does <EM>not</EM> begin with "INHERIT",
4816 then that value replaces whatever value has been defined up to that point.
4817 In other words, that cancels out any previous inheritance.
4820 System-wide config : smtp-server = smtp1.corp.com, smtp2.corp.com
4821 Personal config : smtp-server = INHERIT, mysmtp.org
4822 Exceptions config : smtp-server = yoursmtp.org
4823 Command line : smtp-server = <No Value Set>
4824 Fixed config : smtp-server = <No Value Set>
4831 smtp-server = yoursmtp.org
4835 For some configuration options, like "<!--#echo var="VAR_viewer-hdr-colors"-->" or
4836 "<!--#echo var="VAR_patterns-roles"-->", it is
4837 difficult to insert the value "INHERIT" into the list of values
4838 for the option using the normal Setup tools.
4839 In other words, the color setting screen (for example) does not
4840 provide a way to input the text "INHERIT" as the first
4841 item in the <!--#echo var="VAR_viewer-hdr-colors"--> option.
4842 The way to do this is to either edit the pinerc file directly and manually
4844 on the <A HREF="h_config_expose_hidden_config"><!--#echo var="FEAT_expose-hidden-config"--></A>
4845 feature and insert it using the Setup/Config screen.
4847 <End of help on this topic>
4850 ============== h_special_xon_xoff =============
4853 <TITLE>Explanation of Alpine's XOFF/XON Handling</TITLE>
4856 <H1>XOFF/XON Handling within Alpine</H1>
4858 By default, Alpine treats Ctrl-S or Ctrl-Q (sometimes known as XOFF
4859 and XON) as normal characters, even though Alpine does not use them.
4860 However, the printer, modem, or communication software you are using may
4861 be configured for "software flow control," which means that
4862 XON/XOFF must be treated as special characters by the operating system.
4863 If you see messages such as "^S not defined for this screen",
4864 then your system is probably using software flow control. In this case
4865 you will need to set the
4866 <A HREF="h_config_preserve_start_stop">"<!--#echo var="FEAT_preserve-start-stop-characters"-->"</A>
4869 If you <EM>do</EM> set this
4870 feature, be advised that if you accidentally hit a Ctrl-S, Alpine will
4871 mysteriously freeze up with no warning. In this case, try typing a Ctrl-Q
4872 and see if that puts things right. Printing via the
4873 "attached-to-ansi" or
4874 "attached-to-wyse"
4875 option will automatically enable software
4876 flow-control handling for the duration of the printing.
4878 <End of help on this topic>
4881 ============= h_special_help_nav =============
4884 <TITLE>Help Text Navigation Explained</TITLE>
4887 <H1>Help Text Navigation Explained</H1>
4889 Alpine contains extensive context-sensitive help text. At any point,
4890 pressing the "?" key will bring up a page of help text
4891 explaining the options available to you. You can leave the help
4892 text screen and return to normal Alpine operation by pressing
4894 <!--chtml if pinemode="function_key"-->
4899 key to Exit Help at any time.
4902 Within the help screen you might find a word or phrase displayed in
4903 inverse text and others displayed in bold typeface. Such words and
4904 phrases are used to tell you Alpine has more information available on
4905 the topic they describe.
4906 The inverted text is the "selected" topic.
4907 Use the arrow keys, Ctrl-F, and Ctrl-B to change which of the phrases
4908 displayed in bold type
4909 is "selected".
4910 Hit the Return key to display the information Alpine has available on that
4911 topic. While viewing such additional information, the
4912 <!--chtml if pinemode="function_key"-->
4917 key will return you to the previous help screen, and the
4918 <!--chtml if pinemode="function_key"-->
4923 key will Exit the Help system altogether.
4926 The "N" command will tell you the internal name of the help text you are
4927 reading each time, so that you can send this name in the text of a message
4928 and create a direct link to that internal help using the x-pine-help URL
4929 scheme. For example, the direct link to this item is
4930 x-pine-help:h_special_help_nav. If you add this text to a message, then
4931 a person using Pine to read such message would have a direct link to this
4935 When you are finished reading this help text, you can press the
4936 <!--chtml if pinemode="function_key"-->
4941 key to return to the previously displayed help text.
4944 <End of help on this topic>
4947 ============= h_special_list_commands =============
4950 <TITLE>Email List Commands Explained</TITLE>
4953 <H1>Email List Commands Explained</H1>
4955 Electonic mail lists provide a way for like-minded users to join in
4956 discussions on topics of interest. The email list itself is
4958 single address that participants send messages to when they have
4959 something of interest to share with other members of the list. The
4960 receiving computer then, either automatically or after review by the
4961 list's owner (or moderator), sends a copy of that message to each
4965 Usually, subscribing and unsubscribing is done by sending requests in
4966 an email message to a special address setup to handle managing list
4967 membership. Often this is the name of the list followed by
4968 <I>-request</I>. This address is almost <EM>never</EM> the same as
4969 the address used to send messages to the list.
4972 Unfortunately, email list participation commands are more a matter
4973 of convention than standard, and thus may vary from list to list.
4974 Increasingly, list management software is adding information to
4975 the copy of the postings as they're copied to the list members that
4976 explains how to do the various list management functions.
4979 Alpine will recognize this information and offer the management commands
4980 they represent in a simple display. One or more of the following
4981 operations will be made available:
4986 A method to get help on subscribing, unsubscribing,
4987 an explanation of what the list is about, or special instructions
4988 for participation. This may be in the form of a reply in response
4989 to an email message, or instructions on how to connect to a Web site.
4992 <DT>Unsubscribe</DT>
4994 A method to get your email addressed removed from the list of
4995 recipients of the email list.
5000 A method to get your email address added to the list of recipients
5001 of the email list. It may be in the form of a message sent to
5002 a special address or you may be connected to a web site.
5008 A method used to post to the email list. However, it might also
5009 indicate that no posting is allowed directly to the list.
5014 A method to contact the list owner for special questions you might
5015 have regarding the list.
5020 A method to view an archive of previous messages posted to the list.
5021 This may be in the form of a mail folder on a remote computer, an
5022 IMAP mailbox or even a Web site.
5027 <End of help on this topic>
5030 ============= h_quota_command =============
5033 <TITLE>Quota Screen Explained</TITLE>
5036 <H1>Quota Screen Explained</H1>
5038 <P> This screen summarizes the quota report for this mailbox in the
5039 IMAP server. For each resource that you have a quota, this reports summarizes
5042 <P> Your IMAP server administrator may have set a quota based either on
5043 the total size of your mailbox (STORAGE), or the number of messages in
5044 your mailbox (MESSAGES), or some other criteria. This will be reported
5045 to you indicating the type of quota, its total use and its limit.
5047 <P> The report for STORAGE is reported in kibibytes (KiB). One kibibyte is
5048 1024 bytes. Each of the characters that you see in this help text is one
5049 byte, and this help text is about 1 kibibyte in size. Small messages sent
5050 by Alpine are normally less than 4 kibibytes in size (which includes
5051 headers and text). Other email programs may send messages with bigger
5052 sizes when they send messages, since they send plain text and an
5053 alternative part in HTML.
5055 <P> A convenient way to save space for the STORAGE type of quota is by
5056 deleting attachments. This is done on each individual message by pressing
5057 the "V" command while reading the message text, then moving the cursor
5058 to the position of the attachment that is to be deleted, then pressing
5059 "D" to delete such attachment, going back to reading the
5060 message with the "<" command and pressing "S" to
5061 save the message in the same folder you are reading from. The saved
5062 message will not have the attachment that was marked deleted. Now you
5063 can delete and expunge the message with the unwanted attachment.
5066 <End of help on this topic>
5069 ============= h_mail_thread_index =============
5072 <TITLE>THREAD INDEX COMMANDS</TITLE>
5075 <H1>THREAD INDEX COMMANDS</H1>
5076 <!--chtml if pinemode="function_key"-->
5077 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5078 ------------------------------- -----------------------------<BR>
5079 F1 Show Help Text F1 Show Help Text<BR>
5080 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5081 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
5082 F4 View current thread F4 Quit Alpine<BR>
5083 F5 Move to previous thread F5 <A HREF="h_common_compose">Compose</A> a message<BR>
5084 F6 Move to next thread F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5085 F7 Show previous screen F7 <A HREF="h_common_nextnew">Next new</A> thread<BR>
5086 F8 Show next screen F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
5087 F9 <A HREF="h_common_delete">Mark thread for deletion</A> F9 <A HREF="h_common_print">Print</A> index<BR>
5088 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5089 F11 <A HREF="h_common_reply">Reply</A> to thread F11 <A HREF="h_common_save">Save</A> messages into an email folder<BR>
5090 F12 <A HREF="h_common_reply">Forward</A> messages F12 <A HREF="h_common_save">Export</A> messages into a plain file<BR>
5092 Available Commands -- Group 3<BR>
5093 -----------------------------<BR>
5094 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>
5095 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>
5096 F6 F9 <A HREF="h_common_hdrmode">Full Header Mode</A> F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5098 Available Commands -- Group 4<BR>
5099 -----------------------------<BR>
5100 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
5101 F6 <A HREF="h_common_role">Compose using a role</A><BR>
5104 Navigating the List of Threads Operations on the Current Thread<BR>
5105 ------------------------------- ---------------------------------<BR>
5106 P Move to the previous thread > View Thread % <A HREF="h_common_print">Print</A><BR>
5107 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>
5108 - Show previous screen D <A HREF="h_common_delete">Mark thread for deletion</A><BR>
5109 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
5110 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>
5111 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>
5112 specific thread E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5113 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>
5114 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5116 Miscellaneous Operations General Alpine Commands<BR>
5117 ------------------------ ---------------------<BR>
5118 G <A HREF="h_common_goto">Goto</A> a specified folder O Show all other available commands<BR>
5119 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ? Show Helptext Q Quit Alpine<BR>
5120 H <A HREF="h_common_hdrmode">Full header mode</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5121 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> C <A HREF="h_common_compose">Compose</A> a new message<BR>
5122 Z <A HREF="h_index_cmd_zoom">Zoom</A> # <A HREF="h_common_role">Compose using a role</A><BR>
5123 ; <A HREF="h_index_cmd_select">Select</A> A <A HREF="h_index_cmd_apply">Apply</A> L COLLECTION LIST Screen<BR>
5124 : Select Messages in Current Thread<BR>
5130 <LI>For help on a particular command, highlight the bold text associated
5131 with it above and hit Return.
5132 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5135 <H2>Description of the THREAD INDEX Screen</H2>
5137 The THREAD INDEX displays summary information from each
5138 thread (conversation) in the current folder.
5139 This is useful if you want to quickly
5140 scan new threads, or find a particular thread without having to go
5141 through the text of each message, or to quickly get rid of junk
5143 The current thread is always highlighted.
5144 Each line of the THREAD INDEX contains the following columns: <P>
5147 <DD> The markings on the left side of the thread tell you about its
5148 status. You may see one or more of the following codes on any given
5151 <LI> "D" for Deleted. All of the messages in this thread are marked for deletion but not yet eXpunged from the folder.
5152 <LI> "A" for Answered. All of the messages in this thread are marked answered.
5153 <LI> "N" for New. At least one message in the thread is New (you haven't looked at it yet).
5154 <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.
5155 <LI> "-" for cc-to-you. The "-" indicates that a
5156 message in the thread was sent to you as a cc:. This symbol will only show up if
5158 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5159 <LI> "X" for selected. You have selected at least one message in the thread by using the
5160 "select" command. (Some systems may optionally allow selected
5161 messages to be denoted by the index line being displayed in bold
5163 <LI> "*" for Important. You have previously used the "Flag" command
5164 to mark at least one message in this thread as "important".
5167 <DT>THREAD NUMBER:</DT>
5168 <DD>Threads in a folder are numbered, from one through the number
5169 of threads in the folder, to help you know where you are in the folder.
5172 <DT>DATE STARTED:</DT>
5173 <DD>The date the thread was started. This is actually from the Date header
5174 of the first message in the thread. It doesn't take different time zones
5175 into account.</DD><P>
5177 <DT>WHO STARTED THE THREAD:</DT>
5178 <DD>This is usually the name of the sender of the first message in the thread, taken from
5179 the From header of the message.
5180 If there is no personal name given in that
5181 address, then the email address is used instead.
5182 If the message is from you (or from one of your
5183 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5184 then the recipient's name is shown here instead, with the characters
5185 "To: " inserted before the name.
5186 (The idea of this is that if you started the thread you would rather see who
5187 the mail was sent to instead of that the mail was from you.)
5188 In Newsgroups, if you are
5189 the sender and there are no email recipients, the newsgroup name will be
5190 listed after the "To: ".
5194 <DD>The number in parentheses is the number of messages in the thread.</DD><P>
5197 <DD>As much of the thread's subject line as will fit on the screen.
5198 This is the subject of the first message in the thread.</DD>
5202 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5205 <End of help on this topic>
5208 ============= h_mail_index =============
5211 <TITLE>MESSAGE INDEX COMMANDS</TITLE>
5214 <H1>MESSAGE INDEX COMMANDS</H1>
5215 <!--chtml if pinemode="function_key"-->
5216 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5217 ------------------------------- -----------------------------<BR>
5218 F1 Show Help Text F1 Show Help Text<BR>
5219 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5220 F3 <A HREF="h_common_folders">FOLDER LIST</A> Screen F3 MAIN MENU Screen<BR>
5221 F4 View current message F4 Quit Alpine<BR>
5222 F5 Move to previous message F5 <A HREF="h_common_compose">Compose</A> a message<BR>
5223 F6 Move to next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5224 F7 Show previous screen of messages F7 <A HREF="h_common_nextnew">Next new</A> message<BR>
5225 F8 Show next screen of messages F8 <A HREF="h_index_cmd_whereis">Whereis</A><BR>
5226 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5227 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5228 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5229 F12 <A HREF="h_common_reply">Forward</A> message F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5231 Available Commands -- Group 3<BR>
5232 -----------------------------<BR>
5233 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>
5234 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>
5235 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>
5237 Available Commands -- Group 4<BR>
5238 -----------------------------<BR>
5239 F3 Select Current F4 <A HREF="h_index_cmd_zoom">Zoom</A> F5 COLLECTION LIST Screen
5240 F6 <A HREF="h_common_role">Compose using a role</A> F10 <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread<BR>
5243 Navigating the List of Messages Operations on the Current Message<BR>
5244 ------------------------------- ---------------------------------<BR>
5245 P Move to the previous message > View % <A HREF="h_common_print">Print</A><BR>
5246 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>
5247 - Show previous screen of messages D <A HREF="h_common_delete">Mark for deletion</A><BR>
5248 Spc (space bar) Show next screen U <A HREF="h_common_delete">Undelete</A> (remove deletion mark)<BR>
5249 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>
5250 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>
5251 specific message E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5252 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>
5253 | <A HREF="h_common_pipe">Pipe</A> to a Unix Command<BR>
5254 Miscellaneous Operations<BR>
5255 ------------------------<BR>
5256 G <A HREF="h_common_goto">Goto</A> a specified folder General Alpine Commands<BR>
5257 $ <A HREF="h_index_cmd_sort">Sort</A> order of index ---------------------<BR>
5258 H <A HREF="h_common_hdrmode">Full header mode</A> O Show all other available commands<BR>
5259 X <A HREF="h_index_cmd_expunge">Expunge/Exclude</A> ? Show Help text Q Quit Alpine<BR>
5260 Z <A HREF="h_index_cmd_zoom">Zoom</A> M MAIN MENU Screen < <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5261 ; <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>
5262 : Select Current message # <A HREF="h_common_role">Compose using a role</A><BR>
5263 / <A HREF="h_index_collapse_expand">Collapse/Expand</A> Thread L COLLECTION LIST Screen<BR>
5269 <LI>For help on a particular command, highlight the bold text associated
5270 with it above and hit Return.
5271 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5274 <H2>Description of the MESSAGE INDEX Screen</H2>
5276 The MESSAGE INDEX displays summary information from each
5277 message in the current folder.
5278 This is useful if you want to quickly
5279 scan new messages, or find a particular message without having to go
5280 through the text of each message, or to quickly get rid of junk
5283 The current message is always highlighted
5284 and many commands operate on the current message.
5285 For example, the Delete command will delete the current message.
5286 If the folder is sorted by either Threads or OrderedSubject, then, depending
5287 on some of your configuration settings, a single line in the index may
5288 refer to an entire thread or to a subthread.
5289 If that is the case, then the commands that normally operate on the current
5290 message will operate on the thread or subthread instead.
5291 For example, the Delete command will delete the whole collapsed thread
5292 instead of just a single message.
5294 Each line of the MESSAGE INDEX contains the following columns (by default --
5295 you can change this with the
5296 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
5297 in the SETUP CONFIGURATION screen): <P>
5300 <DD> The markings on the left side of the message tell you about its
5301 status. You may see one or more of the following codes on any given
5304 <LI> "D" for Deleted. You have marked this message for deletion but not
5305 yet eXpunged the folder.
5306 <LI> "N" for New. You have not looked at the text of the message yet.
5307 <LI> "A" for Answered. Any time you reply to a message it is considered
5309 <LI> "F" for Forwarded. Similar to Answered, this is set whenever you
5311 <LI> "+" for direct-to-you. The "+" indicates that a message was sent
5312 directly to your account, your copy is not part of a cc: or a
5314 <LI> "-" for cc-to-you. The "-" indicates that a
5315 message was sent to you as a cc:. This symbol will only show up if
5317 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>" is turned on (which is the default).
5318 <LI> "X" for selected. You have selected the message by using the
5319 "select" command. (Some systems may optionally allow selected
5320 messages to be denoted by the index line being displayed in bold
5322 <LI> "*" for Important. You have previously used the "Flag" command
5323 to mark this message as "important".
5326 <DT>MESSAGE NUMBER:</DT>
5327 <DD>Messages in a folder are numbered, from one through the number
5328 of messages in the folder, to help you know where you are in the folder.
5329 These numbers are always in increasing order, even if you sort the folder
5330 in a different way.</DD><P>
5333 <DD>The date the message was sent. By default, messages are
5334 ordered by arrival time, not by date sent. Most of the time, arrival time
5335 and date sent (effectively departure time) are similar. Sometimes,
5336 however, the index will appear to be out of order because a message took a
5337 long time in delivery or because the sender is in a different time
5338 zone than you are. This date is just the date from the Date header
5339 field in the message.</DD><P>
5341 <DT>WHO SENT THE MESSAGE:</DT>
5342 <DD>This is usually the name of the sender of the message, taken from
5343 the From header of the message.
5344 If there is no personal name given in that
5345 address, then the email address is used instead.
5346 If the message is from you (or from one of your
5347 <A HREF="h_config_alt_addresses">alternate addresses</A>),
5348 then the recipient's name is shown here instead, with the characters
5349 "To: " inserted before the name.
5350 (The idea of this is that if you sent the mail you would rather see who
5351 the mail was sent to instead of that the mail was from you.
5352 This behavior may be changed by modifying the <!--#echo var="VAR_index-format"--> option mentioned
5354 In particular, use the FROM token or the FROMORTONOTNEWS token
5355 in place of the FROMORTO token.)
5356 In Newsgroups, if you are
5357 the sender and there are no email recipients, the newsgroup name will be
5358 listed after the "To: ". </DD><P>
5361 <DD>The number in parentheses is the number of characters in the message.
5362 It may have a suffix of K, M, or G which means the number should be
5363 multiplied by one thousand, one million, or one billion to get the
5364 size of the message.</DD><P>
5367 <DD>As much of the message's subject line as will fit on the screen.</DD>
5371 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5374 <End of help on this topic>
5377 ============= h_mail_view ========================
5380 <TITLE>MESSAGE TEXT SCREEN</TITLE>
5383 <H1>MESSAGE TEXT SCREEN</H1>
5384 <!--chtml if pinemode="function_key"-->
5385 Available Commands -- Group 1 Available Commands -- Group 2<BR>
5386 ------------------------------- ------------------------------<BR>
5387 F1 Show Help Text F1 Show Help Text<BR>
5388 F2 Toggle to see more commands F2 Toggle to see more commands<BR>
5389 F3 <A HREF="h_common_index">MESSAGE INDEX</A> Screen F3 MAIN MENU Screen<BR>
5390 F4 <A HREF="h_view_cmd_viewattch">View attachment</A> F4 Quit Alpine<BR>
5391 F5 Display previous message F5 <A HREF="h_common_folders">FOLDER LIST</A> Screen<BR>
5392 F6 Display next message F6 <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5393 F7 Previous screen of this message F7 <A HREF="h_common_compose">Compose</A> message<BR>
5394 F8 Next screen of this message F8 <A HREF="h_view_cmd_whereis">Whereis</A><BR>
5395 F9 <A HREF="h_common_delete">Mark message for deletion</A> F9 <A HREF="h_common_print">Print</A> message<BR>
5396 F10 <A HREF="h_common_delete">Undelete</A> (remove delete mark) F10 <A HREF="h_common_take">Take Address</A> into address book<BR>
5397 F11 <A HREF="h_common_reply">Reply</A> to message F11 <A HREF="h_common_save">Save</A> message into an email folder<BR>
5398 F12 <A HREF="h_common_reply">Forward</A> F12 <A HREF="h_common_save">Export</A> message into a plain file<BR>
5400 Available Commands -- Group 3<BR>
5401 ------------------------------<BR>
5402 F1 Show Help Text<BR>
5403 F2 Toggle to see more commands<BR>
5404 F3 <A HREF="h_view_cmd_hilite">View hilited</A><BR>
5405 F4 Select current message<BR>
5406 F5 Previous selectable item<BR>
5407 F6 Next selectable item<BR>
5408 F7 <A HREF="h_common_jump">Jump</A> to message number<BR>
5409 F8 <A HREF="h_common_nextnew">Next new</A> message<BR>
5410 F9 <A HREF="h_common_hdrmode">Display full headers</A><BR>
5411 F10 <A HREF="h_common_bounce">Bounce</A> message<BR>
5412 F11 <A HREF="h_common_flag">Flag</A> message<BR>
5413 F12 <A HREF="h_common_pipe">Pipe</A> to a Unix command<BR>
5414 Available Commands -- Group 4<BR>
5415 F5 <A HREF="h_common_role">Compose using a role</A><BR>
5417 Operations on the Current Message<BR>
5418 ---------------------------------<BR>
5420 - Show previous page of this msg S <A HREF="h_common_save">Save</A> into an email folder<BR>
5421 Spc (space bar) Show next page E <A HREF="h_common_save">Export</A> as a plain text file<BR>
5422 > <A HREF="h_view_cmd_viewattch">View attachment</A> B <A HREF="h_common_bounce">Bounce</A><BR>
5423 R <A HREF="h_common_reply">Reply</A> to message F <A HREF="h_common_reply">Forward</A> message<BR>
5424 D <A HREF="h_common_delete">Mark for deletion</A> Ret View <A HREF="h_view_cmd_hilite">hilited</A> item<BR>
5425 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>
5426 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>
5427 % <A HREF="h_common_print">Print</A> * <A HREF="h_common_flag">Flag</A> message<BR>
5428 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>
5430 Navigating the List of Messages Other Commands<BR>
5431 ------------------------------- ----------------------------<BR>
5432 P Display previous message G <A HREF="h_common_goto">Goto</A> a specified folder<BR>
5433 N Display next message H <A HREF="h_common_hdrmode">Full header mode</A> on/off<BR>
5434 J <A HREF="h_common_jump">Jump</A> to a specific message : Select Current message<BR>
5435 Tab <A HREF="h_common_nextnew">Next new</A> message A <A HREF="h_config_prefer_plain_text">Toggle Prefer Plain Text</A><BR>
5437 General Alpine Commands<BR>
5438 ---------------------<BR>
5439 O Show all other available commands<BR>
5440 ? Show Help text Q Quit Alpine<BR>
5441 M MAIN MENU Screen L <A HREF="h_common_folders">FOLDER LIST</A> Screen (or COLLECTION LIST Screen)<BR>
5442 < <A HREF="h_common_index">MESSAGE INDEX</A> Screen C <A HREF="h_common_compose">Compose</A> a new message<BR>
5443 # <A HREF="h_common_role">Compose using a role</A><BR>
5449 <LI>For help on a particular command, highlight the bold text associated
5450 with it above and hit Return.
5451 <LI>Availability of certain commands depends on <A HREF="h_common_conditional_cmds">feature settings</A>.
5454 <H2>Description of the MESSAGE TEXT Screen</H2>
5456 The top line of the view message screen displays status
5457 information about the currently open collection and folder and about the
5458 current message. It shows the name of the collection in angle brackets
5459 and then the name of the folder. The line also displays the number
5460 of messages in the folder, the number of the current message and the
5461 percentage of the current message that has been displayed on the screen.
5462 If the message is marked for deletion "DEL" will appear in the upper
5464 If the message has been answered (but not deleted) "ANS" will show
5468 NOTE: to rapidly move to the end of a message, hit the
5469 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5470 (or Ctrl-W) key followed
5471 by Ctrl-V. Similarly,
5472 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
5473 followed by Ctrl-Y will take you to the beginning of
5476 <H2>Explanation of Alternate Character Sets</H2>
5478 Alpine attempts to stay out of the way so that it won't prevent you from
5479 viewing mail in any character set. It will simply send the message to
5480 your display device. If the device is capable of displaying the
5481 message as it was written it will do so. If not, the display may be
5482 partially or totally incorrect.
5483 If the message contains characters that are not representable in your
5484 <A HREF="h_config_char_set">"Display Character Set"</A>
5485 variable in your configuration, then a warning message will be printed
5486 to your screen at the beginning of the message display.
5487 It is probably best to use UNIX Alpine in a terminal emulator
5488 capable of displaying UTF-8 characters.
5489 See <A HREF="h_config_char_set">Display Character Set</A> for a little
5490 more information about character set settings.
5493 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
5496 <End of help on this topic>
5499 ======= h_index_cmd_select =======
5502 <TITLE>Selecting: Select and WhereIs/Select</TITLE>
5505 <H1>Selecting: Select and WhereIs/Select</H1>
5507 Aggregate operations give you the ability to process a group of messages
5508 at once. Acting on multiple messages requires two steps: (1) selecting a
5509 set of messages and then; (2) applying a command to that set. The first
5510 part is handled by the select command. Select allows you to
5511 select messages based on their status (read, answered, etc.), contents,
5512 date, size, or keywords.
5513 You may also select based on one of your Rules or based on threads,
5514 and there are quick options to select a specific message or range of messages,
5515 to select the current message, or to select all messages.
5518 We describe the various selection criteria briefly:
5523 <DD> Marks all the messages in the folder as selected.
5527 <DD> Selects the currently highlighted message or currently highlighted
5528 set of messages if in a threaded view.
5531 <DT>select by Number</DT>
5532 <DD> Select by message number. This may be a comma-separated list instead or
5534 Each element in the list may be either a single message number or a range
5535 of numbers with a dash between the lowest and highest member of the range.
5536 Some examples are 7 to select only message number 7; 2-5 to select messages
5537 2 through 5; and 2-5,7-9,11 to select messages 2, 3, 4, 5, 7, 8, 9, and 11.
5538 The word "end" or the character "$" may be used as a
5539 substitute for the highest numbered message in the folder, while the
5540 character "." represents the message number holding the position
5541 of the cursor in the folder.
5542 If in a separate thread index where the numbers refer to threads instead of
5543 to messages, then you will be selecting all of the messages in the
5544 referenced threads instead of selecting by message number.
5547 <DT>select by Date</DT>
5548 <DD> Select by either the date stored in the Date headers of each message,
5549 or by the date when the messages arrived.
5550 This does not adjust for different time zones, but just checks to see what
5551 day the message was sent on.
5552 You may type in a date. If you do, the date should be in the form
5553 <P><SAMP><CENTER>DD-Mon-YYYY</CENTER></SAMP><P>
5555 <P><SAMP><CENTER>24-Nov-2004</CENTER></SAMP><P>
5557 <P><SAMP><CENTER>09-Nov-2004</CENTER></SAMP><P>
5558 If the date you want is close to the current date, it is probably
5559 easier to use the "^P Prev Day" or "^N Next Day" commands to change the default date that
5560 is displayed, instead of typing in the date yourself.
5561 Or, the "^X Cur Msg" command may be used to fill in
5562 the date of the currently highlighted message.
5564 There are six possible settings that are selected using the
5565 "^W Toggle When" command.
5566 Three of them select messages based on the Date headers.
5567 They are "SENT SINCE", "SENT BEFORE",
5568 and "SENT ON".
5569 SINCE is all messages with the selected date or later.
5570 BEFORE is all messages earlier than the selected date (not including the day
5572 ON is all messages sent on the selected date.
5573 The other three select messages in the same way but they use the arrival
5574 times of the messages instead of the Date headers included in the messages.
5575 Those three are "ARRIVED SINCE", "ARRIVED BEFORE",
5576 and "ARRIVED ON".
5577 When you save a message from one folder to another the arrival time is
5581 <DT>select by Text</DT>
5582 <DD> Selects messages based on the message contents.
5583 This allows you to select a set of messages based on whether or not the
5584 message headers or message body contain specified text.
5585 You may look for text in the Subject, the From header,
5586 the To header, or the Cc header.
5587 You may also choose Recipient, which searches for the text in
5588 either the To or the Cc header;
5589 or Participant, which means To or Cc or From.
5590 Besides those specific header searches, you may also search the entire
5591 header and text of the message with "All Text", or just the
5592 body of the message.
5594 To search for the absence of text, first type the "! Not" command
5595 before typing the specific type of text search.
5596 For example, you could type "!" followed by "S" to
5597 search for all messages that do not contain a particular word in their
5600 If you choose a Subject search, you may use the subject from the current
5601 message by typing the "^X Cur Subject" command.
5602 You may then edit it further if you wish.
5603 For example, you might select the subject of a reply and edit the
5604 "Re: " off of the front of it in order to search for
5605 the original message being replied to.
5606 All of the other header searches allow you to use addresses from the
5607 headers of the current message if you want to.
5608 You may use the "^T Cur To", "^R Cur From", or
5609 "^W Cur Cc".
5610 In each case, if there is more than one address, only the first is offered.
5613 <DT>select by Status</DT>
5614 <DD> Selects messages based on their status.
5615 You may select all New, Important, Deleted, Answered, Recent, or Unseen
5617 Or, if you first type the "! Not" command, you get not New,
5618 or not Important, and so on.
5619 If you select Deleted messages, you will get all messages with their
5621 Likewise for Important messages, all messages that you have flagged as
5622 being Important with the
5623 <A HREF="h_common_flag">Flag</A> command.
5624 The "New" and "Answered" choices are a little bit odd
5625 because they try to match what you see on the screen by default.
5626 "New" is a shorthand for messages that are Unseen, Undeleted,
5628 If you have looked at the message, or deleted it, or answered it; then it
5629 is not considered "New ".
5630 "! New" is the opposite of "New".
5632 "Answered" is another one that is a little different.
5633 It means that the message has been Answered <EM>and</EM> is not deleted.
5634 And to make it even more confusing, "! Answered" is not
5635 the opposite of "Answered"!
5636 Instead, "! Answered" stands for messages that are
5637 both Unanswered <EM>and</EM> not deleted.
5639 The other two types were added later because the special nature of the
5640 New flag was not what was wanted by all users.
5641 New does match what you see in the index by default, but if you use
5642 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5643 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5644 be exactly what you want.
5645 "Unseen" simply selects all unseen messages, whether or not
5646 they are deleted or answered, and
5647 "Recent" selects all of the messages that have been added to
5648 the folder since you started this Alpine session.
5649 (That's not technically quite true. If there are multiple mail clients
5650 reading an IMAP mailbox, each message will be marked as Recent in only
5651 one of the client's sessions.)
5654 <DT>select by siZe</DT>
5655 <DD> Selects messages based on their size being smaller than or larger
5656 than the size you specify.
5657 The size is the number of bytes.
5658 You may use the suffix "K" or "k" to mean 1,000 times
5660 For example, 7K is the same as 7000.
5661 The suffix "M" or "m" means 1,000,000 times the number,
5662 and the suffix "G" or "g" means 1,000,000,000 times.
5663 Use the "^W" command to toggle back and forth between Smaller
5667 <DT>select by Keyword</DT>
5668 <DD> Selects messages that either have or do not have
5669 (using the "! Not" command)
5670 a particular <A HREF="h_config_keywords">Keyword</A> set.
5671 One way to select a keyword is to use the "^T To List"
5672 command to select one from your list of keywords.
5674 <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.
5677 <DT>select by Rule</DT>
5678 <DD> Selects messages that either match or don't match
5679 (using the "! Not" command)
5680 one of the Rules you have defined.
5681 The most likely method of filling in the Rule is to use the
5682 "^T To List"
5683 command to select one of your Rules.
5684 All of the Rules you have defined will be in the list, including
5685 Rules for Searching, Indexcolors, Filtering, Roles, Score setting, and Other.
5686 They may not all make sense for this purpose, but they are all there for
5688 You might find it useful to define some rules solely for the purpose
5689 of being used by the Select command.
5690 There is a special category for such Rules. They are called Search Rules.
5692 Unfortunately, Alpine does not allow all possible Rules to be defined.
5693 For example, there is no logical OR operation.
5694 OR is accomplished in the Filter Rules or the other types of Rules by
5695 simply defining two rules, one that matches the first part of the OR
5696 and another that matches the second part.
5697 But you can't do that here, since you only have a single Rule to work with.
5698 Likewise, the order of Rules is usually important.
5699 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5700 a message, then that stops the search for a further match.
5701 This means that you may be confused if you try to use Select by Rule to
5702 check your Filter rules because the order is important when filtering but
5703 is not considered here.
5706 <DT>select by tHread</DT>
5707 <DD> Selects all of the messages in the current thread.
5711 After you have an initial selection, the next and subsequent selection
5712 commands modify the selection.
5713 The select command changes. It first gives
5714 you selection "alteration" options: "unselect All",
5715 "unselect Current",
5716 "Broaden selection" (implements a logical OR), and
5717 "Narrow selection" (implements a logical AND).
5718 After you choose either Broaden or Narrow, you then choose one of the
5719 selection criteria listed above (by Text or Number or ...).
5720 You may use select as many times as you wish to get the selected set right.
5723 The WhereIs command has a feature (Ctrl-X) to
5724 select all the messages that match the WhereIs search. WhereIs searches
5725 through just the text that appears on the MESSAGE INDEX screen.
5726 This method is often slower than using the select command itself, unless the
5727 line you are looking for is not too far away in the index.
5730 The availability of the aggregate operations commands is determined by the
5731 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
5732 Feature-List option in your Alpine
5733 configuration, which defaults to set.
5735 <A HREF="h_config_auto_zoom">"<!--#echo var="FEAT_auto-zoom-after-select"-->"</A>
5737 <A HREF="h_config_select_wo_confirm">"<!--#echo var="FEAT_select-without-confirm"-->"</A>
5738 affect the behavior of the Select command.
5741 <End of help on this topic>
5744 ======= h_select_rule =======
5747 <TITLE>Select: Rule</TITLE>
5750 <H1>Select: Rule</H1>
5752 You are selecting messages that either match or don't match
5753 one of the Rules you have defined.
5754 You may either type the nickname of the Rule at the prompt, or use the
5755 "^T To List"
5756 command to select one of your Rules.
5757 All of the Rules you have defined will be in the list, including
5758 Rules for Indexcolors, Filtering, Roles, Score setting, and Other.
5759 They may not all make sense for this purpose, but they are all there for
5761 Rules may be added by using the Setup/Rules screen off of the main Alpine
5764 Unfortunately, Alpine does not allow all possible Rules to be defined.
5765 For example, there is no logical OR operation.
5766 OR is accomplished in the Filter Rules or the other types of Rules by
5767 simply defining two rules, one that matches the first part of the OR
5768 and another that matches the second part.
5769 But you can't do that here, since you only have a single Rule to work with.
5770 Likewise, the order of Rules is usually important.
5771 For example, if the first Filter Rule (or Indexcolor rule or ...) matches
5772 a message, then that stops the search for a further match.
5773 This means that you may be confused if you try to use Select by Rule to
5774 check your Filter rules because the order is important when filtering but
5775 is not considered here.
5778 <End of help on this topic>
5781 ======= h_select_text =======
5784 <TITLE>Select: Text</TITLE>
5787 <H1>Select: Text</H1>
5789 You are selecting messages based on the contents of the message.
5790 This allows you to select a set of messages based on whether or not the
5791 message headers or message body contain specified text.
5792 You may look for text in the Subject, the From header,
5793 the To header, or the Cc header.
5794 You may also choose Recipient, which searches for the text in
5795 either the To or the Cc header;
5796 or Participant, which means either the To header, or the Cc header,
5798 Besides those specific header searches, you may also search the entire
5799 header and text of the message with "All Text", or just the
5800 body of the message with "Body".
5802 To search for the absence of text, first type the "! Not" command
5803 before typing the specific type of text search.
5804 For example, you could type "!" followed by "S" to
5805 search for all messages that do not contain a particular word in their
5808 If you choose a Subject search, you may use the subject from the current
5809 message by typing the "^X Cur Subject" command.
5810 You may then edit it further if you wish.
5811 For example, you might select the subject of a reply and edit the
5812 "Re: " off of the front of it in order to search for
5813 the original message being replied to.
5814 All of the other header searches allow you to use addresses from the
5815 headers of the current message if you want to.
5816 You may use the "^T Cur To", "^R Cur From", or
5817 "^W Cur Cc".
5818 In each case, if there is more than one address, only the first is offered.
5821 <End of help on this topic>
5824 ======= h_select_status =======
5827 <TITLE>Select: Status</TITLE>
5830 <H1>Select: Status</H1>
5832 You are selecting messages based on the status of the message.
5833 For example, whether or not the message has been marked Deleted or Important,
5834 or whether or not it has been Answered or is New.
5835 If you first type the "! Not" command, you will get the
5836 opposite: not Deleted, not Important, and so on.
5838 If you select Deleted messages, you will get all messages with their
5840 Likewise for Important messages, all messages that you have flagged as
5841 being Important with the
5842 <A HREF="h_common_flag">Flag</A> command.
5843 The "New" and "Answered" choices are a little bit odd
5844 because they try to match what you see on the screen by default.
5845 "New" is a shorthand for messages that are Unseen, Undeleted,
5847 If you have looked at the message, or deleted it, or answered it; then it
5848 is not considered "New ".
5849 "! New" is the opposite of "New".
5851 "Answered" is another one that is a little different.
5852 It means that the message has been Answered <EM>and</EM> is not deleted.
5853 And to make it even more confusing, "! Answered" is not
5854 the opposite of "Answered"!
5855 Instead, "! Answered" stands for messages that are
5856 both Unanswered <EM>and</EM> not deleted.
5858 (The New and Answered options may seem counter-intuitive.
5859 The reason it is done this way is
5860 because, by default, a Deleted message will show up with the "D"
5861 symbol in the MAIL INDEX screen even if it is New or Answered.
5862 The Delete symbol overrides the New and Answered symbols, because you
5863 usually don't care about the message anymore once you've deleted it.
5864 Similarly, you usually only care about whether a message is Answered or
5865 not if it is not Deleted.
5866 Once it is Deleted you've put it out of your mind.)
5868 The other two options were added later because the special nature of the
5869 New flag was not what was wanted by all users.
5870 New does match what you see in the index by default, but if you use
5871 the IMAPSTATUS or SHORTIMAPSTATUS token in the
5872 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" it may not
5873 be exactly what you expect.
5874 "Unseen" simply selects all unseen messages, whether or not
5875 they are deleted or answered, and
5876 "Recent" selects all of the messages that have been added to
5877 the folder since you started this Alpine session.
5878 (That's not technically quite true. If there are multiple mail clients
5879 reading an IMAP mailbox, each message will be marked as Recent in only
5880 one of the client's sessions.
5881 That behavior can be convenienent for some purposes, like filtering, but
5882 it isn't usually what you expect when selecting.)
5885 <End of help on this topic>
5888 ======= h_index_cmd_apply =======
5891 <TITLE>Apply Command</TITLE>
5894 <H1>Apply Command</H1>
5897 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->A<!--chtml endif-->)
5898 is the second step of most aggregate operations. Apply
5899 becomes active any time there is a defined set of selected messages. The
5900 following commands can be applied to a selected message set: delete,
5901 undelete, reply, forward,
5902 <!--chtml if pinemode="os_windows"-->
5906 print, take address, save, export, bounce, and flag.
5909 The behavior of some of these commands in an aggregate sense is not easy to
5910 explain. Try them out to see what they do.
5912 <A HREF="h_config_auto_unzoom">"<!--#echo var="FEAT_auto-unzoom-after-apply"-->"</A>
5913 affects the behavior of the Apply command, as does the feature
5914 <A HREF="h_config_auto_unselect">"<!--#echo var="FEAT_auto-unselect-after-apply"-->"</A>.
5917 <End of help on this topic>
5920 ======= h_index_cmd_zoom =======
5923 <TITLE>ZoomMode Command</TITLE>
5926 <H1>ZoomMode Command</H1>
5928 Another action you might want to take on a set of selected messages is to
5929 zoom in on them. Like apply, zoom only becomes active when messages have
5932 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->Z<!--chtml endif-->)
5933 is a toggle command that allows you to
5934 zoom-in (and only see the selected messages) and zoom-out (to see all
5935 messages in the folder). Neither apply nor zoom removes the markings that
5936 define the selected set; you need to use a select command in order
5940 <End of help on this topic>
5943 ======= h_index_collapse_expand =======
5946 <TITLE>Collapse/Expand Command</TITLE>
5949 <H1>Collapse/Expand Command</H1>
5951 The Collapse/Expand command is only available from the MESSAGE INDEX screen when
5952 the folder is sorted by either Threads or OrderedSubject, and the
5953 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
5954 is set to something other than "none".
5955 By default, this command collapses or expands the subthread that starts at
5956 the currently highlighted message, if any.
5957 If the subthread is already collapsed, then this command expands it.
5958 If the subthread is expanded, then this command collapses it.
5959 If there are no more messages below the current message in the
5960 thread tree (that is, there are no replies to the current message) then
5961 this command does nothing.
5964 The behavior of this command is affected by the option
5965 <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>.
5966 Normally, this command Collapses or Expands the subthread that
5967 starts at the currently highlighted message.
5968 If the above option is set, then this command Collapses or Expands the
5969 entire current thread instead of just the subthread.
5970 The current thread is simply the top-level thread that contains the
5974 <End of help on this topic>
5977 ======= h_index_cmd_sort =======
5980 <TITLE>Sort Command</TITLE>
5983 <H1>Sort Command</H1>
5985 In Alpine's generic configuration, messages are presented in the order in
5986 which they arrive. This default can be changed in the SETUP CONFIGURATION
5987 with the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
5988 You can also re-sort the folder on demand with the sort
5989 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
5991 Your sorting options are:
5994 <LI> <A HREF="h_index_sort_arrival">A</A>rrival
5995 <LI> <A HREF="h_index_sort_date">D</A>ate
5996 <LI> <A HREF="h_index_sort_subj">S</A>ubject
5997 <LI> <A HREF="h_index_sort_ordsubj">O</A>rderedSubject
5998 <LI> t<A HREF="h_index_sort_thread">H</A>read
5999 <LI> <A HREF="h_index_sort_from">F</A>rom
6000 <LI> si<A HREF="h_index_sort_size">Z</A>e
6001 <LI> scor<A HREF="h_index_sort_score">E</A>,
6002 <LI> <A HREF="h_index_sort_to">T</A>o
6003 <LI> <A HREF="h_index_sort_cc">C</A>c
6007 The Reverse option will toggle the order the index is currently
6008 sorted by, but will not change the relative sort order.
6011 Sorting a folder does not actually rearrange the way the folder is saved,
6012 it just re-arranges how the messages are presented to you. This means
6013 that Alpine has to do the work of sorting every time you change sort order.
6014 Sometimes, especially with PC-Alpine or with large folders, this could take
6018 <End of help on this topic>
6021 ======= h_index_sort_default =======
6024 <TITLE>SORT OPTION: Default</TITLE>
6027 <H1>SORT OPTION: Default</H1>
6029 The <EM>Default</EM> sort option just means to use the default sort order
6031 <li><a href="h_config_sort_key"><!--#echo var="VAR_sort-key"--></a>
6032 option in Setup/Config.
6035 <End of help on this topic>
6038 ======= h_index_sort_arrival =======
6041 <TITLE>SORT OPTION: Arrival</TITLE>
6044 <H1>SORT OPTION: Arrival</H1>
6046 The <EM>Arrival</EM> sort option arranges messages in the MESSAGE INDEX
6047 in the order that they exist in the folder. This is usually the same as the
6048 order in which they arrived. This option is comparable to not sorting
6049 the messages at all.
6052 <End of help on this topic>
6055 ======= h_index_sort_date =======
6058 <TITLE>SORT OPTION: Date</TITLE>
6061 <H1>SORT OPTION: Date</H1>
6063 The <EM>Date</EM> sort option arranges messages in the MESSAGE INDEX
6064 according to the date and time they were
6068 On a folder like INBOX, sorting by "Date" should be almost
6069 identical to sorting by "Arrival".
6072 <End of help on this topic>
6075 ======= h_index_sort_subj =======
6078 <TITLE>SORT OPTION: Subject</TITLE>
6081 <H1>SORT OPTION: Subject</H1>
6083 The <EM>Subject</EM> sort option arranges messages in the MESSAGE INDEX
6087 Messages with the same subject are
6088 first grouped together, and then the groups of like-subject messages
6089 are arranged alphabetically.
6092 Alpine ignores leading "Re:" and
6093 "re:" and trailing "(fwd)" when determining the
6094 likeness and alphabetical order of subject lines.
6097 <End of help on this topic>
6100 ======= h_index_sort_ordsubj =======
6103 <TITLE>SORT OPTION: OrderedSubject</TITLE>
6106 <H1>SORT OPTION: OrderedSubject</H1>
6108 The <EM>OrderedSubject</EM> sort option arranges messages in the
6109 MESSAGE INDEX by grouping all messages with the same subject
6110 together, similar to sort by <A HREF="h_index_sort_subj">S</A>ubject.
6113 However, <EM>OrderedSubj</EM> then arranges the groups of like-subject
6114 messages by the date of the oldest message in the group.
6117 This sort method provides for pseudo threading of conversations within
6119 You may want to try sorting by Thread instead.
6122 <End of help on this topic>
6125 ======= h_index_sort_thread =======
6128 <TITLE>SORT OPTION: Thread</TITLE>
6131 <H1>SORT OPTION: Thread</H1>
6133 The <EM>Thread</EM> sort option arranges messages in the
6134 MESSAGE INDEX by grouping all messages that indicate
6135 they are part of a conversation (discussion thread) taking
6136 place within a mailbox or newsgroup. This indication is
6137 based on information in the message's header -- specifically
6138 its <tt>References:</tt>, <tt>Message-ID:</tt>, and <tt>Subject:</tt> fields.
6141 <End of help on this topic>
6144 ======= h_index_sort_from =======
6147 <TITLE>SORT OPTION: From</TITLE>
6150 <H1>SORT OPTION: From</H1>
6152 The <EM>From</EM> sort option arranges messages in the MESSAGE INDEX
6153 by the name of the author of the message.
6156 Messages with the same author are grouped together. Groups of
6157 messages are then put into alphabetical order according to message
6161 <End of help on this topic>
6164 ======= h_index_sort_size =======
6167 <TITLE>SORT OPTION: Size</TITLE>
6170 <H1>SORT OPTION: Size</H1>
6172 The <EM>Size</EM> sort option arranges messages in the MESSAGE INDEX
6173 by their relative sizes.
6176 <End of help on this topic>
6179 ======= h_index_sort_score =======
6182 <TITLE>SORT OPTION: Score</TITLE>
6185 <H1>SORT OPTION: Score</H1>
6187 The <EM>Score</EM> sort option arranges messages in the MESSAGE INDEX
6191 Messages with the same score are sorted in arrival order.
6192 Scores are something you create using the
6193 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
6196 <End of help on this topic>
6199 ======= h_index_sort_to =======
6202 <TITLE>SORT OPTION: To</TITLE>
6205 <H1>SORT OPTION: To</H1>
6207 The <EM>To</EM> sort option arranges messages in the MESSAGE INDEX
6208 by the names of the recipients of the message.
6211 Messages with the same recipients are grouped together. Groups of
6212 messages are then put into alphabetical order according to message
6216 <End of help on this topic>
6219 ======= h_index_sort_cc =======
6222 <TITLE>SORT OPTION: Cc</TITLE>
6225 <H1>SORT OPTION: Cc</H1>
6227 The <EM>Cc</EM> sort option arranges messages in the MESSAGE INDEX by
6228 the names of the carbon copy addresses of the message.
6231 <End of help on this topic>
6234 ======= h_index_cmd_whereis =======
6237 <TITLE>WhereIs Command</TITLE>
6240 <H1>WhereIs Command</H1>
6243 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6244 command lets you search the MESSAGE INDEX for a word.
6245 It scans through whatever you see, usually the name of the author
6246 and the Subject line.
6247 WhereIs has special subcommands to let you find the beginning of the
6248 index (Ctrl-Y -- first message)
6249 or the end of the index (Ctrl-V -- last message).
6251 Note that WhereIs only searches through the visible text on the screen.
6252 For example, if only part of the Subject of a message is shown because it
6253 is long, then only the visible portion of the Subject is searched.
6254 Also note that WhereIs does not "see" the
6255 "X" in column one of Index entries for selected messages
6256 so it can't be used to search for
6257 selected messages (use "Zoom" instead).
6260 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
6262 WhereIs can also be used as a quick way to select messages that match the
6263 string being searched for.
6264 Instead of typing carriage return to search for the next match, type
6265 Ctrl-X to select all matches.
6266 Once again, this only selects matches that are (or would be if the right
6267 index line was on the screen) visible.
6268 Truncated From lines or Subjects will cause matches to be missed.
6269 Although WhereIs is sometimes convenient for quick matching, the Select
6270 command is usually more powerful and usually faster.
6273 <End of help on this topic>
6276 ======= h_view_cmd_whereis =======
6279 <TITLE>WhereIs Command</TITLE>
6282 <H1>WhereIs Command</H1>
6285 (<!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->)
6286 command does a "find in current message" operation. You
6287 type in text and Alpine will try to find it in the message you are
6288 reading. WhereIs also has subcommands to jump to the beginning (Ctrl-Y)
6289 or end (Ctrl-V) of the message.
6290 That is, to rapidly move to the end of a message, hit the
6291 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6292 (or Ctrl-W) key followed
6293 by Ctrl-V. Similarly,
6294 <!--chtml if pinemode="function_key"-->F8<!--chtml else-->W<!--chtml endif-->
6295 followed by Ctrl-Y will take you to the beginning of a message.
6298 <End of help on this topic>
6301 ======= h_view_cmd_hilite =======
6304 <TITLE>View Hilite and Next item/Previous item</TITLE>
6307 <H1>View Hilite and Next item/Previous item</H1>
6309 Sometimes messages may be in the form of formatted HTML text
6310 or they may contain URLs or Web server hostnames.
6311 When any of the features
6312 <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>,
6313 <A HREF="h_config_enable_view_web_host">"<!--#echo var="FEAT_enable-msg-view-web-hostnames"-->"</A>,
6314 <A HREF="h_config_enable_view_attach">"<!--#echo var="FEAT_enable-msg-view-attachments"-->"</A>,
6316 <A HREF="h_config_enable_view_addresses">"<!--#echo var="FEAT_enable-msg-view-addresses"-->"</A>
6317 are enabled, Alpine will represent such selectable items in the text
6318 in bold typeface. One of the selectable items will be displayed in
6319 inverse video (highlighted). This is the "currently selected" item.
6320 Press the Return key to view the currently selected item.
6323 The Up and Down Arrows keys can be used to change the selected item
6324 (also see the feature
6325 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
6326 If there are no selectable items in the direction of the arrow you
6327 pressed, Alpine will scroll the display in that direction until one
6328 becomes visible. To "jump" forwards/backwards among selectable
6329 items in the message text, use the Previous and Next item commands,
6330 <!--chtml if pinemode="function_key"-->F5 and F6
6331 <!--chtml else-->^B and ^F<!--chtml endif-->.
6334 <End of help on this topic>
6337 ======= h_view_cmd_viewattch =======
6340 <TITLE>ViewAttch Command</TITLE>
6343 <H1>ViewAttch Command</H1>
6346 The View/Save Attachment
6347 (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->V<!--chtml endif-->)
6348 command allows you to handle MIME attachments to a message you have
6349 received. Alpine shows you a list of the message attachments -- you just
6350 choose the attachment you want. You may either view or save the
6351 selected attachment.
6354 Because many attachments require external programs for display, there
6355 is some system configuration that has to happen before you can
6356 actually display attachments. Hopefully much of that will have been
6357 done already by your system administrator. MIME configuration is
6358 handled with the "mailcap" configuration file. (See the section
6359 on configuration in the
6360 <A HREF="h_news">release notes</A> for more information.)
6363 <End of help on this topic>
6366 ======= h_index_cmd_expunge =======
6369 <TITLE>Expunge/Exclude Command</TITLE>
6372 <H1>Expunge/Exclude Command</H1>
6375 (<!--chtml if pinemode="function_key"-->F3<!--chtml else-->X<!--chtml endif-->)
6376 is the command Alpine uses to actually remove all messages
6377 marked for deletion. With regular email files, expunge literally deletes
6378 the text from the current folder. With newsgroups or shared mailboxes,
6379 you don't have permission to actually remove the message, so it is an
6380 exclude -- Alpine removes the message from your view of the folder even
6381 though it is not technically gone.
6383 <P> A selective expunge command is available in IMAP folders that support
6384 the UID EXPUNGE extension in <A
6385 HREF="http://tools.ietf.org/html/rfc4315">RFC 4315</A> as well as for all
6386 other folders (local folders in all formats, POP3 inbox, and newsgroups)
6387 as a subcommand of the apply command. If some selected messages are marked
6388 deleted, then the apply command will offer the eXpunge command, which when
6389 executed will only expunge those messages that are selected and deleted.
6392 Observe that the expunge command (when not used from the apply command)
6393 will expunge/exclude all deleted messages from the folder, and so all
6394 messages marked deleted will be expunged, regardless of if they are
6395 selected or not. In other words, there is no protection against
6396 potentially expunging more messages than only those that have been
6397 selected and deleted.
6400 The configuration features
6401 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
6403 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>
6404 affect the behavior of the Expunge command.
6407 <End of help on this topic>
6410 ======= h_common_compose =======
6413 <TITLE>Compose Command</TITLE>
6416 <H1>Compose Command</H1>
6418 The Compose command takes you into the Alpine message composer where you
6419 can start a new message for sending. This is where you type in the
6420 message's text and specify its recipient list (the "To:"
6421 address), where copies should be directed (e.g., "Fcc",
6422 "Cc:" or "Bcc:"), and which files, if any, should
6423 be attached to the message.
6426 When you type this command, Alpine will also automatically check for any
6427 interrupted (i.e., a message that was being composed when your modem
6428 or network connection was broken) or previously postponed messages and
6429 offer you a chance to continue working on those.
6433 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6435 <End of help on this topic>
6438 ======= h_common_index =======
6441 <TITLE>Message Index Command</TITLE>
6444 <H1>Message Index Command</H1>
6446 The Index command takes you to the MESSAGE INDEX screen that displays a
6447 summary caption for each message in the currently-open folder. One
6448 message will be highlighted; this is the "Current" message.
6449 The message commands available from this screen (e.g. View, Reply,
6450 Forward, Delete, Print, Save, etc) apply to the current message.
6453 <End of help on this topic>
6456 ======= h_common_folders =======
6459 <TITLE>Folder List Command</TITLE>
6462 <H1>Folder List Command</H1>
6464 This Folder List command takes you to the FOLDER LIST screen that displays
6465 the names of all your message folders and allows you to view, rename,
6466 delete, and add folders. You can open (view) a different folder than the
6467 one currently open by highlighting the desired one (using the arrow keys
6468 or their control-key equivalents) and pressing RETURN.
6471 If you have multiple folder collections defined (see the Help text for
6472 the FOLDER LIST screen to learn more about Collections), you may need
6473 to press Return to expand the collection and display all of the
6477 <End of help on this topic>
6480 ======= h_main_addrbook =======
6483 <TITLE>Address Book Command</TITLE>
6486 <H1>Address Book Command</H1>
6488 This command, available only from the MAIN MENU, takes you
6489 to the ADDRESS BOOK management screen. From here, your personal address
6490 book(s) may be updated.
6493 <End of help on this topic>
6496 ======= h_main_setup =======
6499 <TITLE>Setup Command</TITLE>
6502 <H1>Setup Command</H1>
6504 The Setup command, available only from the MAIN MENU, prompts you for
6505 one of several configuration screens, including the SETUP CONFIGURATION
6506 screen, by which you may activate optional Alpine features.
6509 <End of help on this topic>
6512 ======= h_main_release_notes =======
6515 <TITLE>Release Notes Command</TITLE>
6518 <H1>Release Notes Command</H1>
6520 This command displays information about Alpine <!--#echo var="ALPINE_VERSION"-->,
6521 as well as pointers to further information such as history and legal notes.
6524 <End of help on this topic>
6527 ======= h_main_kblock =======
6530 <TITLE>Keyboard Lock Command</TITLE>
6533 <H1>Keyboard Lock Command</H1>
6535 This command allows your Alpine session to be protected
6536 during a temporary absence from your terminal.
6539 <End of help on this topic>
6542 ======= h_main_journal =======
6545 <TITLE>Journal Command</TITLE>
6548 <H1>Journal Command</H1>
6550 This command displays a list of all the status messages Alpine has
6551 displayed (on the third line from the bottom of the screen). This may
6552 be useful if a message disappeared before you had a chance to read it.
6555 <End of help on this topic>
6558 ======= h_common_role =======
6561 <TITLE>Role Command</TITLE>
6564 <H1>Role Command</H1>
6566 The Role command is similar to the Compose command except that it starts
6567 off by letting you select a <A HREF="h_rules_roles">role</A>
6568 to be used for the composition.
6569 You may set up alternate roles by using Setup/Rules/Roles.
6572 <End of help on this topic>
6575 ======= h_common_conditional_cmds =======
6578 <TITLE>Conditional Commands</TITLE>
6581 <H1>Conditional Commands</H1>
6583 The presence or absence of certain commands, particularly in the
6584 MESSAGE INDEX and MESSAGE TEXT screens, is determined by
6585 whether or not specific features are set in your Alpine configuration.
6586 (You can access the SETUP CONFIGURATION screen, where they are found, from
6587 Alpine's MAIN MENU.) To see if a desired command's availability is
6588 conditioned on a feature setting, see the command's help text (highlight
6589 the phrase associated with the command and hit Return).
6593 commands may be administratively disabled by your system manager;
6594 if they don't work, please check with your local help desk.
6598 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6600 <End of help on this topic>
6603 ======= h_common_pipe =======
6606 <TITLE>Pipe Command</TITLE>
6609 <H1>Pipe Command</H1>
6612 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->|<!--chtml endif-->)
6613 allows you to send a message to a specified Unix command for external
6615 This command's availability is controlled by the
6616 <A HREF="h_config_enable_pipe">"<!--#echo var="FEAT_enable-unix-pipe-cmd"-->"</A>
6618 By default, the processed text of the message is sent to the command
6619 you specify and the output is captured by Alpine and shown to you.
6620 When you run the pipe command, there are some sub-commands which may be
6621 used to alter this behavior.
6622 These sub-commands are described <A HREF="h_pipe_command">here</A>.
6625 <End of help on this topic>
6628 ======= h_common_goto =======
6631 <TITLE>Goto Command</TITLE>
6634 <H1>Goto Command</H1>
6637 (<!--chtml if pinemode="function_key"-->F6<!--chtml else-->G<!--chtml endif-->)
6638 is the command that lets you bypass Alpine's folder selection screens
6639 and jump directly to a new folder. You can select any folder in the
6640 world: one in your current collection, one in a different collection or
6641 one in a collection you've never even used before.
6644 Alpine will help you as much as possible to narrow in on the folder you want.
6645 However, if the folder is outside of your defined collections, you are
6646 going to have to enter the exact folder location using the correct
6647 <A HREF="h_valid_folder_names">syntax</A>
6648 for a remote folder and/or fully-qualified path name.
6651 <End of help on this topic>
6654 ======= h_common_nextnew =======
6657 <TITLE>NextNew Command</TITLE>
6660 <H1>NextNew Command</H1>
6662 When you press the TAB key, Alpine advances to the next
6663 "interesting" message.
6664 This will be the next message you have not seen before, or the next message
6665 you have flagged Important, whichever comes first.
6666 Unread messages that have been deleted are not considered interesting.
6667 (A note about reading news. Alpine expects you to "Delete" news
6668 articles after you have read them if you want to remove them from future
6669 consideration. See <A HREF="h_mainhelp_readingnews">Reading News</A> for
6673 The NextNew command is affected by the feature
6674 <A HREF="h_config_tab_new_only">"<!--#echo var="FEAT_tab-visits-next-new-message-only"-->"</A>,
6675 which causes Alpine to only consider Unread messages interesting, not messages
6679 This command behaves a little differently when it finds there are no more
6680 interesting messages left in the current folder.
6681 If the current folder is one of your Incoming Message Folders
6682 (<A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>)
6683 or it is a newsgroup, then Alpine will try to find the next folder or
6684 newsgroup that contains <EM>Recent</EM> messages and will ask you
6685 if you want to open that folder.
6686 This behavior may be modified by using the
6687 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
6688 feature that causes Alpine to look for Unseen messages instead of Recent
6690 The NextNew command's behavior is also affected by the configuration features
6691 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A>,
6693 <A HREF="h_config_tab_no_prompt">"<!--#echo var="FEAT_continue-tab-without-confirm"-->"</A>.
6696 <End of help on this topic>
6699 ======= h_common_jump =======
6702 <TITLE>Jump Command</TITLE>
6705 <H1>Jump Command</H1>
6707 This is Alpine's way of allowing you to go straight to a specific message.
6708 Just press "J" and then enter the message number. By default, Alpine is also
6709 configured such that typing in any number automatically jumps you to that
6711 (<A HREF="h_config_enable_jump">"<!--#echo var="FEAT_enable-jump-shortcut"-->"</A>
6712 in the SETUP CONFIGURATION).
6715 <End of help on this topic>
6718 ======= h_common_flag =======
6721 <TITLE>Flag Command</TITLE>
6724 <H1>Flag Command</H1>
6727 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6728 is the command that allows users to manipulate the status flags that
6729 appear on the left side of the MESSAGE INDEX screen. The most common
6730 use of this is to mark a message as important. This is something of a
6731 note to yourself to get back to that message. You may also use the
6732 flag command to set (or unset) the flags that indicate that a message
6733 is new, answered, deleted, or forwarded.<P>
6735 Provided the mail server supports it,
6736 you may also manipulate user-defined keywords
6737 for a message using the flag command.
6738 These keywords will be available if you use the Flag Details screen that you
6739 can get to after typing the
6740 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
6742 They will be listed after the Important, New, Answered, Deleted , and Forwarded flags,
6743 which are always present.
6744 You may add new keywords by using the Add KW command from the Flag Details screen
6745 or by defining them in the <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
6747 The availability of the flag command is determined by the
6748 <A HREF="h_config_enable_flag">"<!--#echo var="FEAT_enable-flag-cmd"-->"</A>
6749 feature in your Alpine configuration. Also, it is possible that Flag could be
6750 administratively disabled by your system manager; if it doesn't work,
6751 please check with your local help desk before reporting a bug.
6752 The behavior of the flag command may be modified by the
6753 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
6754 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
6757 <End of help on this topic>
6760 ======= h_common_hdrmode =======
6763 <TITLE>HdrMode Command</TITLE>
6766 <H1>HdrMode Command</H1>
6768 Every email message comes with some header lines that you normally
6769 don't see (and don't want to see).
6770 These include anywhere from 3-20 lines (or more) added by the
6771 Internet mail transport system to record the route your message took,
6772 for diagnostic purposes.
6773 These are normally of no import and simply
6774 add clutter, so Alpine suppresses them in the MESSAGE TEXT display.
6775 This also includes other non-standard headers the message may contain.
6776 If you want to see these headers, there is a way to reveal them.
6780 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6781 command is a toggle that controls Alpine's handling of these header
6782 lines. Normally, full headers is "off" and you only see a
6783 few lines about who a message is to and who it is from. When you
6785 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->H<!--chtml endif-->)
6786 to turn full headers on, Alpine will show you
6787 the normal header lines as well as delivery headers, comment headers,
6788 MIME headers, and any other headers present.
6791 Several different Alpine commands honor the header mode -- it affects how
6792 messages are displayed, how they appear in forward and reply email, how
6793 they are printed, how they are saved, and how they are exported.
6794 <!--chtml if pinemode="os_windows"-->
6796 The pipe command is also affected.
6800 The presence or absence of the Header Mode command is determined by the
6801 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
6802 Feature-List option in your Alpine configuration.
6805 If you have also turned on the
6806 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
6807 option then the HdrMode command actually rotates through three states
6808 instead of just two.
6809 The first is the normal view with long quotes suppressed.
6810 The second is the normal view but with the long quotes included.
6811 The last enables the display of all headers in the message.
6812 When using Export, Pipe, Print, Forward, or Reply the quotes are
6813 never suppressed, so the first two states are identical.
6816 The behavior of the Header Mode command may be altered slightly by
6818 <A HREF="h_config_quell_full_hdr_reset">"<!--#echo var="FEAT_quell-full-header-auto-reset"-->"</A>
6819 Feature-List option in your Alpine configuration.
6820 In particular, it will cause the Header Mode to be persistent when moving
6821 from message to message instead of resetting to the default for each message.
6825 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
6827 <End of help on this topic>
6830 ======= h_common_print =======
6833 <TITLE>Print Command</TITLE>
6836 <H1>Print Command</H1>
6839 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->%<!--chtml endif-->)
6840 command allows you to print a copy of a message.
6841 There are many SETUP CONFIGURATION features that affect the
6842 Print command, including
6843 <A HREF="h_config_enable_y_print">"<!--#echo var="FEAT_enable-print-via-y-command"-->"</A>,
6844 <A HREF="h_config_print_index">"<!--#echo var="FEAT_print-index-enabled"-->"</A>,
6845 <A HREF="h_config_custom_print">"<!--#echo var="FEAT_print-offers-custom-cmd-prompt"-->"</A>,
6846 <A HREF="h_config_print_from">"<!--#echo var="FEAT_print-includes-from-line"-->"</A>, and
6847 <A HREF="h_config_ff_between_msgs">"<!--#echo var="FEAT_print-formfeed-between-messages"-->"</A>.
6848 You set up for printing by using the Printer option of the Setup command
6853 <End of help on this topic>
6856 ======= h_common_take =======
6859 <TITLE>TakeAddr Command</TITLE>
6862 <H1>TakeAddr Command</H1>
6865 With the Take Address
6866 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->T<!--chtml endif-->)
6867 command, you can extract email addresses from an
6868 incoming message and save them in an address book. This is an easy way
6869 to add to your address book and avoid having to remember the email
6870 addresses of the people who write to you.
6873 If the message is just to you individually, then you will only need to
6874 provide a nickname. If the message contains more than one email address,
6875 then you will see an address
6876 selection screen that lets you choose the address you want to save into
6877 your address book, or lets you choose several of them add to a
6878 personal distribution list.
6881 Once you've added an entry to your address book, you can use it from the
6882 message composer by typing the nickname of the entry into one of the
6883 header fields (for example, into the To: field), or you can use ^T from
6884 the header field to select the entry from your address book.
6887 If the configuration feature
6888 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
6889 is set, the behavior of the Take command is altered slightly.
6892 <End of help on this topic>
6895 ======= h_ge_import =======
6898 <TITLE>Import File Selection</TITLE>
6901 <H1>Import File Selection</H1>
6903 You are importing a file that you previously
6904 exported from Alpine.
6905 You are now being asked for the name of that file.
6906 The easiest way to select a file is probably with the "^T"
6907 "To Files" command.
6908 Alternatively, you may type in a file name.
6909 It may be an absolute pathname.
6910 Otherwise, it is a file located in your home directory
6911 or current working directory
6912 <!--chtml if pinemode="running"-->
6913 (which, at least for your current Alpine "session,"
6914 is "<!--#echo var="CURRENT_DIR"-->")
6915 <!--chtml endif-->, depending on the
6916 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6917 In any case, you finish by typing a carriage return to accept the
6918 file name that is displayed.
6920 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6921 is turned on you may use TAB to complete partially typed in names.
6923 You may cancel the import operation by typing "^C" after exiting
6926 <End of help on this topic>
6929 ======= h_ge_allparts =======
6932 <TITLE>Export Message File Selection</TITLE>
6935 <H1>Export Message File Selection</H1>
6937 You are Exporting a message from an Alpine mail folder
6938 to a plain text file.
6939 You also have the option of exporting all of the attachments associated
6941 You are now being asked for the name of the file to export <EM>to</EM>.
6942 The easiest way to select a file is probably with the "^T"
6943 "To Files" subcommand.
6944 After returning from that subcommand you will still be allowed to
6945 edit the name you have selected.
6946 Alternatively, you may type in a file name.
6947 It may be an absolute pathname.
6948 Otherwise, it is a file located in your home directory
6949 or current working directory
6950 <!--chtml if pinemode="running"-->
6951 (which, at least for your current Alpine "session,"
6952 is "<!--#echo var="CURRENT_DIR"-->")
6953 <!--chtml endif-->, depending on the
6954 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
6955 In any case, you finish by typing a carriage return to accept the
6956 file name that is displayed.
6958 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
6959 is turned on you may use TAB to complete partially typed in names.
6961 The message you are exporting appears to have some attachments.
6962 If you wish to save <EM>all</EM> of the attachments at once,
6963 type the "^P" "AllParts" command to turn on
6964 saving of the attachments.
6965 You may turn it back off by typing "^P" again, which will now
6966 be labeled "NoAllParts" instead.
6967 If you want to save the parts the command displayed should be
6968 "NoAllParts"!
6969 When you choose to save attachments like this, the attachments will be saved
6970 in a newly created directory.
6971 That directory will have the same name as the file name you choose here,
6972 with the letters ".d" appended.
6973 If that directory already exists, then the letters ".d_1" will
6974 be tried, then ".d_2" and so on until a name that doesn't exist
6976 For example, if you select the file name
6978 <CENTER><SAMP>filename</SAMP></CENTER>
6980 to export the message to, then the directory used for the attachments will be
6982 <CENTER><SAMP>filename.d</SAMP></CENTER>
6986 <CENTER><SAMP>filename.d_<n></SAMP></CENTER>
6988 The attachments will then be put into files inside that directory.
6989 The names for the attachment files will be derived from the attachments
6991 This is done in the same way as the default values are derived if you
6992 save them one at a time.
6993 (The "filename" parameter from the Content-Disposition header
6994 is the first choice. If that doesn't exist, the "name"
6995 parameter from the Content-Type header is used.)
6996 If a name for a particular attachment is not available, then the
6997 part number of the attachment is used, with the characters "part_"
6999 An example of that would be
7001 <CENTER><SAMP>part_2.1</SAMP></CENTER>
7003 If you want to save only some of the attachments or if you want more control
7004 over the directory and filename where an attachment is saved you may
7005 cancel out of this command and View the attachment list.
7006 From there you can save each attachment individually.
7008 You may cancel the Export operation by typing "^C" after exiting
7011 <End of help on this topic>
7014 ======= h_ge_export =======
7017 <TITLE>Export File Selection</TITLE>
7020 <H1>Export File Selection</H1>
7022 You are Exporting or Saving something from within the Alpine world
7023 (a message, an attachment, etc.)
7024 to a plain text file.
7025 You are now being asked for the name of the file to export <EM>to</EM>.
7026 The easiest way to select a file is probably with the "^T"
7027 "To Files" subcommand.
7028 After returning from that subcommand you will still be allowed to
7029 edit the name you have selected.
7030 Alternatively, you may type in a file name.
7031 It may be an absolute pathname.
7032 Otherwise, it is a file located in your home directory
7033 or current working directory
7034 <!--chtml if pinemode="running"-->
7035 (which, at least for your current Alpine "session,"
7036 is "<!--#echo var="CURRENT_DIR"-->")
7037 <!--chtml endif-->, depending on the
7038 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A> option.
7039 In any case, you finish by typing a carriage return to accept the
7040 file name that is displayed.
7042 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
7043 is turned on you may use TAB to complete partially typed in names.
7045 If the object you are exporting is a message with some attachments,
7046 you may wish to save all of the attachments by typing the "^P"
7047 "AllParts" command to turn on saving of the attachments.
7048 This subcommand will only be visible if the message actually has attachments.
7049 You may also View the attachment list and save individual attachments from
7052 If you are SAVING a text part (text/plain, text/html, etc.) you can use
7053 the Control-R subcommand to toggle if saving will be done in binary mode,
7054 meaning that the attachment will be decoded, but will not be transformed
7055 to UTF-8 for further processing (either in internal filters, or user
7056 supplied filters.) This is useful in case you either want to preserve
7057 the text as it was encoded originally to you, or the attachment was
7058 incorrectly attached (the attachment is not of text type) and you need
7059 the original text to process the attachment.
7061 You may cancel the Export operation by typing "^C" after exiting
7064 <End of help on this topic>
7067 ======= h_common_save =======
7070 <TITLE>Save and Export Commands</TITLE>
7073 <H1>Save and Export Commands</H1>
7076 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->S<!--chtml endif-->)
7078 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->E<!--chtml endif-->)
7079 are the two alternatives Alpine gives you to keep a copy of the message
7080 you are reading. If you want to keep the message within Alpine's email
7081 world, use "Save"; if you want to use the message in another
7082 program, use "Export".
7085 When you Save a message, it is put into an existing folder or into a new
7086 folder in one of your existing folder collections. The message stays in
7087 email format and can be read by Alpine again. Alpine may use a special format
7088 for its mail folders -- never edit an Alpine folder by hand or with any
7089 program other than Alpine. The exact behavior of the Save command can be
7091 <A HREF="h_config_quote_all_froms">"<!--#echo var="FEAT_save-will-quote-leading-froms"-->"</A>,
7092 <A HREF="h_config_save_wont_delete">"<!--#echo var="FEAT_save-will-not-delete"-->"</A>,
7094 <A HREF="h_config_save_advances">"<!--#echo var="FEAT_save-will-advance"-->"</A>
7095 feature list settings.
7096 The name of the folder offered as a default is controlled by the option
7097 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>.
7100 When you use Export, the message is placed in a plain text file in your
7102 <!--chtml if pinemode="running"-->
7103 (which, in the present configuration of your system, is
7104 "<!--#echo var="HOME_DIR"-->")
7106 or current working directory
7107 <!--chtml if pinemode="running"-->
7108 (which, at least for your current Alpine "session,"
7109 is "<!--#echo var="CURRENT_DIR"-->")
7110 <!--chtml endif-->, depending on the
7111 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7112 configuration setting. In the normal case, only minimal
7113 headers are exported with the message; however, if the full header mode
7114 (whose availability may be disabled by setting the feature
7115 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
7116 in SETUP CONFIGURATION) is
7117 toggled on, then complete headers are exported along with the message
7118 text. (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
7119 defined, they may affect the contents of the exported file.)
7122 <End of help on this topic>
7125 ======= h_common_bounce =======
7128 <TITLE>Bounce Command</TITLE>
7131 <H1>Bounce Command</H1>
7134 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->B<!--chtml endif-->)
7135 command allows you to re-send, or "remail", a
7136 message, as if you were never in the loop. It is analogous to crossing
7137 out your address on a postal letter, writing a different address on the
7138 envelope, and putting it into the mailbox. Bounce is used primarily to
7139 redirect email that was sent to you in error.
7140 Also, some owners of email
7141 lists need the bounce command to handle list traffic.
7142 Bounce is not anonymous.
7143 A ReSent-From header is added to the message so that the recipient may
7144 tell that you Bounced it to them.
7147 The presence or absence of the Bounce command is determined by the
7148 <A HREF="h_config_enable_bounce">"<!--#echo var="FEAT_enable-bounce-cmd"-->"</A>
7149 feature in your Alpine configuration.
7151 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A>
7152 affects the behavior of the Bounce command.
7153 Also, it is possible that Bounce could be
7154 administratively disabled by your system manager; if it doesn't work,
7155 please check with your local help desk before reporting a bug.
7158 <End of help on this topic>
7161 ======= h_common_reply =======
7164 <TITLE>Reply and Forward Commands</TITLE>
7168 <H1>Reply and Forward Commands</H1>
7171 (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->R<!--chtml endif-->)
7173 (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->F<!--chtml endif-->)
7174 are your two alternatives for following up on the
7175 message you are reading. You would use reply if you want to get email
7176 back to the author of the message and/or the other people who have
7177 already seen it. You use forward if you want somebody new to see the
7181 In the normal case, the only thing that you must supply when forwarding a
7182 message is the name/email address of the new recipient.
7183 Alpine will include the text of the forwarded message.
7184 Alpine will also include any attachments to the message.
7185 There is space above the forwarded text for you to include additional comments.
7188 When replying, you usually have to answer some questions.
7189 If the message is to multiple people and/or specified with a Reply-To: header,
7190 then you will have to decide who should get the reply.
7191 You also need to decide whether or not to include the previous
7192 message in your reply.
7193 Some of this is configurable.
7194 Specifically, see the
7195 <A HREF="h_config_include_header">"<!--#echo var="FEAT_include-header-in-reply"-->"</A>,
7196 <A HREF="h_config_auto_include_reply">"<!--#echo var="FEAT_include-text-in-reply"-->"</A>,
7197 <A HREF="h_config_attach_in_reply">"<!--#echo var="FEAT_include-attachments-in-reply"-->"</A>,
7199 <A HREF="h_config_auto_reply_to">"<!--#echo var="FEAT_reply-always-uses-reply-to"-->"</A>
7200 configuration features.
7203 Both the Reply and Forward commands react to the full header mode toggle.
7204 If the full header mode is on, then all the header and delivery lines are
7205 included with the text of the message in your reply/forward.
7208 Other configuration features that affect the Reply command are
7209 <A HREF="h_config_sig_at_bottom">"<!--#echo var="FEAT_signature-at-bottom"-->"</A>,
7210 <A HREF="h_config_sigdashes">"<!--#echo var="FEAT_enable-sigdashes"-->"</A>, and
7211 <A HREF="h_config_strip_sigdashes">"<!--#echo var="FEAT_strip-from-sigdashes-on-reply"-->"</A>.
7214 <End of help on this topic>
7217 ======= h_common_delete =======
7220 <TITLE>Delete and Undelete Commands</TITLE>
7223 <H1>Delete and Undelete Commands</H1>
7226 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->D<!--chtml endif-->)
7228 (<!--chtml if pinemode="function_key"-->F10<!--chtml else-->U<!--chtml endif-->)
7229 allow you to change the Deleted flag for the current message.
7230 Delete marks a message Deleted (turns on the Deleted flag) and Undelete
7232 In the MESSAGE INDEX, deleted messages have a "D" in the status field
7233 at the left hand edge of the index line.
7234 When viewing a deleted message, the letters "DEL" will be present
7235 in the upper right hand corner of the screen.
7236 Delete simply <EM>marks</EM> a message Deleted, it does not actually
7237 get rid of the message.
7238 The eXpunge command (available from the MESSAGE INDEX screen) actually
7239 removes all of the deleted messages in a folder.
7240 Once a message is eXpunged, it can't be retrieved.
7243 The Delete command is affected by the setting of the configuration feature
7244 <A HREF="h_config_del_skips_del">"<!--#echo var="FEAT_delete-skips-deleted"-->"</A>.
7247 <End of help on this topic>
7250 ======= h_common_postpone =======
7253 <TITLE>Postpone Command</TITLE>
7256 <H1>Postpone Command</H1>
7259 <!--chtml if pinemode="function_key"-->(F11)<!--chtml else-->(^O)<!--chtml endif-->
7260 command allows you to temporarily stop working on the current
7261 message so you may read
7262 other messages or compose another message. When you want to resume a
7263 message later, start to compose and answer "yes" to the
7264 "Continue postponed composition?" question. You may
7265 postpone as many messages as you like.
7268 Note: If a <A HREF="h_config_form_folder"><!--#echo var="VAR_form-letter-folder"--></A> is defined
7269 in the Setup/Config screen, then the Postpone command will prompt you for
7270 the folder in which to store your outgoing message.
7273 <End of help on this topic>
7276 ======= h_compose_cancel =======
7279 <TITLE>Cancel Command</TITLE>
7282 <H1>Cancel Command</H1>
7285 <!--chtml if pinemode="function_key"-->
7291 The Cancel command returns you to Alpine's normal mail processing and
7292 causes the message currently under composition to be thrown out.
7293 The message text <EM>will be lost</EM>.
7296 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
7297 will be preserved in the file named
7298 <!--chtml if pinemode="os_windows"-->
7299 "DEADLETR".
7301 "dead.letter" in your home directory.
7303 If you unintentionally cancel a message, look there for its text.
7306 <End of help on this topic>
7309 ======= h_compose_addrcomplete =======
7312 <TITLE>Address Completion</TITLE>
7315 <H1>Address Completion</H1>
7317 When entering addresses in the address fields of the composer (To, Cc, etc.)
7318 the TAB key may be used to help complete the address.
7319 Type a partial nickname and tap the TAB key to complete the typing.
7320 The unambiguous part of the name will be filled in automatically.
7321 Typing TAB twice in succession will bring up a selection list of possibilities,
7322 making it easy to find and choose the correct address.
7325 The matching algorithm is rather ad hoc.
7326 The search starts with a search of your address book.
7327 It counts as a match if the nickname, address, or fullname field of an
7328 entry begins with the text typed in so far. It is also a match if
7329 a later word in the fullname (for example, the middle name or last name)
7330 begins with the entered text.
7332 Next comes an LDAP search.
7333 The search will happen for any servers that have the
7334 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
7335 feature set. You can set or unset the feature for each server independently
7336 in the Setup/Directory screen.
7338 Finally, if you are replying to or forwarding a message, that message is
7339 searched for likely candidate addresses that match the typed-in text.
7342 <End of help on this topic>
7345 ======= h_compose_richhdr =======
7348 <TITLE>Rich Header Command</TITLE>
7351 <H1>Rich Header Command</H1>
7353 The Rich Header command allows you to toggle between the list of
7354 all message headers available for editing and those that are most
7358 Use this toggle to expose headers that are not normally visible by
7360 This set usually includes the
7364 and "Newsgroups"
7366 If you are posting to a newsgroup the set of defaults is a little different.
7367 Obviously, in that case, the Newsgroups header is of interest so is not
7369 For news posting the hidden set includes the
7374 and "Lcc:"
7376 You won't normally want to edit these, which is why they are hidden,
7377 but it is sometimes useful to be able to set them manually.
7380 The default sets of headers listed above can be altered.
7381 Any header that you have added to the
7382 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
7383 option, but not to the
7384 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
7385 option will appear when you use the Rich Headers command to
7386 make the Rich Headers visible.
7387 (Headers listed in the <!--#echo var="VAR_default-composer-hdrs"--> list will be visible
7388 even without toggling the Rich Headers command.)
7391 <End of help on this topic>
7394 ======= h_compose_send =======
7397 <TITLE>Send Command</TITLE>
7400 <H1>Send Command</H1>
7403 <!--chtml if pinemode="function_key"-->
7408 tells Alpine you are finished composing.
7409 Before actually sending it, though, Alpine will ask you to confirm
7410 your intention, and, at the same time, redisplayed the message text
7411 with the recipients at the top of the screen to give you the opportunity
7412 to review and verify that the message is addressed to the people
7416 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
7417 then this confirmation prompt and any options it allows are skipped.
7420 This confirmation prompt may also offer, depending
7421 on your particular Setup/Config, options allowing you to set
7422 <A HREF="h_config_compose_dsn">delivery status notifications</A>,
7423 include attachments in the "Fcc" (if you had previously
7424 specified that they <A HREF="h_config_no_fcc_attach">exclude attachments</A>,
7425 observe details of the
7426 <A HREF="h_config_verbose_post">message submission process</A>,
7427 choose the filter through which the
7428 <A HREF="h_config_sending_filter">outgoing text should first pass</A>,
7429 or turn of flowed text generation.
7432 <End of help on this topic>
7435 ======= h_compose_markcutpaste =======
7438 <TITLE>Mark, Cut and Paste Commands</TITLE>
7441 <H1>Mark, Cut and Paste Commands</H1>
7443 You can define a "block" of text, which can subsequently
7445 copied as a unit, by setting a mark at the start of the block (Ctrl-^) and
7446 then moving the cursor to the end of the desired text block. You can then
7447 "cut" the block out
7448 <!--chtml if pinemode="function_key"-->
7453 move the cursor, and "paste" it
7454 <!--chtml if pinemode="function_key"-->
7459 in the new location. Also, you can paste more than once, allowing you
7460 to use this feature to copy a block of text.<P>
7463 <!--chtml if pinemode="function_key"-->
7468 without having marked anything, Alpine will delete
7469 a single line. If you delete a group of lines together, Alpine keeps them
7470 in the same buffer, so
7471 <!--chtml if pinemode="function_key"-->
7476 will restore them as a block. About
7477 terminology: Mark is shown as "^^". The first "^" means you should
7478 hold down the "Control" key on your keyboard. The second "^" means
7479 "type the character ^".
7482 <End of help on this topic>
7485 ======= h_compose_justify =======
7488 <TITLE>Justify Command</TITLE>
7491 <H1>Justify Command</H1>
7494 <!--chtml if pinemode="function_key"-->
7499 command reformats the text in the paragraph the cursor is in.
7500 Paragraphs are separated by one blank line or a line beginning with a space.
7501 This is useful when you have been editing a paragraph and the lines become
7502 uneven. The text is left aligned or justified and the right is ragged. If
7503 the text is already justified as typed with auto-wrap, no justification will
7507 If you have set a <A HREF="h_compose_markcutpaste">mark</A> to select a
7508 block of text, the Justify command is modified.
7509 Instead of automatically justifying the current paragraph you will be
7510 asked if you want to justify the paragraph, justify the selected region,
7511 or adjust the quote level of the selected region.
7512 Adjusting the quote level only works if you are using standard
7513 "> " or ">" quotes, which is the default if you haven't
7514 changed "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>".
7517 When composing a reply containing included text, the justify command
7518 will reformat text to the right of the
7519 "<A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>",
7520 adding or removing indented lines as needed. Paragraphs are separated
7521 by a blank line, a line containing only the <!--#echo var="VAR_reply-indent-string"-->, or a
7522 line containing the indent string and one or more blank spaces.
7523 Included text that was previously indented (or "quoted") is
7527 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
7528 in 1999 and its wide-spread adoption since then, you will usually be better off if you
7530 "> " or ">" quotes.
7533 <End of help on this topic>
7536 ======= h_compose_spell =======
7539 <TITLE>Spell Check Command</TITLE>
7542 <H1>Spell Check Command</H1>
7544 The "To Spell"
7545 <!--chtml if pinemode="function_key"-->
7550 command calls an external spell checking program to look over the
7551 message you are composing. By default, Alpine uses
7553 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
7555 if it knows where to find "aspell".
7556 If there is no "aspell" command available but the command "ispell" is available
7557 then the command used is
7559 <CENTER><SAMP>ispell -l</SAMP></CENTER>
7561 Otherwise, the ancient "spell" command is used.
7563 For PC-Alpine, you must install the aspell library code that you
7565 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
7568 <End of help on this topic>
7571 ======= h_compose_alted =======
7574 <TITLE>Alt Editor Command</TITLE>
7577 <H1>Alt Editor Command</H1>
7579 The "Alt Editor" command's availability depends on the
7580 Setup/Config variable "<A HREF="h_config_editor"><!--#echo var="VAR_editor"--></A>".
7583 When the variable specifies a valid editor on your system, this
7584 command will launch it with the current text of your message
7588 <End of help on this topic>
7591 ======= h_compose_readfile =======
7594 <TITLE>Read File Command</TITLE>
7597 <H1>Read File Command</H1>
7599 The "Read File"
7600 <!--chtml if pinemode="function_key"-->
7605 command allows you to copy in text from an existing file. You will be
7606 prompted for the name of a file to be inserted into the message. The file
7607 name is relative to your home directory
7608 <!--chtml if pinemode="running"-->
7609 (which, in the present configuration of your system, is
7610 "<!--#echo var="HOME_DIR"-->")
7612 or current working directory
7613 <!--chtml if pinemode="running"-->
7614 (which, at least for your current Alpine "session,"
7615 is "<!--#echo var="CURRENT_DIR"-->")
7616 <!--chtml endif-->, depending on the
7617 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
7618 configuration setting; or, the file name must be specified as a full path name
7619 <!--chtml if pinemode="os_windows"-->
7620 -- for example: "A:\PAPER.TXT"
7622 -- for example: "/tmp/wisdom-of-the-day"
7624 (without the quotation marks).
7627 The file will be inserted where the cursor is located. <B>The
7628 file to be read must be on the same system as Alpine.</B> If you use Alpine on a
7629 Unix machine but have files on a PC or Mac, the files must be transferred
7630 to the system Alpine is running on before they can be read. Please ask your
7631 local computer support people about the correct way to transfer a file to
7635 <End of help on this topic>
7638 ======= h_config_tray_icon =======
7641 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></TITLE>
7644 <H1>FEATURE: <!--#echo var="FEAT_enable-tray-icon"--></H1>
7648 This option restores a behavior of previous versions of PC-Alpine.
7650 versions, when started, installed a PC-Alpine icon in the notification
7651 tray of Window's Taskbar. The primary use of this icon was to indicate
7652 new mail arrival by turning red (while the Taskbar icon remained green).
7653 Additionally, the icon now changes to yellow to signify that a mail folder
7654 has been closed unexpectedly.
7657 Rather than add another icon to the Taskbar, this version of PC-Alpine will
7658 color its Taskbar entry's icon red (as well as the icon in the Window
7659 Title). This feature is only provided for backwards compatibility.
7662 <End of help on this topic>
7665 ======= h_common_suspend =======
7668 <TITLE>Suspend Command</TITLE>
7671 <H1>Suspend Command</H1>
7673 With the <A HREF="h_config_can_suspend"><!--#echo var="FEAT_enable-suspend"--></A> feature
7674 enabled, you can, at almost any time, temporarily halt your Alpine session,
7675 <!--chtml if pinemode="os_windows"-->
7676 minimizing it into an icon.
7678 and return to your system prompt.
7682 <End of help on this topic>
7685 ======= h_pipe_command =======
7688 <TITLE>Pipe Command SubOptions</TITLE>
7691 <H1>Pipe Command SubOptions</H1>
7693 By default, when you use the Pipe command, the processed text of the
7694 message is sent to the Unix command
7695 you specify and the output is captured by Alpine and shown to you.
7696 (This command is available in PC-Alpine, as well, but there aren't many
7697 Windows commands that work well with piping.)
7698 There are some sub-commands that may be used to alter this behavior.
7699 These are toggles that switch the behavior between two possibilities.
7700 They can be combined in any way you wish.
7702 By default, the prompt at the bottom of the screen looks like
7704 <CENTER><SAMP>Pipe message 37 to :</SAMP></CENTER>
7708 <CENTER><SAMP>Pipe messages to :</SAMP></CENTER>
7710 if you are piping more than one message.
7712 The sub-command options are:
7714 <DT>Shown Text or Raw Text</DT>
7715 <DD>This option toggles between sending the shown (processed) text
7716 of the message to the Unix command, and sending the
7717 raw (unprocessed) text of the message to the Unix command.
7718 The default is to send the shown text.
7719 The raw version of the message will contain all of the headers and any
7720 MIME encoding that the message contains.
7721 If you've selected the Raw Text then the prompt will have the additional word
7722 "RAW" in it, like
7724 <CENTER><SAMP>Pipe RAW messages to :</SAMP></CENTER>
7726 You can experiment with this option by piping to something simple like the
7727 Unix "cat" command.
7729 <DT>Captured Output or Free Output</DT>
7730 <DD>This option toggles between having Alpine capture the output of
7731 the Unix pipe command for display, and not capturing it.
7732 If the command you are piping to is a filter that will produce output
7733 you want to view, then you want to capture that output
7734 for display (the default).
7735 If the Unix command doesn't produce output or handles the display itself,
7736 then you want free output.
7737 When you've selected the Free Output option the prompt will change to
7739 <CENTER><SAMP>Pipe messages to (uncaptured) :</SAMP></CENTER>
7742 <DT>No Delimiter or With Delimiter</DT>
7743 <DD>This option controls whether or not a Unix mailbox style delimiter
7744 will come before the text of the message.
7745 This is the delimiter used in the common Unix mailbox format.
7746 It's the single line that begins with the five characters
7747 "From" followed by a <SPACE> character.
7748 You'll usually only want to include this if the Unix command requires
7749 input in the format of a traditional Unix mailbox file.
7750 When you've selected the With Delimiter option the prompt will change to
7752 <CENTER><SAMP>Pipe messages to (delimited) :</SAMP></CENTER>
7755 <DT>To Same Pipe or To Individual Pipes</DT>
7756 <DD>This option only shows up if you are running an aggregate
7758 That is, the command was Apply Pipe, not just Pipe.
7759 You have the option of piping all of the selected messages through a
7760 single pipe to a single instance of the Unix command,
7761 or piping each individual message through a separate pipe to separate
7762 instances of the Unix command.
7763 The default is that all of the output will go through a single pipe
7764 to a single instance of the command.
7765 You can try this option with a command like "less", with Free
7767 When you've selected the Individual Pipes option the prompt will change to
7769 <CENTER><SAMP>Pipe messages to (new pipe) :</SAMP></CENTER>
7775 As mentioned earlier, the options can be combined in any way you wish.
7776 You may leave them all off, turn them all on, or turn some of them on
7777 and some of them off.
7778 If you use the pipe command a second time in the same session the default
7779 options will be what you used the last time.
7782 <End of help on this topic>
7785 ========== h_emptydir_subfolder_name =========
7788 <TITLE>ENTER SUBFOLDER NAME</TITLE>
7791 <H1>Enter Subfolder Name</H1>
7794 This is the name of a new subfolder in the directory you are creating.
7795 Because empty directories are hidden and therefore not useful, you must also
7796 create a subfolder in the directory you are creating in order that the
7797 directory remains visible.
7799 Alternatively, you may turn off the configuration feature
7800 <A HREF="h_config_quell_empty_dirs"><!--#echo var="FEAT_quell-empty-directories"--></A>
7801 so that empty directories remain visible.
7802 If you do that, you will not be required to create the subfolder when you
7806 <End of help on this topic>
7809 ========== h_incoming_add_folder_name =========
7812 <TITLE>ENTER FOLDER NAME</TITLE>
7815 <H1>Enter Folder Name</H1>
7818 This is the name of the folder on the previously specified server.
7819 By default the folder name is interpreted as defining a section of your personal
7820 folder area. This area and how you specify it are defined by the
7821 server, if one is specified.
7824 To define a folder outside the default area, prefix
7825 the path with the namespace to use when interpreting the
7826 given path. If a namespace is specified, the folder name begins with the
7827 sharp (#) character followed by the name of the namespace
7828 and then the namespace's path-element-delimiter. Aside from the
7829 name's format, namespaces can also imply access rights, content
7830 policy, audience, location, and, occasionally, access methods.
7833 Each server exports its own set (possibly of size one) of
7835 For a more detailed explanation read about
7836 <A HREF="h_folder_name_namespaces">Namespaces</A>.
7839 To specify the default for INBOX on the server you can usually just enter
7840 "INBOX", and the server will understand the special meaning of
7844 <End of help on this topic>
7847 ========== h_incoming_add_folder_host =========
7850 <TITLE>ENTER INCOMING FOLDER SERVER</TITLE>
7853 <H1>Enter Incoming Folder Server</H1>
7855 You are being asked for the name of the server for use with this incoming
7857 If the folder is on the machine where Alpine is running, then just enter
7858 RETURN without typing a server name.
7861 If the folder is on an IMAP server then type the server's name followed
7863 You may use the ^X command if the server is the same as the server that
7867 You may have to add optional extra information to the server name.
7868 For example, if the IMAP server is using a non-standard port number you
7869 would specify that by appending a colon (:) followed by the port number
7873 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7876 or you may need to specify a different protocol if the server is not an
7877 IMAP server. For example:
7880 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7886 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
7889 for an NNTP news server.
7890 For an explanation of all of the possibilities, see
7891 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7895 There is a special command (^W) if you want to set up a folder that gets its
7897 <A HREF="h_maildrop">Mail Drop</A>.
7898 If you type that command, you will be prompted for the information for
7899 both the Mail Drop folder and the destination folder.
7902 <End of help on this topic>
7905 ========== h_incoming_add_inbox =========
7908 <TITLE>ENTER INBOX SERVER</TITLE>
7911 <H1>Enter INBOX Server</H1>
7913 You are being asked for the name of the server for use with
7915 Type the server's name followed by RETURN.
7918 You may have to add optional extra information to the server name.
7919 For example, if the server is using a non-standard port number you
7920 would specify that by appending a colon (:) followed by the port number
7924 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7927 or you may need to specify a different protocol if the server is not an
7928 IMAP server. For example:
7931 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
7937 For an explanation of all of the possibilities, see
7938 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7942 If the INBOX folder is on the machine where Alpine is running, then just enter
7943 RETURN without typing a server name.
7946 There is a special command (^W) if you want to set up a folder that gets its
7948 <A HREF="h_maildrop">Mail Drop</A>.
7949 If you type that command, you will be prompted for the information for
7950 both the Mail Drop folder and the destination folder, which will be used
7951 as your INBOX folder.
7954 <End of help on this topic>
7957 ========== h_incoming_add_maildrop_destn =========
7960 <TITLE>ENTER DESTINATION SERVER</TITLE>
7963 <H1>Enter Destination Server</H1>
7965 You are being asked for the name of the server where the destination
7966 folder is for use with this Mail Drop incoming folder.
7967 That is, you are using a Mail Drop for this incoming folder and
7968 you've already entered
7969 the server and folder name for the Mail Drop.
7970 Now you need to enter the server for the destination folder
7971 where the mail should be copied to.
7972 Mail will come from the Mail Drop and be copied to the destination folder.
7975 Type the server's name followed by RETURN.
7976 If the folder is local to this computer, just type RETURN without entering
7980 You may have to add optional extra information to the server name.
7981 For example, if the server is using a non-standard port number you
7982 would specify that by appending a colon (:) followed by the port number
7986 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
7989 For an explanation of all of the possibilities, see
7990 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
7994 <End of help on this topic>
7997 ========== h_inbox_add_maildrop_destn =========
8000 <TITLE>ENTER DESTINATION SERVER</TITLE>
8003 <H1>Enter Destination Server</H1>
8005 You are being asked for the name of the server where the destination
8006 folder is for use with your Mail Drop INBOX.
8007 That is, you are using a Mail Drop for your INBOX and you've already entered
8008 the server and folder name for the Mail Drop.
8009 Now you need to enter the server for the destination folder
8010 where the mail should be copied to.
8011 Mail will come from the Mail Drop and be copied to the destination folder.
8014 Type the server's name followed by RETURN.
8015 If the folder is local to this computer, just type RETURN without entering
8019 You may have to add optional extra information to the server name.
8020 For example, if the server is using a non-standard port number you
8021 would specify that by appending a colon (:) followed by the port number
8025 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8028 For an explanation of all of the possibilities, see
8029 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8033 <End of help on this topic>
8036 ========== h_inbox_add_maildrop =========
8039 <TITLE>ENTER MAILDROP SERVER</TITLE>
8042 <H1>Enter Mail Drop Server</H1>
8044 You are being asked for the name of the Mail Drop server for use with
8048 Type the server's name followed by RETURN.
8051 You may have to add optional extra information to the server name.
8052 For example, if the server is using a non-standard port number you
8053 would specify that by appending a colon (:) followed by the port number
8057 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8060 or you may need to specify a different protocol if the server is not an
8061 IMAP server. For example:
8064 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
8070 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
8073 for an NNTP news server.
8074 For an explanation of all of the possibilities, see
8075 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8079 <End of help on this topic>
8082 ========== h_incoming_add_maildrop =========
8085 <TITLE>ENTER MAILDROP SERVER</TITLE>
8088 <H1>Enter Mail Drop Server</H1>
8090 You are being asked for the name of the Mail Drop server for use with
8091 this incoming folder.
8094 Type the server's name followed by RETURN.
8095 You may use the ^X command if the server is the same as the server that
8099 You may have to add optional extra information to the server name.
8100 For example, if the server is using a non-standard port number you
8101 would specify that by appending a colon (:) followed by the port number
8105 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
8108 or you may need to specify a different protocol if the server is not an
8109 IMAP server. For example:
8112 <CENTER><SAMP>foo.example.com/pop3</SAMP></CENTER>
8118 <CENTER><SAMP>foo.example.com/nntp</SAMP></CENTER>
8121 for an NNTP news server.
8122 For an explanation of all of the possibilities, see
8123 <A HREF="h_folder_server_syntax">Server Name Syntax</A>
8127 If the Mail Drop folder is on the machine where Alpine is running, then just enter
8128 RETURN without typing a server name.
8131 <End of help on this topic>
8134 ========== h_maildrop =========
8137 <TITLE>WHAT IS A MAIL DROP?</TITLE>
8140 <H1>What is a Mail Drop?</H1>
8142 In some situaions it may make sense to have your mail delivered to one
8143 folder (the Mail Drop) and then when you want to read mail that has been
8144 delivered to the Mail Drop folder Alpine will move it to another
8146 Often the Mail Drop will be a remote folder and messages will be moved from
8147 there to a local destination folder.
8150 One example where this might make sense is if the Mail Drop folder is accessible
8151 only with the POP protocol.
8152 You could designate your POP inbox as the Mail Drop folder and have Alpine move
8153 mail from there to a local (on the same machine Alpine is running on)
8154 destination folder, where you'll read it.
8157 A Mail Drop may only be used as your Inbox or as an
8158 <A HREF="h_config_enable_incoming">"Incoming folder"</A>.
8161 There is no attempt to synchronize the contents of the destination folder
8162 with the contents of the Mail Drop folder.
8163 All that happens is that all of the messages in the Mail Drop folder are
8164 copied to the destination folder and then they are deleted and expunged (if possible)
8165 from the Mail Drop folder.
8166 The next time a check for new mail is made, any messages in the Mail
8167 Drop folder are once again copied to the destination folder and deleted
8168 and expunged from the Mail Drop folder.
8169 (If the Mail Drop folder is a news group, then the messages can't be
8170 expunged from the newsgroup. Instead, only Recent messages are copied from
8171 the newsgroup to the destination folder.)
8174 Configuration of a Mail Drop is a little different from configuration of
8175 a folder that does not use a Mail Drop because you have to specify two
8176 folder names instead of one.
8177 The two folders may be any types of folders that Alpine can normally use.
8178 They don't have to be a remote folder and a local folder, that is
8179 simply the most common usage.
8180 When you use a Mail Drop folder Alpine will periodically re-open the Mail
8181 Drop to check for new mail.
8182 The new-mail checks will happen at the frequency set with the
8183 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option,
8184 but with a minimum time
8185 (<A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>)
8187 Because of this minimum you may notice that new mail does not
8188 appear promptly when you expect it.
8189 The reason for this is to protect the server from over-zealous opening and
8190 closing of the Mail Drop folder.
8191 If the user initiates the check by typing ^L (Ctrl-L) or the Next command when at
8192 the end of the folder index, then the check will happen, regardless of how
8193 long it has been since the previous check.
8195 If there is new mail, that mail will be copied to the destination folder
8196 and then will be deleted from the Mail Drop.
8197 Note that using a Mail Drop with a local destination folder does not make
8198 sense if you read mail from more than one machine, because the mail is
8199 downloaded to the destination folder (which is accessible from only one
8200 machine) and deleted from the Mail Drop.
8202 The feature <A HREF="h_config_maildrops_preserve_state"><!--#echo var="FEAT_maildrops-preserve-state"--></A> modifies the operation of Mail Drops.
8205 The actual syntax used by Alpine for a folder that uses a Mail Drop is:
8208 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
8210 The brackets are not literal.
8212 <CENTER><SAMP><DELIM></SAMP></CENTER>
8214 is a single character that does not appear in the MailDropFolder name.
8215 If the name doesn't contain spaces then it can be a space character.
8216 The two folder names are full technical
8217 <A HREF="h_valid_folder_names">folder names</A>
8219 Here are a couple examples to give you an idea what is being talked about:
8222 <CENTER><SAMP>#move {popserver.example.com/pop3}inbox localfolder</SAMP></CENTER>
8224 <CENTER><SAMP>#move+{nntpserver.example.com/nntp}#news.comp.mail.pine+local folder</SAMP></CENTER>
8227 A #move folder may only be used as an
8228 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
8230 When you are in the FOLDER LIST of Incoming Message Folders (after turning
8232 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8234 the Add command has a subcommand "Use Mail Drop"
8235 which may be helpful for defining the folder in your Alpine configuration.
8236 The same is true when you edit the
8237 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
8238 option in Setup/Config.
8239 Each of these configuration methods will also create the DestinationFolder
8240 if it doesn't already exist.
8241 If you are having problems, make sure the DestinationFolder exists.
8244 <End of help on this topic>
8247 ========== h_save =========
8250 <TITLE>CHOOSE A FOLDER TO SAVE INTO</TITLE>
8253 <H1>Choose a Folder to Save Into</H1>
8255 After Exiting from this help text,
8256 type the name of the folder you want to save into and press RETURN.
8258 Press ^T to get a list of your folders to choose from.
8259 Press ^C to cancel the Save.
8261 If you have Folder Collections defined you may use
8262 Ctrl-P (Previous collection) and Ctrl-N (Next collection) to switch
8263 the collection being saved to.
8265 If Tab Completion is enabled (it is enabled by default)
8266 you may type a Tab character to have Alpine complete the folder name for you.
8268 If Partial Match Lists is enabled (it is enabled by default) you may type
8269 Ctrl-X to get a list of matches to the prefix you've typed in so far.
8271 If the Ctrl-R subcommand is present that means you can decide to Delete or
8272 not Delete the message you are saving after you save it.
8273 The label on that key gives the action to switch to.
8274 If it says Delete and you type Ctrl-R the label displayed will change to
8275 No Delete and the source message will be deleted after the save. If it
8276 says No Delete and you type Ctrl-R the label displayed will change to
8277 Delete and the message will not be deleted.
8278 You can control the default for the Delete parameter with the
8279 configuration feature <!--#echo var="FEAT_save-will-not-delete"-->.
8281 Similarly, if the Ctrl-W subcommand is present that means you can decide
8282 to Preserve the order of the messages being saved or not.
8283 If it is labeled Preserve Order and you type Ctrl-W, the resulting Saved messages
8284 will be in the same order as you see them in the source folder now.
8285 The opposite action (which is usually the default) is that you don't care
8287 The Saved messages may or may not be in the same order in the destination folder.
8288 There may be a performance penalty for choosing to save the messages in order.
8289 You can control the default for the Preserve Order parameter with the
8290 configuration feature
8291 <!--#echo var="FEAT_save-aggregates-copy-sequence"-->.
8294 If you haven't disabled the Save Input History and you've already done a
8295 Save earlier in this session then you may use the Up and Down arrows to retrieve
8296 a folder name used in a previous Save.
8299 <End of help on this topic>
8302 ============= h_simple_index ========================
8305 <TITLE>SELECT POSTPONED MESSAGE</TITLE>
8308 <H1>POSTPONED MESSAGE SELECTION COMMANDS</H1>
8309 <!--chtml if pinemode="function_key"-->
8311 Navigating the List of Messages General Alpine Commands
8312 ------------------------------- -----------------------
8313 F5 Move to previous message F1 Show this help text
8314 F6 Move to next message
8315 F7 Show previous screen of messages
8316 F8 Show next screen of messages
8318 Message Selection Commands
8319 --------------------------
8320 F3 Exit the Message Select menu (canceling Send command)
8321 F4 Select the currently highlighted message
8322 F9 Mark the currently highlighted message as deleted
8323 F10 Undelete (remove deletion mark from) the highlighted message
8327 Navigating the List of Messages General Alpine Commands
8328 ------------------------------- -----------------------
8329 P Move to previous message ? Show this help text
8330 N Move to next message
8331 - Show previous screen of messages
8332 Spc (space bar) Show next screen of messages
8334 Message Selection Commands
8335 --------------------------
8336 E Exit the Message Select menu (canceling Send command)
8337 S Select the currently highlighted message
8338 D Mark the currently highlighted message as deleted
8339 U Undelete (remove deletion mark from) the highlighted message
8343 <H2>Description of the Select Postponed Message Screen</H2>
8345 This screen allows you to select one of several previously postponed
8346 messages in order to continue composition. Your options are very limited
8347 -- the screen is not meant to let you manipulate these messages. However,
8348 you may now delete messages from this list. Once you choose a message,
8349 Alpine reads it in and puts you into the regular message composer.
8352 Messages do not stay in this postponed state automatically. If you select
8353 a message and then want to postpone it again, use the normal postpone
8354 (Ctrl-O) command in the composer.
8357 If you exit this screen without selecting a message, the Compose command
8358 that got you here is canceled. Other than messages explicitly marked
8359 "Deleted", no messages will be removed.
8362 <End of help on this topic>
8365 ============= h_collection_screen ========================
8368 <TITLE>COLLECTION LIST screen</TITLE>
8371 <H1>COLLECTION LIST screen</H1>
8373 The COLLECTION LIST screen is used to select one of your
8374 collection definitions to display the folders they contain. See
8375 <A HREF="h_what_are_collections">Folder Collections Explained</A> for
8376 detailed explanation of collections.<P>
8378 To manage your collection definitions (Add, Change, Delete, etc.), use
8379 the <A HREF="h_collection_maint">Setup/collectionList</A> command on Alpine's
8383 <End of help on this topic>
8386 ============= h_collection_maint ========================
8389 <TITLE>SETUP COLLECTION LIST screen</TITLE>
8392 <H1>SETUP COLLECTION LIST screen</H1>
8394 The SETUP COLLECTION LIST screen lets you manage your collection
8396 <A HREF="h_what_are_collections">Folder Collections Explained</A>
8397 for detailed explanation of collections.<P>
8399 Maintenance commands include:
8402 <!--chtml if pinemode="function_key"-->
8409 <DD>Modify attributes of the selected collection definition.
8412 <!--chtml if pinemode="function_key"-->
8419 <DD>Create a new collection definition.
8423 <!--chtml if pinemode="function_key"-->
8430 <DD>Delete the selected collection definition.<BR>
8431 NOTE: The folders and directories referred to by the
8432 collection definition are <EM>NOT</EM> deleted. Folders must
8433 be deleted, if that's what you wish to do, from the
8434 <A HREF="h_folder_maint">FOLDER LIST screen</A>, which shows the
8435 individual folders in a collection.
8439 <!--chtml if pinemode="function_key"-->
8446 <DD>Change the order of the displayed collections. Alpine will offer
8447 to move the currently selected collection one position UP
8453 <End of help on this topic>
8456 ============ h_what_are_collections ==========
8459 <TITLE>Folder Collections Explained</TITLE>
8462 <H1>Folder Collections Explained</H1>
8465 Those of you with simple mail configurations will just see a list of all the
8466 folders you have when choosing FOLDER LIST from Alpine's MAIN MENU.
8467 The special folders for INBOX, sent mail and saved messages
8468 will appear at the top of the list. All others are in alphabetical order.
8471 or your system administrator have defined more than one collection or if
8472 you have a collection (for newsgroups or email folders) defined on your
8473 system, then you will see the COLLECTION LIST screen first when choosing
8474 FOLDER LIST from Alpine's MAIN MENU.
8476 <H2>Why have multiple folder collections?</H2>
8478 For Alpine users who only maintain email folders (and not too many) on one host,
8479 a single folder collection is probably sufficient.<P>
8481 However, people who have more than one email account - for example, one
8482 at their university, and one with their personal Internet Service Provider -
8483 will have different sets of folders on different hosts, and they may want to
8484 access them all from the same installation of Alpine, rather than use different
8485 software and/or log into other hosts to manipulate messages in different
8486 accounts. (If in doubt whether one of your email accounts can be accessed
8487 with Alpine, contact the technical support people for that account.) Even people
8488 who have only one email account on one host, but have dozens or
8489 hundreds of email folders, may want to arrange these folders together in a
8491 That is where multiple collections come in.
8493 <H2>Types of Collections</H2>
8495 <DT>INCOMING FOLDERS</DT>
8496 <DD>"Incoming Message Folders"
8497 is a special collection typically used to supplement your single INBOX.
8498 All the folders here are meant to be ones that receive incoming messages,
8499 which you intend to check more or less frequently.
8500 You may have multiple folders like this because you or your systems
8501 administrator have set up an external program or you may have set up
8502 Alpine to filter incoming
8503 messages into different folders, based on certain criteria such as
8504 sender, recipient, or subject; or because you have multiple accounts and
8505 wish to check their INBOXes easily. This collection is established by
8507 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
8508 feature in the SETUP CONFIGURATION screen, which is accessed from the
8513 <DD>You can also define a collection specifically for
8514 newsgroups. Alpine does this for you implicitly when you
8515 <A HREF="h_config_nntp_server">define an NNTP Server</A>
8516 in your Alpine configuration. The news collection appears last in the
8517 COLLECTION LIST (though you can shuffle it up in the order of presentation),
8518 and Alpine knows not to save messages there.
8521 <DT>DEFAULT COLLECTION</DT>
8522 <DD>This is the default collection for your saved and sent messages folders.
8528 <H2>Defining Collections</H2>
8530 In the absence of any folder-collection definitions, Alpine will assume a
8531 single default folder collection.
8532 <!--chtml if pinemode="os_windows"-->
8534 If necessary, Alpine will create the directory
8535 "mail" in your Unix home directory
8536 to hold your folders.
8540 <A HREF="h_collection_maint">Setup/collectionList screen</A>, called up from
8541 the MAIN MENU, to manage your collection list.
8543 <End of help on this topic>
8546 ===== h_select_address_screen =====
8549 <TITLE>SELECT AN ADDRESS SCREEN</TITLE>
8552 <H1>SELECT AN ADDRESS SCREEN</H1>
8554 <!--chtml if pinemode="function_key"-->
8557 -------------------------------
8559 F3 Exit without selecting anything
8560 F4 Select the highlighted address
8561 F5 Move highlight to previous address
8562 F6 Move highlight to next address
8563 F7 Previous page of addresses
8564 F8 Next page of addresses
8570 Navigation General Alpine Commands
8571 ------------------------- -----------------------
8572 P Prev Address ? Display this help text
8573 N Next Address E Exit without selecting anything
8574 - Previous page % Print
8575 Spc (space bar) Next page
8579 ------------------------------------------------
8580 S Select the highlighted address
8584 <H2>Description of the Select Address Screen</H2>
8586 This screen gives you an easy way to select an address from all of
8587 the address book entries that match the prefix typed so far.
8590 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8593 <End of help on this topic>
8596 ===== h_select_rule_screen =====
8599 <TITLE>SELECT A RULE SCREEN</TITLE>
8602 <H1>SELECT A RULE SCREEN</H1>
8604 <!--chtml if pinemode="function_key"-->
8607 -------------------------------
8609 F3 Exit without selecting anything
8610 F4 Select the highlighted rule
8611 F5 Move highlight to previous rule
8612 F6 Move highlight to next rule
8613 F7 Previous page of rules
8614 F8 Next page of rules
8620 Navigation General Alpine Commands
8621 ------------------------- -----------------------
8622 P Prev Rule ? Display this help text
8623 N Next Rule E Exit without selecting anything
8624 - Previous page % Print
8625 Spc (space bar) Next page
8629 ------------------------------------------------
8630 S Select the highlighted rule
8634 <H2>Description of the Select Rule Screen</H2>
8636 This screen just gives you an easy way to select a rule from all of your
8638 The list of rules presented is the list of nicknames of all of the rules
8639 defined using Setup/Rules.
8640 For selecting messages, it is likely that the Indexcolor rules and possibly
8641 the Roles rules will be most useful.
8642 The others are there also, in case you find a use for them.
8644 In order for this to be useful for selecting messages, the nicknames of
8645 the rules have to be different.
8646 Alpine actually just gets the nickname of the rule that you select and then
8647 looks up that rule using the nickname.
8648 So if there are duplicate nicknames, the first rule that has that
8649 nickname will be used.
8652 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8655 <End of help on this topic>
8658 ===== h_select_priority_screen =====
8661 <TITLE>SELECT A PRIORITY SCREEN</TITLE>
8664 <H1>SELECT A PRIORITY SCREEN</H1>
8666 <!--chtml if pinemode="function_key"-->
8669 -------------------------------
8671 F3 Exit without selecting anything
8672 F4 Select the highlighted priority
8673 F5 Move highlight to previous priority
8674 F6 Move highlight to next priority
8675 F7 Previous page of priorities
8676 F8 Next page of priorities
8682 Navigation General Alpine Commands
8683 ------------------------- -----------------------
8684 P Prev Priority ? Display this help text
8685 N Next Priority E Exit without selecting anything
8686 - Previous page % Print
8687 Spc (space bar) Next page
8691 ------------------------------------------------
8692 S Select the highlighted priority
8696 <H2>Description of the Select Priority Screen</H2>
8698 This screen gives you a way to select a priority for the message you are sending.
8699 This priority will be placed in the non-standard X-Priority header of your outgoing mail.
8700 Some mail programs will display an indication of the priority level to
8701 the recipient of the message, some will ignore it.
8702 Even in cases where the mail programs of both the sender and the recipient
8703 agree on the meaning of this header, keep in mind that it is
8704 something that the sender sets so it is only an indication
8705 of the priority that the sender attaches to the mail.
8706 Alpine can be made to display an indication of this priority in incoming
8707 messages by use of one of the tokens
8708 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
8709 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
8710 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
8713 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8716 <End of help on this topic>
8719 ===== h_select_keyword_screen =====
8722 <TITLE>SELECT A KEYWORD SCREEN</TITLE>
8725 <H1>SELECT A KEYWORD SCREEN</H1>
8727 <!--chtml if pinemode="function_key"-->
8730 -------------------------------
8732 F3 Exit without selecting anything
8733 F4 Select the highlighted keyword
8734 F5 Move highlight to previous keyword
8735 F6 Move highlight to next keyword
8736 F7 Previous page of keywords
8737 F8 Next page of keywords
8743 Navigation General Alpine Commands
8744 ------------------------- -----------------------
8745 P Prev Keyword ? Display this help text
8746 N Next Keyword E Exit without selecting anything
8747 - Previous page % Print
8748 Spc (space bar) Next page
8752 ------------------------------------------------
8753 S Select the highlighted keyword
8757 <H2>Description of the Select Keyword Screen</H2>
8759 This screen just gives you an easy way to select a keyword.
8760 The list of keywords presented is the list of all keywords defined in your
8761 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8762 If you have given a keyword a nickname, that nickname is displayed
8763 instead of the actual keyword.
8766 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8769 <End of help on this topic>
8772 ===== h_select_charset_screen =====
8775 <TITLE>SELECT A CHARACTER SET SCREEN</TITLE>
8778 <H1>SELECT A CHARACTER SET SCREEN</H1>
8780 <!--chtml if pinemode="function_key"-->
8783 -------------------------------
8785 F3 Exit without selecting anything
8786 F4 Select the highlighted character set
8787 F5 Move highlight to previous character set
8788 F6 Move highlight to next character set
8789 F7 Previous page of character sets
8790 F8 Next page of character sets
8796 Navigation General Alpine Commands
8797 ------------------------- -----------------------
8798 P Prev Character Set ? Display this help text
8799 N Next Character Set E Exit without selecting anything
8800 - Previous page % Print
8801 Spc (space bar) Next page
8805 ------------------------------------------------
8806 S Select the highlighted character set
8810 <H2>Description of the Select A Character Set Screen</H2>
8812 This screen just gives you an easy way to select a character set from the
8813 set of character sets Alpine knows about.
8814 The list presented will vary slightly depending on what option you are
8815 selecting the character set for.
8818 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8821 <End of help on this topic>
8824 ===== h_select_multcharsets_screen =====
8827 <TITLE>SELECT CHARACTER SETS SCREEN</TITLE>
8830 <H1>SELECT CHARACTER SETS SCREEN</H1>
8832 <!--chtml if pinemode="function_key"-->
8835 -------------------------------
8837 F3 Exit without selecting anything
8838 F4 Select the highlighted charset (or chosen charsets in ListMode)
8839 F5 Move highlight to previous charset
8840 F6 Move highlight to next charset
8841 F7 Previous page of charsets
8842 F8 Next page of charsets
8843 F9 Toggle choices when using ListMode
8844 F10 Turn on/off ListMode (makes it easy to choose multiple charsets)
8850 Navigation General Alpine Commands
8851 ------------------------- -----------------------
8852 P Prev Charset ? Display this help text
8853 N Next Charset E Exit without selecting anything
8854 - Previous page % Print
8855 Spc (space bar) Next page
8859 ------------------------------------------------
8860 S Select the highlighted charset (or chosen charsets in ListMode)
8861 L Turn on ListMode (makes it easy to choose multiple charsets)
8863 X Toggle choices when using ListMode
8867 <H2>Description of the Select Character Set Screen</H2>
8869 This screen just gives you an easy way to select a character set or a list of
8871 The list of character sets presented is the list of all character sets known to
8873 You may select other character sets by typing them in directly.
8876 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8879 <End of help on this topic>
8882 ===== h_select_multkeyword_screen =====
8885 <TITLE>SELECT KEYWORDS SCREEN</TITLE>
8888 <H1>SELECT KEYWORDS SCREEN</H1>
8890 <!--chtml if pinemode="function_key"-->
8893 -------------------------------
8895 F3 Exit without selecting anything
8896 F4 Select the highlighted keyword (or chosen keywords in ListMode)
8897 F5 Move highlight to previous keyword
8898 F6 Move highlight to next keyword
8899 F7 Previous page of keywords
8900 F8 Next page of keywords
8901 F9 Toggle choices when using ListMode
8902 F10 Turn on/off ListMode (makes it easy to choose multiple keywords)
8908 Navigation General Alpine Commands
8909 ------------------------- -----------------------
8910 P Prev Keyword ? Display this help text
8911 N Next Keyword E Exit without selecting anything
8912 - Previous page % Print
8913 Spc (space bar) Next page
8917 ------------------------------------------------
8918 S Select the highlighted keyword (or chosen keywords in ListMode)
8919 L Turn on ListMode (makes it easy to choose multiple keywords)
8921 X Toggle choices when using ListMode
8925 <H2>Description of the Select Keyword Screen</H2>
8927 This screen just gives you an easy way to select a keyword or a list of
8929 The list of keywords presented is the list of all keywords defined in your
8930 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option.
8931 If you have given a keyword a nickname, that nickname is displayed
8932 instead of the actual keyword.
8935 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
8938 <End of help on this topic>
8941 ===== h_select_incoming_to_monitor =====
8944 <TITLE>SELECT FOLDERS TO CHECK SCREEN</TITLE>
8947 <H1>SELECT FOLDERS TO CHECK SCREEN</H1>
8949 <!--chtml if pinemode="function_key"-->
8952 -------------------------------
8954 F3 Exit without selecting anything
8955 F4 Select the marked folders
8956 F5 Move highlight to previous folder
8957 F6 Move highlight to next folder
8958 F7 Previous page of folders
8959 F8 Next page of folders
8960 F9 Toggle choices on or off
8966 Navigation General Alpine Commands
8967 ------------------------- -----------------------
8968 P Prev Folder ? Display this help text
8969 N Next Folder ^C exit without changing anything
8970 - Previous page % Print
8971 Spc (space bar) Next page
8975 ------------------------------------------------
8976 S Select the marked folders
8977 X Toggle choices on or off
8981 <H2>Description of the Select Folders to Check Screen</H2>
8983 This screen is only useful if the feature
8984 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
8986 By default, when you set that feature all of your incoming folders
8987 will be checked periodically for Unseen messages.
8988 By using this screen, you may restrict the set of monitored folders to
8989 a subset of all of the incoming folders.
8991 Mark the folders you want to monitor for Unseen messages with
8993 When you've finished marking all your selections use the Select
8994 command to register your choices.
8995 To return to the default of checking all incoming folders
8996 delete all folders or unmark all folders.
8999 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9002 <End of help on this topic>
9005 ===== h_role_select =====
9008 <TITLE>ROLES SCREEN</TITLE>
9011 <H1>ROLES SCREEN</H1>
9012 <H2>ROLES COMMANDS</H2>
9013 <!--chtml if pinemode="function_key"-->
9016 -------------------------------
9018 F3 Exit without a selection
9019 F4 Select a role to use in composition
9020 F5 Move to previous role
9021 F6 Move to next role
9022 F7 Previous page of roles
9023 F8 Next page of roles
9024 F11 Change Default Role
9025 F12 Whereis (search role nicknames)
9029 Navigation General Alpine Commands
9030 ------------------------- -----------------------
9031 P Prev Role ? Display this help text
9032 N Next Role E Exit without a selection
9034 Spc (space bar) Next page
9035 W WhereIs (search for word in role nicknames)
9037 Select Role Commands
9038 ------------------------------------------------
9039 [Return] Select highlighted role
9040 D Change Default Role
9044 <H2>Description of the Roles Screen</H2>
9046 With this screen you select a role to be used in the composition of a
9048 Use the Previous and Next commands to highlight the role you wish to
9050 When you type carriage return you will be placed in the composer using the highlighted role.
9052 You don't have any non-default <A HREF="h_rules_roles">roles</A>
9053 available unless you set them up.
9054 You may do so by using the Setup/Rules command on the MAIN MENU.
9056 By using the D command, you may set a default role that will persist until
9057 you change it or until you exit Alpine.
9058 The D command toggles through three states: set the default role, unset the
9059 default role, and leave the default role as it is.
9061 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9064 <End of help on this topic>
9067 ===== h_role_abook_select =====
9070 <TITLE>SELECT ADDRESS BOOK SCREEN</TITLE>
9073 <H1>SELECT ADDRESS BOOK SCREEN</H1>
9075 <!--chtml if pinemode="function_key"-->
9078 -------------------------------
9080 F3 Exit screen without selecting anything
9081 F4 Select highlighted address book
9082 F5 Move to previous address book
9083 F6 Move to next address book
9084 F7 Previous page of address books
9085 F8 Next page of address books
9090 Navigation General Alpine Commands
9091 ------------------------- -----------------------
9092 P Previous addrbook ? Display this help text
9095 Spc (space bar) Next page
9098 Select Role Commands
9099 ------------------------------------------------
9100 S Select highlighted address book
9101 E Exit screen without selecting anything
9105 <H2>Description of the Select Address Book Screen</H2>
9107 This screen helps you select one of your address books.
9108 Use the Previous and Next commands to highlight the address book you wish to
9111 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9114 <End of help on this topic>
9117 ======== h_rule_patterns =============
9120 <TITLE>PATTERNS</TITLE>
9124 Patterns are used with Roles, Filtering, Index Coloring,
9125 Scoring, Other Rules, and Search Rules.
9126 Patterns are compared with a message to see if there is a match.
9127 For Filtering, the messages being checked are all the messages in the
9128 folder, one at a time.
9129 For Index Line Coloring, each message that is visible on the screen is
9130 checked for matches with the Index Coloring Patterns.
9131 Roles are used with the Reply, Forward, and Compose commands.
9132 For Reply, the message used to compare the Pattern with is the message
9134 for Forward, the message used to compare the Pattern with is the message
9136 and for Compose, there is no message, so the parts of the Pattern that depend
9137 on a message (everything other than Current Folder Type and the
9138 Beginning of Month and Year)
9140 Only the Current Folder Type matters for Compose (plus the Beginning of
9141 Month or Year, which you wouldn't usually use for a Role).
9142 For Scoring, the message being scored is compared with all of the Score
9143 Patterns, and the Score Values from the ones that match are added together to
9144 get the message's score.
9145 For Other Rules, there is no message. Only the Current Folder Type is checked
9148 Each Pattern has several possible parts, all of which are optional.
9149 In order for there to be a match, <EM>ALL</EM> of the
9150 <EM>defined</EM> parts of the Pattern must match the message.
9151 If a part is not defined it is considered a match, but note that a filtering
9152 Pattern must have at least one defined part or it will be ignored.
9153 For example, if the To pattern is not defined it will be
9156 <CENTER>To pattern = <No Value Set></CENTER>
9158 That is considered a match because it is not defined.
9159 This means that the Pattern with nothing defined is a match if the
9160 Current Folder Type matches, but there is an exception that was mentioned
9161 in the previous paragraph.
9162 Because filtering is a potentially destructive action, filtering Patterns
9163 with nothing other than Current Folder Type defined are ignored.
9164 If you really want a filtering Pattern to match all messages (subject to
9165 Current Folder Type) the best way to do it is to define a Score interval
9166 that includes all possible scores.
9167 This would be the score interval <SAMP>(-INF,INF)</SAMP>.
9168 This can be used even if you haven't defined any rules to Set Scores.
9170 There are six predefined header patterns called the To, From, Sender, Cc, News,
9171 and Subject patterns.
9172 Besides those six predefined header patterns, you may add
9173 additional header patterns with header fieldnames of your choosing.
9174 You add an extra header pattern by placing the cursor on one of the
9175 patterns while in the role editor and using the "eXtraHdr" command.
9176 The Recip pattern is a header pattern that stands for Recipient (To OR Cc)
9177 and the Partic pattern is a header pattern that stands for
9178 Participant (From OR To OR Cc).
9179 (Defining the Recip pattern does not have the same effect as defining both
9180 the To and Cc patterns. Recip is To <EM>OR</EM> Cc, not To <EM>AND</EM> Cc.)
9181 Similar to the header patterns are the AllText pattern and the BodyText pattern.
9182 Instead of comparing this pattern's text against only the contents of
9183 a particular header field, the text for the AllText pattern is compared
9184 with text anywhere in the message's header or body, and the text for the
9185 BodyText pattern is compared with text anywhere in the message's body.
9187 Any of the header patterns, the AllText pattern, or the BodyText pattern may be negated with the
9188 "!" "toggle NOT" command.
9189 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9190 "!" at the beginning of the pattern line.
9191 When the "!" is present, it reverses the meaning of the match.
9192 That is, if the pattern matches then it is considered to NOT be a match, and
9193 if it does not match it is considered to be a match.
9195 Don't make the mistake of putting the "!" in the data field for
9197 For example, if you type the characters "!urgent" into the Subject
9198 pattern, the pattern will look like:
9201 Subject pattern = !urgent
9204 This means you want to match the 7 character sequence "!urgent".
9205 In order to match messages that do not have "urgent" in
9206 their Subject field, first type the characters "urgent" followed
9207 by carriage return for the value of the Subject pattern, then negate it
9208 by typing the "!" command.
9212 ! Subject pattern = urgent
9215 The contents of each of these header patterns (or the AllText or BodyText patterns) may
9216 be a complete email address, part of an address, or a random set of
9217 characters to match against.
9218 It may also be a list of such patterns, which means you
9219 are looking for a match against the first pattern in the list <EM>OR</EM>
9220 the second pattern <EM>OR</EM> the third and so on.
9221 For example, a Subject pattern equal to
9224 Subject pattern = urgent
9229 would match all messages with a subject that contained at least one
9231 It would also match subjects containing the words "alerts" or
9232 "Urgently".
9234 The same example with "NOT" turned on would be
9237 ! Subject pattern = urgent
9242 which would match all messages with a subject that did <EM>NOT</EM> contain any of
9244 You can use the "Add Value" command to add new words to the list,
9245 or you can enter them as a comma-separated list.
9247 (It is not possible to specify two patterns that must <EM>BOTH</EM> be
9248 present for a match.
9249 It is only possible to specify that <EM>EITHER</EM> pattern1 <EM>OR</EM>
9250 pattern2 must be present,
9251 and that is exactly what using a list does.)
9253 The "Current Folder Type" and the "Score Interval" are
9254 also part of the Pattern, although the "Score Interval" is not used
9255 when checking for matches for Scoring.
9256 There are five similar settings that relate to the status of the message.
9257 These settings rely on the message being New or not, Deleted or not,
9258 Answered or not, Important or not, and Recent or not.
9259 There are also some other miscellaneous settings.
9260 The first is the Age of the message in days.
9261 Another is the Size of the message, in bytes.
9262 The third is a setting that detects whether or not the Subject of a
9263 message contains raw 8-bit characters (unencoded characters with the most
9264 significant bit set).
9265 There is a setting that detects whether or not this is the first time
9266 Alpine has been run this month (doesn't depend on individual messages),
9267 and another that detects whether or not this is the first time Alpine has
9269 Other parts of the Pattern detect whether or not the From address of a
9270 message appears in your address book, whether or not certain keywords
9271 are set for a message, and whether or not certain character sets are
9274 <H2>Parts of a Pattern</H2>
9276 <H3>Header patterns</H3>
9278 A header pattern is simply text that is searched for in the corresponding
9280 For example, if a Pattern has a From header pattern with the value
9281 "@company.com", then only messages that have a From header
9282 that contains the text "@company.com" will be possible
9284 Matches don't have to be exact.
9285 For example, if the relevant field of a message contains the text
9286 "mailbox@domain" somewhere
9287 in it, then header patterns of "box", or "x@d", or
9288 "mailbox@domain" are all matches.
9290 All parts of the Pattern must match so, for example,
9291 if a message matches a defined
9292 From pattern, it still must be checked against the other parts of the
9293 Pattern that have been defined.
9294 The To header pattern is a slightly special case.
9295 If the message being checked has a Resent-To header
9296 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on, the addresses
9297 there are used in place of the addresses in the To header.
9298 This is only true for the To header.
9299 Resent-cc and Resent-From headers are never used unless you add them
9300 with the eXtraHdrs command.
9302 The meaning of a header pattern may be negated with the
9303 "!" "toggle NOT" command.
9304 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9305 "!" at the beginning of the pattern line.
9306 It would look something like
9309 ! From pattern = susan@example.com
9312 When the "!" is present, it reverses the meaning of the match.
9314 If you want to check for the presence of a header field but don't care
9315 about its value, then
9316 the empty pattern that you get by entering a pair of
9317 double quotes ("") should match any message that
9318 has the corresponding header field.
9320 <H3><A NAME="pattern_alltext">AllText patterns</A></H3>
9322 AllText patterns are just like header patterns except that the text is
9323 searched for anywhere in the message's headers or body, not just in the
9324 contents of a particular header field.
9327 <H3><A NAME="pattern_bodytext">BodyText patterns</A></H3>
9329 BodyText patterns are just like header patterns except that the text is
9330 searched for anywhere in the message's body, not just in the
9331 contents of a particular header field.
9334 If there is more than one header pattern or AllText pattern or BodyText pattern
9335 for which you want to take the
9336 same action there is a shorthand notation that may be used.
9337 Any of these patterns may be a list of patterns instead of
9338 just a single pattern.
9339 If any one of the patterns in the list matches the message
9340 then it is considered a match.
9341 For example, if "company1" and "company2" both required
9342 you to use the same role when replying to messages, you might have
9343 a To pattern that looks like
9346 To pattern = company1.com
9350 This means that if the mail you are replying to was addressed to
9351 either "anything@company1.com" or "anything@company2.com",
9352 then this Pattern is a match and the same actions will be taken.
9354 The meaning of an AllText or BodyText pattern may be negated with the
9355 "!" "toggle NOT" command.
9356 You can tell that <EM>NOT</EM> has been turned on by looking for the character
9357 "!" at the beginning of the pattern line.
9358 When the "!" is present, it reverses the meaning of the match.
9360 A technicality: Since comma is the character used to separate multiple values
9361 in any of the fields that may have multiple values (such as header patterns,
9362 AllText patterns, BodyText patterns, keywords, folder lists, and so on),
9363 you must escape comma with a
9364 backslash (\) if you want to include a literal comma in one of those fields.
9365 In other words, if you type a backslash followed by a comma it will
9366 be interpreted as a comma by Alpine, instead of as a separator between
9368 All other backslashes (those not followed by a comma) are literal
9369 backslashes and should not be escaped.
9370 It's unlikely you'll ever need to enter a literal comma or backslash in
9371 any of the patterns.
9373 <H3><A NAME="pattern_current_folder">Current Folder Type</A></H3>
9375 The "Current Folder Type" may be set to one of four different
9376 values: "Any", "News", "Email", or
9377 "Specific".
9378 If the value is set to "News", then the
9379 Pattern will only match if the currently open folder is a newsgroup.
9380 The value "Email" only matches if the current folder is not news and
9381 the value "Any" causes any folder to match.
9382 If the value of "Current Folder Type" is set to "Specific",
9383 then you must fill in a value for "Folder", which is on the line
9384 below the "Specific" line.
9385 In this case you will only get a match if the currently open folder is
9386 the specific folder you list.
9387 You may give a list of folders instead of just a single
9388 folder name, in which case the Pattern will match if the open folder is
9389 any one of the folders in the list.
9390 The name of each folder in the list may be either "INBOX",
9391 the technical specification
9392 of the folder (like what appears in your configuration file) or, if the
9393 folder is one of your incoming folders, it may be the nickname you've given
9395 Here are some samples of specific folder names:
9397 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
9399 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
9401 <CENTER><SAMP>mail/local-folder</SAMP></CENTER>
9403 The easiest way to fill in the "Folder" field is to use
9404 the "T" command that is available when the "Folder" line is
9405 highlighted, or to use the "Take" command with the configuration
9407 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
9410 When reading a newsgroup, there may be a performance penalty
9411 incurred when collecting the information necessary to check whether
9412 or not a Pattern matches a message.
9413 For this reason, the default Current Folder Type is set to "Email".
9414 If you have Patterns with a Current Folder Type of either
9415 "Any" or "News" and those Patterns are used for
9416 Index Line Coloring or Scoring, you may experience
9417 slower screen redrawing in the MESSAGE INDEX screen when in a newsgroup.
9419 <H3><A NAME="pattern_age_interval">Age Interval</A></H3>
9421 The "Age Interval" may be set to an interval of message
9422 ages that should be considered a match.
9423 Like the other parts of the Pattern, if it is unset it will be ignored.
9424 The Age Interval looks like
9426 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
9428 where "min_age" and "max_age" are integers greater
9429 than or equal to zero.
9430 The special value "INF" may be used for
9431 the max value. It represents infinity.
9433 Actually, this option may be defined as a list of intervals instead
9434 of just a single interval.
9435 The list is separated by commas.
9438 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
9440 When there is an Age Interval defined, it is a match if the age, in days, of
9441 the message is contained in any of the intervals.
9442 The intervals include both endpoints.
9444 Even though this option is called Age, it isn't actually
9445 the <EM>age</EM> of the message.
9446 Instead, it is how many days ago the message arrived in one of your folders.
9447 If the current time is a little past midnight, then a message that arrived
9448 just before midnight arrived yesterday, even though the message is only
9450 By default, the date being used is not the date in the Date
9451 header of the message.
9452 It is the date that the message arrived in one of your folders.
9453 When you Save a message from one folder to another that arrival date
9455 If you would like to use the date in the Date header that is possible.
9457 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
9458 near the bottom of the rule definition.
9459 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
9461 <H3><A NAME="pattern_size_interval">Size Interval</A></H3>
9463 The "Size Interval" may be set to an interval of message
9464 sizes that should be considered a match.
9465 Like the other parts of the Pattern, if it is unset it will be ignored.
9466 The Size Interval looks like
9468 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
9470 where "min_size" and "max_size" are integers greater
9471 than or equal to zero.
9472 The special value "INF" may be used for
9473 the max value. It represents infinity.
9475 Actually, this option may be defined as a list of intervals instead
9476 of just a single interval.
9477 The list is separated by commas.
9480 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
9482 When there is a Size Interval defined, it is a match if the size, in bytes, of
9483 the message is contained in any of the intervals.
9484 The intervals include both endpoints.
9486 <H3><A NAME="pattern_score_interval">Score Interval</A></H3>
9488 The "Score Interval" may be set to an interval of message
9489 scores that should be considered a match.
9490 Like the other parts of the Pattern, if it is unset it will be ignored.
9491 The Score Interval looks like
9493 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
9495 where "min_score" and "max_score" are positive or
9496 negative integers, with min_score less than or equal to max_score.
9497 The special values "-INF" and "INF" may be used for
9498 the min and max values to represent negative and positive infinity.
9500 Actually, a list of intervals may be used if you wish.
9501 A list would look like
9503 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
9505 When there is a Score Interval defined, it is a match if the score for
9506 the message is contained in any of the intervals in the list.
9507 The intervals include the endpoints.
9508 The score for a message is calculated by looking at every Score rule defined and
9509 adding up the Score Values for the ones that match the message.
9510 When deciding whether or not a Pattern matches a message for purposes of
9511 calculating the score, the Score Interval is ignored.
9513 <H3><A NAME="pattern_message_status">Message Status</A></H3>
9515 There are five separate message status settings.
9516 By default, all five are set to the value "Don't care", which
9517 will match any message.
9518 The value "Yes" means that the particular status must be true
9519 for a match, and the value "No" means that the particular
9520 status must not be true for a match.
9521 For example, one of the five Message Status settings is whether a message
9522 is marked Important or not.
9523 A "Yes" means that the message must be Important to be
9524 considered a match and "No" means that the message must not be
9525 Important to be considered a match.
9526 The same is true of the other four message status settings that depend
9527 on whether or not the message is New; whether the message has
9528 been Answered or not; whether the message has been Deleted or not, and
9529 whether the message is Recent or not.
9531 The nomenclature for New and Recent is a bit confusing:
9533 New means that the message is Unseen.
9534 It could have been in your mailbox for a long time but if you haven't looked
9535 at it, it is still considered New.
9536 That matches the default Alpine index display that shows an N for such a
9539 Recent means that the message was added to this folder since the last time
9540 you opened the folder.
9541 Alpine also shows an N by default for these types of messages.
9542 If you were to run two copies of Alpine that opened a folder one right after
9543 the other, a message would only show up as Recent in (at most) the first
9546 <H3><A NAME="pattern_message_keywords">Message Keywords</A></H3>
9548 Keywords are similar to Message Status, but they are chosen by the user.
9549 Provided the mail server allows for it, you may add a set of possible keywords
9550 to a folder and then you may set those keywords or not for each message
9551 in the folder (see <A HREF="h_common_flag">Flag Command</A>).
9552 The syntax of this part of the Pattern is similar to the header patterns.
9553 It is a list of keywords.
9554 The Keyword part of the Pattern is a match if the message has any of
9555 the keywords in the list set.
9556 Like other parts of the Pattern, if this is unset it will be ignored.
9558 <H3><A NAME="pattern_message_charsets">Message Character Sets</A></H3>
9560 A message may use one or more character sets.
9561 This part of the Pattern matches messages that make use of one or more of
9562 the character sets specified in the pattern.
9563 It will be considered a match if a message uses any of the character
9564 sets in the list you give here.
9567 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
9568 GB2312) you may also use some shorthand names that Alpine provides.
9569 These names are more understandable shorthand names for sets of
9570 character set names.
9571 Two examples are "Cyrillic" and "Greek".
9572 Selecting one of these shorthand names is equivalent to selecting all of
9573 the character sets that make up the set.
9574 You can see all of these shorthand names and the lists of character sets
9575 they stand for by typing the "T" command with the Character
9576 Set pattern highlighted.
9577 The syntax of this part of the Pattern is similar to the header patterns
9578 and the Message Keywords pattern.
9579 It is a list of character sets (or shorthand names).
9580 The Character Set part of the Pattern is a match if the message uses any
9581 of the character sets in the list.
9582 Like other parts of the Pattern, if this is unset it will be ignored.
9584 <H3><A NAME="pattern_8bit_subject">Raw 8-bit in Subject</A></H3>
9586 It seems that lots of unwanted email contains unencoded 8-bit characters
9588 Normally, characters with the 8th bit set are not allowed in the Subject
9589 header unless they are MIME-encoded.
9590 This option gives you a way to match messages that have Subjects that
9591 contain unencoded 8-bit characters.
9592 By default, the value of this option is "Don't care", which
9593 will match any message.
9594 The value "Yes" means that there must be raw 8-bit characters in
9595 the Subject of the message in order for there to be a match,
9596 and the value "No" is the opposite.
9597 Setting this option will affect performance in large folders because the
9598 subject of each message in the folder has to be checked.
9600 <H3><A NAME="pattern_bom">Beginning of Month</A></H3>
9602 This option gives you a way to take some action once per month.
9603 By default, the value of this option is "Don't care", which
9605 The value "Yes" means that this must be the first time Alpine has
9606 been run this month in order to count as a match,
9607 and the value "No" is the opposite.
9609 <H3><A NAME="pattern_boy">Beginning of Year</A></H3>
9611 This option gives you a way to take some action once per year.
9612 By default, the value of this option is "Don't care", which
9614 The value "Yes" means that this must be the first time Alpine has
9615 been run this year in order to count as a match,
9616 and the value "No" is the opposite.
9618 <H3><A NAME="pattern_abookfrom">Address in Address Books</A></H3>
9620 This option gives you a way to match messages that have an address
9621 that is in one of your address books.
9622 Only the simple entries in your address books are searched.
9623 Address book distribution lists are ignored!
9624 By default, the value of this option is "Don't care", which
9625 will match any message.
9626 The value "Yes, in any address book" means the address
9627 from the message must be in at least one of your
9628 address books in order to be a match.
9629 The value "No, not in any address book"
9630 means none of the addresses may
9631 be in any of your address books in order to be a match.
9632 The values "Yes, in specific address books" and
9633 "No, not in any of specific address books" are similar but instead
9634 of depending on all address books you are allowed to give a list of address
9636 The addresses from the message that are checked for are determined by the
9637 setting you have for "Types of addresses to check for in address book".
9638 If you set this to "From" the From address from the message will
9639 be looked up in the address book.
9640 If you set it to only "To" then the To addresses will be used.
9641 If any of the To addresses are in the address book then it is considered
9642 a match for "Yes" or not a match for "No".
9643 You could set it to both From and To, in which case all of the From and To
9645 The "Reply-To" and "Sender" cases are a little unusual.
9646 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
9647 exists or the From address if there is no Reply-To address.
9648 Same for the Sender address.
9649 Setting this option may affect performance in large folders because the
9650 From and Reply-To of each message in the folder have to be checked.
9652 <H3><A NAME="pattern_categorizer">Categorizer Command</A></H3>
9654 This is a command that is run with its standard input set to the message
9655 being checked and its standard output discarded.
9656 The full directory path should be specified.
9657 The command will be run and then its exit status will be checked against
9658 the Exit Status Interval, which defaults to just the value zero.
9659 If the exit status of the command falls in the interval, it is considered
9660 a match, otherwise it is not a match.
9663 This option may actually be a list of commands.
9664 The first one that exists and is executable is used.
9665 That makes it possible to use the same configuration with Unix Alpine and
9669 If none of the commands in the list exists and is executable then the rule
9670 is <EM>not</EM> a match.
9671 If it is possible that the command may not exist, you should be careful
9672 to structure your rules so that nothing destructive
9673 happens when the command does not exist.
9674 For example, you might have a filter that filters away spam when there is
9675 a match but does nothing when there is not a match.
9676 That would continue to work correctly if the command didn't exist.
9677 However, if you have a filter that filters away spam when there is not
9678 a match and keeps it when there is a match, that would filter everything
9679 if the categorizer command didn't exist.
9681 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
9682 setup for the bogofilter filter.
9685 <End of help on this topic>
9688 ===== h_rules_roles =====
9691 <TITLE>SETUP ROLES SCREEN</TITLE>
9694 <H1>SETUP ROLES SCREEN</H1>
9695 <H2>SETUP ROLES COMMANDS</H2>
9696 <!--chtml if pinemode="function_key"-->
9698 Available Commands -- Group 1 Available Commands -- Group 2
9699 ------------------------------- ------------------------------
9700 F1 Show Help Text F1 Show Help Text
9701 F2 See commands in next group F2 See commands in next group
9702 F3 Back to MAIN Alpine menu
9703 F4 Change configuration for role
9704 F5 Move to previous role F5 Include file in role config
9705 F6 Move to next role F6 Exclude file from config
9706 F7 Previous page of roles
9707 F8 Next page of roles
9708 F9 Add new role F9 Replicate existing role
9709 F10 Delete existing role
9710 F11 Shuffle the order of roles
9711 F12 Whereis (search role nicknames)
9715 Navigation General Alpine Commands
9716 ------------------------- -----------------------
9717 P Prev Role ? Display this help text
9718 N Next Role E Back to MAIN Alpine menu
9720 Spc (space bar) Next page
9721 W WhereIs (search for word in role nicknames)
9723 Setup Roles Commands
9724 ------------------------------------------------
9725 A Add new role $ Shuffle the order of roles
9726 D Delete existing role C Change configuration for highlighted role
9727 R Replicate existing role
9728 I Include file in role config X Exclude file from role config
9732 <H2>Description of the Setup Roles Screen</H2>
9734 This screen lets you add, delete, modify, or change the order of the rules
9735 that determine the role you are playing when composing a message.
9737 You may play different roles depending on who you are replying to.
9738 For example, if you are replying to a message addressed to help-desk you
9739 may be acting as a Help Desk Worker.
9740 That role may require that you use a different return address and/or
9741 a different signature.
9744 If you set up roles they work like this: Each role has a set of
9745 "Uses", which indicate whether or not a role is eligible to be
9746 considered for a particular use; a "Pattern",
9747 which is used to decide which of the eligible roles is used; and a set
9748 of "Actions", which are taken when that role is used.
9749 When you reply to a message, the message you are replying to is compared
9750 with the Patterns of the roles marked as eligible for use when replying.
9751 The comparisons start with the first eligible role and keep going until there
9753 If a match is found, the matching role's Actions are taken.
9755 It is also possible to set a default role and to change that role during
9756 your Alpine session.
9757 When you start Alpine no default role will be set.
9758 You may set or change the current default role by using the "D"
9759 command in the role selection screen.
9760 You'll see that screen while composing a message and being asked to select
9762 An easy way to get to that screen is to use the <A HREF="h_common_role">Role Command</A> to
9764 You may find a default role useful if you normally perform the duties of one
9765 of your roles for a while, then you switch to another role and stay in the
9766 new role for another period of time.
9767 It may be easier than using the Role Command to select the role each time you
9772 There are three types of use to be configured;
9773 one for Replying, one for Forwarding, and one for Composing.
9774 These indicate whether or not you want a role to be considered when you
9775 type the Reply, Forward, or Compose commands.
9776 (The Role command is an alternate form of the Compose command, and it is
9777 not affected by these settings.)
9778 Each of these Use types has three possible values.
9779 The value "Never"
9780 means that the role will never be considered as a candidate for use with
9781 the corresponding command.
9782 For example, if you set a role's Reply Use to Never, then when you Reply to
9783 a message, that role won't even be considered.
9784 (That isn't quite true. If the message you are replying to matches some other
9785 role that requires confirmation,
9786 then there will be a ^T command available which allows you to select a role
9787 from all of your roles, not just the reply-eligible roles.)
9790 The options "With confirmation" and "Without confirmation"
9791 both mean that you do want to consider this role when using the corresponding
9793 For either of these settings the role's Pattern will
9794 be checked to see if it matches the message.
9795 For Reply Use, the message used to compare the Pattern with is the message
9797 For Forward Use, the message used to compare the Pattern with is the message
9799 For Compose Use, there is no message, so the parts of the Pattern that depend
9800 on a message (everything other than Current Folder Type) are ignored.
9801 In all cases, the Current Folder Type is checked if defined.
9802 If there is a match then this role will either be used without confirmation
9803 or will be the default when confirmation is asked for, depending on
9804 which of the two options is selected.
9805 If confirmation is requested, you will have a chance to
9806 choose No Role instead of the offered role, or to
9807 change the role to any one of your other roles (with the ^T command).
9809 <H2>Role Patterns</H2>
9811 In order to determine whether or not a message matches a role the message is
9812 compared with the Role's Pattern.
9813 These Patterns are the same for use with Roles, Filtering, Index Coloring,
9814 Scoring, Other Rules, and Search Rules, so are described in only one place,
9815 "<A HREF="h_rule_patterns">here</A>".
9817 Since header patterns, AllText patterns, and BodyText patterns that are unset are ignored,
9818 a role that has all header patterns unset, the AllText pattern unset,
9819 the BodyText pattern unset,
9820 the Score Interval unset, and the Current Folder Type set to
9821 "Any" may be used as a default role.
9822 It should be put last in the list of roles since the matching
9823 starts at the beginning and proceeds until one of the roles is a match.
9824 If no roles at all match, then Alpine will
9825 use its regular methods of defining the role.
9826 If you wanted to, you could define a different "default" role
9827 for Replying, Forwarding, and Composing by setting the
9828 "Use" fields appropriately.
9830 <H2>Role Actions</H2>
9832 Once a role match is found, the role's Actions are taken.
9833 For each role there are several possible actions that may be defined.
9834 They are actions to set the From address, the Reply-To address,
9835 the Fcc, the Signature, the Template file, and Other Headers.
9839 The From address is the address used on the From line of the message
9842 <H3>Set Reply-To</H3>
9844 The Reply-To address is the address used on the Reply-To line of the message
9846 You don't need a Reply-To address unless it is different from the From address.
9848 <H3>Set Other Headers</H3>
9850 If you want to set the value of the From or Reply-To headers, use
9851 the specific fields "Set From" or "Set Reply-To".
9852 If you want to set the values of other headers, use this field.
9853 This field is similar to the
9854 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> configuration option.
9855 Each header you specify here must include the header tag
9856 ("To:", "Approved:", etc.)
9857 and may optionally include a value for that header.
9858 It is different from the <!--#echo var="VAR_customized-hdrs"--> in that the value you give
9859 for a header here will replace any value that already exists.
9860 For example, if you are Replying to a message there will be at least one
9861 address in the To header (the address you are Replying to).
9862 However, if you Reply using a role that sets the To header, that role's
9863 To header value will be used instead.
9867 The Fcc is used as the Fcc for the message you are sending.
9869 <H3>Set Signature or Set LiteralSig</H3>
9871 The Signature is the name of a file to be used as the signature file when
9872 this role is being used.
9873 If the name of the file has a vertical bar following it (|)
9874 then it is assumed that the file is a program that should be run to
9875 produce the signature.
9876 If the LiteralSig is set, then it is used instead of the signature file.
9877 LiteralSig is just a different way to store the signature.
9878 It is stored in the pine configuration file instead of in a separate
9880 If the <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined
9881 either in the role or as the default signature in the Setup/Config screen,
9882 then the signature file is ignored.
9884 <H3>Set Template</H3>
9886 A Template is the name of a file to be included in the message when this
9888 If the name of the file has a vertical bar following it (|)
9889 then it is assumed that the file is a program that should be run to
9890 produce the template.
9893 Both signature files and template files may be stored remotely on an IMAP
9895 In order to do that you just give the file a remote name.
9896 This works just like the regular
9897 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>
9898 option that is configured from the Setup/Configuration screen.
9899 A remote signature file name might look like:
9901 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
9903 Once you have named the remote signature or template file you create its
9904 contents by using the "F" "editFile" command when the
9905 cursor is on the "Set Signature" or "Set Template"
9906 line of the role editor.
9909 Both signature files and template files (or the output of signature programs
9910 and template file programs) may contain special tokens
9911 that are replaced with contents
9912 that depend on the message being replied to or forwarded.
9913 See the help for the individual fields inside the role editor for more
9914 information on tokens.
9916 <H3>Use SMTP Server</H3>
9918 If this field has a value, then it will be used as the SMTP server
9919 to send mail when this role is being used (unless the SMTP server variable
9920 is set in the system-wide fixed configuration file).
9921 It has the same semantics as the
9922 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
9923 variable in the Setup/Config screen.
9924 When you postpone the composition this SMTP server list will be saved
9925 with the postponed composition and it cannot be changed later.
9926 Because of that, you may want to make this a list of SMTP servers
9927 with the preferred server at the front of the list and alternate servers
9931 If any of the actions are left unset, then the action depends on what
9932 is present in the "Initialize settings using role" field.
9933 If you've listed the nickname of another one of your roles there, then the
9934 corresponding action from that role will be used here.
9935 If that action is also blank, or if there is no nickname specified,
9936 then Alpine will do whatever it normally does to set these actions.
9937 This depends on other configuration options and features you've set.
9939 <H2>Command Descriptions</H2>
9943 The Add command is used to add a new role definition to your set of
9945 The new role will be added after the highlighted role.
9949 The Delete command deletes the currently highlighted role.
9953 The Change command lets you edit the nickname, Uses, Pattern,
9954 and Actions of the currently highlighted role.
9958 The Shuffle command allows you to change the order of the roles.
9959 You may move the currently highlighted role up or down in the list.
9960 The order of the roles is important since the roles are tested for a
9961 match starting with the first role and continuing until a match is found.
9962 You should place the roles with more specific Patterns near the beginning
9963 of the list, and those with more general Patterns near the end so that
9964 the more specific matches will happen when appropriate.
9968 The Replicate command is used to copy an existing role and modify it.
9969 The new role will be added after the highlighted role.
9971 <H3>IncludeFile</H3>
9973 The IncludeFile command allows you to add a roles file to your configuration.
9974 Usually, your roles will be contained in your Alpine configuration file.
9975 If you wish, some or all of your roles may be stored in a separate file.
9976 If a roles file already exists (maybe it was made by somebody else using
9977 Alpine), you may insert it before the currently highlighted role.
9978 You may also insert an empty file or a file that does not yet exist.
9979 Once you have an empty roles file in your configuration, you may use
9980 the Shuffle command to move roles into it.
9981 In fact, that's the only way to get the initial role into the file.
9983 <H3>eXcludeFile</H3>
9985 The eXcludeFile command removes a roles file from your roles configuration.
9986 A limitation of the program is that in order to exclude a roles file
9987 that file must have at least one role
9988 in it, otherwise you won't be able to highlight a line in the file.
9989 So you may have to add a dummy role to the file in order to exclude the file.
9991 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
9994 <End of help on this topic>
9997 ===== h_rules_other =====
10000 <TITLE>SETUP OTHER RULES SCREEN</TITLE>
10003 <H1>SETUP OTHER RULES SCREEN</H1>
10004 <H2>SETUP OTHER RULES COMMANDS</H2>
10005 <!--chtml if pinemode="function_key"-->
10007 Available Commands -- Group 1 Available Commands -- Group 2
10008 ------------------------------- ------------------------------
10009 F1 Show Help Text F1 Show Help Text
10010 F2 See commands in next group F2 See commands in next group
10011 F3 Back to MAIN Alpine menu
10012 F4 Change configuration for rule
10013 F5 Move to previous rule F5 Include file in rule config
10014 F6 Move to next rule F6 Exclude file from config
10015 F7 Previous page of rules
10016 F8 Next page of rules
10017 F9 Add new rule F9 Replicate existing rule
10018 F10 Delete existing rule
10019 F11 Shuffle the order of rules
10020 F12 Whereis (search rule nicknames)
10024 Navigation General Alpine Commands
10025 ------------------------- -----------------------
10026 P Prev rule ? Display this help text
10027 N Next rule E Back to MAIN Alpine menu
10029 Spc (space bar) Next page
10030 W WhereIs (search for word in rule nicknames)
10032 Setup Other Rules Commands
10033 ------------------------------------------------
10034 A Add new rule $ Shuffle the order of rules
10035 D Delete existing rule C Change configuration for highlighted rule
10036 R Replicate existing rule
10037 I Include file in rule config X Exclude file from rule config
10041 <H2>Description of the Setup Other Rules Screen</H2>
10043 This is where you may set various actions that do not fit well into the
10044 other Rules categories.
10048 Other Rules are a little different from the rest of the Rules because
10049 they depend only on the current folder, and not on a particular message.
10050 In order to determine whether or not a rule's actions should be applied
10051 the current folder is compared with the rule's Pattern, which consists
10052 of only the Current Folder Type.
10053 Current Folder Type works the same for Other Rules as it does for Roles,
10054 Filtering, Index Coloring, and Scoring.
10055 Keep in mind that the only part of the Pattern that applies to Other
10056 Rules is the Current Folder Type when looking at the description of
10058 "<A HREF="h_rule_patterns">here</A>".
10060 <H2>The Actions</H2>
10062 <H3>Set Sort Order</H3>
10064 When you enter a new folder, these rules will be checked to see if you
10065 have set a sort order that is different from your default sort order.
10066 The default is set in the Setup/Config screen with
10067 the "<A HREF="h_config_sort_key"><!--#echo var="VAR_sort-key"--></A>" option.
10068 If the Sort Order action is set, then the folder will be displayed sorted in
10069 that sort order instead of in the default order.
10071 A possible point of confusion arises when you change the configuration
10072 of the Sort Order for the currently open folder.
10073 The folder will normally be re-sorted when you go back to viewing the
10075 However, if you have manually sorted the folder with the
10077 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
10078 command, then it will not be re-sorted until the next time it is opened.
10080 <H3>Set Index Format</H3>
10082 When you enter a new folder, these rules will be checked to see if you
10083 have set an Index Format that is different from your default Index Format,
10084 which is set with the
10085 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
10086 If so, the index will be displayed with this format instead of the default.
10088 <H3>Set Startup Rule</H3>
10090 When you enter a new folder, these rules will be checked to see if you
10091 have set a startup rule that is different from the default startup rule.
10092 The default for incoming folders is set in the Setup/Config screen with
10093 the "<!--#echo var="VAR_incoming-startup-rule"-->" option.
10094 The default for folders other than INBOX that are not part of your
10095 incoming collection
10096 (see <A HREF="h_config_enable_incoming"><!--#echo var="FEAT_enable-incoming-folders"--></A> feature)
10097 is to start with the last message in the folder.
10098 If the Startup Rule is set to something other than "default",
10099 then the rule will determine which message will be the current message when
10100 the folder is first opened.
10102 The various startup rule possibilities work the same here as they do in
10103 the incoming collection, so check
10104 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
10107 <H2>Command Descriptions</H2>
10111 The Add command is used to add a new rule definition to your set of
10113 The new rule will be added after the highlighted rule.
10117 The Delete command deletes the currently highlighted rule.
10121 The Change command lets you edit the nickname, Pattern,
10122 and Action of the currently highlighted rule.
10126 The Shuffle command allows you to change the order of the rules.
10127 You may move the currently highlighted rule up or down in the list.
10128 The order of the rules is important since the rules are tested for a
10129 match starting with the first rule and continuing until a match is found.
10130 You should place the rules with more specific Patterns near the beginning
10131 of the list, and those with more general Patterns near the end so that
10132 the more specific matches will happen when appropriate.
10136 The Replicate command is used to copy an existing rule definition and modify it.
10137 The new rule will be added after the highlighted rule.
10139 <H3>IncludeFile</H3>
10141 The IncludeFile command allows you to add a rules file to your configuration.
10142 Usually, your rules will be contained in your Alpine configuration file.
10143 If you wish, some or all of your rules may be stored in a separate file.
10144 If a rules file already exists (maybe it was made by somebody else using
10145 Alpine), you may insert it before the currently highlighted rule.
10146 You may also insert an empty file or a file that does not yet exist.
10147 Once you have an empty rules file in your configuration, you may use
10148 the Shuffle command to move rules into it.
10149 In fact, that's the only way to get the initial rule into the file.
10151 <H3>eXcludeFile</H3>
10153 The eXcludeFile command removes a rules file from your rules configuration.
10154 A limitation of the program is that in order to exclude a rules file
10155 that file must have at least one rule
10156 in it, otherwise you won't be able to highlight a line in the file.
10157 So you may have to add a dummy rule to the file in order to exclude the file.
10159 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10162 <End of help on this topic>
10165 ===== h_rules_srch =====
10168 <TITLE>SETUP SEARCH RULES SCREEN</TITLE>
10171 <H1>SETUP SEARCH RULES SCREEN</H1>
10172 <H2>SETUP SEARCH RULES COMMANDS</H2>
10173 <!--chtml if pinemode="function_key"-->
10175 Available Commands -- Group 1 Available Commands -- Group 2
10176 ------------------------------- ------------------------------
10177 F1 Show Help Text F1 Show Help Text
10178 F2 See commands in next group F2 See commands in next group
10179 F3 Back to MAIN Alpine menu
10180 F4 Change configuration for rule
10181 F5 Move to previous rule F5 Include file in rule config
10182 F6 Move to next rule F6 Exclude file from config
10183 F7 Previous page of rules
10184 F8 Next page of rules
10185 F9 Add new rule F9 Replicate existing rule
10186 F10 Delete existing rule
10187 F11 Shuffle the order of rules
10188 F12 Whereis (search rule nicknames)
10192 Navigation General Alpine Commands
10193 ------------------------- -----------------------
10194 P Prev rule ? Display this help text
10195 N Next rule E Back to MAIN Alpine menu
10197 Spc (space bar) Next page
10198 W WhereIs (search for word in rule nicknames)
10200 Setup Search Rules Commands
10201 ------------------------------------------------
10202 A Add new rule $ Shuffle the order of rules
10203 D Delete existing rule C Change configuration for highlighted rule
10204 R Replicate existing rule
10205 I Include file in rule config X Exclude file from rule config
10209 <H2>Description of the Setup Search Rules Screen</H2>
10211 One of the commands that becomes available when that feature is turned on
10212 is the "; Select" command, which is used in the MESSAGE INDEX
10213 screen to select a set of messages.
10214 One way of selecting messages is to use a Rule.
10215 All of the messages that match (or don't match if you wish)
10216 a Rule's Pattern will be selected.
10218 Any of your Rules may be used for this purpose.
10219 You might already have Rules set up for filtering, index line color, scores, or roles;
10220 and you may use any of those Rules with the Select command.
10221 However, you might find it more convenient to set up a separate set of Rules
10222 just for this purpose without having to worry about what other effects
10224 That is the purpose of these Select Rules.
10227 Each rule has a "Pattern"
10228 that is used to decide which messages are selected when you use it with
10229 the Select command.
10233 In order to determine whether or not a message should be selected
10234 the message is compared with the rule's Pattern.
10235 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10236 Scoring, Other Rules, and Search Rules, so are described in only one place,
10237 "<A HREF="h_rule_patterns">here</A>".
10239 <H2>Command Descriptions</H2>
10243 The Add command is used to add a new rule definition to your set of
10245 The new rule will be added after the highlighted rule.
10249 The Delete command deletes the currently highlighted rule.
10253 The Change command lets you edit the nickname and Pattern
10254 of the currently highlighted rule.
10258 The Shuffle command allows you to change the order of the rules.
10259 This affects only the order they are presented in when you use the
10260 ^T subcommand of the Select by Rule command.
10261 You may move the currently highlighted rule up or down in the list.
10265 The Replicate command is used to copy an existing rule definition and modify it.
10266 The new rule will be added after the highlighted rule.
10268 <H3>IncludeFile</H3>
10270 The IncludeFile command allows you to add a rules file to your configuration.
10271 Usually, your rules will be contained in your Alpine configuration file.
10272 If you wish, some or all of your rules may be stored in a separate file.
10273 If a rules file already exists (maybe it was made by somebody else using
10274 Alpine), you may insert it before the currently highlighted rule.
10275 You may also insert an empty file or a file that does not yet exist.
10276 Once you have an empty rules file in your configuration, you may use
10277 the Shuffle command to move rules into it.
10278 In fact, that's the only way to get the initial rule into the file.
10280 <H3>eXcludeFile</H3>
10282 The eXcludeFile command removes a rules file from your rules configuration.
10283 A limitation of the program is that in order to exclude a rules file
10284 that file must have at least one rule
10285 in it, otherwise you won't be able to highlight a line in the file.
10286 So you may have to add a dummy rule to the file in order to exclude the file.
10288 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10291 <End of help on this topic>
10294 ===== h_rules_incols =====
10297 <TITLE>SETUP INDEX LINE COLORS SCREEN</TITLE>
10300 <H1>SETUP INDEX LINE COLORS SCREEN</H1>
10301 <H2>SETUP INDEX LINE COLORS COMMANDS</H2>
10302 <!--chtml if pinemode="function_key"-->
10304 Available Commands -- Group 1 Available Commands -- Group 2
10305 ------------------------------- ------------------------------
10306 F1 Show Help Text F1 Show Help Text
10307 F2 See commands in next group F2 See commands in next group
10308 F3 Back to MAIN Alpine menu
10309 F4 Change configuration for rule
10310 F5 Move to previous rule F5 Include file in rule config
10311 F6 Move to next rule F6 Exclude file from config
10312 F7 Previous page of rules
10313 F8 Next page of rules
10314 F9 Add new rule F9 Replicate existing rule
10315 F10 Delete existing rule
10316 F11 Shuffle the order of rules
10317 F12 Whereis (search rule nicknames)
10321 Navigation General Alpine Commands
10322 ------------------------- -----------------------
10323 P Prev rule ? Display this help text
10324 N Next rule E Back to MAIN Alpine menu
10326 Spc (space bar) Next page
10327 W WhereIs (search for word in rule nicknames)
10329 Setup Index Color Commands
10330 ------------------------------------------------
10331 A Add new rule $ Shuffle the order of rules
10332 D Delete existing rule C Change configuration for highlighted rule
10333 R Replicate existing rule
10334 I Include file in rule config X Exclude file from rule config
10338 <H2>Description of the Setup Index Line Colors Screen</H2>
10340 Index Line Color causes lines in the MESSAGE INDEX screen to be colored.
10341 This action is only available if your terminal is capable of displaying
10342 color and color display has been enabled with the
10343 <A HREF="h_config_color_style">Color Style</A> option within the
10344 Setup Color screen.
10345 (In PC-Alpine, color is always enabled so there is no option to turn on.)
10346 This screen lets you add, delete, modify, or change the order of the rules
10347 that cause the lines in the MESSAGE INDEX to be displayed in different
10350 Each rule has a "Pattern",
10351 which is used to decide which of the rules is used; and the color that
10352 is used if the Pattern matches a particular message.
10354 <H2>Index Color Patterns</H2>
10356 In order to determine whether or not a message matches an Index Color Rule
10357 the message is compared with the rule's Pattern.
10358 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10359 Scoring, Other Rules, and Search Rules, so are described in only one place,
10360 "<A HREF="h_rule_patterns">here</A>".
10363 If none of the Index Color rules is a match for a particular index line,
10364 then the color used is set using
10365 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10367 <H2>Index Line Color</H2>
10369 This is the color that index lines are colored when there is a matching
10371 This colors the whole index line, except possibly the status letters,
10372 which may be colored separately using
10373 the <A HREF="h_color_setup">Setup Kolor</A> screen.
10375 <H2>Command Descriptions</H2>
10379 The Add command is used to add a new rule definition to your set of
10381 The new rule will be added after the highlighted rule.
10385 The Delete command deletes the currently highlighted rule.
10389 The Change command lets you edit the nickname, Pattern,
10390 and Index Line Color of the currently highlighted rule.
10394 The Shuffle command allows you to change the order of the rules.
10395 You may move the currently highlighted rule up or down in the list.
10396 The order of the rules is important since the rules are tested for a
10397 match starting with the first rule and continuing until a match is found.
10398 You should place the rules with more specific Patterns near the beginning
10399 of the list, and those with more general Patterns near the end so that
10400 the more specific matches will happen when appropriate.
10404 The Replicate command is used to copy an existing rule definition and modify it.
10405 The new rule will be added after the highlighted rule.
10407 <H3>IncludeFile</H3>
10409 The IncludeFile command allows you to add a rules file to your configuration.
10410 Usually, your rules will be contained in your Alpine configuration file.
10411 If you wish, some or all of your rules may be stored in a separate file.
10412 If a rules file already exists (maybe it was made by somebody else using
10413 Alpine), you may insert it before the currently highlighted rule.
10414 You may also insert an empty file or a file that does not yet exist.
10415 Once you have an empty rules file in your configuration, you may use
10416 the Shuffle command to move rules into it.
10417 In fact, that's the only way to get the initial rule into the file.
10419 <H3>eXcludeFile</H3>
10421 The eXcludeFile command removes a rules file from your rules configuration.
10422 A limitation of the program is that in order to exclude a rules file
10423 that file must have at least one rule
10424 in it, otherwise you won't be able to highlight a line in the file.
10425 So you may have to add a dummy rule to the file in order to exclude the file.
10427 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10430 <End of help on this topic>
10433 ===== h_rules_filter =====
10436 <TITLE>SETUP FILTERING SCREEN</TITLE>
10439 <H1>SETUP FILTERING SCREEN</H1>
10440 <H2>SETUP FILTERING COMMANDS</H2>
10441 <!--chtml if pinemode="function_key"-->
10443 Available Commands -- Group 1 Available Commands -- Group 2
10444 ------------------------------- ------------------------------
10445 F1 Show Help Text F1 Show Help Text
10446 F2 See commands in next group F2 See commands in next group
10447 F3 Back to MAIN Alpine menu
10448 F4 Change configuration for filter
10449 F5 Move to previous filter F5 Include file in filter config
10450 F6 Move to next filter F6 Exclude file from config
10451 F7 Previous page of filters
10452 F8 Next page of filters
10453 F9 Add new filter F9 Replicate existing filter
10454 F10 Delete existing filter
10455 F11 Shuffle the order of filters
10456 F12 Whereis (search filter nicknames)
10460 Navigation General Alpine Commands
10461 ------------------------- -----------------------
10462 P Prev Filter ? Display this help text
10463 N Next Filter E Back to MAIN Alpine menu
10465 Spc (space bar) Next page
10466 W WhereIs (search for word in filter nicknames)
10468 Setup Filters Commands
10469 ------------------------------------------------
10470 A Add new filter $ Shuffle the order of filters
10471 D Delete existing filter C Change configuration for highlighted filter
10472 R Replicate existing filter
10473 I Include file in filter config X Exclude file from filter config
10477 <H2>Description of the Setup Filtering Screen</H2>
10479 This screen lets you add, delete, modify, or change the order of the rules
10480 that determine the filtering Alpine does on folders you view.
10482 The software that actually delivers mail (the stuff that happens
10483 before Alpine is involved) for you is in a better position to do mail filtering
10484 than Alpine itself.
10485 If possible, you may want to look into using that sort of mail filtering to
10486 deliver mail to different folders, delete it, or forward it.
10487 However, if you'd like Alpine to help with this, Alpine's filtering is for you.
10489 Filtering is a way to automatically move certain messages from one folder
10490 to another or to delete messages.
10491 It can also be used to set message status (Important, Deleted, New,
10492 Answered) and to set <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> for messages.
10493 Alpine doesn't have the ability to forward mail to another address or
10494 to deliver vacation messages.
10496 Each filtering rule has a "Pattern" and a "Filter Action".
10497 When a folder is opened, when new mail arrives in an open folder, or
10498 when mail is Expunged from a folder; each
10499 message is compared with the Patterns of your filtering rules.
10500 The comparisons start with the first rule and keep going until there
10502 If a match is found, the message may be deleted or moved, depending on
10503 the setting of the Filter Action.
10504 If the message is not deleted, it may have its status altered.
10508 When setting up a Pattern used to delete messages,
10509 it is recommended that you test the Pattern first with a "Move"
10510 folder specified in
10511 case unintended matches occur. Messages that are deleted will be removed
10512 from the folder and <EM>unrecoverable</EM> from within Alpine after the
10513 next Expunge command or once the folder being filtered has been closed.
10515 <H2>Filter Patterns</H2>
10517 In order to determine whether or not a message matches a filter the message is
10518 compared with the Filter's Pattern.
10519 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10520 Scoring, Other Rules, and Search Rules, so are described in only one place,
10521 "<A HREF="h_rule_patterns">here</A>".
10523 Since filtering is a potentially destructive action, if you have a filtering
10524 Pattern with nothing other than Current Folder Type set, that filtering
10527 <H2>Filter Actions</H2>
10529 Once a filter match is found for a particular message, there are some actions
10531 First, the message may have its status changed.
10532 This is the same message status that you can manipulate manually using the
10533 <a href="h_common_flag">Flag Command</a>.
10534 There are always four elements of message status that you can control.
10535 You can set or clear the Important status, the New status, the Deleted
10536 status, and the Answered status.
10537 Of course, if the filter is going to delete the message,
10538 then there is no point in setting message status.
10539 You may also be able to set user-defined keywords for a message.
10540 Read a little about keywords in the help text for the
10541 <A HREF="h_common_flag">Flag</A> command.
10543 Second, the filter may delete or move the message.
10544 Deleting the message marks it Deleted and removes it from view.
10545 It is effectively gone forever (though it technically is still there until
10546 the next expunge command, which may happen implicitly).
10547 Moving the message moves it from the open folder into the folder
10548 listed on the "Folder List" line of the filter configuration.
10549 If you list more than one folder name (separated by commas) then the message
10550 will be copied to each of those folders.
10551 In any case, if "Delete" or "Move" is set then the
10552 message is removed from the current folder.
10553 If you just want to set the messages status without deleting it from
10554 the folder, then set the filter action to
10555 "Just Set Message Status".
10557 (There is no way to do a Copy instead of a Move, due to the difficulties
10558 involved in keeping track of whether or not a message has
10559 already been copied.)
10561 <H2>Command Descriptions</H2>
10565 The Add command is used to add a new filter definition to your set of
10567 The new filter will be added after the highlighted filter.
10571 The Delete command deletes the currently highlighted filter.
10575 The Change command lets you edit the nickname, Pattern,
10576 and Folder of the currently highlighted filter.
10580 The Shuffle command allows you to change the order of the filters.
10581 You may move the currently highlighted filter up or down in the list.
10582 The order of the filters is important since the filters are tested for a
10583 match starting with the first filter and continuing until a match is found.
10584 You should place the filters with more specific Patterns near the beginning
10585 of the list, and those with more general Patterns near the end so that
10586 the more specific matches will happen when appropriate.
10590 The Replicate command is used to copy an existing filter and modify it.
10591 The new filter will be added after the highlighted filter.
10593 <H3>IncludeFile</H3>
10595 The IncludeFile command allows you to add a filters file to your configuration.
10596 Usually, your filters will be contained in your Alpine configuration file.
10597 If you wish, some or all of your filters may be stored in a separate file.
10598 If a filters file already exists (maybe it was made by somebody else using
10599 Alpine), you may insert it before the currently highlighted filter.
10600 You may also insert an empty file or a file that does not yet exist.
10601 Once you have an empty filters file in your configuration, you may use
10602 the Shuffle command to move filters into it.
10603 In fact, that's the only way to get the initial filter into the file.
10605 <H3>eXcludeFile</H3>
10607 The eXcludeFile command removes a filters file from your filters configuration.
10608 A limitation of the program is that in order to exclude a filters file
10609 that file must have at least one filter
10610 in it, otherwise you won't be able to highlight a line in the file.
10611 So you may have to add a dummy filter to the file in order to exclude the file.
10613 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10616 <H3>Performance Considerations</H3>
10617 The number and type of patterns being tested can
10618 adversely effect performance. Issues to be aware
10622 <LI> The more filters you have defined the longer it will take to run down
10623 the list. Deleting unused filters is a good idea.
10624 <LI> Filtering in newsgroups served by an NNTP server will be slow
10625 if your patterns include tests other than "From:"
10626 or "Subject:".
10629 <End of help on this topic>
10632 ===== h_rules_score =====
10635 <TITLE>SETUP SCORING SCREEN</TITLE>
10638 <H1>SETUP SCORING SCREEN</H1>
10639 <H2>SETUP SCORING COMMANDS</H2>
10640 <!--chtml if pinemode="function_key"-->
10642 Available Commands -- Group 1 Available Commands -- Group 2
10643 ------------------------------- ------------------------------
10644 F1 Show Help Text F1 Show Help Text
10645 F2 See commands in next group F2 See commands in next group
10646 F3 Back to MAIN Alpine menu
10647 F4 Change configuration for rule
10648 F5 Move to previous rule F5 Include file in rule config
10649 F6 Move to next rule F6 Exclude file from config
10650 F7 Previous page of rules
10651 F8 Next page of rules
10652 F9 Add new rule F9 Replicate existing rule
10653 F10 Delete existing rule
10654 F11 Shuffle the order of rules
10655 F12 Whereis (search rule nicknames)
10659 Navigation General Alpine Commands
10660 ------------------------- -----------------------
10661 P Prev rule ? Display this help text
10662 N Next rule E Back to MAIN Alpine menu
10664 Spc (space bar) Next page
10665 W WhereIs (search for word in rule nicknames)
10667 Setup Scoring Commands
10668 ------------------------------------------------
10669 A Add new rule $ Shuffle the order of rules
10670 D Delete existing rule C Change configuration for highlighted rule
10671 R Replicate existing rule
10672 I Include file in rule config X Exclude file from rule config
10676 <H2>Description of the Setup Scoring Screen</H2>
10678 Most people will not use scores at all, but if you do use them, here's how
10679 they work in Alpine.
10680 Using this screen, you may define Scoring rules.
10681 The score for a message is calculated by looking at every Score rule defined
10682 and adding up the Score Values for the ones that match the message.
10683 If there are no matches for a message, it has a score of zero.
10684 Message scores may be used a couple of ways in Alpine.
10686 <H3>Sorting by Score</H3>
10688 One of the methods you may use to sort message indexes is to sort by
10690 The scores of all the messages in a folder will be calculated and then
10691 the index will be ordered by placing the messages in order of ascending or
10694 <H3>Scores for use in Patterns</H3>
10696 The Patterns used for Roles, Index Line Coloring, and Filtering have a
10697 category labeled "Score Interval".
10698 When a message is being compared with a Pattern to check for a match, if
10699 the Score Interval is set only messages that have a score somewhere in
10700 the interval are a match.
10702 <H2>Scoring Rule Patterns</H2>
10704 In order to determine whether or not a message matches a scoring rule
10705 the message is compared with the rule's Pattern.
10706 These Patterns are the same for use with Roles, Filtering, Index Coloring,
10707 Scoring, Other Rules, and Search Rules, so are described in only one place,
10708 "<A HREF="h_rule_patterns">here</A>".
10711 Actually, Scoring rule Patterns are slightly different from the other types of
10712 Patterns because Scoring rule Patterns don't contain a Score Interval.
10713 In other words, when calculating the score for a message, which is done
10714 by looking at the Scoring rule Patterns, scores aren't used.
10716 <H2>Score Value</H2>
10718 This is the value that will be added to the score for a message if the
10719 rule's Pattern is a match.
10720 Each individual Score Value is an integer between -100 and 100, and the
10721 values from matching rules are added together to get a message's score.
10722 There is also a way to extract the value from a particular header of each
10723 message. See the help text for Score Value for further information.
10725 <H2>Command Descriptions</H2>
10729 The Add command is used to add a new scoring rule definition.
10730 The new rule will be added after the highlighted rule.
10734 The Delete command deletes the currently highlighted scoring rule.
10738 The Change command lets you edit the nickname, Pattern,
10739 and Score Value of the currently highlighted scoring rule.
10743 The Shuffle command allows you to change the order of the scoring rules.
10744 You may move the currently highlighted rule up or down in the list.
10745 The order of the rules is important since the rules are tested for a
10746 match starting with the first rule and continuing until a match is found.
10747 You should place the rules with more specific Patterns near the beginning
10748 of the list, and those with more general Patterns near the end so that
10749 the more specific matches will happen when appropriate.
10753 The Replicate command is used to copy an existing rule and modify it.
10754 The new rule will be added after the highlighted rule.
10756 <H3>IncludeFile</H3>
10758 The IncludeFile command allows you to add a rules file to your configuration.
10759 Usually, your rules will be contained in your Alpine configuration file.
10760 If you wish, some or all of your rules may be stored in a separate file.
10761 If a rules file already exists (maybe it was made by somebody else using
10762 Alpine), you may insert it before the currently highlighted rule.
10763 You may also insert an empty file or a file that does not yet exist.
10764 Once you have an empty rules file in your configuration, you may use
10765 the Shuffle command to move rules into it.
10766 In fact, that's the only way to get the initial rule into the file.
10768 <H3>eXcludeFile</H3>
10770 The eXcludeFile command removes a rules file from your rules configuration.
10771 A limitation of the program is that in order to exclude a rules file
10772 that file must have at least one rule
10773 in it, otherwise you won't be able to highlight a line in the file.
10774 So you may have to add a dummy rule to the file in order to exclude the file.
10776 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10779 <End of help on this topic>
10782 ===== h_direct_config =====
10785 <TITLE>SETUP LDAP DIRECTORY SERVERS SCREEN</TITLE>
10788 <H1>SETUP LDAP DIRECTORY SERVERS SCREEN</H1>
10789 <H2>SETUP LDAP DIRECTORY SERVERS COMMANDS</H2>
10790 <!--chtml if pinemode="function_key"-->
10793 -------------------------------
10795 F3 Back to MAIN Alpine menu
10796 F4 Change configuration for directory server
10797 F5 Move to previous directory server
10798 F6 Move to next directory server
10799 F7 Previous page of directory servers
10800 F8 Next page of directory servers
10801 F9 Add new directory server
10802 F10 Delete existing directory server
10803 F11 Shuffle the order of directory servers
10804 F12 Whereis (search directory server titles)
10808 Navigation General Alpine Commands
10809 ------------------------- -----------------------
10810 P Prev Directory Server ? Display this help text
10811 N Next Directory Server E Back to MAIN Alpine menu
10813 Spc (space bar) Next page
10814 W WhereIs (search for word in directory server titles)
10816 Setup LDAP Directory Server Commands
10817 ------------------------------------------------
10818 A Add new directory server $ Shuffle the order of directory servers
10819 D Delete existing dir server C Change configuration for highlighted server
10823 <H2>Description of the Setup LDAP Directory Servers Screen</H2>
10825 This screen lets you add, delete, modify, or change the order of your
10826 directory servers. You may also set some optional behavior for each server.
10827 The "Add Dir" command brings up a blank form to
10828 fill in. You will have to supply at least the name of the LDAP server.
10829 You will often have to supply a search base to be used with that server,
10830 as well. Once the form has been brought up on your screen, there is help
10831 available for each of the options you may set.
10833 The "Del Dir" command allows you to remove a directory server
10834 from your configuration.
10836 The "Change" command is similar to the "Add Dir" command.
10837 The difference is that instead of bringing up a form for a new server
10838 configuration, you are changing the configuration of an existing entry.
10839 For example, you might want to correct a typing error, change a
10840 nickname, or change one of the options set for that server.
10842 The "Shuffle" command is used to change the order of directory
10845 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
10848 <End of help on this topic>
10851 ============= h_address_display ========================
10854 <TITLE>SEARCH RESULTS INDEX</TITLE>
10857 <H1>SEARCH RESULTS INDEX</H1>
10858 This screen shows the results, if any, of your Directory Server search.
10859 Commands (besides those for screen navigation) are:
10862 <!--chtml if pinemode="function_key"-->
10868 <DD>See the full information for the selected entry.
10871 <!--chtml if pinemode="function_key"-->
10875 <!--chtml endif--></DT>
10876 <DD>Compose a message with the selected entry as the recipient.
10879 <!--chtml if pinemode="function_key"-->
10883 <!--chtml endif--></DT>
10884 <DD>Compose a message with the selected entry as the recipient. This differs
10885 from Compose in that you may select a role before beginning your composition.
10888 <!--chtml if pinemode="function_key"-->
10892 <!--chtml endif--></DT>
10893 <DD>Send the full information for the selected entry as an
10894 email message to someone else.
10897 <!--chtml if pinemode="function_key"-->
10903 <DD>Save to your address book:
10905 <LI>the result of the search (as just found through your query) for the
10907 <LI>the selected entry for repeated Directory Server searching when used
10911 Export to a file (external to Alpine):
10913 <LI>the full information for the selected entry; or
10914 <LI>the email address from the selected entry; or
10915 <LI>the selected entry in <A HREF="h_whatis_vcard">vCard</A> format.
10918 <!--chtml if pinemode="function_key"-->
10924 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10925 displayed text, not the full records for each entry.)
10927 <End of help on this topic>
10930 ============= h_address_select ========================
10933 <TITLE>SEARCH RESULTS INDEX</TITLE>
10936 <H1>SEARCH RESULTS INDEX</H1>
10937 This screen shows the results, if any, of your Directory Server search.
10938 Commands (besides those for screen navigation) are:
10942 <DD>Select this entry for use.
10945 <DD>Exit without selecting any of the entries.
10949 <DD>Search for text in the SEARCH RESULTS INDEX screen. (Searches only the
10950 displayed text, not the full records for each entry.)
10952 <End of help on this topic>
10955 ===== h_folder_maint =====
10958 <TITLE>Help for Folder List</TITLE>
10961 <H1>FOLDER LIST COMMANDS</H1>
10962 <!--chtml if pinemode="function_key"-->
10964 Available Commands -- Group 1 Available Commands -- Group 2
10965 ------------------------------- ------------------------------
10966 F1 Show Help Text F1 Show Help Text
10967 F2 See commands in next group F2 See commands in next group
10968 F3 MAIN MENU Screen F3 Quit Alpine
10969 F4 Select folder and view it F4 MAIN MENU Screen
10970 F5 Move to previous folder
10971 F6 Move to next folder F6 Specify a folder to go to
10972 F7 Show previous screen of listing F7 Show MESSAGE INDEX of current folder
10973 F8 Show next screen of listing F8 Compose a message
10974 F9 Add a new folder F9 Print folder listing
10975 F10 Delete selected folder
10976 F11 Rename selected folder
10977 F12 Whereis (search folder names)
10979 Available Commands -- Group 3
10981 F2 See commands in next group
10982 F5 Go to next new message
10983 (or count recent messages if <A HREF="h_config_tab_checks_recent"><!--#echo var="FEAT_tab-checks-recent"--></A> is set)
10984 F8 Compose a message using roles
10985 F9 Export folder to a file
10986 F10 Import the file back to a folder
10990 Navigating the Folder Screen Operations on the Selected Folder
10991 ---------------------------- ---------------------------------
10992 P Move to previous folder V View Index of selected folder
10993 N Move to next folder D Delete
10994 - Show previous page of listing R Rename
10995 Spc (space bar) Show next page E Export to file
10996 U Import from file to folder
10998 FOLDER LIST Screen Commands General Alpine Command
10999 --------------------------- -----------------------
11000 A Add a folder O Show all other available commands
11001 G Specify a folder to go to ? Show Help text
11002 I Show MESSAGE INDEX of current folder M MAIN MENU Screen
11003 W Whereis (search folder names) Q Quit Alpine
11004 % Print folder listing C Compose a message
11005 # Compose a message using roles
11009 These commands are only available in the FOLDER LIST screen when the
11010 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"
11011 feature</A> is set in the SETUP CONFIGURATION screen:<DL>
11013 <DD>Select folders by certain criteria:<UL>
11014 <LI>All: of limited use, since there is no Apply command.
11015 <LI>by Property: <UL>
11016 <LI>folder contains messages not yet seen
11017 <LI>folder contains new messages
11018 <LI>folder contains exactly as many, more, or fewer messages
11019 than a given number
11022 <LI>contained in name of folder (Name Select)
11023 <LI>contained in messages in folder (Content Select)
11027 <DT>Select current:</DT>
11028 <DD>Select the folder the cursor is on. (Can be used to "manually"
11029 add one or more folders to a set created with the Select command described
11031 <DT>Zoom mode:</DT>
11032 <DD>Toggles display of only selected folders or all folders on and off.</DD>
11036 <A HREF="h_config_tab_checks_recent">"<!--#echo var="FEAT_tab-checks-recent"-->"</A>
11037 is set then the TAB key will display the number of recent messages and
11038 the total number of messages in the highlighted folder.
11040 The "Export" command causes the lowest common denominator style
11041 mailbox to be written to a file.
11042 If the file already exists, you are asked if you want to delete it.
11043 If you say No, then the operation is aborted.
11044 Export might be a reasonable way to store a backup or an archival copy of
11046 The exported-to file is a local file on the system where you are running Alpine.
11047 The "Import" command is the opposite of the Export command.
11048 It reads a file created by Export and asks where it should save it in your
11050 This could be a new folder or an existing folder.
11051 If the folder already exists, the messages from the exported file will be
11052 appended to the folder.
11054 <CENTER>Description of the FOLDER LIST Screen</CENTER>
11056 The purpose of the FOLDER LIST screen is to help you browse and manage
11057 the folders and directories (also known as "hierarchy")
11058 contained within a collection.
11061 Folders and directories are arranged alphabetically across lines of
11062 the screen. Directories, if present, are denoted by a special
11063 character at the end of the name known as the hierarchy delimiter
11064 (typically, "/"). By default, folders and directories are
11065 mixed together. The
11066 "<A HREF="h_config_fld_sort_rule"><!--#echo var="VAR_folder-sort-rule"--></A>"
11067 configuration option can be used to group directories toward the
11068 beginning or end of the list.
11071 The Next/Prev Page commands help browse the list, the Next/Prev Fldr
11072 commands change the "selected" (i.e., highlighted) folder or
11073 directory, and the View Fldr/Dir commands will "open" the
11074 selected item. Folder and directory management is provided via the
11075 Rename, Delete and Add commands.
11077 <P><CENTER>About Folders</CENTER>
11078 What are Folders?<P>
11080 Folders are simply files where messages are kept. Every message has to be
11081 in a folder. Most every Alpine user starts out with 3 folders: an INBOX, a
11082 folder for sent mail and a folder for saved messages.<P>
11084 You may create as many other folders as you wish. They must be given
11085 names that can be filenames on the filesystem.
11088 You can move messages from one folder to another by opening the original
11089 folder and saving messages into the other folder just as you can save
11090 message from your INBOX to any other folder.<P>
11092 Folders are typically just files in the filesystem. However, the files
11094 folders have some special formatting in them (so that Alpine knows where one
11095 message ends and another begins) and should <EM>not</EM> be edited outside of
11096 Alpine. If you want copies of your messages in text files that you can edit
11097 or otherwise manipulate, use the Export command to copy them from Alpine into
11098 your regular file area.
11101 FOR MORE INFORMATION: See the section on
11102 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11104 <CENTER>About Directories</CENTER>
11106 A directory is simply a container used to group folders within a
11107 folder list. You can create as many directories as you like. And
11108 directories can even contain directories themselves.
11111 SPECIAL NOTES: When accessing folders on an IMAP server, it is important
11112 to note that not all IMAP servers support directories. If you find that
11113 the Add command fails to offer the "Create Directory" subcommand,
11114 then it's likely that directories are not supported by the server serving
11115 in that collection.
11118 Similarly, servers that do provide for directories may not do so in
11119 the same way. On some servers, for example, each folder name you
11120 create is at the same time capable of being a directory. When this
11121 happens, Alpine will display both the folder name and the name of the
11122 directory (with trailing hierarchy delimiter) in the folder list.
11125 Another issue with IMAP access, though with a much smaller set of servers,
11126 is that not all servers accept the request to list out the available
11127 folders and directories in the same way. If you find yourself having
11128 trouble viewing folders on your server, you might investigate the
11129 "<A HREF="h_config_lame_list_mode"><!--#echo var="FEAT_enable-lame-list-mode"--></A>"
11133 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11136 <End of help on this topic>
11139 ========= h_valid_folder_names ========
11142 <TITLE>Explanation of Valid Folder Names</TITLE>
11145 <H1>Folder Name Syntax Explained</H1>
11147 Once your folder collections are defined, you can usually refer to
11148 folders by their simple (unqualified) name, or pick from a FOLDER LIST
11149 display. However, understanding the complete syntax for folder names,
11150 both local and remote, is handy when using the Goto command and when
11151 you are adding new folder collections via the Setups/collectionList screen.
11153 An Alpine folder name looks like
11156 <CENTER><SAMP>[{<remote-specification>}][#<namespace>]<namespace-specific-part></SAMP></CENTER>
11159 The square brackets ([]) mean that the part is optional.
11162 If there is no remote-specification, then the folder name is interpreted
11163 locally on the computer running Alpine.
11164 Local folder names depend on the operating system used by the computer
11165 running Alpine, as well as the configuration of that system. For example,
11166 "C:\PINE\FOLDERS\OCT-94" might exist on a PC, and
11167 "~/mail/september-1994" might be a reasonable folder name on a
11168 system running Unix.
11171 Alpine users have the option of using folders that are stored on some other
11172 computer. Alpine accesses remote folders via IMAP (the Internet Message
11173 Access Protocol), or in the case of news, via NNTP (the Network News
11174 Transport Protocol). To be able to access remote folders in Alpine, the
11175 remote host must be running the appropriate server software (imapd or
11176 nntpd) and you must correctly specify the name of the folder to Alpine,
11177 including the domain name of the remote machine. For example,
11179 <CENTER><SAMP>{monet.art.example.com}INBOX</SAMP></CENTER>
11181 could be a remote folder specification, and so could
11183 <CENTER><SAMP>{unixhost.art.example.com}~/mail/september-1994</SAMP></CENTER>
11186 <CENTER><SAMP>{winhost.art.example.com}\mymail\SEP-94</SAMP></CENTER>
11188 Note that in the case of remote folders, the directory/file path in the specification is
11189 determined by the operating system of the remote computer, <B>not</B> by
11190 the operating system of the computer on which you are running Alpine.
11192 As you can tell, the name of the computer is in {} brackets
11193 followed immediately by the name of the folder. (In each of these cases the
11194 optional namespace is missing.) If, as in these
11195 examples, there is no remote access protocol specified, then IMAP is
11197 <A HREF="h_folder_server_syntax">here</A>
11198 for a more detailed look at what options can be placed between the brackets.
11199 If there are no brackets at all, then the folder name is interpreted locally
11200 on the computer on which you are running Alpine.
11203 To the right of the brackets when a server name is present, or at the
11204 start of the foldername if no server is present, the sharp sign,
11205 "#", holds special meaning. It indicates a folder name
11206 outside the area reserved for your personal folders. In fact, it's
11207 used to indicate both the name of the folder, and a special phrase
11208 telling Alpine how to interpret the name that follows.
11211 So, for example, Alpine can be used to access a newsgroup that might be
11212 available on your computer using:
11214 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11216 The sharp sign indicates the folder name is outside your personal
11217 folder area. The "news." phrase after it tells Alpine to
11218 interpret the remainder of the name as a newsgroup.
11221 Similarly, to access a newsgroup on your IMAP server, you might
11222 use something like:
11224 <CENTER><SAMP>{wharhol.art.example.com}#news.comp.mail.misc</SAMP></CENTER>
11227 There are a number of such special phrases (or "namespaces")
11228 available. For a more detailed explanation read about
11229 <A HREF="h_folder_name_namespaces">Namespaces</A>.
11232 Note that "INBOX" has special meaning in both local and remote folder
11233 names. The name INBOX refers to your "principal incoming
11234 message folder" and will be mapped to the actual file name used for your
11235 INBOX on any given host. Therefore, a name like
11236 "{xxx.art.example.com}INBOX" refers to whatever file is used to
11237 store incoming mail for you on that particular host.
11240 <End of help on this topic>
11243 ======= h_folder_name_namespaces =======
11246 <TITLE>FOLDER NAME NAMESPACES EXPLAINED</TITLE>
11249 <H1>Folder Name Namespaces Explained</H1>
11251 An Alpine folder name looks like
11254 <CENTER><SAMP>[{<remote-specification>}][#<namespace>][<namespace-specific-part>]</SAMP></CENTER>
11257 The local part of a folder name has an optional "Namespace" which
11258 tells Alpine how to interpret the rest of the name.
11261 By default the folder name is interpreted as defining a section of your personal
11262 folder area. This area and how you specify it are defined by the
11263 server, if one is specified, or, typically, the home
11264 directory, if no server is defined.
11267 If a namespace is specified, it begins with the
11268 sharp, "#", character followed by the name of the namespace
11269 and then the namespace's path-element-delimiter. Aside from the
11270 path's format, namespaces can also imply access rights, content
11271 policy, audience, location, and, occasionally, access methods.
11274 Each server exports its own set (possibly of size one) of
11275 namespaces. Hence, it's likely communication with your server's
11276 administrator will be required for specific configurations. Some of
11277 the more common namespaces, however, include:
11281 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
11282 names are hierarchically defined with each level delimited by a period.
11284 <CENTER><SAMP>#news.comp.mail.pine</SAMP></CENTER>
11288 <DD>This specifies a folder area that the server may export to the general
11292 <DD>This specifies a folder area that the server may export to groups
11296 <DD>This specifies a folder area that is the same as that it may have
11297 exported via the "File Transfer Protocol".
11300 <DD>This specifies the personal folder area associated with folders
11301 and directories that were created using the MH message handling system.
11304 <DD>This namespace is interpreted locally by Alpine. It has an unusual interpretation and format.
11306 <CENTER><SAMP>#move<DELIM><MailDropFolder><DELIM><DestinationFolder></SAMP></CENTER>
11308 The #move namespace is followed by two folder names separated by a delimiter
11310 The delimiter character may be any character that does not appear in
11311 the MailDropFolder name.
11312 The meaning of #move is that mail will be copied from the MailDropFolder to
11313 the DestinationFolder and then deleted (if possible) from the MailDropFolder.
11314 Periodic checks at frequency
11315 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A>, but with a minimum
11316 time between checks set by
11317 <A HREF="h_config_maildropcheck"><!--#echo var="VAR_maildrop-check-minimum"--></A>,
11318 are made for new mail arriving in the MailDropFolder.
11319 An example that copies mail from a POP inbox to a local folder follows
11321 <CENTER><SAMP>#move+{popserver.example.com/pop3/ssl}inbox+local folder</SAMP></CENTER>
11323 To you it appears that mail is being delivered to the local folder when it
11324 is copied from the MailDropFolder, and you read mail from the local folder.
11326 Note that if the DestinationFolder does not exist then the messages are not
11327 copied from the MailDropFolder.
11328 A #move folder may only be used as an
11329 <A HREF="h_config_enable_incoming">"Incoming folder"</A> or
11331 When you are in the FOLDER LIST of Incoming Message Folders (after turning
11333 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
11335 the Add command has a subcommand "Use Mail Drop"
11336 which may be helpful for defining the folder in your Alpine configuration.
11337 The same is true when you edit the
11338 <A HREF="h_config_inbox_path"><!--#echo var="VAR_inbox-path"--></A>
11339 option in Setup/Config.
11340 Each of these configuration methods will also create the DestinationFolder
11341 if it doesn't already exist.
11342 If you are having problems, make sure the DestinationFolder exists.
11343 You may find some more useful information about Mail Drops at
11344 <A HREF="h_maildrop">What is a Mail Drop?</A>.
11349 In addition, the server may support access to other user's folders,
11350 provided you have suitable permissions. Common methods use a prefix
11351 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
11352 indicate the root of the other user's folder area.
11355 No, nothing's simple.
11358 <End of help on this topic>
11361 ============= h_whatis_vcard ========================
11364 <TITLE>VCARD EXPLAINED</TITLE>
11367 <H1>What is the vCard format?</H1>
11368 A "vCard" is a sort of electronic business card, for exchanging
11369 information about and among people and organizations electronically.
11370 More information about vCard can be found (as of May 1998) on the WWW site
11371 of the Internet Mail Consortium at the URL:
11373 <CENTER><A HREF="http://www.imc.org/pdi/">http://www.imc.org/pdi/</A></CENTER>
11375 <End of help on this topic>
11378 ===== h_folder_open =====
11381 <TITLE>Explanation of Folder Selection</TITLE>
11386 This screen is designed to allow you to quickly and easily survey your
11387 folders and select one to open.
11388 <!--chtml if pinemode="function_key"-->
11390 Navigating the List of Folders General Alpine Commands
11391 ------------------------------ -----------------------
11392 P Move to previous folder ? Show this help text
11393 N Move to next folder
11394 - Show previous screen of folders
11395 Spc (space bar) Show next screen
11396 W WhereIs (search folder names)
11398 Folder Selection Commands
11399 -------------------------
11400 E Exit the Folder Select menu (without selecting a folder)
11401 S Select the currently highlighted folder
11405 Navigating the List of Folders General Alpine Commands
11406 ------------------------------ -----------------------
11407 F5 Move to previous folder F1 Show this help text
11408 F6 Move to next folder
11409 F7 Show previous screen of folders
11410 F8 Show next screen of folders
11411 F12 WhereIs (search folder names)
11413 Folder Selection Commands
11414 -------------------------
11415 F3 Exit the Folder Select menu (without selecting a folder)
11416 F4 Select the currently highlighted folder
11420 FOR MORE INFORMATION: See the section on
11421 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11423 <End of help on this topic>
11426 ===== h_folder_subscribe =====
11429 <TITLE>Newsgroup Subcribe Screen explained</TITLE>
11432 <H1>FOLDER SUBSCRIBE HELP</H1>
11434 This screen is designed to help you subscribe to newsgroups you are
11435 not currently subscribed to. The screen display is a list of all
11436 available newsgroups (or possibly a partial list if you specified a
11437 partial name when entering the screen). Groups you have already
11438 subscribed to have the letters "SUB" next to them. You may
11439 select a single new group to subscribe to by moving the cursor to that
11440 group and pressing "S" or carriage return. Alternatively,
11441 you may change into ListMode with the "ListMode" command.
11442 The display will change slightly so that each group has a checkbox in
11443 front of it. Use the cursor and the Set/Unset command to place an
11444 "X" in front of each newsgroup you wish to subscribe to.
11447 When you are finished marking groups, the "Subscribe"
11448 command will subscribe you to those groups you have marked. Note, you
11449 may not unsubscribe to groups with this command. Instead of the
11450 "A" "Subscribe" command, use the "D"
11454 <!--chtml if pinemode="function_key"-->
11456 Navigating the List of Newsgroups General Alpine Commands
11457 --------------------------------- -----------------------
11458 F5 Move to previous group F1 Show this help text
11459 F6 Move to next group
11460 F7 Show previous screen of groups
11461 F8 Show next screen of groups
11462 F12 WhereIs (search group names)
11465 Group Selection Commands
11466 -------------------------
11467 F3 Exit the News Subscribe menu (without selecting any groups)
11468 F4 Subscribe to the currently highlighted newsgroup
11472 Navigating the List of Newsgroups General Alpine Commands
11473 --------------------------------- -----------------------
11474 P Move to previous group ? Show this help text
11475 N Move to next group
11476 - Show previous screen of groups
11477 Spc (space bar) Show next screen
11478 W WhereIs (search group names)
11481 Group Selection Commands
11482 -------------------------
11483 E Exit the News Subscribe menu (without selecting any groups)
11484 S Subscribe to the currently highlighted newsgroup
11488 When in ListMode, there is an additional command for marking groups to
11491 <!--chtml if pinemode="function_key"-->
11494 -------------------------
11495 F9 Set or unset the highlighted group
11500 -------------------------
11501 X Set or unset the highlighted group
11505 <End of help on this topic>
11508 ===== h_folder_postnews =====
11511 <TITLE>Newsgroup selecting for Posting explained</TITLE>
11514 This screen is designed to allow you to quickly and easily survey
11515 the available newsgroups and select one to post news to.
11517 <!--chtml if pinemode="function_key"-->
11519 Navigating the List of Newsgroups General Alpine Commands
11520 --------------------------------- -----------------------
11521 F5 Move to previous group F1 Show this help text
11522 F6 Move to next group
11523 F7 Show previous screen of groups
11524 F8 Show next screen of groups
11525 F12 WhereIs (search group names)
11527 Group Selection Commands
11528 -------------------------
11529 F3 Exit the Selection menu (without selecting a group)
11530 F4 Select the currently highlighted newsgroup
11534 Navigating the List of Newsgroups General Alpine Commands
11535 --------------------------------- -----------------------
11536 P Move to previous group ? Show this help text
11537 N Move to next group
11538 - Show previous screen of groups
11539 Spc (space bar) Show next screen of groups
11540 W WhereIs (search group names)
11542 Group Selection Commands
11543 -------------------------
11544 E Exit the Selection menu (without selecting a group)
11545 S Select the currently highlighted newsgroup
11549 <End of help on this topic>
11552 ===== h_folder_save =====
11555 <TITLE>Folder Select for Save Explained</TITLE>
11558 This screen is designed to allow you to quickly and easily survey your
11559 folders and select one to use for saving the current message.
11562 <!--chtml if pinemode="function_key"-->
11564 Navigating the List of Folders General Alpine Commands
11565 ------------------------------ -----------------------
11566 F5 Move to previous folder F1 Show this help text
11567 F6 Move to next folder
11568 F7 Show previous screen of folders
11569 F8 Show next screen of folders
11570 F12 WhereIs (search folder names)
11572 Folder Selection Commands
11573 -------------------------
11574 F3 Exit the Folder Select menu (without selecting a folder)
11575 F4 Select the currently highlighted folder
11576 F11 AddNew folder (just like Select, but you type in a new folder name)
11580 Navigating the List of Folders General Alpine Commands
11581 ------------------------------ -----------------------
11582 P Move to previous folder ? Show this help text
11583 N Move to next folder
11584 - Show previous screen of folders
11585 Spc (space bar) Show next screen of folders
11586 W WhereIs (search folder names)
11588 Folder Selection Commands
11589 -------------------------
11590 E Exit the Folder Select menu (without selecting a folder)
11591 S Select the currently highlighted folder
11592 A AddNew folder (just like Select, but you type in a new folder name)
11596 FOR MORE INFORMATION: See the section on
11597 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11599 <End of help on this topic>
11602 ===== h_folder_fcc =====
11605 <TITLE>Folder Select for Fcc Explained</TITLE>
11608 This screen is designed to allow you to quickly and easily survey your
11609 folders and select one to use as the file carbon copy (fcc) for the
11613 <!--chtml if pinemode="function_key"-->
11615 Navigating the List of Folders General Alpine Commands
11616 ------------------------------ -----------------------
11617 F5 Move to previous folder F1 Show this help text
11618 F6 Move to next folder
11619 F7 Show previous screen of folders
11620 F8 Show next screen of folders
11621 F12 WhereIs (search folder names)
11623 Folder Selection Commands
11624 -------------------------
11625 F3 Exit the Folder Select menu (without selecting a folder)
11626 F4 Select the currently highlighted folder
11627 F11 AddNew folder (just like Select, but you type in a new folder name)
11631 Navigating the List of Folders General Alpine Commands
11632 ------------------------------ -----------------------
11633 P Move to previous folder ? Show this help text
11634 N Move to next folder
11635 - Show previous screen of folders
11636 Spc (space bar) Show next screen of folders
11637 W WhereIs (search folder names)
11639 Folder Selection Commands
11640 -------------------------
11641 E Exit the Folder Select menu (without selecting a folder)
11642 S Select the currently highlighted folder
11643 A AddNew folder (just like Select, but you type in a new folder name)
11647 FOR MORE INFORMATION: See the section on
11648 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11650 <End of help on this topic>
11653 ===== h_folder_pattern_roles =====
11656 <TITLE>Folder Select for Current Folder Explained</TITLE>
11659 This screen is designed to allow you to quickly and easily survey your
11660 folders and select one to use as the specific Current Folder
11664 <!--chtml if pinemode="function_key"-->
11666 Navigating the List of Folders General Alpine Commands
11667 ------------------------------ -----------------------
11668 F5 Move to previous folder F1 Show this help text
11669 F6 Move to next folder
11670 F7 Show previous screen of folders
11671 F8 Show next screen of folders
11672 F12 WhereIs (search folder names)
11674 Folder Selection Commands
11675 -------------------------
11676 F3 Exit the Folder Select menu (without selecting a folder)
11677 F4 Select the currently highlighted folder
11678 F11 AddNew folder (just like Select, but you type in a new folder name)
11682 Navigating the List of Folders General Alpine Commands
11683 ------------------------------ -----------------------
11684 P Move to previous folder ? Show this help text
11685 N Move to next folder
11686 - Show previous screen of folders
11687 Spc (space bar) Show next screen of folders
11688 W WhereIs (search folder names)
11690 Folder Selection Commands
11691 -------------------------
11692 E Exit the Folder Select menu (without selecting a folder)
11693 S Select the currently highlighted folder
11694 A AddNew folder (just like Select, but you type in a new folder name)
11698 FOR MORE INFORMATION: See the section on
11699 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11701 <End of help on this topic>
11704 ===== h_folder_stayopen_folders =====
11707 <TITLE>Folder Select Explained</TITLE>
11710 This screen is designed to allow you to quickly and easily survey your
11711 folders and select one to use as a Stay-Open folder.
11714 <!--chtml if pinemode="function_key"-->
11716 Navigating the List of Folders General Alpine Commands
11717 ------------------------------ -----------------------
11718 F5 Move to previous folder F1 Show this help text
11719 F6 Move to next folder
11720 F7 Show previous screen of folders
11721 F8 Show next screen of folders
11722 F12 WhereIs (search folder names)
11724 Folder Selection Commands
11725 -------------------------
11726 F3 Exit the Folder Select menu (without selecting a folder)
11727 F4 Select the currently highlighted folder
11728 F11 AddNew folder (just like Select, but you type in a new folder name)
11732 Navigating the List of Folders General Alpine Commands
11733 ------------------------------ -----------------------
11734 P Move to previous folder ? Show this help text
11735 N Move to next folder
11736 - Show previous screen of folders
11737 Spc (space bar) Show next screen of folders
11738 W WhereIs (search folder names)
11740 Folder Selection Commands
11741 -------------------------
11742 E Exit the Folder Select menu (without selecting a folder)
11743 S Select the currently highlighted folder
11744 A AddNew folder (just like Select, but you type in a new folder name)
11748 FOR MORE INFORMATION: See the section on
11749 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11751 <End of help on this topic>
11754 ===== h_folder_action_roles =====
11757 <TITLE>Folder Select Explained</TITLE>
11760 This screen is designed to allow you to quickly and easily survey your
11761 folders and select one to use as the folder into which messages
11762 matching this filter will be moved.
11765 <!--chtml if pinemode="function_key"-->
11767 Navigating the List of Folders General Alpine Commands
11768 ------------------------------ -----------------------
11769 F5 Move to previous folder F1 Show this help text
11770 F6 Move to next folder
11771 F7 Show previous screen of folders
11772 F8 Show next screen of folders
11773 F12 WhereIs (search folder names)
11775 Folder Selection Commands
11776 -------------------------
11777 F3 Exit the Folder Select menu (without selecting a folder)
11778 F4 Select the currently highlighted folder
11779 F11 AddNew folder (just like Select, but you type in a new folder name)
11783 Navigating the List of Folders General Alpine Commands
11784 ------------------------------ -----------------------
11785 P Move to previous folder ? Show this help text
11786 N Move to next folder
11787 - Show previous screen of folders
11788 Spc (space bar) Show next screen of folders
11789 W WhereIs (search folder names)
11791 Folder Selection Commands
11792 -------------------------
11793 E Exit the Folder Select menu (without selecting a folder)
11794 S Select the currently highlighted folder
11795 A AddNew folder (just like Select, but you type in a new folder name)
11799 FOR MORE INFORMATION: See the section on
11800 <A HREF="h_valid_folder_names">Valid Folder Names</A>.
11802 <End of help on this topic>
11805 ===== h_abook_config =====
11808 <TITLE>SETUP ADDRESS BOOKS SCREEN</TITLE>
11811 <H1>SETUP ADDRESS BOOKS SCREEN</H1>
11812 <H2>SETUP ADDRESS BOOKS COMMANDS</H2>
11813 <!--chtml if pinemode="function_key"-->
11816 -------------------------------
11818 F3 Back to MAIN Alpine menu
11819 F4 Change configuration for address book
11820 F5 Move to previous address book
11821 F6 Move to next address book
11822 F7 Previous page of address books
11823 F8 Next page of address books
11824 F9 Add new address book
11825 F10 Delete existing address book
11826 F11 Shuffle the order of address books
11827 F12 Whereis (search address book titles)
11831 Navigation General Alpine Commands
11832 ----------------------- -----------------------
11833 P Prev Address Book ? Display this help text
11834 N Next Address Book E Back to MAIN Alpine menu
11836 Spc (space bar) Next page
11837 W WhereIs (search for word in address book titles)
11839 Setup Address Books Commands
11840 ------------------------------------------------
11841 A Add new address book $ Shuffle the order of address books
11842 D Delete existing address book C Change configuration for address book
11846 <H2>Description of the Setup Address Books Screen</H2>
11848 This screen lets you add, delete, modify, or change the order of your
11849 address books. The "Add Abook" command brings up a blank form to
11850 fill in. If you are adding a remote address book on an IMAP server
11851 you should fill in the name of the IMAP server. Otherwise, leave
11852 that field blank. (Note that remote IMAP address books are an Alpine
11853 concept and are unlikely to interoperate with other mail clients.)
11854 For a remote address book, fill in the name of the remote folder
11855 in the Folder field. This should be a folder that is used only for
11856 this one purpose, not a general purpose folder you expect to store
11858 <P>If you are adding a local address book, fill in the
11859 Folder Name field with a local file name (e.g., .addressbook).
11861 <B>Please note:</B> Remote address books stored on an IMAP server are
11862 of an entirely different format (namely, a special-purpose
11863 "mail folder") than that of the local addressbook familiar
11864 to Alpine users. Therefore,
11865 you cannot use "add a remote address book" to make an existing
11866 Alpine .addressbook file you may have on a remote IMAP server accessible to
11867 Alpine running on a different host.
11870 The "Del Abook" command allows you to remove an address book
11871 from your configuration. It will also ask you if you wish to remove
11872 the data for that address book, which would erase all traces of the
11873 address book if you answer Yes.
11876 The "Change" command is similar to the "Add Abook" command.
11877 The difference is that instead of adding a new address book to your
11878 configuration, you are changing the configuration of an existing entry.
11879 For example, you might want to correct a typing error or change a
11880 nickname. The "Change" command is not a move command. If you
11881 change the folder name or server name the data will not be moved for you.
11884 The "Shuffle" command is used for two purposes. If you shuffle
11885 an address book toward another address book in the same group then
11886 the order of those two address books will be swapped. If you shuffle
11887 the last Personal address book down towards the Global address book
11888 section, it will become a Global address book. If you shuffle
11889 the first Global address book up it will become a Personal address
11890 book. The main difference between Personal and Global address
11891 books is that Global address books are forced read-only.
11893 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11896 <End of help on this topic>
11899 ===== h_abook_top =====
11902 <TITLE>ADDRESS BOOK LIST COMMANDS</TITLE>
11905 <H1>ADDRESS BOOK LIST COMMANDS</H1>
11906 <!--chtml if pinemode="function_key"-->
11908 Available Commands -- Group 1 Available Commands -- Group 2
11909 ------------------------------- ------------------------------
11910 F1 Show Help Text F1 Show Help Text
11911 F2 See commands in next group F2 See commands in next group
11912 F3 Exit to MAIN MENU F3 Quit Alpine
11913 F4 View/Edit selected address book
11914 F5 Move to previous address book F5 FOLDER LIST screen
11915 F6 Move to next address book F6 Specify a folder to go to
11916 F7 Previous page F7 MESSAGE INDEX screen
11917 F8 Next page F9 Print list of address books
11918 F12 Whereis (search for word)
11922 Navigation General Alpine Commands
11923 ----------------------- -----------------------
11924 P Previous Entry ? Display this help text
11925 N Next Entry O Show all other available commands
11926 - Previous page < Back to MAIN Alpine menu
11927 Spc (space bar) Next page Q Quit Alpine
11928 W WhereIs (search for word) L FOLDER LIST screen
11929 G Specify a folder to go to
11930 Address Book Commands I MESSAGE INDEX screen
11931 ------------------------------------------------
11932 > View/Edit selected address book
11934 > Search on selected directory server
11936 % Print list of address books and directory servers
11940 <H2>Description of the Address Book List Screen</H2>
11942 From this screen you may choose which address book you wish to view
11943 or edit. For more information on address books, view one of your
11944 address books (with
11945 <!--chtml if pinemode="function_key"-->
11949 <!--chtml endif-->)
11950 and see the Help Text there.<P>
11952 You may also choose a directory server on which to search for entries.
11953 You do that by highlighting the directory server line and using
11954 <!--chtml if pinemode="function_key"-->
11958 <!--chtml endif-->.<P>
11960 If you wish to define new address books or directory servers go to the Main
11961 menu and choose Setup. You may then either choose to setup AddressBooks or
11962 Directory (among other things). It's possible that the Directory option
11963 will not be there if the Alpine you are using does not contain LDAP directory
11964 lookup functionality.
11967 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
11969 <End of help on this topic>
11972 ===== h_abook_opened =====
11975 <TITLE>THE ALPINE ADDRESS BOOK</TITLE>
11978 <H1>THE ALPINE ADDRESS BOOK</H1>
11979 <H2>ADDRESS BOOK COMMANDS</H2>
11981 <!--chtml if pinemode="function_key"-->
11982 Available Commands -- Group 1 Available Commands -- Group 2
11983 ------------------------------- ------------------------------
11984 F1 Show Help Text F1 Show Help Text
11985 F2 See commands in next group F2 See commands in next group
11986 F3 Exit this screen F3 Quit Alpine
11987 F4 View/Edit selected entry F4 Go to MAIN MENU screen
11988 F5 Move to previous entry F5 FOLDER LIST screen
11989 F6 Move to next entry F6 Specify a folder to go to
11990 F7 Previous page of address book F7 MESSAGE INDEX screen
11991 F8 Next page of address book F8 Compose to entry using roles
11992 F9 Add new entry to address book F9 Print address book
11993 F10 Delete selected entry F10 TakeAddr to another addrbook
11994 F11 Compose to selected entry F11 Save or Export addrbook selections
11995 F12 Whereis (search address book) F12 Forward entry by mail
11997 Available Commands -- Group 3
11998 ------------------------------
11999 F3 Select F6 Zoom (or unZoom)
12000 F5 Select Current F7 Apply Command to Selection
12002 Address Book Navigation General Alpine Commands
12003 ----------------------- -----------------------
12004 P Prev Address ? Display this help text
12005 N Next Address O Show all other available commands
12006 - Previous page of address book M Back to MAIN MENU
12007 Spc (space bar) Next page Q Quit Alpine
12008 W WhereIs (search for word C Compose message to selected addr
12009 or name in address book) # Compose to addr using roles
12010 < To List of Address Books if L FOLDER LIST screen
12011 more than one, else to MAIN G Specify a folder to go to
12012 I MESSAGE INDEX screen
12014 Address Book Commands
12015 ----------------------------------------------------
12016 > View/Update selected entry D Delete selected entries
12017 % Print address book S Save or Export address book selections
12018 F Forward entries by mail @ Add new entry to address book
12020 ; Select command Z Toggle Zoom Mode
12021 : Select highlighted entry A Apply command to selected entries
12025 Note: The presence or absence of the final four commands above is
12026 controlled by the option
12027 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>.
12030 <H2>Description of the Address Book Screen</H2>
12032 This screen lets you edit and manage entries in your address book. It
12033 also acts as a short-cut for composing messages to people in the address
12034 book. When, from this screen, you press <!--chtml if pinemode="function_key"-->F11<!--chtml else-->"C"<!--chtml endif--> for ComposeTo, the
12035 message starts "pre-addressed" to whatever address book entry is
12036 currently selected. If you use the <!--chtml if pinemode="function_key"-->F8<!--chtml else-->"#"<!--chtml endif--> for Role, you may first select a
12037 role to use in your composition.
12039 Alpine's address book helps you keep a list of addresses you send email to so
12040 you do not have to remember addresses that are often complex. Each entry
12041 in the address book has five fields, all of them optional. The three
12042 elements that are usually visible on the ADDRESS BOOK display, are: <DL>
12044 <P><DT>NICKNAME: <DD>A short easy-to-remember label to identify the entry.
12045 This is what you type in as you are addressing the message in the
12046 composer. If there is a matching entry in your address book(s),
12047 Alpine will extract the corresponding FullName and Address fields to
12048 generate the actual address for your message.
12050 <P><DT>FULLNAME: <DD>A longer field where you can put the full name
12052 person or organization. Usually the full names are put in last
12053 name first so they sort nicely in alphabetical order. Whatever
12054 you put as the name here will appear on the message when it is
12055 finally delivered. Examples:<PRE>
12056 Garcia Marquez, Gabriel
12058 Alpine-Info mailing list
12059 Library materials renewal requests
12061 "George III, King of Great Britain, 1738-1820"
12063 (In the second-to-last example, no comma is used in the name so that
12064 the family name appears first in the address book and when the entry is
12065 used in the composer.
12066 In the last example, retaining the commas is intended;
12067 double-quotation marks surround the name to
12068 prevent the transposition of its parts when the entry is used in
12071 <P><DT>ADDRESS: <DD>This is the actual email address itself. This must be
12072 a valid Internet address that conforms to the Internet message
12073 header standard, RFC-822. (See also <A HREF="h_address_format">Explanation of Address formats</A>.)</DL>
12075 The two fields that aren't usually visible are:<DL>
12077 <P><DT>FCC: <DD>The name of the folder you would like a copy of any outgoing
12078 message to this address to be saved in. If this field is set, and
12079 this address is the first one in the message's To: header, then
12080 Alpine will use this folder name for the FCC in lieu of the normal
12083 <P><DT>COMMENTS: <DD>This field contains arbitrary text for your convenience.
12086 Due to screen width limitations, these last two fields do not show up in
12087 the normal ADDRESS BOOK display. You may select the
12088 "View/Update" command to
12089 view or modify them. You may use the configuration variable
12090 <A HREF="h_config_abook_formats">"<!--#echo var="VAR_addressbook-formats"-->"</A>
12091 to add these fields to your ADDRESS BOOK
12092 display, or to modify the format of the display.
12094 <H2>Sorting the Address book</H2>
12096 By default, address book entries are sorted alphabetically on the full
12097 name with distribution lists sorted to the end. Sorting can be changed by
12098 resetting the address book sort rule in the Alpine SETUP CONFIGURATION screen
12099 --assuming you have "write" permission for the address book file.
12101 Unlike the sorting of folders (which only changes presentation), sorting an
12102 address book actually changes the file as it is kept on the computer. For
12103 this reason you won't be able to sort a shared or system-wide address
12106 <H2>Adding New Entries</H2>
12108 The easiest way to add new entries to your address book is to use the
12109 "TakeAddr" command when viewing a message.
12110 This command allows you to take addresses from the header and body of the
12111 message and put them into your address book, without having to type
12115 To manually add a new entry from within the address book screen, use the AddNew
12116 (<!--chtml if pinemode="function_key"-->F9<!--chtml else-->"@"<!--chtml endif-->) command.
12117 Use this command both for adding a simple alias and for adding a
12120 <H2>Distribution Lists</H2>
12122 Address book entries can be simple cases of aliases (a single nickname is linked
12123 to a single email address) or distribution lists (a single nickname
12124 pointing at more than one email address). Each distribution list has a
12125 nickname, a full name and a list of addresses. The addresses may be
12126 actual addresses or they may be other nicknames in your address book.
12127 They may even refer to other distribution lists.
12128 There's really no difference between a simple alias and a distribution list,
12129 other than the number of addresses.
12130 Therefore, you can turn a simple alias with one address into a distribution
12131 list simply by adding more addresses.
12132 To add entries to an existing list or alias
12133 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
12134 a single address from the list if the cursor is placed on the address;
12135 it will delete the entire distribution list if the cursor is on the
12136 nickname/fullname line. View/Update may also be used to delete addresses
12139 Address field entries in distribution lists may take any one of three
12140 forms: a nickname existing in any of the defined address books, a normal
12141 address of the form "jsmith@art.example.com", or a complete
12142 fullname/address combination, e.g. "John Smith
12143 <jsmith@art.example.com>".
12145 Distribution lists in Alpine address books can only be used by the person or
12146 people who have access to that address book. They are not usually used to
12147 implement discussion groups, but can be used to facilitate small
12148 discussion groups if all the participants have access to the same shared
12151 <H2>FCC and Comments</H2>
12153 As mentioned above, each entry in the address book also has two other optional
12154 fields, Fcc and Comments. The command to look at or change either of these
12155 is the same View/Update command used for all of the fields (<!--chtml if pinemode="function_key"-->F4<!--chtml else-->">"<!--chtml endif-->). The
12156 Comments field is just for your own use. The Fcc field overrides the
12157 default Fcc if this address is the first one on the To line. The WhereIs
12158 command may be used to search for particular strings in the address book,
12159 including fields that are not visible (like Comment and Fcc by default).
12161 <H2>Aggregate Operations</H2>
12164 <A HREF="h_config_enable_agg_ops">"<!--#echo var="FEAT_enable-aggregate-command-set"-->"</A>
12165 is turned on (the default), then the four commands "Select",
12166 "Select Current", "Zoom", and "Apply"
12167 are available. The two selection commands allow you to mark a set of
12168 address book entries as being selected. If you have more than one address
12169 book, the selections may be in more than one of those address books.
12170 The "Zoom" command will toggle between displaying only the selected
12171 entries and all of the entries. The "Apply" command allows you to
12172 apply one of the regular address book commands to all of the selected
12173 entries. Usually the address book commands apply to only the entry
12174 highlighted by the cursor. The "Apply" command works with the
12175 commands "ComposeTo", "Delete", "Print",
12176 "Save", "Forward", and "Role".
12178 <H2>Exporting and Forwarding Address book entries</H2>
12180 Under the save option, when you use the Export (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->"X"<!--chtml endif-->) command, the currently highlighted
12181 address book entry is placed in a plain text file in your home directory
12182 <!--chtml if pinemode="running"-->
12183 (which, in the present configuration of your system, is
12184 "<!--#echo var="HOME_DIR"-->")
12186 or current working directory
12187 <!--chtml if pinemode="running"-->
12188 (which, at least for your current Alpine "session,"
12189 is "<!--#echo var="CURRENT_DIR"-->")
12190 <!--chtml endif-->, depending on the
12191 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
12192 configuration setting. If you have some entries selected and use the
12193 Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Export command, all of the selected addresses will be
12194 placed in the text file.
12196 When you use the Forward (<!--chtml if pinemode="function_key"-->F12<!--chtml else-->"F"<!--chtml endif-->) command, the currently highlighted
12197 address book entry is placed in a special attachment and you are put into
12198 the composer. You can fill in some comments in the body of the message,
12199 if you'd like, and send it to somebody else who uses Alpine. The recipient
12200 may use the TakeAddr command on that message to insert the address book
12201 entry you sent in their own address book. If you have some entries
12202 selected and use the Apply Forward command all of the selected entries
12203 will be forwarded in a single message. You may
12204 use Apply (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->"A"<!--chtml endif-->) Forward to forward a copy of an entire address book.
12205 The recipient must be using Alpine in order to receive this correctly.
12206 One way for the recipient to handle this might be to create an empty
12207 address book and then "Take" your forwarded address book entries into
12208 that empty address book.
12210 <H2>Multiple and/or Site-Wide Address books</H2>
12212 You may have more than one personal address book. In addition, there may
12213 be one or more global address books. This capability allows you to have
12214 multiple personal address books (some of which may be shared) and it also
12215 allows system administrators to implement site-wide address books that
12216 contain entries for users on multiple machines within the organization.
12219 <DD> If you enter a nickname when composing a message, your
12220 personal address books will be searched through in order, and then the
12221 global address book(s) searched. If more than one address book has an entry
12222 for the nickname, Alpine uses the first one that it finds, so an entry in
12223 your personal address book would override a global address book entry. If
12224 after searching all the address books there is still no match, (Unix) Alpine
12225 then searches the local host password file on the assumption that you have
12226 entered a local user name rather than an address book nickname.
12227 You may change the search order of your address books with the <!--chtml if pinemode="function_key"-->F3<!--chtml else-->$<!--chtml endif--> Shuffle
12228 command, but global address books are always searched after personal
12231 <P><DT>Tab completion
12233 <A HREF="h_config_enable_tab_complete"><!--#echo var="FEAT_enable-tab-completion"--></A>
12234 feature is turned on (the default) then the Tab key may be used
12235 in the composer to complete partially typed nicknames in the To
12236 or Cc lines. You type the first few letters of a nickname and then
12237 press the Tab key. It there is only one nickname that matches it will
12238 be filled in by Alpine. If there is more than one the unambiguous part
12239 of the nicknames will be filled in. For example, if your address book or
12240 books contains only the two entries "barley" and "barbecue"
12241 beginning with the letters "ba", then if you type "ba"
12242 followed by a Tab character Alpine will fill in "bar" and stop.
12243 If you then type a second Tab character you will be presented with a list
12244 of matching nicknames to select from. Alternatively, you could type another
12245 "b" resulting in "barb" and then a Tab would fill
12246 in the entire "barbecue" entry.
12249 <DD> You define multiple personal address books in the
12250 <A HREF="h_abook_config">SETUP AddressBooks</A> screen, which you may reach
12251 from the MAIN MENU.
12252 You may add as many as you like. Global address books are usually
12253 site-wide address books defined by the System administrator, but
12254 you may define global address books of your own just like you define
12255 personal address books.
12257 <P><DT>Creating and updating
12258 <DD> Personal address books are normally created empty
12259 and populated by explicit additions from within Alpine, e.g. via the
12260 TakeAddr command. Unlike personal address books, global address books may
12261 not be modified/updated from within Alpine; that is, they are Read-Only.
12262 Thus, global address books are created, populated and updated outside of
12263 Alpine. They might be hand-edited, generated by a program from another
12264 database, or by copying an existing address book. They might also be
12265 some other user's personal address book, and so be modified normally by
12266 that user but accessed Read-Only by you. See the Alpine Technical
12267 Notes document (included in the Alpine distribution) for more information on
12271 <DD>There are two different types of address books in Alpine.
12272 A local address book is stored in a regular file and the normal file
12273 access permissions apply. A remote address book is stored on an IMAP
12274 server in a special folder that contains only messages pertaining to
12275 that address book. The last message in the remote folder contains a
12276 copy of the address book data, and that data is copied to a local cache
12277 file in your home directory. From there it is accessed just like a local
12278 address book. The name of the cache file is kept track of in a special
12280 <A HREF="h_config_abook_metafile"><!--#echo var="VAR_remote-abook-metafile"--></A>,
12281 the name of which is stored in
12282 your Alpine configuration file the first time you use a remote address book.
12283 Just as local Alpine address books use a format that only Alpine understands,
12284 remote Alpine address books do the same and other mail reading programs
12285 are unlikely to be able to understand them.<P>
12286 While global address books are explicitly intended to be shared, there is
12287 nothing to prevent you from sharing a personal address book with other
12288 Alpine users. This might be useful in the case of a small workgroup.
12289 However, it is recommended that updates to shared personal address books
12290 be done when other Alpine users are not accessing the address book. Alpine
12291 does not do any file-locking to manage concurrent updates to the
12292 addressbook, but it does check to see if the file has been modified before
12293 making any changes. Consequently, inadvertent concurrent updates will
12294 only cause other Alpine users to have to restart their address book
12295 operation, which will cause Alpine to reopen the updated file.
12297 <P><DT>Converting to Remote
12298 <DD>The easiest way to convert an existing local
12299 address book into a remote address book is to create an empty new remote
12300 personal address book by typing "A" to execute the
12301 "Add Pers Abook" command in the SETUP Addressbook screen.
12302 Make sure you add a <EM>personal</EM> address book, not a <EM>global</EM>
12304 After you have added the empty
12305 remote address book, go into the screen for the address book you wish
12306 to copy and "Select" "All".
12307 This selects every entry in that
12308 address book. Then type the command "Apply Save".
12309 You will be asked for the address book to save to. You may use ^P and ^N
12310 to get to the new empty address book, then hit RETURN and the addresses
12312 At this point you'll probably want to unselect all the entries in the local
12313 address book before proceeding. You do that with
12314 "Select" "unselect All".
12318 <LI><A HREF="h_address_format">Explanation of Address formats</A>
12321 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
12324 <End of help on this topic>
12327 ===== h_abook_select_addr =====
12330 <TITLE>Addressbook Selection Explained</TITLE>
12333 <H1>SELECT ADDRESS</H1>
12334 <!--chtml if pinemode="function_key"-->
12336 Navigating the List of Messages General Alpine Commands
12337 ------------------------------- -----------------------
12338 F5 Move to previous entry F1 Show this help text
12339 F6 Move to next entry
12340 F7 Show previous screen of address book
12341 F8 Show next screen of address book
12342 F12 WhereIs (search through address book)
12344 Address Selection Commands
12345 --------------------------
12346 F3 Exit the Address Select screen (without selecting an address)
12347 F4 Select the currently highlighted entry
12351 Navigating the List of Messages General Alpine Commands
12352 ------------------------------- -----------------------
12353 P Move to previous entry ? Show this help text
12354 N Move to next entry
12355 - Show previous screen of address book
12356 Spc (space bar) Show next screen of address book
12357 W WhereIs (search through address book)
12359 Address Selection Commands
12360 --------------------------
12361 E Exit the Address Select screen (without selecting an address)
12362 S Select the currently highlighted entry
12367 This screen is designed to let you easily scan your address book(s) in
12368 order to select an entry for the message you are composing. You cannot
12369 edit your address book in any way at this time, for address book
12370 maintenance, select the address book command when not composing a message.
12373 If you are composing a message and know the nickname of the person/list you
12374 want, you can bypass this screen by simply typing in the nickname on the
12375 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12376 selecting an entry does not cancel your message.
12379 FOR MORE INFORMATION on addressing see
12380 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12381 <A HREF="h_abook_opened">Address Book Screen's</A>
12384 <End of help on this topic>
12387 ===== h_abook_select_top =====
12390 <TITLE>Addressbook Selection Navigation Explained</TITLE>
12393 <H1>NAVIGATING WHILE SELECTING ADDRESSES</H1>
12394 <!--chtml if pinemode="function_key"-->
12396 Navigating the List of Address Books General Alpine Commands
12397 ------------------------------------ -----------------------
12398 F4 View the highlighted address book
12399 F5 Move to previous address book F1 Show this help text
12400 F6 Move to next address book
12401 F7 Show previous screen of address books
12402 F8 Show next screen of address books
12403 F12 WhereIs (search through address books)
12405 Address Selection Commands
12406 --------------------------
12407 F3 Exit the Address Select screen (without selecting an address)
12408 F4 Select the currently selected entries (if using ListMode)
12409 F9 Change to ListMode
12413 Navigating the List of Address Books General Alpine Commands
12414 ------------------------------------ -----------------------
12415 > View the highlighted address book
12416 P Move to previous address book ? Show this help text
12417 N Move to next address book
12418 - Show previous screen of address books
12419 Spc (space bar) Show next screen of address books
12420 W WhereIs (search through address books)
12422 Address Selection Commands
12423 --------------------------
12424 E Exit the Address Select screen (without selecting an address)
12425 S Select the currently selected entries (if using ListMode)
12426 L Change to ListMode
12431 This screen is designed to let you easily scan your address book(s) in
12432 order to select entries for the message you are composing. You cannot
12433 edit your address book in any way at this time. For address book
12434 maintenance, select the address book command when not composing a message.
12437 If you are composing a message and know the nickname of the person/list you
12438 want, you can bypass this screen by simply typing in the nickname on the
12439 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12440 selecting an entry does not cancel your message.
12443 The ListMode command will add a column at the left edge of the screen.
12444 You mark the entries that you wish to select with the "X" command.
12445 This allows you to choose more than one entry at a time.
12448 An alternative method of composing a message to entries in your
12449 address book(s) is to first use the "Select" command from
12450 the address book maintenance screen and then the "Apply"
12451 "ComposeTo" command to start the composer composing to the
12455 FOR MORE INFORMATION on addressing see
12456 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12457 <A HREF="h_abook_opened">Address Book Screen's</A>
12460 <End of help on this topic>
12463 ===== h_abook_select_listmode =====
12466 <TITLE>Address Listmode Selection from Composer Explained</TITLE>
12469 <H1>COMPOSER: SELECT ADDRESSES</H1>
12470 <!--chtml if pinemode="function_key"-->
12472 Navigating the List of Messages General Alpine Commands
12473 ------------------------------- -----------------------
12474 F5 Move to previous entry F1 Show this help text
12475 F6 Move to next entry
12476 F7 Show previous screen of address book
12477 F8 Show next screen of address book
12478 F12 WhereIs (search through address book)
12480 Address Selection Commands
12481 --------------------------
12482 F3 Exit the Address Select screen (without selecting an address)
12483 F4 Select the currently highlighted entry
12484 F9 Change to ListMode
12488 Navigating the List of Messages General Alpine Commands
12489 ------------------------------- -----------------------
12490 P Move to previous entry ? Show this help text
12491 N Move to next entry
12492 - Show previous screen of address book
12493 Spc (space bar) Show next screen of address book
12494 W WhereIs (search through address book)
12496 Address Selection Commands
12497 --------------------------
12498 E Exit the Address Select screen (without selecting an address)
12499 S Select the currently highlighted entry
12500 L Change to ListMode
12505 This screen is designed to let you easily scan your address book(s) in
12506 order to select entries for the message you are composing. You cannot
12507 edit your address book in any way at this time, for address book
12508 maintenance, select the address book command when not composing a message.
12511 If you are composing a message and know the nickname of the person/list you
12512 want, you can bypass this screen by simply typing in the nickname on the
12513 appropriate header line (To:, Cc:, etc.) Exiting this screen without
12514 selecting an entry does not cancel your message.
12517 The ListMode command will add a column at the left edge of the screen.
12518 You mark the entries that you wish to select with the "X" command.
12519 This allows you to choose more than one entry at a time.
12522 An alternative method of composing a message to entries in your
12523 address book(s) is to first use the "Select" command from
12524 the address book maintenance screen and then the "Apply"
12525 "ComposeTo" command to start the composer composing to the
12529 FOR MORE INFORMATION on addressing see
12530 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12531 <A HREF="h_abook_opened">Address Book Screen's</A>
12534 <End of help on this topic>
12537 ===== h_abook_select_checks =====
12540 <TITLE>Address Selection from Composer Explained</TITLE>
12543 <H1>COMPOSER: SELECT ADDRESSES</H1>
12544 <!--chtml if pinemode="function_key"-->
12546 Navigating the List of Messages General Alpine Commands
12547 ------------------------------- -----------------------
12548 F5 Move to previous entry F1 Show this help text
12549 F6 Move to next entry
12550 F7 Show previous screen of address book
12551 F8 Show next screen of address book
12552 F12 WhereIs (search through address book)
12554 Address Selection Commands
12555 --------------------------
12556 F3 Exit the Address Select screen (without selecting an address)
12557 F4 Select the currently highlighted entry
12558 F8 Either Sets or Unsets all entries in this address book
12559 F9 Set or Unset the highlighted entry
12563 Navigating the List of Messages General Alpine Commands
12564 ------------------------------- -----------------------
12565 P Move to previous entry ? Show this help text
12566 N Move to next entry
12567 - Show previous screen of address book
12568 Spc (space bar) Show next screen of address book
12569 W WhereIs (search through address book)
12571 Address Selection Commands
12572 --------------------------
12573 E Exit the Address Select screen (without selecting an address)
12574 S Select the currently highlighted entry
12575 X Set or Unset the highlighted entry
12576 A Either Sets or Unsets all entries in this address book
12581 Mark the entries you wish to select with the "X Set/Unset"
12582 command. Type "S Select" to select all of the entries you
12583 have marked, just as if you had typed them in by hand.
12586 An alternative method of composing a message to entries in your
12587 address book(s) is to first use the "Select" command from
12588 the address book maintenance screen and then the "Apply"
12589 "ComposeTo" command to start the composer composing to the
12593 FOR MORE INFORMATION on addressing see
12594 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12595 <A HREF="h_abook_opened">Address Book Screen's</A>
12598 <End of help on this topic>
12601 ===== h_abook_select_nicks_take =====
12604 <TITLE>Take Address Nickname Selection Explained</TITLE>
12607 <H1>TAKEADDR: SELECT NICKNAME</H1>
12608 <!--chtml if pinemode="function_key"-->
12610 Navigating the List of Messages General Alpine Commands
12611 ------------------------------- -----------------------
12612 F5 Move to previous entry F1 Show this help text
12613 F6 Move to next entry
12614 F7 Show previous screen of address book
12615 F8 Show next screen of address book
12616 F12 WhereIs (search through address book)
12618 Message Selection Commands
12619 --------------------------
12620 F3 Exit the Nickname Select screen (without selecting an address)
12621 F4 Select the currently highlighted entry
12625 Navigating the List of Messages General Alpine Commands
12626 ------------------------------- -----------------------
12627 P Move to previous entry ? Show this help text
12628 N Move to next entry
12629 - Show previous screen of address book
12630 Spc (space bar) Show next screen of address book
12631 W WhereIs (search through address book)
12633 Message Selection Commands
12634 --------------------------
12635 E Exit the Nickname Select screen (without selecting an address)
12636 S Select the currently highlighted entry
12641 This screen is designed to let you modify or add to an existing
12642 address book entry. You have already selected the name(s) and
12643 address(es) through "Take Address". This screen simply lets
12644 you scan your address books and select the nickname to be
12645 changed/augmented. If you want to add a new entry, then you are in
12646 the wrong place-- Select "Exit" command.
12649 FOR MORE INFORMATION on addressing see
12650 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12651 <A HREF="h_abook_opened">Address Book Screen's</A>
12654 <End of help on this topic>
12657 ===== h_abook_select_nick =====
12660 <TITLE>Nickname Selection Explained</TITLE>
12663 <H1>SELECT NICKNAME</H1>
12664 <!--chtml if pinemode="function_key"-->
12666 Navigating the List of Messages General Alpine Commands
12667 ------------------------------- -----------------------
12668 F5 Move to previous entry F1 Show this help text
12669 F6 Move to next entry
12670 F7 Show previous screen of address book
12671 F8 Show next screen of address book
12672 F12 WhereIs (search through address book)
12674 Message Selection Commands
12675 --------------------------
12676 F3 Exit the Nickname Select screen (without selecting an address)
12677 F4 Select the currently highlighted entry
12681 Navigating the List of Messages General Alpine Commands
12682 ------------------------------- -----------------------
12683 P Move to previous entry ? Show this help text
12684 N Move to next entry
12685 - Show previous screen of address book
12686 Spc (space bar) Show next screen of address book
12687 W WhereIs (search through address book)
12689 Message Selection Commands
12690 --------------------------
12691 E Exit the Nickname Select screen (without selecting an address)
12692 S Select the currently highlighted entry
12697 This screen is designed to let you look at the nicknames in your address
12698 books before choosing a new one.
12701 FOR MORE INFORMATION on addressing see
12702 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12703 <A HREF="h_abook_opened">Address Book Screen's</A>
12706 <End of help on this topic>
12709 ===== h_takeaddr_screen =====
12712 <TITLE>Take Address Screen Explained</TITLE>
12715 <H1>TAKE ADDRESS COMMANDS</H1>
12716 <!--chtml if pinemode="function_key"-->
12718 Navigating the List of Addresses Address Selection Commands
12719 -------------------------------- --------------------------
12720 F5 Move to previous entry F3 Exit without taking address
12721 F6 Move to next entry F4 Take current address(es)
12722 F7 Show previous page of address list
12723 F8 Show next page of address list
12724 F2 WhereIs (search list)
12726 Mode Toggle F9 Set/Unset current address
12727 ----------- F10 Set all
12728 F12 Toggle between List and single mode F11 Unset all
12732 Navigating the List of Addresses Address Selection Commands
12733 -------------------------------- --------------------------
12734 P Move to previous entry < Exit without taking address
12735 N Move to next entry T Take address
12736 - Show previous page of address list
12737 Spc (space bar) Show next page of address list
12738 W WhereIs (search list) List Mode
12740 Single Mode X Set/Unset current address
12741 ----------- A Set all addresses
12742 L Switch to list mode U Unset all addresses
12743 S Switch to single mode
12747 <H2>Description of the Take Address Screen</H2>
12749 This screen is designed to let you select one or more address/name
12750 combinations from the current message and put them into your address book.
12751 The cursor is initially placed on the line with the message author.
12752 Other lines include the names of people and/or mailing lists who also
12753 received the message. Other people "involved" in the
12754 message (e.g. the person named as Reply-To:) are also listed here.
12757 The simple case is adding a new, single entry into your address book. To
12758 do this, simply highlight the correct line and press
12759 <!--chtml if pinemode="function_key"-->
12764 To create a new list or add to an existing list, switch the screen display
12765 into List Mode by pressing
12766 <!--chtml if pinemode="function_key"-->
12771 In List Mode, you select the
12772 group of addresses you wish to manipulate by marking them with an
12775 <!--chtml if pinemode="function_key"-->
12780 command will turn the "X" on for the
12781 highlighted address if it was off or turn it off if it was previously on.
12782 The SetAll command will select all of the addresses, and the UnSetAll
12783 command will turn off all the selections. Once you've gotten the
12784 selection the way you want it, you may create a new list by pressing
12785 <!--chtml if pinemode="function_key"-->
12792 In both the simple and list cases, after choosing to take the address,
12793 you will be asked for the nickname of the entry. Typing in a new name
12794 creates the new entry/list. Entering an existing nickname will replace
12795 the entry (simple case) or add to the list (list case). Alternatively,
12796 you can press Ctrl-T at the nickname prompt and select an existing
12797 nickname from your address book.
12800 You will normally start in Single Mode, unless you used the Apply command
12801 to startup the TakeAddr screen, in which case you will start in List Mode.
12802 You may switch between the two modes at any time. If you've already
12803 selected several addresses in List Mode, those will be remembered when you
12804 switch to Single Mode and then back to List Mode. The set of addresses
12805 that are pre-selected when you start in List Mode are the From addresses
12806 of all of the messages you are operating on. You may, of course, easily
12807 erase those selections with the UnSetAll command.
12810 If you have more than one writable address book, you will be prompted for
12811 the name of the address book you wish to add the new entry to before
12812 anything else. You can use ^N and ^P to choose among the defined address
12813 books, or type in the address book name.
12816 FOR MORE INFORMATION on addressing see
12817 <A HREF="h_address_format">Explanation of Address formats</A>, and the
12818 <A HREF="h_abook_opened">Address Book Screen's</A>
12821 <End of help on this topic>
12824 ===== h_takeexport_screen =====
12827 <TITLE>Take Export Screen Explained</TITLE>
12830 <H1>TAKE EXPORT COMMANDS</H1>
12831 <!--chtml if pinemode="function_key"-->
12833 Navigating the List of Addresses Address Selection Commands
12834 -------------------------------- --------------------------
12835 F5 Move to previous entry F3 Exit without taking address
12836 F6 Move to next entry F4 Take current address(es)
12837 F7 Show previous page of address list
12838 F8 Show next page of address list
12839 F2 WhereIs (search list)
12841 Mode Toggle F9 Set/Unset current address
12842 ----------- F10 Set all
12843 F12 Toggle between List and single mode F11 Unset all
12847 Navigating the List of Addresses Address Selection Commands
12848 -------------------------------- --------------------------
12849 P Move to previous entry < Exit without taking address
12850 N Move to next entry T Take address
12851 - Show previous page of address list
12852 Spc (space bar) Show next page of address list
12853 W WhereIs (search list) List Mode
12855 Single Mode X Set/Unset current address
12856 ----------- A Set all addresses
12857 L Switch to list mode U Unset all addresses
12858 S Switch to single mode
12862 <H2>Description of the Take Export Screen</H2>
12864 This screen is designed to let you select one or more addresses
12865 from the current message and put them into a file.
12866 Only the user@domain_name part of each address is put into the file.
12869 To put a single entry into a file simply highlight the correct line and press
12870 <!--chtml if pinemode="function_key"-->
12875 To put more than one entry into a file
12876 switch the screen display
12877 into List Mode by pressing
12878 <!--chtml if pinemode="function_key"-->
12883 In List Mode, you select the
12884 group of addresses you wish to manipulate by marking them with an
12887 <!--chtml if pinemode="function_key"-->
12892 command will turn the "X" on for the
12893 highlighted address if it was off or turn it off if it was previously on.
12894 The SetAll command will select all of the addresses, and the UnSetAll
12895 command will turn off all the selections. Once you've gotten the
12896 selection the way you want it, you may put the addresses in a file by typing
12897 <!--chtml if pinemode="function_key"-->
12904 You will be asked for the name of a file to put the addresses in.
12905 If the file already exists, you will be asked whether you want to Overwrite
12906 (replace) the contents of the file or Append to the contents of the file.
12909 <End of help on this topic>
12912 ============= h_abook_view ========================
12915 <TITLE>Address Book View Explained</TITLE>
12918 This function allows you to view the contents of an address book entry. You
12919 can only view one entry at a time.
12923 <!--chtml if pinemode="function_key"-->
12930 Display this help text.
12933 <!--chtml if pinemode="function_key"-->
12940 Go back to index of address book entries.
12943 <!--chtml if pinemode="function_key"-->
12950 Update (modify) this entry.
12953 <!--chtml if pinemode="function_key"-->
12959 <DD>Compose a message to the address(es) in this entry.
12962 <!--chtml if pinemode="function_key"-->
12968 <DD>Compose a message to the address(es) in this entry using roles.
12971 <!--chtml if pinemode="function_key"-->
12978 Show the previous page of the current entry.
12981 <!--chtml if pinemode="function_key"-->
12988 Show the next page of the current entry.
12991 <!--chtml if pinemode="function_key"-->
12997 <DD>Print the current entry. You can select the
12998 printer or the print command via the "Setup" command
13002 <!--chtml if pinemode="function_key"-->
13008 <DD>Search the entry for a string of letters. If it is
13009 found, move to it. The string can be one word or a phrase.
13010 If there are multiple occurrences, the cursor moves to the
13011 first occurrence beyond the current cursor position.
13014 <!--chtml if pinemode="function_key"-->
13020 <DD>Begin composition of a new mail message with the displayed
13021 text already inserted in the message body.
13025 <End of help on this topic>
13028 ============= h_ldap_view ========================
13031 <TITLE>LDAP Response View Explained</TITLE>
13034 This function allows you to view the contents of a directory entry. You
13035 can only view one entry at a time.
13039 <!--chtml if pinemode="function_key"-->
13046 Display this help text.
13049 <!--chtml if pinemode="function_key"-->
13055 <DD>Go back to index of search results.
13058 <!--chtml if pinemode="function_key"-->
13064 <DD>Compose a message to the address(es) in this entry.
13067 <!--chtml if pinemode="function_key"-->
13073 <DD>Compose a message to the address(es) in this entry using roles.
13076 <!--chtml if pinemode="function_key"-->
13083 Show the previous page of the current entry.
13086 <!--chtml if pinemode="function_key"-->
13093 Show the next page of the current entry.
13096 <!--chtml if pinemode="function_key"-->
13102 <DD>Print the current entry on paper. You can select the
13103 printer or the print command via the "Setup" command
13107 <!--chtml if pinemode="function_key"-->
13113 <DD>Search the entry for a string of letters. If it is
13114 found, move to it. The string can be one word or a phrase.
13115 If there are multiple occurrences, the cursor moves to the
13116 first occurrence beyond the current cursor position.
13119 <!--chtml if pinemode="function_key"-->
13125 <DD>Begin composition of a new mail message with the displayed
13126 text already inserted in the message body.
13129 <!--chtml if pinemode="function_key"-->
13135 <DD>Save the displayed entry to one of your address books or export
13139 <End of help on this topic>
13142 ===== h_attachment_screen =====
13145 <TITLE>Attachment Index Screen Explained</TITLE>
13148 The "ATTACHMENT INDEX" displays a list of the current
13149 message's attachments, and allows various operations on them. The
13150 first attachment is usually the message text, but does not include the
13151 header portion of the message.
13153 Available commands include:
13158 <DD>Show this help text.
13160 <DT>Msg #<I>num</I></DT>
13161 <DD>Leave this screen without displaying or saving any attachments.
13164 <DD>View the currently selected attachment.
13166 <DT>Prev Attach</DT>
13167 <DD>Move to previous attachment.
13169 <DT>Next Attach</DT>
13170 <DD>Move to next attachment.
13173 <DD>Previous page of the listed attachments.
13176 <DD>Next page of the listed attachments.
13179 <DD>Mark the currently selected attachment for Deletion.
13180 This does not modify the current message by deleting the attachment from
13181 it, but instead the delete flag <EM>only</EM> has an effect when saving
13182 the message to a folder.
13183 Attachments marked for deletion are not copied to the destination folder
13184 along with the rest of the message when it is saved.
13185 It is ok for the destination folder to be the same as the current folder.
13186 In addition, the delete mark <EM>only</EM> applies to this Alpine session.
13189 <DD>Turn off the Delete flag for the selected attachment.
13192 <DD>Save the selected attachment to a file. If the attachment is of
13193 type "RFC822/Message", then the attachment will be saved to
13194 the specified mail folder.
13197 <DD>If the attachment is of
13198 type "RFC822/Message", then "Export" is used to
13199 copy the message to a file in the same way this command works on
13200 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13203 <DD>Pipe the attachment contents into a UNIX command (if enabled).
13204 A description of the Pipe sub-commands is <A HREF="h_pipe_command">here</A>.
13207 <DD>Find a matching string in the attachment list.
13209 <DT>AboutAttch</DT>
13210 <DD>Examine various aspects of the selected attachment.
13213 <DD>Print the selected attachment.
13216 <DD>Forward the selected attachment as an attachment.
13221 All attachments can be saved or piped into a UNIX command, but some may
13222 not be readily displayed by either Alpine or an external tool. In such
13223 cases, the reason why the message cannot be displayed is displayed on
13224 Alpine's message line.
13226 <End of help on this topic>
13229 ============= h_mail_text_att_view ========================
13232 <TITLE>Attachment View Screen Explained</TITLE>
13235 This function allows you to view the contents of a text attachment. You
13236 can only view one attachment at a time.
13238 Available commands include:
13243 <DD>Display this help text
13245 <DT>AttchIndex</DT>
13246 <DD>Leave viewer and return to the "ATTACHMENT INDEX" screen
13249 <DD>Show the previous page of the current attachment.
13252 <DD>Show the next page of the current attachment by pressing the space bar.
13255 <DD>Mark the viewed attachment for Deletion. The delete
13256 flag <EM>only</EM> has affect when saving the message to a folder.
13257 Attachments marked for deletion are exluded from the messsage when
13258 it is saved. In addition, the delete mark <EM>only</EM> applies to
13259 this Alpine session.
13262 <DD>Turn off the Delete flag for the selected attachment.
13265 <DD>Copy the current attachment to a file. If you just enter
13266 a filename, the attachment will be saved with that name in
13267 your home directory
13268 <!--chtml if pinemode="running"-->
13269 (which, in the present configuration of your system, is
13270 "<!--#echo var="HOME_DIR"-->")
13272 or current working directory
13273 <!--chtml if pinemode="running"-->
13274 (which, at least for your current Alpine "session,"
13275 is "<!--#echo var="CURRENT_DIR"-->")
13276 <!--chtml endif-->, depending on the
13277 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13278 configuration setting. You may enter the full
13279 path and filename to save it in another directory instead.
13282 <DD>If the attachment is of
13283 type "RFC822/Message", then "Export" is used to
13284 copy the message to a file in the same way this command works on
13285 messages in the MESSAGE INDEX and MESSAGE TEXT screens.
13286 (If you have any <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>
13287 defined, they may affect the contents of the exported file.)
13290 <DD>Pipe the attachment contents into a UNIX command (if enabled)
13293 <DD>Search the attachment for a string of letters. If it is
13294 found, move to it. The string can be one word or a phrase.
13295 If there are multiple occurrences, the cursor moves to the
13296 first occurrence beyond the current cursor position.
13299 <DD>Print the current attachment on paper. You can select the
13300 printer or the print command via the "Setup" command
13304 <DD>Forward the selected attachment as an attachment.
13307 <End of help on this topic>
13310 ============= h_journal ==============
13313 <TITLE>Recent Message Journal Explained</TITLE>
13317 The following commands are available on this screen:
13321 <DD>Show this help text
13324 <DD>Exit Viewer, and go back to mail processing
13327 <DD>Show the previous page text
13330 <DD>Show the next page of text by pressing the space bar
13333 <DD>Print the displayed text on paper. You can select the
13334 printer or the print command via the "Setup" command
13338 <DD>Begin composition of a new mail message with the displayed
13339 text already inserted in the message body.
13342 <DD>Copy the displayed text to a file. If you just enter
13343 a filename, the text will be saved with that name in
13346 <!--chtml if pinemode="running"-->
13347 (which, in the present configuration of your system, is
13348 "<!--#echo var="HOME_DIR"-->")
13350 or current working directory
13351 <!--chtml if pinemode="running"-->
13352 (which, at least for your current Alpine "session,"
13353 is "<!--#echo var="CURRENT_DIR"-->")
13354 <!--chtml endif-->, depending on the
13355 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13356 configuration setting. You may enter the full
13357 path and filename to save it in another directory instead.
13360 <DD>Search the text for a string of letters. If it is
13361 found, move to it. The string can be one word or a phrase.
13362 If there are multiple occurrences, the cursor moves to the
13363 first occurrence beyond the current cursor position.
13366 <End of help on this topic>
13369 ============= h_debugjournal ==============
13372 <TITLE>Debug Journal Explained</TITLE>
13376 The following commands are available on this screen:
13380 <DD>Show this help text
13383 <DD>Exit Viewer, and go back to mail processing
13385 <DT>Timestamps</DT>
13386 <DD>Turn on or off timestamps.
13389 <DD>Set the level of debugging you want to see. The level may be any number
13390 in the range 0-9. Higher numbers show more debugging detail. Note that the
13391 debugging information has already been captured. This setting just causes the
13392 debugging information that you see to be filtered. If you set this to
13393 the number "5" then you will be shown all of the debugging information
13394 at levels 5 and below.
13395 It's actually a bit more complicated than that. A fixed amount of memory
13396 is used to store the debug information.
13397 Since the amount of memory used is limited the debugging information
13398 has to be trimmed back when it gets too large.
13401 <DD>Show the previous page text
13404 <DD>Show the next page of text by pressing the space bar
13407 <DD>Print the displayed text on paper. You can select the
13408 printer or the print command via the "Setup" command
13412 <DD>Begin composition of a new mail message with the displayed
13413 text already inserted in the message body.
13416 <DD>Copy the displayed text to a file. If you just enter
13417 a filename, the text will be saved with that name in
13420 <!--chtml if pinemode="running"-->
13421 (which, in the present configuration of your system, is
13422 "<!--#echo var="HOME_DIR"-->")
13424 or current working directory
13425 <!--chtml if pinemode="running"-->
13426 (which, at least for your current Alpine "session,"
13427 is "<!--#echo var="CURRENT_DIR"-->")
13428 <!--chtml endif-->, depending on the
13429 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13430 configuration setting. You may enter the full
13431 path and filename to save it in another directory instead.
13434 <DD>Search the text for a string of letters. If it is
13435 found, move to it. The string can be one word or a phrase.
13436 If there are multiple occurrences, the cursor moves to the
13437 first occurrence beyond the current cursor position.
13440 <End of help on this topic>
13443 ============= h_simple_text_view ==============
13446 <TITLE>Simple Text View Screen Explained</TITLE>
13450 The following commands are available on this screen:
13454 <DD>Show this help text
13457 <DD>Exit Viewer, and go back to mail processing
13460 <DD>Show the previous page text
13463 <DD>Show the next page of text by pressing the space bar
13466 <DD>Print the displayed text on paper. You can select the
13467 printer or the print command via the "Setup" command
13471 <DD>Begin composition of a new mail message with the displayed
13472 text already inserted in the message body.
13475 <DD>Copy the displayed text to a file. If you just enter
13476 a filename, the attachment will be saved with that name in
13479 <!--chtml if pinemode="running"-->
13480 (which, in the present configuration of your system, is
13481 "<!--#echo var="HOME_DIR"-->")
13483 or current working directory
13484 <!--chtml if pinemode="running"-->
13485 (which, at least for your current Alpine "session,"
13486 is "<!--#echo var="CURRENT_DIR"-->")
13487 <!--chtml endif-->, depending on the
13488 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13489 configuration setting. You may enter the full
13490 path and filename to save it in another directory instead.
13493 <DD>Search the attachment for a string of letters. If it is
13494 found, move to it. The string can be one word or a phrase.
13495 If there are multiple occurrences, the cursor moves to the
13496 first occurrence beyond the current cursor position.
13499 <End of help on this topic>
13502 ======= h_pine_for_windows ========
13505 <TITLE>GETTING HELP IN PC-ALPINE</TITLE>
13508 <H1>Getting Help In PC-Alpine</H1>
13511 PC-Alpine offers general and specific help text. From the <A
13512 HREF="main_menu_tx">MAIN MENU</A>, you will find an overview in the MAIN
13513 MENU HELP and the <A HREF="h_news">Release Notes</A>. On all screens,
13514 specific help for that screen is available from the toolbar Help menu or
13516 <!--chtml if pinemode="function_key"-->
13517 "F1" key.
13519 "?" or "Ctrl-G" keys. "Ctrl-G" is used where
13520 typing "?" would be mistaken as entering text.
13524 Although this version of Alpine is for Microsoft Windows, it is not
13525 considered a full "Graphical User Interface" application.
13526 Yet, many of the controls that Windows users are accustomed to seeing,
13527 such as scrollbars and toolbars, are available.
13530 PC-Alpine offers considerable mouse support. You can view what is
13531 "click-able" by dragging your mouse over any screen; when the
13532 arrow cursor changes into a hand, you found something. Mouse-click
13533 possibilities include navigating between screens and folders and
13534 double-clicking on hyperlinks to open your Web browser.
13535 Context-sensitive pop-up menus appear with a right-click on your PC-Alpine
13536 screen. Examples of right-click options include "copy" after
13537 selecting text to copy and "View in New Window" when you click
13538 on a particular message in the Message Index. The menu choices available
13539 to you will vary based upon what screen is open, where on the screen your
13540 cursor is located, and even what action you have already taken.
13543 <End of help on this topic>
13546 ===== h_composer =====
13549 <TITLE>COMPOSER COMMANDS</TITLE>
13552 <H1>COMPOSER COMMANDS</H1>
13554 CURSOR MOTION KEYS |EDITING KEYS<BR>
13555 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13556 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13557 ^P (Up Arrow) Previous line | ^^ Set a <A HREF="h_compose_markcutpaste">mark</A><BR>
13558 ^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>
13559 ^A Beginning of line | delete current line<BR>
13560 ^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>
13561 ^Y Previous page | cut with ^K, or unjustify<BR>
13562 ^V Next page |-------------------------------------<BR>
13563 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13564 ---------------------------------------| <!--chtml if pinemode="function_key"-->F6<!--chtml else-->^W<!--chtml endif--> <A HREF="h_composer_search">Whereis</A> (search for string)<BR>
13565 MESSAGE COMMANDS | GENERAL COMMANDS | <!--chtml if pinemode="function_key"-->F12<!--chtml else-->^T <!--chtml endif--> <A HREF="h_compose_spell">Spell checker</A><BR>
13566 <!--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>
13567 <!--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>
13568 <!--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>
13573 <LI>For help on a particular command, highlight the bold text associated
13574 with it above and hit Return.
13575 <LI> The availability of certain commands
13576 is determined by Alpine configuration files and system capabilities.
13577 At some sites, certain commands may not be available due to security or
13579 <LI>Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
13581 <LI>For special handling of Ctrl-S and Ctrl-Q see special comments regarding
13582 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
13586 HINT: To move rapidly to the bottom of a message you are composing,
13587 enter ^W^V. To go to the top, ^W^Y. These can be used in conjunction
13588 with the Mark and Cut commands to eliminate large amounts of unwanted
13591 <H2>Description of Composer</H2>
13593 Alpine has a built-in editing program that allows you to compose messages
13594 without having to leave Alpine. The editor is designed to be very simple to
13595 use so that you can get started writing email right away.
13598 Messages are usually just text, about 80 columns wide. Using upper and
13599 lower case is encouraged. On some systems the size limit of the message
13600 is about 100,000 characters, which is about 2,000 lines. You can include
13601 punctuation and special characters found on most keyboards, but you can't
13602 include characters with diacritical marks and certain special symbols.
13605 Text automatically wraps as you type past the end of a line so you do not
13606 have to hit return. Using the
13607 "<A HREF="h_compose_justify">Justify</A>" command,
13608 you can also reformat text explicitly, perhaps after you have
13612 You can include other text files with the
13613 "<A HREF="h_compose_readfile">Read File</A>" command,
13614 which will prompt you for the name of the file to insert at the
13615 current cursor postion.
13619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13622 <End of help on this topic>
13625 ====== h_composer_browse =====
13628 <TITLE>BROWSER</TITLE>
13632 This screen lets you browse your files and directories. To go to another
13633 directory (identified by "(dir)"), move the cursor to it and
13634 choose "Select" (the default choice on the menu);
13635 or choose "Goto" and enter the name of the directory.
13636 <!--chtml if pinemode="os_windows"-->
13638 In Unix Alpine, you may use
13639 "~" to refer to your home directory or "~user" to refer
13640 to another's home directory.
13641 <!--chtml endif--><P>
13642 To select a file, move the cursor to it and
13643 choose "Select" (the default choice on the menu).
13646 <LI>Note <B>if</B> you are currently using the BROWSER for choosing a file for
13648 message body (that is, you chose "Read File" with the cursor under
13650 "----- Message Text -----" line
13651 while composing, then "To Files"): Since the file
13652 selected will become part of the message text, it must be in a format
13653 suitable for that (Alpine does not check!), such as a plain text file.
13654 Files of other formats (for example, graphics, databases, software
13655 programs) should be
13656 <B>attached</B> to the message instead --
13657 by moving the cursor in the COMPOSE MESSAGE screen into the
13658 message header area and pressing
13659 <!--chtml if pinemode="function_key"-->
13666 Note <B>if</B> you are currently using the BROWSER for saving a message
13667 attachment, or exporting a message, to a file: You can use the Add command to
13668 provide the name for a new file to save/export to, and then select that name
13669 to use it for the save/export operation. Back at the prompt
13670 "EXPORT: Copy message to file in ..." hit Enter, then choose
13671 either Overwrite or Append (it doesn't make a difference, since the file is
13672 so far empty). Note: If you cancel the
13673 operation at that point, the file created with the Add command will remain
13678 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13681 <End of help on this topic>
13684 ====== h_composer_ins =====
13687 <TITLE>INSERT TEXT FILE</TITLE>
13690 <H1>INSERT TEXT FILE</H1>
13692 Use this function to insert a text file. The file name
13693 given can be an absolute file path name for your system
13694 <!--chtml if pinemode="os_windows"-->
13695 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
13696 with a relative pathname, or simply a file name without
13697 drive or directory specification.
13699 (for example, "/tmp/exported.earlier" on Unix hosts),
13700 a file in your home directory, or a file path relative to your
13701 home directory. In Unix Alpine, you may use "~" to refer to
13702 your home directory or "~user" to refer to another
13703 account's home directory.
13706 No wild card characters may be used.
13707 The file must reside on the system running Alpine.
13710 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
13711 feature is set, names are relative to your current working directory
13712 <!--chtml if pinemode="running"-->
13713 (which, at least for your current Alpine "session,"
13714 is "<!--#echo var="CURRENT_DIR"-->")
13716 rather than your home directory
13717 <!--chtml if pinemode="running"-->
13718 (which, in the present configuration of your system, is
13719 "<!--#echo var="HOME_DIR"-->")
13723 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13726 <End of help on this topic>
13729 ====== h_composer_ins_m =====
13732 <TITLE>INSERT MESSAGE</TITLE>
13735 <H1>INSERT MESSAGE</H1>
13737 Type in the number of a message in the currently open folder to insert it
13740 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13743 <End of help on this topic>
13746 ====== h_composer_search =====
13749 <TITLE>Explanation of Composer Whereis Command </TITLE>
13752 <H1>Help For Whereis Command</H1>
13754 Whereis is used to search the message for a word or part of a word.
13755 When searching in the composer, only the message part of your mail is
13756 searched, and the cursor is put on the first occurrence appearing
13757 after the location of the cursor. The search will wrap to the
13758 beginning of the message when it no longer finds matches in the
13759 remainder of the message.
13761 To search for the same string a second time, press
13762 <!--chtml if pinemode="function_key"-->
13767 to begin search and then just press RETURN to accept the previous
13768 search string shown in square brackets rather than entering a new
13771 The "Search" prompt has several sub-command available:
13775 <DD> Takes you to this help page.
13778 <DD> Cancels the prompt. No search takes place.
13780 <DT>First Line</DT>
13781 <DD> Takes you back to the composer with the cursor on the first character
13782 of the first line of text.
13785 <DD> Takes you back to the composer with the cursor on the last character
13786 of the last line of text.
13788 <DT>Replace (Optional)</DT>
13789 <DD> This sub-command is enabled by the
13790 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13791 feature (which is on by default); see its help screen for details on how replacing works.
13795 <End of help on this topic>
13798 ====== h_sigedit_search =====
13801 <TITLE>Explanation of Whereis Command </TITLE>
13804 <H1>Help For Whereis Command</H1>
13806 Whereis is used to search for a word or part of a word.
13807 When searching the cursor is put on the first occurrence appearing
13808 after the location of the cursor. The search will wrap to the
13809 beginning of the signature when it no longer finds matches in the
13810 remainder of the signature.
13812 To search for the same string a second time, press
13813 <!--chtml if pinemode="function_key"-->
13818 to begin search and then just press RETURN to accept the previous
13819 search string shown in square brackets rather than entering a new
13822 The "Search" prompt has several sub-command available:
13826 <DD> Takes you to this help page.
13829 <DD> Cancels the prompt. No search takes place.
13831 <DT>First Line</DT>
13832 <DD> Takes you back to the composer with the cursor on the first character
13833 of the first line of text.
13836 <DD> Takes you back to the composer with the cursor on the last character
13837 of the last line of text.
13839 <DT>Replace (Optional)</DT>
13840 <DD> This sub-command is enabled by the
13841 <A HREF="h_config_enable_search_and_repl">"<!--#echo var="FEAT_enable-search-and-replace"-->"</A>
13842 feature (which is on by default); see its help screen for details on how replacing works.
13846 <End of help on this topic>
13849 ======= h_composer_to ====
13852 <TITLE>THE MESSAGE COMPOSER'S TO FIELD</TITLE>
13855 <H1>THE MESSAGE COMPOSER'S TO FIELD</H1>
13857 <H2>The "To:" field</H2>
13858 The address you enter here must be a valid email address that is reachable
13861 <H2>Email Address Format</H2>
13862 You may enter a full name and email address,
13863 <!--chtml if pinemode="os_windows"-->
13865 a local (meaning, on the same
13866 host as the one you are running Alpine on) username that Alpine will
13869 the nickname of someone in a
13870 <A HREF="h_abook_opened">Alpine Address Book</A>, or a local
13871 mail alias defined by your system administrator. When you move the cursor
13872 out of this field, the nicknames will be expanded to the addresses in your
13873 address book, and the local usernames will be expanded to include the
13874 persons' actual names. You may enter as many addresses as you wish, but they
13875 must be separated by commas. You can move around this and other header fields
13876 with the arrow keys and use many of the usual composer editing keys.
13879 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13883 <H2>MESSAGE HEADER COMMANDS</H2>
13884 <!--chtml if pinemode="function_key"-->
13885 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13886 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13887 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13888 ^P (Up Arrow) Previous line |<BR>
13889 ^N (Down Arrow) Next line | F9 Cut marked text or<BR>
13890 ^A Beginning of line | delete current line<BR>
13891 ^E End of line | F10 Undelete line(s)<BR>
13892 F7 Previous page | ^W <A HREF="h_composer_search">Whereis</A> (search text)<BR>
13893 F8 Next page |-------------------------------------<BR>
13894 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13895 ----------------------------------------|<BR>
13896 MESSAGE COMMANDS | GENERAL COMMANDS | F12 To Addressbook/Browser<BR>
13897 F3 <A HREF="h_compose_cancel">Cancel</A> | F1 Get help | F4 Attach File<BR>
13898 F11 <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13899 F2 <A HREF="h_compose_send">Send</A> | | F5 <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13901 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------<BR>
13902 ^B (Left Arrow) Back character | ^D Delete current character<BR>
13903 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character<BR>
13904 ^P (Up Arrow) Previous line | <BR>
13905 ^N (Down Arrow) Next line | ^K Cut marked text or<BR>
13906 ^A Beginning of line | delete current line<BR>
13907 ^E End of line | ^U Undelete line(s)<BR>
13908 ^Y Previous page |<BR>
13909 ^V Next page |-------------------------------------<BR>
13910 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS<BR>
13911 ----------------------------------------| ^R <A HREF="h_compose_richhdr">Rich Headers</A><BR>
13912 MESSAGE COMMANDS | GENERAL COMMANDS | ^T To Addressbook/Browser<BR>
13913 ^C <A HREF="h_compose_cancel">Cancel</A> | ^G Get help | ^J Attach File<BR>
13914 ^O <A HREF="h_common_postpone">Postpone</A> | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen<BR>
13915 ^X <A HREF="h_compose_send">Send</A> | | TAB <A HREF="h_compose_addrcomplete">Address Completion</A><BR>
13921 <LI>For help on a particular command, highlight the bold text associated
13922 with it above and hit Return.
13923 <LI> The availability of certain commands
13924 is determined by Alpine configuration files and system capabilities.
13925 At some sites, certain commands may not be available due to security or
13931 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13933 <End of help on this topic>
13936 ======= h_composer_cc ====
13939 <TITLE>THE MESSAGE COMPOSER'S CC FIELD</TITLE>
13942 <H1>THE MESSAGE COMPOSER'S CC FIELD</H1>
13943 The Cc: field is just like the To: field, except it is used for addressees
13944 that you wish to send a "carbon" copy to. That is, the message is
13945 not directly meant directly "for" these recipients, but you wanted
13946 them to see the message. The only difference the recipients see is that their
13947 name is in the Cc: field, rather than the To: field.
13949 For help with Cc: field editing
13950 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
13953 <LI><A HREF="h_address_format">Explanation of Address formats</A>
13957 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
13959 <End of help on this topic>
13962 ======= h_composer_bcc ====
13965 <TITLE>THE MESSAGE COMPOSER'S BCC FIELD</TITLE>
13968 <H1>THE MESSAGE COMPOSER'S BCC FIELD</H1>
13969 The "Bcc:" (Blind carbon copy) header is used when you wish to send
13970 a copy of the message to one or more people whose addresses you do not
13971 wish disclosed, either to reduce clutter or for confidentiality.
13973 The format of the Bcc: field is just the same as the To: and Cc: fields in
13974 the way the addresses are entered. The recipients listed here will
13975 receive a copy of the message, but --assuming your site's mail transport
13976 software is properly configured-- their addresses will not show up in the
13977 headers of the message, as delivered to all of the recipients. The To:
13978 and Cc: recipients will not know a copy was sent to the Bcc: recipients.
13980 Note: if there is no To: or Cc: or Lcc: address in the message, Alpine
13981 will automatically generate and place in the To: field a pseudo-address of
13982 "undisclosed-recipients: ;"
13983 or whatever string has been specified in the
13984 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
13987 The reason for this is to avoid embarrassment caused by some Internet
13988 mail transfer software that interprets a "missing" To: header as
13989 an error and replaces it with an Apparently-to: header that may contain
13990 the addresses you entered on the Bcc: line. In addition, it may be
13991 less disconcerting to Bcc: recipients to see <B>something</B> in the To: field.
13993 You can manipulate what text ends up on the (originally) empty To:
13994 field. Just remember to put a colon and semicolon at the end of the
13995 field, which is a special notation denoting that it is not a real address.
13997 For information on message header editing
13998 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14001 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14005 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14007 <End of help on this topic>
14010 ======= h_composer_lcc ====
14013 <TITLE>THE MESSAGE COMPOSER'S LCC FIELD</TITLE>
14016 <H1>THE MESSAGE COMPOSER'S LCC FIELD</H1>
14017 The "Lcc:" (List carbon copy) header is intended to be used when
14018 you wish to send a message to a list of people but avoid having all
14019 of their addresses visible, in order to reduce clutter when the
14020 message is received.
14022 It is similar to the
14023 <A HREF="h_composer_bcc">"Bcc" (Blind carbon copy) header</A>
14025 addressees are hidden, but Lcc is designed to work specifically with
14026 distribution lists you have created in your
14027 <A HREF="h_abook_opened">Alpine Address Book</A>. Placing
14028 the nickname of the list on the Lcc line will result in the full name of
14029 your Alpine Address Book list being placed on the To: line of the message,
14030 using a special notation that distinguishes it from a real address. You
14031 must leave the To: line blank for your list name to appear there.
14033 For example, if you have this list entered in your Address Book:<PRE>
14035 largo Key Largo List DISTRIBUTION LIST:
14038 walter@mgm.com</PRE>
14041 and you enter "largo" on the Lcc: line while composing a message,
14042 the result is:<PRE>
14044 To : Key Largo List: ;
14048 Lcc : Key Largo List <bogie@mgm.com>,
14053 Each recipient listed on the Lcc: line receives a copy of the message
14054 without their address being visible (as though they were listed on the
14055 Bcc: line). The colon-semicolon notation used to put the full-name of the
14056 list on the To: line is a special address format that doesn't specify any
14057 actual addressees, but does give some information to the recipients of the
14060 Note: if after entering an LCC, you delete the list name that is placed
14061 on the To: line, then recipients will see <PRE>
14062 To: undisclosed-recipients: ;</PRE>
14064 (or whatever string is defined in the
14065 <A HREF="h_config_empty_hdr_msg">"<!--#echo var="VAR_empty-header-message"-->"</A>
14066 variable) just as in the BCC case.
14068 For help with Lcc: field editing
14069 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14072 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14076 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14078 <End of help on this topic>
14081 ======= h_composer_from =======
14084 <TITLE>THE MESSAGE COMPOSER'S FROM FIELD</TITLE>
14087 <H1>THE MESSAGE COMPOSER'S FROM FIELD</H1>
14089 This header carries your return address. It is the address toward which
14090 replies (and often, future unrelated correspondence) will be directed,
14091 unless you have <A HREF="h_config_custom_hdrs">defined an optional
14092 "Reply-To:" header</A> in the SETUP CONFIGURATION screen. Make
14093 sure this address is correct.
14095 For help with message header editing
14096 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14099 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14103 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14105 <End of help on this topic>
14108 ======= h_composer_reply_to =======
14111 <TITLE>THE MESSAGE COMPOSER'S REPLY-TO FIELD</TITLE>
14114 <H1>THE MESSAGE COMPOSER'S REPLY-TO FIELD</H1>
14116 Most people should not need this header. The Reply-To: header is used in
14117 cases where you would like replies to your messages to be directed to an
14118 address other than your normal "From:" address. This is atypical,
14119 but can happen when you use multiple machines and do not have the same account
14120 name on each one, or when you wish to direct certain replies to accounts
14121 or folders designated for specific classes of correspondence.
14123 For help with message header editing
14124 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14127 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14132 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14134 <End of help on this topic>
14137 ======= h_composer_custom_addr ====
14140 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
14143 <H1>CUSTOMIZED HEADER FIELD</H1>
14144 This is a customized header, i.e. not one that is part of Alpine's normal
14145 set of Compose headers.
14147 For help with message header editing
14148 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14151 <LI><A HREF="h_address_format">Explanation of Address formats</A>
14155 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14157 <End of help on this topic>
14160 ======= h_composer_custom_free ====
14163 <TITLE>CUSTOMIZED HEADER FIELD</TITLE>
14166 <H1>CUSTOMIZED HEADER FIELD</H1>
14167 This is a customized header, i.e. not one that is part of Alpine's normal
14168 set of Compose headers.
14170 This field consists of arbitrary text.
14172 For help with message header editing
14173 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14176 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14178 <End of help on this topic>
14181 ====== h_composer_news =====
14184 <TITLE>THE MESSAGE COMPOSER'S NEWSGRPS LINE</TITLE>
14187 <h1>THE MESSAGE COMPOSER'S NEWSGRPS LINE</h1>
14188 Use the newsgroups line to specify any and all USENET newsgroups to which
14189 your message should be posted. When composing a message from scratch, this
14190 line may be hidden. If so, just press the rich headers command
14191 (<!--chtml if pinemode="function_key"-->F5<!--chtml else-->^R<!--chtml endif-->)
14192 to make it visible.
14194 <EM>Be aware</EM> that when you post to a newsgroup thousands of
14195 people will be reading your message. Also, you or your system manager
14196 must have defined an "<!--#echo var="VAR_nntp-server"-->" in your Alpine configuration
14197 in order for you to be able to post.
14199 For help with message header editing
14200 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14202 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14205 <End of help on this topic>
14208 ======= h_composer_fcc ====
14211 <TITLE>THE MESSAGE COMPOSER'S FCC FIELD</TITLE>
14214 <H1>THE MESSAGE COMPOSER'S FCC FIELD</H1>
14215 The FCC (File Carbon Copy) specifies the folder used to keep a copy of
14216 each outgoing message. The default value can be configured with the
14217 "<!--#echo var="VAR_default-fcc"-->" and "<!--#echo var="VAR_fcc-name-rule"-->" options. You can change or remove
14218 the file carbon copy on any message you send by editing the FCC header.<p>
14220 You may type ^T to get a list of all your folders and select one to use as
14221 the FCC for this message.<P>
14223 For help with message header editing
14224 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14227 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14229 <End of help on this topic>
14232 ======= h_composer_subject ====
14235 <TITLE>THE MESSAGE COMPOSER'S SUBJECT FIELD</TITLE>
14238 <H1>THE MESSAGE COMPOSER'S SUBJECT FIELD</H1>
14240 The subject header provides a place to enter a few words that summarize
14241 the topic of the message you are sending. You may leave this line blank,
14242 but it is considered a courtesy to use a meaningful subject.<p>
14244 For help with message header editing
14245 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14248 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14250 <End of help on this topic>
14253 ======= h_composer_attachment ====
14256 <TITLE>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</TITLE>
14259 <H1>THE MESSAGE COMPOSER'S ATTCHMNT FIELD</H1>
14261 The "Attchmnt:" field is where you specify what file or
14262 files you'd like attached to
14263 the message you are composing. Those files must reside on the machine
14264 running Alpine. If your file is on a PC or Mac and you run Alpine with an
14265 account on a Unix machine, you'll have to transfer it before attaching it.
14266 Contact local computer support people for assistance with transferring.
14270 given can be an absolute file path name for your system
14271 <!--chtml if pinemode="os_windows"-->
14272 (for example, "H:\SIGFILES\FULLINFO.TXT"), a file
14273 with a relative pathname, or simply a file name without
14274 drive or directory specification.
14276 (for example, "/tmp/exported.earlier" on Unix hosts),
14277 a file in your home directory, or a file path relative to your
14278 home directory. In Unix Alpine, you may use "~" to refer to
14279 your home directory or "~user" to refer to another
14280 account's home directory.
14281 <!--chtml endif--><P>
14282 No wild card characters may be used.
14284 <A HREF="h_config_use_current_dir">"<!--#echo var="FEAT_use-current-dir"-->"</A>
14285 feature is set, names are relative to your current working directory
14286 <!--chtml if pinemode="running"-->
14287 (which, at least for your current Alpine "session,"
14288 is "<!--#echo var="CURRENT_DIR"-->")
14290 rather than your home directory
14291 <!--chtml if pinemode="running"-->
14292 (which, in the present configuration of your system, is
14293 "<!--#echo var="HOME_DIR"-->")
14297 Alpine uses MIME encoding for attachments, so binaries and files of any
14298 length can safely be delivered to any MIME-capable mail reading program.
14299 If you send an attachment to someone who does not have a MIME-capable mail
14300 reading program yet, then the main message text will be readable, but
14301 attachments (even attachments that are just plain text) are not.
14304 Typing the filename on the Attchmnt: line achieves the same
14305 result as using the
14306 <!--chtml if pinemode="function_key"-->
14310 <!--chtml endif--> command.
14313 If you Forward a message with attachments, you may delete them from your
14314 Forwarded message by editing the Attchmnt header line.
14317 For help with message header editing
14318 commands, check the <A HREF="h_composer_to">Help for the To:</A> header.
14321 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14323 <End of help on this topic>
14326 ======= h_composer_ctrl_j ====
14329 <TITLE>COMPOSER ATTACH</TITLE>
14333 <!--chtml if pinemode="function_key"-->
14337 <!--chtml endif--> command:
14338 At the "File to attach:" prompt, enter the name of the
14339 existing file to attach to your message.
14341 <A HREF="h_config_enable_tab_complete">"<!--#echo var="FEAT_enable-tab-completion"-->"</A>
14343 you need only enter the beginning of the filename (enough of it to uniquely
14344 identify the file) and press TAB to complete it.
14346 Or, press ^T to use the BROWSER screen for
14347 selecting the file. <P>
14348 For more information on attaching files, see the help screen for the
14350 <A HREF="h_composer_attachment">Attchmnt: field</A>, which is normally hidden,
14351 but can be revealed using the
14352 <!--chtml if pinemode="function_key"-->
14357 command with the cursor positioned above the
14358 "----- Message Text -----" line in the COMPOSE MESSAGE screen.
14360 <End of help on this topic>
14363 ======= h_edit_nav_cmds =========
14366 <TITLE>Composer Editing Commands Explained</TITLE>
14369 <H1>EDITING and NAVIGATION COMMANDS</H1>
14370 <!--chtml if pinemode="function_key"-->
14372 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14373 ^B (Left Arrow) Back character | ^D Delete current character
14374 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14375 ^P (Up Arrow) Previous line |
14376 ^N (Down Arrow) Next line | F9 Cut marked text or
14377 ^A Beginning of line | delete current line
14378 ^E End of line | F10 Undelete line(s)
14380 F8 Next page |-------------------------------------
14381 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14382 ----------------------------------------|
14383 EXIT COMMANDS | GENERAL COMMANDS | F12 To Addressbook
14384 F3 Cancel | F1 Get help | F12 RichView (expand lists)
14385 F2 eXit/save | ^Z Suspend | ^L Redraw Screen
14389 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
14390 ^B (Left Arrow) Back character | ^D Delete current character
14391 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14392 ^P (Up Arrow) Previous line |
14393 ^N (Down Arrow) Next line | ^K Cut marked text or
14394 ^A Beginning of line | delete current line
14395 ^E End of line | ^U Undelete line(s)
14397 ^V Next page |-------------------------------------
14398 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
14399 ----------------------------------------|
14400 EXIT COMMANDS | GENERAL COMMANDS | ^T To Addressbook
14401 ^C Cancel | ^G Get help | ^R RichView (expand lists)
14402 ^X eXit/save | ^Z Suspend | ^L Redraw Screen
14405 <End of help on this topic>
14408 ===== h_composer_sigedit =====
14411 <TITLE>Signature Editor Commands Explained</TITLE>
14414 <H1>SIGNATURE EDITOR COMMANDS</H1>
14415 <!--chtml if pinemode="function_key"-->
14417 CURSOR MOTION KEYS |EDITING KEYS
14418 ^B (Left Arrow) Back character | ^D Delete current character
14419 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14420 ^P (Up Arrow) Previous line | ^^ Set a mark
14421 ^N (Down Arrow) Next line | F9 Cut marked text or
14422 ^A Beginning of line | delete current line
14423 ^E End of line | F10 Paste text, undelete lines
14424 F7 Previous page | cut with ^K, or unjustify
14425 F8 Next page |-------------------------------------
14426 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14427 ---------------------------------------| F6 Whereis (search for string)
14428 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14429 F3 Cancel | F1 Get help | F4 Justify paragraph
14430 | ^Z Suspend | ^L Redraw Screen
14431 F2 Send | F6 Alt. editor | F5 Read in a file
14435 CURSOR MOTION KEYS |EDITING KEYS
14436 ^B (Left Arrow) Back character | ^D Delete current character
14437 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14438 ^P (Up Arrow) Previous line | ^^ Set a mark
14439 ^N (Down Arrow) Next line | ^K Cut marked text or
14440 ^A Beginning of line | delete current line
14441 ^E End of line | ^U Paste text, undelete lines
14442 ^Y Previous page | cut with ^K, or unjustify
14443 ^V Next page |-------------------------------------
14444 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14445 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14446 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14447 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14448 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14449 ^X Send | ^_ Alt. editor | ^R Read in a file
14453 NOTE: The presence or absence of the following commands is determined
14454 by "Feature-List" options in your Alpine configuration. Also,
14455 some of these commands may be administratively disabled by your system
14456 manager; if they don't work, please check with your local help desk
14457 before reporting a bug.
14460 <LI>Suspend (suspends Alpine and gives a system prompt)
14461 <LI>Alternate editor (allows you to compose with your own editor)
14465 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14469 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14470 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14472 <End of help on this topic>
14475 ===== h_composer_commentedit =====
14478 <TITLE>Comment Editor Commands Explained</TITLE>
14481 <H1>COMMENT EDITOR COMMANDS</H1>
14482 <!--chtml if pinemode="function_key"-->
14484 CURSOR MOTION KEYS |EDITING KEYS
14485 ^B (Left Arrow) Back character | ^D Delete current character
14486 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14487 ^P (Up Arrow) Previous line | ^^ Set a mark
14488 ^N (Down Arrow) Next line | F9 Cut marked text or
14489 ^A Beginning of line | delete current line
14490 ^E End of line | F10 Paste text, undelete lines
14491 F7 Previous page | cut with ^K, or unjustify
14492 F8 Next page |-------------------------------------
14493 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14494 ---------------------------------------| F6 Whereis (search for string)
14495 MESSAGE COMMANDS | GENERAL COMMANDS | F12 Spell checker
14496 F3 Cancel | F1 Get help | F4 Justify paragraph
14497 | ^Z Suspend | ^L Redraw Screen
14498 F2 Send | F6 Alt. editor | F5 Read in a file
14502 CURSOR MOTION KEYS |EDITING KEYS
14503 ^B (Left Arrow) Back character | ^D Delete current character
14504 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
14505 ^P (Up Arrow) Previous line | ^^ Set a mark
14506 ^N (Down Arrow) Next line | ^K Cut marked text or
14507 ^A Beginning of line | delete current line
14508 ^E End of line | ^U Paste text, undelete lines
14509 ^Y Previous page | cut with ^K, or unjustify
14510 ^V Next page |-------------------------------------
14511 ^@ (Ctrl-SPACE) Next word |SCREEN/COMPOSITION COMMANDS
14512 ---------------------------------------| ^W <A HREF="h_composer_search">Whereis</A> (search text)
14513 MESSAGE COMMANDS | GENERAL COMMANDS | ^T Spell checker
14514 ^C Cancel | ^G Get help | ^J <A HREF="h_compose_justify">Justify</A> paragraph
14515 | ^Z <A HREF="h_common_suspend">Suspend</A> | ^L Redraw Screen
14516 ^X Send | ^_ Alt. editor | ^R Read in a file
14520 NOTE: The presence or absence of the following commands is determined
14521 by "Feature-List" options in your Alpine configuration. Also,
14522 some of these commands may be administratively disabled by your system
14523 manager; if they don't work, please check with your local help desk
14524 before reporting a bug.
14527 <LI>Suspend (suspends Alpine and gives a system prompt)
14528 <LI>Alternate editor (allows you to compose with your own editor)
14532 Alpine does not use the following keys: Ctrl-S, Ctrl-Q, Ctrl-],
14536 NOTE: For special handling of Ctrl-S and Ctrl-Q see special comments regarding
14537 <A HREF="h_special_xon_xoff">"XOFF/XON"</A>.
14539 <End of help on this topic>
14542 ======= h_composer_abook_nick =======
14545 <TITLE>Addressbook Nickname Explained</TITLE>
14548 This is a short nickname for this address book entry. If it is used in
14549 place of an address from the composer, the composer will fill in the
14550 address(es) for the entry that matches the nickname.
14553 Look <A HREF="h_edit_nav_cmds">here</A>
14554 to see the available Editing and Navigation commands.
14556 <End of help on this topic>
14559 ======= h_composer_abook_full =======
14562 <TITLE>Addressbook Fullname Explained</TITLE>
14565 This is the full name field for this entry. If this is going to be a
14566 distribution list (more than one address), it should be a descriptive
14567 phrase describing the list. It will be included in the mail header if you
14568 put the list in the To: or CC: field, or in the To: line if you put the
14569 list in the Lcc: field. It's OK to leave this field blank (and OK to
14570 leave any of the other fields blank, too). If this address book entry is
14571 going to be a simple entry with just one address, then this field is the
14572 person's name. When you send mail to this entry, this is the field to the
14573 left of the brackets. That is, it is the most readable part of the
14574 address. For example, in the sample address:
14576 John Doe <jdoe@some.domain>
14578 "John Doe" is the full name field. If you are sorting your address book
14579 with one of the options that uses full names, then it might be useful to
14580 enter the full name as "Last, First", for example:
14584 so that it will be sorted using Doe instead of John. This will be changed
14585 back into John Doe when you use it.
14587 Look <A HREF="h_edit_nav_cmds">here</A>
14588 to see the available Editing and Navigation commands.
14590 <End of help on this topic>
14593 ======= h_composer_abook_fcc =======
14596 <TITLE>Addressbook Fcc Explained</TITLE>
14599 If this entry is the first one in the To: line of an outgoing message,
14600 this field will be used for the Fcc (File Carbon Copy) instead of whatever
14601 you would normally get (which depends on which
14602 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
14605 If this field consists of two double quotes ("") that tells Alpine
14606 that you don't want any Fcc associated with this entry.
14608 Look <A HREF="h_edit_nav_cmds">here</A>
14609 to see the available Editing and Navigation commands.
14611 <End of help on this topic>
14614 ====== h_config_combined_abook_display =====
14617 <TITLE>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></TITLE>
14620 <H1>FEATURE: <!--#echo var="FEAT_combined-addrbook-display"--></H1>
14622 This feature affects the address book display screens.
14623 Normally, expanding an address book from the ADDRESS BOOK LIST screen
14624 will cause the remaining address books and directory servers to disappear
14625 from the screen, leaving only the entries of the expanded address book.
14626 If this feature is set, then the other address books will remain on the screen,
14627 so that all of the address books can be present at once.
14630 The way that commands work won't be changed.
14631 For example, the Select All command will select all of the entries in the
14632 current address book, not all of the entries in all of the address books.
14633 The WhereIs command will change a little.
14634 It will search through all of the text on the screen plus all of the entries
14635 from expanded address books.
14638 When this feature is set, the setting of the feature
14639 <A HREF="h_config_expanded_addrbooks">"<!--#echo var="FEAT_expanded-view-of-addressbooks"-->"</A>
14642 <End of help on this topic>
14645 ====== h_config_titlebar_color_style =====
14648 <TITLE>OPTION: <!--#echo var="VAR_titlebar-color-style"--></TITLE>
14651 <H1>OPTION: <!--#echo var="VAR_titlebar-color-style"--></H1>
14653 This option affects the colors used to display the titlebar (the top
14654 line on the screen) when viewing a message.
14657 The available options include:
14662 <DD>The color of the titlebar will be the color you set for the
14663 <A HREF="h_config_title_color">Title Color</A>.
14664 The Title Color may be set by using the
14665 <A HREF="h_color_setup">Setup Kolor</A> screen.
14669 <DD>The color of the titlebar will be the same as the color of the
14670 index line corresponding to the message being viewed.
14671 The rules that determine what color the index line will be may be set
14672 up by going to the Setup/Rules/Indexcolor screen.
14673 If the index line for a message is not colored explicitly by the
14674 Indexcolor rules, then the titlebar will be colored the same as for
14675 the "default" option above (which is not the same color that
14676 the index line itself will have).
14679 <DT>reverse-indexline</DT>
14680 <DD>This is similar to the "indexline" option except the
14681 foreground and background colors from the corresponding index line will
14683 For example, if the index line color is red letters on a white background,
14684 then the titlebar will be white letters on a red background.
14685 If the index line for a message is not colored explicitly by the
14686 Indexcolor rules, then the titlebar will be colored the same as for
14687 the "default" option above (which is not the same color that
14688 the index line itself will have).
14695 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14697 <End of help on this topic>
14700 ====== h_config_index_color_style =====
14703 <TITLE>OPTION: <!--#echo var="VAR_current-indexline-style"--></TITLE>
14706 <H1>OPTION: <!--#echo var="VAR_current-indexline-style"--></H1>
14708 This option affects the colors used to display the current line in the
14709 MESSAGE INDEX screen.
14710 If you do not have Index Color Rules defined, then this option will
14711 have no effect in the index.
14712 Those Rules may be defined by going to the Setup/Rules/Indexcolor screen.
14715 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
14716 is turned on and the
14717 <A HREF="h_config_incunseen_color">Incoming Unseen Color</A>
14718 is set to something other than the default, then
14719 this option also affects the color used to display the current folder
14720 in the Incoming FOLDER LIST screen.
14723 The available options include:
14727 <DT>flip-colors</DT>
14728 <DD>This is the default.
14729 If an index line is colored because it matches one of your
14730 Index Color Rules, then its colors will be reversed when it is the currently
14732 For example, if the line is normally red text on a blue background, then
14733 when it is the current line it will be drawn as blue text on a red background.
14735 The rest of the option values all revert to this flip-colors behavior if
14736 there is no Reverse Color defined.
14740 <DD>With this option the Reverse color is always used to highlight the
14744 <DT>reverse-fg</DT>
14745 <DD>The foreground part of the Reverse Color is used to highlight
14747 If this would cause the text to be unreadable (because the foreground and
14748 background colors are the same) or if it would cause no change in the
14749 color of the index line, then the colors are flipped instead.
14751 Some people think this works particularly well if you use different
14752 background colors to emphasize "interesting" lines,
14753 but always with the same Normal foreground color,
14754 and you use a different foreground color for the Reverse Color.
14757 <DT>reverse-fg-no-ambiguity</DT>
14758 <DD>With the "reverse-fg" rule above, it is possible that
14759 the resulting color will be exactly the same as the regular Reverse
14761 That can lead to some possible confusion because an
14762 "interesting"
14763 line that is the current line will be displayed exactly the same as a
14764 non-interesting line that is current.
14765 You can't tell whether the line is just a regular current line or if it is
14766 an "interesting" current line by looking at the color.
14767 Setting the option to this value removes that ambiguity.
14768 It is the same as the "reverse-fg" setting unless the resulting
14769 interesting current line would look just like a non-interesting current line.
14770 In that case, the interesting line's colors are simply flipped (like in the
14773 As an alternative way to preserve the line's interestingness in this case,
14774 you may find that using both a different foreground and a different
14775 background color for the interesting line will help.
14778 <DT>reverse-bg</DT>
14779 <DD>The background part of the Reverse Color is used to highlight
14781 If this would cause the text to be unreadable (because the foreground and
14782 background colors are the same) or if it would cause no change in the
14783 color of the index line, then the colors are flipped instead.
14785 Some people think this works particularly well if you use different
14786 foreground colors to emphasize "interesting" lines,
14787 but always with the same Normal background color,
14788 and you use a different background color for the Reverse Color.
14791 <DT>reverse-bg-no-ambiguity</DT>
14792 <DD>As with the "reverse-fg" case, the "reverse-bg"
14793 rule may also result in a color that is exactly the same as the regular
14795 Setting the option to this value removes that ambiguity.
14796 It is the same as the "reverse-bg" setting unless the resulting
14797 current line has the same color as the Reverse Color.
14798 In that case, the interesting line's colors are simply flipped (like in the
14806 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14808 <End of help on this topic>
14811 ====== h_config_expanded_addrbooks =====
14814 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></TITLE>
14817 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-addressbooks"--></H1>
14819 If multiple address books (either personal or global) are defined, and you
14820 wish to have them all expanded implicitly upon entering the ADDRESS BOOK
14821 screen, then set this feature. This feature will have no effect unless the
14823 <A HREF="h_config_combined_abook_display">"<!--#echo var="FEAT_combined-addrbook-display"-->"</A>
14826 <End of help on this topic>
14829 ====== h_config_combined_folder_display =====
14832 <TITLE>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></TITLE>
14835 <H1>FEATURE: <!--#echo var="FEAT_combined-folder-display"--></H1>
14837 This feature affects the folder list display screens.
14838 Normally, each folder list is viewed within its collection only. This
14839 command allows folder lists to be viewed within a single screen that
14840 combines the contents of all collections.
14843 The way that commands work won't be changed.
14844 For example, the Select All command will select all of the folders in the
14845 current collection, not all of the entries in all of the collections.
14846 The WhereIs command will change a little.
14847 It will search through all of the folders in the current collection as well
14848 as all the folder in any other expanded collection.
14851 When this feature is set, the setting of the feature
14852 <A HREF="h_config_expanded_folders">"<!--#echo var="FEAT_expanded-view-of-folders"-->"</A>
14855 <End of help on this topic>
14858 ====== h_config_combined_subdir_display =====
14861 <TITLE>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></TITLE>
14864 <H1>FEATURE: <!--#echo var="FEAT_combined-subdirectory-display"--></H1>
14866 This feature affects the Folder List screen when
14868 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14869 feature is enabled. Normally, selecting a directory from the Folder
14870 List takes you into a new screen displaying only the contents of
14874 Enabling this feature will cause the contents of the selected
14876 displayed within the boundaries of the "Collection" it
14877 is a part of. All previously displayed collections will remain
14881 The way that commands work won't be changed.
14882 For example, the Select All command will select all of the folders in the
14883 directory, as opposed to all of the entries in all of the collections.
14884 The WhereIs command will change a little.
14885 It will search through all of the folders in the current collection as well
14886 as all the folder in any other expanded collection.
14889 <End of help on this topic>
14892 ====== h_config_separate_fold_dir_view =====
14895 <TITLE>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></TITLE>
14898 <H1>FEATURE: <!--#echo var="FEAT_separate-folder-and-directory-entries"--></H1>
14900 This feature affects folder collections wherein a folder
14901 and directory can have the same name. By default, Alpine displays them
14902 only once, denoting that it is both a folder and directory by appending
14903 the folder name with the hierarchy character enclosed
14904 in square brackets.
14908 Enabling this feature will cause Alpine to display such names
14909 separately marking the name representing a directory with a trailing
14910 hierarchy delimiter (typically the slash, "/", character).
14913 The feature also alters the command set slightly. By default, the
14914 right-arrow descends into the directory, while hitting the Return key will
14915 cause the folder by that name to be opened.
14918 With this feature set, the Return key will open the highlighted folder, or
14919 enter the highlighted directory.
14922 <End of help on this topic>
14925 ====== h_config_expanded_folders =====
14928 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></TITLE>
14931 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-folders"--></H1>
14933 If multiple folder collections are defined, and you
14934 wish to have them all expanded implicitly upon entering the FOLDER LIST
14935 screen, then set this feature. This feature will have no effect unless the
14937 <A HREF="h_config_combined_folder_display">"<!--#echo var="FEAT_combined-folder-display"-->"</A>
14940 <End of help on this topic>
14943 ======= h_config_ldap_server =======
14946 <TITLE>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
14949 <H1>LDAP OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
14950 This is the name of the host where an LDAP server is running.
14951 For redundancy, this may be a space-delimited set of server names, in which
14952 case the first server that answers is used.
14953 Each of the server names may be optionally followed by
14954 a colon and a port number.
14955 If this form is used then the port number configured below in the
14956 <EM>port</EM> field is not used.
14958 To find out whether your organization has its own LDAP server,
14959 contact its computing support staff.
14961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14964 <End of help on this topic>
14967 ======= h_config_ldap_base =======
14970 <TITLE>LDAP OPTION: Search-Base</TITLE>
14973 <H1>LDAP OPTION: Search-Base</H1>
14975 This is the search base to be used on this server. It functions as a filter
14976 by restricting your searches in the LDAP server database
14977 to the specified contents of the specified fields. Without it, searches
14978 submitted to this directory server may fail. It might be something
14982 O = <Your Organization Name>, C = US
14984 or it might be blank.
14985 (Some LDAP servers actually ignore anything specified here.)
14987 If in doubt what parameters you should specify here,
14988 contact the maintainers of the LDAP server.
14990 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
14993 <End of help on this topic>
14996 ======= h_config_ldap_port =======
14999 <TITLE>LDAP OPTION: Port</TITLE>
15002 <H1>LDAP OPTION: Port</H1>
15004 This is the TCP port number to be used with this LDAP server. If you leave
15005 this blank port 389 will be used.
15007 <End of help on this topic>
15010 ======= h_config_ldap_nick =======
15013 <TITLE>LDAP OPTION: Nickname</TITLE>
15016 <H1>LDAP OPTION: Nickname</H1>
15018 This is a nickname to be used in displays. If you don't supply a
15019 nickname the server name
15020 (<A HREF="h_config_ldap_server">"<!--#echo var="VAR_ldap-servers"-->"</A>)
15021 will be used instead. This option is strictly for your convenience.
15023 <End of help on this topic>
15026 ======= h_config_ldap_binddn =======
15029 <TITLE>LDAP OPTION: Bind-DN</TITLE>
15032 <H1>LDAP OPTION: Bind-DN</H1>
15034 You may need to authenticate to the LDAP server before you are able to use it.
15035 This is the Distinguished Name to bind to when authenticating to this server.
15036 Try leaving this blank until you know you need it.
15038 Alpine only knows about LDAP Simple authentication.
15039 It does not attempt LDAP SASL authentication.
15040 The DN and password will be sent in the clear unless TLS encryption is
15041 being used on this connection.
15042 Because of this, you may want to set the LDAP feature
15043 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>
15045 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15046 if you are going to be providing a password.
15048 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
15051 <End of help on this topic>
15054 ======= h_config_ldap_opts_impl =======
15057 <TITLE>LDAP FEATURE: Use-Implicitly-From-Composer</TITLE>
15060 <H1>LDAP FEATURE: Use-Implicitly-From-Composer</H1>
15062 Set this to have lookups done to this server implicitly from the composer.
15063 If an address doesn't look like a fully-qualified address, it will be looked
15064 up in your address books, and if it doesn't match a nickname there, then it
15065 will be looked up on the LDAP servers that have this feature set.
15066 The lookups will also be done when using the address completion feature
15067 (TAB command) in the composer if any of the serves have this feature set.
15068 Also see the LDAP feature
15069 <A HREF="h_config_ldap_opts_rhs">"Lookup-Addrbook-Contents"</A>
15070 and the Setup/Config feature
15071 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
15073 <End of help on this topic>
15076 ======= h_config_ldap_opts_tls =======
15079 <TITLE>LDAP FEATURE: Attempt-TLS-On-Connection</TITLE>
15082 <H1>LDAP FEATURE: Attempt-TLS-On-Connection</H1>
15084 When connecting to this server Alpine will attempt to use TLS encryption
15086 Also see the closely related feature
15087 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15089 Note that if this option is set, then
15090 <A HREF="h_config_ldap_opts_ldaps">
15091 "Require-LDAPS-On-Connection"</A>
15092 can not be enabled for this server. You must disable this feature in
15094 <A HREF="h_config_ldap_opts_ldaps">
15095 "Require-LDAPS-On-Connection"</A>
15097 <End of help on this topic>
15100 ======= h_config_ldap_opts_tlsmust =======
15103 <TITLE>LDAP FEATURE: Require-TLS-On-Connection</TITLE>
15106 <H1>LDAP FEATURE: Require-TLS-On-Connection</H1>
15108 When connecting to this server Alpine will attempt to use TLS encryption
15110 If the StartTLS operation fails then the connection will not be used.
15112 Note that if this option is set, then
15113 <A HREF="h_config_ldap_opts_ldaps">
15114 "Require-LDAPS-On-Connection"</A>
15115 can not be enabled for this server. You must disable this feature in
15117 <A HREF="h_config_ldap_opts_ldaps">
15118 "Require-LDAPS-On-Connection"</A>
15120 <End of help on this topic>
15123 ======= h_config_ldap_opts_ldaps =======
15126 <TITLE>LDAP FEATURE: Require-LDAPS-On-Connection</TITLE>
15129 <H1>LDAP FEATURE: Require-LDAPS-On-Connection</H1>
15131 When connecting to this server Alpine will use LDAPS (LDAP over SSL/TLS)
15134 This feature can not be used along with
15135 <A HREF="h_config_ldap_opts_tlsmust">"Require-TLS-On-Connection"</A>
15137 <A HREF="h_config_ldap_opts_tls">"Attempt-TLS-On-Connection"</A>.
15138 If you want to connect using StartTLS to this server, you must disable
15139 this feature first.
15141 <End of help on this topic>
15144 ====== h_config_ldap_opts_rhs =====
15147 <TITLE>LDAP FEATURE: Lookup-Addrbook-Contents</TITLE>
15150 <H1>LDAP FEATURE: Lookup-Addrbook-Contents</H1>
15152 Normally implicit LDAP lookups from the composer are done only for the
15153 strings you type in from the composer screen. In other words, you type in
15154 something in the To or CC field and press return, then the string is looked up.
15155 First that string is looked up in your address books. If a match is found
15156 there, then the results of that match are looked up again. If you place
15157 a string in your address book that you want to have looked up on the LDAP
15158 directory server, you need to turn on this feature. If you set this feature
15159 for a server, you almost always will also want to set the
15160 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
15161 feature. An example might serve to best illustrate this feature.
15163 If an LDAP lookup of "William Clinton" normally returns an
15165 address of pres@whitehouse.gov, then you might put an entry in your address
15166 book that looks like:
15168 <CENTER><SAMP>Nickname = bill</SAMP></CENTER><BR>
15169 <CENTER><SAMP>Address = "William Clinton"</SAMP></CENTER>
15171 Now, when you type "bill" into an
15172 address field in the composer Alpine will
15173 find the "bill" entry in your address book.
15174 It will replace "bill" with
15175 "William Clinton".
15176 It will then search for an entry with that nickname
15177 in your address book and not find one. If this feature
15178 is set, Alpine will then attempt to lookup
15179 "William Clinton" on the LDAP server and find the entry with address
15180 pres@whitehouse.gov.
15182 A better way to accomplish the same thing is probably to use the feature
15183 <A HREF="h_config_ldap_opts_ref">"Save-Search-Criteria-Not-Result"</A>.
15185 <End of help on this topic>
15188 ====== h_config_ldap_opts_ref =====
15191 <TITLE>LDAP FEATURE: Save-Search-Criteria-Not-Result</TITLE>
15194 <H1>LDAP FEATURE: Save-Search-Criteria-Not-Result</H1>
15196 Normally when you save the results of an LDAP directory lookup to your
15197 address book the results of the lookup are saved. If this feature is set
15198 and the entry being saved was found on this directory server, then the
15199 search criteria is saved instead of the results of the search. When this
15200 address book entry is used in the future, instead of copying the results
15201 from the address book the directory lookup will be done again. This could
15202 be useful if the copied result might become stale because the data on
15203 the directory server changes (for example, the entry's email address changes).
15204 You probably don't want to set this feature if the server is at all slow or
15207 The way this actually works is that instead of saving the email address
15208 in your address book, Alpine saves enough information to look up the same
15209 directory entry again. In particular, it saves the server name and the
15210 distinguished name of the entry. It's possible that the server administrators
15211 might change the format of distinguished names on the server, or that the
15212 entry might be removed from the server. If Alpine notices this, you will be warned
15213 and a backup copy of the email address will be used. You may want to create
15214 a new entry in this case, since you will get the annoying warning every
15215 time you use the old entry. You may do that by Saving the entry to a new
15216 nickname in the same address book. You will be asked whether or not you
15217 want to use the backup email address.
15219 A related feature in the Setup/Config screen is
15220 <A HREF="h_config_add_ldap">"<!--#echo var="FEAT_ldap-result-to-addrbook-add"-->"</A>.
15222 <End of help on this topic>
15225 ======= h_config_ldap_opts_nosub =======
15228 <TITLE>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</TITLE>
15231 <H1>LDAP FEATURE: Disable-Ad-Hoc-Space-Substitution</H1>
15233 Spaces in your input are normally handled specially.
15234 Each space character is replaced
15237 <CENTER><SAMP>* <SPACE></SAMP></CENTER>
15239 in the search query (but not by "* <SPACE> *").
15240 The reason this is done is so the input string
15242 <CENTER><SAMP>Greg Donald</SAMP></CENTER>
15244 (which is converted to "Greg* Donald") will match
15245 the names "Greg Donald",
15246 "Gregory Donald", "Greg F. Donald", and
15247 "Gregory F Donald"; but it won't match "Greg McDonald".
15248 If the "Search-Rule" you were using was "begins-with",
15249 then it would also match the name "Greg Donaldson".
15251 Turning on this feature will disable this substitution.
15253 <End of help on this topic>
15256 ====== h_config_ldap_searchtypes =======
15259 <TITLE>LDAP OPTION: Search-Type</TITLE>
15262 <H1>LDAP OPTION: Search-Type</H1>
15264 This affects the way that LDAP searches are done.
15265 In particular, this tells the server where to look for the string to be matched.
15266 If set to "name" then the string that is being searched for will
15267 be compared with the string in the
15268 "Name" field on the server
15269 (technically, it is the "commonname" field on the server).
15270 "Surname" means we're looking for a
15271 match in the "Surname" field on the
15272 server (actually the "sn" field).
15273 "Givenname" really is "givenname"
15274 and "email" is the electronic mail address (this is actually the field
15275 called "mail" or "electronicmail" on the server).
15276 The other three types are combinations of
15277 the types listed so far. "Name-or-email"
15278 means the string should appear
15279 in either the "name" field OR the "email" field.
15280 Likewise, "surname-or-givenname"
15281 means "surname" OR "givenname"
15282 and "sur-or-given-or-name-or-email" means the obvious thing.
15284 This search TYPE is combined with the
15285 search <A HREF="h_config_ldap_searchrules">RULE</A>
15286 to form the actual search query.
15288 The usual default value for this
15289 option is "sur-or-given-or-name-or-email".
15290 This type of search may be slow on some servers.
15291 Try "name-or-email", which is often
15292 faster, or just "name" if the performance seems to be a problem.
15294 Some servers have been configured with different attribute names for
15296 In other words, instead of using the attribute name "mail"
15297 for the email address field, the server might be configured to use something
15298 else, for example, "rfc822mail" or "internetemailaddress".
15299 Alpine can be configured to use these different attribute names by using
15300 the four configuration options:
15302 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15305 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15308 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15311 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15314 <End of help on this topic>
15317 ====== h_config_ldap_searchrules =======
15320 <TITLE>LDAP OPTION: Search-Rule</TITLE>
15323 <H1>LDAP OPTION: Search-Rule</H1>
15325 This affects the way that LDAP searches are done.
15326 If set to "equals" then
15327 only exact matches count.
15328 "Contains" means that the string you type in
15329 is a substring of what you are matching against.
15330 "Begins-with" and "ends-with"
15331 mean that the string starts or ends with the string you type in.
15333 Spaces in your input are normally handled specially, but you can turn that
15334 special handling off with the
15335 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15338 The usual default value for this option is "begins-with".
15340 <End of help on this topic>
15343 ======= h_config_ldap_email_attr =======
15346 <TITLE>LDAP OPTION: EmailAttribute</TITLE>
15349 <H1>LDAP OPTION: EmailAttribute</H1>
15351 This is the name of the attribute that is searched for when looking for
15352 an email address. The default value for this option is "mail" or
15353 "electronicmail".
15354 If the server you are using uses a different attribute name for the email
15355 address, put that attribute name here.
15357 This will affect the search filter used if your Search-Type is one that
15358 contains a search for "email".
15359 It will also cause the attribute value matching this attribute name to be used
15360 as the email address when you look up an entry from the composer.
15362 <End of help on this topic>
15365 ======= h_config_ldap_sn_attr =======
15368 <TITLE>LDAP OPTION: SurnameAttribute</TITLE>
15371 <H1>LDAP OPTION: SurnameAttribute</H1>
15373 This is the name of the attribute that is searched for when looking for
15374 the surname of the entry. The default value for this option is "sn".
15375 If the server you are using uses a different attribute name for the surname,
15376 put that attribute name here.
15377 This will affect the search filter used if your Search-Type is one that
15378 contains a search for "surname".
15380 <End of help on this topic>
15383 ======= h_config_ldap_gn_attr =======
15386 <TITLE>LDAP OPTION: GivennameAttribute</TITLE>
15389 <H1>LDAP OPTION: GivennameAttribute</H1>
15391 This is the name of the attribute that is searched for when looking for
15392 the given name of the entry. The default value for this option is "givenname".
15393 If the server you are using uses a different attribute name for the given name,
15394 put that attribute name here.
15395 This will affect the search filter used if your Search-Type is one that
15396 contains a search for "givenname".
15398 <End of help on this topic>
15401 ======= h_config_ldap_cn_attr =======
15404 <TITLE>LDAP OPTION: NameAttribute</TITLE>
15407 <H1>LDAP OPTION: NameAttribute</H1>
15409 This is the name of the attribute that is searched for when looking for
15410 the name of the entry. The default value for this option is "cn", which
15411 stands for common name.
15412 If the server you are using uses a different attribute name for the name,
15413 put that attribute name here.
15414 This will affect the search filter used if your Search-Type is one that
15415 contains a search for "name".
15417 <End of help on this topic>
15420 ======= h_config_ldap_time =======
15423 <TITLE>LDAP OPTION: Timelimit</TITLE>
15426 <H1>LDAP OPTION: Timelimit</H1>
15428 This places a limit on the number of seconds the LDAP search will continue.
15429 The default is 30 seconds. A value of 0 means no limit. Note that some servers
15430 may place limits of their own on searches.
15432 <End of help on this topic>
15435 ======= h_config_ldap_size =======
15438 <TITLE>LDAP OPTION: Sizelimit</TITLE>
15441 <H1>LDAP OPTION: Sizelimit</H1>
15443 This places a limit on the number of entries returned by the LDAP server.
15444 A value of 0 means no limit. The default is 0. Note that some servers
15445 may place limits of their own on searches.
15447 <End of help on this topic>
15450 ======= h_config_ldap_cust =======
15453 <TITLE>LDAP OPTION: Custom-Search-Filter</TITLE>
15456 <H1>LDAP OPTION: Custom-Search-Filter</H1>
15458 This one is for advanced users only! If you define this, then the
15459 "Search-Type" and "Search-Rule" defined are both ignored.
15460 However, the feature
15461 <A HREF="h_config_ldap_opts_nosub">"Disable-Ad-Hoc-Space-Substitution"</A>
15462 is still in effect.
15463 That is, the space substitution will take place even in a custom filter unless
15466 If your LDAP service stops working and you suspect it might be because
15467 of your custom filter, just delete this filter and try using the
15468 "Search-Type" and "Search-Rule" instead.
15469 Another option that sometimes causes trouble is the
15470 <A HREF="h_config_ldap_base">"Search-Base"</A> option.
15472 This variable may be set to the string representation of an LDAP search
15473 filter (see RFC1960). In the places where you want the address string to be
15474 substituted in, put a '%s' in this filter string. Here are some examples:
15476 A "Search-Type" of "name" with "Search-Rule" of "begins-with"
15477 is equivalent to the "Custom-Search-Filter"
15481 When you try to match against the string "string" the program replaces
15482 the "%s" with "string" (without the quotes). You may have multiple "%s"'s and
15483 they will all be replaced with the string. There is a limit of 10 "%s"'s.
15485 A "Search-Type" of "name-or-email" with "Search-Rule"
15486 of "contains" is equivalent to
15488 (|(cn=*%s*)(mail=*%s*))
15491 If your server uses a different attribute <EM>name</EM> than
15492 Alpine uses by default,
15493 (for example, it uses "rfc822mail" instead of "mail"),
15494 then you may be able to use one or more of the four attribute configuration
15495 options instead of defining a custom filter:
15497 <LI><A HREF="h_config_ldap_email_attr">"EmailAttribute"</A>
15500 <LI><A HREF="h_config_ldap_cn_attr">"NameAttribute"</A>
15503 <LI><A HREF="h_config_ldap_sn_attr">"SurnameAttribute"</A>
15506 <LI><A HREF="h_config_ldap_gn_attr">"GivennameAttribute"</A>
15509 <End of help on this topic>
15512 ======= h_composer_abook_comment =======
15515 <TITLE>Addressbook Comment Explained</TITLE>
15518 This is a comment to help you remember what this entry is. The WhereIs
15519 command searches comments so that it is easier to find an entry with a comment
15520 you know about attached to it. This field is not used in the outgoing message.
15522 Look <A HREF="h_edit_nav_cmds">here</A>
15523 to see the available Editing and Navigation commands.
15525 <End of help on this topic>
15528 ======= h_composer_abook_addrs =======
15531 <TITLE>Addressbook Lists</TITLE>
15534 <H1>Addressbook Lists</H1>
15536 This is a list of addresses to send to when sending to this address book
15537 entry. Each member of the list may be an address or another nickname from
15538 any of your address books. If it is an address, it is OK to include the
15539 full name field as well as the electronic address portion of that address.
15540 For example, the following are all legitimate entries in this field:
15542 <DL><DT> </DT>
15543 <DD>john (a nickname in your address book)
15544 <DD>jdoe@some.domain
15545 <DD>John Doe <jdoe@some.domain>
15548 The addresses should be listed separated by commas, just like you would
15549 enter them from the composer.
15553 The only difference between a distribution list and a simple entry with a
15554 single address, is that a distribution list has more than one address
15555 listed in the Addresses: field, whereas a simple personal entry has just
15560 For individual address book entries, if there is a full name in the
15561 Fullname: field (filling in the Fullname: field is not required), it is
15562 used. If the full name is specified in the Address: field and not in the
15563 Fullname: field, then the full name from the Address: field is used.
15567 If you type the nickname of a distribution list from one of your address
15568 books in the Lcc: field, then the full name of that list is used in the
15569 To: field. If you put a list in the To: or Cc: fields, that list will be
15570 expanded into all of its addresses. If the list has a full name, then
15571 that will appear at the beginning of the addresses.
15573 <DL><DT> </DT>
15574 <DD>Sewing Club <john@somewhere>, nancy@something.else, Sal
15575 <sal@here.there>
15578 If the first address in the distribution list also has a full name, then
15579 the list full name and that full name are combined into something like the
15582 <DL><DT> </DT>
15583 <DD>Sewing Club -- John Smith <john@somewhere>
15587 If you specify a list via Lcc, the full name is used in the To: line. If
15588 you specify a list in the To: or Cc: fields, then it uses the same method
15589 as for individual entries for filling in the full name.
15593 For help with editing and navigation commands, check the Help for the
15597 <End of help on this topic>
15600 ======= h_config_role_nick =======
15603 <TITLE>Nickname Explained</TITLE>
15606 <H1>Nickname Explained</H1>
15608 This is a nickname to help you.
15609 You should have a different nickname for each role you define.
15610 The nickname will be used in the SETUP ROLE RULES screen to allow you to
15611 pick a role to edit.
15612 It will also be used when you send a message to let you know you are
15613 sending with a different role than you use by default, and
15614 it will be useful for choosing a role when composing with the Role command
15615 or when composing with one of the Role Uses set to With Confirmation.
15616 This field is not used in the outgoing message.
15618 Look <A HREF="h_edit_nav_cmds">here</A>
15619 to see the available Editing and Navigation commands.
15621 <End of help on this topic>
15624 ======= h_config_role_comment =======
15627 <TITLE>Comment Explained</TITLE>
15630 <H1>Comment Explained</H1>
15632 This is a comment to help you.
15633 This comment does not play any functional role, it is simply an optional
15634 comment to help you remember what the rule is for.
15636 Look <A HREF="h_edit_nav_cmds">here</A>
15637 to see the available Editing and Navigation commands.
15639 <End of help on this topic>
15642 ======= h_config_other_nick =======
15645 <TITLE>Nickname Explained</TITLE>
15648 <H1>Nickname Explained</H1>
15650 This is a nickname to help you.
15651 You should have a different nickname for each rule you define.
15652 The nickname will be used in the SETUP OTHER RULES screen to allow you to
15653 pick a rule to edit.
15655 Look <A HREF="h_edit_nav_cmds">here</A>
15656 to see the available Editing and Navigation commands.
15658 <End of help on this topic>
15661 ======= h_config_score_nick =======
15664 <TITLE>Nickname Explained</TITLE>
15667 <H1>Nickname Explained</H1>
15669 This is a nickname to help you.
15670 You should have a different nickname for each scoring rule you define.
15671 The nickname will be used in the SETUP SCORING RULES screen to allow you to
15672 pick a rule to edit.
15674 Look <A HREF="h_edit_nav_cmds">here</A>
15675 to see the available Editing and Navigation commands.
15677 <End of help on this topic>
15680 ======= h_config_incol_nick =======
15683 <TITLE>Nickname Explained</TITLE>
15686 <H1>Nickname Explained</H1>
15688 This is a nickname to help you.
15689 You should have a different nickname for each color rule you define.
15690 The nickname will be used in the SETUP INDEX COLOR RULES screen to allow you to
15691 pick a rule to edit.
15693 Look <A HREF="h_edit_nav_cmds">here</A>
15694 to see the available Editing and Navigation commands.
15696 <End of help on this topic>
15699 ======= h_config_filt_nick =======
15702 <TITLE>Nickname Explained</TITLE>
15705 <H1>Nickname Explained</H1>
15707 This is a nickname to help you.
15708 You should have a different nickname for each filtering rule you define.
15709 The nickname will be used in the SETUP FILTERING RULES screen to allow you to
15710 pick a rule to edit.
15712 Look <A HREF="h_edit_nav_cmds">here</A>
15713 to see the available Editing and Navigation commands.
15715 <End of help on this topic>
15718 ======= h_config_score_topat =======
15721 <TITLE>"To:" Pattern Explained</TITLE>
15724 <H1>"To:" Pattern Explained</H1>
15726 Any text you enter as the "To pattern"
15727 will be compared to the recipients from the To: line of
15728 the message being scored.
15729 When the text you entered matches
15730 all or part of the To: line of a message, then the Score Value
15731 you have specified will be added to the score for the message.
15732 (Any other non-blank parts of the Pattern must match, too.)
15735 You may enter a complete email address, part of an address, or a
15736 list of addresses or partial addresses.
15741 To pattern = friend@public.com
15743 To pattern = rated.net
15745 To pattern = xxx@adults.com
15747 fool@motleyfool.com
15751 Each of those are valid To patterns.
15754 Messages match those patterns if any of the
15755 addresses in the To: line of the message contains the pattern.
15756 If the pattern is a list of patterns
15757 (like the last example above) then it is a match if any of the patterns in
15758 the list match any of the addresses in the To: line.
15759 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15760 present for a match.
15761 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15762 address2 must be present.
15763 That is exactly what using a list does.)
15766 Some messages may be "bounced" to you, and will
15767 have a "Resent-To:" header line.
15768 If the message contains a Resent-To: line
15769 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15770 Alpine will look for
15771 matches to your "To patterns" there, and <EM>NOT</EM> in
15772 the original To: line.
15775 When entering a pattern, you may choose an address from your address book
15776 with the "T" command.
15779 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15780 "!" "toggle NOT" command.
15781 This changes the meaning of the To pattern so that it has the opposite meaning.
15782 It will be considered a match if there are no matches between the
15783 addresses in the To: line and the list of To patterns.
15785 Don't make the mistake of putting the "!" in the data field for
15787 For example, if you type the characters "!frizzle" into the To
15788 pattern, the pattern will look like:
15791 To pattern = !frizzle
15794 This means you want to match the 8 character sequence "!frizzle".
15795 In order to match messages that do not have "frizzle" in
15796 their To field, first type the characters "frizzle" followed
15797 by carriage return for the value of the To pattern, then negate it
15798 by typing the "!" command.
15799 It should end up looking like
15802 ! To pattern = frizzle
15805 You are not limited to using the six standard header patterns that are
15806 normally shown (To, From, Sender, Cc, News, and Subject).
15807 You may add any other header to a Pattern by
15808 using the "eXtraHdr" command to specify a different
15809 message header line; and then the Add or Change command to fill in
15810 a pattern for the new header line, just like you would for a standard header.
15812 A technicality: Since comma is the character used to separate multiple
15813 values in a pattern field, you have to escape comma with a backslash (\) if
15814 you want to include a literal comma in the field.
15815 In other words, if you type a backslash followed by a comma it will
15816 be interpreted as a comma by Alpine, instead of as a separator between
15818 All other backslashes are literal backslashes and should not be escaped.
15820 Look "<A HREF="h_rule_patterns">here</A>"
15821 for more information on Patterns.
15823 Look <A HREF="h_edit_nav_cmds">here</A>
15824 to see the available Editing and Navigation commands.
15826 <End of help on this topic>
15829 ======= h_config_incol_topat =======
15832 <TITLE>"To:" Pattern Explained</TITLE>
15835 <H1>"To:" Pattern Explained</H1>
15837 Any text you enter as the "To pattern"
15838 will be compared to the recipients from the To: lines of
15839 the messages in the index.
15840 When the text you entered matches
15841 all or part of the To: line of a message, then the Index Line Color you have
15842 specified will be used for that line in the index.
15843 (Any other non-blank parts of the Pattern must match, too.)
15846 You may enter a complete email address, part of an address, or a
15847 list of addresses or partial addresses.
15852 To pattern = friend@public.com
15853 To pattern = rated.net
15854 To pattern = xxx@adults.com
15856 fool@motleyfool.com
15860 Each of those are valid To patterns.
15863 Messages match those patterns if any of the
15864 addresses in the To: line of the message contains the pattern.
15865 If the pattern is a list of patterns
15866 (like the last example above) then it is a match if any of the patterns in
15867 the list match any of the addresses in the To: line.
15868 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
15869 present for a match.
15870 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
15871 address2 must be present.
15872 That is exactly what using a list does.)
15875 Some messages may be "bounced" to you, and will
15876 have a "Resent-To:" header line.
15877 If the message contains a Resent-To: line
15878 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
15879 Alpine will look for
15880 matches to your "To patterns" there, and <EM>NOT</EM> in
15881 the original To: line.
15884 When entering a pattern, you may choose an address from your address book
15885 with the "T" command.
15888 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
15889 "!" "toggle NOT" command.
15890 This changes the meaning of the To pattern so that it has the opposite meaning.
15891 It will be considered a match if there are no matches between the
15892 addresses in the To: line and the list of To patterns.
15894 Don't make the mistake of putting the "!" in the data field for
15896 For example, if you type the characters "!frizzle" into the To
15897 pattern, the pattern will look like:
15900 To pattern = !frizzle
15903 This means you want to match the 8 character sequence "!frizzle".
15904 In order to match messages that do not have "frizzle" in
15905 their To field, first type the characters "frizzle" followed
15906 by carriage return for the value of the To pattern, then negate it
15907 by typing the "!" command.
15908 It should end up looking like
15911 ! To pattern = frizzle
15915 You are not limited to using the six standard header patterns that are
15916 normally shown (To, From, Sender, Cc, News, and Subject).
15917 You may add any other header to a Pattern by
15918 using the "eXtraHdr" command to specify a different
15919 message header line; and then the Add or Change command to fill in
15920 a pattern for the new header line, just like you would for a standard header.
15922 A technicality: Since comma is the character used to separate multiple
15923 values in a pattern field, you have to escape comma with a backslash (\) if
15924 you want to include a literal comma in the field.
15925 In other words, if you type a backslash followed by a comma it will
15926 be interpreted as a comma by Alpine, instead of as a separator between
15928 All other backslashes are literal backslashes and should not be escaped.
15930 Look "<A HREF="h_rule_patterns">here</A>"
15931 for more information on Patterns.
15933 Look <A HREF="h_edit_nav_cmds">here</A>
15934 to see the available Editing and Navigation commands.
15936 <End of help on this topic>
15939 ======= h_config_other_topat =======
15942 <TITLE>"To:" Pattern Explained</TITLE>
15945 <H1>"To:" Pattern Explained</H1>
15947 For some of the OTHER RULES actions, there is no message that is being
15949 If that is the case, then only the Current Folder Type is checked.
15950 In particular, this To pattern is ignored.
15951 Actions that fall into this category include both
15952 Sort Order and Index Format.
15954 A technicality: Since comma is the character used to separate multiple
15955 values in a pattern field, you have to escape comma with a backslash (\) if
15956 you want to include a literal comma in the field.
15957 In other words, if you type a backslash followed by a comma it will
15958 be interpreted as a comma by Alpine, instead of as a separator between
15960 All other backslashes are literal backslashes and should not be escaped.
15962 Look "<A HREF="h_rule_patterns">here</A>"
15963 for more information on Patterns.
15965 Look <A HREF="h_edit_nav_cmds">here</A>
15966 to see the available Editing and Navigation commands.
15968 <End of help on this topic>
15971 ======= h_config_filt_topat =======
15974 <TITLE>"To:" Pattern Explained</TITLE>
15977 <H1>"To:" Pattern Explained</H1>
15979 Any text you enter as the "To pattern"
15980 will be compared to the recipients from the To: line of
15981 messages when Alpine opens folders.
15982 When the text you entered matches
15983 all or part of the To: line of a message, then the Filter Action you have
15984 specified will be carried out.
15985 (Any other non-blank parts of the Pattern must match, too.)
15988 You may enter a complete email address, part of an address, or a
15989 list of addresses or partial addresses.
15994 To pattern = friend@public.com
15995 To pattern = rated.net
15996 To pattern = xxx@adults.com
15998 fool@motleyfool.com
16002 Each of those are valid To patterns.
16005 Messages match those patterns if any of the
16006 addresses in the To: line of the message contains the pattern.
16007 If the pattern is a list of patterns
16008 (like the last example above) then it is a match if any of the patterns in
16009 the list match any of the addresses in the To: line.
16010 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
16011 present for a match.
16012 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
16013 address2 must be present.
16014 That is exactly what using a list does.)
16017 Some messages may be "bounced" to you, and will
16018 have a "Resent-To:" header line.
16019 If the message contains a Resent-To: line
16020 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
16021 Alpine will look for
16022 matches to your "To patterns" there, and <EM>NOT</EM> in
16023 the original To: line.
16026 When entering a pattern, you may choose an address from your address book
16027 with the "T" command.
16030 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
16031 "!" "toggle NOT" command.
16032 This changes the meaning of the To pattern so that it has the opposite meaning.
16033 It will be considered a match if there are no matches between the
16034 addresses in the To: line and the list of To patterns.
16036 Don't make the mistake of putting the "!" in the data field for
16038 For example, if you type the characters "!frizzle" into the To
16039 pattern, the pattern will look like:
16042 To pattern = !frizzle
16045 This means you want to match the 8 character sequence "!frizzle".
16046 In order to match messages that do not have "frizzle" in
16047 their To field, first type the characters "frizzle" followed
16048 by carriage return for the value of the To pattern, then negate it
16049 by typing the "!" command.
16050 It should end up looking like
16053 ! To pattern = frizzle
16057 You are not limited to using the six standard header patterns that are
16058 normally shown (To, From, Sender, Cc, News, and Subject).
16059 You may add any other header to a Pattern by
16060 using the "eXtraHdr" command to specify a different
16061 message header line; and then the Add or Change command to fill in
16062 a pattern for the new header line, just like you would for a standard header.
16064 A technicality: Since comma is the character used to separate multiple
16065 values in a pattern field, you have to escape comma with a backslash (\) if
16066 you want to include a literal comma in the field.
16067 In other words, if you type a backslash followed by a comma it will
16068 be interpreted as a comma by Alpine, instead of as a separator between
16070 All other backslashes are literal backslashes and should not be escaped.
16072 Look "<A HREF="h_rule_patterns">here</A>"
16073 for more information on Patterns.
16075 Look <A HREF="h_edit_nav_cmds">here</A>
16076 to see the available Editing and Navigation commands.
16078 <End of help on this topic>
16081 ======= h_config_role_topat =======
16084 <TITLE>"To:" Pattern Explained</TITLE>
16087 <H1>"To:" Pattern Explained</H1>
16089 Any text you enter as the "To pattern"
16090 will be compared to the recipients from the To: line of
16091 the message being replied to or forwarded.
16092 (Any other non-blank parts of the Pattern must match, too.)
16093 In the case of the Compose command, this pattern and the other header
16094 patterns are ignored.
16097 You may enter a complete email address, part of an address, or a
16098 list of addresses or partial addresses.
16103 To pattern = friend@public.com
16104 To pattern = rated.net
16105 To pattern = xxx@adults.com
16107 fool@motleyfool.com
16111 Each of those are valid To patterns.
16114 Messages match those patterns if any of the
16115 addresses in the To: line of the message contains the pattern.
16116 If the pattern is a list of patterns
16117 (like the last example above) then it is a match if any of the patterns in
16118 the list match any of the addresses in the To: line.
16119 (It is not possible to specify two addresses that must <EM>BOTH</EM> be
16120 present for a match.
16121 It is only possible to specify that <EM>EITHER</EM> address1 <EM>OR</EM>
16122 address2 must be present.
16123 That is exactly what using a list does.)
16126 Some messages may be "bounced" to you, and will
16127 have a "Resent-To:" header line.
16128 If the message contains a Resent-To: line
16129 and the feature <A HREF="h_config_use_resentto"><!--#echo var="FEAT_use-resent-to-in-rules"--></A> is turned on,
16130 Alpine will look for
16131 matches to your "To patterns" there, and <EM>NOT</EM> in
16132 the original To: line.
16135 When entering a pattern, you may choose an address from your address book
16136 with the "T" command.
16139 It is possible to add a <EM>NOT</EM> to the To Pattern meaning with the
16140 "!" "toggle NOT" command.
16141 This changes the meaning of the To pattern so that it has the opposite meaning.
16142 It will be considered a match if there are no matches between the
16143 addresses in the To: line and the list of To patterns.
16145 Don't make the mistake of putting the "!" in the data field for
16147 For example, if you type the characters "!frizzle" into the To
16148 pattern, the pattern will look like:
16151 To pattern = !frizzle
16154 This means you want to match the 8 character sequence "!frizzle".
16155 In order to match messages that do not have "frizzle" in
16156 their To field, first type the characters "frizzle" followed
16157 by carriage return for the value of the To pattern, then negate it
16158 by typing the "!" command.
16159 It should end up looking like
16162 ! To pattern = frizzle
16166 You are not limited to using the six standard header patterns that are
16167 normally shown (To, From, Sender, Cc, News, and Subject).
16168 You may add any other header to a Pattern by
16169 using the "eXtraHdr" command to specify a different
16170 message header line; and then the Add or Change command to fill in
16171 a pattern for the new header line, just like you would for a standard header.
16173 A technicality: Since comma is the character used to separate multiple
16174 values in a pattern field, you have to escape comma with a backslash (\) if
16175 you want to include a literal comma in the field.
16176 In other words, if you type a backslash followed by a comma it will
16177 be interpreted as a comma by Alpine, instead of as a separator between
16179 All other backslashes are literal backslashes and should not be escaped.
16181 Look "<A HREF="h_rule_patterns">here</A>"
16182 for more information on Patterns.
16184 Look <A HREF="h_edit_nav_cmds">here</A>
16185 to see the available Editing and Navigation commands.
16187 <End of help on this topic>
16190 ======= h_config_role_frompat =======
16193 <TITLE>"From:" Pattern Explained</TITLE>
16196 <H1>"From:" Pattern Explained</H1>
16198 This is just like the "To pattern" except that it is compared with
16199 the address in the From: line of the message
16200 instead of the addresses from the To: line.
16201 See the help for the To pattern for more information on header patterns.
16203 Look "<A HREF="h_rule_patterns">here</A>"
16204 for more information on Patterns.
16206 Look <A HREF="h_edit_nav_cmds">here</A>
16207 to see the available Editing and Navigation commands.
16209 <End of help on this topic>
16212 ======= h_config_role_senderpat =======
16215 <TITLE>"Sender:" Pattern Explained</TITLE>
16218 <H1>"Sender:" Pattern Explained</H1>
16220 This is just like the "To pattern" except that it is compared with
16221 the address from the Sender: line of the message
16222 instead of the addresses from the To: line.
16223 See the help for the To pattern for more information on header patterns.
16225 Look "<A HREF="h_rule_patterns">here</A>"
16226 for more information on Patterns.
16228 Look <A HREF="h_edit_nav_cmds">here</A>
16229 to see the available Editing and Navigation commands.
16231 <End of help on this topic>
16234 ======= h_config_role_ccpat =======
16237 <TITLE>"Cc:" Pattern Explained</TITLE>
16240 <H1>"Cc:" Pattern Explained</H1>
16242 This is just like the "To pattern" except that it is compared with
16243 the addresses from the Cc: line of the message
16244 instead of the addresses from the To: line.
16245 See the help for the To pattern for more information on header patterns.
16247 Look "<A HREF="h_rule_patterns">here</A>"
16248 for more information on Patterns.
16250 Look <A HREF="h_edit_nav_cmds">here</A>
16251 to see the available Editing and Navigation commands.
16253 <End of help on this topic>
16256 ======= h_config_role_recippat =======
16259 <TITLE>Recipient Pattern Explained</TITLE>
16262 <H1>Recipient Pattern Explained</H1>
16264 This is just like the "To pattern" except that it is compared with
16265 the addresses from both the To: line and the Cc: line of the
16266 message instead of just the addresses from the To: line.
16267 In other words, it is considered a match if the pattern matches
16268 <EM>EITHER</EM> an address in the To: line <EM>OR</EM> an address
16270 (Notice that defining the Recipient pattern does not have the same
16271 effect as defining both the To and Cc patterns.
16272 Recipient is To <EM>OR</EM> Cc; not To <EM>AND</EM> Cc.
16273 It is equivalent to having two different rules;
16274 one with a To pattern and the other with the same Cc pattern.)
16276 A technicality: Since comma is the character used to separate multiple
16277 values in a pattern field, you have to escape comma with a backslash (\) if
16278 you want to include a literal comma in the field.
16279 In other words, if you type a backslash followed by a comma it will
16280 be interpreted as a comma by Alpine, instead of as a separator between
16282 All other backslashes are literal backslashes and should not be escaped.
16284 Look "<A HREF="h_rule_patterns">here</A>"
16285 for more information on Patterns.
16287 Look <A HREF="h_edit_nav_cmds">here</A>
16288 to see the available Editing and Navigation commands.
16290 <End of help on this topic>
16293 ======= h_config_role_particpat =======
16296 <TITLE>Participant Pattern Explained</TITLE>
16299 <H1>Participant Pattern Explained</H1>
16301 This is just like the "To pattern" except that it is compared with
16302 the addresses from the From: line, the To: line, and the Cc: line of the
16303 message instead of just the addresses from the To: line.
16304 In other words, it is considered a match if the pattern matches
16305 <EM>EITHER</EM> an address in the From: line, <EM>OR</EM> an address
16306 in the To: line, <EM>OR</EM> an address in the Cc: line.
16307 (Notice that defining the Participant pattern does not have the same
16308 effect as defining all of the From, To, and Cc patterns.
16309 Participant is From <EM>OR</EM> To <EM>OR</EM> Cc; not
16310 From <EM>AND</EM> To <EM>AND</EM> Cc.
16311 It is equivalent to having three different rules;
16312 one with a From pattern, another with the same To pattern, and a third with
16313 the same Cc pattern.)
16315 A technicality: Since comma is the character used to separate multiple
16316 values in a pattern field, you have to escape comma with a backslash (\) if
16317 you want to include a literal comma in the field.
16318 In other words, if you type a backslash followed by a comma it will
16319 be interpreted as a comma by Alpine, instead of as a separator between
16321 All other backslashes are literal backslashes and should not be escaped.
16323 Look "<A HREF="h_rule_patterns">here</A>"
16324 for more information on Patterns.
16326 Look <A HREF="h_edit_nav_cmds">here</A>
16327 to see the available Editing and Navigation commands.
16329 <End of help on this topic>
16332 ======= h_config_role_newspat =======
16335 <TITLE>News Pattern Explained</TITLE>
16338 <H1>News Pattern Explained</H1>
16340 If this pattern is non-blank, then for this rule to be considered a
16341 match, at least one of the newsgroups from
16342 the Newsgroups line of the message must match this pattern.
16343 If this pattern is a list of patterns, then at least one of the
16344 newsgroups must match at least one of the patterns.
16345 (Any other non-blank parts of the Pattern must match, too.)
16347 It is possible to add a <EM>NOT</EM> to the News Pattern meaning with the
16348 "!" "toggle NOT" command.
16349 This changes the meaning of the News pattern so that it has the opposite meaning.
16350 It will be considered a match if there are no matches between the
16351 addresses in the Newsgroups: line and the list of News patterns.
16353 Don't make the mistake of putting the "!" in the data field for
16355 For example, if you type the characters "!frizzle" into the News
16356 pattern, the pattern will look like:
16359 News pattern = !frizzle
16362 This means you want to match the 8 character sequence "!frizzle".
16363 In order to match messages that do not have "frizzle" in
16364 their Newsgroups header, first type the characters "frizzle" followed
16365 by carriage return for the value of the News pattern, then negate it
16366 by typing the "!" command.
16367 It should end up looking like
16370 ! News pattern = frizzle
16373 A technicality: Since comma is the character used to separate multiple
16374 values in a pattern field, you have to escape comma with a backslash (\) if
16375 you want to include a literal comma in the field.
16376 In other words, if you type a backslash followed by a comma it will
16377 be interpreted as a comma by Alpine, instead of as a separator between
16379 All other backslashes are literal backslashes and should not be escaped.
16382 Look "<A HREF="h_rule_patterns">here</A>"
16383 for more information on Patterns.
16385 Look <A HREF="h_edit_nav_cmds">here</A>
16386 to see the available Editing and Navigation commands.
16388 <End of help on this topic>
16391 ======= h_config_role_subjpat =======
16394 <TITLE>"Subject:" Pattern Explained</TITLE>
16397 <H1>"Subject:" Pattern Explained</H1>
16399 This is similar to the other parts of the Pattern.
16400 It is compared with
16401 the contents from the Subject of the message.
16403 Look "<A HREF="h_rule_patterns">here</A>"
16404 for more information on Patterns.
16406 It is possible to add a <EM>NOT</EM> to the Subject Pattern meaning with the
16407 "!" "toggle NOT" command.
16408 This changes the meaning of the Subject pattern so that it has the opposite meaning.
16409 It will be considered a match if there are no matches between the
16410 text in the Subject: line and the list of Subject patterns.
16413 If you wish to have a header pattern that is not one of the six standard
16414 header patterns, you may add it with the "eXtraHdr" command.
16416 A technicality: Since comma is the character used to separate multiple
16417 values in a pattern field, you have to escape comma with a backslash (\) if
16418 you want to include a literal comma in the field.
16419 In other words, if you type a backslash followed by a comma it will
16420 be interpreted as a comma by Alpine, instead of as a separator between
16422 All other backslashes are literal backslashes and should not be escaped.
16424 Look <A HREF="h_edit_nav_cmds">here</A>
16425 to see the available Editing and Navigation commands.
16427 <End of help on this topic>
16430 ======= h_config_role_alltextpat =======
16433 <TITLE>AllText Pattern Explained</TITLE>
16436 <H1>AllText Pattern Explained</H1>
16438 This is similar to the header patterns.
16439 Instead of comparing with text in a particular header field it
16440 is compared with all of the text in the message header and body.
16442 It is possible to add a <EM>NOT</EM> to the AllText Pattern meaning with the
16443 "!" "toggle NOT" command.
16444 This changes the meaning of the AllText pattern so that it has the opposite meaning.
16445 It will be considered a match if there are no matches between the
16446 text of the message and the list of AllText patterns.
16448 Don't make the mistake of putting the "!" in the data field for
16450 For example, if you type the characters "!frizzle" into the AllText
16451 pattern, the pattern will look like:
16454 AllText pattern = !frizzle
16457 This means you want to match the 8 character sequence "!frizzle".
16458 In order to match messages that do not have "frizzle" in
16459 the text of the message, first type the characters "frizzle" followed
16460 by carriage return for the value of the AllText pattern, then negate it
16461 by typing the "!" command.
16462 It should end up looking like
16465 ! AllText pattern = frizzle
16468 It is possible that you may notice degraded performance when using
16471 A technicality: Since comma is the character used to separate multiple
16472 values in a pattern field, you have to escape comma with a backslash (\) if
16473 you want to include a literal comma in the field.
16474 In other words, if you type a backslash followed by a comma it will
16475 be interpreted as a comma by Alpine, instead of as a separator between
16477 All other backslashes are literal backslashes and should not be escaped.
16479 Look "<A HREF="h_rule_patterns">here</A>"
16480 for more information on Patterns.
16482 Look <A HREF="h_edit_nav_cmds">here</A>
16483 to see the available Editing and Navigation commands.
16485 <End of help on this topic>
16488 ======= h_config_role_bodytextpat =======
16491 <TITLE>BodyText Pattern Explained</TITLE>
16494 <H1>BodyText Pattern Explained</H1>
16496 This is similar to the header patterns.
16497 Instead of comparing with text in a particular header field it
16498 is compared with all of the text in the message body.
16500 It is possible to add a <EM>NOT</EM> to the BodyText Pattern meaning with the
16501 "!" "toggle NOT" command.
16502 This changes the meaning of the BodyText pattern so that it has the opposite meaning.
16503 It will be considered a match if there are no matches between the
16504 text of the body of the message and the list of BodyText patterns.
16506 Don't make the mistake of putting the "!" in the data field for
16508 For example, if you type the characters "!frizzle" into the BodyText
16509 pattern, the pattern will look like:
16512 BdyText pattern = !frizzle
16515 This means you want to match the 8 character sequence "!frizzle".
16516 In order to match messages that do not have "frizzle" in
16517 their BodyText, first type the characters "frizzle" followed
16518 by carriage return for the value of the BodyText pattern, then negate it
16519 by typing the "!" command.
16520 It should end up looking like
16523 ! BodyText pattern = frizzle
16526 It is possible that you may notice degraded performance when using
16529 A technicality: Since comma is the character used to separate multiple
16530 values in a pattern field, you have to escape comma with a backslash (\) if
16531 you want to include a literal comma in the field.
16532 In other words, if you type a backslash followed by a comma it will
16533 be interpreted as a comma by Alpine, instead of as a separator between
16535 All other backslashes are literal backslashes and should not be escaped.
16537 Look "<A HREF="h_rule_patterns">here</A>"
16538 for more information on Patterns.
16540 Look <A HREF="h_edit_nav_cmds">here</A>
16541 to see the available Editing and Navigation commands.
16543 <End of help on this topic>
16546 ======= h_config_role_charsetpat =======
16549 <TITLE>Character Set Pattern Explained</TITLE>
16552 <H1>Character Set Pattern Explained</H1>
16554 A message may use one or more character sets.
16555 This part of the Pattern matches messages that make use of
16556 certain specified character sets.
16557 It will be considered a match if a message uses any of the character
16558 sets in the list you give here.
16561 When filling in a value for this field, you may use
16562 the "T" command, which presents you with a large list of
16563 possible character sets to choose from.
16564 You may also just type in the name of a character set, and it need not
16565 be one that Alpine knows about.
16568 Besides actual character set names (for example, ISO-8859-7, KOI8-R, or
16569 GB2312) you may also use some shorthand names that Alpine provides.
16570 These names are more understandable shorthand names for sets of
16571 character set names.
16572 Two examples are "Cyrillic" and "Greek".
16573 Selecting one of these shorthand names is equivalent to selecting all of
16574 the character sets that make up the set.
16575 You can see all of these shorthand names and the lists of character sets
16576 they stand for by typing the "T" command.
16579 For the purposes of this Pattern,
16580 Alpine will search through a message for all of the text parts and
16581 collect the character sets declared for each part.
16582 It will also look in the Subject line for a character set used there.
16583 Alpine does not actually look at the text of the message or the text
16584 of the Subject to determine if a declared character set is actually
16585 used, it looks only at the declarations themselves in the MIME part headers
16586 and in the Subject.
16589 It is possible to add a <EM>NOT</EM> to the Character Set Pattern meaning with the
16590 "!" "toggle NOT" command.
16591 This changes the meaning of the Character Set pattern so that
16592 it has the opposite meaning.
16593 It will be considered a match if none of the character sets in the
16594 list are used in a message.
16596 Don't make the mistake of putting the "!" in the data field for
16598 For example, if you type the characters "!GB2312" into the
16599 Character Set pattern, the pattern will look like:
16602 Charset pattern = !GB2312
16605 This means you want to match the 7 character sequence "!GB2312".
16606 In order to match messages that do not have the
16607 character set "GB2312"
16608 set, first type the characters "GB2312" followed
16609 by carriage return for the value of the Character Set pattern, then negate it
16610 by typing the "!" command.
16611 It should end up looking like
16614 ! Charset pattern = GB2312
16617 A technicality: Since comma is the character used to separate multiple
16618 values in a pattern field, you have to escape comma with a backslash (\) if
16619 you want to include a literal comma in the field.
16620 In other words, if you type a backslash followed by a comma it will
16621 be interpreted as a comma by Alpine, instead of as a separator between
16623 All other backslashes are literal backslashes and should not be escaped.
16625 Look "<A HREF="h_rule_patterns">here</A>"
16626 for more information on Patterns.
16628 Look <A HREF="h_edit_nav_cmds">here</A>
16629 to see the available Editing and Navigation commands.
16631 <End of help on this topic>
16634 ======= h_config_role_keywordpat =======
16637 <TITLE>Keyword Pattern Explained</TITLE>
16640 <H1>Keyword Pattern Explained</H1>
16642 A folder may have user-defined keywords.
16643 These are similar to the Important flag, which the user may set using the
16645 The difference is that the Important flag is always present for each folder.
16646 User-defined keywords are picked by the user.
16647 You may add new keywords by defining them in the
16648 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
16649 After you have added a potential keyword with the <!--#echo var="VAR_keywords"--> option,
16650 the Flag command may be used to set or clear the keyword on individual messages.
16651 If you have given a keyword a nickname when configuring it,
16652 that nickname may be used instead of the actual keyword.
16655 When filling in a value for this field, it may be easiest to use
16656 the "T" command, which presents you with a list of the keywords
16657 you have defined to choose from.
16660 This part of the Pattern matches messages with certain keywords set.
16661 It will be considered a match if a message has any of the keywords in the
16663 A keyword that you have not defined using the
16664 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16665 will not be a match.
16668 It is possible to add a <EM>NOT</EM> to the Keyword Pattern meaning with the
16669 "!" "toggle NOT" command.
16670 This changes the meaning of the Keyword pattern so that it has the opposite meaning.
16671 It will be considered a match if none of the keywords in the list are set
16673 A keyword that you have not defined using the
16674 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen
16675 will not be a match, so a <EM>NOT</EM> of that keyword does match.
16677 Don't make the mistake of putting the "!" in the data field for
16679 For example, if you type the characters "!frizzle" into the Keyword
16680 pattern, the pattern will look like:
16683 Keyword pattern = !frizzle
16686 This means you want to match the 8 character sequence "!frizzle".
16687 In order to match messages that do not have the keyword "frizzle"
16688 set, first type the characters "frizzle" followed
16689 by carriage return for the value of the Keyword pattern, then negate it
16690 by typing the "!" command.
16691 It should end up looking like
16694 ! Keyword pattern = frizzle
16697 A technicality: Since comma is the character used to separate multiple
16698 values in a pattern field, you have to escape comma with a backslash (\) if
16699 you want to include a literal comma in the field.
16700 In other words, if you type a backslash followed by a comma it will
16701 be interpreted as a comma by Alpine, instead of as a separator between
16703 All other backslashes are literal backslashes and should not be escaped.
16705 Look "<A HREF="h_rule_patterns">here</A>"
16706 for more information on Patterns.
16708 Look <A HREF="h_edit_nav_cmds">here</A>
16709 to see the available Editing and Navigation commands.
16711 <End of help on this topic>
16714 ======= h_config_role_arbpat =======
16717 <TITLE>Extra Header Patterns Explained</TITLE>
16720 <H1>Extra Header Patterns Explained</H1>
16722 The header patterns that come after the Participant pattern but before the
16723 AllText pattern are extra header patterns that you have added to a rule's
16724 Pattern. These are just like the other header patterns except that
16725 the contents of the particular header listed on the left hand side will
16726 be used for comparisons.
16728 The "eXtraHdr" command may be used to add more of these
16729 header patterns to the rule you are editing.
16731 The "RemoveHdr" command may be used to delete the highlighted
16732 extra header pattern from the rule you are editing.
16734 It is possible to add a <EM>NOT</EM> to the Extra Header Pattern meaning with the
16735 "!" "toggle NOT" command.
16736 This changes the meaning of the pattern so that it has the opposite meaning.
16737 It will be considered a match if there are no matches between the
16738 text in the header line and the list of patterns.
16740 Don't make the mistake of putting the "!" in the data field for
16742 For example, if you type the characters "!frizzle" into the
16743 pattern, the pattern will look like:
16746 Xyz pattern = !frizzle
16749 This means you want to match the 8 character sequence "!frizzle".
16750 In order to match messages that do not have "frizzle" in
16751 their Xyz field, first type the characters "frizzle" followed
16752 by carriage return for the value of the pattern, then negate it
16753 by typing the "!" command.
16754 It should end up looking like
16757 ! Xyz pattern = frizzle
16761 A technicality: Since comma is the character used to separate multiple
16762 values in a pattern field, you have to escape comma with a backslash (\) if
16763 you want to include a literal comma in the field.
16764 In other words, if you type a backslash followed by a comma it will
16765 be interpreted as a comma by Alpine, instead of as a separator between
16767 All other backslashes are literal backslashes and should not be escaped.
16769 Look "<A HREF="h_rule_patterns">here</A>"
16770 for more information on Patterns.
16772 Look <A HREF="h_edit_nav_cmds">here</A>
16773 to see the available Editing and Navigation commands.
16775 <End of help on this topic>
16778 ======= h_config_role_cat_cmd =======
16781 <TITLE>Categorizer Command Explained</TITLE>
16784 <H1>Categorizer Command Explained</H1>
16786 This is a command that is run with its standard input set to the message
16787 being checked and its standard output discarded.
16788 The full directory path should be specified.
16789 The command will be run and then its exit status will be checked against
16790 the Exit Status Interval, which defaults to just the value zero.
16791 If the exit status of the command falls in the interval, it is considered
16792 a match, otherwise it is not a match.
16795 This option may actually be a list of commands.
16796 The first one that exists and is executable is used.
16797 That makes it possible to use the same configuration with Unix Alpine and
16801 If none of the commands in the list exists and is executable then the rule
16802 is <EM>not</EM> a match.
16803 If it is possible that the command may not exist, you should be careful
16804 to structure your rules so that nothing destructive
16805 happens when the command does not exist.
16806 For example, you might have a filter that filters away spam when there is
16807 a match but does nothing when there is not a match.
16808 That would cause no harm if the command didn't exist.
16809 However, if you have a filter that filters away spam when there is not
16810 a match and keeps it when there is a match, that would filter everything
16811 if the categorizer command didn't exist.
16813 Here is an <A HREF="h_config_role_cat_cmd_example">example</A>
16814 setup for the bogofilter filter.
16817 Look "<A HREF="h_rule_patterns">here</A>"
16818 for more information on Patterns.
16820 Look <A HREF="h_edit_nav_cmds">here</A>
16821 to see the available Editing and Navigation commands.
16823 <End of help on this topic>
16826 ======= h_config_role_cat_cmd_example =======
16829 <TITLE>Categorizer Command Example</TITLE>
16832 <H1>Categorizer Command Example</H1>
16835 (<A HREF="http://bogofilter.sourceforge.net/">http://bogofilter.sourceforge.net/</A>)
16836 is a mail filter that attempts to classify mail as spam or
16837 non-spam using statistical analysis of the message content.
16838 When run with no arguments and a message as standard input, it exits with
16839 exit status 0 if it thinks a message is spam and 1 if it thinks
16841 To use bogofilter as your Categorizer Command you would simply set Command to
16842 the pathname of the bogofilter program.
16845 <CENTER><SAMP>Command = /usr/local/bin/bogofilter</SAMP></CENTER>
16847 Exit status of zero is what you are interested in, so you'd set the
16848 Exit Status Interval to
16850 <CENTER><SAMP>Exit Status Interval = (0,0)</SAMP></CENTER>
16853 In order to prevent downloading an entire huge message to check for spam, you
16854 might want to set the Character Limit to a few thousand characters (the
16855 assumption being that the spam will reveal itself in those characters)
16857 <CENTER><SAMP>Character Limit = 50000</SAMP></CENTER>
16860 You would probably use bogofilter in an Alpine Filter Rule, and have the action
16861 be to move the message to a spam folder.
16862 It would usually be wise to also check the "Message is Recent"
16863 part of the rule so that messages are only checked when they first arrive,
16864 and to restrict the Current Folder Type to just your INBOX.
16865 The reason for checking only Recent messages is to save the time it takes
16866 to run bogofilter on each message.
16867 As an experiment, you might start out by using this in an Indexcolor Rule
16868 instead of a Filter Rule.
16869 In that case, you probably wouldn't check the Recent checkbox.
16871 The use described above assumes that you are somehow maintaining bogofilter's
16872 database of words associated with spam and non-spam messages.
16873 One way to start your database would be to select a bunch of spam messages
16874 in Alpine (you might Save spam messages to a special folder or use Alpine's
16875 Select command to select several) and then Apply
16876 (<A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>)
16877 a pipe command to the spam messages.
16878 For example, you could have a shell script or an alias
16879 called <EM>this_is_spam</EM>, which would simply be the command
16881 <CENTER><SAMP>bogofilter -s</SAMP></CENTER>
16884 It is probably best to use the pipe command's Raw Text, With Delimiter,
16885 and Free Output options,
16886 which are at the bottom of the screen when you type the pipe command.
16887 That's because bogofilter expects the raw message as input, and uses
16888 the Delimiters to tell when a new message starts.
16889 You would not need to use a separate pipe for each message, because
16890 bogofilter can handle multiple messages at once.
16892 Similarly, you would select a group of non-spam messages
16893 and run them through a <EM>this_is_nonspam</EM> script
16894 that was something like
16896 <CENTER><SAMP>bogofilter -n</SAMP></CENTER>
16899 For the more adventurous, the next step might be to automate the upkeep of
16900 the bogofilter database.
16901 It might make more sense to have bogofilter be part of the delivery process,
16902 but it is also possible to do it entirely from within Alpine.
16903 Instead of using just plain "bogofilter" as the Categorizer Command,
16904 the "-u" argument will cause bogofilter to update the database.
16906 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16908 You'd want a couple more aliases or shell scripts called something like
16909 <EM>change_to_spam</EM>
16911 <CENTER><SAMP>bogofilter -Ns</SAMP></CENTER>
16914 <EM>change_to_nonspam</EM>
16916 <CENTER><SAMP>bogofilter -Sn</SAMP></CENTER>
16918 When you run across a message in your INBOX that should have been
16919 classified as spam you would pipe it to the change_to_spam script, and
16920 when you run across a message in your spam folder that should have been
16921 left in your INBOX you would pipe it through change_to_nonspam.
16924 There is a technical problem with this approach.
16925 Alpine may check your filters more than once.
16926 In particular, every time you start Alpine the filters will be checked for
16928 Also, if you have any filters that depend on message state (New, Deleted, etc.)
16929 then Alpine will recheck for matches in messages that have changed state
16930 at the time you close the folder and before expunging.
16931 This is usually ok.
16932 However, in this case it is a problem because the command
16934 <CENTER><SAMP>Command = /usr/local/bin/bogofilter -u</SAMP></CENTER>
16936 has the side effect of updating the database.
16937 So you run the risk of updating the database multiple times for a single
16938 message instead of updating it just once per message.
16939 There are some ways to work around this problem.
16940 What you need is a way to mark the message after you have run the filter.
16941 One way to mark messages is with the use of a keyword (say "Bogo").
16942 Besides having the filter move the message to a spam folder, also have it
16943 set the Bogo keyword.
16944 (Note that you will have to set up the "Bogo" keyword in the
16945 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in Setup/Config.)
16946 This rule can only set the Bogo keyword for the messages that it matches.
16947 You will also need to add a second rule right after this one that
16948 matches all the messages that don't have the Bogo keyword set
16949 (put the keyword in the Keyword pattern and toggle
16950 the Not with the ! command)
16951 and takes the action of setting it.
16952 Then change the "bogofilter -u" rule so that it won't be a match
16953 (and so it won't re-run the bogofilter command) if the keyword is already
16956 What you will end up with is a rule that runs "bogofilter -u"
16957 on all messages that don't have the Bogo keyword set.
16958 This will have the side effect of inserting that message in the bogofilter
16959 database, match or not.
16960 If this rule matches (it is spam), the Bogo keyword will be set and
16961 the message will be moved to a spam folder.
16962 If it does not match, the
16963 following rule will mark the message by turning on the keyword.
16964 This second rule should be a non-terminating
16965 (<A HREF="h_config_filt_opts_nonterm">Dont-Stop-Even-if-Rule-Matches</A>)
16966 rule so that it doesn't stop the filtering process before the rest of
16967 your rules are consulted.
16970 In summary, the first rule is something like
16972 Nickname = bogofilter -u rule
16973 Current Folder Type =
16977 ! Keyword pattern = Bogo
16979 External Categorizer Commands =
16980 Command = /usr/local/bin/bogofilter -u
16981 Exit Status Interval = (0,0)
16982 Character Limit = <No Value Set: using "-1"> (optionally set this)
16988 Set These Keywords = Bogo
16991 and the following rule is
16993 Nickname = Set Bogo Keyword
16994 Current Folder Type =
16998 ! Keyword pattern = Bogo
17001 (*) Just Set Message Status
17003 Set These Keywords = Bogo
17006 [X] dont-stop-even-if-rule-matches
17009 If it is possible for you to insert bogofilter in the delivery process instead
17010 of having it called from Alpine you could prevent having to wait
17011 for the bogofilter processing while you read your mail.
17012 You would have bogofilter add a header to the message at the time of delivery
17013 that identified it as spam or nonspam.
17014 With this method, you could avoid using a Categorizer Command while running Alpine,
17015 and just match on the header instead.
17016 You might still want to use the scripts mentioned above to initialize the
17017 database or to re-classify wrongly classified messages.
17020 Finally, it isn't for the faint-hearted,
17021 but it is also possible to run bogofilter from PC-Alpine.
17022 You can install Cygwin from
17023 <A HREF="http://www.cygwin.com/">http://www.cygwin.com/</A> and
17024 then compile bogofilter in the cygwin environment, and run it from
17026 You would end up with a Categorizer command that looked something like
17028 <CENTER><SAMP>Command = C:\cygwin\bin\bogofilter.exe -u</SAMP></CENTER>
17030 Note that the ".exe" extension is explicit,
17031 and that the bogofilter.exe executable should be in the same directory
17035 <End of help on this topic>
17038 ======= h_config_role_cat_status =======
17041 <TITLE>Exit Status Interval Explained</TITLE>
17044 <H1>Exit Status Interval Explained</H1>
17046 The categorizer command is run and the result is the exit status of
17048 If that exit status falls in the Exit Status Interval
17049 then it is considered a match, otherwise it is not a match.
17050 Of course for the entire rule to match, it must also be checked against
17051 the other defined parts of the Pattern.
17053 The Exit Status Interval defaults to the single value 0 (zero).
17054 If you define it, it should be set to something like:
17056 <CENTER><SAMP>(min_exit_value,max_exit_value)</SAMP></CENTER>
17058 where "min_exit_value" and "max_exit_value" are integers.
17059 The special values "INF" and "-INF" may be used for large
17060 positive and negative integers.
17062 Actually, a list of intervals may be used if you wish.
17063 A list would look like
17065 <CENTER><SAMP>(min_exit_value1,max_exit_value1),(min_exit_value2,max_exit_value2),...</SAMP></CENTER>
17067 When there is an Exit Status Interval defined, it is a match if the exit status
17068 of the categorizer command is contained in any of the intervals.
17069 The intervals include both endpoints.
17071 The default interval is
17073 <CENTER><SAMP>(0,0)</SAMP></CENTER>
17075 and it matches only if the command exits with exit status equal to zero.
17078 Look "<A HREF="h_rule_patterns">here</A>"
17079 for more information on Patterns.
17081 Look <A HREF="h_edit_nav_cmds">here</A>
17082 to see the available Editing and Navigation commands.
17084 <End of help on this topic>
17087 ======= h_config_role_cat_limit =======
17090 <TITLE>Character Limit Explained</TITLE>
17093 <H1>Character Limit Explained</H1>
17095 Setting this option makes it possible to limit how much of the message
17096 is made available to the categorizer command as input.
17097 The default value (-1) means that the entire message is fed to the
17099 A value of 0 (zero) means that only the headers of the message are
17101 A positive integer means that the headers plus that many characters from
17102 the body of the message are passed to the categorizer.
17105 Look "<A HREF="h_rule_patterns">here</A>"
17106 for more information on Patterns.
17108 Look <A HREF="h_edit_nav_cmds">here</A>
17109 to see the available Editing and Navigation commands.
17111 <End of help on this topic>
17114 ======= h_config_role_age =======
17117 <TITLE>Age Interval Explained</TITLE>
17120 <H1>Age Interval Explained</H1>
17122 The Age Interval, if defined, is part of the Pattern.
17123 If you use this, it should be set to something like:
17125 <CENTER><SAMP>(min_age,max_age)</SAMP></CENTER>
17127 where "min_age" and "max_age" are non-negative integers.
17128 The special value "INF" may be used for the max value.
17129 It represents infinity.
17131 In rare cases it may be useful to use the more general form of the value,
17132 which is a comma-separated list of intervals.
17133 It would look something like:
17135 <CENTER><SAMP>(min_age1,max_age1),(min_age2,max_age2),...</SAMP></CENTER>
17137 When there is an Age Interval defined, it is a match if the age, in days, of
17138 the message is contained in the interval.
17139 The interval includes both endpoints.
17140 If the option is set to a list of intervals then it is a match if the
17141 age of the message is contained in any of the intervals.
17143 Even though this option is called Age, it isn't actually
17144 the <EM>age</EM> of the message.
17145 Instead, it is how many days ago the message arrived in one of your folders.
17146 If the current time is a little past midnight, then a message that arrived
17147 just before midnight arrived yesterday, even though the message is only
17149 By default, the date being used is not the date in the Date
17150 header of the message.
17151 It is the date that the message arrived in one of your folders.
17152 When you Save a message from one folder to another that arrival date
17154 If you would like to use the date in the Date header that is possible.
17156 <A HREF="h_config_filt_opts_sentdate">"Use-Date-Header-For-Age"</A>
17157 near the bottom of the rule definition.
17159 A value of 0 is today, 1 is yesterday, 2 is the day before yesterday, and so on.
17162 <CENTER><SAMP>(2,2)</SAMP></CENTER>
17164 matches all messages that arrived on the day before yesterday.
17167 <CENTER><SAMP>(180,INF)</SAMP></CENTER>
17169 matches all messages that arrived at least 180 days before today.
17172 <CENTER><SAMP>(0,1)</SAMP></CENTER>
17174 matches all messages that arrived today or yesterday.
17177 Look "<A HREF="h_rule_patterns">here</A>"
17178 for more information on Patterns.
17180 Look <A HREF="h_edit_nav_cmds">here</A>
17181 to see the available Editing and Navigation commands.
17183 <End of help on this topic>
17186 ======= h_config_role_size =======
17189 <TITLE>Size Interval Explained</TITLE>
17192 <H1>Size Interval Explained</H1>
17194 The Size Interval, if defined, is part of the Pattern.
17195 If you use this, it should be set to something like:
17197 <CENTER><SAMP>(min_size,max_size)</SAMP></CENTER>
17199 where "min_size" and "max_size" are non-negative integers.
17200 The special value "INF" may be used for the max value.
17201 It represents infinity.
17203 In rare cases it may be useful to use the more general form of the value,
17204 which is a comma-separated list of intervals.
17205 It would look something like:
17207 <CENTER><SAMP>(min_size1,max_size1),(min_size2,max_size2),...</SAMP></CENTER>
17209 When there is a Size Interval defined, it is a match if the size of
17210 the message is contained in the interval.
17211 The interval includes both endpoints.
17212 If the option is set to a list of intervals then it is a match if the
17213 size of the message is contained in any of the intervals.
17217 <CENTER><SAMP>(10000,50000)</SAMP></CENTER>
17219 matches all messages with sizes greater than or equal to 10000, and less
17220 than or equal to 50000.
17223 <CENTER><SAMP>(100000,INF)</SAMP></CENTER>
17225 matches all messages with sizes greater than or equal to 100000.
17228 Look "<A HREF="h_rule_patterns">here</A>"
17229 for more information on Patterns.
17231 Look <A HREF="h_edit_nav_cmds">here</A>
17232 to see the available Editing and Navigation commands.
17234 <End of help on this topic>
17237 ======= h_config_role_scorei =======
17240 <TITLE>Score Interval Explained</TITLE>
17243 <H1>Score Interval Explained</H1>
17245 The Score Interval, if defined, is part of the Pattern.
17246 If you use this, it should be set to something like:
17248 <CENTER><SAMP>(min_score,max_score)</SAMP></CENTER>
17250 where "min_score" and "max_score" are integers between
17252 The special values "-INF" and "INF" may be used for
17253 the min and max values.
17254 These represent negative and positive infinity.
17256 Actually, the value may be a list of intervals rather than just a
17257 single interval if that is useful.
17258 The elements of the list are separated by commas like:
17260 <CENTER><SAMP>(min_score1,max_score1),(min_score2,max_score2),...</SAMP></CENTER>
17262 When there is a Score Interval defined, it is a match if the score for
17263 the message is contained in any of the intervals.
17264 The intervals include both endpoints.
17265 The score for a message is calculated by looking at every scoring rule
17266 defined and adding up the Score Values for the rules that match the message.
17267 Scoring rules are created using the
17268 <A HREF="h_rules_score">"SETUP SCORING"</A> screen.
17271 Look "<A HREF="h_rule_patterns">here</A>"
17272 for more information on Patterns.
17274 Look <A HREF="h_edit_nav_cmds">here</A>
17275 to see the available Editing and Navigation commands.
17277 <End of help on this topic>
17280 ======= h_config_role_fldr_type =======
17283 <TITLE>Current Folder Type Explained</TITLE>
17286 <H1>Current Folder Type Explained</H1>
17288 The Current Folder Type is part of the role's Pattern.
17289 It refers to the type of the currently open folder, which is the folder
17290 you were last looking at from the MESSAGE INDEX or MESSAGE TEXT screen.
17291 In order for a role to be considered a match, the current folder must
17292 be of the type you set here.
17293 The three types "Any", "News", and "Email" are
17294 all what you might think.
17296 If the Current Folder Type for a role's Pattern is set to "News", for
17298 that role will only be a match if the current folder is a newsgroup and
17299 the rest of the Pattern matches.
17300 The value "Specific" may be used when you want to limit the match
17301 to a specific folder (not just a specific type of folder), or to a list of
17304 In order to match a specific folder you Select the "Specific"
17305 button <EM>AND</EM> fill in
17306 the name (or list of names) of
17307 the folder in the "Folder List" field.
17308 If the current folder is any of the folders in the list, that is considered
17310 The name of each folder in the list may be either "INBOX",
17311 the technical specification
17312 of the folder (like what appears in your configuration file) or, if the
17313 folder is one of your incoming folders, it may be the nickname you've given
17315 Here are a couple samples of specific folder names:
17317 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17319 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17321 The easiest way to fill in the "Folder List" field is to use
17322 the "T" command that is available when the "Folder List" line is
17323 highlighted, or to use the "Take" command with the configuration
17325 <A HREF="h_config_enable_role_take">"<!--#echo var="FEAT_enable-rules-under-take"-->"</A>
17327 Note that you won't be able to edit the "Folder List" line unless the
17328 Current Folder Type is set to "Specific", and any value that
17329 "Folder List" has is ignored unless the type
17330 is set to "Specific".
17332 When reading a newsgroup, there may be a performance penalty
17333 incurred when collecting the information necessary to check a Pattern.
17334 For this reason, the default Current Folder Type is set to "Email".
17336 Look "<A HREF="h_rule_patterns">here</A>"
17337 for more information on Patterns.
17339 Look <A HREF="h_edit_nav_cmds">here</A>
17340 to see the available Editing and Navigation commands.
17342 <End of help on this topic>
17345 ======= h_config_filt_rule_type =======
17348 <TITLE>Filter Action Explained</TITLE>
17351 <H1>Filter Action Explained</H1>
17353 The Filter Action specifies the action to be taken when the Pattern is a
17355 It may be set to "Delete" "Move", or
17356 "Just Set Message Status".
17358 If it is set to "Delete", then the message that matches the
17359 Pattern will be deleted from the open folder.
17361 If it is set to "Move", then the name of the folder to which
17362 the matching message should be moved is given in the "Folder List" field on the
17363 next line of the screen.
17364 A list of folders separated by commas may be given, in which case the
17365 message will be copied to all of the folders in the list before it is
17368 If it is set to neither of those two values (it is set to the value
17369 labeled "Just Set Message Status") then the message status
17370 setting will happen
17371 but the message will not be deleted or moved.
17373 If you are Moving a message you may also set Message Status if you wish.
17375 The easiest way to fill in the "Folder List" field is to use
17376 the T command that is available when the "Folder List" line is
17378 Note that you won't be able to edit the "Folder List" line unless the
17379 Filter Action is set to "Move", and any value that
17380 "Folder List" has is ignored unless the type
17381 is set to "Move".
17383 There are a few tokens that may be used in the names in the Folder List.
17384 They are all related to the date on which the filtering is taking place.
17385 The tokens are words surrounded by underscores.
17386 For example, if you want your filter to move messages to a folder named
17387 <P><CENTER><SAMP>abc-year-mon</SAMP></CENTER><P>
17388 you could specify the folder as
17389 <P><CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER><P>
17390 which would result in a file named something like
17391 <P><CENTER><SAMP>abc-2004-oct</SAMP></CENTER><P>
17393 <P><CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER><P>
17394 which would result in a file named something like
17395 <P><CENTER><SAMP>abc-04-10</SAMP></CENTER><P>
17396 The available tokens are listed
17397 <A HREF="h_index_tokens">here</A>.
17399 Look "<A HREF="h_rule_patterns">here</A>"
17400 for more information on Patterns.
17402 Look <A HREF="h_edit_nav_cmds">here</A>
17403 to see the available Editing and Navigation commands.
17405 <End of help on this topic>
17408 ======= h_config_score_fldr_type =======
17411 <TITLE>Current Folder Type Explained</TITLE>
17414 <H1>Current Folder Type Explained</H1>
17416 The Current Folder Type is part of the scoring rule's Pattern.
17417 It refers to the type of the folder that
17418 the message being scored is in.
17419 In order for a rule to be considered a match, the current folder must
17420 be of the type you set here.
17421 The three types "Any", "News", and "Email" are
17422 all what you might think.
17424 If the Current Folder Type for a Pattern is set to "News", for
17426 that Pattern will only match if the current folder is a newsgroup and
17427 the rest of the Pattern matches.
17428 The value "Specific" may be used when you want to limit the match
17429 to a specific folder (not just a specific type of folder), or to a list of
17432 In order to match a specific folder you Select the "Specific"
17433 button <EM>AND</EM> fill in
17434 the name (or list of names) of
17435 the folder in the "Folder List" field.
17436 If the current folder is any of the folders in the list, that is considered
17438 The name of each folder in the list may be either "INBOX", the technical specification
17439 of the folder (like what appears in your configuration file) or, if the
17440 folder is one of your incoming folders, it may be the nickname you've given
17442 Here are a couple samples of specific folder names:
17444 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17446 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17448 The easiest way to fill in the "Folder List" field is to use
17449 the T command that is available when the "Folder List" line is
17451 Note that you won't be able to edit the "Folder List" line unless the
17452 Current Folder Type is set to "Specific", and any value that
17453 "Folder List" has is ignored unless the type
17454 is set to "Specific".
17456 When reading a newsgroup, there may be a performance penalty
17457 incurred when collecting the information necessary to check a Pattern.
17458 For this reason, the default Current Folder Type is set to "Email".
17459 For example, if you have Index Line Coloring rules that have Score Intervals
17460 defined then the scores for all the visible messages will need to be calculated.
17461 If some of your Scoring rules have
17462 a Current Folder Type of
17463 "Any" or "News" this may cause the MESSAGE INDEX
17464 screen to draw more slowly when in a newsgroup.
17466 Look "<A HREF="h_rule_patterns">here</A>"
17467 for more information on Patterns.
17469 Look <A HREF="h_edit_nav_cmds">here</A>
17470 to see the available Editing and Navigation commands.
17472 <End of help on this topic>
17475 ======= h_config_other_fldr_type =======
17478 <TITLE>Current Folder Type Explained</TITLE>
17481 <H1>Current Folder Type Explained</H1>
17483 The Current Folder Type is part of the rule's Pattern.
17484 It refers to the type of the folder being viewed.
17485 In order for a rule to be considered a match, the current folder must
17486 be of the type you set here.
17487 The three types "Any", "News", and "Email" are
17488 all what you might think.
17490 If the Current Folder Type for a Pattern is set to "News", for
17492 that Pattern will only match if the current folder is a newsgroup.
17493 The value "Specific" may be used when you want to limit the match
17494 to a specific folder (not just a specific type of folder), or to a list of
17497 In order to match a specific folder you Select the "Specific"
17498 button <EM>AND</EM> fill in
17499 the name (or list of names) of
17500 the folder in the "Folder List" field.
17501 If the current folder is any of the folders in the list, that is considered
17503 The name of each folder in the list may be either "INBOX", the technical specification
17504 of the folder (like what appears in your configuration file) or, if the
17505 folder is one of your incoming folders, it may be the nickname you've given
17507 Here are a couple samples of specific folder names:
17509 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17511 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17513 The easiest way to fill in the "Folder List" field is to use
17514 the T command that is available when the "Folder List" line is
17516 Note that you won't be able to edit the "Folder List" line unless the
17517 Current Folder Type is set to "Specific", and any value that
17518 "Folder List" has is ignored unless the type
17519 is set to "Specific".
17521 Look "<A HREF="h_rule_patterns">here</A>"
17522 for more information on Patterns.
17524 Look <A HREF="h_edit_nav_cmds">here</A>
17525 to see the available Editing and Navigation commands.
17527 <End of help on this topic>
17530 ======= h_config_incol_fldr_type =======
17533 <TITLE>Current Folder Type Explained</TITLE>
17536 <H1>Current Folder Type Explained</H1>
17538 The Current Folder Type is part of the Line Coloring rule's Pattern.
17539 It refers to the type of the folder for which the MESSAGE INDEX is
17541 In order for a rule to be considered a match, the current folder must
17542 be of the type you set here.
17543 The three types "Any", "News", and "Email" are
17544 all what you might think.
17546 If the Current Folder Type for a Pattern is set to "News", for
17548 that Pattern will only match if the current folder is a newsgroup and
17549 the rest of the Pattern matches.
17550 The value "Specific" may be used when you want to limit the match
17551 to a specific folder (not just a specific type of folder), or to a list of
17554 In order to match a specific folder you Select the "Specific"
17555 button <EM>AND</EM> fill in
17556 the name (or list of names) of
17557 the folder in the "Folder List" field.
17558 If the current folder is any of the folders in the list, that is considered
17560 The name of each folder in the list may be either "INBOX", the technical specification
17561 of the folder (like what appears in your configuration file) or, if the
17562 folder is one of your incoming folders, it may be the nickname you've given
17564 Here are a couple samples of specific folder names:
17566 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17568 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17570 The easiest way to fill in the "Folder List" field is to use
17571 the T command that is available when the "Folder List" line is
17573 Note that you won't be able to edit the "Folder List" line unless the
17574 Current Folder Type is set to "Specific", and any value that
17575 "Folder List" has is ignored unless the type
17576 is set to "Specific".
17578 When reading a newsgroup, there may be a performance penalty
17579 incurred when collecting the information necessary to check a Pattern.
17580 For this reason, the default Current Folder Type is set to "Email".
17581 For example, a rule with a non-Normal Index Line Color
17582 and a Current Folder Type of
17583 "Any" or "News" may cause the MESSAGE INDEX
17584 screen to draw more slowly when in a newsgroup.
17586 Look "<A HREF="h_rule_patterns">here</A>"
17587 for more information on Patterns.
17589 Look <A HREF="h_edit_nav_cmds">here</A>
17590 to see the available Editing and Navigation commands.
17592 <End of help on this topic>
17595 ======= h_config_filt_fldr_type =======
17598 <TITLE>Current Folder Type Explained</TITLE>
17601 <H1>Current Folder Type Explained</H1>
17603 The Current Folder Type is part of the Filtering rule's Pattern.
17604 It refers to the type of the folder for which the filtering is being done.
17605 In order for a rule to be considered a match, the current folder must
17606 be of the type you set here.
17607 The three types "Any", "News", and "Email" are
17608 all what you might think.
17610 If the Current Folder Type for a Pattern is set to "News", for
17612 that Pattern will only match if the current folder is a newsgroup and
17613 the rest of the Pattern matches.
17614 The value "Specific" may be used when you want to limit the match
17615 to a specific folder (not just a specific type of folder), or to a list of
17618 In order to match a specific folder you Select the "Specific"
17619 button <EM>AND</EM> fill in
17620 the name (or list of names) of
17621 the folder in the "Folder List" field.
17622 If the current folder is any of the folders in the list, that is considered
17624 The name of each folder in the list may be either "INBOX", the technical specification
17625 of the folder (like what appears in your configuration file) or, if the
17626 folder is one of your incoming folders, it may be the nickname you've given
17628 Here are a couple samples of specific folder names:
17630 <CENTER><SAMP>{monet.art.example.com}mail/art-class</SAMP></CENTER>
17632 <CENTER><SAMP>{news.example.com/nntp}#news.comp.mail.pine</SAMP></CENTER>
17634 The easiest way to fill in the "Folder List" field is to use
17635 the T command that is available when the "Folder List" line is
17637 Note that you won't be able to edit the "Folder List" line unless the
17638 Current Folder Type is set to "Specific", and any value that
17639 "Folder List" has is ignored unless the type
17640 is set to "Specific".
17642 When reading a newsgroup, there may be a performance penalty
17643 incurred when collecting the information necessary to check a Pattern.
17644 For this reason, the default Current Folder Type is set to "Email".
17645 For example, a rule with a Current Folder Type of either
17646 "Any" or "News" may cause the filtering to happen
17647 more slowly when opening a newsgroup.
17649 Look "<A HREF="h_rule_patterns">here</A>"
17650 for more information on Patterns.
17652 Look <A HREF="h_edit_nav_cmds">here</A>
17653 to see the available Editing and Navigation commands.
17655 <End of help on this topic>
17658 ======= h_config_role_stat_imp =======
17661 <TITLE>Message Important Status Explained</TITLE>
17664 <H1>Message Important Status Explained</H1>
17666 This part of the Pattern may have one of three possible values.
17667 The default value is "Don't care", which matches any message.
17668 The other two values are "Yes", which means the message must be
17669 flagged "Important" in order to be a match; or "No", which
17670 means the message must <EM>not</EM> be flagged "Important" in order
17673 Look "<A HREF="h_rule_patterns">here</A>"
17674 for more information on Patterns.
17676 Look <A HREF="h_edit_nav_cmds">here</A>
17677 to see the available Editing and Navigation commands.
17679 <End of help on this topic>
17682 ======= h_config_role_stat_new =======
17685 <TITLE>Message New Status Explained</TITLE>
17688 <H1>Message New Status Explained</H1>
17690 This part of the Pattern may have one of three possible values.
17691 The default value is "Don't care", which matches any message.
17692 The other two values are "Yes", which means the message must be
17693 "New" in order to be a match; or "No", which
17694 means the message must <EM>not</EM> be "New" in order
17696 "New" is the same as <EM>Unseen</EM> and not "New" is the
17697 same as <EM>Seen</EM>.
17699 The nomenclature for New and Recent is a bit confusing:
17701 New means that the message is Unseen.
17702 It could have been in your mailbox for a long time but if you haven't looked
17703 at it, it is still considered New.
17704 That matches the default Alpine index display that shows an N for such a
17707 Recent means that the message was added to this folder since the last time
17708 you opened the folder.
17709 Alpine also shows an N by default for these types of messages.
17710 If you were to run two copies of Alpine that opened a folder one right after
17711 the other, a message would only show up as Recent in (at most) the first
17714 Look "<A HREF="h_rule_patterns">here</A>"
17715 for more information on Patterns.
17717 Look <A HREF="h_edit_nav_cmds">here</A>
17718 to see the available Editing and Navigation commands.
17720 <End of help on this topic>
17723 ======= h_config_role_stat_recent =======
17726 <TITLE>Message Recent Status Explained</TITLE>
17729 <H1>Message Recent Status Explained</H1>
17731 This part of the Pattern may have one of three possible values.
17732 The default value is "Don't care", which matches any message.
17733 The other two values are "Yes", which means the message must be
17734 "Recent" in order to be a match; or "No", which
17735 means the message must <EM>not</EM> be "Recent" in order
17737 "Recent" means that the message was added to the folder since
17738 the last time the folder was opened.
17739 If more than one mail client has the folder opened, the message will
17740 appear to be "Recent" to only one of the clients.
17742 The nomenclature for New and Recent is a bit confusing:
17744 New means that the message is Unseen.
17745 It could have been in your mailbox for a long time but if you haven't looked
17746 at it, it is still considered New.
17747 That matches the default Alpine index display that shows an N for such a
17750 Recent means that the message was added to this folder since the last time
17751 you opened the folder.
17752 Alpine also shows an N by default for these types of messages.
17753 If you were to run two copies of Alpine that opened a folder one right after
17754 the other, a message would only show up as Recent in (at most) the first
17757 Look "<A HREF="h_rule_patterns">here</A>"
17758 for more information on Patterns.
17760 Look <A HREF="h_edit_nav_cmds">here</A>
17761 to see the available Editing and Navigation commands.
17763 <End of help on this topic>
17766 ======= h_config_role_stat_del =======
17769 <TITLE>Message Deleted Status Explained</TITLE>
17772 <H1>Message Deleted Status Explained</H1>
17774 This part of the Pattern may have one of three possible values.
17775 The default value is "Don't care", which matches any message.
17776 The other two values are "Yes", which means the message must be
17777 marked "Deleted" in order to be a match; or "No", which
17778 means the message must <EM>not</EM> be marked "Deleted" in order
17781 If you are thinking of using this part of the Pattern as a way to prevent
17782 messages from being filtered more than once in a Filter Pattern,
17783 take a look at the Filter Option
17784 <A HREF="h_config_filt_opts_notdel">"Move-Only-if-Not-Deleted"</A>
17786 It should work better than using this field since it will hide the filtered
17787 messages even if they are already Deleted.
17788 That option is at the bottom of the Filter configuration screen.
17790 Look "<A HREF="h_rule_patterns">here</A>"
17791 for more information on Patterns.
17793 Look <A HREF="h_edit_nav_cmds">here</A>
17794 to see the available Editing and Navigation commands.
17796 <End of help on this topic>
17799 ======= h_config_role_stat_ans =======
17802 <TITLE>Message Answered Status Explained</TITLE>
17805 <H1>Message Answered Status Explained</H1>
17807 This part of the Pattern may have one of three possible values.
17808 The default value is "Don't care", which matches any message.
17809 The other two values are "Yes", which means the message must be
17810 marked "Answered" in order to be a match; or "No", which
17811 means the message must <EM>not</EM> be marked "Answered" in order
17814 Look "<A HREF="h_rule_patterns">here</A>"
17815 for more information on Patterns.
17817 Look <A HREF="h_edit_nav_cmds">here</A>
17818 to see the available Editing and Navigation commands.
17820 <End of help on this topic>
17823 ======= h_config_role_abookfrom =======
17826 <TITLE>Address in Address Book Explained</TITLE>
17829 <H1>Address in Address Book Explained</H1>
17831 This option gives you a way to match messages that contain an address
17832 that is in one of your address books.
17833 Only the simple entries in your address books are searched.
17834 Address book distribution lists are ignored!
17836 This part of the Pattern may have one of five possible values.
17837 The default value is "Don't care", which matches any message.
17838 The value "Yes, in any address book" means at least one of the addresses
17839 from the message must be in at least one of your
17840 address books in order to be a match.
17841 The value "No, not in any address book"
17842 means none of the addresses may
17843 be in any of your address books in order to be a match.
17845 The values "Yes, in specific address books" and
17846 "No, not in any of specific address books" are similar but instead
17847 of depending on all address books you are allowed to give a list of address
17849 Usually this would be a single address book but it may be a
17850 list of address books as well.
17851 For each of these "specific" address book options you Select which
17852 of the Specific options you want (Yes or No) <EM>AND</EM> fill in the
17853 name (or list of names) of the address book in the
17854 "Abook List" field.
17855 The names to be used are those that appear in the ADDRESS BOOK LIST screen.
17856 The easiest way to fill in the Abook List field it to use
17857 the "T" command that is available when the "Abook List"
17858 line is highlighted.
17859 Note that you won't be able to edit the "Abook List" line unless the
17860 option is set to one of the two "Specific", values.
17862 The addresses from the message that are checked for are determined by the
17863 setting you have for "Types of addresses to check for in address book".
17864 If you set this to "From" the From address from the message will
17865 be looked up in the address book.
17866 If you set it to "To" instead then the To addresses will be used.
17867 If any of the To addresses are in the address book then it is considered
17868 a match for "Yes" or not a match for "No".
17869 You could set it to both From and To, in which case all of the From and To
17870 addresses are used.
17871 The "Reply-To" and "Sender" cases are a little unusual.
17872 Due to deficiencies in our tools, Reply-To uses the Reply-To address if it
17873 exists or the From address if there is no Reply-To address.
17874 Same for the Sender address.
17876 Look "<A HREF="h_rule_patterns">here</A>"
17877 for more information on Patterns.
17879 Look <A HREF="h_edit_nav_cmds">here</A>
17880 to see the available Editing and Navigation commands.
17882 <End of help on this topic>
17885 ======= h_config_inabook_from =======
17888 <TITLE>From</TITLE>
17893 Setting the From line will cause the address from the From header line
17894 of the message to be checked for in the address book.
17896 <End of help on this topic>
17899 ======= h_config_inabook_replyto =======
17902 <TITLE>Reply-To</TITLE>
17907 Setting the Reply-To line will cause the address from the Reply-To header line
17908 of the message to be checked for in the address book.
17909 However, if there is no Reply-To header line in the message the From header
17910 line will be used instead.
17911 We understand this is dumb but we don't have an easy way around it.
17913 <End of help on this topic>
17916 ======= h_config_inabook_sender =======
17919 <TITLE>Sender</TITLE>
17924 Setting the Sender line will cause the address from the Sender header line
17925 of the message to be checked for in the address book.
17926 However, if there is no Sender header line in the message the From header
17927 line will be used instead.
17928 We understand this is dumb but we don't have an easy way around it.
17930 <End of help on this topic>
17933 ======= h_config_inabook_to =======
17941 Setting the To line will cause the address from the To header line
17942 of the message to be checked for in the address book.
17944 <End of help on this topic>
17947 ======= h_config_inabook_cc =======
17955 Setting the CC line will cause the address from the CC header line
17956 of the message to be checked for in the address book.
17958 <End of help on this topic>
17961 ======= h_config_role_stat_8bitsubj =======
17964 <TITLE>Raw 8-bit in Subject Explained</TITLE>
17967 <H1>Raw 8-bit in Subject Explained</H1>
17969 It seems that lots of unwanted email contains unencoded 8-bit characters
17971 Normally, characters with the 8th bit set are not allowed in the Subject
17972 header unless they are MIME-encoded.
17973 This option gives you a way to match messages that have Subjects that
17974 contain unencoded 8-bit characters.
17976 This part of the Pattern may have one of three possible values.
17977 The default value is "Don't care", which matches any message.
17978 The other two values are "Yes", which means the Subject of
17979 the message must contain unencoded 8-bit characters (characters with the
17980 most significant bit set)
17981 in order to be a match; or "No", which
17982 means the Subject must <EM>not</EM>
17983 contain unencoded 8-bit characters in order to be a match.
17985 Look "<A HREF="h_rule_patterns">here</A>"
17986 for more information on Patterns.
17988 Look <A HREF="h_edit_nav_cmds">here</A>
17989 to see the available Editing and Navigation commands.
17991 <End of help on this topic>
17994 ======= h_config_role_bom =======
17997 <TITLE>Beginning of Month</TITLE>
18000 <H1>Beginning of Month</H1>
18002 This option gives you a limited ability to take different actions depending on whether
18003 this is the first time Alpine has been run this month or not.
18004 Though it would be nice to have such an option available, this is not the
18005 same as whether or not this is the first time a paricular folder has been
18007 If you want some action (probably Filtering) to take place in a folder each
18008 month, then you will need to be sure that the folder is opened during the
18009 first Alpine session of the month in order for this option to be helpful.
18011 This part of the Pattern may have one of three possible values.
18012 The default value is "Don't care", which matches any message.
18013 The other two values are "Yes", which means this is the first
18014 time Alpine has been run this month;
18015 or "No", which
18016 means this is not the first time Alpine has been run this month.
18018 Look "<A HREF="h_rule_patterns">here</A>"
18019 for more information on Patterns.
18021 Here are some technical details.
18022 The way that Alpine decides if it is the beginning of the month or not is
18023 to compare today's date with the date stored in the
18024 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
18025 variable in the config file.
18026 If the month of today's date is later than the month stored in the variable,
18027 then this is considered to be the first time you have run Alpine this month, and
18028 that turns the Beginning of the Month option on.
18030 Look <A HREF="h_edit_nav_cmds">here</A>
18031 to see the available Editing and Navigation commands.
18033 <End of help on this topic>
18036 ======= h_config_role_boy =======
18039 <TITLE>Beginning of Year</TITLE>
18042 <H1>Beginning of Year</H1>
18044 This option gives you a limited ability to take different actions depending on whether
18045 this is the first time Alpine has been run this year or not.
18046 Though it would be nice to have such an option available, this is not the
18047 same as whether or not this is the first time a paricular folder has been
18049 If you want some action (probably Filtering) to take place in a folder each
18050 year, then you will need to be sure that the folder is opened during the
18051 first Alpine session of the year in order for this option to be helpful.
18053 This part of the Pattern may have one of three possible values.
18054 The default value is "Don't care", which matches any message.
18055 The other two values are "Yes", which means this is the first
18056 time Alpine has been run this year;
18057 or "No", which
18058 means this is not the first time Alpine has been run this year.
18060 Look "<A HREF="h_rule_patterns">here</A>"
18061 for more information on Patterns.
18063 Here are some technical details.
18064 The way that Alpine decides if it is the beginning of the year or not is
18065 to compare today's date with the date stored in the
18066 <A HREF="h_config_prune_date"><!--#echo var="VAR_last-time-prune-questioned"--></A>
18067 variable in the config file.
18068 If the year of today's date is later than the year stored in the variable,
18069 then this is considered to be the first time you have run Alpine this year, and
18070 that turns the Beginning of the Year option on.
18072 Look <A HREF="h_edit_nav_cmds">here</A>
18073 to see the available Editing and Navigation commands.
18075 <End of help on this topic>
18078 ======= h_config_role_inick =======
18081 <TITLE>Initialize Values From Role Explained</TITLE>
18084 <H1>Initialize Values From Role Explained</H1>
18086 This is a power user feature.
18087 You will usually want to leave this field empty.
18088 The value of this field is the nickname of another one of your roles.
18089 The Action values from that other role
18090 are used as the initial values of the Action items for this role.
18091 If you put something in any of the action fields for this role, that will
18092 override whatever was in the corresponding field of the initializer role.
18094 You might use this field if the "Action" part of one of your roles
18095 is something you want to use in more than one role.
18096 Instead of filling in those action values again for each role, you
18097 may give the nickname of the role where the values are filled in.
18098 It's just a shortcut way to define Role Actions.
18100 Here's an example to help explain how this works.
18101 Suppose you have a role with nickname "role1" and role1 has
18102 (among other things)
18104 <CENTER><SAMP>Set Reply-To = The Pres <president@example.com></SAMP></CENTER>
18107 If in "role2" you set "Initialize settings using role" to
18108 "role1", then role2 will inherit the Set Reply-To value
18109 from role1 by default (and any of the other inheritable action values
18113 <CENTER><SAMP>Set Reply-To = <No Value Set></SAMP></CENTER>
18115 defined, the Reply-To used with role2 would be "The Pres <president@example.com>"
18116 However, if role2 had
18118 <CENTER><SAMP>Set Reply-To = VP <vicepresident@example.com></SAMP></CENTER>
18120 defined, then the Reply-To used with role2 would be "VP <vicepresident@example.com>" instead.
18123 you may choose a nickname from your list of roles by using the
18124 "T" command.
18125 If the role you are using to initialize also has a role it initializes from,
18126 then that initialization happens first.
18127 That is, inheritance works as expected with the grandparent and
18128 great-grandparent (and so on) roles having the expected effect.
18130 Look <A HREF="h_edit_nav_cmds">here</A>
18131 to see the available Editing and Navigation commands.
18133 <End of help on this topic>
18136 ======= h_config_role_setfrom =======
18139 <TITLE>Set From Explained</TITLE>
18142 <H1>Set From Explained</H1>
18144 This describes part of the action to be taken if the Pattern for this
18146 This field consists of a single address that will be used as the From
18147 address on the message you are sending.
18148 This should be a fully-qualified address like
18150 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
18154 <CENTER><SAMP>user@domain</SAMP></CENTER>
18157 you may choose an address from your address book with the
18158 "T" command.
18160 If this is left blank, then your normal From address will be used.
18162 You may also find it useful to add the changed From address to the
18163 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
18164 configuration option.
18166 Look <A HREF="h_edit_nav_cmds">here</A>
18167 to see the available Editing and Navigation commands.
18169 <End of help on this topic>
18172 ======= h_config_role_setreplyto =======
18175 <TITLE>Set Reply-To Explained</TITLE>
18178 <H1>Set Reply-To Explained</H1>
18180 This describes part of the action to be taken if the Pattern for this
18182 This field consists of a single address that will be used as the Reply-To
18183 address on the message you are sending.
18184 This may be a fully-qualified address like
18186 <CENTER><SAMP>Full Name <user@domain></SAMP></CENTER>
18190 <CENTER><SAMP>user@domain</SAMP></CENTER>
18193 you may choose an address from your address book with the
18194 "T" command.
18196 If this is left blank, then there won't be a Reply-To address unless
18197 you have configured one specially with the
18198 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>"
18199 configuration option.
18201 Look <A HREF="h_edit_nav_cmds">here</A>
18202 to see the available Editing and Navigation commands.
18204 <End of help on this topic>
18207 ======= h_config_role_setfcc =======
18210 <TITLE>Set Fcc Explained</TITLE>
18213 <H1>Set Fcc Explained</H1>
18215 This describes part of the action to be taken if the Pattern for this
18217 This field consists of a single folder name that will be used in
18218 the Fcc field of the message you are sending.
18219 You may put anything here that you would normally type into the Fcc
18220 field from the composer.
18222 In addition, an fcc of "" (two double quotation marks) means
18225 A blank field here means that Alpine will use its normal rules for deciding
18226 the default value of the Fcc field.
18227 For many roles, perhaps most, it may make more sense for you to use the
18228 other Alpine facilities for setting the Fcc.
18229 In particular, if you want the Fcc to depend on who you are sending the
18230 message to then the <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
18231 is probably more useful.
18232 In that case, you would want to leave the Fcc field here blank.
18233 However, if you have a role that depends on who the message you are replying
18234 to was From, or what address that message was sent to;
18235 then it might make sense to set the Fcc for that role here.
18238 you may choose a folder from your folder collections by using the
18239 "T" command.
18241 Look <A HREF="h_edit_nav_cmds">here</A>
18242 to see the available Editing and Navigation commands.
18244 <End of help on this topic>
18247 ======= h_config_role_usesmtp =======
18250 <TITLE>Use SMTP Server Explained</TITLE>
18253 <H1>Use SMTP Server Explained</H1>
18255 This describes part of the action to be taken if the Pattern for this
18257 If this field has a value, then it will be used as the SMTP server
18258 to send mail when this role is being used (unless the SMTP server variable
18259 is set in the system-wide fixed configuration file).
18260 It has the same semantics as the
18261 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
18262 variable in the Setup/Config screen.
18264 If you are using this to post from home when you are at home and from
18265 work when you are at work you need to be careful about postponing messages.
18266 When you postpone a composition that was using a role with this variable
18267 set, the SMTP server list will be saved
18268 with the postponed composition.
18269 It cannot be changed later.
18270 Because of this, you may want to make this a list of SMTP servers
18271 with the preferred server at the front of the list and alternate servers
18273 In your "Home" role you would put the home SMTP server first and
18274 the work SMTP server last.
18275 In your "Work" role you would put the work SMTP server first and
18276 the home SMTP server last.
18277 Then if you start a composition as "Work", postpone
18278 it, and then later resume it from home the work SMTP server will fail but
18279 the home SMTP server later in the list will succeed.
18281 You may be able to simplify things by making the regular
18282 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
18283 variable in the Setup/Config screen a list instead of using roles
18284 to set the SMTP server.
18287 Look <A HREF="h_edit_nav_cmds">here</A>
18288 to see the available Editing and Navigation commands.
18290 <End of help on this topic>
18293 ======= h_config_role_usenntp =======
18296 <TITLE>Use NNTP Server Explained</TITLE>
18299 <H1>Use NNTP Server Explained</H1>
18301 This describes part of the action to be taken if the Pattern for this
18303 If this field has a value, then it will be used as the NNTP server
18304 to post to newsgroups when this role is being used (unless the NNTP server
18306 is set in the system-wide fixed configuration file).
18307 It has the same semantics as the
18308 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18309 variable in the Setup/Config screen.
18311 This role setting can facilitate posting to the right nntp server for someone
18312 who reads news from various news sources. The feature
18313 <A HREF="h_config_predict_nntp_server">"<!--#echo var="FEAT_predict-nntp-server"-->"</A>
18314 allows for setting the correct <!--#echo var="VAR_nntp-server"--> without having to individually
18315 set a role for that <!--#echo var="VAR_nntp-server"-->, but for greater flexibility, setting
18316 nntp servers for roles may be more desirable for some people.
18318 If you are using this to post from home when you are at home and from
18319 work when you are at work you need to be careful about postponing messages.
18320 When you postpone a composition that was using a role with this variable
18321 set, the NNTP server list will be saved
18322 with the postponed composition.
18323 It cannot be changed later.
18324 Because of this, you may want to make this a list of NNTP servers
18325 with the preferred server at the front of the list and alternate servers
18327 In your "Home" role you would put the home NNTP server first and
18328 the work NNTP server last.
18329 In your "Work" role you would put the work NNTP server first and
18330 the home NNTP server last.
18331 Then if you start a composition as "Work", postpone
18332 it, and then later resume it from home the work NNTP server will fail but
18333 the home NNTP server later in the list will succeed.
18335 You may be able to simplify things by making the regular
18336 <A HREF="h_config_nntp_server">"<!--#echo var="VAR_nntp-server"-->"</A>
18337 variable in the Setup/Config screen a list instead of using roles
18338 to set the NNTP server.
18341 Look <A HREF="h_edit_nav_cmds">here</A>
18342 to see the available Editing and Navigation commands.
18344 <End of help on this topic>
18347 ======= h_config_role_setotherhdr =======
18350 <TITLE>Set Other Headers Explained</TITLE>
18353 <H1>Set Other Headers Explained</H1>
18355 This describes part of the action to be taken if the Pattern for this
18357 This field gives you a way to set values for headers besides
18358 "From" and "Reply-To".
18359 If you want to set either of those, use the specific
18360 "Set From" and "Set Reply-To" settings above.
18362 This field is similar to the
18363 "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" option.
18364 Each header you specify here must include the header tag
18365 ("To:", "Approved:", etc.)
18366 and may optionally include a value for that header.
18367 In order to see these headers when you compose using this role you
18368 must use the rich header
18369 <!--chtml if pinemode="function_key"-->(F5)
18370 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
18371 Here's an example that shows how you might set the To address.
18373 <CENTER><SAMP>Set Other Hdrs = To: Full Name <user@domain></SAMP></CENTER>
18375 Headers set in this way are different from headers set with the
18376 <!--#echo var="VAR_customized-hdrs"--> option in that the value you give for a header here
18377 will replace any value that already exists.
18378 For example, if you are Replying to a message there will already be at
18379 least one address in the To header (the address you are Replying to).
18380 However, if you Reply using a role that sets the To header, that role's
18381 To header value will be used instead.
18383 Limitation: Because commas are used to separate the list of
18384 Other Headers, it is not possible to have the value of a
18385 header contain a comma;
18386 nor is there currently an "escape" mechanism provided
18389 Look <A HREF="h_edit_nav_cmds">here</A>
18390 to see the available Editing and Navigation commands.
18392 <End of help on this topic>
18395 ======= h_config_role_setlitsig =======
18398 <TITLE>Set Literal Signature Explained</TITLE>
18401 <H1>Set Literal Signature Explained</H1>
18403 This describes part of the action to be taken if the Pattern for this
18405 This field contains the actual text for your signature, as opposed to
18406 the name of a file containing your signature.
18407 If this is defined it takes precedence over any value set in the
18408 "Set Signature" field.
18410 This is simply a different way to store the signature.
18411 The signature is stored inside your Alpine configuration file instead of in
18413 Tokens work the same way they do with
18414 <A HREF="h_config_role_setsig">Set Signature</A>, so refer to the
18415 help text there for more information.
18418 The two character sequence \n (backslash followed by
18419 the character n) will be used to signify a line-break in your signature.
18420 You don't have to enter the \n, but it will be visible in the
18421 CHANGE THIS ROLE RULE window after you are done editing the signature.
18423 Look <A HREF="h_edit_nav_cmds">here</A>
18424 to see the available Editing and Navigation commands.
18426 <End of help on this topic>
18429 ======= h_config_role_setsig =======
18432 <TITLE>Set Signature Explained</TITLE>
18435 <H1>Set Signature Explained</H1>
18437 This describes part of the action to be taken if the Pattern for this
18440 If either the default <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A>
18441 option from Setup/Config
18442 or the "Set LiteralSig" option for this role are defined,
18443 then this option will be ignored.
18444 You can tell that that is the case because the value of this
18445 option will show up as
18447 <CENTER><SAMP><Ignored: using LiteralSig instead></SAMP></CENTER>
18449 You may either use all Literal Signatures (signatures stored in your
18450 configuration file) throughout Alpine, or all signature files.
18451 You can't mix the two.
18453 This field consists of a filename that will be used as the signature
18454 file when using this role.
18456 If the filename is followed by a vertical bar (|) then instead
18457 of reading the contents of the file the file is assumed to be a
18458 program that will produce the text to be used on its standard output.
18459 The program can't have any arguments and doesn't receive any input from Alpine,
18460 but the rest of the processing works as if the contents came from a file.
18462 Instead of storing the data in a local file, the
18463 signature data may be stored remotely in an IMAP folder.
18464 In order to do this,
18465 you must use a remote name for the signature.
18466 A remote signature name might look like:
18468 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/sig3</SAMP></CENTER>
18471 The syntax used here is the same as the syntax used for a remote
18472 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18473 Note that you may not access an existing signature file remotely,
18474 you have to create a new <EM>folder</EM> that contains the signature data.
18475 If the name you use here for the signature data is a remote name, then when
18476 you edit the file using the "F" command the data will
18477 be saved remotely in the folder.
18478 You aren't required to do anything special to create the folder, it
18479 gets created if you use a remote name.
18482 If you type "F" you may edit the contents of the file (as opposed to
18483 the name of the file) you have specified.
18484 If you type "T" you may use a browser to choose an existing filename.
18486 Besides containing regular text, a signature file may also
18487 contain (or a signature program may produce) tokens that are replaced with text
18488 that depends on the message you are replying to or forwarding.
18489 The tokens all look like _word_ (a word surrounded by underscores).
18490 For example, if the token
18492 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18494 is included in the text of the signature file, then when you reply to
18495 or forward a message, the token will be replaced with the actual date
18496 the message you are replying to or forwarding was sent.
18498 If you use a role that has a signature file for a plain composition
18499 (that is, not a reply or forward) then there is no original message, so
18500 any tokens that depend on the message will be replaced with nothing.
18501 So if you want a signature file to be useful for new compositions it
18502 shouldn't include any of the tokens that depend on the message being
18503 replied to or forwarded.
18505 The list of available tokens is
18506 <A HREF="h_index_tokens">here</A>.
18508 Actually, for the adventurous, there is a way to conditionally include text based
18509 on whether or not a token would result in specific replacement text.
18510 For example, you could include some text based on whether or not
18511 the _NEWS_ token would result in any newsgroups if it was used.
18512 It's explained in detail
18513 <A HREF="h_reply_token_conditionals">here</A>.
18515 In the very unlikely event that you want to include a literal token in
18516 a signature file, you must precede it with a backslash character.
18517 For example, to include the literal text _DATE_ you must actually use
18519 It is not possible to have a literal backslash followed by an expanded token.
18521 A blank field here means that Alpine will use its normal rules for deciding
18522 which file (if any) to use for the signature file.
18524 An alternate method for storing the signature is available in
18525 <A HREF="h_config_role_setlitsig">Set Literal Signature</A>.
18527 Look <A HREF="h_edit_nav_cmds">here</A>
18528 to see the available Editing and Navigation commands.
18530 <End of help on this topic>
18533 ======= h_config_role_settempl =======
18536 <TITLE>Set Template Explained</TITLE>
18539 <H1>Set Template Explained</H1>
18541 This describes part of the action to be taken if the Pattern for this
18543 This field consists of a filename that will be used as the template
18544 file when using this role.
18545 The template file is a file that is included at the top of the message you
18548 If the filename is followed by a vertical bar (|) then instead
18549 of reading the contents of the file the file is assumed to be a
18550 program that will produce the text to be used on its standard output.
18551 The program can't have any arguments and doesn't receive any input from Alpine,
18552 but the rest of the processing works as if the contents came from a file.
18554 Instead of storing the data in a local file, the
18555 template may be stored remotely in an IMAP folder.
18556 In order to do this,
18557 you must use a remote name for the template.
18558 A remote template name might look like:
18560 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/templ3</SAMP></CENTER>
18563 The syntax used here is the same as the syntax used for a remote
18564 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>.
18565 Note that you may not access an existing template file remotely,
18566 you have to create a new <EM>folder</EM> that contains the template data.
18567 If the name you use here for the template is a remote name, then when
18568 you edit the file using the "F" command the data will
18569 be saved remotely in the folder.
18570 You aren't required to do anything special to create the folder, it
18571 gets created if you use a remote name.
18573 If you type "F" you may edit the contents of the file (as opposed to
18574 the name of the file) you have specified.
18575 If you type "T" you may use a browser to choose an existing filename.
18577 Besides containing regular text, the template file may also
18578 contain (or a template file program may produce) tokens that are replaced with text
18579 that depends on the message you are replying to or forwarding.
18580 The tokens all look like _word_ (a word surrounded by underscores).
18581 For example, if the token
18583 <CENTER><SAMP>_DATE_</SAMP></CENTER>
18585 is included in the text of the template file, then when you reply to
18586 or forward a message, the token will be replaced with the actual date
18587 the message you are replying to or forwarding was sent.
18589 If you use a role that has a template file for a plain composition
18590 (that is, not a reply or forward) then there is no original message, so
18591 any tokens that depend on the message will be replaced with nothing.
18592 So if you want a template file to be useful for new compositions it
18593 shouldn't include any of the tokens that depend on the message being
18594 replied to or forwarded.
18596 The list of available tokens is
18597 <A HREF="h_index_tokens">here</A>.
18599 Actually, for the adventurous, there is a way to conditionally include text based
18600 on whether or not a token would result in specific replacement text.
18601 For example, you could include some text based on whether or not
18602 the _NEWS_ token would result in any newsgroups if it was used.
18603 It's explained in detail
18604 <A HREF="h_reply_token_conditionals">here</A>.
18606 In the very unlikely event that you want to include a literal token in
18607 a template file, you must precede it with a backslash character.
18608 For example, to include the literal text _DATE_ you must actually use
18610 It is not possible to have a literal backslash followed by an expanded token.
18612 A blank template field means that Alpine will not use a template file when
18613 this role is being used.
18615 Look <A HREF="h_edit_nav_cmds">here</A>
18616 to see the available Editing and Navigation commands.
18618 <End of help on this topic>
18621 ======= h_config_filt_stat_imp =======
18624 <TITLE>Set Important Status Explained</TITLE>
18627 <H1>Set Important Status Explained</H1>
18629 This describes part of the action to be taken if the Pattern for this
18631 If set to "Don't change it" then this does nothing.
18632 If set to "Set this state" then the Important flag is set
18633 for the matching message.
18634 If set to "Clear this state" then the Important flag is cleared
18635 for the matching message.
18636 The important flag usually causes an asterisk to show up in the MESSAGE
18638 It may also be useful when selecting a set of messages
18639 with the Select command.
18641 Look <A HREF="h_edit_nav_cmds">here</A>
18642 to see the available Editing and Navigation commands.
18644 <End of help on this topic>
18647 ======= h_config_filt_stat_new =======
18650 <TITLE>Set New Status Explained</TITLE>
18653 <H1>Set New Status Explained</H1>
18655 This describes part of the action to be taken if the Pattern for this
18657 If set to "Don't change it" then this does nothing.
18658 If set to "Set this state" then the
18659 matching message is marked New.
18660 If set to "Clear this state" then the
18661 matching message is marked Seen.
18663 Look <A HREF="h_edit_nav_cmds">here</A>
18664 to see the available Editing and Navigation commands.
18666 <End of help on this topic>
18669 ======= h_config_filt_stat_ans =======
18672 <TITLE>Set Answered Status Explained</TITLE>
18675 <H1>Set Answered Status Explained</H1>
18677 This describes part of the action to be taken if the Pattern for this
18679 If set to "Don't change it" then this does nothing.
18680 If set to "Set this state" then the Answered flag is set
18681 for the matching message.
18682 If set to "Clear this state" then the Answered flag is cleared
18683 for the matching message.
18685 Look <A HREF="h_edit_nav_cmds">here</A>
18686 to see the available Editing and Navigation commands.
18688 <End of help on this topic>
18691 ======= h_config_filt_stat_del =======
18694 <TITLE>Set Deleted Status Explained</TITLE>
18697 <H1>Set Deleted Status Explained</H1>
18699 This describes part of the action to be taken if the Pattern for this
18701 If set to "Don't change it" then this does nothing.
18702 If set to "Set this state" then the
18703 matching message is marked Deleted.
18704 If set to "Clear this state" then the
18705 matching message is marked UnDeleted.
18707 You should not use this option unless you are prepared to have matching
18708 messages expunged from the folder permanently.
18709 For example, if you type the Expunge command, this filter is applied
18710 before the expunge, so matching messages will be marked Deleted and then
18711 will be permanently expunged from the folder.
18712 However, since the index isn't redrawn in between the time that the message
18713 is marked Deleted and the time that you are asked to expunge, the only
18714 indication that you are expunging the message comes in the number of messages
18716 The same thing may happen when you close a folder.
18717 It is also possible that an expunge not initiated by you will
18718 delete matching messages.
18720 Look <A HREF="h_edit_nav_cmds">here</A>
18721 to see the available Editing and Navigation commands.
18723 <End of help on this topic>
18726 ======= h_config_role_scoreval =======
18729 <TITLE>Score Value Explained</TITLE>
18732 <H1>Score Value Explained</H1>
18734 A message's score is the sum of the Score Values from all of the Scoring rules
18735 with Patterns that match the message.
18736 The value you give here is the Score Value associated with this rule.
18737 A Score Value is an integer between -100 and 100, with the default
18740 Alternatively, if the
18741 <A HREF="h_config_role_scorehdrtok">"Score From Header"</A>
18743 (on the line right below the "Score Value" field)
18744 then the "Score Value" is ignored and
18745 the "Score From Header" field is used instead.
18747 Look <A HREF="h_edit_nav_cmds">here</A>
18748 to see the available Editing and Navigation commands.
18750 <End of help on this topic>
18753 ======= h_config_role_scorehdrtok =======
18756 <TITLE>Score Value From Header Explained</TITLE>
18759 <H1>Score Value From Header Explained</H1>
18761 This option provides a way to use a number that appears in the headers of your
18762 messages as the message's score, or as a component of that score.
18763 If this field is defined then it is used instead of the "Score Value".
18764 The idea behind this option is that there may be a score embedded in the
18765 headers of messages that has already been calculated outside of Alpine.
18766 For example, messages delivered to you may contain an "X-Spam" header and
18767 somewhere in that header there is a score.
18769 The value for this option is the name of the header followed by parentheses
18770 with two arguments inside:
18772 <CENTER><SAMP>HeaderName(field_number,field_separators)</SAMP></CENTER>
18774 No space is allowed between the comma and the start of the field_separators.
18775 It would be interpreted as the first separator if it was there.
18776 Field 0 is the whole line, Field 1 is the data up to the first separator, Field 2
18777 starts after that and goes to the second separator, and so on.
18778 It's easier to explain with examples.
18780 <CENTER><SAMP>X-Spam(2," ")</SAMP></CENTER>
18782 In the above example the header that is used is the "X-Spam" header.
18783 The value of that header (the part after the colon and the space) is split
18784 into fields separated by spaces.
18786 <CENTER><SAMP>Field1 <space> Field2 <space> Field3 ...</SAMP></CENTER>
18788 The second field is selected and converted to an integer. It only makes sense
18789 if Field2 really is an integer.
18791 Here's an example of a SpamAssassin header.
18792 The exact look of the header will vary, but if your incoming mail
18793 contains headers that look like the following
18795 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
18797 you might want to use the hits value as a score.
18798 Since the score is an integer value you can't make use of the decimal part of
18800 you might split off the hits=10 part as a score by using the characters "="
18801 and "." as your separators.
18803 <CENTER><SAMP>X-Spam-Status(2,"=.")</SAMP></CENTER>
18805 The first field starts with the Y in Yes and goes until the "=" after
18807 The second field is "10" so the score value would be 10.
18809 Another example we've seen has headers that look like
18811 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
18813 Because there are two equals before the 7% the value
18815 <CENTER><SAMP>X-Spam(3,"=%")</SAMP></CENTER>
18817 should capture the probability as the score.
18819 The Score From Header scoring value actually works just like the
18820 regular Score Value in that the rest of the pattern has to match before
18821 it is used and the scores from all the different scoring rules that
18822 match for a particular message are added together.
18823 When using the Score From Header method it may (or may not) make sense to
18824 use only a single scoring rule with a pattern that matches every message.
18826 Look <A HREF="h_edit_nav_cmds">here</A>
18827 to see the available Editing and Navigation commands.
18829 <End of help on this topic>
18832 ======= h_config_role_replyuse =======
18835 <TITLE>Reply Use Explained</TITLE>
18838 <H1>Reply Use Explained</H1>
18840 This option determines how this particular role will be used when Replying
18842 There are three possible values for this option.
18843 The value "Never"
18844 means that this role will not be a candidate for use when Replying.
18845 The role's Pattern will not be checked for a match, however the role will
18846 be available to be manually switched to if there is a confirmation prompt.
18849 The options "With confirmation" and "Without confirmation"
18850 mean that you do want to consider this role when Replying.
18851 For either of these settings, the role's Pattern will be compared with
18852 the message being replied to.
18853 If there is a match then this role will either be used without confirmation
18854 or will be the default when confirmation is asked for, depending on
18855 which of the two options is selected.
18856 If confirmation is requested, you will also have a chance to
18857 manually change the role to any one of your other roles.
18860 You won't be prompted for confirmation if none of your role Patterns
18861 match the message being replied to.
18862 This is independent of the value of the current option.
18863 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18864 feature may be used to change this behavior.
18866 <End of help on this topic>
18869 ======= h_config_role_forwarduse =======
18872 <TITLE>Forward Use Explained</TITLE>
18875 <H1>Forward Use Explained</H1>
18877 This option determines how this particular role will be used when Forwarding
18879 There are three possible values for this option.
18880 The value "Never"
18881 means that this role will not be a candidate for use when Forwarding.
18882 The role's Pattern will not be checked for a match, however the role will
18883 be available to be manually switched to if there is a confirmation prompt.
18886 The options "With confirmation" and "Without confirmation"
18887 mean that you do want to consider this role when Forwarding.
18888 For either of these settings, the role's Pattern will be compared with
18889 the message being forwarded.
18890 If there is a match then this role will either be used without confirmation
18891 or will be the default when confirmation is asked for, depending on
18892 which of the two options is selected.
18893 If confirmation is requested, you will also have a chance to
18894 manually change the role to any one of your other roles.
18897 You won't be prompted for confirmation if none of your role Patterns
18898 match the message being forwarded.
18899 This is independent of the value of the current option.
18900 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18901 feature may be used to change this behavior.
18903 <End of help on this topic>
18906 ======= h_config_role_composeuse =======
18909 <TITLE>Compose Use Explained</TITLE>
18912 <H1>Compose Use Explained</H1>
18914 This option determines how this particular role will be used when Composing
18915 a new message using the "Compose" command.
18916 This does not affect what happens when using the "Role" command
18917 to compose a new message.
18918 The "Role" command allows you to select a role from all of the
18919 roles you have defined, regardless of what Uses you've assigned to those
18923 There are three possible values for this option.
18924 The value "Never"
18925 means that this role will not be a candidate for use when Composing.
18926 The role's Current Folder Type will not be checked for a match, however the role
18927 will be available to be manually switched to if there is a confirmation prompt.
18930 The options "With confirmation" and "Without confirmation"
18931 mean that you do want to consider this role when Composing.
18932 For either of these settings,
18933 the role's Current Folder Type will be checked (since there is no message
18934 to compare with, the rest of the Pattern is considered a match).
18935 If there is a match then this role will either be used without confirmation
18936 or will be the default when confirmation is asked for, depending on
18937 which of the two options is selected.
18938 If confirmation is requested, you will also have a chance to
18939 manually change the role to any one of your other roles.
18942 When using the Compose command the role checking is a little different
18943 because there is no message being replied to or forwarded.
18944 Because of this the Current Folder Type is checked but the header pattern
18945 fields, the AllText pattern, the BodyText pattern, and the Score Interval are all ignored.
18946 A role is considered to be a match if it is a candidate for Compose Use and
18947 its Current Folder Type matches the currently open folder.
18948 This could be useful if you want to set a role based on the folder you
18949 are reading, or the type of folder you are reading.
18952 You won't be prompted for confirmation if none of your role Patterns
18954 This is independent of the value of the current option.
18955 The <A HREF="h_config_confirm_role"><!--#echo var="FEAT_confirm-role-even-for-default"--></A>
18956 feature may be used to change this behavior.
18958 <End of help on this topic>
18961 ======= h_config_filter_folder =======
18964 <TITLE>Filter Folder Explained</TITLE>
18967 <H1>Filter Folder Explained</H1>
18969 When the Filter Action is set to "Move",
18970 the folder or folders specified here will be used to store messages matching
18971 the provided pattern.
18974 If you set the Filter Action to "Move" you must give a folder name
18979 you may choose a folder from your folder collections by using the
18980 "T" command.
18982 Besides regular text, the folder name may also contain
18983 tokens that are replaced with text representing the current date
18984 when you run Alpine.
18985 For example, if the folder name you use is
18987 <CENTER><SAMP>abc-_CURYEAR_-_CURMONTHABBREV_</SAMP></CENTER>
18989 that is replaced with something like
18991 <CENTER><SAMP>abc-2004-oct</SAMP></CENTER>
18995 <CENTER><SAMP>abc-_CURYEAR2DIGIT_-_CURMONTH2DIGIT_</SAMP></CENTER>
18999 <CENTER><SAMP>abc-04-10</SAMP></CENTER>
19001 The token names must be surrounded by underscores in order to be recognized
19003 The tokens that may be used are those that are derived from the current date.
19004 They're listed near the bottom of the list of tokens give
19005 <A HREF="h_index_tokens">here</A>.
19007 Look "<A HREF="h_rule_patterns">here</A>"
19008 for more information on Patterns.
19010 Look <A HREF="h_edit_nav_cmds">here</A>
19011 to see the available Editing and Navigation commands.
19013 <End of help on this topic>
19016 ======= h_config_filter_kw_set =======
19019 <TITLE>Set These Keywords Explained</TITLE>
19022 <H1>Set These Keywords Explained</H1>
19024 This describes part of the action to be taken if the Pattern for this
19026 Read a little about keywords in the help text for the
19027 <A HREF="h_common_flag">Flag</A> command.
19028 This option is a list of keywords that will be Set when there is a match.
19029 If you wish, you may choose keywords from the list of keywords you have
19030 defined with the "T" command.
19031 You may add new keywords by defining them in the
19032 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
19033 If you have given a keyword a nickname when configuring it,
19034 that nickname may be used instead of the actual keyword.
19037 Look <A HREF="h_edit_nav_cmds">here</A>
19038 to see the available Editing and Navigation commands.
19040 <End of help on this topic>
19043 ======= h_config_filter_kw_clr =======
19046 <TITLE>Clear These Keywords Explained</TITLE>
19049 <H1>Clear These Keywords Explained</H1>
19051 This describes part of the action to be taken if the Pattern for this
19053 Read a little about keywords in the help text for the
19054 <A HREF="h_common_flag">Flag</A> command.
19055 This option is a list of keywords that will be Cleared when there is a match.
19056 If you wish, you may choose keywords from the list of keywords you have
19057 defined with the "T" command.
19058 You may add new keywords by defining them in the
19059 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
19060 If you have given a keyword a nickname when configuring it,
19061 that nickname may be used instead of the actual keyword.
19064 Look <A HREF="h_edit_nav_cmds">here</A>
19065 to see the available Editing and Navigation commands.
19067 <End of help on this topic>
19070 ======= h_index_tokens =======
19073 <TITLE>Tokens for Index and Replying</TITLE>
19077 This set of special tokens may be used in the
19078 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option,
19079 in the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
19080 in signature files,
19081 in template files used in
19082 <A HREF="h_rules_roles">"roles"</A>, and in the folder name
19083 that is the target of a Filter Rule.
19084 Some of them aren't available in all situations.
19086 The tokens are used as they appear below for the "<!--#echo var="VAR_index-format"-->"
19087 option, but they must be surrounded by underscores for the
19088 "<!--#echo var="VAR_reply-leadin"-->" option, in signature and template files,
19089 and in the target of Filter Rules.
19093 <H1><EM>Tokens Available for all Cases (except Filter Rules)</EM></H1>
19098 This token represents the Subject the sender gave the message.
19099 Alternatives for use in the index screen are SHORTSUBJECT,
19100 SUBJKEY, SHORTSUBJKEY, SUBJKEYINIT, SHORTSUBJKEYINIT, SUBJECTTEXT,
19101 SUBJKEYTEXT, and SUBJKEYINITTEXT.
19102 You may color the subject text in the MESSAGE INDEX screen differently by using the
19103 <A HREF="h_config_index_subject_color">Index Subject Color</A> and the
19104 <A HREF="h_config_index_opening_color">Index Opening Color</A>
19105 options available from
19106 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19111 This token represents the personal name (or email address if the name
19112 is unavailable) of the person specified in the message's "From:"
19114 You may color the from text in the MESSAGE INDEX screen differently by using the
19115 <A HREF="h_config_index_from_color">Index From Color</A>
19116 option available from
19117 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19122 This is similar to the "FROM" token, only it is always the
19123 email address, never the personal name.
19124 For example, "mailbox@domain".
19129 This is the same as the "ADDRESS" except that the
19130 domain part of the address is left off.
19131 For example, "mailbox".
19136 This token represents the personal name (or email address) of the person
19137 listed in the message's "Sender:" header field.
19142 This token represents the personal names (or email addresses if the names
19143 are unavailable) of the persons specified in the
19144 message's "To:" header field.
19149 This token represents the newsgroups from the
19150 message's "Newsgroups:" header field <EM>and</EM>
19151 the personal names (or email addresses if the names
19152 are unavailable) of the persons specified in the
19153 message's "To:" header field.
19158 Same as "NEWSANDTO" except in the opposite order.
19163 This token represents the newsgroups from the
19164 message's "Newsgroups:" header field.
19169 This token represents the personal names (or email addresses if the names
19170 are unavailable) of the persons specified in the
19171 message's "Cc:" header field.
19176 This token represents the personal names (or email addresses if the names
19177 are unavailable) of the persons specified in both the
19178 message's "To:" header field and
19179 the message's "Cc:" header field.
19182 <DT>NEWSANDRECIPS</DT>
19184 This token represents the newsgroups from the
19185 message's "Newsgroups:" header field <EM>and</EM>
19186 the personal names (or email addresses if the names
19187 are unavailable) of the persons specified in the
19188 message's "To:" and "Cc:" header fields.
19191 <DT>RECIPSANDNEWS</DT>
19193 Same as "NEWSANDRECIPS" except in the opposite order.
19198 This token represents the initials from the personal name
19199 of the person specified in the message's "From:"
19201 If there is no personal name, it is blank.
19206 This token represents the date on which the message was sent, according
19207 to the "Date" header field.
19208 It has the format MMM DD. For example, "Oct 23".
19210 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>,
19211 which adjusts for the timezone the message was sent from,
19212 may have an effect on the value of this token as well as the values of
19213 all of the other DATE or TIME tokens.
19214 Some of the DATE and TIME tokens are displayed in a locale-specific
19215 way unless the option
19216 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is set.
19221 This token represents the date on which the message was sent, according
19222 to the "Date" header field.
19223 It is "Today" if the message was sent today,
19224 "Yesterday" for yesterday,
19225 "Wednesday" if it was last Wednesday, and so on. If the
19226 message is from last year and is more than six months old it includes the year, as well.
19227 See the SMARTDATE alternatives below, as well.
19232 This token represents the most relevant elements of the date on which
19233 the message was sent (according to the "Date" header field),
19234 in a compact form. If the message was sent today, only the time is used
19235 (e.g. "9:22am", "10:07pm"); if it was sent during
19236 the past week, the day of the week and the hour are used
19237 (e.g. "Wed09am", "Thu10pm"); other dates are
19238 given as date, month, and year (e.g. "23Aug00",
19239 "9Apr98").
19242 <DT>SMARTTIME24</DT>
19244 This token has the structure "day hour:minute"
19245 (e.g. "Sun 19:03") for messages dated less than a week
19246 from the current date, or "month day" (e.g.
19247 "Nov 23") for messages dated less than 6 months
19248 ago, or "day/month/year" (e.g "06/Jan/16")
19249 for messages dated more than 6 months ago. It uses 9 characters
19250 of the width of the screen, and it left aligned.
19253 <DT>SMARTDATETIME</DT>
19255 This is a combination of SMARTDATE and SMARTTIME.
19256 It is SMARTDATE unless the SMARTDATE value is "Today", in which
19257 case it is SMARTTIME.
19258 See the SMARTDATETIME alternatives below, as well.
19263 This token represents the date on which the message was sent, according
19264 to the "Date" header field.
19265 It has the format YYYY-MM-DD. For example, "1998-10-23".
19268 <DT>SHORTDATEISO</DT>
19270 This token represents the date on which the message was sent, according
19271 to the "Date" header field.
19272 It has the format YY-MM-DD. For example, "98-10-23".
19275 <DT>SHORTDATE1</DT>
19277 This token represents the date on which the message was sent, according
19278 to the "Date" header field.
19279 It has the format MM/DD/YY. For example, "10/23/98".
19282 <DT>SHORTDATE2</DT>
19284 This token represents the date on which the message was sent, according
19285 to the "Date" header field.
19286 It has the format DD/MM/YY. For example, "23/10/98".
19289 <DT>SHORTDATE3</DT>
19291 This token represents the date on which the message was sent, according
19292 to the "Date" header field.
19293 It has the format DD.MM.YY. For example, "23.10.98".
19296 <DT>SHORTDATE4</DT>
19298 This token represents the date on which the message was sent, according
19299 to the "Date" header field.
19300 It has the format YY.MM.DD. For example, "98.10.23".
19305 This token represents the date on which the message was sent, according
19306 to the "Date" header field.
19307 It has the format MMM DD, YYYY. For example, "Oct 23, 1998".
19310 <DT>SMARTDATE alternatives</DT>
19312 There are several versions of SMARTDATE that are all the same except
19313 for the way they format dates far in the past.
19314 SMARTDATE formats the date using the information from your locale settings
19315 to format the date string. It may end up formatting dates so that they look
19316 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19318 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19319 may have an effect on the values of these tokens.
19320 If you want more control you may use one of the following.
19322 <DT>SMARTDATE</DT> <DD>If the option
19323 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19324 then this will be locale specific. Control this with the
19325 LC_TIME locale setting on a UNIX system. On Windows
19326 the Regional Options control panel may be used to set the Short date
19327 format. At the programming level, the strftime routine is what Alpine
19328 uses to print the date.
19329 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19330 to SMARTDATES1.</DD>
19331 <DT>SMARTDATEISO</DT> <DD>DATEISO format. See text above.</DD>
19332 <DT>SMARTDATESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19333 <DT>SMARTDATES1</DT> <DD>SHORTDATE1 format.</DD>
19334 <DT>SMARTDATES2</DT> <DD>SHORTDATE2 format.</DD>
19335 <DT>SMARTDATES3</DT> <DD>SHORTDATE3 format.</DD>
19336 <DT>SMARTDATES4</DT> <DD>SHORTDATE4 format.</DD>
19340 <DT>SMARTDATETIME alternatives</DT>
19342 There are several versions of SMARTDATETIME that are all very similar.
19343 The ones that end in 24 use a 24-hour clock for Today's messages instead
19344 of a 12-hour clock.
19345 The other variation is
19346 for the way they format dates far in the past.
19347 SMARTDATETIME and SMARTDATETIME24 format the date using the information from your locale settings
19348 to format the date string. It may end up formatting dates so that they look
19349 like DATEISO tokens, or SHORTDATE2 tokens, or something else entirely.
19351 <A HREF="h_config_dates_to_local"><!--#echo var="FEAT_convert-dates-to-localtime"--></A>
19352 may have an effect on the values of these tokens.
19353 The possible choices are:
19355 <DT>SMARTDATETIME</DT> <DD>If the option
19356 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A> is not set
19357 then this will be locale specific. Control this with the
19358 LC_TIME locale setting on a UNIX system. On Windows
19359 the Regional Options control panel may be used to set the Short date
19360 format. At the programming level, the strftime routine is what Alpine
19361 uses to print the date.
19362 If the <!--#echo var="FEAT_disable-index-locale-dates"--> option is set then this is equivalent
19363 to SMARTDATETIMES1.</DD>
19364 <DT>SMARTDATETIME24</DT> <DD>Use TIME24 for Today</DD>
19365 <DT>SMARTDATETIMEISO</DT> <DD>DATEISO format. See text above.</DD>
19366 <DT>SMARTDATETIMEISO24</DT> <DD>Use TIME24 for Today</DD>
19367 <DT>SMARTDATETIMESHORTISO</DT> <DD>SHORTDATEISO format.</DD>
19368 <DT>SMARTDATETIMESHORTISO24</DT> <DD>Use TIME24 for Today</DD>
19369 <DT>SMARTDATETIMES1</DT> <DD>SHORTDATE1 format.</DD>
19370 <DT>SMARTDATETIMES124</DT> <DD>Use TIME24 for Today</DD>
19371 <DT>SMARTDATETIMES2</DT> <DD>SHORTDATE2 format.</DD>
19372 <DT>SMARTDATETIMES224</DT> <DD>Use TIME24 for Today</DD>
19373 <DT>SMARTDATETIMES3</DT> <DD>SHORTDATE3 format.</DD>
19374 <DT>SMARTDATETIMES324</DT> <DD>Use TIME24 for Today</DD>
19375 <DT>SMARTDATETIMES4</DT> <DD>SHORTDATE4 format.</DD>
19376 <DT>SMARTDATETIMES424</DT> <DD>Use TIME24 for Today</DD>
19382 This token represents the date on which the message was sent, according
19383 to the "Date" header field.
19384 It looks like "Sat, 23 Oct 1998".
19385 This token is never converted in any locale-specific way.
19390 This token represents the date on which the message was sent, according
19391 to the "Date" header field.
19392 It is your operating system's idea of the preferred date representation for the current locale.
19393 Internally it uses the %x version of the date from the strftime routine.
19398 This token represents the time at which the message was sent, according
19399 to the "Date" header field.
19400 It is the preferred time representation for the current locale.
19401 Internally it uses the %X version of the time from the strftime routine.
19404 <DT>PREFDATETIME</DT>
19406 This token represents the date and time at which the message was sent, according
19407 to the "Date" header field.
19408 It is the preferred date and time representation for the current locale.
19409 Internally it uses the %c version of the time from the strftime routine.
19414 This token represents the day of the month on which the message was sent,
19415 according to the "Date" header field.
19416 For example, "23" or "9".
19421 This token represents the day of the month on which the message was sent,
19422 according to the "Date" header field.
19423 For example, "23" or "09".
19424 It is always 2 digits.
19427 <DT>DAYORDINAL</DT>
19429 This token represents the ordinal number that is the day of
19430 the month on which the message was sent,
19431 according to the "Date" header field.
19432 For example, "23rd" or "9th".
19437 This token represents the day of the week on which the message was sent,
19438 according to the "Date" header field.
19439 For example, "Sunday" or "Wednesday".
19442 <DT>DAYOFWEEKABBREV</DT>
19444 This token represents the day of the week on which the message was sent,
19445 according to the "Date" header field.
19446 For example, "Sun" or "Wed".
19449 <DT>MONTHABBREV</DT>
19451 This token represents the month the message was sent, according
19452 to the "Date" header field.
19453 For example, "Oct".
19458 This token represents the month in which the message was sent, according
19459 to the "Date" header field.
19460 For example, "October".
19465 This token represents the month in which the message was sent, according
19466 to the "Date" header field.
19467 For example, "10" or "9".
19470 <DT>MONTH2DIGIT</DT>
19472 This token represents the month in which the message was sent, according
19473 to the "Date" header field.
19474 For example, "10" or "09".
19475 It is always 2 digits.
19480 This token represents the year the message was sent, according
19481 to the "Date" header field.
19482 For example, "1998" or "2001".
19485 <DT>YEAR2DIGIT</DT>
19487 This token represents the year the message was sent, according
19488 to the "Date" header field.
19489 For example, "98" or "01".
19490 It is always 2 digits.
19495 This token represents the time at which the message was sent, according
19496 to the "Date" header field.
19497 There is no adjustment made for different time zones, so you'll get
19498 the time the message was sent according to the time zone the sender
19500 It has the format HH:MM. For example, "17:28".
19505 This token represents the time at which the message was sent, according
19506 to the "Date" header field.
19507 This time is for a 12 hour clock.
19508 It has the format HH:MMpm.
19509 For example, "5:28pm" or "11:13am".
19514 This token represents the numeric timezone from
19515 the "Date" header field.
19516 It has the format [+-]HHMM. For example, "-0800".
19522 <H1><EM>Tokens Available Only for <!--#echo var="VAR_index-format"--></EM></H1>
19527 This token represents the message's current position in the folder that,
19528 of course, may change as the folder is sorted or new mail arrives.
19533 This token represents a three character wide field displaying various
19534 aspects of the message's state.
19535 The first character is either blank,
19536 a '*' for message marked Important, or a '+' indicating a message
19537 addressed directly to you (as opposed to your having received it via a
19538 mailing list, for example).
19540 "<A HREF="h_config_mark_for_cc"><!--#echo var="FEAT_mark-for-cc"--></A>"
19541 is set, if the first character would have been
19542 blank then it will instead be a '-' if the message is cc'd to you.
19543 The second character is typically blank,
19544 though the arrow cursor may occupy it if either the
19545 "<A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>"
19547 "<A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A>" feature
19548 is set (or you actually are on a slow link).
19549 The third character is either '<A HREF="h_flag_deleted">D</A>' (Deleted),
19550 '<A HREF="h_flag_answered">A</A>' (Answered),
19551 '<A HREF="h_flag_forwarded">F</A>' (Forwarded),
19552 '<A HREF="h_flag_new">N</A>' (New), or blank.
19554 If you are using a threaded view of the index and this message is at the
19555 top of a collapsed portion of a thread,
19556 then this token refers to all of the messages in the collapsed portion of
19557 the thread instead of just the top message.
19558 The first character will be a '*' if <EM>any</EM> of the messages in the thread
19559 are marked Important, else a '+' if any of the messages are addressed
19560 to you, else a '-' if any of the messages are cc'd to you.
19561 The third character will be a 'D' if <EM>all</EM> of the messages
19562 in the collapsed thread are marked deleted,
19563 an 'A' if <EM>all</EM> of the messages
19564 in the collapsed thread are marked answered,
19565 it will be an 'N' if any of
19566 the messages are undeleted and unseen, and it will be blank otherwise.
19569 <DT>FULLSTATUS</DT>
19571 This token represents a less abbreviated alternative
19572 to the "STATUS" token.
19573 It is six characters wide.
19574 The first character is '+', '-', or blank, the
19575 second blank, the third either '*' or blank, the fourth
19576 '<A HREF="h_flag_new">N</A>' or blank,
19577 the fifth '<A HREF="h_flag_answered">A</A>'
19578 or blank, and the sixth character is
19579 either '<A HREF="h_flag_deleted">D</A>' or
19582 If you are using a threaded view of the index and this message is at the
19583 top of a collapsed portion of a thread,
19584 then this token refers to all of the messages in the collapsed portion of
19585 the thread instead of just the top message.
19586 The first character is '+', '-', or blank depending on whether <EM>any</EM>
19587 of the messages in the collapsed thread are addressed to you or cc'd to you.
19588 The third character will be '*' if any of the messages are marked
19590 The fourth character will be 'N' if all of the messages in the thread
19591 are New, else 'n' if some of the messages in the thread are New, else blank.
19592 The fifth character will be 'A' or 'a' or blank, and the sixth character
19593 will be 'D' or 'd' or blank.
19596 <DT>IMAPSTATUS</DT>
19598 This token represents an even less abbreviated alternative to the
19599 "STATUS" token.
19600 It differs from "FULLSTATUS" in only the fourth character, which is
19601 an 'N' if the message is new to this folder since the last time
19602 it was opened <EM>and</EM> it has not been viewed, an 'R' (Recent) if the message
19603 is new to the folder and has been viewed, a 'U' (Unseen) if the message is not
19604 new to the folder since it was last opened <EM>but</EM> has not been
19605 viewed, or a blank if the message has been in the folder since it was
19606 last opened and has been viewed.
19608 If you are using a threaded view of the index and this message is at the
19609 top of a collapsed portion of a thread,
19610 then the fourth character will be
19611 'N' if all of the messages in the thread are unseen and recent;
19612 else 'n' if some of the messages in the thread are unseen and recent;
19613 else 'U' if all of the messages in the thread are unseen and not recent;
19614 else 'u' if some of the messages in the thread are unseen and not recent;
19615 else 'R' if all of the messages in the thread are seen and recent;
19616 else 'r' if some of the messages in the thread are seen and recent;
19620 <DT>SHORTIMAPSTATUS</DT>
19622 This is the same as the last four of the six characters of IMAPSTATUS,
19623 so the '+' To Me information will be missing.
19628 This token represents the total size, in bytes, of the message.
19629 If a "K" (Kilobyte)
19630 follows the number, the size is approximately 1,000
19631 times that many bytes (rounded to the nearest 1,000).
19632 If an "M" (Megabyte) follows the number, the size is approximately
19633 1,000,000 times that many bytes.
19634 Commas are not used in this field.
19635 This field is seven characters wide, including the enclosing parentheses.
19636 Sizes are rounded when "K" or "M" is present.
19637 The progression of sizes used looks like:
19640 <CENTER><SAMP>0 1 ... 9999 10K ... 999K 1.0M ... 99.9M 100M ... 2000M</SAMP></CENTER>
19646 This token represents the total size, in bytes, of the message.
19647 If a "K" (Kilobyte)
19648 follows the number, the size is approximately 1,000
19649 times that many bytes (rounded to the nearest 1,000).
19650 If an "M" (Megabyte) follows the number, the size is approximately
19651 1,000,000 times that many bytes.
19652 Commas are used if the number shown is 1,000 or greater.
19653 The SIZECOMMA field is one character wider than the SIZE field.
19654 Sizes are rounded when "K" or "M" is present.
19655 The progression of sizes used looks like:
19658 <CENTER><SAMP>0 1 ... 99,999 100K ... 9,999K 10.0M ... 999.9M 1,000M ... 2,000M</SAMP></CENTER>
19664 This token represents the total size of the message, expressed in
19665 kilobytes or megabytes, as most appropriate.
19666 These are 1,024 byte kilobytes and 1,024 x 1,024 byte megabytes.
19667 The progression of sizes used looks like:
19670 <CENTER><SAMP>0K 1K ... 1023K 1.0M ... 99.9M 100M ... 2047M</SAMP></CENTER>
19674 <DT>SIZENARROW</DT>
19676 This token represents the total size, in bytes, of the message.
19677 If a "K" (Kilobyte)
19678 follows the number, the size is approximately 1,000
19679 times that many bytes.
19680 If an "M" (Megabyte) follows the number, the size is approximately
19681 1,000,000 times that many bytes.
19682 If a "G" (Gigabyte) follows the number, the size is approximately
19683 1,000,000,000 times that many bytes.
19684 This field uses only five characters of screen width, including the enclosing
19686 The progression of sizes used looks like:
19689 <CENTER><SAMP>0 1 ... 999 1K ... 99K .1M ... .9M 1M ... 99M .1G ... .9G 1G 2G</SAMP></CENTER>
19693 <DT>DESCRIPSIZE</DT>
19695 This token is intended to represent a more useful description of the
19696 message than just its size, but it isn't very useful at this point.
19697 The plus sign in this view means there are attachments.
19698 Note that including this token in
19699 the "<!--#echo var="VAR_index-format"-->" could slow down the
19700 display a little while Alpine collects the necessary information.
19703 <DT>SHORTSUBJECT</DT>
19704 <DD> This token is the same as SUBJECT, but removes
19705 text between "[" and "]". Typically text enclosed
19706 between these characters corresponds to mailing list names, and may be
19707 unnecessary or unwanted in some instances.
19712 This token is the same as the SUBJECT token unless keywords are set for
19714 In that case, a list of keywords enclosed in braces will be prepended to
19715 the subject of the message.
19716 Only those keywords that you have defined in your
19717 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19718 in Setup/Config are considered in the list.
19719 In other words, keywords that have been set by some other means, perhaps
19720 by another email program, won't show up unless included in
19721 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19722 Having this set in the <!--#echo var="VAR_index-format"--> will also cause the keywords to be
19723 prepended to the subject in the MESSAGE TEXT screen.
19724 If you have given a keyword a nickname
19725 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19726 instead of the actual keyword.
19727 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19728 option may be used to modify this token slightly.
19729 It is also possible to color keywords in the index using the
19730 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19733 <DT>SHORTSUBJKEY</DT>
19734 <DD> This token is the same as SUBJKEY, but it is based on
19735 SHORTSUBJECT, instead of in SUBJECT.
19738 <DT>SUBJKEYINIT</DT>
19740 This token is the same as the SUBJKEY token except that instead of
19741 prepending a list of keywords to the subject, a list of first initials
19742 of keywords will be prepended instead.
19743 For example, if a message has the keywords <EM>Work</EM> and <EM>Now</EM>
19744 set (or Work and Now are the Alpine nicknames of keywords that are set)
19745 then the SUBJKEY token would cause a result like
19747 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
19749 whereas the SUBJKEYINIT token would give
19751 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
19753 Only those keywords that you have defined in your
19754 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19755 in Setup/Config are considered in the list.
19756 In other words, keywords that have been set by some other means, perhaps
19757 by another email program, won't show up unless included in
19758 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19759 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
19760 option may be used to modify this token slightly.
19761 It is also possible to color keywords in the index using the
19762 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19765 <DT>SHORTSUBJKEYINIT</DT>
19766 <DD> This token is the same as SUBJKEYINIT, but it is based on
19767 SHORTSUBJECT, instead of in SUBJECT.
19770 <DT>SUBJECTTEXT</DT>
19772 Same as SUBJECT but if there is room in the Subject field for more text,
19773 the opening part of the text of the message is displayed after the subject.
19774 The time needed to fetch the text may cause a performance problem
19775 which can, of course, be avoided by using the SUBJECT version of
19776 the Subject instead.
19777 You may color this opening text differently by using the
19778 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19779 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19780 You may adjust the characters that are displayed between the Subject and the
19781 opening text with the option
19782 <A HREF="h_config_opening_sep"><!--#echo var="VAR_opening-text-separator-chars"--></A>.
19785 <DT>SUBJKEYTEXT</DT>
19787 Same as SUBJKEY but with the opening message text.
19790 <DT>OPENINGTEXT</DT>
19792 This is similar to SUBJECTTEXT.
19793 Instead of combining the Subject and the opening text in a single
19794 field in the index screen this token allows you to allocate a
19795 separate column just for the opening text of the message.
19796 The time needed to fetch this text may cause a performance problem.
19797 You may color this opening text differently by using the
19798 <A HREF="h_config_index_opening_color">Index Opening Color</A> option available from
19799 the <A HREF="h_color_setup">Setup Kolor</A> screen.
19802 <DT>OPENINGTEXTNQ</DT>
19804 This is very similar to OPENINGTEXT.
19805 The NQ stands for No Quotes.
19806 The only difference is that quoted text (lines beginning with >) is deleted.
19807 For some messages this may be confusing.
19808 For example, a message might have a line preceding some quoted
19809 text that reads something like "On May 8th person A said."
19810 That no longer makes sense after the quoted text is deleted and it
19811 will appear that person A said whatever the text after the quote
19812 is, even though that is really person B talking.
19815 <DT>SUBJKEYINITTEXT</DT>
19817 Same as SUBJKEYINIT but with the opening message text.
19822 This is a space-delimited list of keywords that are set for the message.
19823 Only those keywords that you have defined in your
19824 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option
19825 in Setup/Config are considered in the list.
19826 In other words, keywords that have been set by some other means, perhaps
19827 by another email program, won't show up unless included in
19828 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>.
19829 If you have given a keyword a nickname
19830 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), that nickname is displayed
19831 instead of the actual keyword.
19832 It is also possible to color keywords in the index using the
19833 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19834 This token defaults to an arbitrary width of 5.
19835 You should set it to whatever width suits you using something
19836 like KEY(17) in the <!--#echo var="VAR_index-format"-->.
19841 This is a list of keyword initials that are set for the message.
19842 If you have given a keyword a nickname
19843 (<A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>), the initial of that nickname
19844 is displayed instead of the initial of the actual keyword.
19845 It is also possible to color keyword initials in the index using the
19846 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
19847 This token defaults to an arbitrary width of 2.
19848 You should set it to whatever width suits you using something
19849 like KEYINIT(3) in the <!--#echo var="VAR_index-format"-->.
19854 The X-Priority header is a non-standard header that is used in a
19855 somewhat standard way by many mail programs.
19856 Alpine expects the value of this header to be a digit with a value
19857 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
19858 Since this priority is something that the sender sets it is only an indication
19859 of the priority that the sender attaches to the mail and it is therefore almost
19860 totally unreliable for use as a filtering criterion.
19861 This token will display the numeric value of the priority if it is between
19863 It will be suppressed (blank) if the value is 3, which is normal priority.
19864 This token may be colored with the
19865 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19868 <DT>PRIORITYALPHA</DT>
19870 This is a more verbose interpretation of the X-Priority field.
19871 Once again nothing is displayed unless the value of the field
19873 The values displayed for those values are:
19876 <TR> <TD>1</TD> <TD>Highest</TD> </TR>
19877 <TR> <TD>2</TD> <TD>High</TD> </TR>
19878 <TR> <TD>4</TD> <TD>Low</TD> </TR>
19879 <TR> <TD>5</TD> <TD>Lowest</TD> </TR>
19882 This token may be colored with the
19883 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19888 This is a one character, non-numeric version of the X-Priority field.
19889 If the value of the X-Priority header is 1 or 2 an exclamation
19890 point is displayed.
19891 If the value is 4 or 5 a "v" (think down arrow) is displayed.
19892 This token may be colored with the
19893 <A HREF="h_config_index_pri_color">Index Priority Symbol Colors</A>.
19898 This is a one column wide field that represents the number of attachments
19899 a message has. It will be blank if there are no attachments, a single
19900 digit for one to nine attachments, or an asterisk for more than nine.
19901 Note that including this token in
19902 the "<!--#echo var="VAR_index-format"-->" could slow down the
19903 display a little while Alpine collects the necessary information.
19908 This token represents <EM>either</EM> the personal name (or email address) of
19909 the person listed in the message's "From:" header
19910 field, <EM>or</EM>, if that address is yours or one of your
19911 <A HREF="h_config_alt_addresses">alternate addresses</A>,
19912 the first person specified in the
19913 message's "To:" header field
19914 with the prefix "To: " prepended.
19915 If the from address is yours and there is also no "To" address,
19916 Alpine will use the address on the "Cc" line.
19917 If there is no address there, either, Alpine will look for a newsgroup name
19918 from the "Newsgroups" header field and put
19919 that after the "To: " prefix.
19922 <DT>FROMORTONOTNEWS</DT>
19924 This is almost the same as <EM>FROMORTO</EM>.
19925 The difference is that newsgroups aren't considered.
19926 When a message is from you, doesn't have a To or Cc, and does have
19927 a Newsgroups header; this token will be your name instead of the name
19928 of the newsgroup (like it would be with FROMORTO).
19933 This is a different sort of token.
19934 It allows you to display a label within each index line.
19935 It will be the same fixed text for each line.
19936 It is different from all the other tokens in that there is no space column
19937 displayed after this token.
19938 Instead, it is butted up against the following field.
19939 It also has a different syntax.
19940 The text to display is given following a colon after the
19941 word "TEXT".
19944 <CENTER><SAMP>TEXT:abc=</SAMP></CENTER>
19946 would insert the literal text "abc=" (without the quotes)
19947 into the index display line.
19948 You must quote the text if it includes space characters, like
19950 <CENTER><SAMP>TEXT:"abc = "</SAMP></CENTER>
19956 This allows you to display the text from a particular header line in the
19958 The syntax for this token is substantially different from all the others
19959 in order that you might be able to display a portion of the text following
19960 a particular header.
19961 The header name you are interested in is given following a colon
19962 after the word "HEADER".
19965 <CENTER><SAMP>HEADER:X-Spam</SAMP></CENTER>
19967 would display the text of the X-Spam header, if any.
19968 Like for other index tokens a width field may (and probably should)
19971 <CENTER><SAMP>HEADER:X-Spam(10)</SAMP></CENTER>
19973 displays the first ten characters of the X-Spam header.
19974 Unlike other index tokens, the syntax for HEADER is more flexible.
19975 An optional second argument comes after a comma inside the parentheses.
19976 It specifies the "field" number.
19977 By default, the field separator is a space character.
19978 No extra space characters are allowed in the argument list.
19980 <CENTER><SAMP>HEADER:X-Spam(10,2)</SAMP></CENTER>
19982 would display the second field, left-justified, in a 10 character
19984 The second field would consist of all the text after the first space
19985 up to the next space or the end of the header.
19986 The default field number is zero, which stands for the entire line.
19987 There is also an optional third argument that is a list of field
19988 separators. It defaults to a space character.
19991 <CENTER><SAMP>HEADER:X-Spam(10,2,:% )</SAMP></CENTER>
19993 would cause the field separators to be any of colon, percent,
19994 or space (there is a space character between the percent and the
19995 right parenthesis).
19996 The first field runs from the start of the header value up to the first
19997 colon, percent, or space; the second goes from there to the next; and so on.
19998 In order to use a comma character as a field separator you must escape
19999 it by preceding it with a backslash (\).
20000 The same is true of the backslash character itself.
20001 There is one further optional argument.
20002 It is an R or an L to specify right or left adjustment of the text
20004 The default is to left justify, however if you are displaying numbers
20005 you might prefer to right justify.
20007 Here's an example of a SpamAssassin header.
20008 The exact look of the header will vary, but if your incoming mail
20009 contains headers that look like the following
20011 <CENTER><SAMP>X-Spam-Status: Yes, hits=10.6 tagged_above=-999.0 required=7.0 tests=BAYE...</SAMP></CENTER>
20013 you might want to display the hits value.
20014 The first field starts with the Y in Yes.
20015 To get what you're interested in you might use "=" and
20016 space as the field separators and display the third field, like
20018 <CENTER><SAMP>HEADER:X-Spam-Status(4,3,= )</SAMP></CENTER>
20020 or maybe you would break at the dot instead
20022 <CENTER><SAMP>HEADER:X-Spam-Status(2,2,=.,R)</SAMP></CENTER>
20024 Another example we've seen has headers that look like
20026 <CENTER><SAMP>X-Spam: Gauge=IIIIIII, Probability=7%, Report=...</SAMP></CENTER>
20028 Because there are two equals and a comma before the 7% and a comma
20029 after it, the token
20031 <CENTER><SAMP>HEADER:X-Spam(3,4,=\,,R)</SAMP></CENTER>
20033 should display the probability (for example 7% or 83%) right justified
20039 This gives an alternative way to display the current message in the
20040 MESSAGE INDEX screen.
20041 Usually the current message is indicated by the line being shown in
20043 Instead, if the ARROW token is included in your <!--#echo var="VAR_index-format"-->,
20044 the current line will include an "arrow" that
20047 <CENTER><SAMP>-></SAMP></CENTER>
20049 in the ARROW token's field.
20050 For all of the non-current messages, the ARROW field will be filled
20052 If you use the fixed-field width feature the length of the "arrow"
20054 The arrow will be drawn as width-1 dashes followed by a greater than sign.
20055 For example, if you use ARROW(3) you will get
20057 <CENTER><SAMP>--></SAMP></CENTER>
20059 and ARROW(1) will give you just
20061 <CENTER><SAMP>></SAMP></CENTER>
20063 It is also possible to set the color of the ARROW field.
20064 By default (and for non-current messages) the arrow is colored the same
20065 as the index line it is part of.
20066 You may set it to be another color with the
20067 <A HREF="h_config_index_arrow_color">Index Arrow Color</A> option available from
20068 the <A HREF="h_color_setup">Setup Kolor</A> screen.
20074 <a href="h_rules_score">score</a>
20076 This will be six columns wide to accomodate the widest possible score.
20077 You will probably want to use the <!--#echo var="VAR_index-format"--> fixed-field width feature
20078 to limit the width of the field to the widest score that
20079 you use (e.g. SCORE(3) if your scores are always between 0 and 999).
20080 If you have not defined any score rules the scores will all be zero.
20081 If any of your score rules contain AllText or BodyText patterns
20082 then including SCORE in the <!--#echo var="VAR_index-format"-->
20083 may slow down the display of the MESSAGE INDEX screen.
20088 <H1><EM>Tokens Available for all but <!--#echo var="VAR_index-format"--></EM></H1>
20093 This token represents the current newsgroup if there is one.
20094 For example, "comp.mail.pine".
20099 This token represents the message ID of the message.
20100 This token does not work with Filter Rule folder names.
20105 This token represents the current date.
20106 It has the format MMM DD. For example, "Oct 23".
20109 <DT>CURDATEISO</DT>
20111 This token represents the current date.
20112 It has the format YYYY-MM-DD. For example, "1998-10-23".
20115 <DT>CURDATEISOS</DT>
20117 This token represents the current date.
20118 It has the format YY-MM-DD. For example, "98-10-23".
20121 <DT>CURPREFDATE</DT>
20123 This token represents the current date.
20124 It is your operating system's idea of the preferred date representation for the current locale.
20125 Internally it uses the %x version of the date from the strftime routine.
20128 <DT>CURPREFTIME</DT>
20130 This token represents the current time.
20131 It is the preferred time representation for the current locale.
20132 Internally it uses the %X version of the time from the strftime routine.
20135 <DT>CURPREFDATETIME</DT>
20137 This token represents the current date and time.
20138 It is the preferred date and time representation for the current locale.
20139 Internally it uses the %c version of the time from the strftime routine.
20144 This token represents the current time.
20145 It has the format HH:MM. For example, "17:28".
20150 This token represents the current time.
20151 This time is for a 12 hour clock.
20152 It has the format HH:MMpm.
20153 For example, "5:28pm" or "11:13am".
20158 This token represents the current day of the month.
20159 For example, "23" or "9".
20162 <DT>CURDAY2DIGIT</DT>
20164 This token represents the current day of the month.
20165 For example, "23" or "09".
20166 It is always 2 digits.
20169 <DT>CURDAYOFWEEK</DT>
20171 This token represents the current day of the week.
20172 For example, "Sunday" or "Wednesday".
20175 <DT>CURDAYOFWEEKABBREV</DT>
20177 This token represents the current day of the week.
20178 For example, "Sun" or "Wed".
20183 This token represents the current month.
20184 For example, "10" or "9".
20187 <DT>CURMONTH2DIGIT</DT>
20189 This token represents the current month.
20190 For example, "10" or "09".
20191 It is always 2 digits.
20194 <DT>CURMONTHLONG</DT>
20196 This token represents the current month.
20197 For example, "October".
20200 <DT>CURMONTHABBREV</DT>
20202 This token represents the current month.
20203 For example, "Oct".
20208 This token represents the current year.
20209 For example, "1998" or "2001".
20212 <DT>CURYEAR2DIGIT</DT>
20214 This token represents the current year.
20215 For example, "98" or "01".
20216 It is always 2 digits.
20221 This token represents last month.
20222 For example, if this is November (the 11th month),
20223 it is equal to "10" or if this is October (the 10th month),
20224 it is "9".
20225 It is possible that this and the other tokens beginning with LASTMONTH
20226 below could be useful when used with a Filtering Rule that
20227 has the "Beginning of Month" option set.
20230 <DT>LASTMONTH2DIGIT</DT>
20232 This token represents last month.
20233 For example, if this is November (the 11th month),
20234 it is equal to "10" or if this is October (the 10th month),
20235 it is "09".
20236 It is always 2 digits.
20239 <DT>LASTMONTHLONG</DT>
20241 This token represents last month.
20242 For example, if this is November the value is "October".
20245 <DT>LASTMONTHABBREV</DT>
20247 This token represents last month.
20248 For example, if this is November the value is "Oct".
20251 <DT>LASTMONTHYEAR</DT>
20253 This token represents what the year was a month ago.
20254 For example, if this is October, 1998, it is "1998".
20255 If this is January, 1998, it is "1997".
20258 <DT>LASTMONTHYEAR2DIGIT</DT>
20260 This token represents what the year was a month ago.
20261 For example, if this is October, 1998, it is "98".
20262 If this is January, 1998, it is "97".
20267 This token represents last year.
20268 For example, if this is 1998, it equals "1997".
20269 It is possible that this
20270 could be useful when used with a Filtering Rule that
20271 has the "Beginning of Year" option set.
20274 <DT>LASTYEAR2DIGIT</DT>
20276 This token represents last year.
20277 For example, if this is 1998, it equals "97".
20278 It is always 2 digits.
20283 This token represents the nickname of the
20284 role currently being used. If no role is being used,
20285 then no text will be printed for this token.
20286 This token does not work with Filter Rule folder names.
20291 <H1><EM>Token Available Only for <!--#echo var="VAR_reply-leadin"--></EM></H1>
20292 See the help for the
20293 <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option
20294 to see why you might want to use this.
20295 Since the <!--#echo var="VAR_reply-leadin"--> contains free text this token
20296 must be surrounded by underscores when used.
20301 This is an end of line marker.
20306 <H1><EM>Token Available Only for Templates and Signatures</EM></H1>
20311 This token is different from the others.
20312 When it is replaced it is replaced with nothing, but it sets an Alpine
20313 internal variable that tells the composer to start with the cursor
20314 positioned at the position where this token was.
20315 If both the template file and the signature file contain
20316 a "CURSORPOS" token, then the position in the template file
20318 If there is a template file and neither it nor the signature file contains
20319 a "CURSORPOS" token, then the cursor is positioned
20320 after the end of the contents of the
20321 template file when the composer starts up.
20326 <End of help on this topic>
20329 ======= h_reply_token_conditionals =======
20332 <TITLE>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</TITLE>
20335 <H1>Conditional Inclusion of Text for <!--#echo var="VAR_reply-leadin"-->, Signatures, and Templates</H1>
20337 Conditional text inclusion may be used with
20338 the <A HREF="h_config_reply_intro">"<!--#echo var="VAR_reply-leadin"-->"</A> option,
20339 in signature files, and in template files used in
20340 <A HREF="h_rules_roles">"roles"</A>.
20341 It may <EM>not</EM> be used with the
20342 <A HREF="h_config_index_format">"<!--#echo var="VAR_index-format"-->"</A> option.
20345 There is a limited if-else capability for including text.
20346 The if-else condition is based
20347 on whether or not a given token would result in replacement text you
20349 The syntax of this conditional inclusion is
20351 <CENTER><SAMP>_token_(match_this, if_matched [ , if_not_matched ] )</SAMP></CENTER>
20353 The left parenthesis must follow the underscore immediately, with no
20355 It means the token is expanded and the results of that expansion are
20356 compared against the "match_this" argument.
20357 If there is an exact match, then the "if_matched" text is used
20358 as the replacement text.
20359 Otherwise, the "if_not_matched" text is used.
20360 One of the most useful values for the "match_this" argument is
20361 the empty string, "".
20362 In that case the expansion is compared against the empty string.
20364 Here's an example to make it clearer.
20365 This text could be included in one of your template files:
20367 <CENTER><SAMP>_NEWS_("", "I'm replying to email", "I'm replying to news")</SAMP></CENTER>
20369 If that is included in a template file that you are using while replying
20370 to a message (because you chose to use the role it was part of),
20371 and that message has a newsgroup header and a newsgroup in that header,
20374 <CENTER><SAMP>I'm replying to news</SAMP></CENTER>
20376 will be included in the message you are about to compose.
20377 On the other hand, if the message you are replying to does not have
20378 a newsgroup, then the text
20380 <CENTER><SAMP>I'm replying to email</SAMP></CENTER>
20382 would be included instead.
20383 This would also work in signature files and in
20384 the "<!--#echo var="VAR_reply-leadin"-->" option.
20385 If the "match_this", "if_matched",
20386 or "if_not_matched" arguments contain
20387 spaces, parentheses, or commas;
20388 they have to be quoted with double quotation marks (like in the example
20390 If you want to include a literal quote (") in the text you must escape the
20391 quote by preceding it with a backslash (\) character.
20392 If you want to include a literal backslash character you must escape it
20393 by preceding it with another backslash.
20395 The comma followed by "if_not_matched" is optional.
20396 If there is no "if_not_matched"
20397 present then no text is included if the not_matched case is true.
20398 Here's another example:
20400 <CENTER><SAMP>_NEWS_("", "", "This msg was seen in group: _NEWS_.")</SAMP></CENTER>
20402 Here you can see that tokens may appear in the arguments.
20403 The same is true for tokens with the conditional parentheses.
20404 They may appear in arguments,
20405 though you do have to be careful to get the quoting and escaping of
20406 nested double quotes correct.
20407 If this was in the signature file being used and you were replying to a message
20408 sent to comp.mail.pine the resulting text would be:
20410 <CENTER><SAMP>This msg was seen in group: comp.mail.pine.</SAMP></CENTER>
20412 If you were replying to a message that wasn't sent to any newsgroup the
20413 resulting text would be a single blank line.
20414 The reason you'd get a blank line is because the end of the line is
20415 outside of the conditional, so is always included.
20416 If you wanted to get rid of that blank line you could do so by moving
20417 the end of line inside the conditional.
20418 In other words, it's ok to have multi-line
20419 "if_matched" or "if_not_matched" arguments in your
20421 The text just continues until the next double quotation, even if it's not
20424 Here's an example for use in the "<!--#echo var="VAR_reply-leadin"-->":
20426 <CENTER><SAMP>On _DAYDATE_, _FROM__CURNEWS_("", "", "seen in _CURNEWS_,") wrote</SAMP></CENTER>
20428 If this was in your <!--#echo var="VAR_reply-leadin"--> and you were replying to a message
20429 while reading the newsgroup comp.mail.pine the resulting text would be:
20431 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone, seen in comp.mail.pine, wrote:</SAMP></CENTER>
20433 If you were replying to a message while reading an email folder instead
20434 of a newsgroup the resulting leadin text would be
20436 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
20438 Here's one more (contrived) example illustrating a matching argument
20439 that is not the empty string.
20441 <CENTER><SAMP>_SMARTDATE_("Today", _SMARTDATE_, "On _DATE_") _FROM_ wrote:</SAMP></CENTER>
20443 If this was the value of your "<!--#echo var="VAR_reply-leadin"-->" option and you
20445 a message that was sent today, then the value of the "<!--#echo var="VAR_reply-leadin"-->"
20448 <CENTER><SAMP>Today Fred Flintstone wrote:</SAMP></CENTER>
20450 But if you were replying to a message sent on Oct. 27 (and that wasn't
20451 today) you would get
20453 <CENTER><SAMP>On Oct 27 Fred Flintstone wrote:</SAMP></CENTER>
20456 <End of help on this topic>
20459 ======= h_composer_cntxt_nick =======
20462 <TITLE>Collection Nickname Explained</TITLE>
20465 <H1>Collection Edit Help -- Nickname Field</H1>
20467 This field is provided so you can add a short nickname to use when
20468 referring to this collection within Alpine. Spaces are allowed, and
20469 you don't need to use double-quotes. However, the double-quote
20470 character is not allowed.
20472 Look <A HREF="h_edit_nav_cmds">here</A>
20473 to see the available Editing and Navigation commands.
20475 <End of help on this topic>
20478 ======= h_folder_server_syntax =======
20481 <TITLE>Server Name Syntax</TITLE>
20484 <H1>Server Name Syntax</H1>
20486 This help describes the syntax that may be used for server names
20487 that may be associated with remote folders or SMTP servers.
20490 A server name is the hostname of the server.
20491 It's a good idea to use the host's fully-qualified network name.
20494 <CENTER><SAMP>foo.example.com</SAMP></CENTER>
20497 However, IP addresses are allowed if surrounded
20498 with square-brackets.
20501 <CENTER><SAMP>[127.0.0.1]</SAMP></CENTER>
20504 An optional network port number may be supplied by appending
20505 a colon (:) followed by the port number
20506 to the server name.
20507 By default, the IMAP port number, 143, is used.
20510 <CENTER><SAMP>foo.example.com:port</SAMP></CENTER>
20513 Besides server name and optional port number, various other optional
20514 parameters may be supplied that alter Alpine's interaction with the server.
20515 A parameter is supplied by appending a slash (/) character followed by
20516 the parameter's name and,
20517 depending on the particular parameter, the value assigned to that
20518 name, to the server name (and optional port number).
20519 Parameter names are <EM>not</EM> case sensitive.
20520 Currently supported parameters include:
20525 <DD>This parameter requires an associated value, and is intended to
20526 provide the username identifier with which to establish the server
20528 If your SMTP server offers SMTP AUTH authentication, adding this
20530 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
20531 option will cause Alpine to attempt to authenticate to the server using the
20533 Similarly, if your NNTP server offers NNTP "AUTHINFO SASL"
20534 or "AUTHINFO USER" authentication, adding this parameter to the
20535 <A HREF="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></A>
20536 option (or to the server name for any folder collection using NNTP)
20537 will cause Alpine to attempt
20538 to authenticate to the server using the supplied username.
20539 An example might be:
20542 <CENTER><SAMP>/user=katie</SAMP></CENTER>
20549 Normally, when a new connection is made an attempt is made to
20550 negotiate a secure (encrypted) session using Transport Layer Security (TLS).
20551 If that fails then a non-encrypted connection will be attempted instead.
20552 This is a unary parameter indicating communication with the server must
20553 take place over a TLS connection. If the attempt to use TLS fails then
20554 this parameter will cause the connection to fail instead of falling
20555 back to an unsecure connection.
20558 <CENTER><SAMP>/tls</SAMP></CENTER>
20565 This is a unary parameter indicating communication with the server should
20566 take place over a Secure Socket Layer connection. The server must support
20567 this method, and be prepared to accept connections on the appropriate
20568 port (993 by default).
20569 Alpine must be linked with an SSL library for this option to be operational.
20572 <CENTER><SAMP>/ssl</SAMP></CENTER>
20579 This parameter indicates that the connection to the server will be made
20580 over the SSL port, but using the TLSv1 protocol, instead of the usual
20581 SSLv3 or SSLv2 protocols.
20582 Alpine must be linked with an SSL library for this option to be operational.
20585 <CENTER><SAMP>/tls1</SAMP></CENTER>
20592 This parameter indicates that the connection to the server will be made
20593 over the SSL port, but using the DTLSv1 protocol, instead of the usual
20594 SSLv3 or SSLv2 protocols.
20595 Alpine must be linked with an SSL library for this option to be operational.
20598 <CENTER><SAMP>/dtls1</SAMP></CENTER>
20605 This parameter indicates that the connection to the server will be made
20606 over the SSL port, but using the TLSv1.1 protocol, instead of the usual
20607 SSLv3 or SSLv2 protocols.
20608 Alpine must be linked with an SSL library for this option to be operational.
20611 <CENTER><SAMP>/tls1_1</SAMP></CENTER>
20618 This parameter indicates that the connection to the server will be made
20619 over the SSL port, but using the TLSv1.2 protocol, instead of the usual
20620 SSLv3 or SSLv2 protocols.
20621 Alpine must be linked with an SSL library for this option to be operational.
20624 <CENTER><SAMP>/tls1_2</SAMP></CENTER>
20630 <DT>NoValidate-Cert</DT>
20631 <DD>Do not validate certificates (for TLS or SSL connections) from the server.
20632 This is needed if the server uses self-signed certificates or if Alpine
20633 cannot validate the certificate for some other known reason.
20638 <DD>This is a unary parameter (that means it does not have a value)
20639 indicating that the connection be logged in as
20640 "anonymous" rather than a specific user.
20641 Not all servers offer anonymous
20642 access; those which do generally only offer read-only access to certain
20643 "public" folders.
20646 <CENTER><SAMP>/anonymous</SAMP></CENTER>
20652 <DD>This is a unary parameter indicating that the connection use the
20653 most secure authentication method mutually supported by Alpine and the
20655 Alpine is capable of authenticating connections to
20656 the server using several methods.
20657 By default, Alpine will attempt each
20658 method until either a connection is established or the
20659 list of methods is exhausted.
20660 This parameter causes Alpine to instead fail
20661 the connection if the first (generally most "secure") method fails.
20664 <CENTER><SAMP>/secure</SAMP></CENTER>
20670 <DD>This is a unary parameter for use with the
20671 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A> option.
20672 It indicates that the connection should be made to the Submit server
20673 (<A HREF="http://www.ietf.org/rfc/rfc2476.txt">RFC 3676</A>)
20674 (port 587) instead of the SMTP port (25).
20675 At the time this help was written the submit option was equivalent to
20676 specifying port 587.
20679 <CENTER><SAMP>/submit</SAMP></CENTER>
20683 <CENTER><SAMP>host:587</SAMP></CENTER>
20689 <DD>This is a unary parameter indicating that the connection be established
20690 in a verbose mode. Basically, it causes Alpine to log the communication with
20691 the server in Alpine's debug file.
20692 Normally, the pine -d command-line flag would be used instead.
20697 <DD>By default, Alpine attempts to login using "rsh",
20698 the UNIX remote shell program.
20699 Including "NoRsh" will cause connections to this server to skip
20700 the "rsh" attempt.
20701 This might be useful to avoid long timeouts caused by rsh firewalls, for
20707 <DD>This option makes sense only for IMAP servers that do not perform
20708 a SEARCH command correctly. If your filtering rules
20709 fail to filter some messages, that should have been filtered, then this
20710 option will make Alpine download all data necessary data to perform that
20711 search. There is a performance penalty when using this option. Downloading
20712 the data to perfom the search will take longer than requesting the IMAP
20713 server to perform the filtering, but the filtering will be done correctly.
20719 <DD>This parameter requires an associated value. The default value is
20720 "IMAP" which indicates communication with the server based
20721 on the IMAP4rev1 protocol (defined in RFC 3501 -- see
20722 <A HREF="http://www.imap.org/docs/rfc3501.html">http://www.imap.org/docs/rfc3501.html</A>).</DD>
20724 Other service values include:
20727 <DD>This value indicates communication with the server takes place via
20728 the Network News Transfer Protocol. Use this to define a collection
20729 of newsgroups on a remote news server. So
20732 <CENTER><SAMP>/service=NNTP</SAMP></CENTER>
20736 <CENTER><SAMP>/NNTP</SAMP></CENTER>
20739 is the way to specify NNTP access.
20744 <DD>This value indicates communication with the server takes place via the
20745 Post Office Protocol 3 protocol.
20748 <CENTER><SAMP>/service=POP3</SAMP></CENTER>
20752 <CENTER><SAMP>/POP3</SAMP></CENTER>
20755 Note that there are several important issues
20756 to consider when selecting this option:
20758 <LI> POP3 provides access to only your INBOX. In other words,
20759 secondary folders such as your "saved-messages" are inaccessible.
20760 <LI> Alpine's implementation of POP3 does not follow the traditional POP
20761 model and will leave your mail on the server. Refer to the
20762 <A HREF="h_maildrop">Mail Drop</A> functionality for a possible way around this problem.
20763 <LI> See the discussion about new-mail checking in <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
20770 Note that it is possible to include more than one parameter in a server
20771 specification by concatenating the parameters. For example:
20774 <CENTER><SAMP>foo.example.com:port/user=katie/novalidate-cert/debug</SAMP></CENTER>
20778 <End of help on this topic>
20781 ======= h_composer_cntxt_server =======
20784 <TITLE>Collection Server: Explained</TITLE>
20787 <H1>Collection Edit Help -- Server Field</H1>
20789 This collection's "Server:" definition indicates the
20790 hostname of the server providing access to the folders in this
20792 The syntax of this server name is the same as for other server names used
20793 in remote folder names in
20794 Alpine and is described
20795 <A HREF="h_folder_server_syntax">here</A>.
20798 <End of help on this topic>
20801 ======= h_composer_cntxt_path =======
20804 <TITLE>Collection Path: Explained</TITLE>
20807 <H1>Collection Edit Help -- Path Field</H1>
20809 The collection's "Path:" definition indicates the location
20810 of the folders in this collection. If the path or any of its components
20811 do not exist, Alpine will prompt you for their creation when exiting the
20815 By default the path is interpreted as defining a section of your personal
20816 folder area. This area and how you specify it are defined by the
20817 server, if one is specified in the collection, or, typically, the home
20818 directory if no server is defined.
20821 To define a collection outside the default "area", prefix
20822 the path with the "namespace" to use when interpreting the
20823 given path. If a namespace is specified, the Path begins with the
20824 sharp, "#", character followed by the name of the namespace
20825 and then the namespace's path-element-delimiter. Aside from the
20826 path's format, namespaces can also imply access rights, content
20827 policy, audience, location, and, occasionally, access methods.
20830 Each server exports its own set (possibly of size one) of
20831 namespaces. Hence, it's likely communication with your server's
20832 administrator will be required for specific configurations. Some of
20833 the more common namespaces, however, include:
20837 <DD>This specifies a set of folders in the newsgroup namespace. Newsgroup
20838 names are hierarchically defined with each level delimited by a period.
20841 <DD>This specifies a folder area that the server may export to the general
20845 <DD>This specifies a folder area that the folder may export to groups
20849 <DD>This specifies a folder area that is the same as that it may have
20850 exported via the "File Transfer Protocol".
20853 <DD>This specifies the personal folder area associated with folders
20854 and directories that were created using the MH message handling system.
20859 In addition, the server may support access to other user's folders,
20860 provided you have suitable permissions. Common methods use a prefix
20861 of either "~<VAR>user</VAR>/", or "/<VAR>user</VAR>/" to
20862 indicate the root of the other user's folder area.
20865 No, nothing's simple.
20868 <End of help on this topic>
20871 ======= h_composer_cntxt_view =======
20874 <TITLE>Collection View: Explained</TITLE>
20877 <H1>Collection Edit Help -- View Field</H1>
20879 The collection's "View:" definition provides a way to limit
20880 the displayed list of folders within a collection. By default, only
20881 folders that contain the specified characters anywhere in their name
20882 are shown in the collection's folder list.
20885 Additionally, you can use a wildcard character to better control
20886 the list of folders selected for display. The wildcard specifier is
20887 the star, "*", character.
20890 So, for example, to define a collection of all folders ending with
20891 "c", you'd specify a view of "*c" (without the
20892 quote characters!). Or, similarly, to define a collection of folders
20893 whose names start with "a" and end with "z", you'd
20894 specify a view of "a*z".
20897 <End of help on this topic>
20900 ======= h_composer_abook_add_server =======
20903 <TITLE>Addressbook Server Name Field Explained</TITLE>
20906 This field should be left blank if the address book is stored in a regular
20907 file on this system. If it is a remote address book stored on an IMAP
20908 server then this is the name of that IMAP server.
20910 Look <A HREF="h_edit_nav_cmds">here</A>
20911 to see the available Editing and Navigation commands.
20913 <End of help on this topic>
20916 ======= h_composer_abook_add_folder =======
20919 <TITLE>Addressbook Folder Name Field Explained</TITLE>
20922 For a remote address book (one for which the Server Name is filled in)
20923 this is the name of a folder on the remote server. The address book data
20924 will be stored in this folder. This folder should be used only for
20925 storing this single address book, not for other address books or for
20928 For a local address book (one for which the Server Name is not filled in)
20929 this is the name of a file in which the address book will be stored.
20930 The file is in the same directory as the Alpine configuration file if the
20931 configuration file is local.
20932 If the configuration file is remote, then this will be in the home directory
20933 for Unix Alpine and in the directory specified by the
20934 "-aux local_directory" command line argument.
20936 Look <A HREF="h_edit_nav_cmds">here</A>
20937 to see the available Editing and Navigation commands.
20939 <End of help on this topic>
20942 ======= h_composer_abook_add_nick =======
20945 <TITLE>Addressbook NickName Field Explained</TITLE>
20948 This is just an optional nickname for this address book. If present, it
20949 is used in some of the displays and error messages in the address book
20950 maintenance screens. It is for your convenience only and serves no
20953 Look <A HREF="h_edit_nav_cmds">here</A>
20954 to see the available Editing and Navigation commands.
20956 <End of help on this topic>
20959 ======= h_composer_qserv_cn =======
20962 <TITLE>Directory Query Form Explained</TITLE>
20966 Fill in as many of these fields as you wish to narrow down your
20967 search. All the fields you fill in must match in order for an entry
20968 to be returned. You may use the wildcard character "*" in
20969 any of the fields, it matches any zero or more characters at that
20970 point in the string. There are no implicit wildcards, so the match is
20971 exact unless you include wildcards.
20974 Note that if an attribute isn't present at all, then the match will fail.
20975 For example, if a server doesn't support the Locality attribute, then no
20976 matter what you put in the Locality field (other than leaving it empty)
20977 the search will fail.
20980 This field, the Common Name field, is typically a person's full name.
20983 <H1>EDITING and NAVIGATION COMMANDS</H1>
20984 <!--chtml if pinemode="function_key"-->
20986 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
20987 ^B (Left Arrow) Back character | ^D Delete current character
20988 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
20989 ^P (Up Arrow) Previous line |
20990 ^N (Down Arrow) Next line | F9 Cut marked text or
20991 ^A Beginning of line | delete current line
20992 ^E End of line | F10 Undelete line(s)
20994 F8 Next page |-------------------------------------
20995 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
20996 ----------------------------------------|
20997 EXIT COMMANDS | GENERAL COMMANDS | F5 Restore previous search
20998 F2 Cancel | F1 Get help |
20999 F3 Search | ^Z Suspend | ^L Redraw Screen
21003 CURSOR MOTION KEYS----------------------|EDITING KEYS-------------------------
21004 ^B (Left Arrow) Back character | ^D Delete current character
21005 ^F (Right Arrow) Forward character | ^H (DEL) Delete previous character
21006 ^P (Up Arrow) Previous line |
21007 ^N (Down Arrow) Next line | ^K Cut marked text or
21008 ^A Beginning of line | delete current line
21009 ^E End of line | ^U Undelete line(s)
21011 ^V Next page |-------------------------------------
21012 ^@ (Ctrl-SPACE) Next word | MISCELLANEOUS COMMANDS
21013 ----------------------------------------|
21014 EXIT COMMANDS | GENERAL COMMANDS | ^R Restore previous search
21015 ^C Cancel | ^G Get help |
21016 ^X Search | ^Z Suspend | ^L Redraw Screen
21020 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21022 <End of help on this topic>
21025 ======= h_composer_qserv_sn =======
21027 The Surname is usually the family name of a person.
21029 <End of help on this topic>
21030 ======= h_composer_qserv_gn =======
21032 This is the part of a person's name that isn't the surname or initials.
21034 <End of help on this topic>
21035 ======= h_composer_qserv_mail =======
21037 This is the email address of a person.
21039 <End of help on this topic>
21040 ======= h_composer_qserv_org =======
21042 This is the organization a person belongs to.
21044 <End of help on this topic>
21045 ======= h_composer_qserv_unit =======
21047 This is the organizational unit a person belongs to.
21049 <End of help on this topic>
21050 ======= h_composer_qserv_country =======
21052 This is the country a person belongs to.
21054 <End of help on this topic>
21055 ======= h_composer_qserv_state =======
21057 This is the state a person belongs to.
21059 <End of help on this topic>
21060 ======= h_composer_qserv_locality =======
21062 This is the locality a person belongs to.
21064 <End of help on this topic>
21065 ======= h_composer_qserv_custom =======
21067 This one is for advanced users only! If you put something in this field,
21068 then the rest of the fields are ignored.
21070 This field may be set to the string representation of an LDAP search
21071 filter (see RFC1960). Here are some examples:
21073 To search for an entry with a surname equal to "clinton" you could set
21074 the custom filter to:
21078 This is equivalent to putting "clinton" in the SurName field.
21079 To search for an entry that has a surname that begins with "clint" and
21080 has a givenname equal to "william" you could use:
21082 (&(sn=clint*)(givenname=william))
21084 This is equivalent to setting the SurName field to "clint*" and the
21085 GivenName field to "william".
21086 To search for an entry where either the common name OR the email address
21087 contains "abcde" you could use:
21089 (|(cn=*abcde*)(mail=*abcde*))
21091 That isn't equivalent to anything you can do by setting the other fields
21094 <End of help on this topic>
21095 ======= h_composer_qserv_qq =======
21097 This one is a little different from the rest of the categories. It causes
21098 a search to be formed from the configured search filter that you filled
21099 in when you added the directory server to your configuration. It can also
21100 be combined with the other fields if you'd like.
21102 <End of help on this topic>
21103 ======= h_address_format =======
21106 <TITLE>INTERNET EMAIL ADDRESS FORMAT</TITLE>
21109 <H1>INTERNET EMAIL ADDRESS FORMAT</H1>
21111 A valid email address on the Internet has a username, an "@" sign,
21112 and then a domain, with no spaces.
21113 For example, jsmith@art.example.com might be the email address
21115 with the username "jsmith" who has an account in the domain
21116 "art.example.com". The number of dot-separated segments on the
21117 right of the "@" sign can vary - a shorter example would be
21118 isabelle@elsewhere.edu (the shortest possible form: here, only the
21119 organization's domain is specified after the "@" sign); a longer
21121 jsingh@shakti.edutech.example.com
21122 (here, the name of the host "shakti" in the domain
21123 edutech.example.com is also specified).
21125 If you do not know the exact email address of someone you want to write
21126 to, ask them what it is using other means of communication than email; or
21128 finding people's addresses that are available on the Internet.
21130 If you are sending to someone on the same system as you are, you can leave
21131 the "@" sign and all the information to its right off of the
21132 address, and Alpine will fill it in automatically,
21134 <A HREF="h_config_compose_rejects_unqual">"<!--#echo var="FEAT_compose-rejects-unqualified-addrs"-->"</A> is set in SETUP CONFIGURATION.
21137 When an email address you send a message to is not reachable -- either because
21138 it is simply an incorrect address, or because email can temporarily not be
21139 delivered to it due to a technical problem on the way to or at the recipient's
21140 end -- you will almost always get an error notification email message back.
21142 If you encounter problems with, or have questions about, email delivery or
21143 email address syntax, contact your local network computing consultants.
21145 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21148 <End of help on this topic>
21151 ======= h_flag_user_flag =======
21154 <TITLE>STATUS FLAG: User Defined Keyword</TITLE>
21157 <H1>STATUS FLAG: User Defined Keyword</h1>
21159 This is a keyword that is defined for this folder.
21160 It was most likely defined by the owner of the folder.
21161 Alpine will not set or clear this flag on its own.
21164 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21166 <End of help on this topic>
21169 ======= h_flag_important =======
21171 <title>STATUS FLAG: Important</title>
21173 <h1>STATUS FLAG: Important</h1>
21176 The <EM>Important</EM> flag, indicated by an asterisk in Alpine's
21178 screen, can only be set by the user, and is intended to be used in
21179 whatever fashion makes sense to you. You are the only one that can set or
21183 <End of help on this topic>
21186 ======= h_flag_new =======
21188 <title>STATUS FLAG: New</title>
21190 <h1>STATUS FLAG: New</h1>
21193 The <EM>New</EM> flag, indicated by the letter 'N' in Alpine's
21194 MESSAGE INDEX screen,
21195 is automatically set when messages are delivered to your Inbox (or other
21196 folder specified outside of Alpine). Likewise, it is cleared automatically
21197 the first time you read the message it is associated with.
21200 Sometimes it's helpful in prioritizing your mail. For example, perhaps
21201 a message isn't weighty enough to assign it an <A HREF="h_flag_important">Important</A> flag, but
21202 you'd like to be reminded of it next time you read mail. This can be done
21203 easily by <A HREF="h_common_flag">explicitly</A> resetting the <EM>New</EM> flag.
21207 <End of help on this topic>
21210 ======= h_flag_answered =======
21212 <title>STATUS FLAG: Answered</title>
21214 <h1>STATUS FLAG: Answered</h1>
21216 The <EM>Answered</EM> flag, indicated by the letter 'A' in Alpine's
21218 screen, is automatically set when you reply to a message. This flag is not
21219 automatically cleared.
21222 <End of help on this topic>
21225 ======= h_flag_forwarded =======
21227 <title>STATUS FLAG: Forwarded</title>
21229 <h1>STATUS FLAG: Forwarded</h1>
21231 The <EM>Forwarded</EM> flag, indicated by the letter 'F' in Alpine's
21233 screen, is automatically set when you forward a message. This flag is not
21234 automatically cleared.
21237 <End of help on this topic>
21240 ======= h_flag_deleted =======
21242 <title>STATUS FLAG: Deleted</title>
21244 <h1>STATUS FLAG: Deleted</h1>
21246 The <EM>Deleted</EM> flag, indicated by the letter 'D' in Alpine's
21248 screen, is set when you use the ""D Delete" command.
21250 when you use the "U Undelete" command.
21253 Messages marked with this flag will be permanently removed from
21254 the folder when you issue the <A HREF="h_index_cmd_expunge">Expunge</A>
21256 when you indicate acceptance of their removal upon leaving the folder.
21259 Note, there can be other actions implicit in the
21260 "D Delete" command,
21261 such as advancing to the next message, that may be momentarily undesirable.
21262 For this reason, it's sometimes useful to set or clear the <EM>Deleted</EM>
21263 flag <A HREF="h_common_flag">explicitly</A>.
21266 <End of help on this topic>
21269 ====== h_config_incoming_timeo ======
21272 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></TITLE>
21275 <H1>OPTION: <!--#echo var="VAR_incoming-check-timeout"--></H1>
21277 This option has no effect unless the feature
21278 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21279 is set, which in turn has no effect unless
21280 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21283 Sets the time in seconds that Alpine will
21284 attempt to open a network connection used for monitoring for Unseen
21285 messages in Incoming Folders. The default is 5.
21286 If a connection has not completed within this many seconds Alpine will
21287 give up and consider it a failed connection.
21290 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21292 <End of help on this topic>
21295 ====== h_config_psleep ======
21298 <TITLE>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</TITLE>
21301 <H1>OPTION: <!--#echo var="VAR_mailcap-check-interval"--> (UNIX Alpine only)</H1>
21304 In the good old days a mailcap viewer was used to examine an
21305 attachment before saving it, and after viewing the attachment control
21306 would return to the operating system when the viewer was closed. Therefore,
21307 when the mailcap viewer returned control to the operating system, it
21308 could be assumed that the user who opened the attachment was done
21309 examining it, and the copy of the attachment that was used, could be removed.
21312 However, today this assumption is not longer valid. Some viewers return
21313 control to the operating system before they actually read the attachment
21314 to be examined. This causes Alpine to delete the attachment before it
21315 is read by the viewer, causing the viewer to fail opening the attachment.
21318 In order to work around this problem, Alpine checks, after the viewer has
21319 returned control to the operating system, if there is any process that is
21320 using the attachment. This variable controls the number of seconds that
21321 must elapse between checks. Once it is found that no process is using the
21322 attachment, this is removed.
21325 The minimum value for this variable is 60 (checks will be made once per
21326 minute), and the maximum value is 600 (checks will be made once every 10
21327 minutes). The default value is 60.
21331 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21333 <End of help on this topic>
21336 ====== h_config_incoming_interv ======
21339 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval"--></TITLE>
21342 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval"--></H1>
21344 This option has no effect unless the feature
21345 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21346 is set, which in turn has no effect unless
21347 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21350 This option specifies, in seconds, how often Alpine will check
21351 for new mail and state changes in Incoming Folders when Incoming Folders
21352 Checking is turned on.
21353 The default is 3 minutes (180).
21354 This value applies only to folders that are local to the system that
21355 Alpine is running on or that are accessed using the IMAP protocol.
21357 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>
21358 applies to all other monitored folders.
21361 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21363 <End of help on this topic>
21366 ====== h_config_incoming_second_interv ======
21369 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></TITLE>
21372 <H1>OPTION: <!--#echo var="VAR_incoming-check-interval-secondary"--></H1>
21374 This option has no effect unless the feature
21375 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21376 is set, which in turn has no effect unless
21377 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21380 This option together with the option
21381 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21382 specifies, in seconds, how often Alpine will check
21383 for new mail and state changes in Incoming Folders when Incoming Folders
21384 Checking is turned on.
21385 The default for this option is 3 minutes (180).
21386 For folders that are local to this system or
21387 that are accessed using the IMAP protocol
21388 the value of the option
21389 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>
21391 For all other monitored folders, the value of this option is used.
21393 The reason there are two separate options is because it is usually
21394 less expensive to check local and IMAP folders than it is to check
21395 other types, like POP or NNTP folders.
21396 You may want to set this secondary value to a higher number than
21397 the primary check interval.
21400 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21402 <End of help on this topic>
21405 ====== h_config_incoming_list ======
21408 <TITLE>OPTION: <!--#echo var="VAR_incoming-check-list"--></TITLE>
21411 <H1>OPTION: <!--#echo var="VAR_incoming-check-list"--></H1>
21413 This option has no effect unless the feature
21414 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
21415 is set, which in turn has no effect unless
21416 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
21419 When monitoring the Incoming Message Folders for Unseen messages Alpine will
21420 normally monitor all Incoming Folders.
21421 You may use this option to restrict the list of monitored folders to a
21422 subset of all Incoming Folders.
21425 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21427 <End of help on this topic>
21430 ====== h_config_pers_name ======
21433 <TITLE>OPTION: <!--#echo var="VAR_personal-name"--></TITLE>
21436 <H1>OPTION: <!--#echo var="VAR_personal-name"--></H1>
21438 This value is used to determine the full name part of the "From" address
21439 on messages you send.
21440 <!--chtml if pinemode="os_windows"-->
21441 PC-Alpine requires that this be set in order to properly construct the "From" address.
21443 If unset, Unix Alpine will obtain your full name from
21444 the system password file. PC-Alpine, on the other hand, requires that this be set.
21447 If you want to change the value of what gets included in the From header
21448 in messages you send (other than just the Personal Name)
21449 look <A HREF="h_config_change_your_from">here</A> for a description.
21451 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21453 <End of help on this topic>
21456 ====== h_config_pruned_folders ======
21459 <title>OPTION: <!--#echo var="VAR_pruned-folders"--></title>
21462 <h1>OPTION: <!--#echo var="VAR_pruned-folders"--></h1>
21464 This variable allows you to define a list of one or more folders that
21465 Alpine will offer to prune for you in the same way it automatically offers
21466 to prune your "sent-mail" folder each month.
21467 Each folder in this list must be a folder in your default folder collection
21468 (the first folder collection if you have more than one), and it is just
21469 the relative name of the folder in the collection, not the fully-qualified name.
21470 It is similar to sent-mail.
21471 Instead of something like
21473 <CENTER><SAMP><!--#echo var="VAR_pruned-folders"-->={servername}mail/folder</SAMP></CENTER>
21475 the correct value to use would be
21477 <CENTER><SAMP>folder</SAMP></CENTER>
21479 There is an assumption here that your first collection is the folders in
21481 <CENTER><SAMP>{servername}mail</SAMP></CENTER>
21484 Once a month, for each folder listed, Alpine will offer to move
21485 the contents of the folder to a new folder of the same name but with
21486 the previous month's date appended. Alpine will then look for any such
21487 date-appended folder names created for a previous month, and offer each
21488 one it finds for deletion.
21491 If you decline the first offer, no mail is moved and no new folder is
21495 The new folders will be created
21496 in your default folder collection.
21500 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21502 <End of help on this topic>
21505 ====== h_config_upload_cmd ======
21508 <TITLE>OPTION: <!--#echo var="VAR_upload-command"--></TITLE>
21511 <H1>OPTION: <!--#echo var="VAR_upload-command"--></H1>
21513 This option affects the behavior of the Composer's "Read File"
21514 (^R in the message body) and "Attach File" (^J in the header)
21515 commands. It specifies
21516 a Unix program name, and any necessary command line arguments, that Alpine can
21517 use to transfer files from your personal computer into messages that you are
21520 <B>Note:</B> this facility is intended for use with serial line transfer
21521 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21522 to work with TCP/IP file transfer programs such as ftp.<P>
21524 If a program is specified, the commands listed above are modified to offer a
21525 subcommand (^Y) to activate the transfer. Obviously, the Unix program
21526 specified here must match the transfer program or protocol available on the
21527 personal computer.<P>
21529 Alpine expects to exchange uploaded data via a file on your Unix system. When
21530 the specified upload program finishes, Alpine expects the uploaded data to be
21531 contained in this file.<P>
21533 When upload is invoked via the "Read File" subcommand, Alpine
21535 temporary file name that it will pass to the specified Unix program. Alpine
21536 will read the resulting uploaded text from this file and then delete it when
21537 the upload command is finished.<P>
21539 When upload is invoked via the "Attach File" subcommand, Alpine will
21541 you for the name of the file that is to contain the uploaded information that
21542 it is to attach. Alpine will attach this file to the composition, but will
21543 <B>not</B> delete this file after the upload command is finished.<P>
21545 The special token "_FILE_" may be included among the Unix program's
21547 line arguments. Alpine will replace this symbol with the name of the file
21548 being used to exchange the uploaded information. This token allows you to
21549 position the file name where it is required in the Unix program's command
21552 If the "_FILE_" token is not present in the specified command, the
21553 temporary file's name is automatically appended to the specified Unix
21554 program. In other words, you don't need to use "_FILE_" if it is the
21555 <B>last</B> command line argument.
21557 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21559 <End of help on this topic>
21562 ====== h_config_upload_prefix ======
21565 <TITLE>OPTION: <!--#echo var="VAR_upload-command-prefix"--></TITLE>
21568 <H1>OPTION: <!--#echo var="VAR_upload-command-prefix"--></H1>
21570 This option is used in conjunction with the <!--#echo var="VAR_upload-command"--> option.
21571 It defines text to be written to the terminal emulator (via standard output)
21572 immediately prior to starting upload command. This is useful for
21573 integrated serial line file transfer agents that permit command passing
21574 (e.g., Kermit's APC method).<P>
21576 The special token "_FILE_" may be included in the string specification.
21577 That symbol will be replaced with the (Alpine-created) name of the temporary
21578 file in which Alpine will expect to find the uploaded file.
21580 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21582 <End of help on this topic>
21585 ====== h_config_download_cmd ======
21588 <TITLE>OPTION: <!--#echo var="VAR_download-command"--></TITLE>
21591 <H1>OPTION: <!--#echo var="VAR_download-command"--></H1>
21593 This option affects the behavior of the Export command. It specifies a Unix
21594 program name, and any necessary command line arguments, that Alpine can use to
21595 transfer the exported message to your personal computer's disk.<P>
21596 Note: this facility is intended for use with serial line transfer
21597 protocols, such as kermit, xmodem, or zmodem. It is <B>not</B> intended
21598 to work with TCP/IP file transfer programs such as ftp.<P>
21599 If a program is specified, the Export command is modified to offer a
21600 subcommand (^V) to activate the transfer (in lieu of saving it to
21601 the machine where Alpine is running). Obviously, the Unix program
21602 specified here must match the transfer program or protocol available on the
21603 personal computer.<P>
21605 When this subcommand is selected and before Alpine invokes the specified Unix
21606 program, Alpine will create a temporary file containing the text of the
21607 exported message. Alpine uses this file to pass the exported message text to
21608 the specified Unix program.<P>
21610 The special token "_FILE_" may be included among the Unix program's command
21611 line arguments. Alpine will replace this symbol with the temporary file's name
21612 before executing the Unix program. This token allows you to position the
21613 file name where it is required in the Unix program's command line arguments.
21615 If the "_FILE_" token is not present in the specified command, the
21616 temporary file's name is automatically appended to the specified Unix
21617 program. In other words, you don't need to use "_FILE_" if it is the
21618 <B>last</B> command line argument.
21620 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21622 <End of help on this topic>
21625 ====== h_config_download_prefix ======
21628 <TITLE>OPTION: <!--#echo var="VAR_download-command-prefix"--></TITLE>
21631 <H1>OPTION: <!--#echo var="VAR_download-command-prefix"--></H1>
21633 This option is used in conjunction with the <!--#echo var="VAR_download-command"--> option.
21634 It defines text to be written to the terminal emulator (via standard output)
21635 immediately prior to starting the download command. This is useful for
21636 integrated serial line file transfer agents that permit command passing
21637 (e.g., Kermit's APC method).
21639 The special token "_FILE_" may be included in the string
21641 That symbol will be replaced with the (Alpine-created) name of the temporary
21642 file into which Alpine will place the message to be downloaded.
21644 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21646 <End of help on this topic>
21649 ====== h_config_mailcap_path ======
21652 <TITLE>OPTION: <!--#echo var="VAR_mailcap-search-path"--></TITLE>
21655 <H1>OPTION: <!--#echo var="VAR_mailcap-search-path"--></H1>
21656 This variable is used to replace Alpine's default mailcap file search path.
21657 It takes one or more file names (full paths must be specified) in which to
21658 look for mail capability data. The default search path can be found in this
21659 <A HREF="h_news_config">Alpine Configuration</A> help, near the bottom.
21660 If there is more than one file name listed, list members should be delimited
21662 <!--chtml if pinemode="os_windows"-->
21663 a semi-colon (;) under Windows; for example:<PRE>
21664 C:\MYCONFIG\MAILCAP.TXT;H:\NETCONFIG\MAILCAP.TXT
21667 a colon (:) under UNIX; for example:<PRE>
21668 ~/.mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap
21672 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21675 <End of help on this topic>
21678 ====== h_config_mimetype_path ======
21681 <TITLE>OPTION: <!--#echo var="VAR_mimetype-search-path"--></TITLE>
21684 <H1>OPTION: <!--#echo var="VAR_mimetype-search-path"--></H1>
21686 This variable is used to replace Alpine's default mime.types file search path.
21687 It takes one or more file names (full paths must be specified) in which to
21688 look for file-name-extension to MIME type mapping data. The default search
21689 path can be found in this
21690 <A HREF="h_news_config">Alpine Configuration</A> help.
21694 If there is more than one file name listed, list members should be delimited
21695 by a colon (:) under UNIX and a semi-colon (;) under Windows.
21697 <End of help on this topic>
21699 ====== h_config_set_att_ansi ======
21701 <TITLE>OPTION: Set printer to attached ansi printer</TITLE>
21704 <H1>OPTION: Set printer to attached ansi printer</H1>
21706 Type "S" to set your printer to "attached-to-ansi".<BR>
21707 It is OK to include "attached-to-ansi" in your personal list below.
21709 <End of help on this topic>
21711 ====== h_config_set_att_ansi2 ======
21713 <TITLE>OPTION: Set printer to attached ansi printer (no formfeed)</TITLE>
21716 <H1>OPTION: Set printer to attached ansi printer (no formfeed)</H1>
21718 Type "S" to set your printer to "attached-to-ansi-no-formfeed".<BR>
21719 It is OK to include "attached-to-ansi-no-formfeed" in your personal
21724 This is the same as the "attached-to-ansi" option except that a
21725 formfeed character will not be appended to the end of the print job.
21726 If your printer already ejects the paper by itself at the end of the
21727 job, you may prefer the "no-formfeed" form of this printer so that you
21728 don't get an extra blank page between print jobs.
21731 <End of help on this topic>
21733 ====== h_config_set_att_wyse ======
21735 <TITLE>OPTION: Set printer to attached Wyse60 printer</TITLE>
21738 <H1>OPTION: Set printer to attached Wyse60 printer</H1>
21740 Type "S" to set your printer to "attached-to-wyse".<BR>
21741 It is OK to include "attached-to-wyse" in your personal list below.
21743 This is very similar to "attached-to-ansi".
21744 The only difference is in the control characters sent to turn the printer
21746 The ansi version of the printer uses ESC LEFT_BRACKET 5 i
21747 to turn on the printer and ESC LEFT_BRACKET 4 i
21749 The Wyse version uses Ctrl-R for on, and Ctrl-T for off.
21750 <End of help on this topic>
21752 ====== h_config_set_att_wyse2 ======
21754 <TITLE>OPTION: Set printer to attached Wyse60 printer (no formfeed)</TITLE>
21757 <H1>OPTION: Set printer to attached Wyse60 printer (no formfeed)</H1>
21759 Type "S" to set your printer to "attached-to-wyse-no-formfeed".<BR>
21760 It is OK to include "attached-to-wyse-no-formfeed" in your personal
21765 This is the same as the "attached-to-wyse" option except that a
21766 formfeed character will not be appended to the end of the print job.
21767 If your printer already ejects the paper by itself at the end of the
21768 job, you may prefer the "no-formfeed" form of this printer so that you
21769 don't get an extra blank page between print jobs.
21772 <End of help on this topic>
21774 ====== h_config_set_stand_print ======
21777 <TITLE>OPTION: Set default printer</TITLE>
21779 <H1>OPTION: Set default printer</H1>
21781 Move to the printer you want and type "S" to set it to be your
21782 default printer. This list is not modifiable by you and has been
21783 set up by the system administrators. If there is more than one printer
21784 listed in the Command List, you will be able to cycle through that
21785 whole list at the time you print, starting with your default.
21786 It is OK to include entries from this Standard list in your personal
21789 <End of help on this topic>
21792 ====== h_config_set_custom_print ======
21795 <TITLE>OPTION: Set default printer</TITLE>
21797 <H1>OPTION: Set default printer</H1>
21799 You may add as many print commands as you want to your personal list.
21800 Specify one of them as your default printer by moving to the printer
21801 you want and typing "S". If there is more than one printer listed
21802 in the Command List, you will be able to cycle through that list at
21803 the time you print, starting with your default. It is OK to include
21804 entries from the Standard list above or to include the command
21805 "attached-to-ansi", "attached-to-ansi-no-formfeed", "attached-to-wyse", or
21806 "attached-to-wyse-no-formfeed" as one of the entries here.
21808 <End of help on this topic>
21811 ====== h_config_user_id =====
21814 <TITLE>OPTION: <!--#echo var="VAR_user-id"--></TITLE>
21817 <H1>OPTION: <!--#echo var="VAR_user-id"--></H1>
21819 This value is used as part of the "From" address on messages you send.
21820 It is also the default login name for remote IMAP server access. Set this
21821 to the username part you want to appear on outgoing email.
21823 If you want to change the value of what gets included in the From header
21824 in messages you send (other than just the User ID)
21825 look <A HREF="h_config_change_your_from">here</A> for a description.
21828 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21830 <End of help on this topic>
21833 ====== h_config_user_dom =====
21836 <TITLE>OPTION: <!--#echo var="VAR_user-domain"--></TITLE>
21839 <H1>OPTION: <!--#echo var="VAR_user-domain"--></H1>
21841 This value specifies the domain part (right-hand side) of your return
21842 address on outgoing email and is also used as the default domain for email
21843 composed to a local user.
21844 <!--chtml if pinemode="os_windows"-->
21845 This value is required for PC-Alpine. If you are unsure as to what this should be,
21846 contact your local help desk, system administrator, or Internet Service Provider.
21848 If unset, Unix Alpine will obtain the domain from
21849 the system. Often this value will be set for your whole site by the
21850 system administrator.<P>
21852 If you set this, see also the <A HREF="h_config_quell_local_lookup">
21853 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
21855 If you want to change the value of what gets included in the From header
21856 in messages you send (other than just the User Domain)
21857 look <A HREF="h_config_change_your_from">here</A> for a description.
21859 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21861 <End of help on this topic>
21864 ====== h_config_smtp_server =====
21867 <TITLE>OPTION: <!--#echo var="VAR_smtp-server"--></TITLE>
21870 <H1>OPTION: <!--#echo var="VAR_smtp-server"--></H1>
21871 This value specifies the name of one or more SMTP
21872 (Simple Mail Transfer Protocol) servers for sending mail.
21873 <!--chtml if pinemode="os_windows"-->
21874 You must have an SMTP server for use with PC-Alpine.
21876 normally set up by a system administrator for use by all members of a given
21877 campus or department.
21878 Contact your local help desk to ask what SMTP
21879 servers you should use.
21881 Unix Alpine users may not need to set an SMTP server.
21882 Alpine will attempt to execute the program (usually sendmail) that is used
21883 to insert mail into the mail system.
21884 If this works for you, you may leave this option blank.
21885 If there is an SMTP server running on the Unix host you may be able to
21886 improve sending performance slightly by setting the SMTP server option
21887 to "localhost" or to the actual name of the Unix host.
21889 If the Unix host doesn't work the way Alpine was expecting you will need to
21890 set the value of this option.
21892 normally set up by a system administrator for use by all members of a given
21893 campus or department.
21894 Contact your local help desk to ask what SMTP
21895 servers you should use.
21898 Your SMTP server may offer SMTP AUTH authentication.
21899 It may even require it.
21900 If your SMTP server offers SMTP AUTH authentication you may specify a
21901 "user" name parameter to cause Alpine to attempt to authenticate.
21902 This parameter requires an associated value,
21903 the username identifier with which to establish the server
21905 An example might be:
21908 <CENTER><SAMP>smtpserver.example.com/user=katie</SAMP></CENTER>
21911 If AUTH authentication is offered by the server, this will cause Alpine to
21913 If AUTH authentication is not offered by the server, this will cause Alpine
21914 to fail sending with an error similar to:
21917 <CENTER><SAMP>Error: SMTP authentication not available</SAMP></CENTER>
21920 Another type of authentication that is used by some ISPs is called
21921 "POP before SMTP" or "IMAP before SMTP",
21922 which means that you have to authenticate
21923 yourself to the POP or IMAP server by opening a mailbox before you
21925 To do this, you usually only have to open your INBOX.
21928 You may tell Alpine to use the
21929 <A HREF="http://www.ietf.org/rfc/rfc2476.txt">Message Submission</A>
21930 port (587) instead of the SMTP port (25) by including the "submit"
21933 At this time "/submit" is simply equivalent to specifying
21934 port 587, though it may imply more than that at some point in the future.
21935 Some ISPs are blocking port 25 in order to reduce the amount of spam
21936 being sent to their users.
21937 You may find that the submit option allows you to get around such a block.
21940 <CENTER><SAMP>smtpserver.example.com/submit</SAMP></CENTER>
21943 To specify any non-standard port number on the SMTP server you may follow
21944 the hostname with a colon followed by the portnumber.
21947 <CENTER><SAMP>smtpserver.example.com:12345</SAMP></CENTER>
21950 Normally, when a connection is made to the Smtp-Server Alpine will attempt
21951 to negotiate a secure (encrypted) session using Transport Layer Security (TLS).
21952 If that fails then a non-encrypted connection will be attempted instead.
21953 You may specify that a TLS connection is required if you wish.
21954 If you append "/tls" to the name then the connection will fail
21955 instead of falling back to a non-secure connection.
21958 <CENTER><SAMP>smtpserver.example.com/tls</SAMP></CENTER>
21962 For more details about server name possibilities see
21963 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
21967 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
21970 <End of help on this topic>
21973 ====== h_config_nntp_server =====
21976 <TITLE>OPTION: <!--#echo var="VAR_nntp-server"--></TITLE></HEAD>
21978 <H1>OPTION: <!--#echo var="VAR_nntp-server"--></H1>
21980 This value specifies the name of one or more NNTP
21981 (Network News Transfer Protocol)
21982 servers for reading and posting USENET news.
21983 NNTP servers are normally
21984 set up by a system administrator for use by all members of a given campus
21986 Contact your local help desk to ask what NNTP servers you should use.
21987 <!--chtml if pinemode="os_windows"--><!--chtml else-->
21988 Often Unix Alpine users will find that this variable has been
21989 set for the whole system (and they don't have to worry about it).
21991 When you define an NNTP server here, Alpine implicitly defines a news
21992 collection for you, assuming that server as the news server and assuming
21993 that you will use the NNTP protocol and a local newsrc configuration file
21995 For more about reading news with Alpine, see
21996 <A HREF="h_reading_news">how to use Alpine to read news</A>.
21998 Your NNTP server may offer NNTP "AUTHINFO SASL"
21999 or "AUTHINFO USER" authentication.
22000 It may even require it.
22001 If your NNTP server does offer such authentication you may specify a user name
22002 parameter to cause Alpine to attempt to authenticate.
22003 The same is true for the server name in a folder collection that uses NNTP.
22004 This parameter requires an associated value,
22005 the username identifier with which to establish the server connection.
22006 An example might be:
22009 <CENTER><SAMP>nntpserver.example.com/user=katie</SAMP></CENTER>
22012 If authentication is offered by the server, this will cause Alpine to
22014 If authentication is not offered by the server, this will cause Alpine
22015 to fail with an error similar to:
22018 <CENTER><SAMP>Error: NNTP authentication not available</SAMP></CENTER>
22020 For more details about the server name possibilities see
22021 <A HREF="h_folder_server_syntax">Server Name Syntax</A>.
22023 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22025 <End of help on this topic>
22028 ====== h_config_inbox_path =====
22031 <TITLE>OPTION: <!--#echo var="VAR_inbox-path"--></TITLE>
22034 <H1>OPTION: <!--#echo var="VAR_inbox-path"--></H1>
22036 This value overrides the default value of your INBOX name/path/location.
22037 <!--chtml if pinemode="os_windows"-->
22038 PC-Alpine users must specify an inbox path and it must be a folder on an
22041 Unix and VMS Alpine users will often find that this variable
22042 has been pre-configured by your system administrator.
22044 You may be able to specify an alternate INBOX that is either a local folder
22045 or a folder on an IMAP server.
22047 A typical remote <!--#echo var="VAR_inbox-path"--> entry would be: {monet.art.example.com}INBOX
22048 where "monet.art.example.com" is replaced by the name of your IMAP
22051 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22052 details on the syntax of folder definitions.
22054 See <A HREF="h_info_on_mbox">Missing mail and the mbox driver</A> if your
22055 mail is disappearing.
22057 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22059 <End of help on this topic>
22062 ====== h_config_change_your_from =====
22065 <TITLE>How to Change your From Address</TITLE>
22068 <H1>How to Change your From Address</H1>
22070 If the From address that Alpine includes in mail that you send is not correct,
22071 you may want to configure a different default value for the From address.
22072 You may follow these directions to change the default:
22076 <LI> Go to the Main Alpine Menu
22077 <LI> From there type the Setup Command
22078 <LI> From there type the Config Command
22082 You've probably already seen this SETUP CONFIGURATION screen.
22083 If not, there are many options you may want to set here.
22084 To set the value of the From header you may use the
22085 <A href="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A> option.
22086 Find it by scrolling down a few pages or use the WhereIs command to
22087 search for "customized".
22088 You may want to read the help text associated with the option.
22090 To add a custom From header, type the Add command and enter the
22091 full header line, including the leading "From: ".
22094 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22096 Now exit the Setup command and try sending mail to yourself to see
22097 what the From line looks like.
22099 When you are in the composer you may edit the custom From line by typing
22100 Ctrl-R while your cursor is in the headers of the message and then moving
22101 to the From line and editing.
22102 If you want to leave the default value the same but add the possibility
22103 of being able to edit the header when you compose, add just the header
22104 name without a value.
22107 <CENTER><SAMP>From:</SAMP></CENTER>
22109 If you change your From address you may also find it useful to add the
22110 changed From address to the
22111 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22112 configuration option.
22115 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22117 <End of help on this topic>
22120 ====== h_config_default_fcc =====
22123 <TITLE>OPTION: <!--#echo var="VAR_default-fcc"--></TITLE>
22126 <H1>OPTION: <!--#echo var="VAR_default-fcc"--></H1>
22128 This value specifies where a copy of outgoing mail should be saved. If
22129 this is not a path name, it will be in the default collection for saves.
22130 Any valid folder specification, local or IMAP, is allowed. This default
22131 folder carbon copy only applies when the
22132 <A HREF="h_config_fcc_rule">"<!--#echo var="VAR_fcc-name-rule"-->"</A>
22133 is set to use the default folder.
22134 <!--chtml if pinemode="os_windows"-->
22135 PC-Alpine default is "SENTMAIL" (normally stored as SENTMAIL.MTX)
22137 Unix Alpine default
22138 is normally "sent-mail" in the default folder collection.
22141 If you access your email through an IMAP server, especially if you often switch between Unix Alpine
22142 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on your
22143 IMAP server (remember that in order to later access this remote folder through Alpine, it
22144 must be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
22145 for more information). An example:<p>
22146 <CENTER><SAMP>{monet.art.example.com}mail/sent-mail</SAMP></CENTER>
22148 To suppress saving of outgoing mail, set: <!--#echo var="VAR_default-fcc"-->=""
22150 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22151 details on the syntax of folder definitions.
22154 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22156 <End of help on this topic>
22159 ====== h_config_def_save_folder =====
22162 <TITLE>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></TITLE>
22165 <H1>OPTION: <!--#echo var="VAR_default-saved-msg-folder"--></H1>
22167 This option determines the default folder name for save-message operations
22168 ("saves").
22170 If this is not a path name, it will be in the default collection for saves.
22171 Any valid folder specification, local or IMAP, is allowed. This default
22172 folder only applies when the
22173 <A HREF="h_config_saved_msg_name_rule">"<!--#echo var="VAR_saved-msg-name-rule"-->"</A>
22174 doesn't override it.
22175 <!--chtml if pinemode="os_windows"-->
22176 PC-Alpine default is "SAVEMAIL" (normally stored as SAVEMAIL.MTX).
22178 Unix Alpine default
22179 is normally "saved-messages" in the default folder collection.
22181 If you access your email through an IMAP server, especially if you often switch between Unix
22182 and PC-Alpine, or between various desktop email systems, you may want to set this to a folder on an
22183 IMAP server (remember that in order to later access this remote folder through Alpine, it
22184 should be in a folder collection. See <A HREF="h_what_are_collections">Folder Collections Explained</a>
22185 for more information). An example:<p>
22186 <CENTER><SAMP>{monet.art.example.com}mail/saved-messages</SAMP></CENTER>
22188 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22189 details on the syntax of folder definitions.
22192 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22194 <End of help on this topic>
22197 ====== h_config_postponed_folder =====
22200 <TITLE>OPTION: <!--#echo var="VAR_postponed-folder"--></TITLE>
22203 <H1>OPTION: <!--#echo var="VAR_postponed-folder"--></H1>
22205 This value overrides the default name for the folder where postponed
22206 messages are saved. If this is not a path name, it will be in the default
22207 collection for message Saves. Any valid folder specification, local or
22208 remote, is allowed.
22210 is "POSTPOND" (stored as POSTPOND.MTX).
22211 The Unix Alpine default is normally "postponed-msgs"
22212 in the default collection.
22214 Tip: If you are using different installations of (PC-)Alpine -- for example, PC-Alpine on your personal
22215 computer at home, and Unix Alpine on campus -- you can postpone a composition begun with one Alpine and
22216 resume it later with the other if you set this option to the <B>same folder on the same IMAP host</B>
22217 in all Alpine copies you use.
22218 (Remember that in order to later access this remote folder through Alpine, it must be in a folder
22219 collection. See <A HREF="h_what_are_collections">Folder Collections Extensions Explained</a>
22220 for more information). An
22222 <CENTER><SAMP>{monet.art.example.com}mail/postponed-msgs</SAMP></CENTER>
22224 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22225 details on the syntax of folder definitions.
22228 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22230 <End of help on this topic>
22233 ====== h_config_read_message_folder =====
22236 <TITLE>OPTION: <!--#echo var="VAR_read-message-folder"--></TITLE>
22239 <H1>OPTION: <!--#echo var="VAR_read-message-folder"--></H1>
22241 By virtue of specifying a folder name here, Alpine will be configured to
22242 save all messages that you have read during a session into the designated
22243 "read messages" folder. This allows you to more easily distinguish
22244 between your really new email (in your INBOX) and those that you have
22245 already read. Depending on how you define the
22246 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22247 setting, you may or may not be asked when you quit
22248 Alpine if you want read messages to be moved to this folder. In either
22249 case, moving the messages means they will be deleted from your INBOX.
22251 If this is not a path name, it will be in the default collection for
22252 saves. Any valid folder specification, local or remote (via IMAP), is
22253 allowed. There is no default for the name of the read message folder.
22255 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22256 details on the syntax of folder definitions.
22259 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22261 <End of help on this topic>
22264 ====== h_config_form_folder =====
22267 <TITLE>OPTION: <!--#echo var="VAR_form-letter-folder"--></TITLE>
22270 <H1>OPTION: <!--#echo var="VAR_form-letter-folder"--></H1>
22272 A "<!--#echo var="VAR_form-letter-folder"-->" is a mail folder that is intended to
22273 contain messages that you have composed and that are intended to be
22274 sent in their original form repeatedly.
22277 Setting this variable will alter Alpine's usual behavior when you
22278 execute the Compose command. Normally, Alpine offers a chance to
22279 continue a postponed or interrupted message should one or the other
22280 exist. When this variable is set to a folder name that exists, Alpine
22281 will also offer the chance to select a message from the folder to
22282 insert into the composer (much like when continuing a postponed message).
22283 The difference, however, is that Alpine will not automatically delete
22284 the selected message from the Form Letter Folder.
22286 Setting this variable will also affect Alpine's behavior when you
22287 Postpone a message from the composer. Normally, Alpine simply stashes
22288 the message away in your
22289 "<A HREF="h_config_postponed_folder"><!--#echo var="VAR_postponed-folder"--></A>".
22290 Regardless of the specified folder's existence, Alpine will ask which
22291 folder you intend the message to be stored in. Choose the
22292 "F" option to store the message in your Form Letter Folder.
22293 This is the most common way to add a message to the folder.
22296 Another method of adding messages to the folder is via the Alpine
22297 composer's <SAMP>Fcc:</SAMP> field. If you are sending a message that
22298 you expect to send in the same form again, you can enter the Form
22299 Letter Folder's name in this field. Alpine, as usual, will copy the
22300 message as it's sent. Note, when you later select this message from
22301 your Form Letter Folder, it will have the same recipients as the original
22305 To delete a message from the Form Letter Folder, you can either select
22306 the folder from a suitable FOLDER LIST screen, or use the Delete
22307 command in the MESSAGE INDEX offered when selecting from the folder as
22308 part of the Compose command. You can delete a Form Letter Folder just
22309 as any other folder from a suitable FOLDER LIST screen.
22312 You may find that the <A HREF="h_rules_roles">"Roles"</A>
22313 facility can be used
22314 to replace the Form Letter Folder.
22317 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22318 details on the syntax of folder definitions.
22322 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22324 <End of help on this topic>
22327 ====== h_config_archived_folders =====
22330 <TITLE>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></TITLE>
22333 <H1>OPTION: <!--#echo var="VAR_incoming-archive-folders"--></H1>
22336 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>,
22337 only more general. You may archive
22338 any of the folders in your incoming collection. This is a list of folder
22339 pairs, with the first separated from the second in the pair by a space.
22340 The first folder in a pair is the folder you want to archive, and the
22341 second folder is the folder that read messages from the first should be
22342 moved to. Depending on how you define the
22343 <A HREF="h_config_auto_read_msgs">"auto-move-read-messages"</A>
22344 setting, you may or may not be asked when you
22345 leave the first folder if you want read messages to be moved to the
22346 second folder. In either case, moving the messages means they will be
22347 deleted from the first folder.
22349 The name of the first folder in each pair can be either the technical
22350 specification of the folder (like what appears in your configuration file)
22351 or (much easier) the nickname that you gave the folder when you made it
22352 an incoming folder.
22355 <CENTER><SAMP>{monet.art.example.com}inbox {monet.art.example.com}mail/inbox-archive</SAMP></CENTER>
22356 <p>or, using nicknames:<p>
22357 <CENTER><SAMP>inbox inbox-archive</SAMP></CENTER>
22359 If these are not path names, they will be in the default collection for
22360 saves. Any valid folder specification, local or remote (via IMAP), is
22361 allowed. There is no default.
22363 See the section on <A HREF="h_valid_folder_names">Valid Folder Names</A> for
22364 details on the syntax of folder definitions.
22367 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22369 <End of help on this topic>
22372 ====== h_config_newsrc_path ======
22375 <TITLE>OPTION: <!--#echo var="VAR_newsrc-path"--></TITLE>
22378 <H1>OPTION: <!--#echo var="VAR_newsrc-path"--></H1>
22380 This option overrides the default name Alpine uses for your "newsrc" news
22381 status and subscription file. If set, Alpine will take this value as the
22382 full pathname for the desired newsrc file.<P>
22384 If this option is <B>not</B> set,
22385 <!--chtml if pinemode="os_windows"-->
22386 PC-Alpine looks first for $HOME\NEWSRC (where $HOME defaults to the root
22387 of the current drive, e.g. "C:\") and then it looks in the same
22388 directory as your pinerc file for NEWSRC.
22390 Unix Alpine looks for the file ~/.newsrc (that is, the file named .newsrc in
22391 your account's home directory).
22394 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22397 <End of help on this topic>
22400 ====== h_config_literal_sig =====
22403 <TITLE>OPTION: <!--#echo var="VAR_literal-signature"--></TITLE>
22406 <H1>OPTION: <!--#echo var="VAR_literal-signature"--></H1>
22408 With this option your actual signature, as opposed to
22409 the name of a file containing your signature,
22410 is stored in the Alpine configuration file.
22411 If this is defined it takes precedence over the <!--#echo var="VAR_signature-file"--> option.
22414 This is simply a different way to store the signature.
22415 The signature is stored inside your Alpine configuration file instead of in
22417 Tokens work the same way they do with the
22418 <A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A> so look there for
22422 The Setup/Signature command on Alpine's MAIN MENU will edit
22423 the "<!--#echo var="VAR_literal-signature"-->" by default. However, if no
22424 "<!--#echo var="VAR_literal-signature"-->" is defined and the file named in the
22425 "<!--#echo var="VAR_signature-file"-->" option exists, then the latter will be used
22429 The two character sequence \n (backslash followed by
22430 the character n) will be used to signify a line-break in your signature.
22431 You don't have to enter the \n, but it will be visible in the
22432 SETUP CONFIGURATION window after you are done editing the signature.
22436 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22438 <End of help on this topic>
22441 ====== h_config_signature_file =====
22444 <TITLE>OPTION: <!--#echo var="VAR_signature-file"--></TITLE>
22447 <H1>OPTION: <!--#echo var="VAR_signature-file"--></H1>
22449 If a <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> option is defined,
22450 then this "<!--#echo var="VAR_signature-file"-->" option will be ignored.
22451 You can tell that that is the case because the value of the
22452 "<!--#echo var="VAR_signature-file"-->" will show up as
22454 <CENTER><SAMP><Ignored: using <!--#echo var="VAR_literal-signature"--> instead></SAMP></CENTER>
22456 You may either use all Literal Signatures (signatures stored in your
22457 configuration file) throughout Alpine, or all signature files.
22458 You can't mix the two.
22460 This is the name of a file that will be automatically inserted into
22462 It typically contains information such as your
22463 name, email address and organizational affiliation.
22465 signature into the message as soon as you enter the composer so you
22466 can choose to remove it or edit it on a message by message basis.
22467 Signature file placement in message replies is controlled by the
22468 "<A HREF="h_config_sig_at_bottom"><!--#echo var="FEAT_signature-at-bottom"--></A>"
22469 setting in the feature list.
22472 The default file name is
22473 <!--chtml if pinemode="os_windows"-->
22474 "PINE.SIG" in the same directory as your PINERC file if your
22475 PINERC file is a local file.
22476 If your PINERC file is remote, then it will be in the directory specified
22477 by the "-aux local_directory" command line option.
22479 ".signature".
22483 To create or edit your signature file choose Setup from the MAIN MENU
22484 and then select S for Signature (Main/Setup/Signature). This puts you
22485 into the Signature Editor where you can enter a <EM>few</EM> lines of
22486 text containing your identity and affiliation.
22489 If the filename is followed by a vertical bar (|) then instead
22490 of reading the contents of the file the file is assumed to be a
22491 program that will produce the text to be used on its standard output.
22492 The program can't have any arguments and doesn't receive any input from Alpine,
22493 but the rest of the processing works as if the contents came from a file.
22496 Instead of storing the data in a local file, the
22497 signature data may be stored remotely in an IMAP folder.
22498 In order to do this,
22499 you must use a remote name for the file.
22500 A remote <!--#echo var="VAR_signature-file"--> name might look like:
22502 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/signature</SAMP></CENTER>
22505 The syntax used here is the same as the syntax used for remote configuration
22506 files from the command line.
22507 Note that you may not access an existing signature file remotely,
22508 you have to create a new <EM>folder</EM> that contains the signature data.
22509 If the name you use here for the signature file is a remote name, then when
22510 you edit the file from the Setup/Signature command the data will be stored
22511 remotely in the folder.
22512 You aren't required to do anything special to create the folder, it
22513 gets created automatically if you use a remote name.
22516 Besides regular text, the signature file may also contain
22517 (or a signature program may produce) tokens that
22518 are replaced with text that usually depends on the message you are replying
22520 For example, if the signature file contains the token
22522 <CENTER><SAMP>_DATE_</SAMP></CENTER>
22524 anywhere in the text, then that token is replaced by the date
22525 the message you are replying to or forwarding was sent.
22528 <CENTER><SAMP>_CURDATE_</SAMP></CENTER>
22530 that is replaced with the current date.
22531 The first is an example of a token that depends on the message you
22532 are replying to (or forwarding) and the second is an example which
22533 doesn't depend on anything other than the current date.
22534 You have to be a little careful with this facility since tokens that
22535 depend on the message you are replying to or forwarding will be replaced
22536 by nothing in the case where you are composing a new message from scratch.
22537 The use of <A HREF="h_rules_roles">"roles"</A> may help you
22539 It allows you to use different signature files in different cases.
22542 The list of tokens available for use in the signature file is
22543 <A HREF="h_index_tokens">here</A>.
22546 Instead of, or along with the use of "roles" to give you
22547 different signature files in different situations, there is also
22548 a way to conditionally include text based
22549 on whether or not a token would result in specific replacement text.
22550 For example, you could include some text based on whether or not
22551 the _NEWS_ token would result in any newsgroups if it was used.
22552 This is explained in detail
22553 <A HREF="h_reply_token_conditionals">here</A>.
22554 This isn't for the faint of heart.
22556 In the very unlikely event that you want to include a literal token
22557 in the signature you must precede it with a backslash character.
22560 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
22562 would produce something like
22564 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
22566 It is not possible to have a literal backslash followed by an expanded token.
22568 An alternate method for storing the signature data is available by using the
22569 <A HREF="h_config_literal_sig"><!--#echo var="VAR_literal-signature"--></A> configuration option.
22570 This variable will be used by default.
22573 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22575 <End of help on this topic>
22578 ====== h_config_init_cmd_list =====
22581 <TITLE>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></TITLE>
22584 <H1>OPTION: <!--#echo var="VAR_initial-keystroke-list"--></H1>
22586 The initial keystroke--or command--list option lets you start Alpine at
22587 any place you like.
22588 Whatever keystrokes you specify here will be executed
22589 by Alpine upon startup as a macro.
22590 The words SPACE, TAB, DOWN, UP, LEFT, and
22591 RIGHT indicate the pressing of those keys.
22592 CR indicates the pressing of the RETURN key.
22593 F1 through F12 represent the function keys, and ^ followed
22594 by a character indicates that key pressed along with the control key (in
22595 other words, ^P means Ctrl-P).
22596 As a shortcut notation, an element of the list may be several characters
22597 surrounded by double-quotes (").
22598 That will be expanded into the individual keystrokes
22599 (excluding the double-quote characters).
22600 For example, the quoted-string
22602 <P><CENTER>"ABC"</CENTER>
22605 is interpreted the same as the three separate list members
22607 <P><CENTER>A and B and C</CENTER>
22610 which is also the same as
22612 <P><CENTER>A,B,C</CENTER>
22615 An example: To view message 1 on startup,
22616 you could use an <!--#echo var="VAR_initial-keystroke-list"--> equal to
22618 <P><CENTER>I,J,1,CR,V</CENTER>
22621 An equivalent version of this is
22623 <P><CENTER>"IJ1",CR,V</CENTER>
22626 Restrictions: You cannot pre-type into the composer with the initial
22627 keystroke list, and you cannot mix function key commands with letter
22631 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22634 <End of help on this topic>
22637 ====== h_config_comp_hdrs =====
22640 <title>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></title>
22643 <h1>OPTION: <!--#echo var="VAR_default-composer-hdrs"--></h1>
22645 You can control which headers you want visible when composing outgoing
22646 email using this option.
22647 You can specify any of the regular set, any
22648 <A HREF="h_compose_richhdr">Rich Header</A>,
22649 or any <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22650 that you have already defined.
22651 If you use this setting at all, you must specify all the
22652 headers you want to see, you can't just add to the regular header set.
22653 The default set is To:, Cc:, Attchmnt:, and Subject:.<p>
22655 Note that the "Newsgroups:" header will be abbreviated in the Composer
22656 display, but should be spelled out in full here.<p>
22658 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22660 <End of help on this topic>
22663 ====== h_config_custom_hdrs =====
22666 <TITLE>OPTION: <!--#echo var="VAR_customized-hdrs"--></TITLE>
22669 <H1>OPTION: <!--#echo var="VAR_customized-hdrs"--></H1>
22671 You may add your own custom headers to outgoing messages.
22672 Each header you specify here must include the header tag
22673 (<A HREF="h_composer_reply_to">Reply-To:</A>, Approved:, etc.)
22674 and may optionally include a value for that header.
22675 If you want to see these custom headers each time you compose a message,
22676 you must add them to your
22677 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> list,
22678 otherwise they become part
22679 of the rich header set that you only see when you press the
22680 <A HREF="h_compose_richhdr">Rich Header</A>
22681 <!--chtml if pinemode="function_key"-->(F5)
22682 <!--chtml else-->(Ctrl-R)<!--chtml endif--> command.
22683 (If you are looking for a way to change which headers are <EM>displayed</EM>
22684 when you view a message, take a look at the
22685 <A HREF="h_config_viewer_headers"><!--#echo var="VAR_viewer-hdrs"--></A>
22687 Here's an example that shows how you might set your From address
22689 <CENTER><SAMP>From: Full Name <user@example.com></SAMP></CENTER>
22691 and another showing how you might set a Reply-To address
22693 <CENTER><SAMP>Reply-To: user@example.com</SAMP></CENTER>
22695 You may also set non-standard header values here.
22696 For example, you could add
22698 <CENTER><SAMP>Organization: My Organization Name</SAMP></CENTER>
22702 <CENTER><SAMP>X-Favorite-Colors: Purple and Gold</SAMP></CENTER>
22704 If you include a value after the colon then that header will be included
22705 in your outgoing messages unless you delete it before sending.
22706 If a header in the <!--#echo var="VAR_customized-hdrs"--> list has only a tag but no value, then
22707 it will not be included in outgoing messages unless you edit a value
22711 <CENTER><SAMP>Reply-To:</SAMP></CENTER>
22713 is in the list, then the Reply-To header will be available for editing
22714 but won't be included unless a value is added while in the composer.
22716 It's actually a little more complicated than that.
22717 The values of headers that you set with the <!--#echo var="VAR_customized-hdrs"--> option are
22719 If the message you are about to compose already has a value for a header,
22720 that value is used instead of a value from your <!--#echo var="VAR_customized-hdrs"-->.
22721 For example, if you are Replying to a message the Subject field
22722 will already be filled in.
22723 In that case, if the <!--#echo var="VAR_customized-hdrs"--> list contains a Subject line, the
22724 custom subject will <EM>NOT</EM> be used.
22725 The subject derived from the subject of the message you are Replying
22726 to will be used instead.
22728 It is also possible to make header setting even more complicated and more
22730 <A HREF="h_rules_roles">Roles</A>,
22731 but if all you want to do is set a default value for a header, you don't
22732 need to think about Roles.
22734 If you change your From address you may also find it useful to add the
22735 changed From address to the
22736 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
22737 configuration option.
22739 Limitation: Because commas are used to separate the list of
22740 <!--#echo var="VAR_customized-hdrs"-->, it is not possible to have the value of a
22741 header contain a comma.
22742 Nor is there currently an "escape" mechanism provided
22745 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22748 <End of help on this topic>
22751 ====== h_config_viewer_headers =====
22754 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdrs"--></TITLE>
22757 <H1>OPTION: <!--#echo var="VAR_viewer-hdrs"--></H1>
22759 You may change the default list of headers that are viewed by listing
22760 the headers you want to view here. If the headers in your
22761 "<!--#echo var="VAR_viewer-hdrs"-->" list are present in the message, then they
22762 will be shown. The order of the headers you list will be honored. If
22763 the special value "all-except" is included as the first
22764 header in the "<!--#echo var="VAR_viewer-hdrs"-->" list, then all headers in the
22765 message except those in the list will be shown. The values are all
22769 Note that once you put anything in the "<!--#echo var="VAR_viewer-hdrs"-->" list,
22770 then the original default headers are ignored. So, if you just wanted
22771 to add the header Organization to the list, you would have to list
22772 Organization plus all of the other headers originally in the default
22773 list. If you just included Organization and nothing else, then you
22774 would see only the Organization header, nothing else.
22777 The default list of headers includes:
22796 If you are looking for a way to control which headers are included in
22797 outgoing mail and are visible or not in the composer, take a look at the
22799 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>
22800 and <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A> instead of
22804 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
22806 <End of help on this topic>
22809 ====== h_config_viewer_margin_left =====
22812 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-left"--></TITLE>
22815 <H1>OPTION: <!--#echo var="VAR_viewer-margin-left"--></H1>
22817 This variable controls the left-hand vertical margin's width in
22818 Alpine's Message Viewing screen.
22819 Its value is the number of space characters preceding each displayed line.
22820 For consistency with
22821 <A HREF="h_config_viewer_margin_right"><!--#echo var="VAR_viewer-margin-right"--></A>,
22822 you may specify the column number to start in
22823 (column numbering begins with number 1)
22824 instead of the width of the margin by appending a lower case letter
22825 "c" to the number.
22826 For example, a value of "2c" means to start the text in column two,
22827 which is entirely equivalent to a value of "1", which means to
22828 leave a margin of 1 space.
22830 The default is a left margin of 0 (zero).
22831 Misconfigurations (for example, negative values or values with starting
22832 left columns greater than the ending right column)
22833 are silently ignored.
22834 If the number of columns for text between the <!--#echo var="VAR_viewer-margin-left"--> and
22835 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22839 <End of help on this topic>
22842 ====== h_config_viewer_margin_right =====
22845 <TITLE>OPTION: <!--#echo var="VAR_viewer-margin-right"--></TITLE>
22848 <H1>OPTION: <!--#echo var="VAR_viewer-margin-right"--></H1>
22850 This variable controls the right-hand vertical margin's width in
22851 Alpine's Message Viewing screen.
22852 Its value is the number of space characters following each displayed line.
22853 You may specify the column number to end the text in
22854 (column numbering begins with number 1)
22855 instead of the width of the margin by appending a lower case letter
22856 "c" to the number.
22857 For example, a value of "76c" means to end the text in column 76.
22858 If the screen is 80 characters wide, this is equivalent to a value
22859 of "4", which means to leave a margin of 4 spaces.
22860 However, if you use different size screens at different times, then these
22861 two values are not equivalent.
22863 The default right margin is 4.
22864 Misconfigurations (for example, negative values or values with starting
22865 left columns greater than the ending right column)
22866 are silently ignored.
22867 If the number of columns for text between the
22868 <A HREF="h_config_viewer_margin_left"><!--#echo var="VAR_viewer-margin-left"--></A> and
22869 the <!--#echo var="VAR_viewer-margin-right"--> is fewer than 8, then margins of zero will be used
22873 <End of help on this topic>
22876 ====== h_config_quote_suppression =====
22879 <TITLE>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></TITLE>
22882 <H1>OPTION: <!--#echo var="VAR_quote-suppression-threshold"--></H1>
22884 This option should be used with care.
22885 It will cause some of the quoted text to be eliminated from the
22886 display when viewing a message in the MESSAGE TEXT screen.
22887 For example, if you set the <!--#echo var="VAR_quote-suppression-threshold"--> to the
22888 value "5",
22889 this will cause quoted text that is longer than five lines to be truncated.
22890 Quoted text of five or fewer consecutive lines will be displayed in its entirety.
22891 Quoted text of more than six lines will have the first five lines displayed
22892 followed by a line that looks something like
22894 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
22896 As a special case, if exactly one line of quoted text would be hidden, the
22897 entire quote will be shown instead.
22898 So for the above example, quoted text that is exactly six lines long will
22899 will be shown in its entirety.
22900 (In other words, instead of hiding a single line and adding a line
22901 that announces that one line was hidden, the line is just shown.)
22903 If the sender of a message has carefully chosen the quotes that he or she
22904 includes, hiding those quotes may change the meaning of the message.
22905 For that reason, Alpine requires that when you want to set the value of this
22906 variable to something less than four lines, you actually have to set it
22907 to the negative of that number.
22908 So if you want to set this option to "3", you actually have to
22909 set it to "-3".
22910 The only purpose of this is to get you to think about whether or not you
22911 really want to do this!
22912 If you want to delete all quoted text you set the value of this option
22913 to the special value "-10".
22915 The legal values for this option are
22919 <TD> 0 </TD>
22920 <TD> Default, don't hide anything </TD>
22923 <TD> -1,-2,-3 </TD>
22924 <TD> Suppress quote lines past 1, 2, or 3 lines </TD>
22927 <TD> 4,5,6,... </TD>
22928 <TD> Suppress if more than that many lines </TD>
22931 <TD> -10 </TD>
22932 <TD> Suppress all quoted lines </TD>
22936 If you set this option to a non-default value you may sometimes wish to
22937 view the quoted text that is not shown.
22938 When this is the case, the
22939 <A HREF="h_common_hdrmode">HdrMode Command</A>
22940 may be used to show the hidden text.
22941 Typing the "H" command once will show the hidden text.
22942 Typing a second "H" will also turn on Full Header mode.
22943 The presence or absence of the HdrMode command is determined by the
22944 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
22945 Feature-List option in your Alpine configuration, so you will want to
22946 be sure that is turned on if you use quote suppression.
22948 For the purposes of this option, a quote is a line that begins with the
22949 character ">".
22951 Quotes are only suppressed when displaying a message on the screen.
22952 The entire quote will be left intact when printing or forwarding or something
22955 <End of help on this topic>
22958 ====== h_config_saved_msg_name_rule =====
22961 <TITLE>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></TITLE>
22964 <H1>OPTION: <!--#echo var="VAR_saved-msg-name-rule"--></H1>
22966 This option determines the default folder name when saving
22970 The default option is "default-folder", which is the folder
22971 called "saved-messages" in Unix Alpine and
22972 "savemail" in PC-Alpine. To change the default folder, modify
22973 the Alpine option called
22974 <A HREF="h_config_def_save_folder">"<!--#echo var="VAR_default-saved-msg-folder"-->"</A>.
22977 Choosing any of the "by-" options cause Alpine to attempt to
22978 get the chosen option's value for the message being saved (or for the
22979 first message being saved if using an aggregrate save).
22980 For example, if "by-from" is chosen, Alpine attempts to get the
22981 value of who the message came from (i.e. the from address).
22982 Alpine then attempts to save the message to a folder matching that value.
22983 If "by-from" is chosen and no value is obtained, Alpine uses
22984 "by-sender".
22985 The opposite is also true.
22986 If "by-recipient" is chosen and the message was posted to a
22987 newsgroup, Alpine will use the newsgroup name.
22988 If "by-replyto" is chosen and no value is obtained, Alpine uses
22989 "by-from".
22992 If any of the "by-realname" options are chosen, Alpine will attempt
22993 to use the personal name part of the address instead of the mailbox part.
22994 If any of the "by-nick" options are chosen, the
22995 address is looked up in your address book and if found, the
22996 nickname for that entry is used.
22997 Only simple address book entries are checked, not distribution lists.
22998 Similarly, if any of the
22999 "by-fcc" options are chosen, the fcc from the corresponding
23000 address book entry is used.
23001 If by-realname, or the by-nick or by-fcc lookups result in no value,
23002 then if the chosen option ends with the "then-from",
23003 "then-sender", "then-replyto",
23004 or "then-recip" suffix, Alpine
23005 reverts to the same behavior as "by-from",
23006 "by-sender", "by-replyto", or "by-recip"
23007 depending on which option was specified.
23008 If the chosen option doesn't end with one of
23009 the "then-" suffixes, then Alpine reverts to the default
23010 folder when no match is found in the address book.
23013 Choosing the option called "last-folder-used", causes Alpine
23014 to save to the folder that you saved to the last time you saved a
23015 message. The first time you save a message in an Alpine session, Alpine
23016 attempts to save the message to the default folder.
23019 Here is an example to make some of the options clearer.
23020 If the message is From
23022 <CENTER><SAMP>Fred Flintstone <flint@bedrock.org></SAMP></CENTER>
23024 and this rule is set to "by-from", then the default folder offered
23025 in the save dialog would be "flint".
23027 If this rule is set to "by-realname-of-from" then the default would
23028 be "Fred Flintstone".
23030 If this rule is set to "by-nick-of-from" then Alpine will search
23031 for the address "flint@bedrock.org" in your address book.
23032 If an entry is found and it has a nickname associated with it, that nickname
23033 will be offered as the default folder.
23034 If not, the default saved message folder will be offered as the default.
23036 If this rule is set to "by-fcc-of-from" then Alpine will search
23037 for the address "flint@bedrock.org" in your address book.
23038 If an entry is found and it has an Fcc associated with it, that Fcc
23039 will be offered as the default folder.
23040 If not, the default saved message folder will be offered as the default.
23042 If this rule is set to "by-nick-of-from-then-from" then Alpine will search
23043 for the address "flint@bedrock.org" in your address book.
23044 If an entry is found and it has a nickname associated with it, that nickname
23045 will be offered as the default folder.
23046 If it is not found (or has no nickname) then the default offered will be
23047 the same as it would be for the "by-from" rule.
23048 That is, it would be "flint"
23051 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23053 <End of help on this topic>
23056 ====== h_config_fcc_rule =====
23059 <TITLE>OPTION: <!--#echo var="VAR_fcc-name-rule"--></TITLE>
23062 <H1>OPTION: <!--#echo var="VAR_fcc-name-rule"--></H1>
23064 This option determines the default name for folder carbon copy. Choose
23068 <DT>default-fcc</DT>
23069 <DD>This is the normal default, the value of which is set in the
23070 "<!--#echo var="VAR_default-fcc"-->" variable as specified earlier in this
23074 <DT>last-fcc-used</DT>
23075 <DD> Causes Alpine to use the folder that was last
23076 used in the fcc field
23079 <DT>by-nickname</DT>
23080 <DD>Means that Alpine will use the nickname
23081 from your address book that matches the first address in the To line.
23082 If there is no match, it will use the value of the
23083 "<!--#echo var="VAR_default-fcc"-->" variable.
23086 <DT>by-recipient</DT>
23087 <DD>Means Alpine will form a folder name
23088 based on the left hand side of the first address in the To line.
23091 <DT>by-nick-then-recip</DT>
23092 <DD>Means that it will use the
23093 matching nickname from your address book if there is one, otherwise it
23094 will extract the recipient name from the address and use that (like
23098 <DT>current-folder</DT>
23099 <DD>Causes a copy to be written to
23100 the currently open folder, unless that is the INBOX. In the case
23101 where the current folder is the INBOX, the "<!--#echo var="VAR_default-fcc"-->" is
23107 Note: Whatever the fcc specified by the rule here, it will be
23108 over-ridden by any fcc entries you have in your address book.
23112 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23114 <End of help on this topic>
23117 ====== h_config_sort_key =====
23120 <TITLE>OPTION: <!--#echo var="VAR_sort-key"--></TITLE>
23123 <H1>OPTION: <!--#echo var="VAR_sort-key"--></H1>
23125 This option determines the order in which messages will be displayed in
23126 the MESSAGE INDEX screen. Choose from:
23129 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
23130 <LI> <A HREF="h_index_sort_date">Date</A>
23131 <LI> <A HREF="h_index_sort_subj">Subject</A>
23132 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
23133 <LI> <A HREF="h_index_sort_thread">Thread</A>
23134 <LI> <A HREF="h_index_sort_from">From</A>
23135 <LI> <A HREF="h_index_sort_size">Size</A>
23136 <LI> <A HREF="h_index_sort_score">Score</A>
23137 <LI> <A HREF="h_index_sort_to">To</A>
23138 <LI> <A HREF="h_index_sort_cc">Cc</A>
23142 Each type of sort may also be reversed.
23143 Normal default is by "Arrival".
23146 A possible point of confusion arises when you change the configuration
23147 of the <!--#echo var="VAR_sort-key"-->.
23148 The folder will normally be re-sorted when you go back to viewing the
23150 However, if you have manually sorted the folder with the
23152 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
23153 command, then it will not be re-sorted until the next time it is opened.
23157 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23159 <End of help on this topic>
23162 ====== h_config_other_startup =====
23165 <TITLE>OPTION: Set Startup Rule</TITLE>
23168 <H1>OPTION: Set Startup Rule</H1>
23170 This option determines which message will be the <EM>current message</EM> when
23171 the folder is first opened.
23172 It works the same way that the option
23173 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>
23174 works, so look there for help.
23175 It may be used for any folder, not just incoming folders.
23179 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23181 <End of help on this topic>
23184 ====== h_config_perfolder_sort =====
23187 <TITLE>Set Sort Order</TITLE>
23190 <H1>Set Sort Order</H1>
23192 This option determines the order in which messages will be displayed in
23193 the MESSAGE INDEX screen when the Current Folder Type set in the
23194 Pattern is a match. Choose from:
23197 <LI> <A HREF="h_index_sort_default">Default</A>
23198 <LI> <A HREF="h_index_sort_arrival">Arrival</A>
23199 <LI> <A HREF="h_index_sort_date">Date</A>
23200 <LI> <A HREF="h_index_sort_subj">Subject</A>
23201 <LI> <A HREF="h_index_sort_ordsubj">OrderedSubj</A>
23202 <LI> <A HREF="h_index_sort_thread">Thread</A>
23203 <LI> <A HREF="h_index_sort_from">From</A>
23204 <LI> <A HREF="h_index_sort_size">Size</A>
23205 <LI> <A HREF="h_index_sort_score">Score</A>
23206 <LI> <A HREF="h_index_sort_to">To</A>
23207 <LI> <A HREF="h_index_sort_cc">Cc</A>
23211 Each type of sort may also be reversed.
23212 Normal default is by "Arrival".
23215 A possible point of confusion arises when you change the configuration
23216 of the Sort Order for the currently open folder.
23217 The folder will normally be re-sorted when you go back to viewing the
23219 However, if you have manually sorted the folder with the
23221 (<!--chtml if pinemode="function_key"-->F7<!--chtml else-->$<!--chtml endif-->)
23222 command, then it will not be re-sorted until the next time it is opened.
23226 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23228 <End of help on this topic>
23231 ====== h_config_fld_sort_rule =====
23234 <TITLE>OPTION: <!--#echo var="VAR_folder-sort-rule"--></TITLE>
23237 <H1>OPTION: <!--#echo var="VAR_folder-sort-rule"--></H1>
23239 This option controls the order in which folder list entries will be
23240 presented in the FOLDER LIST screen. Choose one of the following:
23243 <DT>Alphabetical</DT>
23244 <DD>sort by alphabetical name independent of type
23247 <DT>Alpha-with-dirs-last</DT>
23248 <DD>sort by alphabetical name grouping directory entries
23249 to the end of the list
23252 <DT>Alpha-with-dirs-first</DT>
23253 <DD>sort by alphabetical name grouping directory entries
23254 to the start of the list
23258 The normal default is "Alphabetical".
23262 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23264 <End of help on this topic>
23267 ====== h_config_ab_sort_rule =====
23270 <TITLE>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></TITLE>
23273 <H1>OPTION: <!--#echo var="VAR_addrbook-sort-rule"--></a></H1>
23275 This option controls the order in which address book entries will be
23276 presented. Choose one of the following:
23280 <DD>use fullname field, lists mixed in
23283 <DT>fullname-with-lists-last</DT>
23284 <DD>use fullname field, but put lists at end
23288 <DD>use nickname field, lists mixed in
23291 <DT>nickname-with-lists-last</DT>
23292 <DD>use nickname field, but put lists at end
23296 <DD>don't change order of file
23301 The normal default is "fullname-with-lists-last".
23302 If you use an address book from more than one computer and those
23303 computers sort the address book differently then the sort order
23304 will be the order where the last change to the address book was
23306 There are two reasons the sorting might be different on different
23308 First, the <!--#echo var="VAR_addrbook-sort-rule"--></a> may be set differently in the two
23310 Second, the collation rules on the two computers may be different.
23311 For example, one system might ignore special characters while the other
23312 doesn't or one may sort upper and lower case letters together while
23314 In any case, the order you see is the order on the system where the
23315 last change was made, for example by an address book edit or a
23316 Take Address command.
23320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23322 <End of help on this topic>
23325 ====== h_config_post_char_set =====
23328 <TITLE>OPTION: <!--#echo var="VAR_posting-character-set"--></TITLE>
23331 <H1>OPTION: <!--#echo var="VAR_posting-character-set"--></H1>
23333 The <!--#echo var="VAR_posting-character-set"--> configuration option is used
23334 when sending messages.
23338 When sending a message the text typed in the composer is
23339 labeled with the character set specified by this option.
23340 If the composed text is not fully representable in the
23341 specified <!--#echo var="VAR_posting-character-set"-->, then it is labeled as "UTF-8."
23345 Attachments are labeled with your
23346 <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>.
23349 Generally, there should be little need to set this option.
23351 default behavior is to label composed text as specifically as
23352 possible. That is, if the composed text has no non-ASCII characters,
23353 it is labeled as "US-ASCII." Similarly, if it is composed of
23354 only ISO-8859-15 characters, it is labeled as such. Alpine will
23355 attempt to automatically detect a number of character sets including ISO-8859-15,
23356 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23357 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, and EUC-KR.
23358 If the message contains a mix of character sets,
23359 it is labeled as "UTF-8."
23363 This setting is provided to allow you to force a particular character set that
23364 Alpine does not automatically detect. For example, if a message is representable
23365 in more than one character set then Alpine may choose a different default
23367 Lastly, by setting this option explicitly to
23368 "UTF-8" all non-ASCII messages you send will be labeled as
23369 "UTF-8" instead of something more specific.
23372 In the Setup/Config screen you may choose from a list of all the
23373 character sets Alpine knows about by using the "T" ToCharsets command.
23377 <A HREF="h_config_char_set">"Display Character Set"</A>
23378 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23379 are closely related.
23380 Setting the feature
23381 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23382 should cause this option to be ignored.
23386 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23388 <End of help on this topic>
23391 ====== h_config_unk_char_set =====
23394 <TITLE>OPTION: <!--#echo var="VAR_unknown-character-set"--></TITLE>
23397 <H1>OPTION: <!--#echo var="VAR_unknown-character-set"--></H1>
23399 The <!--#echo var="VAR_unknown-character-set"--> configuration option is used
23400 when reading or replying to messages.
23404 A text message should either be made up of all US-ASCII characters
23405 or it should contain a charset label which tells the software which
23406 character set encoding to use to interpret the message.
23407 Sometimes a malformed message may be unlabeled but contain non-ascii text.
23408 This message is outside of the standards so any attempt to read it could fail.
23409 When Alpine attempts to read such a message it will try to interpret the
23410 text in the character set you specify here.
23411 For example, if you have correspondents who send you unlabeled messages that
23412 are usually made up of characters from the WINDOWS-1251 character set, setting
23413 this <!--#echo var="VAR_unknown-character-set"--> to <CODE>WINDOWS-1251</CODE> will
23414 allow you to read those messages.
23415 Of course, if the unlabeled message is actually in some other character set,
23416 then you may see garbage on your screen.
23418 Instead of just unlabeled text, this option also affects text which is labeled
23419 with the charsets "X-Unknown", "MISSING_PARAMETER_VALUE"
23420 or "US-ASCII".
23423 In the Setup/Config screen you may choose from a list of all the
23424 character sets Alpine knows about by using the "T" ToCharsets command.
23428 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23430 <End of help on this topic>
23433 ====== h_config_char_set =====
23436 <TITLE>OPTION: Display Character Set</TITLE>
23439 <H1>OPTION: Display Character Set</H1>
23441 The Display Character Set configuration option is used when viewing messages.
23443 Alpine uses Unicode characters internally and
23444 it is a goal for Alpine to handle email in many different languages.
23445 Alpine will properly display only left-to-right character sets
23446 in a fixed-width font. Specifically, Alpine assumes that a fixed-width
23447 font is in use, in the sense that
23448 characters are assumed to take up zero, one, or two character cell
23449 widths from left to right on the screen. This is true even in PC-Alpine.
23452 Alpine recognizes some local character sets that are right-to-left
23453 (Arabic, Hebrew, and Thai) or not representable in a fixed-width font
23454 (Arabic) and properly converts texts in these character sets to/from
23455 Unicode; however, there are known display bugs with these character
23459 There are three possible configuration character settings and some
23460 environment variable settings that can affect how Alpine
23461 handles international characters.
23462 The first two of these are only available in UNIX Alpine.
23463 The three configuration options are
23464 Display Character Set,
23465 Keyboard Character Set, and
23466 <!--#echo var="VAR_posting-character-set"-->.
23467 The Keyboard Character Set defaults to being the same value
23468 as the Display Character Set, and that is usually correct, because
23469 the keyboard almost always produces characters in the same character set
23470 as the display displays.
23471 The Display Character Set is the character set that Alpine
23472 will attempt to use when sending characters to the display.
23475 By default, the Display Character Set variable is not set and UNIX Alpine
23476 will attempt to get this information from the environment.
23477 In particular, the <CODE>nl_langinfo(CODESET)</CODE> call is used.
23478 This usually depends on the setting of the environment variables LANG or LC_CTYPE.
23479 An explicit configuration setting for Display Character Set will,
23480 of course, override any default setting.
23482 For PC-Alpine the Display Character Set
23483 and the Keyboard Character Set
23484 are always equivalent to <CODE>UTF-8</CODE> and this is not settable.
23487 It is probably best to use UNIX Alpine in a terminal emulator
23488 capable of displaying UTF-8 characters, since that will allow you to
23489 view just about any received text that is correctly formatted (note,
23490 however, the above comments about known index display bugs with certain
23491 character sets). You'll need to have an emulator that uses a UTF-8 font
23492 and you'll need to set up your environment to use a UTF-8 charmap. For
23493 example, on a Linux system you might include
23495 <CENTER> <CODE>setenv LANG en_US.UTF-8</CODE> </CENTER>
23498 or something similar in your UNIX startup files.
23499 You'd also have to select a UTF-8 font in your terminal emulator.
23502 The types of values that the character set variables may be set to are
23503 <CODE>UTF-8</CODE>, <CODE>ISO-8859-1</CODE>, or <CODE>EUC-JP</CODE>.
23504 The <CODE>ISO-2022</CODE> character sets are not supported for input or
23505 for display, but as a special case, <CODE>ISO-2022-JP</CODE> is supported
23506 for use only as a <!--#echo var="VAR_posting-character-set"-->.
23507 In the Setup/Config screen you may choose from a list of all the
23508 character sets Alpine knows about by using the "T" ToCharsets command.
23509 Here is a list of many of the possible character sets:
23513 <TR> <TD>UTF-8</TD> <TD>Unicode</TD> </TR>
23514 <TR> <TD>US-ASCII</TD> <TD>7 bit American English characters</TD> </TR>
23515 <TR> <TD>ISO-8859-1</TD> <TD>8 bit European "Latin 1" character set</TD> </TR>
23516 <TR> <TD>ISO-8859-2</TD> <TD>8 bit European "Latin 2" character set</TD> </TR>
23517 <TR> <TD>ISO-8859-3</TD> <TD>8 bit European "Latin 3" character set</TD> </TR>
23518 <TR> <TD>ISO-8859-4</TD> <TD>8 bit European "Latin 4" character set</TD> </TR>
23519 <TR> <TD>ISO-8859-5</TD> <TD>8 bit Latin and Cyrillic</TD> </TR>
23520 <TR> <TD>ISO-8859-6</TD> <TD>8 bit Latin and Arabic</TD> </TR>
23521 <TR> <TD>ISO-8859-7</TD> <TD>8 bit Latin and Greek</TD> </TR>
23522 <TR> <TD>ISO-8859-8</TD> <TD>8 bit Latin and Hebrew</TD> </TR>
23523 <TR> <TD>ISO-8859-9</TD> <TD>8 bit European "Latin 5" character set</TD> </TR>
23524 <TR> <TD>ISO-8859-10</TD> <TD>8 bit European "Latin 6" character set</TD> </TR>
23525 <TR> <TD>ISO-8859-11</TD> <TD>Latin and Thai</TD> </TR>
23526 <TR> <TD>ISO-8859-12</TD> <TD>Reserved</TD> </TR>
23527 <TR> <TD>ISO-8859-13</TD> <TD>8 bit European "Latin 7" character set</TD> </TR>
23528 <TR> <TD>ISO-8859-14</TD> <TD>8 bit European "Latin 8" character set</TD> </TR>
23529 <TR> <TD>ISO-8859-15</TD> <TD>8 bit European "Latin 9" character set</TD> </TR>
23530 <TR> <TD>ISO-8859-16</TD> <TD>8 bit European "Latin 10" character set</TD> </TR>
23531 <TR> <TD>KOI8-R</TD> <TD>8 bit Latin and Russian</TD> </TR>
23532 <TR> <TD>KOI8-U</TD> <TD>8 bit Latin and Ukranian</TD> </TR>
23533 <TR> <TD>WINDOWS-1251</TD> <TD>8 bit Latin and Russian</TD> </TR>
23534 <TR> <TD>TIS-620</TD> <TD>8 bit Latin and Thai</TD> </TR>
23535 <TR> <TD>VISCII</TD> <TD>8 bit Latin and Vietnamese</TD> </TR>
23536 <TR> <TD>GBK</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23537 <TR> <TD>GB2312</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23538 <TR> <TD>CN-GB</TD> <TD>Latin and Chinese Simplified</TD> </TR>
23539 <TR> <TD>BIG5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23540 <TR> <TD>BIG-5</TD> <TD>Latin and Chinese Traditional</TD> </TR>
23541 <TR> <TD>EUC-JP</TD> <TD>Latin and Japanese</TD> </TR>
23542 <TR> <TD>SHIFT-JIS</TD> <TD>Latin and Japanese</TD> </TR>
23543 <TR> <TD>EUC-KR</TD> <TD>Latin and Korean</TD> </TR>
23544 <TR> <TD>KSC5601</TD> <TD>Latin and Korean</TD> </TR>
23548 When reading incoming email, Alpine understands many different
23549 character sets and is able to convert the incoming mail into Unicode.
23550 The Unicode will be converted to the Display Character Set
23551 for display on your terminal.
23552 Characters typed at the keyboard will be converted from the
23553 Keyboard Character Set to Unicode for Alpine's internal
23555 You may find that you can read some malformed messages that do not
23556 contain a character set label by setting the option
23557 <A HREF="h_config_unk_char_set">"<!--#echo var="VAR_unknown-character-set"-->"</A>.
23560 The <!--#echo var="VAR_posting-character-set"--> is used when sending messages.
23561 The default behavior obtained by leaving this variable unset is usually
23562 what is wanted. In that default case, Alpine will attempt
23563 to label the message with the most specific character set from the
23564 rather arbitrary set
23566 US-ASCII, ISO-8859-15,
23567 ISO-8859-1, ISO-8859-2, VISCII, KOI8-R, KOI8-U, ISO-8859-7, ISO-8859-6,
23568 ISO-8859-8, TIS-620, ISO-2022-JP, GB2312, BIG5, EUC-KR, and UTF-8.
23571 For example, if the message is made up of only US-ASCII characters, it
23572 will be labeled US-ASCII. Otherwise, if it is all ISO-8859-15 characters,
23573 that will be the label. If that doesn't work the same is tried for the
23574 remaining members of the list.
23577 It might make sense to set <!--#echo var="VAR_posting-character-set"--> to an
23578 explicit value instead.
23579 For example, if you usually send messages in Greek, setting this
23580 option to ISO-8859-7 will result in messages being labeled as
23581 US-ASCII if there are no non-ascii characters, ISO-8859-7 if there
23582 are only Greek characters, or UTF-8 if there are some characters
23583 that aren't representable in ISO-8859-7.
23584 Another possibility is to set this option explicitly to UTF-8.
23586 Alpine labels only ascii messages as US-ASCII and all other
23591 <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23592 and <A HREF="h_config_key_char_set">"Keyboard Character Set"</A>
23593 are closely related to this option.
23594 Setting the feature
23595 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23596 should cause this option to be ignored.
23599 When displaying a message, Alpine compares this setting to the character
23600 set specified in the message. If not all of the
23601 characters in the message can be displayed using the Display Character Set
23602 then Alpine places an editorial
23603 comment in the displayed text (enclosed in square-brackets) indicating
23604 that some characters may not be displayed correctly.
23605 This comment may be eliminated by turning on the option
23606 <A HREF="h_config_quell_charset_warning"><!--#echo var="FEAT_quell-charset-warning"--></A>.
23610 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23612 <End of help on this topic>
23615 ====== h_config_key_char_set =====
23618 <TITLE>OPTION: Keyboard Character Set</TITLE>
23621 <H1>OPTION: Keyboard Character Set</H1>
23625 The Keyboard Character Set identifies the character set of the characters
23626 coming from your keyboard.
23627 It defaults to having the same value as your
23628 <A HREF="h_config_char_set">"Display Character Set"</A>,
23629 which in turn defaults to a value obtained from your environment.
23630 It is unlikely that you will need to use this option, because the keyboard
23631 almost always produces the same kind of characters as the display displays.
23634 This character set is also used when accessing files in your local
23636 The names of the files are assumed to be in the same character set as
23637 what the keyboard produces, as well as the contents of the files.
23640 In the Setup/Config screen you may choose from a list of all the
23641 character sets Alpine knows about by using the "T" ToCharsets command.
23645 <A HREF="h_config_char_set">"Display Character Set"</A>
23646 and <A HREF="h_config_post_char_set">"<!--#echo var="VAR_posting-character-set"-->"</A>
23647 are closely related.
23648 Setting the feature
23649 <A HREF="h_config_use_system_translation">"Use System Translation"</A>
23650 should cause this option to be ignored.
23654 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23656 <End of help on this topic>
23659 ====== h_config_editor =====
23662 <TITLE>OPTION: <!--#echo var="VAR_editor"--></TITLE>
23665 <H1>OPTION: <!--#echo var="VAR_editor"--></H1>
23667 <!--#echo var="VAR_editor"--> specifies the program invoked by ^_ in the Composer. This is
23668 normally an alternative to Alpine's internal composer (Pico). You could use
23669 this setting to specify an alternate editor to use occasionally or if you
23670 have a favorite editor and want to use it all the time (see the
23671 <A HREF="h_config_alt_ed_now">"<!--#echo var="FEAT_enable-alternate-editor-implicitly"-->"</A> setting). <P>
23672 If you specify multiple editors for this option, ^_ will invoke the first one
23673 of those specified that exists and is executable. When specifying a program
23674 for use here, make sure that the format of the text it saves -- which, when
23675 you exit it, will become the message body in Alpine -- is appropriate
23676 for the body of an email message; avoid proprietary formats that may result in
23677 a message body that the recipient of your message will be unable to decipher.
23679 <!--chtml if pinemode="os_windows"-->
23681 If you are in doubt about what editors are available on your system, or which
23682 of them may be appropriate for specification here, ask your local computing
23686 Note that if <a href="h_config_quell_flowed_text"><!--#echo var="FEAT_quell-flowed-text"--></a> is
23687 unset, outgoing text will be set as flowed. In most cases this will be fine,
23688 but if the editor has a "flowed text" mode, it would be best to
23692 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23695 <End of help on this topic>
23698 ====== h_config_speller =====
23701 <TITLE>OPTION: <!--#echo var="VAR_speller"--></TITLE>
23704 <H1>OPTION: <!--#echo var="VAR_speller"--></H1>
23708 For PC-Alpine, you must install the aspell library code that you
23710 <A HREF="http://aspell.net/win32/">http://aspell.net/win32/</A>.
23712 This option affects the behavior of the ^T (spell check) command in the
23713 Composer. It specifies the program invoked by ^T in the Composer.
23714 By default, Alpine uses
23716 <CENTER><SAMP>aspell --dont-backup --mode=email check</SAMP></CENTER>
23718 if it knows where to find "aspell".
23719 If there is no "aspell" command available but the command "ispell" is available
23720 then the command used is
23722 <CENTER><SAMP>ispell -l</SAMP></CENTER>
23724 Otherwise, the ancient "spell" command is used.
23726 If you specify a value for this command (with full pathname) then that is what
23727 will be used instead of any of the defaults.
23729 spell-checking program, Alpine appends a tempfile name (where the message is
23730 passed) to the command line. Alpine expects the speller to correct the
23731 spelling in that file. When you exit from that program Alpine will read the
23732 tempfile back into the composer.
23734 Don't set this speller option to the standard Unix spell command.
23735 That won't work because spell works in a different way.
23739 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23741 <End of help on this topic>
23744 ====== h_config_aspell_dictionary =====
23747 <TITLE>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></TITLE>
23750 <H1>OPTION: <!--#echo var="VAR_aspell-dictionary-list"--></H1>
23754 This option specifies a list of dictionaries you will use with
23755 aspell. A sample entry is "en_US" for american english, or
23756 "en_GB" for brittish english.
23760 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
23762 <End of help on this topic>
23765 ====== h_config_display_filters =====
23768 <TITLE>OPTION: <!--#echo var="VAR_display-filters"--></TITLE>
23771 <H1>OPTION: <!--#echo var="VAR_display-filters"--></H1>
23773 This option defines a list of text-filtering commands (programs or
23774 scripts) that may be used to filter text portions of received messages
23775 prior to their use (e.g., presentation in the "MESSAGE TEXT"
23776 display screen, exporting to a text file).
23777 For security reasons, the full path name of the
23778 filter command must be specified.
23781 The command is executed and the message is piped into its standard input.
23782 The standard output of the command is read back by Alpine. The
23783 "_TMPFILE_" token (see below) overrides this default behavior.
23786 The filter's use is based on the configured "trigger" string. The
23787 format of a filter definition is:
23790 <CENTER><trigger> <command> <arguments></CENTER>
23793 You can specify as many filters as you wish, separating them with a comma.
23794 Each filter can have only one trigger and command. Thus, two trigger
23795 strings that invoke the same command require separate filter
23799 The "trigger" is simply text that, if found in the message,
23800 will invoke the associated command. If the trigger contains any space
23801 characters, it must be placed within quotes. Likewise, should you
23802 wish a filter to be invoked unconditionally, define the trigger as the
23803 null string, "" (two consecutive double-quote characters). If the
23804 trigger string is found anywhere in the text of the message the filter
23805 is invoked. Placing the trigger text within the tokens defined below
23806 changes where within the text the trigger must be before considering
23810 Trigger Modifying Tokens:
23812 <DT>_CHARSET(<VAR>string</VAR>)_</DT>
23813 <DD>This token tells Alpine to invoke the supplied command
23814 if the text is in a character set matching <VAR>string</VAR>
23815 (e.g., ISO-8859-2 or ISO-2022-JP).
23819 <DT>_LEADING(<VAR>string</VAR>)_</DT>
23820 <DD>This token tells Alpine to invoke the supplied command
23821 if the enclosed <VAR>string</VAR> is found to be the first
23822 non-whitespace text.
23823 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23824 the space character.
23827 <DT>_BEGINNING(<VAR>string</VAR>)_</DT>
23828 <DD>This token tells Alpine to invoke the supplied command
23829 if the enclosed <VAR>string</VAR> is found at the beginning
23830 of any line in the text.
23831 <BR>NOTE: Quotes are necessary if <VAR>string</VAR> contains
23832 the space character.
23837 The "command" and "arguments" portion is simply
23838 the command line to be invoked if the trigger string is found. Below
23839 are tokens that Alpine will recognize and replace with special values
23840 when the command is actually invoked.
23843 Command Modifying Tokens:
23847 <DD>When the command is executed, this token is
23848 replaced with the path and name of the temporary
23849 file containing the text to be filtered. Alpine
23850 expects the filter to replace this data with the
23854 NOTE: Use of this token implies that the text to
23855 be filtered is not piped into standard input of the
23856 executed command and its standard output is ignored.
23857 Alpine restores the tty modes before invoking the
23858 filter in case the filter interacts with the user
23859 via its own standard input and output.
23862 <DT>_RESULTFILE_</DT>
23863 <DD>When the command is executed, this token is
23864 replaced with the path and name of a temporary
23865 file intended to contain a status message from the
23866 filter. Alpine displays this in the message status
23870 <DT>_DATAFILE_</DT>
23871 <DD>When the command is executed, this token is
23872 replaced with the path and name of a temporary
23873 file that Alpine creates once per session and deletes
23874 upon exit. The file is intended to be used by the
23875 filter to store state information between instances
23879 <DT>_PREPENDKEY_</DT>
23880 <DD>When the command is executed, this token indicates that a random
23881 number will be passed down the input stream before the message text.
23882 This number could be used as a session key. It is sent in this way to
23883 improve security. The number is unique to the current Alpine session
23884 and is only generated once per session.
23888 <DD>When the filter is executed, this token tells Alpine not to repaint
23889 the screen while the command is being executed. This can be used with
23890 filters that do not interact with the user, and therefore repainting
23891 the screen is not necessary.
23897 <A HREF="h_config_disable_reset_disp"><!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></A> is related.
23899 Performance caveat/considerations:
23901 Testing for the trigger and invoking the filter doesn't come for free.
23902 There is overhead associated with searching for the trigger string, testing
23903 for the filter's existence and actually piping the text through the filter.
23904 The impact can be reduced if the Trigger Modifying Tokens above are
23907 <End of help on this topic>
23910 ====== h_config_sending_filter =====
23913 <TITLE>OPTION: <!--#echo var="VAR_sending-filters"--></TITLE>
23916 <H1>OPTION: <!--#echo var="VAR_sending-filters"--></H1>
23918 This option defines a list of text-filtering commands (programs and
23919 scripts) that may be selectively invoked to process a message just before
23920 it is sent. If set, the Composer's ^X (Send) command will allow you to
23921 select which filter (or none) to apply to the message before it is sent.
23922 For security reasons, the full path of the filter program must be
23926 Command Modifying Tokens:
23929 <DT>_RECIPIENTS_</DT>
23930 <DD>When the command is executed, this token is replaced
23931 with the space delimited list of recipients of the
23932 message being sent.
23937 When the command is executed, this token is
23938 replaced with the path and name of the temporary
23939 file containing the text to be filtered. Alpine
23940 expects the filter to replace this data with the
23944 NOTE: Use of this token implies that the text to
23945 be filtered is not piped into standard input of the
23946 executed command and its standard output is ignored.
23947 Alpine restores the tty modes before invoking the
23948 filter in case the filter interacts with the user
23949 via its own standard input and output.
23952 <DT>_RESULTFILE_</DT>
23953 <DD>When the command is executed, this token is
23954 replaced with the path and name of a temporary
23955 file intended to contain a status message from the
23956 filter. Alpine displays this in the message status
23960 <DT>_DATAFILE_</DT>
23961 <DD>When the command is executed, this token is replaced
23962 in the command line with the path and name of a
23963 temporary file that Alpine creates once per session
23964 and deletes upon exit. The file is intended to be
23965 used by the filter to store state information between
23966 instances of the filter.
23969 <DT>_PREPENDKEY_</DT>
23970 <DD>When the command is executed, this token indicates
23971 that a random number will be passed down the input
23972 stream before the message text. This number could
23973 be used as a session key. It is sent in this way
23974 to improve security. The number is unique to the
23975 current Alpine session and is only generated once per
23979 <DT>_INCLUDEALLHDRS_</DT>
23980 <DD>When the command is executed, this token indicates
23981 that the headers of the message will be passed down the input stream
23982 before the message text.
23985 <DT>_MIMETYPE_</DT>
23986 <DD>When the command is executed, this token is replaced in the
23987 command name with a temporary file name used to accept any new MIME
23988 Content-Type information necessitated by the output of the filter.
23989 Upon the filter's exit, if the file contains new MIME type
23990 information, Alpine verifies its format and replaces the outgoing
23991 message's MIME type information with that contained in the file. This
23992 is basically a cheap way of sending something other than Text/Plain.
23997 NOTE: Only the body text, which is visible in the Composer, is piped
23998 through this filter. Attachments are not sent to the filter.
24000 Sending filters are not used if the feature
24001 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set.
24004 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24006 <End of help on this topic>
24009 ====== h_config_keywords =====
24012 <TITLE>OPTION: <!--#echo var="VAR_keywords"--></TITLE>
24015 <H1>OPTION: <!--#echo var="VAR_keywords"--></H1>
24017 You may define your own set of keywords and optionally set them on a
24018 message by message basis.
24019 These are similar to the "Important" flag which the user
24020 may set using the Flag command.
24021 The difference is that the Important flag is always present for each folder.
24022 User-defined keywords are chosen by the user.
24023 You may set up the list of possible keywords here, or you may add keywords
24024 from the Flag Details screen that you
24025 can get to after typing the
24026 Flag (<!--chtml if pinemode="function_key"-->F11<!--chtml else-->*<!--chtml endif-->)
24028 After the keywords have been defined,
24029 then you use the <A HREF="h_common_flag">Flag command</A>
24030 to set or clear the keywords in each message.
24031 The behavior of the flag command may be modified by using the
24032 <A HREF="h_config_flag_screen_default">"<!--#echo var="FEAT_enable-flag-screen-implicitly"-->"</A> option or the
24033 <A HREF="h_config_flag_screen_kw_shortcut">"<!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"-->"</A> option.
24036 Keywords may be used when Selecting messages (Select Keyword).
24037 Keywords may also be used in the Patterns of Rules (Filters, Indexcolors, etc).
24038 Filter Rules may be used to set keywords automatically.
24039 Keywords may be displayed as part of the Subject of a message by using
24040 the SUBJKEY or SUBJKEYINIT tokens in the
24041 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
24042 The <A HREF="h_config_kw_braces"><!--#echo var="VAR_keyword-surrounding-chars"--></A>
24043 option may be used to modify the display of keywords using
24044 SUBJKEY and SUBJKEYINIT slightly.
24045 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
24046 screen by using the KEY or KEYINIT tokens.
24047 It is also possible to color keywords in the index using the
24048 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
24049 Keywords are not supported by all mail servers.
24052 You may give keywords nicknames if you wish.
24053 If the keyword definition you type in contains a SPACE character, then the
24054 actual value of the keyword is everything after the last SPACE and the
24055 nickname for that keyword is everything before the last SPACE.
24056 For example, suppose you are trying to interoperate with another email program
24057 that uses a particular keyword with an unpleasant name.
24058 Maybe it uses a keyword called
24060 <CENTER><SAMP>VendorName.SoftwareName.08</SAMP></CENTER>
24062 but for you that keyword means that the message is work-related.
24063 You could define a keyword to have the value
24065 <CENTER><SAMP>Work VendorName.SoftwareName.08</SAMP></CENTER>
24067 and then you would use the name "Work" when dealing with
24068 that keyword in Alpine.
24069 If you defined it as
24071 <CENTER><SAMP>My Work VendorName.SoftwareName.08</SAMP></CENTER>
24073 the nickname would be everything before the last SPACE, that is the nickname
24074 would be "My Work".
24076 Some commonly used keywords begin with dollar signs.
24077 This presents a slight complication, because the dollar sign is normally used
24079 <A HREF="h_news_config">environment variable expansion</A>
24080 in the Alpine configuration.
24081 In order to specify a keyword that begins with a dollar sign you must
24082 precede the dollar sign with a second dollar sign to escape its special
24084 For example, if you want to include the keyword
24086 <CENTER><SAMP>$Label1</SAMP></CENTER>
24088 as one of your possible keywords, you must enter the text
24090 <CENTER><SAMP>$$Label1</SAMP></CENTER>
24095 There are a couple limitations.
24096 First, not all servers support keywords.
24097 Second, some servers (including the IMAP server included with Alpine)
24098 have a per folder limit on the number of keywords that may be defined.
24099 This count commonly includes every keyword you have ever used in the
24100 folder, even if it is no longer being used.
24101 In other words, you can add keywords but you cannot remove them easily.
24102 If you have changed keywords over the life of a folder and find that
24103 you have reached such a limit, one possible solution might be to copy
24104 all of the messages to a newly created folder (using Alpine) and then
24105 delete the original and rename the new folder.
24106 The reason this might work is that only the keywords currently set in
24107 any of the messages will be used in the new folder, hopefully putting you
24112 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24114 <End of help on this topic>
24117 ====== h_config_alt_addresses =====
24120 <TITLE>OPTION: <!--#echo var="VAR_alt-addresses"--></TITLE>
24123 <H1>OPTION: <!--#echo var="VAR_alt-addresses"--></H1>
24125 This option provides a place for you to list alternate email addresses
24127 Each address in the list should be the actual email address part of an
24128 address, without the full name field or the angle brackets.
24132 <CENTER><SAMP>user@example.com</SAMP></CENTER>
24135 The matching is case-insensitive, so this would match any of
24136 <SAMP>User@example.com</SAMP>, <SAMP>user@Example.Com</SAMP>, or
24137 <SAMP>USER@EXAMPLE.COM</SAMP> as well.
24140 If set, the option affects the behavior of the Reply
24141 command and the "+" symbol in the MESSAGE INDEX, which denotes that
24142 a message has been addressed specifically to you.
24145 In the default INDEX display
24146 the personal name (or email address) of
24147 the person listed in the message's "From:" header
24148 field is usually displayed except when that address is yours or one of your
24149 alternate addresses.
24150 In that case you will usually see the name of
24151 the first person specified in the
24152 message's "To:" header field
24153 with the prefix "To: " prepended.
24156 With respect to Reply, the reply-to-all option will exclude addresses
24161 <A HREF="h_config_copy_to_to_from"><!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></A>
24162 is somewhat related to this option.
24165 In addition to a list of actual addresses,
24166 you may use regular expressions (as used with egrep with the ignore case flag)
24167 to describe the addresses you want to match.
24168 Alpine will somewhat arbitrarily interpret your entry as a regular
24169 expression if it contains any of the characters
24170 *, |, +, ?, {, [, ^, $, or \.
24171 Otherwise, it will be treated literally.
24173 <a href="h_config_disable_regex"><!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></a>
24174 may be used to turn off regular expression processing regardless of whether or not
24175 special characters appear in the entry.
24178 A description of how regular expressions work is beyond the
24179 scope of this help text, but some examples follow.
24185 <CENTER><SAMP>.*@example.com</SAMP></CENTER>
24188 in the <!--#echo var="VAR_alt-addresses"--> list would mean that any
24189 address with a domain name of <SAMP>example.com</SAMP> (such as
24190 <SAMP>fred@example.com</SAMP> or <SAMP>wilma@example.com</SAMP>) will be considered
24191 one of your alternate addresses.
24192 Strictly speaking, the dot in <SAMP>example.com</SAMP> ought to be escaped with
24193 a backslash, as in <SAMP>example\.com</SAMP>, and a dollar sign anchor ought
24194 to come at the end of the expression to prevent a match of <SAMP>example.com.org</SAMP>.
24195 Complicating things further, the dollar sign
24196 is special in the Alpine configuration (it signifies environment variable expansion)
24197 so the dollar sign should be doubled or backslash escaped for Alpine's sake.
24198 Quotes around the whole expression will not escape the dollar sign successfully.
24199 So this example should look like
24202 <CENTER><SAMP>.*@example\.com$$</SAMP></CENTER>
24209 <CENTER><SAMP>^fred[0-9]*@example.com$$</SAMP></CENTER>
24213 <SAMP>fred3@example.com</SAMP> or <SAMP>fred17@example.com</SAMP> as well
24214 as <SAMP>fred@example.com</SAMP>.
24217 You could match all addresses that look like
24218 <SAMP>fred+stuff@example.com</SAMP> for any value of <SAMP>stuff</SAMP> with the
24222 <CENTER><SAMP>^fred\+.*@example.com$$</SAMP></CENTER>
24225 Notice that you have to escape the plus sign with a backslash because plus
24226 is a special character in regular expressions.
24227 If you wanted to match plain <SAMP>fred</SAMP> as well as <SAMP>fred+stuff</SAMP>
24231 <CENTER><SAMP>^fred(()|\+.*)@example.com$$</SAMP></CENTER>
24234 would do it, but it would be easier to just add fred@example.com as a
24238 One more example, a match of all first-level subdomains, is given by
24241 <CENTER><SAMP>^fred@[[:alnum:]_-]*\.example\.com$$</SAMP></CENTER>
24245 Because the regular expression matching is based on an old library
24246 (<SAMP>hs_regex</SAMP>) the regular expressions might not work exactly as you expect,
24247 but they should be close.
24251 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24253 <End of help on this topic>
24256 ====== h_config_abook_formats =====
24259 <TITLE>OPTION: <!--#echo var="VAR_addressbook-formats"--></TITLE>
24262 <H1>OPTION: <!--#echo var="VAR_addressbook-formats"--></H1>
24264 This option specifies the format that address books are displayed in.
24265 Normally, address books are displayed with the nicknames in the first
24266 column, the fullnames in the second column, and addresses in the third
24267 column. The system figures out reasonable defaults for the widths of
24268 the columns. An address book may be given a different format by
24269 listing special tokens in the order you want them to display. The
24270 possible tokens are NICKNAME, FULLNAME, ADDRESS, FCC, and COMMENT.
24271 So, for example, to get the default behavior you could list
24274 <CENTER><!--#echo var="VAR_addressbook-formats"-->=NICKNAME FULLNAME ADDRESS</CENTER>
24277 (You can also use the token DEFAULT to get the default behavior for
24278 an address book format.)
24281 The tokens are separated by spaces. "<!--#echo var="VAR_addressbook-formats"-->"
24282 is a list, so if you have more than one address book you may have a
24283 separate format for each by putting its format at the corresponding
24284 location in the "<!--#echo var="VAR_addressbook-formats"-->" list.
24288 Listed first are the personal address books, then the global address
24289 books. So, if you have two personal address books and one global
24290 address book, you may have up to three formats in the
24291 "<!--#echo var="VAR_addressbook-formats"-->" list. If
24292 "<!--#echo var="VAR_addressbook-formats"-->" doesn't have as many elements as there
24293 are address books, the last element is used repeatedly.
24297 Each of the tokens may also be optionally followed by parentheses with
24298 either a number or a percentage inside the parentheses. For example,
24299 <SAMP>FULLNAME(13)</SAMP> means to allocate 13 characters of space to
24300 the fullnames column, <SAMP>FULLNAME(20%)</SAMP> means to allocate 20%
24301 of the available space (the screen width minus the space for
24302 inter-column spaces) to the fullnames column, while plain
24303 <SAMP>FULLNAME</SAMP> means the system will attempt to figure out a
24304 reasonable number of columns.
24307 There are always 2 spaces between every column, so if you use
24308 fixed column widths (like 13) you should remember to take that into
24313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24315 <End of help on this topic>
24318 ====== h_config_set_index_format =====
24321 <TITLE>Set Index Format</TITLE>
24324 <H1>Set Index Format</H1>
24326 This option is used to customize the content of lines in the
24327 <A HREF="h_mail_index">MESSAGE INDEX screen</A>.
24328 This action works exactly like the regular
24329 "<!--#echo var="VAR_index-format"-->" option in the Setup/Config screen,
24330 except that you can have a folder-specific value for it if you specify it here.
24331 Consult the help for
24332 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>"
24333 for more information.
24337 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24339 <End of help on this topic>
24342 ====== h_config_index_format =====
24345 <TITLE>OPTION: <!--#echo var="VAR_index-format"--></TITLE>
24348 <H1>OPTION: <!--#echo var="VAR_index-format"--></H1>
24350 This option is used to customize the content of lines in the
24351 <A HREF="h_mail_index">MESSAGE INDEX screen</A>. Each line is intended
24352 to convey some amount of immediately relevant information about each
24353 message in the current folder.
24356 Alpine provides a pre-defined set of informational fields with
24357 reasonable column widths automatically computed. You can, however,
24358 replace this default set by listing special tokens in the order you
24359 want them displayed.
24362 The list of available tokens is
24363 <A HREF="h_index_tokens">here</A>.
24366 Spaces are used to separate listed tokens. Additionally, you can
24367 specify how much of the screen's width the token's associated data
24368 should occupy on the index line by appending to the token a pair of
24369 parentheses enclosing either a number or percentage. For example,
24370 "SUBJECT(13)" means to allocate 13 characters of space to the subject
24371 column, and "SUBJECT(20%)" means to
24372 allocate 20% of the available space
24373 to the subjects column, while plain "SUBJECT" means the system will
24374 attempt to figure out a reasonable amount of space.
24377 There is always one space between every pair of columns, so if you use fixed
24378 column widths (like 13) you should remember to take that into account.
24379 Several of the fields are virtually fixed-width, so it doesn't make
24380 much sense to specify the width for them. The fields STATUS,
24381 FULLSTATUS, IMAPSTATUS, MSGNO, the DATE fields, SIZE,
24382 and DESCRIPSIZE all fall into that category.
24383 You <EM>may</EM> specify widths for those if you wish, but
24384 you're probably better off letting the system pick those widths. <P>
24387 The default is equivalent to:
24390 <CENTER><SAMP>STATUS MSGNO SMARTDATETIME24 FROMORTO(33%) SIZENARROW SUBJKEY(67%)</SAMP></CENTER>
24393 This means that the four fields without percentages will be allocated
24394 first, and then 33% and 67% of the <EM>remaining</EM> space will go to
24395 the from and subject fields. If one of those two fields is specified
24396 as a percentage and the other is left for the system to choose, then
24397 the percentage is taken as an absolute percentage of the screen, not
24398 of the space remaining after allocating the first four columns. It
24399 doesn't usually make sense to do it that way. If you leave off all
24400 the widths, then the subject and from fields (if both are present) are
24401 allocated space in a 2 to 1 ratio, which is almost exactly the same as
24405 What you are most likely to do with this configuration option is to
24406 specify which fields appear at all, which order they appear in, and the
24407 percentage of screen that is used for the from and subject fields if you
24408 don't like the 2 to 1 default.
24411 If you want to retain the default format that Pine 4.64 had, use
24414 <CENTER><SAMP><!--#echo var="VAR_index-format"-->=STATUS MSGNO DATE FROMORTO(33%) SIZE SUBJKEY(67%)</SAMP></CENTER>
24416 <EM>and</EM> set the feature
24417 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>.
24419 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24421 <End of help on this topic>
24424 ====== h_config_reply_intro =====
24427 <TITLE>OPTION: <!--#echo var="VAR_reply-leadin"--></TITLE>
24430 <H1>OPTION: <!--#echo var="VAR_reply-leadin"--></H1>
24432 This option is used to customize the content of the introduction line
24433 that is included when replying to a message and including the original
24434 message in the reply.
24435 The normal default (what you will get if you delete this variable) looks
24438 <CENTER><SAMP>On Sat, 24 Oct 1998, Fred Flintstone wrote:</SAMP></CENTER>
24440 where the day of the week is only included if it is available in the
24442 You can replace this default with text of your own.
24443 The text may contain tokens that are replaced with text
24444 that depends on the message you are replying to.
24445 For example, the default is equivalent to:
24447 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24450 Since this variable includes regular text mixed with special tokens
24451 the tokens have to be surrounded by underscore characters.
24452 For example, to use the token "<SAMP>PREFDATE</SAMP>"
24453 you would need to use "<SAMP>_PREFDATE_</SAMP>",
24454 not "<SAMP>PREFDATE</SAMP>".
24456 The list of available tokens is
24457 <A HREF="h_index_tokens">here</A>.
24460 By default, the text is all on a single line and is followed by a blank line.
24461 If your "<!--#echo var="VAR_reply-leadin"-->" turns out to be longer
24462 than 80 characters when replying to a particular message, it is shortened.
24463 However, if you use the token
24465 <CENTER><SAMP>_NEWLINE_</SAMP></CENTER>
24468 anywhere in the value, no end of line or blank line is appended, and no
24469 shortening is done.
24470 The _NEWLINE_ token may be used to get rid of the blank line following
24471 the text, to add more blank lines, or to form a multi-line
24472 "<!--#echo var="VAR_reply-leadin"-->".
24473 To clarify how _NEWLINE_ works recall that the default value is:
24475 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:</SAMP></CENTER>
24478 That is equivalent to
24480 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE__NEWLINE_</SAMP></CENTER>
24483 In the former case, two newlines are added automatically because
24484 no _NEWLINE_ token appears in the value of the option (for backwards
24485 compatibility). In the latter case, the newlines are explicit.
24486 If you want to remove the blank line that follows the
24487 "<!--#echo var="VAR_reply-leadin"-->" text use a single
24488 _NEWLINE_ token like
24490 <CENTER><SAMP>On _DAYDATE_, _FROM_ wrote:_NEWLINE_</SAMP></CENTER>
24493 Because of the backwards compatibility problem, it is not possible to
24494 remove all of the ends of lines, because then there will be no _NEWLINE_ tokens
24495 and that will cause the automatic adding of two newlines!
24496 If you want, you may embed newlines in the middle of the text, as well,
24497 producing a multi-line "<!--#echo var="VAR_reply-leadin"-->".
24500 By default, no attempt is made to localize the date.
24501 If you prefer a localized form you may find that one of the tokens
24502 _PREFDATE_ or _PREFDATETIME_ is a satisfactory substitute.
24503 If you want more control one of the many other date tokens, such as _DATEISO_,
24507 For the adventurous, there is a way to conditionally include text based
24508 on whether or not a token would result in specific replacement text.
24509 For example, you could include some text based on whether or not
24510 the _NEWS_ token would result in any newsgroups if it was used.
24511 It's explained in detail
24512 <A HREF="h_reply_token_conditionals">here</A>.
24515 In the very unlikely event that you want to include a literal token
24516 in the introduction line you must precede it with a backslash character.
24519 <CENTER><SAMP>\_DAYDATE_ = _DAYDATE_</SAMP></CENTER>
24521 would produce something like
24523 <CENTER><SAMP>_DAYDATE_ = Sat, 24 Oct 1998</SAMP></CENTER>
24525 It is not possible to have a literal backslash followed by an expanded token.
24528 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24530 <End of help on this topic>
24533 ====== h_config_remote_abook_history =====
24536 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-history"--></TITLE>
24539 <H1>OPTION: <!--#echo var="VAR_remote-abook-history"--></H1>
24541 Sets how many extra copies of
24542 remote address book
24543 data will be kept in each remote address book folder.
24544 The default is three.
24545 These extra copies are simply old versions of the data. Each time a change
24546 is made a new copy of the address book data is appended to the folder. Old
24547 copies are trimmed, if possible, when Alpine exits.
24548 An old copy can be put back into use by
24549 deleting and expunging newer versions of the data from the folder.
24550 Don't delete the first message from the folder. It is a special header
24551 message for the remote address book and it must be there.
24552 This is to prevent regular folders from being used as remote address book
24553 folders and having their data destroyed.
24555 This option is also used to determine how many extra copies of remote
24556 Alpine configuration files are kept.
24559 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24561 <End of help on this topic>
24564 ====== h_config_remote_abook_validity =====
24567 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-validity"--></TITLE>
24570 <H1>OPTION: <!--#echo var="VAR_remote-abook-validity"--></H1>
24572 Sets the minimum number of minutes that a
24573 remote address book will be considered up to date.
24574 Whenever an entry contained in a remote address book is used,
24575 if more than this many minutes have
24576 passed since the last check the remote server will be queried to see if the
24577 address book has changed.
24578 If it has changed, the local copy is updated.
24579 The default value is five minutes.
24580 The special value of -1 means never check.
24581 The special value of zero means only check when the address book is first
24584 No matter what the value, the validity check is always done when the
24585 address book is about to be changed by the user.
24586 The check can be initiated manually by typing <EM>^L</EM> (Ctrl-L)
24587 while in the address book maintenance screen for the remote address book.
24590 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24592 <End of help on this topic>
24595 ====== h_config_user_input_timeo =====
24598 <TITLE>OPTION: <!--#echo var="VAR_user-input-timeout"--></TITLE>
24601 <H1>OPTION: <!--#echo var="VAR_user-input-timeout"--></H1>
24603 If this is set to an integer greater than zero, then this is the number
24604 of <EM>hours</EM> to wait for user input before Alpine times out.
24606 in the midst of composing a message or is waiting for user response to
24607 a question, then it will not timeout.
24608 However, if Alpine is sitting idle waiting for
24609 the user to tell it what to do next and the user does not give any
24610 input for this many hours, Alpine will exit.
24611 No expunging or moving of read
24612 messages will take place.
24613 It will exit similarly to the way it would exit
24614 if it received a hangup signal.
24615 This may be useful for cleaning up unused Alpine sessions that have been
24616 forgotten by their owners.
24617 The Alpine developers envision system administrators
24618 setting this to a value of several hours (24?) so that it won't surprise
24619 a user who didn't want to be disconnected.
24622 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24624 <End of help on this topic>
24627 ====== h_config_ssh_open_timeo =====
24630 <TITLE>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></TITLE>
24633 <H1>OPTION: <!--#echo var="VAR_ssh-open-timeout"--></H1>
24635 Sets the time in seconds that Alpine will
24636 attempt to open a UNIX secure shell connection.
24637 The default is 15, the minimum non-zero value is 5,
24638 and the maximum is unlimited. If this is set to zero ssh connections
24639 will be completely disabled.
24642 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24644 <End of help on this topic>
24647 ====== h_config_rsh_open_timeo =====
24650 <TITLE>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></TITLE>
24653 <H1>OPTION: <!--#echo var="VAR_rsh-open-timeout"--></H1>
24655 Sets the time in seconds that Alpine will
24656 attempt to open a UNIX remote shell connection.
24657 The default is 15, the minimum non-zero value is 5,
24658 and the maximum is unlimited. If this is set to zero rsh connections
24659 will be completely disabled.
24660 This might be useful if rsh connections will never work in your environment
24661 but are causing delays due to firewalls or some other reason.
24664 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24666 <End of help on this topic>
24669 ====== h_config_tcp_open_timeo =====
24672 <TITLE>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></TITLE>
24675 <H1>OPTION: <!--#echo var="VAR_tcp-open-timeout"--></H1>
24677 Sets the time in seconds that Alpine will
24678 attempt to open a network connection. The default is 30, the minimum is 5,
24679 and the maximum is system defined (typically 75). If a connection has not
24680 completed within this many seconds Alpine will give up and consider it a
24684 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24686 <End of help on this topic>
24689 ====== h_config_tcp_readwarn_timeo =====
24692 <TITLE>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></TITLE>
24695 <H1>OPTION: <!--#echo var="VAR_tcp-read-warning-timeout"--></H1>
24697 Sets the time in seconds that Alpine will
24698 wait for a network read before warning you that things are moving slowly
24699 and possibly giving you the option to break the connection.
24700 The default is 15 seconds. The minimum is 5 seconds and the maximumn is
24703 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24706 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24708 <End of help on this topic>
24711 ====== h_config_tcp_writewarn_timeo =====
24714 <TITLE>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></TITLE>
24717 <H1>OPTION: <!--#echo var="VAR_tcp-write-warning-timeout"--></H1>
24719 Sets the time in seconds that Alpine will
24720 wait for a network write before warning you that things are moving slowly
24721 and possibly giving you the option to break the connection.
24722 The default is 0 which means it is unset. If set to a non-zero value, the
24723 minimum is 5 and the maximum is 1000.
24725 Related option: <A HREF="h_config_tcp_query_timeo"><!--#echo var="VAR_tcp-query-timeout"--></A>.
24728 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24730 <End of help on this topic>
24733 ====== h_config_tcp_query_timeo =====
24736 <TITLE>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></TITLE>
24739 <H1>OPTION: <!--#echo var="VAR_tcp-query-timeout"--></H1>
24741 When Alpine times out a network read or write it will normally just display
24742 a message saying "Still waiting".
24743 However, if enough time has elapsed since it started waiting it will offer
24744 to let you break the connection.
24745 That amount of time is set by this option, which defaults to 60 seconds,
24746 has a minimum of 5 seconds, and a maximum of 1000 seconds.
24749 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24751 <End of help on this topic>
24754 ====== h_config_incoming_folders =====
24757 <TITLE>OPTION: <!--#echo var="VAR_incoming-folders"--></TITLE>
24760 <H1>OPTION: <!--#echo var="VAR_incoming-folders"--></H1>
24762 This is a list of one or more folders other than <EM>INBOX</EM> that
24763 may receive new messages.
24764 It is related to the
24765 <A HREF="h_config_enable_incoming">"<!--#echo var="FEAT_enable-incoming-folders"-->"</A>
24767 This variable is normally manipulated with the Add, Delete, and Rename
24768 commands in the FOLDER LIST for the Incoming Message Folders collection.
24771 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24773 <End of help on this topic>
24776 ====== h_config_folder_spec =====
24779 <TITLE>OPTION: <!--#echo var="VAR_folder-collections"--></TITLE>
24782 <H1>OPTION: <!--#echo var="VAR_folder-collections"--></H1>
24784 This is a list of one or more collections where saved mail is stored.
24785 The first collection in this list is the default
24786 collection for <EM>Save</EM>s,
24787 including <A HREF="h_config_default_fcc"><!--#echo var="VAR_default-fcc"--></A>.
24789 This variable is normally manipulated using the Setup/collectionList screen.
24792 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24794 <End of help on this topic>
24797 ====== h_config_news_spec =====
24800 <TITLE>OPTION: <!--#echo var="VAR_news-collections"--></TITLE>
24803 <H1>OPTION: <!--#echo var="VAR_news-collections"--></H1>
24805 This is a list of collections where news folders are located.
24807 This variable is normally manipulated using the Setup/collectionList screen.
24810 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24812 <End of help on this topic>
24815 ====== h_config_address_book =====
24818 <TITLE>OPTION: <!--#echo var="VAR_address-book"--></TITLE>
24821 <H1>OPTION: <!--#echo var="VAR_address-book"--></H1>
24823 A list of personal address books.
24824 Each entry in the list is an
24825 optional nickname followed by a pathname or file name relative to the home
24827 The nickname is separated from the rest of the line with whitespace.
24828 Instead of a local pathname or file name, a remote folder name can be given.
24829 This causes the address book to
24830 be a Remote address book.
24832 Use the Setup/AddressBook screen to modify this variable.
24835 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24837 <End of help on this topic>
24840 ====== h_config_glob_addrbook =====
24843 <TITLE>OPTION: <!--#echo var="VAR_global-address-book"--></TITLE>
24846 <H1>OPTION: <!--#echo var="VAR_global-address-book"--></H1>
24848 A list of shared address books. Each entry in the list is an
24849 optional nickname followed by a pathname or file name relative to the home
24851 A SPACE character separates the nickname from the rest of the line.
24852 Instead of a local pathname or file name, a remote folder name can be given.
24853 This causes the address book to
24854 be a Remote address book.
24855 Global address books are
24856 defined to be ReadOnly.
24858 Use the Setup/AddressBook screen to modify this variable.
24861 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24863 <End of help on this topic>
24866 ====== h_config_last_vers =====
24869 <TITLE>OPTION: <!--#echo var="VAR_last-version-used"--></TITLE>
24872 <H1>OPTION: <!--#echo var="VAR_last-version-used"--></H1>
24874 This is set automatically by Alpine.
24875 It is used to keep track of the last version of Alpine that
24876 was run by the user.
24877 Whenever the version number increases, a new version message is printed out.
24878 This may not be set in the system-wide configuration files.
24881 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24883 <End of help on this topic>
24886 ====== h_config_printer =====
24889 <TITLE>OPTION: Printer</TITLE>
24892 <H1>OPTION: Printer</H1>
24894 Your default printer selection.
24896 Use the Setup/Printer screen to modify this variable.
24899 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24901 <End of help on this topic>
24904 ====== h_config_print_cat =====
24907 <TITLE>OPTION: <!--#echo var="VAR_personal-print-category"--></TITLE>
24910 <H1>OPTION: <!--#echo var="VAR_personal-print-category"--></H1>
24912 This is an internal Alpine variable.
24913 It will be equal to 1, 2, or 3 depending on whether the default printer is
24914 attached, standard, or a personal print command.
24916 Use the Setup/Printer screen to modify this variable.
24919 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24921 <End of help on this topic>
24924 ====== h_config_print_command =====
24927 <TITLE>OPTION: <!--#echo var="VAR_personal-print-command"--></TITLE>
24930 <H1>OPTION: <!--#echo var="VAR_personal-print-command"--></H1>
24932 List of personal print commands.
24934 Use the Setup/Printer screen to modify this variable.
24937 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24939 <End of help on this topic>
24942 ====== h_config_pat_old =====
24945 <TITLE>OPTION: Patterns</TITLE>
24948 <H1>OPTION: Patterns</H1>
24950 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by the
24951 options Patterns-Roles, Patterns-Filters, Patterns-Scores, Patterns-Indexcolors,
24952 and Patterns-Other.
24953 Patterns-Scores and Patterns-Filters have been replaced since then by
24954 Patterns-Scores2 and Patterns-Filters2.
24956 Use the Setup/Rules screens to modify these variable.
24959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24961 <End of help on this topic>
24964 ====== h_config_pat_roles =====
24967 <TITLE>OPTION: <!--#echo var="VAR_patterns-roles"--></TITLE>
24970 <H1>OPTION: <!--#echo var="VAR_patterns-roles"--></H1>
24972 List of rules used for roles.
24973 The option Patterns is obsolete in Alpine and in Pine 4.50 and later, replaced by this and
24976 Use the Setup/Rules/Roles screen to modify this variable.
24979 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24981 <End of help on this topic>
24984 ====== h_config_pat_filts =====
24987 <TITLE>OPTION: <!--#echo var="VAR_patterns-filters2"--></TITLE>
24990 <H1>OPTION: <!--#echo var="VAR_patterns-filters2"--></H1>
24992 List of rules used for filters.
24994 Use the Setup/Rules/Filters screen to modify this variable.
24997 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
24999 <End of help on this topic>
25002 ====== h_config_pat_scores =====
25005 <TITLE>OPTION: <!--#echo var="VAR_patterns-scores2"--></TITLE>
25008 <H1>OPTION: <!--#echo var="VAR_patterns-scores2"--></H1>
25010 List of rules used for scoring.
25012 Use the Setup/Rules/SetScores screen to modify this variable.
25015 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25017 <End of help on this topic>
25020 ====== h_config_pat_other =====
25023 <TITLE>OPTION: <!--#echo var="VAR_patterns-other"--></TITLE>
25026 <H1>OPTION: <!--#echo var="VAR_patterns-other"--></H1>
25028 List of rules used for miscellaneous configuration.
25030 Use the Setup/Rules/Other screen to modify this variable.
25033 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25035 <End of help on this topic>
25038 ====== h_config_pat_incols =====
25041 <TITLE>OPTION: patterns-indexcolors</TITLE>
25044 <H1>OPTION: patterns-indexcolors</H1>
25046 List of rules used for coloring lines in the index.
25048 Use the Setup/Rules/Indexcolor screen to modify this variable.
25051 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25053 <End of help on this topic>
25056 ====== h_config_pat_srch =====
25059 <TITLE>OPTION: patterns-search</TITLE>
25062 <H1>OPTION: patterns-search</H1>
25064 List of rules used only for searching with the Select command in the MESSAGE INDEX.
25066 Use the Setup/Rules/searCh screen to modify this variable.
25069 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25071 <End of help on this topic>
25074 ====== h_config_font_name =====
25077 <TITLE>OPTION: Font Name</TITLE>
25080 <H1>OPTION: Font Name</H1>
25084 Name of normal font.
25086 Use the pulldown Config menu to modify this variable.
25089 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25091 <End of help on this topic>
25094 ====== h_config_font_size =====
25097 <TITLE>OPTION: Font Size</TITLE>
25100 <H1>OPTION: Font Size</H1>
25104 Size of normal font.
25106 Use the pulldown Config menu to modify this variable.
25109 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25111 <End of help on this topic>
25114 ====== h_config_font_style =====
25117 <TITLE>OPTION: Font Style</TITLE>
25120 <H1>OPTION: Font Style</H1>
25124 Style of normal font.
25126 Use the pulldown Config menu to modify this variable.
25129 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25131 <End of help on this topic>
25134 ====== h_config_font_char_set =====
25137 <TITLE>OPTION: Font Character Set</TITLE>
25140 <H1>OPTION: Font Character Set</H1>
25144 Character set of normal font.
25146 Use the pulldown Config menu to modify this variable.
25149 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25151 <End of help on this topic>
25154 ====== h_config_print_font_name =====
25157 <TITLE>OPTION: Print-Font-Name</TITLE>
25160 <H1>OPTION: Print-Font-Name</H1>
25164 Name of printer font.
25166 Use the pulldown Config menu to modify this variable.
25169 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25171 <End of help on this topic>
25174 ====== h_config_print_font_size =====
25177 <TITLE>OPTION: Print-Font-Size</TITLE>
25180 <H1>OPTION: Print-Font-Size</H1>
25184 Size of printer font.
25186 Use the pulldown Config menu to modify this variable.
25189 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25191 <End of help on this topic>
25194 ====== h_config_print_font_style =====
25197 <TITLE>OPTION: Print-Font-Style</TITLE>
25200 <H1>OPTION: Print-Font-Style</H1>
25204 Style of printer font.
25206 Use the pulldown Config menu to modify this variable.
25209 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25211 <End of help on this topic>
25214 ====== h_config_print_font_char_set =====
25217 <TITLE>OPTION: Print-Font-Char-Set</TITLE>
25220 <H1>OPTION: Print-Font-Char-Set</H1>
25224 Character set of printer font.
25226 Use the pulldown Config menu to modify this variable.
25229 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25231 <End of help on this topic>
25234 ====== h_config_window_position =====
25237 <TITLE>OPTION: Window-Position</TITLE>
25240 <H1>OPTION: Window-Position</H1>
25244 Position on the screen of the Alpine window.
25246 Alpine normally maintains this variable itself, and it is set automatically.
25247 This variable is provided to those who wish to use the same window position
25248 across different machines from the same configuration.
25249 <A HREF="h_config_winpos_in_config"><!--#echo var="FEAT_store-window-position-in-config"--></A>
25250 must also be set for this setting to be used.
25252 The format for this variable is of the form: <CODE>CxR+X+Y</CODE>, where
25253 C is the number of columns, R is the number of rows, and X and Y specify the
25254 top left corner of the window.
25257 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25259 <End of help on this topic>
25262 ====== h_config_cursor_style =====
25265 <TITLE>OPTION: Cursor Style</TITLE>
25268 <H1>OPTION: Cursor Style</H1>
25274 Use the pulldown Config menu to modify this variable.
25277 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25279 <End of help on this topic>
25282 ====== h_config_ldap_servers =====
25285 <TITLE>OPTION: <!--#echo var="VAR_ldap-servers"--></TITLE>
25288 <H1>OPTION: <!--#echo var="VAR_ldap-servers"--></H1>
25290 List of LDAP servers and associated data.
25292 Use the Setup/Directory screen to modify this variable.
25295 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25297 <End of help on this topic>
25300 ====== h_config_sendmail_path =====
25303 <TITLE>OPTION: <!--#echo var="VAR_sendmail-path"--></TITLE>
25306 <H1>OPTION: <!--#echo var="VAR_sendmail-path"--></H1>
25308 This names the path to an
25309 alternative program, and any necessary arguments, to be used in posting
25310 mail messages. See the Technical notes for more information.
25313 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25315 <End of help on this topic>
25318 ====== h_config_oper_dir =====
25321 <TITLE>OPTION: <!--#echo var="VAR_operating-dir"--></TITLE>
25324 <H1>OPTION: <!--#echo var="VAR_operating-dir"--></H1>
25326 This names the root of the
25327 tree to which you are restricted when reading and writing folders and
25328 files. It is usually used in the system-wide,
25329 <EM>fixed</EM> configuration file.
25332 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25334 <End of help on this topic>
25337 ====== h_config_rshpath =====
25340 <TITLE>OPTION: <!--#echo var="VAR_rsh-path"--></TITLE>
25343 <H1>OPTION: <!--#echo var="VAR_rsh-path"--></H1>
25345 Sets the name of the command used to open a UNIX remote shell
25346 connection. The default is typically <CODE>/usr/ucb/rsh</CODE>.
25349 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25351 <End of help on this topic>
25354 ====== h_config_rshcmd =====
25357 <TITLE>OPTION: <!--#echo var="VAR_rsh-command"--></TITLE>
25360 <H1>OPTION: <!--#echo var="VAR_rsh-command"--></H1>
25362 Sets the format of the command used to
25363 open a UNIX remote shell connection. The default is
25364 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25365 provided command. The first is for the command's pathname, the second is
25366 for the host to connnect to, the third is for the user to connect as, and
25367 the fourth is for the connection method (typically <CODE>imap</CODE>).
25370 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25372 <End of help on this topic>
25375 ====== h_config_sshpath =====
25378 <TITLE>OPTION: <!--#echo var="VAR_ssh-path"--></TITLE>
25381 <H1>OPTION: <!--#echo var="VAR_ssh-path"--></H1>
25383 Sets the name of the command used to open a UNIX secure shell
25384 connection. The default is typically <CODE>/usr/bin/ssh</CODE>.
25387 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25389 <End of help on this topic>
25392 ====== h_config_sshcmd =====
25395 <TITLE>OPTION: <!--#echo var="VAR_ssh-command"--></TITLE>
25398 <H1>OPTION: <!--#echo var="VAR_ssh-command"--></H1>
25400 Sets the format of the command used to
25401 open a UNIX secure shell connection. The default is
25402 "%s %s -l %s exec /etc/r%sd". All four "%s" entries MUST exist in the
25403 provided command. The first is for the command's pathname, the second is
25404 for the host to connnect to, the third is for the user to connect as, and
25405 the fourth is for the connection method (typically <CODE>imap</CODE>).
25408 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25410 <End of help on this topic>
25413 ====== h_config_new_ver_quell =====
25416 <TITLE>OPTION: <!--#echo var="VAR_new-version-threshold"--></TITLE>
25419 <H1>OPTION: <!--#echo var="VAR_new-version-threshold"--></H1>
25421 When a new version of Alpine is run for the first time it offers a
25422 special explanatory screen to the user upon startup. This option
25423 helps control when and if that special screen appears for users that
25424 have previously run Alpine. It takes as its value an Alpine version
25425 number. Alpine versions less than the specified value will supress this
25426 special screen while versions equal to or greater than that specified
25427 will behave normally.
25430 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25432 <End of help on this topic>
25435 ====== h_config_disable_drivers =====
25438 <TITLE>OPTION: <!--#echo var="VAR_disable-these-drivers"--></TITLE>
25441 <H1>OPTION: <!--#echo var="VAR_disable-these-drivers"--></H1>
25443 This variable is a list of mail drivers that will be disabled.
25444 The candidates for disabling are listed below.
25445 There may be more in the future if you compile Alpine with
25446 a newer version of the c-client library.
25463 The <EM>mbox</EM> driver enables the following behavior: if there is a
25464 file called <CODE>mbox</CODE>
25465 in your home directory, and if that file is either empty or in Unix mailbox
25466 format, then every time you open <EM>INBOX</EM> the <EM>mbox</EM> driver
25467 will automatically transfer mail from the system mail spool directory into the
25468 <CODE>mbox</CODE> file and
25469 delete it from the spool directory. If you disable the <EM>mbox</EM> driver,
25470 this will not happen.
25473 It is not recommended to disable the driver that supports the system default
25474 mailbox format. On most non-SCO systems, that driver is the
25475 <EM>unix</EM> driver.
25476 On most SCO systems, it is the <EM>mmdf</EM> driver.
25477 The system default driver may be
25478 configured to something else on your system; check with your system manager
25479 for additional information.
25482 It is most likely not very useful for you to disable any of the drivers other
25483 than possibly <EM>mbox</EM>.
25484 You could disable some of the others if you know for
25485 certain that you don't need them but the performance gain in doing so
25489 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25491 <End of help on this topic>
25494 ====== h_config_disable_auths =====
25497 <TITLE>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></TITLE>
25500 <H1>OPTION: <!--#echo var="VAR_disable-these-authenticators"--></H1>
25502 This variable is a list of SASL (Simple Authentication and Security
25503 Layer) authenticators that will be disabled.
25504 SASL is a mechanism for
25505 authenticating to IMAP, POP3, SMTP, and other network servers.
25508 Alpine matches its list of supported authenticators with the server to
25509 determine the most secure authenticator that is supported by both.
25510 If no matching authenticators are found, Alpine will revert to plaintext
25511 login (or, in the case of SMTP, will be unable to authenticate at all).
25513 The candidates for disabling can be found <A HREF="X-Alpine-Config:">here</A>.
25516 Normally, you will not disable any authenticators.
25517 There are two exceptions:
25520 <LI> You use a broken server that advertises an authenticator,
25521 but does not actually implement it.
25522 <LI> You have a Kerberos-capable version of Alpine and the server is
25523 also Kerberos-capable, but you can not obtain Kerberos
25524 credentials on the server machine, thus you desire to disable
25525 GSSAPI (which in turn disables Alpine's Kerberos support).
25528 It is never necessary to disable authenticators, since Alpine will try
25529 other authenticators before giving up.
25530 However, disabling the relevant authenticator avoids annoying error messages.
25533 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25535 <End of help on this topic>
25538 ====== h_config_abook_metafile =====
25541 <TITLE>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></TITLE>
25544 <H1>OPTION: <!--#echo var="VAR_remote-abook-metafile"--></H1>
25546 This is usually set by Alpine and is the name of a file
25547 that contains data about
25548 remote address books and remote configuration files.
25551 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25553 <End of help on this topic>
25556 ====== h_config_composer_wrap_column =====
25559 <TITLE>OPTION: <!--#echo var="VAR_composer-wrap-column"--></TITLE>
25562 <H1>OPTION: <!--#echo var="VAR_composer-wrap-column"--></H1>
25565 This option specifies an aspect of Alpine's Composer. This gives the
25566 maximum width that auto-wrapped lines will have. It's also the maximum
25567 width of lines justified using the <A HREF="h_compose_justify">^J
25568 Justify</A> command. The normal default
25569 is "74". The largest allowed setting is normally "80"
25571 prevent very long lines from being sent in outgoing mail. When the mail
25572 is actually sent, trailing spaces will be stripped off of each line.
25576 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25578 <End of help on this topic>
25581 ====== h_config_deadlets =====
25584 <TITLE>OPTION: <!--#echo var="VAR_dead-letter-files"--></TITLE>
25587 <H1>OPTION: <!--#echo var="VAR_dead-letter-files"--></H1>
25590 This option affects Alpine's behavior when you cancel a message being
25591 composed. Alpine's usual behavior is to write the canceled message to
25593 <!--chtml if pinemode="os_windows"-->
25594 "DEADLETR",
25596 "dead.letter" in your home directory,
25598 overwriting any previous message.
25600 If you set this option to a value higher than one, then that many copies
25601 of dead letter files will be saved.
25602 For example, if you set this option to "3" then you may have
25604 <!--chtml if pinemode="os_windows"-->
25605 "DEADLETR",
25606 "DEADLETR2", and
25607 "DEADLETR3".
25609 "dead.letter",
25610 "dead.letter2", and
25611 "dead.letter3" in your home directory.
25613 In this example, the most recently cancelled message will be in
25614 <!--chtml if pinemode="os_windows"-->
25615 "DEADLETR",
25617 "dead.letter",
25619 and the third most recently cancelled message will be in
25620 <!--chtml if pinemode="os_windows"-->
25621 "DEADLETR3".
25623 "dead.letter3".
25625 The fourth most recently cancelled message will no longer be saved.
25628 If you set this option to zero, then NO record of canceled messages is
25632 <A HREF="h_config_quell_dead_letter"><!--#echo var="FEAT_quell-dead-letter-on-cancel"--></A>
25633 is set, that overrides whatever you set for this option.
25634 If this option had existed at the time, then the Quell feature would not
25635 have been added, but it is still there for backwards compatibility.
25636 So, in order for this option to have the desired effect, make sure the
25637 Quell feature is turned off.
25641 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25643 <End of help on this topic>
25646 ====== h_config_maxremstream =====
25649 <TITLE>OPTION: <!--#echo var="VAR_max-remote-connections"--></TITLE>
25652 <H1>OPTION: <!--#echo var="VAR_max-remote-connections"--></H1>
25654 This option affects low-level behavior of Alpine.
25655 The default value for this option is <EM>3</EM>.
25656 If your INBOX is accessed using the IMAP protocol
25657 from an IMAP server, that connection is kept open throughout the
25658 duration of your Alpine session, independent of the value of this option.
25659 The same is true of any
25660 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
25662 This option controls Alpine's behavior when connecting to remote IMAP folders
25663 other than your INBOX or your <!--#echo var="VAR_stay-open-folders"-->.
25664 It specifies the maximum number of remote IMAP connections (other than
25665 those mentioned above) that Alpine will use for accessing the rest of your
25667 If you set this option to zero, you will turn off most remote connection
25669 It's difficult to understand exactly what this option does, and it is usually
25670 fine to leave it set to its default value.
25671 It is probably more likely that you will be interested in setting the
25672 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A> option
25673 instead of changing the value of this option.
25674 A slightly longer explanation of what is going on with this option
25675 is given in the next paragraphs.
25678 There are some time costs involved in opening and closing remote IMAP
25679 folders, the main costs being the time you have to wait for the connection
25680 to the server and the time for the folder to open.
25681 Opening a folder may involve not only the time the server takes to do its
25682 processing but time that Alpine uses to do filtering.
25683 These times can vary widely.
25684 They depend on how loaded the server is, how large
25685 the folder being opened is, and how you set up filtering, among other things.
25686 Once Alpine has opened a connection to a particular folder, it will attempt
25687 to keep that connection open in case you use it again.
25688 In order to do this,
25689 Alpine will attempt to use the <!--#echo var="VAR_max-remote-connections"--> (the value of
25690 this option) IMAP connections you have alloted for this purpose.
25692 For example, suppose the value of this option is set to "2".
25693 If your INBOX is accessed on a remote server using the IMAP protocol, that
25694 doesn't count as one of the remote connections but it is always kept open.
25695 If you then open another IMAP folder, that would be your first
25696 remote connection counted as one of the <!--#echo var="VAR_max-remote-connections"--> connections.
25697 If you open a third folder the second will be left open, in case you
25699 You won't be able to tell it has been left open.
25700 It will appear to be closed when you leave the folder but the connection
25701 will remain in the background.
25702 Now suppose you go back to the second folder (the first folder after the
25704 A connection to that folder is still open so you won't have to wait
25705 for the startup time to open it.
25706 Meanwhile, the connection to the third folder will be left behind.
25707 Now, if you open a fourth folder, you will bump into the
25708 <!--#echo var="VAR_max-remote-connections"--> limit, because this will be the third folder other
25709 than INBOX and you have the option set to "2".
25710 The connection that is being used for
25711 the third folder will be re-used for this new fourth folder.
25712 If you go back to the third folder after this, it is no longer already
25713 connected when you get there.
25714 You'll still save some time since Alpine will re-use the connection to the
25715 fourth folder and you have already logged in on that connection,
25716 but the folder will have to be re-opened from scratch.
25718 If a folder is large and the startup cost is dominated by the time it takes
25719 to open that folder or to run filters on it, then it will pay to make the
25720 value of this option large enough to keep it open.
25721 On the other hand, if you only revisit a handful of folders or if
25722 the folders are small, then it might
25723 make more sense to keep this number small so that the reconnect
25724 time (the time to start up a new connection and authenticate)
25725 is eliminated instead.
25727 You may also need to consider the impact on the server.
25728 On the surface, a larger number here may cause a larger impact on the
25729 server, since you will have more connections open to the server.
25730 On the other hand, not only will <EM>you</EM> be avoiding the startup costs
25731 associated with reopening a folder, but the <EM>server</EM> will be
25732 avoiding those costs as well.
25734 When twenty five minutes pass without any active use of an IMAP connection
25735 being saved for possible re-use, that connection will be shut down,
25739 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25741 <End of help on this topic>
25744 ====== h_config_permlocked =====
25747 <TITLE>OPTION: <!--#echo var="VAR_stay-open-folders"--></TITLE>
25750 <H1>OPTION: <!--#echo var="VAR_stay-open-folders"--></H1>
25752 This option affects low-level behavior of Alpine.
25753 There is no default value for this option.
25754 It is related to the options
25755 <A HREF="h_config_preopen_stayopens">"<!--#echo var="FEAT_preopen-stayopen-folders"-->"</A>,
25756 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>,
25757 and <A HREF="h_config_expunge_stayopens">"<!--#echo var="FEAT_offer-expunge-of-stayopen-folders"-->"</A>.
25760 Note: changes made to this list take effect the next time you open a
25761 folder in the list.
25764 This is a list of folders that will be permanently kept open once they
25766 The names in this list may be either the nickname of an Incoming folder
25767 or the full technical specification of a folder.
25768 The folders in this list need not be remote IMAP folders, they could usefully
25769 be local folders, as well.
25770 If a folder in the list is a newsgroup or is not accessed either locally
25771 or via IMAP, then the entry will be ignored.
25772 For example, folders accessed via NNTP or POP3 will not be kept open, since
25773 the way that new mail is found with those protocols involves closing and
25774 reopening the connection.
25776 Once a Stay Open folder has been opened, new-mail checking will continue
25777 to happen on that folder for the rest of the Alpine session.
25778 Your INBOX is always implicitly included in this Stay-Open list and doesn't
25779 need to be added explicitly.
25781 Another difference that you may notice between a Stay Open folder and a
25782 non-Stay Open folder is which message is selected as the current message
25783 when you enter the folder index.
25784 Normally, the starting position for an incoming folder (which most Stay Open
25785 folders will likely be) is controlled by the
25786 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
25787 However, if a folder is a Stay Open folder, when you re-enter the folder
25788 after the first time the current message will be the same as it was when
25789 you left the folder.
25790 An exception is made if you use the TAB command to get to the folder.
25791 In that case, the message number will be incremented by one from what it
25792 was when you left the folder.
25794 The above special behavior is thought to be useful.
25795 However, it is special and different from what you might at first expect.
25797 <A HREF="h_config_use_reg_start_for_stayopen"><!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></A>
25798 may be used to turn off this special treatment.
25800 If the message that was current when you left the folder no longer exists,
25801 then the regular startup rule will be used instead.
25805 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25807 <End of help on this topic>
25810 ====== h_config_viewer_overlap =====
25813 <title>OPTION: <!--#echo var="VAR_viewer-overlap"--></title>
25816 <h1>OPTION: <!--#echo var="VAR_viewer-overlap"--></h1>
25818 This option specifies an aspect of Alpine's Message Viewing screen. When
25819 the space bar is used to page forward in a message, the number of lines
25820 specified by the "<!--#echo var="VAR_viewer-overlap"-->" variable will be repeated from the
25821 bottom of the screen. That is, if this was set to two lines, then the
25822 bottom two lines of the screen would be repeated on the top of the next
25823 screen. The normal default value is "2".<p>
25825 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25827 <End of help on this topic>
25830 ====== h_config_scroll_margin =====
25833 <TITLE>OPTION: <!--#echo var="VAR_scroll-margin"--></TITLE>
25836 <H1>OPTION: <!--#echo var="VAR_scroll-margin"--></H1>
25838 This option controls when Alpine's line-by-line scrolling occurs.
25839 Typically, when a selected item is at the top or bottom screen edge
25840 and the UP or DOWN (and Ctrl-P or Ctrl-N) keys are struck, the
25841 displayed items are scrolled down or up by a single line.
25844 This option allows you to tell Alpine the number of lines from the top and
25845 bottom screen edge that line-by-line paging should occcur. For example,
25846 setting this value to one (1) will cause Alpine to scroll the display
25847 vertically when you move to select an item on the display's top or
25851 By default, this variable is zero, indicating that scrolling happens
25852 when you move up or down to select an item immediately off the display's
25853 top or bottom edge.
25857 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25859 <End of help on this topic>
25862 ====== h_config_wordseps =====
25865 <TITLE>OPTION: <!--#echo var="VAR_composer-word-separators"--></TITLE>
25868 <H1>OPTION: <!--#echo var="VAR_composer-word-separators"--></H1>
25870 This option affects how a "word" is defined in the composer.
25871 The definition of a word is used when using the Forward Word and Backward
25872 Word commands in the composer, as well as when using the spell checker.
25873 Whitespace is always considered a word separator.
25874 Punctuation (like question marks, periods, commas, and so on) is always
25875 a word separator if it comes at the end of a word.
25876 By default, a punctuation character that is in the middle of a word does
25877 not break up that word as long as the character before and the character
25878 after it are both alphanumeric.
25879 If you add a character to this option it will be considered a
25880 word separator even when it occurs in the middle of an alphanumeric word.
25881 For example, if you want to skip through each part of an address instead
25882 of skipping the whole address at once you might want to include "@"
25883 and "." in this list.
25884 If you want the word-skipper to stop on each part of a UNIX filename you
25885 could add "/" to the list.
25886 The equal sign and dash are other possibilities you might find helpful.
25889 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25891 <End of help on this topic>
25894 ====== h_config_reply_indent_string =====
25897 <TITLE>OPTION: <!--#echo var="VAR_reply-indent-string"--></TITLE>
25900 <H1>OPTION: <!--#echo var="VAR_reply-indent-string"--></H1>
25902 This option specifies an aspect of Alpine's Reply command.
25903 When a message is replied to and the text of the message is included, the
25904 included text usually has the string "> " prepended
25905 to each line indicating it is quoted text.
25906 (In case you haven't seen this before, "string" is a technical term
25907 that means chunk of text.)
25910 Because of the introduction of <A HREF="h_config_quell_flowed_text">Flowed Text</A>
25911 in 1999 and its wide-spread adoption since then, you will usually be better off if you
25912 use one of the standard values,
25913 "> " or ">", for this option.
25916 This option specifies a different value for that string.
25917 If you wish to use a string that begins or ends with a space,
25918 enclose the string in double quotes.
25921 Besides simple text, the prepended string can be based
25922 on the message being replied to.
25923 The following tokens are substituted for the message's corresponding value:
25927 <DD>This token gets replaced with the message sender's "username".
25928 If the name is longer than six characters, only the first six characters are
25933 <DD>This token gets replaced with the nickname of the message sender's
25934 address as found in your addressbook.
25935 If no addressbook entry is found,
25936 Alpine replaces the characters "_NICK_" with nothing.
25937 If the nickname is longer than six characters, only the first six characters are
25942 <DD>This token gets replaced with the initials of the sender of the message.
25948 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
25949 feature is enabled, you are given the opportunity to edit the string, whether
25950 it is the default or one automatically generated using the above tokens.
25952 If you change your <!--#echo var="VAR_reply-indent-string"-->
25953 so that it is not equal to the default value of "> ", then
25954 quoted text will not be flowed
25955 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
25957 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
25958 set to the default value.
25961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
25963 <End of help on this topic>
25966 ====== h_config_quote_replace_string =====
25969 <TITLE>OPTION: <!--#echo var="VAR_quote-replace-string"--></TITLE>
25972 <H1>OPTION: <!--#echo var="VAR_quote-replace-string"--></H1>
25974 This option specifies what string to use as a quote when <b>viewing</b> a
25975 message. The standard way of quoting messages when replying is the string
25976 "> " (quote space).
25977 With this variable set, viewing a message will
25978 replace occurrences of
25979 "> " and ">" with the replacement string.
25980 This setting works best when
25981 <A HREF="h_config_reply_indent_string"><!--#echo var="VAR_reply-indent-string"--></A>
25982 or the equivalent setting in your correspondents' mail programs
25983 is set to the default
25984 "> ", but it will also work fine with the
25985 <!--#echo var="VAR_reply-indent-string"--> set to ">".
25987 By default, this setting will only work on messages that are flowed, which is
25988 the default way of sending messages for many mail clients including
25989 Alpine. Enable the feature
25990 <A HREF="h_config_quote_replace_noflow"><!--#echo var="FEAT_quote-replace-nonflowed"--></A>
25991 to also have quote-replacement performed on non-flowed messages.
25994 Setting this option will replace ">" and
25995 "> " with the new setting. This string may include trailing
25996 spaces. To preserve those spaces enclose the full string in double quotes.
25998 No padding to separate the text of the message from the quote string is
25999 added. This means that if you do not add trailing spaces to the value of
26000 this variable, text will be displayed right next to the quote string,
26001 which may be undesirable. This can be avoided by adding a new string
26002 separated by a space from your selection of quote string replacement. This
26003 last string will be used for padding. For example, setting this variable to
26004 <br>">" " " has the effect of setting
26005 ">" as the <!--#echo var="VAR_quote-replace-string"-->, with the text padded by
26006 a space from the last quote string to make it more readable.
26008 One possible setting for this variable could be
26009 " " (four spaces wrapped in quotes), which
26010 would have the effect of indenting each level of quoting four spaces and
26011 removing the ">"'s. Different levels of quoting could be made
26012 more discernible by setting colors for quoted text.
26014 Replying to or forwarding the viewed message will preserve the original
26015 formatting of the message, so quote-replacement will not be performed on
26016 messages that are being composed.
26019 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26021 <End of help on this topic>
26024 ====== h_config_empty_hdr_msg =====
26027 <TITLE>OPTION: <!--#echo var="VAR_empty-header-message"--></TITLE>
26030 <H1>OPTION: <!--#echo var="VAR_empty-header-message"--></H1>
26032 When sending, if both the To and Cc fields are empty and you
26033 are sending the message to a Bcc,
26034 Alpine will put a special address in the To line. The default value is:
26037 <CENTER><SAMP>undisclosed-recipients: ;</SAMP></CENTER>
26040 The reason for this is to avoid embarrassment caused by some Internet
26041 mail transfer software that interprets a "missing"
26042 <SAMP>To:</SAMP> header as an error and replaces it with an
26043 <SAMP>Apparently-to:</SAMP> header that may contain the addresses you
26044 entered on the <SAMP>Bcc:</SAMP> line, defeating the purpose of the
26045 Bcc. You may change the part of this message that comes before the
26046 ": ;" by setting the "<!--#echo var="VAR_empty-header-message"-->"
26047 variable to something else.
26050 The normal default is "undisclosed-recipients".
26054 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26056 <End of help on this topic>
26059 ====== h_config_status_msg_delay =====
26062 <TITLE>OPTION: <!--#echo var="VAR_status-message-delay"--></TITLE>
26065 <H1>OPTION: <!--#echo var="VAR_status-message-delay"--></H1>
26067 This option has evolved over time, causing the possible values to be
26069 Read carefully before you set this option.
26070 First we explain what the option does, then there is a longer discussion
26073 If this is set to zero, the default value, it has <EM>no</EM> effect.
26074 Positive and negative values serve two similar, but different purposes.
26076 If it is set to a positive number, it causes the cursor to move to the
26077 status line whenever a status message is printed and pause there for this
26079 It will probably only be useful if the
26080 <A HREF="h_config_show_cursor">"<!--#echo var="FEAT_show-cursor"-->"</A> feature is
26082 Setting this option to a positive number can only be used to
26083 <EM>increase</EM> the status message delay.
26084 This may be useful for Braille displays, or other non-traditional displays.
26086 If it is set to a negative number the interpretation is a bit complicated.
26087 Negative numbers are used to <EM>decrease</EM> the amount of delay Alpine uses to
26088 allow you to read important status messages.
26089 Of course, this may cause you to miss some important messages.
26090 If you see a message flash by but miss what it says you can use the
26091 Journal command from the MAIN MENU to read it.
26092 If you set this option to a negative value, the delay will be
26093 no more than one second less than the absolute value
26094 of the value you set.
26095 So if you set it to -1, the delay will be no more than zero seconds, no
26097 If you set it to -2, the delay will be no more than 1 second.
26098 And so on, -3 is 2 seconds, -4 is 3 seconds, ...
26099 If the delay that Alpine would have used by default is less than this delay,
26100 then the smaller delay set by Alpine will be used.
26101 Setting this option to a negative value can only reduce the amount of
26102 delay, never increase it.
26104 Here is a more detailed explanation.
26105 Status messages are the messages that show up spontaneously in the
26106 status message line, usually the third line from the bottom of the screen.
26107 By default, Alpine assigns each status message it produces a minimum
26109 Some status messages have a minimum display time of zero.
26110 You can see an example of such a message by paging up in this help text
26111 until you reach the top of the screen.
26112 If you try to page past the top you will see the message
26114 <CENTER><SAMP>[Already at start of help text]</SAMP></CENTER>
26116 in the status line.
26117 If there is another more important use of the status message line this message
26118 might be replaced quickly, or it even might not be shown at all.
26119 However, if there is no reason to get rid of the message, it might stay
26120 there for several seconds while you read the help.
26121 An example where it is replaced immediately happens when you page up in
26122 the help text past the top of the screen, but then type the "WhereIs"
26123 command right after paging up.
26124 The message will disappear immediately without causing a delay (unless you
26125 have set this option to a positive value) to allow you to type input for
26126 the "WhereIs" command.
26127 Since it isn't a very important message, Alpine has set its minimum display
26128 time to zero seconds.
26130 Other messages have minimum display times of three or more seconds.
26131 These are usually error messages that Alpine thinks you ought to see.
26132 For example, it might be a message about a failed Save or a failed folder open.
26133 It is often the case that this minimum display time won't delay you in
26134 any way because the status message line is not needed for another reason.
26135 However, there are times when Alpine has to delay what it is doing in
26136 order to display a status message for the minimum display time.
26137 This happens when a message is being displayed and Alpine wants to ask
26138 for input from the keyboard.
26139 For example, when you Save a message you use the status message line.
26140 You get a prompt there asking for the name of the folder to save to.
26141 If there is a status message being displayed that has not
26142 yet displayed for its minimum
26143 time Alpine will display that status message surrounded with the characters
26144 > and < to show you that it is delaying.
26145 That might happen, for example, if you tried to save to a folder that
26146 caused an error, then followed that immediately with another Save command.
26147 You might find yourself waiting for a status message like
26149 <CENTER><SAMP>[>Can't get write access to mailbox, access is readonly<]</SAMP></CENTER>
26151 to finish displaying for three seconds.
26152 If that is something you find happening to you frequently, you may use
26153 negative values of this option to decrease or eliminate that delay, at
26154 the risk of missing the message.
26157 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26159 <End of help on this topic>
26162 ====== h_config_active_msg_interval =====
26165 <TITLE>OPTION: <!--#echo var="VAR_busy-cue-rate"--></TITLE>
26168 <H1>OPTION: <!--#echo var="VAR_busy-cue-rate"--></H1>
26170 When Alpine is delayed for some reason it usually shows that
26171 something is happening with a small animated display in the status
26172 message line near the bottom of the screen.
26173 This option sets how frequently the characters (for example, a spinning bar)
26174 in the active status message lines are updated.
26175 At most, it can be set to be udpated 20 times per second.
26178 Setting this value to zero will prevent display of the animations
26182 The option <A HREF="h_config_use_boring_spinner"><!--#echo var="FEAT_busy-cue-spinner-only"--></A>
26183 can be used to remove the randomness from this animated display.
26187 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26189 <End of help on this topic>
26192 ====== h_config_mailchecknoncurr =====
26195 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></TITLE>
26198 <H1>OPTION: <!--#echo var="VAR_mail-check-interval-noncurrent"--></H1>
26200 This option is closely related to the
26201 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26202 option, as well as the
26203 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A> and
26204 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> options.
26205 If the "<!--#echo var="VAR_mail-check-interval"-->" option is set to zero, then automatic
26206 new-mail checking is disabled and this option will have no effect.
26208 Normally this option is set to zero, which means that the value used will be
26209 the same as the value for the "<!--#echo var="VAR_mail-check-interval"-->".
26210 If you set this option to a value different from zero
26211 (usually larger than the value for "<!--#echo var="VAR_mail-check-interval"-->")
26212 then that is the check interval that will be used
26213 for folders that are not the currently open folder or the INBOX.
26214 You may not even have any folders that are noncurrent and not the INBOX.
26215 If you do, it is likely that they are due to
26216 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>
26217 you have configured.
26218 This option also affects the rate of mail checking done on cached
26219 connections to folders you previously had open but are no longer actively
26221 You aren't expected to understand that last sentence, but if you are interested
26223 <A HREF="h_config_maxremstream">"<!--#echo var="VAR_max-remote-connections"-->"</A>
26224 and the related options.
26227 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26229 <End of help on this topic>
26232 ====== h_config_fifopath =====
26235 <TITLE>OPTION: NewMail FIFO Path</TITLE>
26238 <H1>OPTION: NewMail FIFO Path</H1>
26240 This option is only available in UNIX Alpine.
26241 However, there is a very similar feature built in to PC-Alpine.
26242 In PC-Alpine's Config menu at the top of the screen
26243 is an option called "New Mail Window".
26245 You may have Alpine create a FIFO special file (also called a named pipe) where
26246 it will send a one-line message each time a new message is received in
26247 the current folder, the INBOX, or any open
26248 <A HREF="h_config_permlocked"><!--#echo var="VAR_stay-open-folders"--></A>.
26249 To protect against two different Alpines both writing to the same FIFO, Alpine
26250 will only create the FIFO and write to it if it doesn't already exist.
26252 A possible way to use this option would be to have a separate window
26253 on your screen running the command
26255 <CENTER><SAMP>cat filename</SAMP></CENTER>
26257 where "filename" is the name of the file given for this option.
26258 Because the file won't exist until after you start Alpine, you must <EM>first</EM>
26259 start Alpine and <EM>then</EM> run the "cat" command.
26260 You may be tempted to use "tail -f filename" to view the new
26262 However, the common implementations of the tail command will not do what you
26265 The width of the messages produced for the FIFO may be altered with the
26266 <A HREF="h_config_newmailwidth"><!--#echo var="VAR_newmail-window-width"--></A> option.
26268 On some systems, fifos may only be created in a local filesystem.
26269 In other words, they may not be in NFS filesystems.
26270 This requirement is not universal.
26271 If the system you are using supports it, it should work.
26272 (It is often the case that your home directory is in an NFS filesystem.
26273 If that is the case, you might try using a file in the "/tmp"
26274 filesystem, which is usually a local filesytem.)
26275 Even when it is possible to use an NFS-mounted filesystem as a place to name
26276 the fifo (for example, your home directory), it will still be the case that
26277 the reader (probably the "cat" command) and the
26278 writer (Alpine) of the fifo must be running on the same system.
26281 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26283 <End of help on this topic>
26286 ====== h_config_newmailwidth =====
26289 <TITLE>OPTION: <!--#echo var="VAR_newmail-window-width"--></TITLE>
26292 <H1>OPTION: <!--#echo var="VAR_newmail-window-width"--></H1>
26294 For UNIX Alpine, this option is only useful if you have turned on the
26295 <A HREF="h_config_fifopath">NewMail FIFO Path</A> option.
26296 That option causes new mail messages to be sent to a fifo file.
26297 Those messages will be 80 characters wide by default.
26298 You can change the width of those messages by changing this option.
26299 For example, if you are reading those messages in another window you might
26300 want to set this width to the width of that other window.
26302 If you are using PC-Alpine, it has an option in the Config menu to turn
26303 on the "New Mail Window".
26304 This present option also controls the width of that window.
26307 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26309 <End of help on this topic>
26312 ====== h_config_mailcheck =====
26315 <TITLE>OPTION: <!--#echo var="VAR_mail-check-interval"--></TITLE>
26318 <H1>OPTION: <!--#echo var="VAR_mail-check-interval"--></H1>
26320 This option specifies, in seconds,
26321 how often Alpine will check for new mail.
26322 If set to zero, new-mail checking is disabled.
26323 (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
26324 current message is the last message of the folder.)
26325 There is a minimum value for this option, normally 15 seconds.
26326 The default value is normally 150 seconds.
26327 The higher you set this option, the easier it is on the server.
26329 There are some situations where automatic new-mail checking does not work.
26330 See the discussion about new-mail checking in
26331 <A HREF="h_config_reopen_rule">"<!--#echo var="VAR_folder-reopen-rule"-->"</A>.
26333 The new-mail checking will not happen exactly at the frequency that you specify.
26334 For example, Alpine may elect to defer a non-INBOX mail check if you
26336 Or, it may check more frequently than you have specified if that is
26337 thought to be necessary to keep the server from closing the connection
26338 to the folder due to inactivity.
26339 If Alpine checks for new mail as a side effect of another command, it will reset
26340 the timer, so that new-mail checking may seem to happen irregularly instead of
26341 every X seconds like clockwork.
26343 If you are anxious to know about new mail as soon as possible, set the check
26344 interval low, and you'll know about the new mail by approximately
26345 that amount of time after it arrives.
26346 If you aren't so worried about knowing right away, set this option to a
26348 That will save the server some processing time and may save you some of
26349 the time you spend waiting for new-mail checks to happen if you are
26350 dealing with a slow server or slow network connection.
26352 If you suspect that new-mail checking is causing slow downs for you,
26353 you may want to look into the options
26354 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>,
26355 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A> and
26356 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A>,
26357 which refine when mail checking is done.
26359 If the mailbox being checked uses a <A HREF="h_maildrop">Mail Drop</A> then
26360 there is a minimum time
26361 (<A HREF="h_config_maildropcheck">"<!--#echo var="VAR_maildrop-check-minimum"-->"</A>)
26362 between new-mail checks.
26363 Because of this minimum you may notice that new mail does not
26364 appear promptly when you expect it.
26365 The reason for this is to protect the server from over-zealous opening and
26366 closing of the Mail Drop folder, since that is a costly operation.
26369 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26371 <End of help on this topic>
26374 ====== h_config_quell_checks_comp =====
26377 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></TITLE>
26380 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"--></H1>
26382 This option is closely related to the
26383 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26385 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26386 <A HREF="h_config_quell_checks_comp_inbox">"<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->"</A>.
26388 If this option is set, then the normal new-mail checking that happens
26389 while you are composing will not happen for folders other than your
26390 INBOX (which depends on the setting
26391 of "<!--#echo var="FEAT_quell-mailchecks-composing-inbox"-->").
26393 You might want to set this option if you are experiencing delays while
26394 composing that you think might be related to the speed of the new-mail
26397 Even with this option turned on, an occasional new-mail check may be done
26398 in order to keep the server from killing the connection to the folder.
26399 For example, IMAP servers may remove a connection to a folder if there
26400 has been no activity on the connection for 30 minutes or more.
26401 Instead of letting that happen, Alpine will check for new mail before the
26402 30 minutes is up even though you have turned on this feature to quell
26405 Besides new-mail checks, checkpoint operations on the folders
26406 will also be quelled when you set this option.
26407 The purpose of checkpointing is to write the changes to a folder out to
26408 disk periodically in order to avoid losing those changes when system or
26409 software problems occur.
26410 New-mail checking and checkpointing while you are not composing are not
26411 affected by this option.
26414 <End of help on this topic>
26417 ====== h_config_quell_checks_comp_inbox =====
26420 <TITLE>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></TITLE>
26423 <H1>FEATURE: <!--#echo var="FEAT_quell-mailchecks-composing-inbox"--></H1>
26425 This option is closely related to the
26426 <A HREF="h_config_mailcheck">"<!--#echo var="VAR_mail-check-interval"-->"</A>
26428 <A HREF="h_config_mailchecknoncurr">"<!--#echo var="VAR_mail-check-interval-noncurrent"-->"</A> option, and
26429 <A HREF="h_config_quell_checks_comp">"<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->"</A>.
26431 If this option is set, then the normal new-mail checking that happens
26432 while you are composing will not happen for your INBOX.
26433 Checking of other folders is controlled in a similar way with the
26434 "<!--#echo var="FEAT_quell-mailchecks-composing-except-inbox"-->" option.
26436 You might want to set this option if you are experiencing delays while
26437 composing that you think might be related to the speed of the new-mail
26440 Even with this option turned on, an occasional new-mail check may be done
26441 in order to keep the server from killing the connection to the folder.
26442 For example, IMAP servers may remove a connection to a folder if there
26443 has been no activity on the connection for 30 minutes or more.
26444 Instead of letting that happen, Alpine will check for new mail before the
26445 30 minutes is up even though you have turned on this feature to quell
26448 Besides new-mail checks, checkpoint operations on the INBOX
26449 will also be quelled when you set this option.
26450 The purpose of checkpointing is to write the changes to a folder out to
26451 disk periodically in order to avoid losing those changes when system or
26452 software problems occur.
26453 New-mail checking and checkpointing while you are not composing are not
26454 affected by this option.
26456 <End of help on this topic>
26459 ====== h_config_maildropcheck =====
26462 <TITLE>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></TITLE>
26465 <H1>OPTION: <!--#echo var="VAR_maildrop-check-minimum"--></H1>
26467 New-mail checking for a
26468 <A HREF="h_maildrop">Mail Drop</A> is a little different from new
26469 mail checking for a regular folder.
26470 One of the differences is that the connection to the Mail Drop is not
26471 kept open and so the cost of checking
26472 (delay for you and additional load for the server) may be significant.
26473 Because of this additional cost we set a minimum time that
26474 must pass between checks.
26475 This minimum only applies to the automatic checking done by Alpine.
26476 If you force a check by typing ^L (Ctrl-L) or by typing the Next command when you are
26477 at the end of a folder index, then the check is done right away.
26479 This option specifies, in seconds, the <EM>minimum</EM> time between Mail Drop
26481 You may want to set this minimum high in order to avoid experiencing some
26482 of the delays associated with the checks.
26483 Note that the time between checks is still controlled by the regular
26484 <A HREF="h_config_mailcheck"><!--#echo var="VAR_mail-check-interval"--></A> option.
26485 When Alpine is about to do an automatic check for new mail (because
26486 the <!--#echo var="VAR_mail-check-interval"--> has expired) then if the time since the last
26488 of any open Mail Drops has been greater than the <!--#echo var="VAR_maildrop-check-minimum"-->,
26489 the Mail Drop is checked for new mail as well.
26490 Therefore, it is only useful to set this option to a value that is higher
26491 than the <!--#echo var="VAR_mail-check-interval"-->.
26493 If this option is set to zero, automatic Mail Drop new-mail
26494 checking is disabled.
26495 There is a minimum value, normally 60 seconds.
26496 The default value is normally 60 seconds as well.
26497 This applies to the INBOX and to the currently open folder if that is
26498 different from the INBOX.
26502 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26504 <End of help on this topic>
26507 ====== h_config_nntprange =====
26510 <TITLE>OPTION: <!--#echo var="VAR_nntp-range"--></TITLE>
26513 <H1>OPTION: <!--#echo var="VAR_nntp-range"--></H1>
26515 This option applies only to newsgroups accessed using the NNTP protocol.
26516 It does not, for example,
26517 apply to newsgroups accessed using an IMAP-to-NNTP proxy.
26520 When you open a connection to a News server using the NNTP protocol, you
26521 normally have access to all of the articles in each newsgroup.
26522 If a server keeps a large backlog of messages it may speed performance
26523 some to restrict attention to only the newer messages in a group.
26524 This option allows you to set how many article numbers should be checked
26525 when opening a newsgroup.
26526 You can think of "<!--#echo var="VAR_nntp-range"-->" as specifying the maximum number
26527 of messages you ever want to see.
26528 For example, if you only ever wanted to look at the last 500 messages in each
26529 newsgroup you could set this option to 500.
26530 In actuality, it isn't quite that.
26531 Instead, for performance reasons, it specifies the range of article
26532 numbers to be checked, beginning
26533 with the highest numbered article and going backwards from there.
26534 If there are messages that have been canceled or deleted
26535 their article numbers are still counted as part of the range.
26537 So, more precisely, setting the "<!--#echo var="VAR_nntp-range"-->" will cause article
26539 <P><CENTER>last_article_number - <!--#echo var="VAR_nntp-range"--> + 1 through last_article_number</CENTER>
26541 to be considered when reading a newsgroup.
26542 The number of messages that show up in your index will be less than or equal
26543 to the value of "<!--#echo var="VAR_nntp-range"-->".
26546 The purpose of this option is simply to speed up access when reading news.
26547 The speedup comes because Alpine can ignore all but the last <!--#echo var="VAR_nntp-range"--> article
26548 numbers, and can avoid downloading any information about the ignored articles.
26549 There is a cost you pay for this speedup.
26550 That cost is that there is no way for you to see those ignored articles.
26551 The articles that come before the range you specify are invisible to you and
26552 to Alpine, as if they did not exist at all.
26553 There is no way to see those messages using, for example, an unexclude command
26554 or something similar.
26555 The only way to see those articles is to set this option high enough (or
26556 set it to zero) and then to reopen the newsgroup.
26559 If this option is set to 0 (which is also the default),
26560 then the range is unlimited.
26561 This option applies globally to all NNTP servers and to all newsgroups
26563 There is no way to set different values for different newsgroups or servers.
26567 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26569 <End of help on this topic>
26572 ====== h_config_news_active =====
26575 <title>OPTION: <!--#echo var="VAR_news-active-file-path"--></title>
26578 <h1>OPTION: <!--#echo var="VAR_news-active-file-path"--></h1>
26580 This option tells Alpine where to look for the "active file" for newsgroups
26581 when accessing news locally, rather than via NNTP. The default path is
26582 usually "/usr/lib/news/active".<p>
26584 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26586 <End of help on this topic>
26589 ====== h_config_news_spool =====
26592 <title>OPTION: <!--#echo var="VAR_news-spool-directory"--></title>
26595 <h1>OPTION: <!--#echo var="VAR_news-spool-directory"--></h1>
26597 This option tells Alpine where to look for the "news spool" for newsgroups
26598 when accessing news locally, rather than via NNTP. The default path is
26599 usually "/var/spool/news".<p>
26601 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26603 <End of help on this topic>
26606 ====== h_config_image_viewer =====
26609 <title>OPTION: <!--#echo var="VAR_image-viewer"--></title>
26612 <h1>OPTION: <!--#echo var="VAR_image-viewer"--></h1>
26614 This option specifies the program Alpine should call to view MIME
26615 attachments of type IMAGE (e.g. GIF or TIFF). The Image Viewer setting is
26616 no longer needed, but remains for backward compatibility. The more
26617 general method for associating external printing and viewing programs with
26618 specific MIME data types is to use the system's (or your personal)
26619 "mailcap" configuration file.<p>
26621 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26623 <End of help on this topic>
26626 ====== h_config_domain_name =====
26629 <TITLE>OPTION: <!--#echo var="VAR_use-only-domain-name"--></TITLE>
26632 <H1>OPTION: <!--#echo var="VAR_use-only-domain-name"--></H1>
26634 This option is used only if the
26635 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> option is <B>not</B>
26636 set. If set to "Yes" (and <!--#echo var="VAR_user-domain"--> is not used), then Alpine
26637 strips the hostname from your return ("From") address and when
26638 completing unqualified addresses that you enter into the composer.
26640 If you set this, see also the <A HREF="h_config_quell_local_lookup">
26641 "<!--#echo var="FEAT_quell-user-lookup-in-passwd-file"-->"</A> feature.
26644 <!--chtml if pinemode="os_windows"-->
26645 <P>This option is not applicable to PC-Alpine.
26650 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26653 <End of help on this topic>
26656 ====== h_config_prune_date =====
26659 <TITLE>OPTION: Last-Time-Prune Question</TITLE>
26662 <H1>OPTION: Last-Time-Prune Question</H1>
26664 This value records the last time you were asked about deleting old
26666 It is set automatically by Alpine at the beginning of each month.
26667 In the past, if you wished to suppress the monthly sent-mail
26668 pruning feature, you could set this to a date in the future.
26669 This value is relative to the year 1900, so
26670 to set this, for example, to October 2005, use 105.10.
26672 You can still do that if you wish, or you can use the
26673 <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option, which is probably
26674 a little more convenient to use.
26677 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26679 <End of help on this topic>
26682 ====== h_config_goto_default =====
26685 <TITLE>OPTION: <!--#echo var="VAR_goto-default-rule"--></TITLE>
26688 <H1>OPTION: <!--#echo var="VAR_goto-default-rule"--></H1>
26690 This value affects Alpine's behavior when you use the Goto command.
26691 Alpine's usual behavior has two parts. If your current folder is
26692 "Inbox", Alpine will offer the last open folder as the
26693 default. If the current folder is other than "Inbox",
26694 "Inbox" is offered as the default.
26697 The available options include:
26701 <DT>folder-in-first-collection</DT>
26703 <DD> Alpine will offer the most recently visited folder in the default
26704 collection found in the "Collection List" screen as the default.
26707 <DT> inbox-or-folder-in-first-collection</DT>
26709 <DD> If the current folder is "Inbox",
26710 Alpine will offer the most recently visited folder in the
26711 default collection found in the "Collection List" screen.
26712 If the current folder is other than "Inbox",
26713 "Inbox" is offered as the default.
26716 <DT> inbox-or-folder-in-recent-collection</DT>
26718 <DD> This is Alpine's default behavior.
26719 If the current folder is "Inbox",
26720 Alpine will offer the last open
26721 folder as the default.
26722 If the current folder is other than "Inbox",
26723 "Inbox" is offered as the default.
26726 <DT> first-collection-with-inbox-default</DT>
26728 <DD> Instead of offering the most recently visited folder in the default
26729 collection, the default collection is offered but with "Inbox" as
26730 the default folder.
26731 If you type in a folder name it will be in the default collection.
26732 If you simply accept the default, however, your "Inbox" will be opened.
26735 <DT> most-recent-folder</DT>
26737 <DD> The last accepted value simply causes the most recently opened
26738 folder to be offered as the default regardless of the currently opened
26744 NOTE: The default while a newsgroup is open remains the same; the last
26749 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26751 <End of help on this topic>
26754 ====== h_config_thread_lastreply_char =====
26757 <TITLE>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></TITLE>
26760 <H1>OPTION: <!--#echo var="VAR_threading-lastreply-character"--></H1>
26762 The <!--#echo var="VAR_threading-lastreply-character"--> option has a small effect on the MESSAGE
26763 INDEX display when using a
26764 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
26765 of "show-thread-structure", "mutt-like", or
26766 "show-structure-in-from"; and sorting by Threads or OrderedSubject.
26767 The value of this option is a single character.
26768 This character is used instead of the vertical line character when there are
26769 no more replies directly to the parent of the current message.
26770 It can be used to "round-off" the bottom of the vertical line
26771 by setting it to a character such as a backslash (\) or
26772 a backquote (`).
26773 The default value of this option is the backslash character (\).
26774 This option may not be set to the Empty Value.
26775 In that case, the default will be used instead.
26779 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26781 <End of help on this topic>
26784 ====== h_config_thread_indicator_char =====
26787 <TITLE>OPTION: <!--#echo var="VAR_threading-indicator-character"--></TITLE>
26790 <H1>OPTION: <!--#echo var="VAR_threading-indicator-character"--></H1>
26792 The <!--#echo var="VAR_threading-indicator-character"--> option has a small effect on the MESSAGE
26793 INDEX display when using a
26794 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26795 than "none" and sorting by Threads or OrderedSubject.
26796 The value of this option is a single character.
26797 This character is used to indicate that part of a thread (a conversation) is
26798 hidden beneath a message.
26799 The message could be expanded
26800 if desired with the "/" Collapse/Expand command.
26801 By default, the value of this option is the greater than sign (>).
26803 If this option is set to the Empty Value, then the column (and the following
26804 blank column) will be deleted from the display.
26807 This option is closely related to the
26808 <A HREF="h_config_thread_exp_char"><!--#echo var="VAR_threading-expanded-character"--></A> option.
26809 Another similar option that affects the thread display is the
26810 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26814 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26816 <End of help on this topic>
26819 ====== h_config_thread_exp_char =====
26822 <TITLE>OPTION: <!--#echo var="VAR_threading-expanded-character"--></TITLE>
26825 <H1>OPTION: <!--#echo var="VAR_threading-expanded-character"--></H1>
26827 The <!--#echo var="VAR_threading-expanded-character"--> option has a small effect on the MESSAGE
26828 INDEX display when using a
26829 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A> other
26830 than "none".
26831 The value of this option is a single character.
26832 This character is used to indicate that part of a thread has been expanded
26833 and could be collapsed if desired with
26834 the "/" Collapse/Expand command.
26835 By default, the value of this option is a dot (.).
26837 If this option is set to the Empty Value, then the column (and the following
26838 blank column) will be deleted from the display.
26841 This option is closely related to the
26842 <A HREF="h_config_thread_indicator_char"><!--#echo var="VAR_threading-indicator-character"--></A> option.
26843 Another similar option that affects the thread display is the
26844 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A> option.
26848 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26850 <End of help on this topic>
26853 ====== h_config_thread_index_style =====
26856 <TITLE>OPTION: <!--#echo var="VAR_threading-index-style"--></TITLE>
26859 <H1>OPTION: <!--#echo var="VAR_threading-index-style"--></H1>
26861 When a folder is sorted by Threads or OrderedSubject,
26862 this option will affect the INDEX displays.
26865 The possible values for this option are:
26868 <DT>regular-index-with-expanded-threads</DT>
26869 <DD>This is the default display.
26870 If the configuration option
26871 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26872 is set to something other than "none", then this setting
26873 will cause Alpine to start off with a MESSAGE INDEX with all of
26874 the threads expanded.
26875 That is, each message will have a line in the MESSAGE INDEX display.
26876 The Collapse/Expand command (/) may be used to manually collapse or
26877 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26879 This setting affects the display when the folder is first threaded.
26880 The collapsed state may also be re-initialized by re-sorting the folder manually
26881 using the SortIndex command ($).
26882 After re-sorting the threads will once again all be expanded, even if you
26883 have previously collapsed some of them.
26885 If "<!--#echo var="VAR_threading-display-style"-->" is set to "none", then
26886 the display will be the regular default Alpine MESSAGE INDEX, but sorted
26887 in a different order.
26890 <DT>regular-index-with-collapsed-threads</DT>
26891 <DD>If the configuration option
26892 <A HREF="h_config_thread_disp_style">"<!--#echo var="VAR_threading-display-style"-->"</A>
26893 is set to something other than "none", then this setting
26894 will cause Alpine to start out with all of the threads collapsed instead of
26895 starting out with all of the threads expanded.
26896 The Collapse/Expand command (/) may be used to manually collapse or
26897 expand a thread or subthread (see also <A HREF="h_config_slash_coll_entire">"<!--#echo var="FEAT_slash-collapses-entire-thread"-->"</A>).
26899 This setting affects the display when the folder is first threaded.
26900 The collapsed state may also be re-initialized by re-sorting the folder manually
26901 using the SortIndex command ($).
26902 After re-sorting the threads will once again all be collapsed, even if you
26903 have previously expanded some of them.
26906 <DT>separate-index-screen-always</DT>
26907 <DD>With this setting and the next, you will see an index of threads
26909 index of messages, provided you have sorted by Threads or OrderedSubject.
26911 The THREAD INDEX contains a '*' in the first column if any message in the thread
26912 is marked Important.
26913 If not, it contains a '+' if any message in the thread is to you.
26914 The second column is blank. The third column contains a 'D' if all of the
26915 messages in the thread are deleted.
26916 Otherwise, it contains an 'N' if any of the messages in the thread are New.
26918 When you view a particular thread from the THREAD INDEX you will be
26919 in the MESSAGE INDEX display
26920 but the index will only contain messages from the thread you are viewing.
26923 <DT>separate-index-screen-except-for-single-messages</DT>
26924 <DD>This is very similar to the option above.
26925 When you are in the THREAD INDEX, one of the available commands
26926 is "ViewThd".
26927 With the setting "separate-index-screen-always" (the option above)
26928 when you view a particular thread you will be in the
26929 MESSAGE INDEX display and the index will only contain messages from
26930 the thread you are viewing.
26931 If the thread you are viewing consists of a single message, the MESSAGE INDEX
26932 will be an index with only one message in it.
26933 If you use this "separate-index-screen-except-for-single-messages"
26934 setting instead, then that index that contains a single message
26935 will be skipped and you will go directly from the THREAD INDEX into the
26936 MESSAGE TEXT screen.
26943 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
26945 <End of help on this topic>
26948 ====== h_config_thread_disp_style =====
26951 <TITLE>OPTION: <!--#echo var="VAR_threading-display-style"--></TITLE>
26954 <H1>OPTION: <!--#echo var="VAR_threading-display-style"--></H1>
26956 When a folder is sorted by Threads or OrderedSubject,
26957 this option will affect the MESSAGE INDEX display.
26958 By default, Alpine will display the MESSAGE INDEX in the
26959 "show-thread-structure" style if a folder is sorted
26960 by Threads or OrderedSubject.
26963 The possible values for this option are:
26967 <DD>Regular index display.
26968 The same index line as would be displayed without threading is used.
26969 The only difference will be in the order of the messages.
26972 <DT>show-thread-structure</DT>
26973 <DD>Threaded Subjects will be indented and vertical bars and horizontal
26974 lines will be added to make it easier to see the relationships among
26975 the messages in a thread (a conversation).
26979 <DD>This is the same as the option above except that the Subject
26980 is suppressed (is blank) if it matches the previous Subject in the thread.
26981 The name comes from the email client <A HREF="http://www.mutt.org/">Mutt</A>.
26982 Here is an example of what a mutt-like index might look like.
26983 In this example, the first column represents the message number, the
26984 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
26985 is set to "regular-index-with-expanded-threads", and the
26986 <A HREF="h_config_thread_lastreply_char"><!--#echo var="VAR_threading-lastreply-character"--></A>
26987 is set to a backslash:
26989 1 Some topic
26990 2 . Subject original message in thread
26991 3 |-> reply to 2
26992 4 . |-> another reply to 2
26993 5 . | \-> reply to 4
26994 6 . | \-> reply to 5
26995 7 | \-> reply to 6
26996 8 |-> another reply to 2
26997 9 . |->New subject another reply to 2 but with a New subject
26998 10 | |-> reply to 9
26999 11 | \-> another reply to 9
27000 12 | \-> reply to 11
27001 13 \-> final reply to 2
27002 14 Next topic
27006 <DT>indent-subject-1</DT>
27007 <DD>Threaded Subjects will be indented one space per level of the conversation.
27008 The bars and lines that show up in the show-thread-structure display will
27009 not be there with this style.
27012 <DT>indent-subject-2</DT>
27013 <DD>Same as above but indent two spaces per level instead of one space.
27016 <DT>indent-from-1</DT>
27017 <DD>Similar to indent-subject-1, except that instead of indenting the
27018 Subject field one space the From field of a thread will be indented one
27019 space per level of the conversation.
27022 <DT>indent-from-2</DT>
27023 <DD>Same as above but indent two spaces per level instead of one space.
27026 <DT>show-structure-in-from</DT>
27027 <DD>The structure of the thread is illustrated with indenting, vertical bars,
27028 and horizontal lines just like with the show-thread-structure option, but
27029 the From field is used to show the relationships instead of the Subject field.
27036 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27038 <End of help on this topic>
27041 ====== h_config_pruning_rule =====
27044 <TITLE>OPTION: <!--#echo var="VAR_pruning-rule"--></TITLE>
27047 <H1>OPTION: <!--#echo var="VAR_pruning-rule"--></H1>
27049 By default, Alpine will ask at the beginning of each month whether or not
27050 you want to rename your sent-mail folder to a name like sent-mail-month-year.
27051 (See the feature <A HREF="h_config_prune_uses_iso"><!--#echo var="FEAT_prune-uses-yyyy-mm"--></A> to
27052 change the format of the folder to sent-mail-yyyy-mm.)
27053 It will also ask whether you would like to delete old sent-mail folders.
27054 If you have defined
27055 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>
27057 <A HREF="h_config_pruned_folders"><!--#echo var="VAR_pruned-folders"--></A>
27058 Alpine will also ask about pruning those folders.
27061 With this option you may provide an automatic answer to these questions.
27062 The default value is to ask you what you'd like to do.
27065 The six possible values for this option are:
27068 <DT>ask about rename, ask about deleting</DT>
27069 <DD>This is the default.
27070 Alpine will ask whether you want to rename the folders and whether you
27071 want to delete each of the old folders.
27074 <DT>ask about rename, don't delete</DT>
27075 <DD>Alpine will ask whether you want to rename the folders, but won't
27076 ask about or delete old folders.
27079 <DT>always rename, ask about deleting</DT>
27080 <DD>This means you want to always answer yes and have Alpine automatically
27081 rename the folder if possible.
27082 You will also be asked about deleting old folders.
27085 <DT>always rename, don't delete</DT>
27086 <DD>This means you want to always answer yes and have Alpine automatically
27087 rename the folder if possible.
27088 There will be no deleting of old folders.
27091 <DT>don't rename, ask about deleting</DT>
27092 <DD>This means you want to always answer no.
27093 Alpine will not rename the folder.
27094 You will be asked about deleting old folders.
27097 <DT>don't rename, don't delete</DT>
27098 <DD>This means you want to always answer no.
27099 Alpine will not rename the folder.
27100 There will be no deleting of old folders, either.
27106 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27108 <End of help on this topic>
27111 ====== h_config_reopen_rule =====
27114 <TITLE>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></TITLE>
27117 <H1>OPTION: <!--#echo var="VAR_folder-reopen-rule"--></H1>
27119 Alpine normally checks for new mail in the currently open folder
27120 and in the INBOX every few <A HREF="h_config_mailcheck">minutes</A>.
27123 There are some situations where automatic new-mail checking does not work.
27124 For example, if a mail folder is opened using the POP protocol or a newsgroup
27125 is being read using the NNTP protocol, then new-mail checking is disabled.
27128 It may be possible to check for new mail in these cases by reopening the
27130 Alpine does not do this for you automatically, but you may do the commands
27131 manually to cause this to happen.
27132 You reopen by going back to the folder list screen from the message
27133 index screen with the "<" command,
27134 and then going back into the message index screen with
27135 the ">" command.
27136 (Actually, any method you would normally use to open a folder will work the
27137 same as the "<" followed by ">" method.
27138 For example, the GoTo Folder command will work, or you may use L to go to the
27139 Folder List screen and Carriage Return to reopen the folder.)
27142 There are some cases where Alpine knows that reopening the folder should
27143 be useful as a way to discover new mail.
27144 At the time of this writing, connections made using the POP protocol,
27145 news reading using the NNTP protocol, local news reading, and local
27146 ReadOnly folders that are in the traditional UNIX or the MMDF format all
27147 fall into this category.
27148 There are other cases where it <EM>may</EM> be a way to discover new mail, but Alpine
27149 has no way of knowing, so it might also just be an exercise in futility.
27150 All remote, ReadOnly folders other than those listed just above fall into this
27152 The setting of this option together with the type of folder
27153 controls how Alpine will react to the apparent attempt to reopen a folder.
27156 If you don't reopen, then you will just be back in
27157 the message index with no change.
27158 You left the index and came back, but the folder remained "open"
27160 However, if you do reopen the folder, the folder is closed and then reopened.
27161 In this case, the current state of the open folder is lost.
27162 The New status, Important and Answered flags,
27163 selected state, Zoom state, collapsed or expanded state of threads,
27164 current message number,
27165 and any other temporary state is all lost when the reopen happens.
27166 For POP folders (but not NNTP newsgroups) the Deleted flags are also lost.
27169 In the possibilities listed below, the text says "POP/NNTP" in
27171 That really implies the case where Alpine knows it is a good way to discover
27172 new mail, which is more than just POP and NNTP, but POP and NNTP are
27173 the cases of most interest.
27174 This option probably has more possible values than it deserves. They are:
27177 <DT>Always reopen</DT>
27178 <DD>Alpine will not ask whether you want to reopen but will just do the reopen
27179 whenever you type a command that implies a reopen, regardless of the
27181 In other words, it is assumed you would always answer Yes if asked
27185 <DT>Yes for POP/NNTP, Ask about other remote [Yes]</DT>
27186 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
27187 will ask you whether to reopen other remote folders,
27188 with a default answer of Yes.
27191 <DT>Yes for POP/NNTP, Ask about other remote [No]</DT>
27192 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, but
27193 will ask you whether to reopen other remote folders,
27194 with a default answer of No.
27197 <DT>Yes for POP/NNTP, No for other remote</DT>
27198 <DD>Alpine will assume a Yes answer if the access method is POP or NNTP, and
27199 will assume a No answer for all other remote folders.
27202 <DT>Always ask [Yes]</DT>
27203 <DD>Alpine will not differentiate based on access method.
27204 It will always ask for all remote folders, with a default answer of Yes.
27207 <DT>Always ask [No]</DT>
27208 <DD>Alpine will not differentiate based on access method.
27209 It will always ask for all remote folders, with a default answer of No.
27212 <DT>Ask about POP/NNTP [Yes], No for other remote</DT>
27213 <DD>Alpine will ask if the access method is POP or NNTP, with a default answer
27215 It will never attempt to reopen other remote folders.
27218 <DT>Ask about POP/NNTP [No], No for other remote</DT>
27219 <DD>This is the default.
27220 Alpine will ask if the access method is POP or NNTP, with a default answer
27222 It will never attempt to reopen other remote folders.
27225 <DT>Never reopen</DT>
27226 <DD>Alpine will never attempt to reopen already open folders.
27231 Remember, wherever it says POP or NNTP above it really means POP or NNTP or
27232 any of the other situations where it is likely that reopening is a good way
27233 to discover new mail.
27236 There is an alternative that may be of useful in some situations.
27237 Instead of manually checking for new mail you can set up a
27238 <A HREF="h_maildrop">Mail Drop</A>
27239 and automatically check for new mail.
27243 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27245 <End of help on this topic>
27248 ====== h_config_inc_startup =====
27251 <TITLE>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></TITLE>
27254 <H1>OPTION: <!--#echo var="VAR_incoming-startup-rule"--></H1>
27256 This value affects Alpine's behavior when opening the "INBOX" or
27257 one of the "INCOMING MESSAGE FOLDERS".
27258 It determines which message will be the <EM>current message</EM> when
27259 the folder is first opened.
27260 The default value is "first-unseen".
27263 The seven possible values for this option are:
27266 <DT>first-unseen</DT>
27267 <DD>The current message is set to the first
27268 unseen message that has not been marked deleted, or the last message if
27269 all of the messages have been seen previously.
27270 Messages which have not been seen or which have been seen but re-marked
27271 as New are considered unseen messages.
27272 See the note at the bottom of this help about newsgroups.
27275 <DT>first-recent</DT>
27276 <DD>Similar to the default, but rather than starting on the first
27277 unseen message Alpine starts on the first <EM>recent</EM> message.
27278 A message is recent if it arrived since the last time the folder was
27279 open. This value causes the current message to be set to the first
27280 recent message if there is one, otherwise to the last
27281 message in the folder.
27284 <DT>first-important</DT>
27285 <DD>This will result in the current message being set to the first
27286 message marked Important (but not Deleted).
27287 If no messages are marked Important, then it will be the last message.
27288 Messages are marked Important by <EM>you</EM>, not by the sender, using
27290 <A HREF="h_common_flag">Flag command</A>.
27291 Or they may be marked Important by an Alpine
27292 <A HREF="h_mainhelp_filtering">Filter</A>
27293 that you have set up.
27296 <DT>first-important-or-unseen</DT>
27297 <DD>This selects the first of the first unseen and the first important
27301 <DT>first-important-or-recent</DT>
27302 <DD>This selects the first of the first recent and the first important
27307 <DD>Simply starts you on the <EM>first</EM> undeleted message in the folder.
27308 If all messages are deleted you start on the last message.
27312 <DD>Simply starts you on the <EM>last</EM> undeleted message in the folder
27313 If all messages are deleted you start on the last message.
27318 NOTE: For newsgroups in the incoming collection, "first-unseen" and
27319 "first-recent" are the same and are affected by whether or not the
27321 <A HREF="h_config_news_uses_recent">"<!--#echo var="FEAT_news-approximates-new-status"-->"</A>
27323 Also, there is no permanent storage in news for an Important flag.
27324 This means that no messages will be marked Important when a newsgroup is
27329 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27331 <End of help on this topic>
27334 ====== h_config_browser =====
27337 <TITLE>OPTION: <!--#echo var="VAR_url-viewers"--></TITLE>
27340 <H1>OPTION: <!--#echo var="VAR_url-viewers"--></H1>
27341 <!--chtml if pinemode="os_windows"-->
27342 PC-Alpine users do not need to enter anything here, unless:<UL>
27343 <LI> they want to override, for use with Alpine, the application defined
27344 in the Windows operating system for handling URLs; or
27345 <LI> they are (planning on) using the same configuration file with
27349 Note that if using a viewer that has a space in its path, you should
27350 use the DOS name for that directory or file. Example:
27352 url-viewer=C:\Progra~1\mozilla\mozilla.exe
27356 This option affects Alpine's handling of URLs that are found in
27357 messages you read. Normally, only URLs Alpine can handle directly
27358 are automatically offered for selection in the "Message
27359 Text" screen. When one or more applications
27360 capable of deciphering URLs on their command line are added here, Alpine
27361 will choose the first available to display URLs it cannot handle directly.
27362 A viewer's availability is based on its being specified with a <B>full
27363 directory path</B> and the evaluation of any optionally supplied
27364 parameters described below.
27367 Additionally, to support various connection methods and applications, each
27368 entry in this list can optionally begin with one or more of
27369 the following special tokens. The allowed tokens include:
27373 <DT>_TEST(<VAR>test-string</VAR>)_</DT>
27375 The <VAR>test-string</VAR> is a shell command that Alpine will run to
27376 evaluate a viewer's availability. The command specified by the test
27377 string is run and if its resulting exit status is non-zero, Alpine will
27378 not consider the associated viewer for use.
27381 <DT>_SCHEME(<VAR>scheme-list</VAR>)_</DT>
27383 The <VAR>scheme-list</VAR> is a list of one or more (comma-delimited)
27384 URL schemes that are to be used with the associated viewer. This is
27385 the way to configure Alpine to recognize URLs other than the built-in set.
27387 It can also be used to override Alpine's built-in handlers.
27388 For example, you could specify "news" in the <VAR>scheme-list</VAR>,
27389 and Alpine would use (provided it passed all other criteria) the associated
27390 viewer when it encounterd a URL of the form "news:comp.mail.pine".
27396 By default, Alpine will simply append a space character followed by the
27397 selected URL prior to launching the command in your specified SHELL. You can
27398 optionally specify where in the command the selected URL should appear
27399 by using the "_URL_" token. All occurrences found in the command
27400 will be replaced with the selected URL before the command is handed
27401 to the shell. If such replacement occurs, the default appending of the
27402 selected URL does not take place.
27405 NOTE: If the viewer you specify has any command-line arguments,
27406 including the "_URL_" token, you will need to add a
27407 double-quote character before the command path and after the last
27408 argument (see the "lynx" example below).
27411 So, here are some example entries:
27413 url-viewers = _TEST("test -n '${DISPLAY}'")_ /usr/local/bin/netscape
27414 "/usr/local/bin/lynx _URL_"
27415 C:\BIN\NETSCAPE.BAT
27418 This example shows that for the first viewer in the list to be used
27419 the environment variable "DISPLAY" must be defined. If it
27420 is, then the path and file "/usr/local/bin/netscape" must exist.
27421 If neither condition is met,
27422 then the path and file "/usr/local/bin/lynx" must exist.
27423 If it does, then the "_URL_" token is replaced by the selected URL.
27424 If the path to "lynx" is invalid,
27425 then the final path and file C:\BIN\NETSCAPE.BAT must exist.
27427 entry is a DOS/Windows path. This is one way to support Alpine running
27428 on more than one architecture with the same configuration file.<P>
27430 <!--chtml if pinemode="os_windows"-->
27432 Note that depending on the type of browser used and the method of
27433 its invocation (such as whether it will open in a separate window) from
27434 the MESSAGE TEXT screen, the browser may "supplant"
27435 the MESSAGE TEXT screen, and you will have to quit the browser to return to
27436 it (for example, when using Lynx; to exit Lynx, use the "Q" command).
27437 In other words, launching the browser from Alpine may make Alpine
27438 "disappear" (although it is still "running")
27439 until you close the browser again.<P>
27440 <UL><LI><A HREF="h_config_browser_xterm">Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27441 environment: for advanced users and systems administrators</A>
27444 <P>If you are unsure what browsers are available on your system or how to
27445 specify them in Alpine's <!--#echo var="VAR_url-viewers"--> option for best usability, contact your
27446 local computing support staff.
27448 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27451 <End of help on this topic>
27454 ====== h_config_history =====
27457 <TITLE>OPTION: <!--#echo var="VAR_default-directories"--></TITLE>
27460 <H1>OPTION: <!--#echo var="VAR_default-directories"--></H1>
27462 This option allows you to input a list of directories that Alpine will offer
27463 for you to use when you are saving or exporting attachments. This is useful
27464 when navigating to specific directories becomes too tedious, or when you
27465 need to do this on a daily basis, and want Alpine to remember this on a
27468 The list of directories saved here can be accessed using the ^Y and ^V commands
27469 in the save prompt for attachments, or the export command.
27472 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27475 <End of help on this topic>
27478 ====== h_config_browser_xterm =====
27481 <TITLE><!--#echo var="VAR_url-viewers"--> and X windows applications</TITLE>
27484 <H1>Defining <!--#echo var="VAR_url-viewers"--> in an X windows
27485 environment: for advanced users and systems administrators</H1>
27486 If you are using Alpine with an X-terminal (emulator) and want to define an
27487 X windows-based application in <!--#echo var="VAR_url-viewers"-->,
27488 you may want to do so in a manner that causes any <B>already</B>
27489 invoked viewer application to be used for viewing URLs you select from Alpine
27490 messages, and a <B>new</B> URL-viewer process to be
27491 started <B>only</B> if the same application has <B>not already</B>
27492 been launched -- for one reason, to avoid file-locking contentions among
27493 multiple invocations of the same URL-viewer application.
27494 (The example entries set in the help screen for the "<!--#echo var="VAR_url-viewers"-->"
27495 option does not do this.) A method of doing that would be:<OL>
27497 the _TEST(<VAR>test-string</VAR>)_ token in the <B>first</B> entry to
27498 check (using commands appropriate for your Unix shell
27499 in place of <VAR>test-string</VAR>) for the presence of a
27500 lockfile created by the URL-viewer application -- which implies that the
27501 application is already running, though this is not foolproof.
27502 Following that in the same <!--#echo var="VAR_url-viewers"--> entry, specify the
27503 application with its appropriate command line option(s) to
27504 show the URL selected from the Alpine message in an already open window of
27505 that application, or perhaps in a new window of that application.
27508 <B>second</B> entry for the <!--#echo var="VAR_url-viewers"--> option, specify the same
27509 application without those command line options, but this time using the
27510 _TEST(...)_ token to check whether the environment variable "DISPLAY"
27512 <LI> If you will be using Alpine (with the same .pinerc file) outside of the X
27513 windows environment (for instance, using VT-100 terminal emulation), you
27514 may wish to specify a non-X windows URL-viewer application such as Lynx
27517 How exactly you define your <!--#echo var="VAR_url-viewers"--> entries to do this will depend on
27518 the command shell, the URL-viewer application(s), and possibly the specific
27519 version of the latter, you are using.
27522 line options for the Netscape browser for showing URLs (selected from Alpine)
27523 when Netscape is already running are discussed in the document
27524 "Remote Control of UNIX Netscape"
27525 found at the URL (as of 12 Aug. 1998):
27528 <CENTER><A HREF="http://home.netscape.com/newsref/std/x-remote.html">http://home.netscape.com/newsref/std/x-remote.html</A></CENTER>
27530 <P>(If the URL-viewer application is
27531 <B>not</B> running on the same host as Alpine, but being launched from an
27532 applications server, you may not be able to use the command line options for
27533 using an existing invocation of the application in Alpine's <!--#echo var="VAR_url-viewers"--> entry.)
27535 <!--chtml if this-method="shown-to-work"-->
27536 An example using the Korn shell and the Netscape browser (first entry wrapped
27537 because of its length, but should all appear on one line):
27539 url-viewers = _TEST("test -L /myhomedir/.netscape/lock")_ "/usr/local/bin/netscape -remote 'openURL(_URL_, new-window)' &"<BR>
27541 _TEST("test -n '${DISPLAY}'")_ "/usr/local/bin/netscape &"<BR>
27542 "/usr/local/bin/lynx '_URL_'"
27547 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27549 <End of help on this topic>
27552 ====== h_config_enable_full_hdr =====
27555 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></TITLE>
27558 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-cmd"--></H1>
27560 This feature enables the "H Full Headers" command which toggles between
27561 the display of all headers in the message and the normal edited view of
27562 headers. The Full Header command also controls which headers are included
27563 for Export, Pipe, Print, Forward, and Reply functions. (For Reply, the
27564 Full Header mode will respect the
27565 <A HREF="h_config_include_header">"Include-Headers-in-Reply"</A>
27568 If Full Header mode is turned on and you Forward a message, you will
27569 be asked if you'd like to forward the message as an attachment, as opposed
27570 to including the text of the message in the body of your new message.
27572 If you have also turned on the
27573 <A HREF="h_config_quote_suppression">"Quote Suppression"</A>
27574 option then the Full Headers command actually rotates through three states
27575 instead of just two.
27576 The first is the normal view with long quotes suppressed.
27577 The second is the normal view but with the long quotes included.
27578 The last enables the display of all headers in the message.
27579 When using Export, Pipe, Print, Forward, or Reply the quotes are
27580 never suppressed, so the first two states are identical.
27582 Normally, the Header Mode will reset
27583 to the default behavior when moving to a new message.
27584 The mode can be made to persist from message to message by setting the feature
27585 <A HREF="h_config_quell_full_hdr_reset"><!--#echo var="FEAT_quell-full-header-auto-reset"--></A>.
27588 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27590 <End of help on this topic>
27593 ====== h_config_enable_full_hdr_and_text =====
27596 <TITLE>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></TITLE>
27599 <H1>FEATURE: <!--#echo var="FEAT_enable-full-header-and-text"--></H1>
27601 This feature affects how the "H Full Headers" command displays
27602 message text. If set, the raw message text will be displayed. This
27603 especially affects MIME formatted email, where the entire MIME format
27604 will be displayed. This feature similarly affects how messages are
27605 included for the Export, Pipe, Print, Forward, and Reply functions.
27607 When viewing a raw message that has attachments with this feature set,
27608 you will not be able to view attachments without first leaving full
27609 headers mode. This is because MIME parsing is not done on the raw message.
27612 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27614 <End of help on this topic>
27617 ====== h_config_enable_pipe =====
27620 <TITLE>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></TITLE>
27623 <H1>FEATURE: <!--#echo var="FEAT_enable-unix-pipe-cmd"--></H1>
27625 This feature enables the "| Pipe" command that sends the current message
27626 to the specified command for external processing.
27629 A short description of how the pipe command works is given
27630 <A HREF="h_pipe_command">here</A>.
27634 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27636 <End of help on this topic>
27639 ====== h_config_quell_full_hdr_reset =====
27642 <TITLE>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></TITLE>
27645 <H1>FEATURE: <!--#echo var="FEAT_quell-full-header-auto-reset"--></H1>
27647 The <A HREF="h_common_hdrmode">HdrMode Command</A>
27648 normally resets to the default state when switching to a new message.
27649 For example, if you've used the "H" command to turn on Full
27650 Headers for a message you are viewing, and then you type the Next command
27651 to look at the next message, the full headers will no longer be shown.
27652 Setting this feature disables that reset.
27653 Instead, the Header Mode remains the same from message to message.
27656 The presence or absence of the HdrMode command is determined by the
27657 <A HREF="h_config_enable_full_hdr">"<!--#echo var="FEAT_enable-full-header-cmd"-->"</A>
27658 Feature-List option.
27661 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27663 <End of help on this topic>
27666 ====== h_config_enable_tab_complete =====
27669 <TITLE>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></TITLE>
27672 <H1>FEATURE: <!--#echo var="FEAT_enable-tab-completion"--></H1>
27674 This feature enables the TAB key when at a prompt for a filename. In this
27675 case, TAB will cause the partial name already entered to be automatically
27676 completed, provided the partial name is unambiguous.
27677 This feature is on by default.
27679 Similarly, this feature also enables TAB completion of address book
27680 nicknames when at a prompt for a nickname,
27681 or when typing in an address field in the composer.
27683 <End of help on this topic>
27686 ====== h_config_quit_wo_confirm =====
27689 <TITLE>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></TITLE>
27692 <H1>FEATURE: <!--#echo var="FEAT_quit-without-confirm"--></H1>
27694 This feature controls whether or not Alpine will ask for confirmation when a
27695 Quit command is received.
27697 <End of help on this topic>
27700 ====== h_config_quote_replace_noflow =====
27703 <TITLE>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></TITLE>
27706 <H1>FEATURE: <!--#echo var="FEAT_quote-replace-nonflowed"--></H1>
27708 This feature, which is only active when
27709 <A HREF="h_config_quote_replace_string"><!--#echo var="VAR_quote-replace-string"--></A> is
27711 enables quote-replacement on non-flowed messages. It is off
27712 by default because a non-flowed message is more dependent on its format,
27713 and thus quote-replacement may cause less-than-pleasing results.
27714 Setting this feature will cause quote-replacement similar to that of flowed
27715 messages, but with the added possibility of long lines being wrapped
27716 into new lines if the Quote-Replacement-String is longer than the string
27717 it is replacing, which is "> ".
27719 <End of help on this topic>
27722 ====== h_config_enable_jump =====
27725 <TITLE>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></TITLE>
27728 <H1>FEATURE: <!--#echo var="FEAT_enable-jump-shortcut"--></H1>
27730 When this feature is set you may enter a number (followed by RETURN)
27731 and jump to that message number, when in the MESSAGE INDEX or MESSAGE TEXT
27732 screens. In other words, it obviates the need for typing the "J" for the
27735 <End of help on this topic>
27738 ====== h_config_enable_alt_ed =====
27741 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></TITLE>
27744 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-cmd"--></H1>
27746 If this feature is set (the default), and the
27747 <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27748 <B>is not</B> set, entering
27749 the ^_ (Ctrl-underscore) key while composing a message will prompt you
27750 for the name of the editor you would like to use.
27752 If the environment variable $EDITOR is set, its value will be offered as
27755 If the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A> option
27756 <B>is</B> set, the ^_ key will activate the specified
27757 editor without prompting, in which case it is not necessary to
27758 set the "<!--#echo var="FEAT_enable-alternate-editor-cmd"-->" feature.
27761 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27763 <End of help on this topic>
27766 ====== h_config_alt_ed_now =====
27769 <TITLE>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></TITLE>
27772 <H1>FEATURE: <!--#echo var="FEAT_enable-alternate-editor-implicitly"--></H1>
27774 If this feature and the <A HREF="h_config_editor">"<!--#echo var="VAR_editor"-->"</A>
27775 variable are both set, Alpine will
27776 automatically activate the specified editor when the cursor is moved from
27777 the header of the message being composed into the message text. For
27778 replies, the alternate editor will be activated immediately. If this
27779 feature is set but the "<!--#echo var="VAR_editor"-->" variable is not set, then Alpine will
27780 automatically ask for the name of an alternate editor when the cursor
27781 is moved out of the header being composed, or if a reply is being done.
27784 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27787 <End of help on this topic>
27790 ====== h_config_enable_bounce =====
27793 <TITLE>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></TITLE>
27795 <H1>FEATURE: <!--#echo var="FEAT_enable-bounce-cmd"--></H1>
27798 Setting this feature enables the "B Bounce" command, which will prompt
27799 for an address and *remail* the message to the new recipient. This command
27800 is used to re-direct messages that you have received in error, or need to
27801 be redirected for some other reason (e.g. list moderation). The final
27802 recipient will see a header indicating that you have Resent the msg, but
27803 the message's From: header will show the original author of the message,
27804 and replies to it will go back to that author, and not to you.
27806 <End of help on this topic>
27809 ====== h_config_enable_agg_ops =====
27812 <TITLE>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></TITLE>
27815 <H1>FEATURE: <!--#echo var="FEAT_enable-aggregate-command-set"--></H1>
27817 When this feature is set you may use the commands and subcommands that relate to
27818 performing operations on more than one message at a time. We call these
27819 "aggregate operations". In particular, the
27820 <!--chtml if pinemode="function_key"-->"F5
27821 <!--chtml else-->";
27822 <!--chtml endif--> Select",
27824 <!--chtml if pinemode="function_key"-->
27830 <!--chtml if pinemode="function_key"-->
27835 Zoom" commands are enabled by this feature. Select is used to
27836 "tag" one or more messages meeting the specified criteria. Apply can
27837 then be used to apply any message command to all of the selected/tagged
27838 messages. Further, the Zoom command allows you to toggle the MESSAGE INDEX
27839 view between just those Selected and all messages in the folder.
27841 This feature also enables the
27842 <!--chtml if pinemode="function_key"-->
27848 subcommand in the MESSAGE INDEX
27849 WhereIs command that causes all messages matching the WhereIs argument to
27850 become selected; and the Select, Select Current, and ZoomMode commands in the
27851 <A HREF="h_folder_maint">FOLDER LIST screen</A>.
27853 Some related help topics are
27855 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
27856 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
27857 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>,
27858 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
27859 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
27860 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
27864 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
27866 <End of help on this topic>
27870 ====== h_config_enable_flag =====
27873 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></TITLE>
27876 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-cmd"--></H1>
27878 Setting this feature enables the
27879 <A HREF="h_common_flag">"* Flag"</A>
27880 command that allows you to
27881 manipulate the status flags associated with a message. By default, Flag
27882 will set the "Important" flag, which results in an asterisk being
27883 displayed in column one of the MESSAGE INDEX for such messages.
27885 <End of help on this topic>
27888 ====== h_config_flag_screen_default =====
27891 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></TITLE>
27894 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-implicitly"--></H1>
27896 The feature modifies the behavior of the
27897 <a href="h_common_flag">Flag</a>
27898 command (provided it too is
27899 <A HREF="h_config_enable_flag">enabled</A>).
27900 By default, when the "* Flag" command is selected,
27901 Alpine offers a prompt to set one of several flags and also offers the
27902 option of entering the detailed flag manipulation screen via the "^T"
27903 key. Enabling this feature causes Alpine to immediately enter the detailed
27904 flag screen rather than first offer the simple prompt.
27906 <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.
27908 <End of help on this topic>
27911 ====== h_config_flag_screen_kw_shortcut =====
27914 <TITLE>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></TITLE>
27917 <H1>FEATURE: <!--#echo var="FEAT_enable-flag-screen-keyword-shortcut"--></H1>
27919 This feature modifies the behavior of the
27920 <a href="h_common_flag">Flag</a> command
27921 and the <A HREF="h_index_cmd_select">Select</A> command.
27922 This feature is set by default.
27923 When this feature is not set, when the "* Flag" command is selected,
27924 Alpine offers a prompt to set one of several flags and also offers the
27925 option of entering the detailed flag manipulation screen via the "^T"
27928 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
27929 defined, then enabling this feature adds a shortcut way to set or unset
27931 You use "*" followed by the first letter of a keyword (or the nickname of
27932 a keyword if you've given it a nickname) and that will set the keyword.
27934 An example is easier to understand than the explanation.
27935 The flag command can always be used to set the system flags.
27936 For example, to set the Answered flag you would type
27938 <CENTER><SAMP>* A</SAMP></CENTER>
27940 Now suppose you have defined a keyword "Work" using the <!--#echo var="VAR_keywords"-->
27941 option in the Config screen.
27942 By default, to set a keyword like "Work" you would usually
27943 have to go to the Flag Details screen using
27944 the "^T To Flag Details" command.
27945 Instead, if you have enabled this feature, you may type
27947 <CENTER><SAMP>* W</SAMP></CENTER>
27949 to set the Work flag, or
27951 <CENTER><SAMP>* ! W</SAMP></CENTER>
27954 Just like for the other flag setting commands, the case of the letter does
27955 not matter, so "w" or "W" both set the "Work"
27958 Notice that you can only use this trick for one keyword that begins
27959 with "W".
27960 If you happen to have a "Work" keyword and another keyword that is
27961 "WIFI" the "* W" command will set the first one in
27962 your list of keywords.
27963 Also, there are five letters that are reserved for system
27964 flags and the NOT command.
27965 If you type "* A" it will always set the Answered flag, not
27966 your "Aardvark" keyword.
27967 In order to set the "Aardvark" keyword you'll still have to use
27968 the Flag Details screen.
27970 Because enabling the
27971 <A HREF="h_config_flag_screen_default"><!--#echo var="FEAT_enable-flag-screen-implicitly"--></A>
27972 option causes Alpine to skip directly to the Flag Details screen when the
27973 Flag command is used,
27974 setting it will cause this feature to have no effect at all.
27976 Similarly, when Selecting by Keyword, setting this option will allow you
27977 to use Keyword initials instead of full keywords.
27979 <End of help on this topic>
27982 ====== h_config_can_suspend =====
27985 <TITLE>FEATURE: <!--#echo var="FEAT_enable-suspend"--></TITLE>
27988 <H1>FEATURE: <!--#echo var="FEAT_enable-suspend"--></H1>
27990 Setting this feature will allow you to type ^Z (Control Z) to
27991 <!--chtml if pinemode="os_windows"-->
27992 minimize Alpine into its icon, bringing into focus whatever
27993 application is running behind the PC-Alpine window.
27995 temporarily suspend Alpine.
27998 This does not exit Alpine, but puts it in the background to watch
27999 for new mail and such. Normally, you type a command, such
28000 as "fg" at your system prompt to return to your Alpine session.
28003 The <A HREF="h_config_suspend_spawns"><!--#echo var="FEAT_use-subshell-for-suspend"--></A> feature
28004 adjusts whether Alpine is placed into the background of the shell its
28005 running in or starts a news shell.
28010 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28012 <End of help on this topic>
28015 ====== h_config_take_lastfirst ======
28018 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></TITLE>
28021 <H1>FEATURE: <!--#echo var="FEAT_disable-take-last-comma-first"--></H1>
28023 Normally, when TakeAddr is used to copy an address from a message into
28024 an address book entry, Alpine will attempt to rewrite the full name of the
28025 address in the form
28028 Last, First<P>
28032 First Last
28035 It does this because many people find it useful to sort by Last name
28036 instead of First name. If this feature is set, then the TakeAddr command
28037 will not attempt to reverse the name in this manner.
28039 <End of help on this topic>
28041 ====== h_config_disable_regex ======
28044 <TITLE>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></TITLE>
28047 <H1>FEATURE: <!--#echo var="FEAT_disable-regular-expression-matching-for-alternate-addresses"--></H1>
28050 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
28051 option is interpreted as a regular expression.
28052 One type of address that might cause trouble is an address that
28053 contains a plus sign.
28054 If you want to have an address with a plus as one of your
28055 <!--#echo var="VAR_alt-addresses"-->
28056 and you don't want to use regular expressions, then setting this
28057 feature will cause Alpine to treat the addresses you list literally instead.
28059 <End of help on this topic>
28061 ====== h_config_take_fullname ======
28064 <TITLE>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></TITLE>
28067 <H1>FEATURE: <!--#echo var="FEAT_disable-take-fullname-in-addresses"--></H1>
28069 Normally, when TakeAddr is used to copy an address or addresses
28070 from a message into an address book entry, Alpine will try to preserve
28071 the full name associated with each address in the list of addresses.
28072 The reason for this is so that if the entry is a list or later becomes a
28073 list, then information about the individual addresses in the list
28075 If you would rather just have the simple addresses in the list of addresses,
28076 set this feature. For example, with the default setting you might
28077 see something like this in the ADDRESS BOOK editor after you type TakeAddr
28081 Fullname : Bedrock Elders
28084 Addresses : Fred Flintstone <flint@bedrock.org>,
28085 Barney Rubble <rubble@bedrock.org>
28088 but with this feature set it would look like
28092 Fullname : Bedrock Elders
28095 Addresses : flint@bedrock.org,
28099 instead. Note the difference in the Addresses field.
28101 <End of help on this topic>
28103 ====== h_config_print_from ======
28106 <TITLE>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></TITLE>
28109 <H1>FEATURE: <!--#echo var="FEAT_print-includes-from-line"--></H1>
28111 If this feature is set, then the Berkeley-mail style From line is included
28112 at the start of each message that is printed. This line looks something
28113 like the following, with the address replaced by the address from the
28114 From line of the message being printed:
28116 From user@domain.somewhere.com Mon May 13
28119 <End of help on this topic>
28122 ====== h_config_expanded_distlists ======
28125 <TITLE>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></TITLE>
28128 <H1>FEATURE: <!--#echo var="FEAT_expanded-view-of-distribution-lists"--></H1>
28129 If this feature is set, then distribution lists in the address book
28130 screen will always be expanded automatically.
28132 <End of help on this topic>
28135 ====== h_config_compose_news_wo_conf ======
28138 <TITLE>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></TITLE>
28141 <H1>FEATURE: <!--#echo var="FEAT_compose-sets-newsgroup-without-confirm"--></H1>
28142 This feature controls one aspect of Alpine's Composer. If you enter the
28143 composer while reading a newsgroup, you will normally be prompted to
28144 determine whether you intend the new message to be posted to the current
28145 newsgroup or not. If this feature is set, Alpine will not prompt you
28146 in this situation, and will assume that you do indeed wish to post
28147 to the newsgroup you are reading.
28149 <End of help on this topic>
28152 ====== h_config_compose_rejects_unqual ======
28155 <TITLE>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></TITLE>
28158 <H1>FEATURE: <!--#echo var="FEAT_compose-rejects-unqualified-addrs"--></H1>
28160 This feature controls one aspect of the message composer; in particular,
28161 what happens when an unqualified name is entered into an address header.
28162 If set, unqualified names entered as addresses will be treated as errors
28163 unless they match an addressbook nickname. Alpine will not attempt to turn
28164 them into complete addresses by adding your local domain.<P>
28166 A complete (fully qualified) address is one containing a username followed
28167 by an "@" ("at") symbol, followed by a domain name (e.g.
28168 "jsmith@example.com"). An unqualified name is one <B>without</B>
28169 the "@" symbol and domain name (e.g. "jsmith").
28171 (See also <A HREF="h_address_format">Explanation of Address formats</A>.)
28175 When you enter a fully qualified address, Alpine does not interpret or
28176 modify it, but simply passes it on to the mail-transport-agent (MTA) for
28177 your system. Alpine conforms to the Internet standards governing message
28178 headers and will not send an unqualifed name to the MTA. Therefore, when
28179 you enter an unqualified name, Alpine will normally attempt to turn it into
28180 a fully qualified address, first by checking to see if you have entered a
28181 matching nickname in your addressbook, or failing that, by simply adding
28182 your own domain to the name entered. So if your address is
28183 "jsmith@example.com" and you enter "fred", then (assuming
28184 "fred" is not a nickname in your addressbook), Alpine will turn
28185 that into "fred@example.com".<P>
28187 There are situations where it is not desirable for Alpine to interpret such
28188 unqualified names as valid (local) addresses. For example, if "fred"
28189 turned out to be a typo (intended to be an addressbook nickname), but
28190 there actually was a "fred" in your local domain, the message might
28191 be mis-delivered without your realizing it. In order to reduce the likelihood
28192 of such accidents, setting this feature will cause Alpine to treat such
28193 addresses as errors, and require that you explicitly enter the full local
28194 address (e.g. "fred@example.com") or correct the name so that it
28195 matches an address book nickname.<P>
28197 Consider this a safety feature against mis-directed mail.
28200 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28202 <End of help on this topic>
28205 ====== h_config_quell_local_lookup ======
28208 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></TITLE>
28211 <H1>FEATURE: <!--#echo var="FEAT_quell-user-lookup-in-passwd-file"--></H1>
28213 This feature controls an aspect of Alpine's Composer, and if needed, will
28214 usually be set by your system manager in Alpine's system-wide configuration
28215 file. Specifically, if this feature is set, Alpine will not attempt to look
28216 in the system password file to find a Full Name for the entered address.
28218 Normally, names you enter into address fields (e.g. To: or Cc:) are
28219 checked against your address book(s) to see if they match an address book
28220 nickname. Failing that, (in Unix Alpine) the name is then checked against
28221 the Unix password file. If the entered name matches a username in the
28222 system password file, Alpine extracts the corresponding Full Name information
28223 for that individual, and adds that to the address being entered.
28225 However, password file matching can have surprising (incorrect) results if
28226 other users of the system do not receive mail at the domain you are using.
28227 That is, if either the
28228 <A HREF="h_config_user_dom">"<!--#echo var="VAR_user-domain"-->"</A> or
28229 <A HREF="h_config_domain_name">"<!--#echo var="VAR_use-only-domain-name"-->"</A>
28231 is set such that the administrative domain of other users on the system
28232 isn't accurately reflected, Alpine should be told that a passwd file match
28233 is coincidental, and Full Name info will be incorrect. For example, a
28234 personal name from the password file could get falsely paired with the
28235 entered name as it is turned into an address in the configured domain.
28237 If you are seeing this behavior, enabling this feature will prevent Unix
28238 Alpine from looking up names in the password file to find the Full Name
28239 for incomplete addresses you enter.<P>
28241 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28244 <End of help on this topic>
28247 ====== h_config_tab_checks_recent ======
28250 <TITLE>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></TITLE>
28253 <H1>FEATURE: <!--#echo var="FEAT_tab-checks-recent"--></H1>
28255 In a FOLDER LIST screen, the TAB key usually just changes which
28256 folder is highlighted.
28257 If this feature is set, then the TAB key will cause the number of
28258 recent messages and the total number of messages in the highlighted folder
28259 to be displayed instead.
28262 <End of help on this topic>
28265 ====== h_config_maildrops_preserve_state ======
28268 <TITLE>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></TITLE>
28271 <H1>FEATURE: <!--#echo var="FEAT_maildrops-preserve-state"--></H1>
28273 This feature affects the way <A HREF="h_maildrop">Mail Drops</A> work.
28274 Normally, when mail is moved from a Mail Drop folder to a destination
28275 folder, it is delivered as new mail.
28276 Any Seen/New, Answered, Important/Flagged state that has changed will be
28278 All of the mail will be considered unSeen, unAnswered, and unImportant after
28281 If this feature is set, then the state changes that have been made
28282 to the messages in the Mail Drop folder will be preserved.
28284 In any case, messages that are already marked Deleted when the
28285 mail is to be moved from the Mail Drop will be ignored.
28287 <End of help on this topic>
28290 ====== h_config_preopen_stayopens ======
28293 <TITLE>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></TITLE>
28296 <H1>FEATURE: <!--#echo var="FEAT_preopen-stayopen-folders"--></H1>
28298 This feature is related to the option
28299 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
28300 Normally, Stay Open folders are only opened on demand, when the user
28302 From then on they are kept open for the duration of the session.
28303 However, if this feature is set, then the Stay Open folders will all be
28304 opened at startup, at the same time that the INBOX is opened.
28307 <End of help on this topic>
28310 ====== h_config_expunge_inbox ======
28313 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></TITLE>
28316 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-inbox"--></H1>
28318 The INBOX is normally treated differently from regular folders in several
28320 One of the differences is that the normal "close" sequence of
28321 events is deferred until Alpine is exited, instead of happening when you
28322 leave the INBOX to view another folder.
28323 The "close" sequence normally includes the Expunging
28324 of deleted messages
28325 (either automatically or after a prompt, controlled by the features
28326 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28327 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28328 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28330 <A HREF="h_config_read_message_folder"><!--#echo var="VAR_read-message-folder"--></A>.
28333 If this feature is set the "close" sequence handling will take
28334 place every time you leave the INBOX.
28335 The INBOX will still be kept open, but the offer to Expunge and the archiving
28336 to the <!--#echo var="VAR_read-message-folder"-->
28337 will take place each time you leave the INBOX instead of only once at the
28338 end of the session.
28341 <End of help on this topic>
28344 ====== h_config_expunge_stayopens ======
28347 <TITLE>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></TITLE>
28350 <H1>FEATURE: <!--#echo var="FEAT_offer-expunge-of-stayopen-folders"--></H1>
28352 This feature is related to the option
28353 <A HREF="h_config_permlocked">"<!--#echo var="VAR_stay-open-folders"-->"</A>.
28354 Stay Open folders are treated differently from regular folders in several
28356 One of the differences is that the normal "close" sequence of
28357 events is deferred until Alpine is exited, instead of happening when you
28358 leave the folder to view another folder.
28359 The "close" sequence normally includes the Expunging
28360 of deleted messages
28361 (either automatically or after a prompt, controlled by the features
28362 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>,
28363 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>, and
28364 <A HREF="h_config_expunge_manually"><!--#echo var="FEAT_expunge-only-manually"--></A>), and the
28366 <A HREF="h_config_archived_folders"><!--#echo var="VAR_incoming-archive-folders"--></A>.
28369 If this feature is set the "close" sequence handling will take
28370 place when you leave the Stay Open folder.
28371 The folder will still be kept open, but the offer to Expunge and the archiving
28372 will take place each time you leave the folder instead of only once at the
28373 end of the session.
28374 This feature does not affect the INBOX, which will still only be processed
28375 when you exit Alpine.
28376 However, there is a similar feature that affects only the INBOX called
28377 <A HREF="h_config_expunge_inbox">"<!--#echo var="FEAT_offer-expunge-of-inbox"-->"</A>.
28380 <End of help on this topic>
28383 ====== h_config_preserve_start_stop ======
28386 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></TITLE>
28389 <H1>FEATURE: <!--#echo var="FEAT_preserve-start-stop-characters"--></H1>
28391 This feature controls how special control key characters, typically
28392 Ctrl-S and Ctrl-Q, are interpreted when input to Alpine. These characters
28393 are known as the "stop" and "start" characters and are sometimes used in
28394 communications paths to control data flow between devices that operate at
28399 By default, Alpine turns the system's handling of these special characters
28400 off except during printing. However, if you see Alpine reporting input errors
28403 [ Command "^Q" not defined for this screen.]
28405 and, at the same time, see your display become garbled, then it is likely
28406 that setting this option will solve the problem. Be aware, though, that
28407 enabling this feature will also cause Alpine to ostensibly "hang"
28408 whenever the Ctrl-S key combination is entered as the system is now
28409 interpreting such input as a "stop output" command. To "start
28410 output" again, simply type Ctrl-Q.
28412 <End of help on this topic>
28415 ====== h_config_enable_incoming ======
28418 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></TITLE>
28421 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders"--></H1>
28423 Alpine's Incoming Message Folders collection
28424 provides a convenient way to access multiple incoming folders.
28425 It is also useful if you have accounts on multiple computers.
28428 If set, this feature defines a pseudo-folder collection called
28429 "INCOMING MESSAGE FOLDERS". Initially, the only folder included
28430 in this collection will be your INBOX, which will no longer show up in
28431 your Default folder collection.
28434 You may add more folders to the Incoming Message Folders collection by
28436 <!--chtml if pinemode="function_key"-->
28441 Add" command in the FOLDER LIST screen. You will be prompted for
28442 the host the folder is stored on (which defaults to the same host used
28443 for your INBOX), a nickname, and the actual folder name. Once a set
28444 of Incoming Message Folders are defined, the TAB key (in MESSAGE INDEX
28445 or MESSAGE TEXT screens) may be used to scan the folders for those
28446 with Recent messages. If you add more folders to
28447 your <!--#echo var="VAR_incoming-folders"--> collection, turning this feature back off will have
28450 NOTE: Normally the software that actually delivers mail (the stuff that happens
28451 before Alpine is involved) is in a better position to do delivery filtering
28452 than is Alpine itself.
28453 If possible, you may want to look at programs such as
28454 "filter" or "procmail", which are examples of delivery
28455 filtering programs.
28456 If you'd prefer to have Alpine do the filtering for you, you may set that
28458 Look <A HREF="h_rules_filter">here</A> for help with Alpine filtering.
28461 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28463 <End of help on this topic>
28466 ====== h_config_enable_incoming_checking ======
28469 <TITLE>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></TITLE>
28472 <H1>FEATURE: <!--#echo var="FEAT_enable-incoming-folders-checking"--></H1>
28474 This feature is only operational if you have enabled the optional
28475 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A> collection.
28476 If you do have Incoming Message Folders and you also set this feature,
28477 then the number of Unseen messages in each folder will be displayed
28478 in the FOLDER LIST screen for the Incoming Message Folders.
28479 The number of Unseen messages in a folder will be displayed in parentheses
28480 to the right of the name of each folder.
28481 If there are no Unseen messages in a folder then only the name
28482 is displayed, not a set of parentheses with zero inside them.
28483 A redraw command, Ctrl-L, can be used in the FOLDER LIST screen for
28484 the Incoming Message Folders to cause an immediate update.
28486 If a check for Unseen messages fails for a particular folder then Alpine
28487 will no longer attempt to check that folder for the duration of the
28488 session and this will be indicated by a question mark inside the
28492 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>,
28493 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>,
28494 <A HREF="h_config_incoming_list"><!--#echo var="VAR_incoming-check-list"--></A>,
28495 <A HREF="h_config_incoming_interv"><!--#echo var="VAR_incoming-check-interval"--></A>,
28496 <A HREF="h_config_incoming_second_interv"><!--#echo var="VAR_incoming-check-interval-secondary"--></A>, and
28497 <A HREF="h_config_incoming_timeo"><!--#echo var="VAR_incoming-check-timeout"--></A>
28498 all affect how this feature behaves.
28501 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28503 <End of help on this topic>
28506 ====== h_config_incoming_checking_total ======
28509 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></TITLE>
28512 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-includes-total"--></H1>
28514 This option has no effect unless the feature
28515 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28516 is set, which in turn has no effect unless
28517 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28520 When incoming folder checking is turned on the default is to display
28521 the number of unseen messages in each folder.
28522 More precisely, it is the number of undeleted unseen messages.
28523 Using this option you may also display the total number of messages
28525 Instead of a single number representing the number of unseen messages
28526 you will get two numbers separated by a slash character.
28527 The first is the number of unseen messages and the second is the
28528 total number of messages.
28530 You may also use the recent message count instead of the unseen message
28531 count by turning on the feature
28532 <A HREF="h_config_incoming_checking_recent"><!--#echo var="FEAT_incoming-checking-uses-recent"--></A>.
28535 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28537 <End of help on this topic>
28540 ====== h_config_incoming_checking_recent ======
28543 <TITLE>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></TITLE>
28546 <H1>FEATURE: <!--#echo var="FEAT_incoming-checking-uses-recent"--></H1>
28548 This option has no effect unless the feature
28549 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
28550 is set, which in turn has no effect unless
28551 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
28554 When incoming folder checking is turned on the default is to display
28555 the number of unseen messages in each folder.
28556 More precisely, it is the number of undeleted unseen messages.
28557 Using this option you may display the number of recent messages instead
28558 of the number of unseen messages.
28559 A message is only counted as recent if this is the first session to
28560 see it, so the recent count might be less than the unseen count.
28561 The difference between the two would be accounted for by the unseen messages
28562 in the folder which were there previously but have not been looked at yet.
28564 If you simultaneously run more than one email client at a time
28565 (for example, you run more than one Alpine in parallel) then turning
28566 this feature on can cause some confusion.
28567 The confusion stems from the fact that each message is only considered to be
28568 recent in one session.
28569 That means that the counts of new messages may be different in the two
28570 Alpines running side by side, because each incoming message will only be
28571 counted as recent in one of the two sessions.
28573 You may also display the total number of messages
28574 in each folder by using the
28575 <A HREF="h_config_incoming_checking_total"><!--#echo var="FEAT_incoming-checking-includes-total"--></A>
28579 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28581 <End of help on this topic>
28584 ====== h_config_attach_in_reply ======
28587 <TITLE>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></TITLE>
28590 <H1>FEATURE: <!--#echo var="FEAT_include-attachments-in-reply"--></H1>
28592 This feature controls an aspect of Alpine's Reply command. If set, any MIME
28593 attachments that were part of the original message will automatically be
28594 included in the Reply.
28596 <End of help on this topic>
28599 ====== h_config_include_header =====
28602 <TITLE>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></TITLE>
28605 <H1>FEATURE: <!--#echo var="FEAT_include-header-in-reply"--></H1>
28607 This feature controls an aspect of Alpine's Reply command. If set, and the
28608 original message is being included in the reply, then headers from that
28609 message will also be part of the reply.
28611 <End of help on this topic>
28614 ====== h_config_sig_at_bottom =====
28617 <TITLE>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></TITLE>
28620 <H1>FEATURE: <!--#echo var="FEAT_signature-at-bottom"--></H1>
28622 This feature controls an aspect of Alpine's Reply command. If this feature
28623 is set, and the original message is being included in the reply, then the
28624 contents of your signature file (if any) will be inserted after the included
28627 This feature does not affect the results of a Forward command.
28629 <End of help on this topic>
28632 ====== h_config_sigdashes =====
28635 <TITLE>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></TITLE>
28638 <H1>FEATURE: <!--#echo var="FEAT_enable-sigdashes"--></H1>
28640 This feature enables support for the common USENET news convention
28641 of preceding a message signature with the special line consisting of
28642 the three characters "-- " (i.e., dash, dash, and space).
28646 "<A HREF="h_config_signature_file"><!--#echo var="VAR_signature-file"--></A>" exists,
28647 Alpine will insert the special line before including the file's text (unless
28648 the special line already exists somewhere in the file's text).
28651 In addition, when you Reply or Followup to a message containing one of
28652 these special lines and choose to include its text, Alpine will observe
28653 the convention of not including text beyond the special line in your
28655 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28656 mode is enabled and turned on, then Alpine <EM>will</EM>
28657 include the text beyond the special line regardless of the setting of
28661 See also "<a href="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></a>"
28662 for a related feature.
28666 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28668 <End of help on this topic>
28671 ====== h_config_new_thread_blank_subject =====
28674 <TITLE>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></TITLE>
28677 <H1>FEATURE: <!--#echo var="FEAT_new-thread-on-blank-subject"--></H1>
28679 When this feature is enabled (the default) Alpine will create a new thread
28680 every time that the subject line becomes empty at any time during composition.
28683 This behavior is particularly useful in case you are replying to a message.
28684 Replying to a message causes the message to be in the same thread than the
28685 original message that is being replied to. However, many authors want to create
28686 a new message (in a different thread) while replying to a message, and they do
28687 this by changing the full subject, by first deleting the original subject and
28688 typing the new subject of the current message.
28691 Enabling this feature causes that any time that the subject is deleted, the
28692 message being composed will be considered the first message of a new thread.
28696 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28698 <End of help on this topic>
28701 ====== h_config_strip_sigdashes =====
28704 <TITLE>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></TITLE>
28707 <H1>FEATURE: <!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></H1>
28709 This feature doesn't do anything if the feature
28710 "<A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>" is turned on.
28711 However, if the "<!--#echo var="FEAT_enable-sigdashes"-->" feature is not turned on,
28712 then turning on this feature enables support for the convention
28713 of not including text beyond the sigdashes line when Replying or Following
28714 up to a message and including the text of that message.
28715 If <A HREF="h_config_enable_full_hdr">"Full Header"</A>
28716 mode is enabled and turned on, then Alpine <EM>will</EM>
28717 include the text beyond the special line regardless of the setting of
28720 In other words, this is a way to turn on the signature stripping behavior
28721 without also turning on the dashes-adding behavior.
28724 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28726 <End of help on this topic>
28729 ====== h_config_forward_as_attachment =====
28732 <TITLE>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></TITLE>
28735 <H1>FEATURE: <!--#echo var="FEAT_forward-as-attachment"--></H1>
28737 This feature affects the way forwarded message text is handled. When set, rather than
28738 include the text of the forwarded message below any additional text you provide in the
28739 composer, the forwarded message is attached in its entirety to the message you send.
28741 This is useful in that it keeps the text you provide in the composer distinct from the
28742 text of the forwarded message. Similarly, it allows the recipient to
28743 conveniently operate on the forwarded message. For example, they might reply directly to
28744 the sender of the forwarded message, or process it as part of a spam report.
28746 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28748 <End of help on this topic>
28751 ====== h_config_preserve_field =====
28754 <TITLE>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></TITLE>
28757 <H1>FEATURE: <!--#echo var="FEAT_preserve-original-fields"--></H1>
28759 This feature affects Alpine's behavior when one replies to a message.
28760 When you receive a message, some or all of the recipients of the message
28761 have been added to the To: and Cc: fields. If you reply to such message,
28762 and this feature is disabled, then the original sender of the message is
28763 added to the To: field, and all other recipients are added to the Cc:
28764 field, while your address is added to the From: field.
28767 However, if this feature is enabled, then Alpine will preserve the
28768 original fields as sent in the original message, so the Cc: and To:
28769 fields will be preserved. The sender's address will be added to the To:
28770 field, while your address is added to the From: field.
28773 The behavior of this feature is that replies to all messages will behave
28774 in the way described above. If you only intend this to happen on a per
28775 message basis, then keep this feature disabled, and when replying to a
28776 message you will see a new option in the menu for the "Reply to all
28777 recipients?" question. In this case, pressing "p" will
28778 make Alpine toggle its question so you can preserve the To: and Cc:
28779 fields for that message only.
28782 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
28784 <End of help on this topic>
28787 ====== h_config_sub_lists =====
28790 <TITLE>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></TITLE>
28793 <H1>FEATURE: <!--#echo var="FEAT_enable-partial-match-lists"--></H1>
28795 This feature affects the subcommands available when Saving,
28796 or when Opening a new folder. If set, the subcommand ^X ListMatches will be
28797 available. This command allows you to type in a substring of the folder
28798 you are looking for and when you type ^X it will display all folders
28799 that contain that substring in their names.
28800 This feature is set by default.
28803 <End of help on this topic>
28806 ====== h_config_scramble_message_id =====
28809 <TITLE>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></TITLE>
28812 <H1>FEATURE: <!--#echo var="FEAT_scramble-message-id"--></H1>
28814 Normally the Message-ID header that Alpine generates when sending a message
28815 contains the name of the computer from which the message is being sent.
28816 Some believe that this hostname could be used by spammers or could
28817 be used by others for nefarious purposes.
28818 If this feature is set, that name will be transformed with a simple
28819 Rot13 transformation.
28820 The result will still have the correct syntax for a Message-ID but the
28821 part of the MessageID that is often a domain name will not be an actual
28822 domain name because the letters will be scrambled.
28824 In addition, other information such as the name program, version, and
28825 a code for operating system used to build Alpine, will be encoded using
28826 the Rot13 transformation, except for the version number which will be
28827 encoded using a Rot5 transformation.
28829 It is possible (but unlikely?) that some spam detection
28830 software will use that as a reason to reject the mail as spam.
28831 It has also been reported that some spam detection software uses the
28832 fact that there are no dots after the "@" as a reason to reject
28834 If your PC-Alpine Message-ID is using a name without a dot that is because
28835 that is what Windows thinks is your "Full computer name".
28836 The method used to set this varies from one type of Windows to another but
28837 check under Settings -> Control Panel -> System and
28838 look for Network Identification or Computer Name or something similar.
28839 How to set it is beyond the scope of Alpine.
28842 <End of help on this topic>
28845 ====== h_downgrade_multipart_to_text =====
28848 <TITLE>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></TITLE>
28851 <H1>FEATURE: <!--#echo var="FEAT_downgrade-multipart-to-text"--></H1>
28854 This feature affects Alpine's behavior when sending mail. Internet
28855 standards require Alpine to translate all non-ASCII characters in
28856 messages that it sends using MIME encoding. This encoding can be
28857 ostensibly broken for recipients if any agent between Alpine and the
28858 recipient, such as an email list expander, appends text to the
28859 message, such as list information or advertising. When sending such
28860 messages Alpine attempts to protect such encoding by placing extra
28861 MIME boundaries around the message text.
28863 These extra boundaries are invisible to recipients that
28864 use MIME-aware email programs (the vast majority). However, if
28865 you correspond with users of email programs that are not MIME-aware,
28866 or do not handle the extra boundaries gracefully, you can
28867 use this feature to prevent Alpine from including the extra
28868 MIME information. Of course, it will increase the likelihood
28869 that non-ASCII text you send may appear corrupt to the recipient.
28871 <End of help on this topic>
28874 ====== h_config_show_sort =====
28877 <TITLE>FEATURE: <!--#echo var="FEAT_show-sort"--></TITLE>
28880 <H1>FEATURE: <!--#echo var="FEAT_show-sort"--></H1>
28882 If this feature is set and there is sufficient space on the screen,
28883 a short indication of the current sort order will be
28884 added in the titlebar (the top line on the screen), before the name
28886 For example, with the default Arrival sort in effect,
28887 the display would have the characters
28889 <P><CENTER>[A]</CENTER><P>
28891 added between the title of the screen and the folder name.
28892 The letters are the same as the letters you may type to manually
28893 sort a folder with the SortIndex command ($).
28894 The letters in the table below are the ones that may show
28895 up in the titlebar line.
28898 <TR> <TD> A </TD> <TD> <EM>A</EM>rrival </TD> </TR>
28899 <TR> <TD> S </TD> <TD> <EM>S</EM>ubject </TD> </TR>
28900 <TR> <TD> F </TD> <TD> <EM>F</EM>rom </TD> </TR>
28901 <TR> <TD> T </TD> <TD> <EM>T</EM>o </TD> </TR>
28902 <TR> <TD> C </TD> <TD> <EM>C</EM>c </TD> </TR>
28903 <TR> <TD> D </TD> <TD> <EM>D</EM>ate </TD> </TR>
28904 <TR> <TD> Z </TD> <TD> si<EM>Z</EM>e </TD> </TR>
28905 <TR> <TD> O </TD> <TD> <EM>O</EM>rderedsubject </TD> </TR>
28906 <TR> <TD> E </TD> <TD> scor<EM>E</EM> </TD> </TR>
28907 <TR> <TD> H </TD> <TD> t<EM>H</EM>read </TD> </TR>
28910 If the sort order is Reversed, the letter above will be preceded by the letter
28911 "R", for example
28913 <P><CENTER>[RS]</CENTER><P>
28915 means that a Reverse Subject sort is in effect.
28916 For the case where the sort is in Reverse Arrival order, the "A" is
28917 left out, and just an "R" is shown.
28919 <P><CENTER>[R]</CENTER>
28922 <End of help on this topic>
28925 ====== h_config_disable_reset_disp =====
28928 <TITLE>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></TITLE>
28931 <H1>FEATURE: <!--#echo var="FEAT_disable-terminal-reset-for-display-filters"--></H1>
28935 This feature affects Alpine's behavior when using
28936 <A HREF="h_config_display_filters"><!--#echo var="VAR_display-filters"--></A>.
28937 Normally, before the display filter is run, the terminal mode is reset
28938 to what it was before you started Alpine.
28939 This may be necessary if the filter requires the use of the terminal.
28940 For example, it may need to interact with you.
28941 If you set this feature, then the terminal mode will not be reset.
28942 One thing that turning on this feature should fix is the coloring of
28943 <A HREF="h_config_quote_color">quoted text</A> in the message view, which
28944 breaks because the terminal reset resets the color state of the terminal.
28947 <End of help on this topic>
28950 ====== h_config_disable_sender =====
28953 <TITLE>FEATURE: <!--#echo var="FEAT_disable-sender"--></TITLE>
28956 <H1>FEATURE: <!--#echo var="FEAT_disable-sender"--></H1>
28958 This feature affects Alpine's generation of the "Sender:" or
28959 <A HREF="h_config_use_sender_not_x">"X-X-Sender"</A>
28961 By default, Alpine will generate such a header in situations where the
28962 username or domain are not the same as
28963 the "From:" header on the message.
28964 With this feature set,
28965 no "Sender:" or "X-X-Sender" header will be generated.
28966 This may be desirable on a system that is virtually hosting many domains,
28967 and the sysadmin has other methods available for tracking a message to
28970 See also <A HREF="h_config_allow_chg_from">"<!--#echo var="FEAT_allow-changing-from"-->"</A>.
28973 <End of help on this topic>
28976 ====== h_config_use_sender_not_x =====
28979 <TITLE>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></TITLE>
28982 <H1>FEATURE: <!--#echo var="FEAT_use-sender-not-x-sender"--></H1>
28984 Normally Alpine adds a header line
28985 labeled "X-X-Sender", if the sender is
28986 different from the From: line.
28987 The standard specifies that this header
28988 line should be labeled "Sender", not "X-X-Sender".
28989 Setting this feature causes
28990 "Sender" to be used instead of "X-X-Sender".
28992 See also <A HREF="h_config_disable_sender">"<!--#echo var="FEAT_disable-sender"-->"</A>.
28995 <End of help on this topic>
28998 ====== h_config_use_fk =====
29001 <TITLE>FEATURE: <!--#echo var="FEAT_use-function-keys"--></TITLE>
29004 <H1>FEATURE: <!--#echo var="FEAT_use-function-keys"--></H1>
29006 This feature specifies that Alpine will respond to function keys instead of
29007 the normal single-letter commands. In this mode, the key menus at the
29008 bottom of each screen will show function key designations instead of the
29009 normal mnemonic key.
29012 <End of help on this topic>
29015 ====== h_config_cancel_confirm =====
29018 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></TITLE>
29021 <H1>FEATURE: <!--#echo var="FEAT_compose-cancel-confirm-uses-yes"--></H1>
29023 This feature affects what happens when you type ^C to cancel a composition.
29024 By default, if you attempt to cancel a composition by typing ^C, you will be
29025 asked to confirm the cancellation by typing a "C"
29026 for <EM>C</EM>onfirm.
29027 It logically ought to be a "Y" for <EM>Y</EM>es, but that is
29028 risky because the "^C Y" needed to cancel a message
29029 is close (on the keyboard) to the "^X Y" needed to send a message.
29031 If this feature is set the confirmation asked for
29032 will be a "<EM>Y</EM>es"
29033 instead of a "<EM>C</EM>onfirm" response.
29036 <End of help on this topic>
29039 ====== h_config_compose_maps_del =====
29042 <TITLE>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></TITLE>
29045 <H1>FEATURE: <!--#echo var="FEAT_compose-maps-delete-key-to-ctrl-d"--></H1>
29047 This feature affects the behavior of the DELETE key.
29048 If set, Delete will be equivalent to ^D, and delete
29049 the current character. Normally Alpine defines the Delete key
29050 to be equivalent to ^H, which deletes the <EM>previous</EM>
29054 <End of help on this topic>
29057 ====== h_config_compose_bg_post =====
29060 <TITLE>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></TITLE>
29063 <H1>FEATURE: <!--#echo var="FEAT_enable-background-sending"--></H1>
29065 This feature affects the behavior of Alpine's mail sending. If set, this
29066 feature enables a subcommand in the composer's "Send?" confirmation
29067 prompt. The subcommand allows you to tell Alpine to handle the actual
29068 posting in the background. While this feature usually allows posting
29069 to appear to happen very fast, it has no affect on the actual delivery
29070 time it takes a message to arrive at its destination.
29075 <LI>This feature will have no effect if the feature
29076 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A>
29078 <LI>This feature isn't supported on all systems. All DOS and Windows,
29079 as well as several Unix ports, do not recognize this feature.
29080 <LI>Error handling is significantly different when this feature is
29081 enabled. Any message posting failure results in the message
29082 being appended to your "Interrupted" mail folder. When you
29083 type the <A HREF="h_common_compose">C</A>ompose command,
29084 Alpine will notice this folder and
29085 offer to extract any messages contained. Upon continuing a
29086 failed message, Alpine will display the nature of the failure
29087 in the status message line.
29088 <LI> <EM>WARNING</EM>: Under extreme conditions, it is possible
29089 for message data to
29090 get lost. <EM>Do</EM> <EM>not</EM> enable this feature
29091 if you typically run close to any sort of disk-space limits or quotas.
29094 <End of help on this topic>
29097 ====== h_config_compose_dsn =====
29100 <TITLE>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></TITLE>
29103 <H1>FEATURE: <!--#echo var="FEAT_enable-delivery-status-notification"--></H1>
29105 This feature affects the behavior of Alpine's mail sending. If set, this
29106 feature enables a subcommand in the composer's "Send?" confirmation
29107 prompt. The subcommand allows you to tell Alpine to request the type of
29108 Delivery Status Notification (DSN) that you would like. Most users will
29109 be happy with the default, and need not enable this feature.
29112 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29113 then this feature has no effect and the type of DSN is not selectable.
29116 Turning on this feature and then turning on the DSNOpts from the send
29117 prompt reveals four on-off toggles at the bottom of the screen.
29118 The "X" command toggles between NoErrRets and ErrRets. NoErrRets requests
29119 that no notification be returned to you, even if there is a delivery
29120 failure. The "D" key toggles between Delay and NoDelay. This tells the
29121 server that you are willing (or not) to receive delay notifications, which
29122 happen when there is an unusual delay at some mail server (in that mail
29123 server's opinion). The "S" key toggles between Success and NoSuccess.
29124 Success requests that you be sent a DSN message when the message is
29125 successfully delivered to the recipients mailbox. Setting NoErrRets will
29126 automatically turn off Delay and Success notification, and will flip the
29127 toggles to show that. Similarly, turning on Delay and/or Success will
29128 automatically toggle the "X" key to ErrRets. The fourth command, the
29129 "H" key, toggles between RetHdrs and RetFull. RetFull requests that
29130 the full message be returned in any failed DSN. RetHdrs requests that
29131 only the headers be returned in any failed DSN. Notice that this command
29132 applies only to failed delivery status reports. For delay or success
29133 reports, the full message is never returned, only the headers are returned.
29136 If you don't enable the DSN feature or if you don't turn it on for a
29137 particular message, the default is that you will be notified about failures,
29138 you might be notified about delays, and you won't be notified about
29139 successes. You will usually receive the full message back when there is
29143 If you turn on the DSNOpts the default is to return as much information as
29144 possible to you. That is, by default, the Success and Delay options are
29145 turned on and the full message will be returned on failure.
29148 The sending prompt will display the current DSN request (if any) in a
29149 shorthand form. It will be:
29151 <P><CENTER>[Never]</CENTER>
29154 if you have requested NoErrRets. Otherwise, it will look something like:
29156 <P><CENTER>[FDS-Hdrs]</CENTER>
29159 The "F" will always be there, indicating that you will be notified
29160 of failures. (Alpine doesn't provide a way to request no failure notification
29161 and at the same time request either success or delay notification. The only
29162 way to request no failure notifications is to request no notifications at
29163 all with NoErrRets.) The "D" and/or "S" will be present if you have
29164 requested Delay and/or Success notification. If one of those is missing,
29165 that means you are requesting no notification of the corresponding type.
29166 After the dash it will say either Hdrs or Full. Hdrs means to return only
29167 the headers and Full means to return the full message (applies to
29168 failure notifications only).
29171 NOTE: This feature relies on your system's mail transport agent or
29173 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
29174 having the negotiation mechanism introduced in
29175 "Extended SMTP" (ESMTP) and the specific extension called
29176 "Delivery Status Notification" (DSN). If the mail tranport agent you
29177 are using doesn't support DSN, a short warning will be shown to you on
29178 the message line at the bottom of the screen after you send your message,
29179 but your message will have been sent anyway.
29182 Note that DSNs don't provide a mechanism to request read receipts. That
29183 is, if you request notification on success you are notified when the
29184 message is delivered to the mailbox, not when the message is read.
29187 ESMTP allows for graceful migration to upgraded mail transfer agents, but
29188 it is possible that this feature might cause problems for some servers.
29191 <End of help on this topic>
29194 ====== h_config_auto_zoom =====
29197 <TITLE>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></TITLE>
29200 <H1>FEATURE: <!--#echo var="FEAT_auto-zoom-after-select"--></H1>
29202 This feature affects the behavior of the Select command.
29203 If set, the select command will automatically perform a zoom
29204 after the select is complete.
29205 This feature is set by default.
29207 Some related help topics are
29209 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29210 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29211 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29212 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
29213 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
29214 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29218 <End of help on this topic>
29221 ====== h_config_auto_unzoom =====
29224 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></TITLE>
29227 <H1>FEATURE: <!--#echo var="FEAT_auto-unzoom-after-apply"--></H1>
29229 This feature affects the behavior of the Apply command. If set, and if
29230 you are currently looking at a Zoomed Index view of selected messages,
29231 the Apply command will do the operation you specify, but then will
29232 implicitly do an "UnZoom", so that you will automatically be back in
29233 the normal Index view after the Apply.
29234 This feature is set by default.
29237 Some related help topics are
29239 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29240 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29241 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29242 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
29243 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
29244 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29247 <End of help on this topic>
29250 ====== h_config_auto_unselect =====
29253 <TITLE>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></TITLE>
29256 <H1>FEATURE: <!--#echo var="FEAT_auto-unselect-after-apply"--></H1>
29258 This feature affects the behavior of the Apply command. If set,
29259 the Apply command will do the operation you specify, but then will
29260 implicitly do an "UnSelect All", so that you will automatically be back in
29261 the normal Index view after the Apply.
29264 Some related help topics are
29266 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
29267 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
29268 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
29269 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>, and
29270 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
29271 <LI> <A HREF="h_config_select_wo_confirm"><!--#echo var="FEAT_select-without-confirm"--></A>.
29274 <End of help on this topic>
29277 ====== h_config_fast_recent =====
29280 <TITLE>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></TITLE>
29283 <H1>FEATURE: <!--#echo var="FEAT_enable-fast-recent-test"--></H1>
29285 This feature controls the behavior of the TAB key when traversing folders
29287 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
29288 collection or in optional <!--#echo var="VAR_news-collections"-->.
29292 (<A HREF="h_common_nextnew">NextNew</A>)
29293 key is pressed, the default behavior is to
29294 explicitly examine the status of the folder for the number of recent
29295 messages (messages delivered since the last time it was viewed).
29296 Depending on the size and number of messages in the folder, this test
29297 can be time consuming.
29300 Enabling this feature will cause Alpine to only test for the existence of
29301 any recent messages rather than to obtain the count. This is much faster
29302 in many cases. The downside is that you're not given the number of recent
29303 messages when prompted to view the next folder.
29305 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
29306 is turned on, then the present feature will have no effect.
29310 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29312 <End of help on this topic>
29315 ====== h_config_arrow_nav =====
29318 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></TITLE>
29321 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation"--></H1>
29323 This feature controls the behavior of the left and right arrow keys.
29324 If set, the left and right arrow keys will operate like the usual
29325 navigation keys < and >.
29326 This feature is set by default.
29329 If you set this feature, and do not like the changed behavior of the up/down
29331 keys when navigating through the FOLDER LIST screen --
29332 <B>first</B> from column to column, if more than one folder is
29334 and <B>then</B> from row to row -- you may either also wish to set the feature
29335 "<A HREF="h_config_relaxed_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></A>",
29336 "<A HREF="h_config_single_list"><!--#echo var="FEAT_single-column-folder-list"--></A>", or
29337 use the ^P/^N (instead of up/down arrow) keys to move up/down the list of
29338 folders in each column.
29341 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29343 <End of help on this topic>
29346 ====== h_config_relaxed_arrow_nav =====
29349 <TITLE>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></TITLE>
29352 <H1>FEATURE: <!--#echo var="FEAT_enable-arrow-navigation-relaxed"--></H1>
29354 This feature controls the behavior of the left, right, up and down
29355 arrow keys in the FOLDER LIST screen when the "<A
29356 HREF="h_config_arrow_nav"><!--#echo var="FEAT_enable-arrow-navigation"--></A>" feature is
29358 This feature is set by default.
29362 When this feature is set, the left and right
29363 arrow keys in the FOLDER LIST screen
29364 move the highlight bar to the left or right, and the up and
29365 down arrows move it up or down.
29368 When the "<!--#echo var="FEAT_enable-arrow-navigation"-->" feature is set and this
29369 feature is not set;
29370 the left and right arrow keys in the Folder List screen strictly
29371 track the commands bound to the '<' and '>' keys, and the up
29372 and down arrow keys move the highlight bar to the previous and next
29373 folder or directory name.
29377 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29379 <End of help on this topic>
29382 ====== h_config_alt_compose_menu =====
29385 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></TITLE>
29388 <H1>FEATURE: <!--#echo var="FEAT_alternate-compose-menu"--></H1>
29390 This feature controls the menu that is displayed when Compose is selected.
29391 If set, a list of options will be presented, with each option representing
29392 the type of composition that could be used. This feature is most useful for
29393 users who want to avoid being prompted with each option separately, or who
29394 want to avoid the checking of remote postponed or form letter folders.
29395 The possible types of composition are:
29398 New, for starting a new composition. Note that if New is selected and roles
29399 are set, roles are checked for matches and applied according to the setting
29400 of the matching role.
29403 Interrupted, for continuing an interrupted composition. This option is only
29404 offered if an interrupted message folder is detected.
29407 Postponed, for continuing postponed compositions. This option is offered
29408 if a <!--#echo var="VAR_postponed-folder"--> is set in the config REGARDLESS OF whether or not
29409 the postponed folder actually exists. This option is especially handy
29410 for avoiding having to check for the existence of a remote postponed folder.
29413 Form, for using form letters. This option is offered if the <!--#echo var="VAR_form-letter-folder"-->
29414 is set in the config, and is not checked for existence for reasons similar
29415 to those explained by the postponed option.
29418 setRole, for selecting a role to apply to a composition.
29421 <End of help on this topic>
29424 ====== h_config_alt_role_menu =====
29427 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></TITLE>
29430 <H1>FEATURE: <!--#echo var="FEAT_alternate-role-menu"--></H1>
29432 Normally the <A HREF="h_common_role">Role Command</A> allows you to choose
29433 a role and compose a new message using that role.
29434 When this feature is set, the role command will first ask whether you want to
29435 Compose a new message, Forward the current message, Reply to the
29436 current message, or Bounce the current message.
29437 If you are not in the MESSAGE INDEX and are not viewing a message,
29438 then there is no current message and the question will be skipped.
29439 After you have chosen to Compose, Forward, Reply, or Bounce you will
29440 then choose the role to be used.
29442 When Bouncing the "Set From" address is used for the
29443 Resent-From header, the "Set Fcc" value is used for the Fcc
29444 provided that the option
29445 <A HREF="h_config_fcc_on_bounce">"<!--#echo var="FEAT_fcc-on-bounce"-->"</A> is turned on,
29446 and the "Use SMTP Server" value is used for the SMTP server, if
29448 Other actions of the role are ignored when Bouncing.
29451 <End of help on this topic>
29454 ====== h_config_always_spell_check =====
29457 <TITLE>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></TITLE>
29460 <H1>FEATURE: <!--#echo var="FEAT_spell-check-before-sending"--></H1>
29462 When this feature is set, every composed message will be spell-checked before
29465 <End of help on this topic>
29468 ====== h_config_quell_asterisks =====
29471 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></TITLE>
29474 <H1>FEATURE: <!--#echo var="FEAT_suppress-asterisks-in-password-prompt"--></H1>
29476 When you are running Alpine you will sometimes be asked for a password
29477 in a prompt on the third line from the bottom of the screen.
29478 Normally each password character you type will cause an asterisk to echo
29479 on the screen. That gives you some feedback to know that your typing is
29481 There is a very slight security risk in doing it this way because someone
29482 watching over your shoulder might be able to see how many characters there
29483 are in your password.
29484 If you'd like to suppress the echoing of the asterisks set this feature.
29486 <End of help on this topic>
29489 ====== h_config_quell_flowed_text =====
29492 <TITLE>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></TITLE>
29495 <H1>FEATURE: <!--#echo var="FEAT_quell-flowed-text"--></H1>
29497 Alpine generates flowed text where possible.
29498 The method for generating flowed text is defined by
29499 <A HREF="http://www.ietf.org/rfc/rfc3676.txt">RFC 3676</A>,
29500 the benefit of doing so is
29501 to send message text that can properly be viewed both on normal width displays
29502 and on displays with smaller or larger than normal screen widths.
29503 With flowed text, a space at the end of a line tells the receiving mail
29504 client that the following line belongs to the same paragraph.
29505 Quoted text will also be affected, with only the innermost
29506 level of ">" quoting being followed by a space.
29507 However, if you have changed the
29508 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29509 so that it is not equal to the default value of "> ", then
29510 quoted text will not be flowed.
29511 For this reason, we recommend that you leave your
29512 "<!--#echo var="VAR_reply-indent-string"-->" set to the default.
29514 This feature turns off the generation of flowed text, as it might be
29515 desired to more tightly control how a message is displayed on the receiving end.
29517 If this feature is <EM>not</EM> set, you can control on a message by message
29518 basis whether or not flowed text is generated.
29519 You do this by typing ^V at the Send confirmation prompt that you get
29520 after typing ^X to send a message.
29521 ^V is a toggle that turns flowing off and back on if typed again.
29522 If for some reason flowing cannot be done on a particular message, then the
29523 ^V command will not be available.
29524 This would be the case, for example, if this feature was set, or if your
29525 "<!--#echo var="VAR_reply-indent-string"-->" was set to a non-default value.
29527 <A HREF="h_config_send_wo_confirm">"<!--#echo var="FEAT_send-without-confirm"-->"</A> is set,
29528 then the opportunity to control on a message by message basis
29529 whether or not flowed text is generated is lost.
29531 When this feature is not set and you have typed ^V to turn off flowing,
29532 the Send confirmation prompt will change to look like
29534 <CENTER><SAMP>Send message (not flowed)?</SAMP></CENTER>
29536 <A HREF="h_config_strip_ws_before_send">"<!--#echo var="FEAT_strip-whitespace-before-send"-->"</A> will
29537 also turn off the sending of flowed text messages, but it differs in that
29538 it also trims all trailing white space from a message before sending it.
29540 If alternate editors are used extensively, be aware that a message will still
29541 be sent flowed if this feature is unset. In most cases this will be fine,
29542 but if the editor has a "flowed text" mode, it would be best to
29545 <End of help on this topic>
29548 ====== h_config_strip_ws_before_send =====
29551 <TITLE>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></TITLE>
29554 <H1>FEATURE: <!--#echo var="FEAT_strip-whitespace-before-send"--></H1>
29556 By default, trailing whitespace is not stripped from
29557 a message before sending. Trailing whitespace should have no effect on an
29558 email message, and in flowed text can aid in delimiting paragraphs.
29559 However, the old behavior of stripping trailing whitespace was in place
29560 to better deal with older clients that couldn't handle certain types of
29561 text encodings. This feature restores the old behavior
29563 Trailing whitespace is of aid to flowed-text-formatted messages, which are
29564 generated by default but can be turned off via the
29565 <A HREF="h_config_quell_flowed_text">"<!--#echo var="FEAT_quell-flowed-text"-->"</A> feature.
29566 <!--#echo var="FEAT_strip-whitespace-before-send"--> also has the effect of turning off sending
29569 <End of help on this topic>
29572 ====== h_config_alt_reply_menu =====
29575 <TITLE>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></TITLE>
29578 <H1>FEATURE: <!--#echo var="FEAT_alternate-reply-menu"--></H1>
29580 Note that if this option is enabled, then the option
29581 <A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A>
29582 is ignored. See below to understand why.
29584 When you reply to a message, a series of questions are asked that
29585 determines how your reply will be handled by Alpine. This feature only
29586 affects the result of the first question you are asked, and its purpose is
29587 to set values that could override defaults set in Alpine's main
29588 configuration screen. As a result, this menu allows you to configure even
29589 more features than you would be able to do without this option. For
29590 example, this menu always allows you to override or select a <A
29591 HREF="h_rules_roles">Role</A> if you have defined one, or allows you to
29592 override your indent string, regardless of if you have enabled
29593 <A HREF="h_config_prefix_editing"><!--#echo var="FEAT_enable-reply-indent-string-editing"--></A>.
29594 The full list of options can be found below.
29596 Here is an example of how this option works. After you press Reply,
29597 if you see "A Inc Attach" in the menu, it means that
29598 if you press "A", then Alpine will include the attachments
29599 of the original message, and the default is not to include them.
29600 Conversely, if you see "A No Attach"
29601 then by pressing "A" Alpine will not include
29602 attachments in your reply, and the default is that Alpine will
29603 include them in your reply. The value that you see when you
29604 start your reply is controlled by the option
29605 <A HREF="h_config_attach_in_reply">
29606 <!--#echo var="FEAT_include-attachments-in-reply"-->
29607 </A>. If the feature is enabled, then Alpine will display
29608 "A No Attach" to override the default behavior. You can
29609 toggle between the two values of this option by pressing "A".
29610 Remember that the value that you see in the menu is the action that will
29611 be done when you press the associated command.
29613 Below are your options:
29615 <LI><B>A</B>: This determines if Alpine will include or not the
29616 attachments sent to you in the message that you are replying to. The default
29617 is to use the value of the configuration option
29618 <A HREF="h_config_attach_in_reply"><!--#echo var="FEAT_include-attachments-in-reply"--></A> and can be overriden by using this command.
29620 <LI><B>H</B>: This command determines if the headers of a message are
29621 included in the body of the message that is being replied to. By default
29622 Alpine will use the value of the configuration option
29623 <A HREF="h_config_include_header"><!--#echo var="FEAT_include-header-in-reply"--></A>.
29624 Observe that by toggling this option to include headers, text will be toggled
29625 to be included by default.
29627 <LI><B>R</B>: Can be used to set a role different from the default.
29629 <LI><B>S</B>: Determines if Alpine will strip the signature from a
29630 message. The default is to strip the signature when the message is not
29631 viewed in headers mode, and you either have enabled
29632 <A HREF="h_config_sigdashes"><!--#echo var="FEAT_enable-sigdashes"--></A>
29634 <A HREF="h_config_strip_sigdashes"><!--#echo var="FEAT_strip-from-sigdashes-on-reply"--></A>.
29636 <LI><B>Ctrl-R</B>: Can be used to edit the
29637 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>.
29640 In order to include the text of the original message in the reply
29641 you either need to press 'y' to include the original text, or 'n' to
29642 exclude it from the reply. Pressing return will execute the default
29643 action, which is to include text only if the option
29644 <A HREF="h_config_auto_include_reply"><!--#echo var="FEAT_include-text-in-reply"--></A>
29645 is enabled. However, notice that the default is to include text if you edit the
29646 reply indent string or if you explicitly set through this menu that you
29647 want headers included in the reply message.
29650 <End of help on this topic>
29653 ====== h_config_del_from_dot =====
29656 <TITLE>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></TITLE>
29659 <H1>FEATURE: <!--#echo var="FEAT_compose-cut-from-cursor"--></H1>
29661 This feature controls the behavior of the Ctrl-K command in the composer.
29662 If set, ^K will cut from the current cursor position to the end of the line,
29663 rather than cutting the entire line.
29666 <End of help on this topic>
29669 ====== h_config_print_index =====
29672 <TITLE>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></TITLE>
29675 <H1>FEATURE: <!--#echo var="FEAT_print-index-enabled"--></H1>
29677 This feature controls the behavior of the Print command when in the
29678 MESSAGE INDEX screen. If set, the print command will give you a prompt
29679 asking if you wish to print the message index, or the currently highlighted
29680 message. If not set, the message will be printed.
29683 <End of help on this topic>
29686 ====== h_config_allow_talk =====
29689 <TITLE>FEATURE: <!--#echo var="FEAT_allow-talk"--></TITLE>
29692 <H1>FEATURE: <!--#echo var="FEAT_allow-talk"--></H1>
29696 By default, permission for others to "talk" to your terminal is turned
29697 off when you are running Alpine. When this feature is set, permission is
29698 instead turned on. If enabled, you may see unexpected messages in the
29699 middle of your Alpine screen from someone attempting to contact you via the
29700 "talk" program.
29703 NOTE: The "talk" program has nothing to do with Alpine or email. The
29704 talk daemon on your system will attempt to print a message on your screen
29705 when someone else is trying to contact you. If you wish to see these
29706 messages while you are running Alpine, you should enable this feature.
29709 If you do enable this feature and see a "talk" message, you must
29710 suspend or quit Alpine before you can respond.
29713 <End of help on this topic>
29716 ====== h_config_send_filter_dflt =====
29719 <TITLE>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></TITLE>
29722 <H1>FEATURE: <!--#echo var="FEAT_compose-send-offers-first-filter"--></H1>
29723 If you have <A HREF="h_config_sending_filter">"<!--#echo var="VAR_sending-filters"-->"</A>
29724 configured, setting this feature will cause
29725 the first filter in the <!--#echo var="VAR_sending-filters"--> list to be offered as the default
29726 instead of unfiltered, the usual default.
29729 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29731 <End of help on this topic>
29734 ====== h_config_custom_print =====
29737 <TITLE>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></TITLE>
29740 <H1>FEATURE: <!--#echo var="FEAT_print-offers-custom-cmd-prompt"--></H1>
29742 When this feature is set, the print command will have an additional
29743 subcommand called "C CustomPrint". If selected, you will have
29744 the opportunity to enter any system print command --instead of being
29745 restricted to using those that have been previously configured in the
29746 printer setup menu.
29749 <End of help on this topic>
29752 ====== h_config_enable_dot_files =====
29755 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></TITLE>
29758 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-files"--></H1>
29760 When this feature is set, files beginning with dot (".") will be
29761 visible in the file browser. For example, you'll be able to select them
29762 when using the browser to add an attachment to a message.
29764 <End of help on this topic>
29767 ====== h_config_enable_dot_folders =====
29770 <TITLE>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></TITLE>
29773 <H1>FEATURE: <!--#echo var="FEAT_enable-dot-folders"--></H1>
29775 When this feature is set, folders beginning with dot (".") may be added
29778 <End of help on this topic>
29781 ====== h_config_ff_between_msgs =====
29784 <TITLE>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></TITLE>
29787 <H1>FEATURE: <!--#echo var="FEAT_print-formfeed-between-messages"--></H1>
29789 Setting this feature causes a formfeed to be printed between messages when
29790 printing multiple messages (with Apply Print command).
29792 <End of help on this topic>
29795 ====== h_config_blank_keymenu =====
29798 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></TITLE>
29801 <H1>FEATURE: <!--#echo var="FEAT_disable-keymenu"--></H1>
29803 If this feature is set the command key menu that normally appears on the
29804 bottom two lines of the screen will not usually be there. Asking for
29805 help with ^G or ? will cause the key menu to appear instead of causing
29806 the help message to come up. If you want to actually see the help text,
29807 another ^G or ? will show it to you. After the key menu has popped
29808 up with the help key it will remain there for an O for Other command but
29809 disappear if any other command is typed.
29811 <End of help on this topic>
29814 ====== h_config_enable_mouse =====
29817 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></TITLE>
29820 <H1>FEATURE: <!--#echo var="FEAT_enable-mouse-in-xterm"--></H1>
29822 This feature controls whether or not an X terminal mouse can be used with
29823 Alpine. If set, and the $DISPLAY variable indicates that an X terminal is
29824 being used, the left mouse button on the mouse can be used to select text
29826 Clicking on a command at the bottom of the screen will behave as if you had
29827 typed that command.
29828 Clicking on an index line will move the current message highlight to
29830 Double-clicking on an index line will view the message.
29831 Double-clicking on a link will view the link.
29833 This type of mouse support will also work in some terminal emulators which are
29834 not actually X terminals, but which have extra code to support the xterm
29836 For those emulators you not only need to turn this feature on but you also
29837 have to set the $DISPLAY environment variable even though it isn't needed
29839 That will cause Alpine to think that it is an xterm and to properly interpret the
29840 escape sequences sent by the mouse.
29842 Note: if this feature is set, the behavior of X terminal cut-and-paste is
29843 also modified. It is sometimes possible to hold the shift key down while clicking
29844 left or middle mouse buttons for the normal xterm cut/paste operations.
29845 There is also an Alpine command to toggle this mode on or off.
29846 The command is Ctrl-\ (Control-backslash).
29848 <End of help on this topic>
29851 ====== h_config_enable_xterm_newmail =====
29854 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></TITLE>
29857 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></H1>
29859 This feature controls whether or not Alpine will attempt to announce new
29860 mail arrival when it is running in an X terminal window and that window
29861 is iconified. If set, and the $DISPLAY variable indicates that an X
29862 terminal is being used, Alpine will send appropriate escape sequences to
29863 the X terminal to modify the label on Alpine's icon to indicate that new
29864 mail has arrived. Alpine will also modify the Alpine window's title to
29866 See also <a href="h_config_enable_newmail_short_text"><!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></a>.
29868 <End of help on this topic>
29870 ====== h_config_enable_newmail_short_text =====
29873 <TITLE>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></TITLE>
29876 <H1>FEATURE: <!--#echo var="FEAT_enable-newmail-short-text-in-icon"--></H1>
29878 This feature controls the text to be displayed in an icon in the event
29879 of a new message arrival. Normally, the message will
29880 be the one that is displayed on the screen. This feature shortens the
29881 message to a count of the number of new messages in brackets. This may be
29882 more useful for those who use the window's title bar in the task bar as a
29883 new mail indicator. This feature is only useful if the
29884 <A HREF="h_config_enable_xterm_newmail"><!--#echo var="FEAT_enable-newmail-in-xterm-icon"--></A>
29885 feature is also set. Like the <!--#echo var="FEAT_enable-newmail-in-xterm-icon"-->
29886 feature, this feature is only relevant when run in an xterm environment.
29888 <End of help on this topic>
29890 ====== h_config_copy_to_to_from =====
29893 <TITLE>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></TITLE>
29896 <H1>FEATURE: <!--#echo var="FEAT_copy-to-address-to-from-if-it-is-us"--></H1>
29898 This feature affects the From address used when Replying to a message.
29899 It is probably only useful if you have some
29900 <a href="h_config_alt_addresses"><!--#echo var="VAR_alt-addresses"--></a>
29902 When enabled, it checks to see if any of the addresses in the To or Cc
29903 fields of the message you are replying to is one of your addresses.
29904 If it is, and there is only one of them, then that address is used as
29905 the From address in the message you are composing.
29906 In other words, you will be using a From address that is the same
29907 as the To address that was used to get the mail to you in the first place.
29910 If a role is being used and it has a From address defined, that From address will
29911 be used rather than the one derived from this feature.
29915 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29917 <End of help on this topic>
29920 ====== h_config_prefix_editing =====
29923 <TITLE>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></TITLE>
29926 <H1>FEATURE: <!--#echo var="FEAT_enable-reply-indent-string-editing"--></H1>
29928 This feature affects the Reply command's "Include original message
29929 in Reply?" prompt. When enabled, it causes the
29930 "Edit Indent String" sub-command to appear which allows
29931 you to edit the string Alpine would otherwise use to denote included
29932 text from the message being replied to.<P>
29934 Thus, you can change Alpine's default message quote character (usually
29935 an angle bracket) on a per message basis. So you could change your quoted message to
29936 look, for example, like this:<p>
29938 <pre>On Tues, 26 Jan 1999, John Q. Smith wrote:
29940 John: I just wanted to say hello and to congratulate you
29941 John: on a job well done!</pre><p>
29943 The configuration option
29944 <A HREF="h_config_reply_indent_string">"<!--#echo var="VAR_reply-indent-string"-->"</A>
29945 may be used to change what appears as the default string to be edited.
29947 NOTE: Edited <!--#echo var="VAR_reply-indent-string"--> only apply to the message
29948 currently being replied to.
29950 If you change your <!--#echo var="VAR_reply-indent-string"-->
29951 so that it is not equal to the default value of "> ", then
29952 quoted text will not be flowed
29953 (<A HREF="h_config_quell_flowed_text">Flowed Text</A>)
29955 For this reason, we recommend that you leave your <!--#echo var="VAR_reply-indent-string"-->
29956 set to the default value.
29959 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
29961 <End of help on this topic>
29964 ====== h_config_enable_search_and_repl =====
29967 <TITLE>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></TITLE>
29970 <H1>FEATURE: <!--#echo var="FEAT_enable-search-and-replace"--></H1>
29972 This feature modifies the behavior of Alpine's composer. Setting this
29973 feature causes Alpine to offer the "^R Replace" subcommand, which
29974 allows you to search and replace text strings in a message you are composing,
29975 inside the "^W Where is" command.
29979 To search and replace text, first enter the text to be replaced at the
29980 "Search: " prompt. Then, rather than pressing Enter to just search for that
29981 text, press ^R, which turns the prompt into
29985 Search (to replace):
29989 and then press Enter. The cursor will highlight the first occurrence
29990 of the text string you entered, and the prompt will show:
29994 Replace "<your text string>" with :
29998 where <your text string> is what you entered at the previous prompt;
29999 here, enter the replacement text. To only replace the highlighted
30000 occurrence, simply press Enter now; to replace all occurrences in the
30001 message, press ^X (Repl All), then Enter. You will then be asked to confirm
30006 The command ^R toggles between "Replace" and "Don't Replace"; its subcommand
30007 ^X toggles between "Replace All" and "Replace One."
30011 If you previously searched for text in a message, it will be offered for
30012 re-use as part of the prompt, shown in [ ] brackets.
30015 <End of help on this topic>
30018 ====== h_config_enable_view_attach =====
30021 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></TITLE>
30024 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-attachments"--></H1>
30026 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30027 Setting this feature causes Alpine to present attachments in boldface.
30028 The first available attachment is displayed in inverse. This is the
30029 "selected" attachment. Pressing RETURN will cause Alpine to display
30030 the selected attachment. Use the arrow keys to change which of the
30031 attachments displayed in boldface is the current selection.
30035 Speaking of arrow keys, the Up and Down Arrows will select the next
30036 and previous attachments if one is available on the screen for selection.
30037 Otherwise, they will simply adjust the viewed text one line up or down.
30041 Similarly, when selectable items are present in a message, the Ctrl-F key
30042 can be used to select the next item in the message independent of which
30043 portion of the viewed message is currently displayed. The Ctrl-B key can
30044 be used to select the previous item in the same way.
30046 <End of help on this topic>
30049 ====== h_config_enable_y_print =====
30052 <TITLE>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></TITLE>
30055 <H1>FEATURE: <!--#echo var="FEAT_enable-print-via-y-command"--></H1>
30057 This feature modifies the behavior of Alpine's Print command.
30059 By default, Alpine's print command is available by pressing the "%" key.
30060 (This command is a substantial change from Pine versions before 4.00 --
30061 where the print command was "Y" -- based on numerous complaints about
30062 printing being invoked inadvertently, since Y also means "Yes.")
30066 This feature is supplied to mitigate any disruption or anxiety users
30067 might feel as a result of this change.
30071 Enabling this feature will cause Alpine to recognize both the old
30072 command, "Y" for Prynt, as well the new "%" method for invoking
30073 printing. Note, key menu labels are not changed as a result of
30074 enabling this feature.
30078 <End of help on this topic>
30081 ====== h_config_enable_lessthan_exit =====
30084 <TITLE>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></TITLE>
30087 <H1>FEATURE: <!--#echo var="FEAT_enable-exit-via-lessthan-command"--></H1>
30089 If this feature is set, then on screens where there is an Exit command
30090 but no < command, the < key will perform the same function as the Exit
30092 This feature is set by default.
30094 <End of help on this topic>
30097 ====== h_config_enable_view_url =====
30100 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></TITLE>
30103 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-urls"--></H1>
30104 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30105 When this feature is set (the default) Alpine will select possible URLs from the
30106 displayed text and display them in boldface for selection.
30108 The first available URL is displayed in inverse. This is the
30109 "selected" URL. Pressing RETURN will cause Alpine to display
30110 the selected URL via either built-in means as with mailto:, imap:,
30111 news:, and nntp:, or via an external application as defined
30112 by the <A HREF="h_config_browser">"url-viewer"</A>
30115 Use the arrow keys to change which of the URLs displayed in boldface
30116 is the current selection.
30118 Speaking of arrow keys, the Up and Down Arrows will select the next
30119 and previous URL if one is available on the screen for selection (unless
30120 you have set the feature
30121 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>).
30122 Otherwise, they will simply adjust the viewed text one line up or down.
30124 Similarly, when selectable items are present in a message, the Ctrl-F
30125 key can be used to select the next item in the message independent
30126 of which portion of the viewed message is currently displayed. The
30127 Ctrl-B key can be used to select the previous item in the same way.
30130 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30132 <End of help on this topic>
30135 ====== h_config_enable_view_web_host =====
30138 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></TITLE>
30141 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-web-hostnames"--></H1>
30143 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30144 When this feature is set (the default) Alpine will select possible web hostnames
30145 from the displayed text and display them in boldface for selection.
30146 This can be useful when you receive messages referencing World Wide Web
30147 sites without the use of complete URLs; for example, specifying only
30148 "www.patches.freeiz.com/alpine/" (which will <B>not</B> become a
30150 item by setting <A HREF="h_config_enable_view_url">"<!--#echo var="FEAT_enable-msg-view-urls"-->"</A>)
30151 rather than explicitly
30152 "http://www.patches.freeiz.com/alpine/".
30154 The first available hostname is displayed in inverse. This is the
30155 "selected" hostname. Pressing RETURN will cause Alpine to display
30156 the selected hostname via an external application as defined
30157 by the <A HREF="h_config_browser">"url-viewer"</A>
30160 Use the arrow keys (unless you have set the feature
30161 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
30162 to change which of the hostnames displayed in
30163 boldface is the current selection.
30165 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
30166 key can be used to select the next web hostname in the message independent
30167 of which portion of the viewed message is currently displayed. The
30168 Ctrl-B key can be used to select the previous web hostnames in the same way.
30171 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30173 <End of help on this topic>
30176 ====== h_config_enable_view_addresses =====
30179 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></TITLE>
30182 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-addresses"--></H1>
30184 This feature modifies the behavior of Alpine's MESSAGE TEXT screen.
30185 Setting this feature causes Alpine to select possible email addresses
30186 from the displayed text and display them in boldface for selection.
30189 The first available email address is displayed in inverse. This is the
30190 "selected" address. Pressing RETURN will cause Alpine to enter
30191 the message composition screen with the To: field filled in with the
30194 Use the arrow keys (unless you have set the feature
30195 <A HREF="h_config_enable_view_arrows">"<!--#echo var="FEAT_enable-msg-view-forced-arrows"-->"</A>)
30196 to change which of the hostnames displayed in
30197 boldface is the current selection.
30199 Similarly, when selectable web hostnames are present in a message, the Ctrl-F
30200 key can be used to select the next web hostname in the message independent
30201 of which portion of the viewed message is currently displayed. The
30202 Ctrl-B key can be used to select the previous web hostnames in the same way.
30205 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30207 <End of help on this topic>
30210 ====== h_config_enable_view_arrows =====
30213 <TITLE>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></TITLE>
30216 <H1>FEATURE: <!--#echo var="FEAT_enable-msg-view-forced-arrows"--></H1>
30218 This feature modifies Up and Down arrow key behavior in Alpine's
30219 MESSAGE TEXT screen when selectable Attachments, URL's, or
30220 web-hostnames are presented. Alpine's usual behavior is to move to
30221 the next or previous selectable item if currently displayed or
30222 simply to adjust the screen view by one line.
30226 Setting this feature causes the UP and Down arrow key to behave as
30227 if no selectable items were present in the message.
30231 Note, the Ctrl-F (next selectable item) and Ctrl-B (previous selectable
30232 item) functionality is unchanged.
30235 <End of help on this topic>
30238 ====== h_config_quell_charset_warning =====
30241 <TITLE>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></TITLE>
30244 <H1>FEATURE: <!--#echo var="FEAT_quell-charset-warning"--></H1>
30246 By default, if the message you are viewing contains characters that are
30247 not representable in your
30248 <A HREF="h_config_char_set">"Display Character Set"</A>
30250 add a warning to the start of the displayed text.
30251 If this option is set, then that editorial message will be suppressed.
30253 Setting this feature also suppresses the comment about the character set
30255 For example, when viewing a message you might see
30257 <CENTER><SAMP>From: "[ISO-8859-2] Name" <address></SAMP></CENTER>
30259 in the From header if your Character-Set is something other than ISO-8859-2.
30260 If you set this feature, the comment about the character set will
30261 no longer be there.
30263 <End of help on this topic>
30266 ====== h_config_quell_host_after_url =====
30269 <TITLE>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></TITLE>
30272 <H1>FEATURE: <!--#echo var="FEAT_quell-server-after-link-in-html"--></H1>
30274 By default, links in HTML text are displayed with the host the link
30275 references appended, within square brackets, to the link text. Alpine
30276 does this to help indicate where a link will take you, particularly when
30277 the link text might suggest a different destination.
30280 Setting this feature will prevent the server name from being appended
30281 to the displayed text.
30284 <End of help on this topic>
30287 ====== h_config_prefer_plain_text =====
30290 <TITLE>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></TITLE>
30293 <H1>FEATURE: <!--#echo var="FEAT_prefer-plain-text"--></H1>
30295 A message being viewed may contain alternate versions of the same content.
30296 Those alternate versions are supposed to be ordered by the sending software such that the
30297 first alternative is the least preferred and the last alternative is the
30298 most preferred. Alpine will normally display the most-preferred version that
30299 it knows how to display. This is most often encountered where the two
30300 alternate versions are a plain text version and an HTML version, with the
30301 HTML version listed last as the most preferred.
30303 If this option is set, then any plain text version will be preferred to
30304 all other versions.
30306 When viewing a message there is a command "A TogglePreferPlain",
30307 which will temporarily change the sense of this option.
30308 If this option is set you will first see the plain text version of a
30310 If you then type the "A" command, you will see the most preferred version,
30311 most likely HTML, instead.
30312 Typing the "A" command a second time will switch it back.
30313 Alternatively, if the present option is not set you will originally see
30314 the most preferred version of the message and typing "A" will switch to
30315 the plain text version.
30317 <End of help on this topic>
30320 ====== h_config_pass_control =====
30323 <TITLE>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></TITLE>
30326 <H1>FEATURE: <!--#echo var="FEAT_pass-control-characters-as-is"--></H1>
30328 It is probably not useful to set this option.
30329 This is a legacy option left behind "just in case".
30330 Multi-byte characters that have an octet that has the same
30331 value as a control character are permitted through whether or not
30332 this option is turned on.
30334 This feature controls how certain characters contained in messages are
30336 If set, all characters in a message will be sent to the
30337 screen. Normally, control characters are displayed as shown below to
30338 avoid a garbled screen and to
30339 avoid inadvertently changing terminal setup parameters.
30340 Control characters are usually displayed as two character sequences like
30341 <P><CENTER><SAMP> ^C </SAMP></CENTER><P>
30343 <P><CENTER><SAMP> ^[ </SAMP></CENTER><P>
30345 <P><CENTER><SAMP> ^? </SAMP></CENTER><P>
30347 <P><CENTER><SAMP> ~E </SAMP></CENTER><P>
30348 for the character with value 133 (0x85).
30349 (The DEL character is displayed as ^?, regular control characters are displayed
30350 as the character ^ followed by the character obtained by adding the
30351 five low-order bits of the character to 0x40, and the C1
30352 control characters 0x80 - 0x9F are displayed as the character ~ followed by the
30353 character obtained by adding the
30354 five low-order bits of the character to 0x40.)
30355 Sometimes, in cases where changing a single control character into a
30356 two-character sequence would confuse Alpine's display routines,
30357 a question mark is substituted for the control character.
30359 If you wish to filter out regular control characters but pass the
30360 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
30361 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.
30363 <End of help on this topic>
30366 ====== h_config_pass_c1_control =====
30369 <TITLE>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></TITLE>
30372 <H1>FEATURE: <!--#echo var="FEAT_pass-c1-control-characters-as-is"--></H1>
30374 It is probably not useful to set this option.
30375 This is a legacy option left behind "just in case".
30376 Multi-byte characters that have an octet that has the same
30377 value as a control character are permitted through whether or not
30378 this option is turned on.
30380 If the feature <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
30381 is set, then this feature has no effect.
30382 However, if you wish to filter out regular control characters but pass the
30383 so-called C1 control characters (0x80 <= char < 0xA0) through unchanged, then
30384 you may leave <A HREF="h_config_pass_control"><!--#echo var="FEAT_pass-control-characters-as-is"--></A>
30385 unset and set this feature.
30387 <End of help on this topic>
30390 ====== h_config_fcc_on_bounce =====
30393 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></TITLE>
30396 <H1>FEATURE: <!--#echo var="FEAT_fcc-on-bounce"--></H1>
30398 This feature controls an aspect of Alpine's behavior when bouncing a
30399 message. If set, normal FCC ("File Carbon Copy") processing will be
30400 done, just as if you had composed a message to the address you are
30401 bouncing to. If not set, no FCC of the message will be saved.
30403 <End of help on this topic>
30406 ====== h_config_show_cursor =====
30409 <TITLE>FEATURE: <!--#echo var="FEAT_show-cursor"--></TITLE>
30412 <H1>FEATURE: <!--#echo var="FEAT_show-cursor"--></H1>
30414 This feature controls an aspect of Alpine's displays. If set, the system
30415 cursor will move to convenient locations in the displays. For example,
30416 to the beginning of the status field of the highlighted index line, or
30417 to the highlighted word after a successful WhereIs command. It is intended
30418 to draw your attention to an "interesting" spot on the screen.
30420 <End of help on this topic>
30423 ====== h_config_sort_fcc_alpha =====
30426 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></TITLE>
30429 <H1>FEATURE: <!--#echo var="FEAT_sort-default-fcc-alpha"--></H1>
30431 This feature controls an aspect of Alpine's FOLDER LIST screen.
30432 If set, the default Fcc folder will be sorted alphabetically with the other
30433 folders instead of appearing right after the INBOX.
30435 <End of help on this topic>
30438 ====== h_config_sort_save_alpha =====
30441 <TITLE>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></TITLE>
30444 <H1>FEATURE: <!--#echo var="FEAT_sort-default-save-alpha"--></H1>
30446 This feature controls an aspect of Alpine's FOLDER LIST screen.
30447 If set, the default save folder will be sorted alphabetically with the other
30448 folders instead of appearing right after the INBOX (and default FCC folder).
30450 <End of help on this topic>
30453 ====== h_config_single_list =====
30456 <TITLE>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></TITLE>
30459 <H1>FEATURE: <!--#echo var="FEAT_single-column-folder-list"--></H1>
30461 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30462 the folders will be listed one per line instead of several per line
30463 in the FOLDER LIST display.
30465 <End of help on this topic>
30468 ====== h_config_vertical_list =====
30471 <TITLE>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></TITLE>
30474 <H1>FEATURE: <!--#echo var="FEAT_vertical-folder-list"--></H1>
30476 This feature controls an aspect of Alpine's FOLDER LIST screen. If set,
30477 the folders will be listed alphabetically down the columns rather
30478 than across the columns as is the default.
30480 <End of help on this topic>
30483 ====== h_config_verbose_post =====
30486 <TITLE>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></TITLE>
30489 <H1>FEATURE: <!--#echo var="FEAT_enable-verbose-smtp-posting"--></H1>
30490 This feature controls an aspect of Alpine's message sending. When enabled,
30491 Alpine will send a VERB (i.e., VERBose) command early in the posting process
30492 intended to cause the SMTP server to provide a more detailed account of
30493 the transaction. This feature is typically only useful to system
30494 administrators and other support personel as an aid in troublshooting
30497 Note, this feature relies on a specific capability of the system's mail
30498 transport agent or configured
30499 <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>.
30500 It is possible that this
30501 feature will cause problems for some tranport agents, and may result in
30502 sending failure. In addition, as the verbose output comes from the mail
30503 transport agent, it is likely to vary from one system to another.
30505 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30507 <End of help on this topic>
30510 ====== h_config_auto_reply_to =====
30513 <TITLE>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></TITLE>
30516 <H1>FEATURE: <!--#echo var="FEAT_reply-always-uses-reply-to"--></H1>
30518 This feature controls an aspect of Alpine's Reply command. If set, Alpine
30519 will not prompt when a message being replied to contains a "Reply-To:"
30520 header value, but will simply use its value (as opposed to using the
30521 "From:" field's value).
30525 Note: Using the "Reply-To:" address is usually the preferred behavior,
30526 however, some mailing list managers choose to place the list's address in
30527 the "Reply-To:" field of any message sent out to the list. In such
30528 cases, this feature makes it all too easy for personal replies to be
30529 inadvertently sent to the entire mail list, so be careful!
30531 <End of help on this topic>
30534 ====== h_config_del_skips_del =====
30537 <TITLE>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></TITLE>
30540 <H1>FEATURE: <!--#echo var="FEAT_delete-skips-deleted"--></H1>
30542 This feature controls an aspect of Alpine's Delete command. If set, this
30543 feature will cause the Delete command to advance past following messages that
30544 are marked deleted. In other words, pressing "D" will both mark the
30545 current message deleted and advance to the next message that is not marked
30547 This feature is set by default.
30549 <End of help on this topic>
30551 ====== h_config_expunge_manually =====
30554 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></TITLE>
30557 <H1>FEATURE: <!--#echo var="FEAT_expunge-only-manually"--></H1>
30559 Normally, when you close a folder that contains deleted messages you are
30560 asked if you want to expunge those messages from the folder permanently.
30561 If this feature is set, you won't be asked and the deleted messages will
30562 remain in the folder.
30563 If you choose to set this feature you will have to expunge the
30564 messages manually using the eXpunge command, which you can use while
30565 in the MESSAGE INDEX screen.
30566 If you do not expunge deleted messages the size of your
30567 folder will continue to increase until you are out of disk space.
30570 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30572 <End of help on this topic>
30575 ====== h_config_auto_expunge =====
30578 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></TITLE>
30581 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm"--></H1>
30583 This features controls an aspect of Alpine's eXpunge command. If set, you
30584 will <B>not</B> be prompted to confirm your intent before the expunge takes
30586 Actually, this is only true for the INBOX folder and for folders in the
30587 Incoming Folders collection. See the feature
30588 <A HREF="h_config_full_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm-everywhere"-->"</A>.
30591 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30593 <End of help on this topic>
30596 ====== h_config_full_auto_expunge =====
30599 <TITLE>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></TITLE>
30602 <H1>FEATURE: <!--#echo var="FEAT_expunge-without-confirm-everywhere"--></H1>
30604 This features controls an aspect of Alpine's eXpunge command. If set, you
30605 will <B>not</B> be prompted to confirm your intent before the expunge
30606 takes place. This feature sets this behavior for all folders, unlike the
30607 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
30608 feature that works only for incoming folders.
30611 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30613 <End of help on this topic>
30616 ====== h_config_auto_read_msgs =====
30619 <TITLE>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></TITLE>
30622 <H1>FEATURE: <!--#echo var="FEAT_auto-move-read-msgs"--></H1>
30623 This feature controls an aspect of Alpine's behavior upon quitting. If set,
30625 <A HREF="h_config_read_message_folder">"<!--#echo var="VAR_read-message-folder"-->"</A>
30626 option is also set, then Alpine will
30627 automatically transfer all read messages to the designated folder and mark
30628 them as deleted in the INBOX. Messages in the INBOX marked with an
30629 "N" (meaning New, or unseen) are not affected.
30632 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30634 <End of help on this topic>
30637 ====== h_config_auto_fcc_only =====
30640 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></TITLE>
30643 <H1>FEATURE: <!--#echo var="FEAT_fcc-only-without-confirm"--></H1>
30644 This features controls an aspect of Alpine's composer.
30645 The only time this feature will be used is if you attempt to send mail
30646 that has no recipients but does have an Fcc.
30647 Normally, Alpine will ask if you really mean to copy the message only to
30649 That is, it asks if you really meant to have no recipients.
30650 If this feature is set, you
30651 will <B>not</B> be prompted to confirm your intent to make only a copy
30652 of a message with no recipients.
30654 This feature is closely related to
30655 <A HREF="h_config_warn_if_no_to_or_cc"><!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></A>.
30656 The difference between this feature and that feature is that this feature
30657 considers a Bcc to be a recipient while that feature will ask for confirmation
30658 even if there is a Bcc when there is no To, Cc, or Newsgroup.
30659 The default values also differ. This feature defaults to asking the question
30660 and you have to turn it off.
30661 The <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--> feature defaults to not asking
30662 unless you turn it on.
30666 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30668 <End of help on this topic>
30671 ====== h_config_mark_fcc_seen =====
30674 <TITLE>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></TITLE>
30677 <H1>FEATURE: <!--#echo var="FEAT_mark-fcc-seen"--></H1>
30679 This features controls the way Fccs (File carbon copies) are
30680 made of the messages you send.
30683 Normally, when Alpine saves a copy of a message you sent as an Fcc, that
30684 copy will be marked as Unseen.
30685 When you look at the folder it was saved in the message will appear to
30686 be a New message until you read it.
30687 When this feature is enabled, the message will be marked as having
30692 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30694 <End of help on this topic>
30697 ====== h_config_no_fcc_attach =====
30700 <TITLE>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></TITLE>
30703 <H1>FEATURE: <!--#echo var="FEAT_fcc-without-attachments"--></H1>
30705 This features controls the way Fcc's (File carbon copies) are
30706 made of the messages you send.
30709 Normally, Alpine saves an exact copy of your message as it was sent.
30710 When this feature is enabled, the "body" of the message
30711 you send (the text you type in the composer) is preserved in the
30712 copy as before, however all attachments are replaced with text
30713 explaining what had been sent rather than the attachments themselves.
30716 This feature also affects Alpine's "Send ?" confirmation prompt
30717 in that a new "^F Fcc Attchmnts" option becomes available which
30718 allows you to interactively set whether or not attachments are saved
30723 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30725 <End of help on this topic>
30728 ====== h_config_read_in_newsrc_order =====
30731 <TITLE>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></TITLE>
30734 <H1>FEATURE: <!--#echo var="FEAT_news-read-in-newsrc-order"--></H1>
30736 This feature controls the order in which newsgroups will be presented. If
30737 set, they will be presented in the same order as they occur in your
30738 <!--chtml if pinemode="os_windows"-->
30741 ".newsrc"
30743 file (the default location of which can be changed with the
30744 <A HREF="h_config_newsrc_path">"<!--#echo var="VAR_newsrc-path"-->"</A> option).
30746 If not set, the newsgroups will be presented in alphabetical order.
30749 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30751 <End of help on this topic>
30754 ====== h_config_quell_tz_comment =====
30757 <TITLE>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></TITLE>
30760 <H1>FEATURE: <!--#echo var="FEAT_quell-timezone-comment-when-sending"--></H1>
30762 Normally, when Alpine generates a Date header for outgoing mail,
30763 it will try to include the symbolic timezone at the end of the
30764 header inside parentheses.
30765 The symbolic timezone is often three characters long, but on
30766 some operating systems, it may be longer.
30767 Apparently there are some SMTP servers in the world that will reject an
30768 incoming message if it has a Date header longer than about 80 characters.
30769 If this feature is set, the symbolic timezone normally generated by
30770 Alpine will not be included.
30771 You probably don't need to worry about this feature unless you run into
30772 the problem described above.
30775 <End of help on this topic>
30778 ====== h_config_post_wo_validation =====
30781 <TITLE>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></TITLE>
30784 <H1>FEATURE: <!--#echo var="FEAT_news-post-without-validation"--></H1>
30786 This feature controls whether the NNTP server is queried as newsgroups
30787 are entered for posting. Validation over slow links (e.g. dialup using
30788 SLIP or PPP) can cause delays. Set this feature to eliminate such delays.
30790 <End of help on this topic>
30793 ====== h_config_send_wo_confirm =====
30796 <TITLE>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></TITLE>
30799 <H1>FEATURE: <!--#echo var="FEAT_send-without-confirm"--></H1>
30801 By default, when you send or post a message you will be asked to confirm
30802 with a question that looks something like:
30805 <CENTER><SAMP>Send message?</SAMP></CENTER>
30808 If this feature is set, you
30809 will <B>not</B> be prompted to confirm your intent to send
30810 and your message will be sent.
30812 If this feature is set it disables some possibilities and renders some
30813 other features meaningless.
30814 You will not be able to use
30815 <A HREF="h_config_sending_filter">Sending Filters</A>,
30816 Verbose sending mode,
30817 <A HREF="h_config_compose_bg_post">Background Sending</A>,
30818 <A HREF="h_config_compose_dsn">Delivery Status Notifications</A>,
30819 or ^V to turn off the generation of flowed text for this message.
30820 These options are normally available as suboptions in the Send prompt, but
30821 with no Send prompt the options are gone.
30824 A somewhat related feature is
30825 <A HREF="h_config_quell_post_prompt">"<!--#echo var="FEAT_quell-extra-post-prompt"-->"</A>,
30826 which may be used to eliminate the extra confirmation
30827 question when posting to a newsgroup.
30830 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30832 <End of help on this topic>
30835 ====== h_config_quell_filtering_done_message =====
30838 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></TITLE>
30841 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-done-message"--></H1>
30843 If you use Filter Rules that move messages or set status of messages
30844 you sometimes see a message from Alpine that looks like
30847 <CENTER><SAMP>filtering done</SAMP></CENTER>
30850 If this feature is set, this message will be suppressed.
30852 <A HREF="h_config_quell_filtering_messages"><!--#echo var="FEAT_quell-filtering-messages"--></A>
30853 is set then this message will be suppressed regardless.
30857 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30859 <End of help on this topic>
30862 ====== h_config_quell_filtering_messages =====
30865 <TITLE>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></TITLE>
30868 <H1>FEATURE: <!--#echo var="FEAT_quell-filtering-messages"--></H1>
30870 If you use Filter Rules that move messages or set status of messages
30871 you sometimes see messages from Alpine that look like
30874 <CENTER><SAMP><filter name>: Moving 2 filtered messages to <folder name></SAMP></CENTER>
30880 <CENTER><SAMP><filter name>: Setting flags in 5 messages</SAMP></CENTER>
30886 <CENTER><SAMP>Processing filter <filter name></SAMP></CENTER>
30889 If this feature is set, these messages will be suppressed.
30891 <A HREF="h_config_quell_filtering_done_message"><!--#echo var="FEAT_quell-filtering-done-message"--></A>
30896 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30898 <End of help on this topic>
30901 ====== h_config_quell_post_prompt =====
30904 <TITLE>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></TITLE>
30907 <H1>FEATURE: <!--#echo var="FEAT_quell-extra-post-prompt"--></H1>
30909 By default, when you post a message to a newsgroup you are asked to confirm
30910 that you want to post with the question
30913 <CENTER><SAMP>Posted message may go to thousands of readers. Really post?</SAMP></CENTER>
30916 If this feature is set, you
30917 will <B>not</B> be prompted to confirm your intent to post to a newsgroup
30918 and your message will be posted.
30922 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30924 <End of help on this topic>
30927 ====== h_config_check_mail_onquit =====
30930 <TITLE>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></TITLE>
30933 <H1>FEATURE: <!--#echo var="FEAT_check-newmail-when-quitting"--></H1>
30935 If this feature is set, Alpine will check for new mail after you give the
30937 If new mail has arrived since the previous check, you will be notified
30938 and given the choice of quitting or not quitting.
30941 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30943 <End of help on this topic>
30946 ====== h_config_inbox_no_confirm =====
30949 <TITLE>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></TITLE>
30952 <H1>FEATURE: <!--#echo var="FEAT_return-to-inbox-without-confirm"--></H1>
30954 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
30955 command and there are no more folders or newsgroups to visit, you are asked
30956 if you want to return to the INBOX.
30957 If this feature is set you will not be asked.
30958 It will be assumed that you do want to return to the INBOX.
30961 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30963 <End of help on this topic>
30966 ====== h_config_dates_to_local =====
30969 <TITLE>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></TITLE>
30972 <H1>FEATURE: <!--#echo var="FEAT_convert-dates-to-localtime"--></H1>
30974 Normally, the message dates that you see in the
30975 MESSAGE INDEX and MESSAGE VIEW are displayed in the timezone they were sent from.
30976 For example, if a message was sent to you from a few timezones to the east
30977 it might appear that it was sent from the future;
30978 or if it was sent from somewhere to the west it might appear
30979 as if it is from yesterday even though it was sent only a few minutes ago.
30980 If this feature is set an attempt will be made to convert the dates
30981 to your local timezone to be displayed.
30983 Note that this does not affect the results of Select by Date or of
30984 anything else other than these displayed dates.
30985 When viewing the message you may look at the original unconverted value of the Date
30986 header by using the <A HREF="h_common_hdrmode">HdrMode Command</A>.
30989 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
30991 <End of help on this topic>
30994 ====== h_config_tab_no_prompt =====
30997 <TITLE>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></TITLE>
31000 <H1>FEATURE: <!--#echo var="FEAT_continue-tab-without-confirm"--></H1>
31002 Normally, when you use the TAB <A HREF="h_common_nextnew">NextNew</A>
31003 command and there is a problem checking a folder, you are asked
31004 whether you want to continue with the search in the following folder or not.
31005 This question gives you a chance to stop the NextNew processing.
31006 (The checking problem might be caused by the fact that the folder does not
31007 exist, or by an authentication problem, or by a server problem
31011 If this feature is set you will not be asked.
31012 It will be assumed that you do want to continue.
31015 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31017 <End of help on this topic>
31020 ====== h_config_input_history =====
31023 <TITLE>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></TITLE>
31026 <H1>FEATURE: <!--#echo var="FEAT_disable-save-input-history"--></H1>
31028 Many of the prompts that ask for input in the status line near the
31029 bottom of the screen will respond to Up Arrow and Down Arrow
31030 with the history of previous entries.
31031 For example, in the MESSAGE INDEX screen when you use the WhereIs
31032 command the text you entered will be remembered and can be recalled
31033 by using the Up Arrow key.
31034 Another example, when saving a message the folders saved to will
31035 be remembered and can be recalled using the arrow keys.
31037 In the Save prompt, some users prefer that the Up and Down arrow keys
31038 be used for the Previous Collection and Next Collection commands
31039 instead of for a history of previous saves.
31040 If this option is set the Up and Down arrow keys will become synonyms for the
31041 Previous Collection and Next Collection (^P and ^N) commands in the
31042 prompt for the name of a folder to Save to or in the prompt for the
31043 name of a folder to GoTo.
31044 When this feature is not set (the default), ^P and ^N will change the
31045 collection and the arrow keys will show the history.
31048 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31050 <End of help on this topic>
31053 ====== h_config_confirm_role =====
31056 <TITLE>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></TITLE>
31059 <H1>FEATURE: <!--#echo var="FEAT_confirm-role-even-for-default"--></H1>
31061 If you have roles, when you Reply to or Forward a message, or Compose
31062 a new message, Alpine
31063 will search through your roles for one that matches.
31064 Normally, if no matches are found you will be placed into the composer
31065 with no opportunity to select a role.
31066 If this feature is set, then you will be asked to confirm that you don't
31068 This will give you the opportunity to select a role (with the ^T command).
31069 If you confirm no role with a Return, you will be placed in
31070 the composer with no role.
31071 You may also confirm with either an "N" or a "Y".
31072 These behave the same as if you pressed the Return.
31073 (The "N" and "Y" answers are available because they
31074 match what you might type if there was a role match.)
31076 If you are using the alternate form of the Compose command called
31077 "Role", then all of your roles will be available to you,
31078 independent of the value of this feauture and of the values set for all of
31079 Reply Use, Forward Use, and Compose Use.
31082 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31084 <End of help on this topic>
31087 ====== h_config_news_cross_deletes =====
31090 <TITLE>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></TITLE>
31093 <H1>FEATURE: <!--#echo var="FEAT_news-deletes-across-groups"--></H1>
31095 This feature controls what Alpine does when you delete a message in a
31096 newsgroup that appears in more than one newsgroup. Such a message
31097 is sometimes termed a "crossposting" in that it was posted
31098 across several newsgroups.
31101 Alpine's default behavior when you delete such a message is to remove
31102 only the copy in the current newsgroup from view when you use the
31103 "Exclude" command or the next time you visit the newsgroup.
31106 Enabling this feature causes Alpine to remove every occurrence of the
31107 message from all newsgroups it appears in and to which you are
31111 NOTE: As currently implemented, enabling this feature may increase the
31112 time it takes the Expunge command and newsgroup closing to complete.
31116 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31118 <End of help on this topic>
31121 ====== h_config_news_catchup =====
31124 <TITLE>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></TITLE>
31127 <H1>FEATURE: <!--#echo var="FEAT_news-offers-catchup-on-close"--></H1>
31129 This feature controls what Alpine does as it closes a newsgroup.
31130 When set, Alpine will offer to delete all messages from the newsgroup
31131 as you are quitting Alpine or opening a new folder.
31134 This feature is useful if you typically read all the interesting messages
31135 in a newsgroup each time you open it. This feature saves you from
31136 having to delete each message in a newsgroup as you read it or from
31137 selecting all the messages and doing an
31138 <A HREF="h_config_enable_agg_ops">aggregate delete</A> before you
31139 move on to the next folder or newsgroup.
31143 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31145 <End of help on this topic>
31148 ====== h_config_next_thrd_wo_confirm =====
31151 <TITLE>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></TITLE>
31154 <H1>FEATURE: <!--#echo var="FEAT_next-thread-without-confirm"--></H1>
31156 This feature controls an aspect of Alpine's Next and Prev commands in
31157 the case where you are using one of the
31158 "separate-index-screen" styles for the configuration option
31159 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
31160 and currently have the folder sorted by a Threaded or OrderedSubject sort.
31161 When you are Viewing a particular thread you have a
31162 MESSAGE INDEX of only the messages in that thread.
31163 If you press the Next command with the last message in the thread highlighted
31164 you will normally be asked if you want to "View next thread?",
31165 assuming there is a next thread to view.
31166 If this feature is set it will be assumed that you always want to view the
31167 next thread and you won't be asked to confirm that.
31168 Similarly, if the first message of the thread is highlighted and you
31169 press the Prev command, this feature will prevent the question
31170 "View previous thread".
31172 This feature only has an effect in the MESSAGE INDEX screen.
31173 If you then view a particular message from that screen and press the
31174 Next command, you will be sent to the next thread without being asked,
31175 independent of the setting of this feature.
31178 <A HREF="h_config_auto_open_unread">"<!--#echo var="FEAT_auto-open-next-unread"-->"</A> also has some similar effects.
31180 <End of help on this topic>
31183 ====== h_config_kw_braces =====
31186 <TITLE>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></TITLE>
31189 <H1>OPTION: <!--#echo var="VAR_keyword-surrounding-chars"--></H1>
31191 This option controls a minor aspect of Alpine's MESSAGE INDEX and MESSAGE
31193 If you have modified the
31194 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
31195 so that either the "SUBJKEY" or "SUBJKEYINIT" tokens
31196 are used to display keywords or their initials along with the Subject; then
31197 this option may be used to modify the resulting display slightly.
31198 By default, the keywords or initials displayed for these tokens will be
31199 surrounded with curly braces ({ and }) and a trailing space.
31200 For example, if keywords "Work" and "Now" are set for
31201 a message, the "SUBJKEY" token will normally look like
31203 <CENTER><SAMP>{Work Now} actual subject</SAMP></CENTER>
31205 and the SUBJKEYINIT token would look like
31207 <CENTER><SAMP>{WN} actual subject</SAMP></CENTER>
31209 The default character before the keywords is the left brace ({) and the
31210 default after the keywords is the right brace followed by a space (} ).
31212 This option allows you to change that.
31213 You should set it to two values separated by a space.
31214 The values may be quoted if they include space characters.
31215 So, for example, the default value could be specified explicitly by setting this
31218 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="{" "} "</SAMP></CENTER>
31220 The first part wouldn't need to be quoted (but it doesn't hurt).
31221 The second part does need the quotes because it includes a space character.
31222 If you wanted to change the braces to brackets you could use
31224 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="[" "] "</SAMP></CENTER>
31226 Inside the quotes you can use backslash quote to mean quote, so
31228 <CENTER><SAMP><!--#echo var="VAR_keyword-surrounding-chars"-->="\"" "\" "</SAMP></CENTER>
31232 <CENTER><SAMP>"Work Now" actual subject</SAMP></CENTER>
31234 It is also possible to color keywords in the index using the
31235 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>).
31237 It is not possible to change the fact that a space character is used to
31238 separate the keywords if more than one keyword is set for a message.
31239 It is also not possible to change the fact that there are no separators
31240 between the keyword initials if more than one keyword is set.
31242 <End of help on this topic>
31245 ====== h_config_opening_sep =====
31248 <TITLE>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></TITLE>
31251 <H1>OPTION: <!--#echo var="VAR_opening-text-separator-chars"--></H1>
31253 This option controls a minor aspect of Alpine's MESSAGE INDEX screen.
31254 With some setups the text of the subject is followed
31255 by the opening text of the message if there is any room available in the index line.
31256 If you have configured your
31257 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
31258 to include one of the Subject tokens that causes this behavior
31259 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), then this option may be used
31260 to modify what is displayed slightly.
31261 By default, the Subject is separated from the opening text of the message by
31262 the three characters space dash space;
31264 <CENTER><SAMP>" - "</SAMP></CENTER>
31266 Use this option to set it to something different.
31267 The value must be quoted if it includes any space characters.
31268 For example, the default value could be specified explicitly by setting this
31271 <CENTER><SAMP><!--#echo var="VAR_opening-text-separator-chars"-->=" - "</SAMP></CENTER>
31273 <End of help on this topic>
31276 ====== h_config_select_wo_confirm =====
31279 <TITLE>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></TITLE>
31282 <H1>FEATURE: <!--#echo var="FEAT_select-without-confirm"--></H1>
31284 This feature controls an aspect of Alpine's Save, Export, and Goto commands.
31285 These commands all take text input to specify the name of the folder or
31286 file to be used, but allow you to press ^T for a list of possible names.
31287 If set, the selected name will be used immediately, without further
31288 opportunity to confirm or edit the name.
31290 Some related help topics are
31292 <LI> <A HREF="h_mainhelp_aggops">Aggregate Operations</A>
31293 <LI> <A HREF="h_index_cmd_select">Selecting: Select and WhereIs/Select</A>,
31294 <LI> <A HREF="h_config_enable_agg_ops"><!--#echo var="FEAT_enable-aggregate-command-set"--></A>,
31295 <LI> <A HREF="h_config_auto_unselect"><!--#echo var="FEAT_auto-unselect-after-apply"--></A>.
31296 <LI> <A HREF="h_config_auto_unzoom"><!--#echo var="FEAT_auto-unzoom-after-apply"--></A>, and
31297 <LI> <A HREF="h_config_auto_zoom"><!--#echo var="FEAT_auto-zoom-after-select"--></A>.
31300 <End of help on this topic>
31303 ====== h_config_save_part_wo_confirm =====
31306 <TITLE>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></TITLE>
31309 <H1>FEATURE: <!--#echo var="FEAT_save-partial-msg-without-confirm"--></H1>
31311 This feature controls an aspect of Alpine's Save command.
31312 By default, when you Save a message that has some deleted parts, you will
31313 be asked to confirm that you want to Save with a prompt that looks like:
31315 <CENTER><SAMP>Saved copy will NOT include entire message! Continue?</SAMP></CENTER>
31317 If this feature is set, you will not be asked.
31319 <End of help on this topic>
31322 ====== h_config_use_resentto =====
31325 <TITLE>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></TITLE>
31328 <H1>FEATURE: <!--#echo var="FEAT_use-resent-to-in-rules"--></H1>
31330 This feature is turned off by default because turning it on causes problems
31331 with some deficient IMAP servers.
31332 In Alpine <A HREF="h_mainhelp_filtering">Filters</A> and other types of Rules, if the
31333 <A HREF="h_rule_patterns">Pattern</A>
31334 contains a To header pattern and this feature is turned on,
31335 then a check is made in the message to see
31336 if a Resent-To header is present, and that is used instead of the To header.
31337 If this feature is not turned on, then the regular To header will always
31341 <End of help on this topic>
31344 ====== h_config_use_reg_start_for_stayopen =====
31347 <TITLE>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></TITLE>
31350 <H1>FEATURE: <!--#echo var="FEAT_use-regular-startup-rule-for-stayopen-folders"--></H1>
31352 This feature affects which message is selected as the current message
31354 <A HREF="h_config_permlocked">Stay Open</A> folder.
31356 Normally, the starting position for an incoming folder (which most Stay Open
31357 folders will likely be) is controlled by the
31358 <A HREF="h_config_inc_startup"><!--#echo var="VAR_incoming-startup-rule"--></A>.
31359 However, if a folder is a Stay Open folder, when you re-enter the folder
31360 after the first time the current message will be the same as it was when
31361 you left the folder.
31362 An exception is made if you use the TAB command to get to the folder.
31363 In that case, the message number will be incremented by one from what it
31364 was when you left the folder.
31366 The above special behavior is thought to be useful.
31367 However, it is special and different from what you might at first expect.
31368 If this feature is set, then Stay Open folders will not be treated specially
31369 as far as the startup rule is concerned.
31372 <End of help on this topic>
31375 ====== h_config_use_current_dir =====
31378 <TITLE>FEATURE: <!--#echo var="FEAT_use-current-dir"--></TITLE>
31381 <H1>FEATURE: <!--#echo var="FEAT_use-current-dir"--></H1>
31383 This feature controls an aspect of several commands.
31384 If set, your "current working directory"
31385 <!--chtml if pinemode="running"-->
31386 (which, at least for your current Alpine "session,"
31387 is "<!--#echo var="CURRENT_DIR"-->")
31389 will be used instead of your home directory
31390 <!--chtml if pinemode="running"-->
31391 (which, in the present configuration of your system, is
31392 "<!--#echo var="HOME_DIR"-->")
31394 for all of the following operations:<UL>
31395 <LI> Export in the MESSAGE INDEX and MESSAGE TEXT screens
31396 <LI> Attachment Save in the MESSAGE TEXT and ATTACHMENT TEXT screens
31397 <LI> <!--chtml if pinemode="function_key"-->F4
31398 <!--chtml else-->Ctrl-R
31399 <!--chtml endif--> file inclusion in the COMPOSER
31400 <LI> <!--chtml if pinemode="function_key"-->F5
31401 <!--chtml else-->Ctrl-J
31402 <!--chtml endif--> file attachment in the COMPOSER
31404 <!--chtml if pinemode="os_windows"-->
31406 If you are starting PC-Alpine from a desktop icon or the Start menu,
31407 you can set the "current drive"
31408 by specifying it in the "Start in:"
31409 box found in the Shortcut tab of the Properties.
31413 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31417 <End of help on this topic>
31420 ====== h_config_save_wont_delete =====
31423 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></TITLE>
31426 <H1>FEATURE: <!--#echo var="FEAT_save-will-not-delete"--></H1>
31428 This feature controls one aspect of the Save command. If set, Save will
31429 not mark the message "deleted" (its default behavior) after
31430 it has been copied to the designated folder.
31433 <End of help on this topic>
31436 ====== h_config_use_boring_spinner =====
31439 <TITLE>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></TITLE>
31442 <H1>FEATURE: <!--#echo var="FEAT_busy-cue-spinner-only"--></H1>
31444 When Alpine is delayed for some reason it usually shows that
31445 something is happening with a small animated display in the status
31446 message line near the bottom of the screen.
31447 Setting this feature will cause that animation to be the same
31448 each time instead of having Alpine choose a random animation.
31449 You may turn the animation off altogether by setting the
31450 <A HREF="h_config_active_msg_interval"><!--#echo var="VAR_busy-cue-rate"--></A>
31454 <End of help on this topic>
31457 ====== h_config_unsel_wont_advance =====
31460 <TITLE>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></TITLE>
31463 <H1>FEATURE: <!--#echo var="FEAT_unselect-will-not-advance"--></H1>
31465 This feature controls one aspect of the Unselect Current message command.
31466 Normally, when the Unselect current message command (:) is typed when the
31467 current message is selected, the message will be unselected and the next
31468 message will become the current message.
31469 If this feature is set, the cursor will not advance to the next message.
31470 Instead, the current message will remain the current message after
31474 <End of help on this topic>
31477 ====== h_config_prune_uses_iso =====
31480 <TITLE>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></TITLE>
31483 <H1>FEATURE: <!--#echo var="FEAT_prune-uses-yyyy-mm"--></H1>
31485 By default, Alpine asks monthly whether or not you would like to rename
31486 some folders to a new name containing the date.
31487 It also asks whether or not you would like to delete some old folders.
31488 See the <A HREF="h_config_pruning_rule"><!--#echo var="VAR_pruning-rule"--></A> option for an
31492 By default, the name used when renaming a folder looks like
31494 <CENTER><SAMP><foldername>-<month>-<year></SAMP></CENTER>
31496 For example, the first time you run Alpine in May of 2004,
31497 the folder "sent-mail" might be renamed to
31499 <CENTER><SAMP>sent-mail-apr-2004</SAMP></CENTER>
31501 If this feature is set, the name used will be of the form
31503 <CENTER><SAMP><foldername>-<yyyy>-<mm></SAMP></CENTER>
31505 where "yyyy" is the year and "mm" is the two-digit
31506 month (01, 02, ..., 12).
31507 For the April, 2004 example above, it would instead be
31509 <CENTER><SAMP>sent-mail-2004-04</SAMP></CENTER>
31511 because April is the 4th month of the year.
31512 A reason you might want to set this feature is so that the folders
31513 will sort in chronological order.
31516 <End of help on this topic>
31519 ====== h_config_save_advances =====
31522 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-advance"--></TITLE>
31525 <H1>FEATURE: <!--#echo var="FEAT_save-will-advance"--></H1>
31527 This feature controls one aspect of the Save command. If set, Save will
31528 (in addition to copying the current message to the designated folder) also
31529 advance to the next message.
31532 <End of help on this topic>
31535 ====== h_config_force_arrow =====
31538 <TITLE>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></TITLE>
31541 <H1>FEATURE: <!--#echo var="FEAT_force-arrow-cursor"--></H1>
31543 This feature affects Alpine's MESSAGE INDEX display routine.
31544 If set, the normal inverse-video cursor will be
31545 replaced by a simple "arrow" cursor, which normally occupies the
31546 second column of the index display.
31548 This is the same index cursor you get if you turn on
31549 <A HREF="h_config_force_low_speed"><!--#echo var="FEAT_assume-slow-link"--></A>, but the index
31550 line coloring will still be present if this feature is turned on and
31551 <!--#echo var="FEAT_assume-slow-link"--> is off.
31553 An alternative version of the Arrow cursor is available by including the
31554 <A HREF="h_config_index_arrow_color">ARROW</A>
31556 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
31558 It ought to be the case that this feature also affects the ATTACHMENT INDEX,
31559 but that is not implemented.
31562 <End of help on this topic>
31565 ====== h_config_ignore_size =====
31568 <TITLE>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></TITLE>
31571 <H1>FEATURE: <!--#echo var="FEAT_ignore-size-changes"--></H1>
31573 When you have an account residing in an IMAP server, Alpine records the
31574 size of each message as reported by the server. However, when Alpine saves
31575 a message in such IMAP server, Alpine will compute the size of the message
31576 independently, from the data it received. If these two numbers do not
31577 match for a message, Alpine asks you if you still want to take the risk of
31578 saving such message, since data corruption or loss of data could result
31582 Sometimes the root of this problem is that the IMAP server does not
31583 compute sizes correctly, and there will not be loss of information when
31584 saving such message. Enabling this feature will make Alpine ignore such
31585 error and continue saving the message without producing any warnings or
31586 ever stopping the process, as if there had not been any error. This option
31587 applies to all IMAP servers that you use, so if you enable this feature,
31588 size discrepancy warnings will not be given for any IMAP server you
31592 Example of a server where you could reproduce this problem is the Gmail
31593 IMAP server. Another example can be found in some versions of the Exchange
31597 It is recommended that this feature be disabled most of the time and only
31598 enabled when you find a server which you can determine that has the above
31599 mentioned defect, but be disabled again after making the save operation
31603 <End of help on this topic>
31606 ====== h_config_force_low_speed =====
31609 <TITLE>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></TITLE>
31612 <H1>FEATURE: <!--#echo var="FEAT_assume-slow-link"--></H1>
31616 This feature affects Alpine's display routines. If set, the normal
31617 inverse-video cursor (used to highlight the current item in a list) will be
31618 replaced by an "arrow" cursor and other
31619 screen update optimizations for
31620 low-speed links (e.g. 2400 bps dialup connections) will be activated.
31621 One of the optimizations is that colored index lines (set up with Indexcolor
31622 Rules) will not be colored.
31623 If you are just turning this feature on because you like using
31624 the "arrow" cursor you may have an arrow cursor with index line
31625 coloring by turning this feature off and the
31626 <A HREF="h_config_force_arrow"><!--#echo var="FEAT_force-arrow-cursor"--></A> on.
31629 <End of help on this topic>
31632 ====== h_config_show_delay_cue =====
31635 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></TITLE>
31638 <H1>FEATURE: <!--#echo var="FEAT_enable-mail-check-cue"--></H1>
31640 If set, this feature will cause an asterisk to appear in the upper
31641 left-hand corner of the screen whenever Alpine checks for new mail.
31642 Two asterisks whenever Alpine saves (checkpoints) the state of the current
31645 <!--chtml if pinemode="os_windows"-->
31647 In addition, PC-Alpine will display a less-than symbol, '<', when
31648 it is trying to open a network connection (e.g, to open your INBOX
31650 server) or read from the network connection. A greater-than symbol,
31651 will be displayed when PC-Alpine is trying to write to the network
31652 connection (e.g, sending a command to your IMAP server).
31656 <End of help on this topic>
31659 ====== h_config_color_style =====
31662 <TITLE>OPTION: Color Style</TITLE>
31665 <H1>OPTION: Color Style</H1>
31669 If the terminal or terminal emulator you are using is capable of displaying
31670 colors, this option controls whether or not color will be used in Alpine.
31671 If you turn color on and things are set up correctly,
31672 you should see color appear on the screen immmediately.
31673 Modern terminal emulators are usually capable of displaying colors.
31675 The available options include:
31680 <DD>Don't use color.
31683 <DT>use-termdef</DT>
31684 <DD>In order to decide if your terminal is capable of color, Alpine looks in
31685 the terminal capabilities database, TERMINFO or TERMCAP, depending on
31686 how Alpine was compiled.
31687 This is a good option to choose if you switch between a color and a non-color
31688 terminal with the same Alpine configuration.
31689 Alpine will know to use color on the color terminal because it is described
31690 in the termcap entry, and Alpine will know to use black and white on the
31691 non-color terminal.
31692 The Alpine Technical Notes
31693 <CENTER><SAMP><A HREF="http://www.washington.edu/alpine/tech-notes/">http://www.washington.edu/alpine/tech-notes/</A></SAMP></CENTER>
31694 have more information on configuring a TERMCAP or TERMINFO
31695 entry for color Alpine.
31696 This is usually something a system administrator does.
31699 <DT>force-ansi-8color</DT>
31700 <DD>This is probably the setting that most people should use.
31701 Because setting up a termcap entry is confusing and because the
31702 terminal capabilities database is often not correctly configured for color,
31703 this choice and the next may be easier for you to use.
31704 If your terminal emulator responds to ANSI color escape sequences, which
31705 many do, this option will cause Alpine to believe your terminal will respond
31706 to the escape sequences that produce eight different foreground and background
31708 The escape sequences used to set the foreground colors are
31710 <P><CENTER>ESC [ 3 <color_number> m</CENTER><P>
31712 where the color_number is an ASCII digit between 0 and 7.
31713 The numbers 0 through 7 should correspond to the colors black, red, green,
31714 yellow, blue, magenta, cyan, and white.
31715 Some terminal emulators use a pre-ANSI scheme that swaps
31716 the colors blue and red and the colors yellow and cyan.
31717 This will cause the default colors to be different, but other than that
31718 things should work fine.
31719 There is also a 9th color available, the last one shown, which is the default
31720 color from the terminal emulator.
31721 When used as a background color some people refer to this color as
31722 "transparent", which is why the letters "TRAN" are
31723 shown in the color swatch of the SETUP COLOR screen.
31724 The foreground transparent color is shown as
31725 the color of the "TRAN" text.
31726 (The transparent color will not work correctly in a PC-Alpine configuration.)
31727 The escape sequences used to set the background colors are the same
31728 as for the foreground colors except a "4" replaces the "3".
31729 The escape sequences for foreground and background default colors (transparent)
31732 Note: With the Tera Term terminal emulator this setting works well.
31733 You should also have the Tera Term "Full color" option turned OFF.
31734 You may find the "Full color" option in Tera Term's "Setup"
31735 menu, in the "Window" submenu.
31738 <DT>force-ansi-16color</DT>
31739 <DD>Many terminal emulators know about the same eight colors above
31741 This option attempts to use all 16 colors.
31742 The same escape sequences as for the eight-color terminal are used
31743 for the first eight colors.
31744 The escape sequences used to set foreground colors 8-15 are the same as
31745 for 0-7 except the "3" is replaced with a "9".
31746 The background color sequences for colors 8-15 are the same as for 0-7
31747 except the "4" is replaced with "10".
31748 You can tell if the 16 colors are working by turning on this option
31749 and then going into one of the color configuration screens, for example,
31750 the configuration screen for Normal Color.
31751 If you see 16 different colors to select from (plus a 17th for
31752 the transparent color), it's working.
31755 <DT>force-xterm-256color</DT>
31756 <DD>Some versions of xterm (and some other terminal emulators)
31757 have support for 256 colors.
31758 The escape sequences used to set the foreground colors are
31760 <P><CENTER>ESC [ 38 ; 5 ; <color_number> m</CENTER><P>
31762 where the color_number is an ASCII digit between 0 and 255.
31763 Background colors are the same with the 38 replaced with a 48.
31764 The numbers 0 through 15 are probably similar to the 16 color version
31765 above, then comes a 6x6x6 color cube, followed by 24 colors of gray.
31766 The terminal default (transparent) color is the 257th color at the bottom.
31767 Some terminal emulators will misinterpret these escape sequences causing
31768 the terminal to blink or overstrike characters or to do something else
31771 The PuTTY terminal emulator has an option called "Allow terminal to
31772 use xterm 256-colour mode" which allows PuTTY to work well with
31773 this 256-color setting.
31779 The normal default is "no-color".
31782 Once you've turned on color you may set the
31783 colors of many objects on the screen individually.
31784 For example, you may add colors to the status letters on the MESSAGE
31786 Most categories of color that Alpine supports are configurable here.
31787 For example, "Normal Color"
31788 is the color used to display most of the text in Alpine, and
31789 "Reverse Color" is used to display highlighted text, such as the
31790 current message in the MESSAGE INDEX.
31792 Lines in the MESSAGE INDEX may also be colored.
31793 Use Setup Rules to get to the Indexcolor configuration screen.
31797 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31799 <End of help on this topic>
31802 ====== h_config_disable_index_locale_dates =====
31805 <TITLE>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></TITLE>
31808 <H1>FEATURE: <!--#echo var="FEAT_disable-index-locale-dates"--></H1>
31810 This feature affects the display of dates in the MESSAGE INDEX.
31811 Normally an attempt is made to localize the dates
31812 used in the MESSAGE INDEX display to your locale.
31813 This is controlled with the
31814 LC_TIME locale setting on a UNIX system.
31815 On Windows the Regional Options control panel may be used to set the date format.
31816 At the programming level, Alpine is using the strftime routine
31817 to print the parts of a date.
31819 If this feature is set, dates are displayed in English and
31820 with the conventions of the United States.
31824 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31826 <End of help on this topic>
31829 ====== h_config_auto_open_unread =====
31832 <TITLE>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></TITLE>
31835 <H1>FEATURE: <!--#echo var="FEAT_auto-open-next-unread"--></H1>
31837 This feature controls the behavior of the TAB key when traversing folders
31839 <A HREF="h_config_enable_incoming">"<!--#echo var="VAR_incoming-folders"-->"</A>
31840 collection or in optional <!--#echo var="VAR_news-collections"-->.
31843 (<A HREF="h_common_nextnew">NextNew</A>)
31844 key is pressed, and there
31845 are no more unseen messages in the current (incoming message or news)
31846 folder, Alpine will search the list of folders in the current collection for
31847 one containing New or Recent (new since the last time the folder was
31849 This behavior may be modified slightly with the
31850 <A HREF="h_config_tab_uses_unseen">"<!--#echo var="FEAT_tab-uses-unseen-for-next-folder"-->"</A>
31851 feature that causes Alpine to look for Unseen messages instead of Recent
31853 Normally, when such a folder is found, Alpine will ask
31854 whether you wish to open the folder. If this feature is set, Alpine will
31855 automatically open the folder without prompting.
31857 This feature also affects some other similar situations.
31859 <A HREF="h_config_thread_index_style"><!--#echo var="VAR_threading-index-style"--></A>
31860 that is equal to one of the "separate-" values, and you are
31861 viewing a thread; then when you type the NextNew command and are at the
31862 end of the current thread you will automatically go to the next thread
31863 if this feature is set.
31864 By default, you would be asked if you want to view the next thread.
31865 You will also be asked at times whether or not you want to view the next
31866 thread after you delete the last message in the thread.
31867 Setting this feature will also cause that question to be skipped.
31871 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31873 <End of help on this topic>
31876 ====== h_config_auto_include_reply =====
31879 <TITLE>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></TITLE>
31882 <H1>FEATURE: <!--#echo var="FEAT_include-text-in-reply"--></H1>
31884 This feature controls an aspect of Alpine's Reply command. Normally, Alpine
31885 will ask whether you wish to include the original message in your reply.
31886 If this feature is set and the feature
31887 <A HREF="h_config_prefix_editing">"<!--#echo var="FEAT_enable-reply-indent-string-editing"-->"</A>
31888 is <EM>not</EM> set, then the original message will be included in the reply
31889 automatically, without prompting.
31891 <End of help on this topic>
31894 ====== h_config_select_in_bold =====
31897 <TITLE>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></TITLE>
31900 <H1>FEATURE: <!--#echo var="FEAT_show-selected-in-boldface"--></H1>
31902 This feature controls an aspect of Alpine's
31903 <A HREF="h_config_enable_agg_ops">"aggregate operation"</A>
31905 particular, the Select and WhereIs commands. Select and WhereIs (with the
31906 ^X subcommand) will search the current folder for messages meeting a
31907 specified criteria, and "tag" the resulting messages with an
31908 "X" in the
31909 first column of the applicable lines in the MESSAGE INDEX. If this feature
31910 is set, instead of using the "X" to denote a selected message,
31912 attempt to display those index lines in boldface. Whether this is
31913 preferable to the "X" will depend on personal taste and the type of
31914 terminal being used.
31917 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31919 <End of help on this topic>
31922 ====== h_config_alt_auth =====
31925 <TITLE>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></TITLE>
31928 <H1>FEATURE: <!--#echo var="FEAT_try-alternative-authentication-driver-first"--></H1>
31930 This feature affects how Alpine connects to IMAP servers.
31931 It's utility has largely been overtaken by events,
31932 but it may still be useful in some circumstances.
31933 If you only connect to modern IMAP servers that support
31934 "TLS" you can ignore this feature.
31940 By default, Alpine will attempt to connect to an IMAP server on the
31941 normal IMAP service port (143), and if the server offers "Transport Layer
31942 Security" (TLS) and Alpine has been compiled with encryption capability,
31943 then a secure (encrypted) session will be negotiated.
31946 With this feature enabled, before connecting on the normal IMAP port, Alpine
31947 will first attempt to connect to an alternate IMAP service port (993) used
31948 specifically for encrypted IMAP sessions via the Secure Sockets Layer
31950 If the SSL attempt fails, Alpine will then try the default
31951 behavior described in the previous paragraph.
31954 TLS negotiation on the normal port is preferred, and supersedes the use of
31955 SSL on port 993, but older servers may not provide TLS support.
31956 This feature may be convenient when accessing IMAP servers that do not support
31957 TLS, but do support SSL connections on port 993.
31958 However, it is important to understand that with this feature enabled,
31959 Alpine will <EM>attempt</EM> to make a secure connection if that is possible,
31960 but it will proceed to make an insecure connection if that is the only
31961 option offered by the server, or if the Alpine in question has been built
31962 without encryption capability.
31965 Note that this feature specifies a per-user (or system-wide) default
31966 behavior, but host/folder specification flags may be used to control the
31967 behavior of any specific connection.
31968 This feature interacts with some of
31969 the possible host/folder path specification flags as follows:
31972 The <SAMP>/tls</SAMP> host flag, for example,
31975 <CENTER><SAMP>{foo.example.com/tls}INBOX</SAMP></CENTER>
31977 will over-ride this feature for the specified host by bypassing the
31978 SSL connection attempt.
31979 Moreover, with <SAMP>/tls</SAMP> specified,
31980 the connection attempt will fail if the
31981 service on port 143 does not offer TLS support.
31984 The <SAMP>/ssl</SAMP> host flag, for example,
31987 <CENTER><SAMP>{foo.example.com/ssl}INBOX</SAMP></CENTER>
31989 will insist on an SSL connection for the specified host,
31990 and will fail if the SSL service on port 993 is not available.
31991 Alpine will not subsequently retry a connection
31992 on port 143 if <SAMP>/ssl</SAMP> is specified.
31996 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
31998 <End of help on this topic>
32001 ====== h_config_file_dir ======
32004 <TITLE>OPTION: File Directory</TITLE>
32007 <H1>OPTION: File Directory</H1>
32011 This value affects the Composer's "^J Attach" command,
32012 the Attachment Index Screen's "S Save" command, and the
32013 Message Index's "E Export" command.
32016 Normally, when a filename is supplied that lacks a leading "path"
32017 component, Alpine assumes the file exists in the user's home directory.
32018 Under Windows operating systems, this definition isn't always clear. This
32019 feature allows you to explictly set where Alpine should look for files
32020 without a leading path.
32023 NOTE: this feature's value is ignored if either
32024 <A HREF="h_config_use_current_dir"><!--#echo var="FEAT_use-current-dir"--></A> feature
32025 is set or the PINERC has a value for the "<!--#echo var="VAR_operating-dir"-->" variable.
32029 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
32031 <End of help on this topic>
32034 ====== h_config_quote_all_froms =====
32037 <TITLE>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></TITLE>
32040 <H1>FEATURE: <!--#echo var="FEAT_save-will-quote-leading-froms"--></H1>
32042 This feature controls an aspect of the Save command (and also the way
32043 outgoing messages are saved to an FCC folder). If set, Alpine will add
32044 a leading ">" character in front of message lines beginning with "From"
32045 when they are saved to another folder, including lines syntactically
32046 distinguishable from the type of message separator line commonly used on
32050 The default behavior is that a ">" will be prepended only to lines
32051 beginning with "From " that might otherwise be confused with a message
32052 separator line on Unix systems. If pine is the only mail program you use,
32053 this default is reasonable. If another program you use has trouble
32054 displaying a message with an unquoted "From " saved by Alpine, you should
32055 enable this feature. This feature only applies to the common Unix mailbox
32056 format that uses message separator lines beginning with "From ". If
32057 Alpine has been configured to use a different mailbox format (possibly
32058 incompatible with other mail programs), then this issue does not arise,
32059 and the feature is irrelevant.
32062 <End of help on this topic>
32065 ====== h_config_normal_color =====
32068 <TITLE>OPTION: Normal Color</TITLE>
32071 <H1>OPTION: Normal Color</H1>
32073 Sets the color Alpine normally uses.
32074 The foreground color is the color of the actual character and the
32075 background color is the color of the area behind the character.
32076 By default this color is black characters on a white background.
32078 <A HREF="h_color_setup">Descriptions of the available commands</A>
32080 Look <A HREF="h_edit_nav_cmds">here</A>
32081 to see the available Editing and Navigation commands.
32083 <End of help on this topic>
32086 ====== h_config_reverse_color =====
32089 <TITLE>OPTION: Reverse Color</TITLE>
32092 <H1>OPTION: Reverse Color</H1>
32094 Sets the color Alpine uses for reverse video characters.
32095 The foreground color is the color of the actual character and the
32096 background color is the color of the area behind the character.
32098 <A HREF="h_color_setup">Descriptions of the available commands</A>
32100 Look <A HREF="h_edit_nav_cmds">here</A>
32101 to see the available Editing and Navigation commands.
32103 <End of help on this topic>
32106 ====== h_config_title_color =====
32109 <TITLE>OPTION: Title Color</TITLE>
32112 <H1>OPTION: Title Color</H1>
32114 Sets the color Alpine uses for the titlebar (the top line on the screen).
32115 The foreground color is the color of the actual character and the
32116 background color is the color of the area behind the character.
32117 By default, the Title Color is black characters on a yellow background.
32119 The actual titlebar color may be different from the Title Color if
32121 <A HREF="h_config_titlebar_color_style">"<!--#echo var="VAR_titlebar-color-style"-->"</A>
32122 is set to some value other than the default.
32123 It may also be different if the current folder is closed and the
32124 <A HREF="h_config_titleclosed_color">Title Closed Color</A>
32125 color is set to something different from the Title Color.
32127 <A HREF="h_color_setup">Descriptions of the available commands</A>
32129 Look <A HREF="h_edit_nav_cmds">here</A>
32130 to see the available Editing and Navigation commands.
32132 <End of help on this topic>
32135 ====== h_config_titleclosed_color =====
32138 <TITLE>OPTION: Title Closed Color</TITLE>
32141 <H1>OPTION: Title Closed Color</H1>
32143 Sets the color Alpine uses for the titlebar (the top line on the screen)
32144 when the current folder is closed.
32145 The foreground color is the color of the actual character and the
32146 background color is the color of the area behind the character.
32147 By default, the Title Color Closed Color is white characters on a red background.
32149 By setting this color to something noticeable you will be alerted to the
32150 fact that the current folder is closed, perhaps unexpectedly.
32152 <End of help on this topic>
32155 ====== h_config_status_color =====
32158 <TITLE>OPTION: Status Color</TITLE>
32161 <H1>OPTION: Status Color</H1>
32163 Sets the color Alpine uses for status messages written to the message
32164 line near the bottom of the screen.
32165 The foreground color is the color of the actual character and the
32166 background color is the color of the area behind the character.
32167 By default, the Status Color is the same as the Reverse Color.
32169 <A HREF="h_color_setup">Descriptions of the available commands</A>
32171 Look <A HREF="h_edit_nav_cmds">here</A>
32172 to see the available Editing and Navigation commands.
32174 <End of help on this topic>
32177 ====== h_config_index_opening_color =====
32180 <TITLE>OPTION: Index Opening Color</TITLE>
32183 <H1>OPTION: Index Opening Color</H1>
32185 With some setups the text of the subject is followed
32186 by the opening text of the message if there is any room available in the index line.
32187 If you have configured your
32188 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
32189 to include one of the Subject tokens that causes this behavior
32190 (SUBJECTTEXT, SUBJKEYTEXT, or SUBJKEYINITTEXT), you may set the color of
32191 this opening text with this option.
32192 This coloring takes place for all but the current index line, and the Opening
32193 Color appears to be in front of any color from an Index Color Rule.
32195 By default the Index Opening Color is gray characters on a white background.
32198 <A HREF="h_color_setup">Descriptions of the available commands</A>
32200 Look <A HREF="h_edit_nav_cmds">here</A>
32201 to see the available Editing and Navigation commands.
32203 <End of help on this topic>
32206 ====== h_config_index_pri_color =====
32209 <TITLE>OPTION: Index Priority Symbol Colors</TITLE>
32212 <H1>OPTION: Index Priority Symbol Colors</H1>
32214 The X-Priority header is a non-standard header that is used in a
32215 somewhat standard way by many mail programs.
32216 Alpine expects the value of this header to be a digit with a value
32217 from 1 to 5, with 1 being the highest priority and 5 the lowest priority.
32218 Alpine can be made to display an indication of this priority in
32219 messages by use of one of the tokens
32220 (<A HREF="h_index_tokens">Tokens for Index and Replying</A>)
32221 PRIORITY, PRIORITYALPHA, or PRIORITY! in the
32222 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32225 You may set the color used to draw these tokens by use of the colors
32226 Index High Priority Symbol Color and Index Low Priority Symbol Color.
32227 This coloring takes place for all but the current index line, and the Priority
32228 Color appears to be in front of any color from an Index Color Rule.
32229 If the priority has a value of 1 or 2 the High Priority color will be
32231 and if the value is 4 or 5 the Low Priority color will be used.
32233 If you don't set these colors the index line will be colored in the same color as
32234 the bulk of the index line.
32237 <A HREF="h_color_setup">Descriptions of the available commands</A>
32239 Look <A HREF="h_edit_nav_cmds">here</A>
32240 to see the available Editing and Navigation commands.
32242 <End of help on this topic>
32245 ====== h_config_index_subject_color =====
32248 <TITLE>OPTION: Index Subject Color</TITLE>
32251 <H1>OPTION: Index Subject Color</H1>
32253 You may set the color used to draw the Subject part of the index line.
32254 This coloring takes place for all but the current index line, and the Subject
32255 Color appears to be in front of any color from an Index Color Rule.
32257 If you don't set this color it will be colored in the same color as
32258 the bulk of the index line.
32261 <A HREF="h_color_setup">Descriptions of the available commands</A>
32263 Look <A HREF="h_edit_nav_cmds">here</A>
32264 to see the available Editing and Navigation commands.
32266 <End of help on this topic>
32269 ====== h_config_index_from_color =====
32272 <TITLE>OPTION: Index From Color</TITLE>
32275 <H1>OPTION: Index From Color</H1>
32277 You may set the color used to draw the From part of the index line.
32278 This coloring takes place for all but the current index line, and the From
32279 Color appears to be in front of any color from an Index Color Rule.
32281 If you don't set this color it will be colored in the same color as
32282 the bulk of the index line.
32285 <A HREF="h_color_setup">Descriptions of the available commands</A>
32287 Look <A HREF="h_edit_nav_cmds">here</A>
32288 to see the available Editing and Navigation commands.
32290 <End of help on this topic>
32293 ====== h_config_index_arrow_color =====
32296 <TITLE>OPTION: Index Arrow Color</TITLE>
32299 <H1>OPTION: Index Arrow Color</H1>
32301 If you have configured your
32302 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option
32303 to include the "ARROW" token, you may set the color of
32304 the arrow displayed with this option.
32305 If you don't set the color it will be colored in the same color as
32306 the bulk of the index line.
32309 <A HREF="h_color_setup">Descriptions of the available commands</A>
32311 Look <A HREF="h_edit_nav_cmds">here</A>
32312 to see the available Editing and Navigation commands.
32314 <End of help on this topic>
32317 ====== h_config_index_color =====
32320 <TITLE>OPTION: Index Colors</TITLE>
32323 <H1>OPTION: Index Colors</H1>
32325 You may add color to the single character symbols that give the status
32326 of each message in the MESSAGE INDEX.
32327 By default the characters "+", "*", "D",
32328 "A", and "N" show up near the left hand side of the
32329 screen depending on whether the message is addressed to you, and whether
32330 the message is marked Important, is Deleted, is Answered, or is New.
32331 The color for each of those characters may be specified by setting the
32332 "Index-to-me" Symbol Color,
32333 the "Index-important" Symbol Color,
32334 the "Index-deleted" Symbol Color,
32335 the "Index-answered" Symbol Color,
32336 and the "Index-new" Symbol Color.
32337 There are also two other symbol colors called "Index-recent"
32338 and "Index-unseen".
32339 These two colors will only be used if you have configured your
32340 "<A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A>" option
32341 to include the "IMAPSTATUS" or "SHORTIMAPSTATUS" token.
32343 The default colors for these symbols are:
32345 <TR> <TD> Index-to-me </TD> <TD> black on cyan </TD> </TR>
32346 <TR> <TD> Index-important </TD> <TD> white on bright red </TD> </TR>
32347 <TR> <TD> Index-deleted </TD> <TD> same as Normal Color </TD> </TR>
32348 <TR> <TD> Index-answered </TD> <TD> bright red on yellow </TD> </TR>
32349 <TR> <TD> Index-new </TD> <TD> white on magenta </TD> </TR>
32350 <TR> <TD> Index-recent </TD> <TD> same as Normal Color </TD> </TR>
32351 <TR> <TD> Index-unseen </TD> <TD> same as Normal Color </TD> </TR>
32354 Besides coloring the message status symbols, you may also color the
32356 This is done by using the
32357 <A HREF="h_rules_incols">SETUP INDEX LINE COLORS</A> screen, which you
32358 may get to with the commands <EM>S</EM>etup/<EM>R</EM>ules/<EM>I</EM>ndexcolor.
32359 When the entire line is colored that color will be "behind" the
32360 status symbol colors talked about in the paragraph above.
32363 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
32364 in the index using the
32365 Setup/Kolor screen (<A HREF="h_config_kw_color">Keyword Colors</A>);
32366 the <A HREF="h_config_index_arrow_color">ARROW</A> cursor;
32368 <A HREF="h_config_index_subject_color">Index Subject Color</A>;
32369 the From field using
32370 <A HREF="h_config_index_from_color">Index From Color</A>;
32372 <A HREF="h_config_index_opening_color">Index Opening</A> text.
32374 <A HREF="h_color_setup">Descriptions of the available commands</A>
32376 Look <A HREF="h_edit_nav_cmds">here</A>
32377 to see the available Editing and Navigation commands.
32379 <End of help on this topic>
32382 ====== h_config_metamsg_color =====
32385 <TITLE>OPTION: Meta-Message Color</TITLE>
32388 <H1>OPTION: Meta-Message Color</H1>
32390 Sets the color Alpine uses in the MESSAGE TEXT screen for messages to you
32391 that aren't part of the message itself.
32392 For example, an attachment that isn't shown might produce a meta
32393 message something like:
32395 <CENTER><SAMP> [ Part 2, "comment" Text/PLAIN (Name: "file") ]</SAMP></CENTER>
32398 <A HREF="h_config_quote_suppression"><!--#echo var="VAR_quote-suppression-threshold"--></A>
32399 option you might see
32401 <CENTER><SAMP>[ 12 lines of quoted text hidden from view ]</SAMP></CENTER>
32403 Warnings about suspicious looking URLs in HTML will also be colored
32406 The foreground color is the color of the actual character and the
32407 background color is the color of the area behind the character.
32408 By default, the Meta-Message Color is black characters on a yellow background.
32410 <A HREF="h_color_setup">Descriptions of the available commands</A>
32412 Look <A HREF="h_edit_nav_cmds">here</A>
32413 to see the available Editing and Navigation commands.
32415 <End of help on this topic>
32418 ====== h_config_keylabel_color =====
32421 <TITLE>OPTION: KeyLabel Color</TITLE>
32424 <H1>OPTION: KeyLabel Color</H1>
32426 Sets the color Alpine uses for the labels of the keys in the two-line
32427 menu at the bottom of the screen.
32428 For example, some of the screens have a "P PrevMsg" command.
32429 This option sets the color used when displaying "PrevMsg".
32430 The foreground color is the color of the actual character and the
32431 background color is the color of the area behind the character.
32432 By default, the KeyLabel Color is the same as the Normal Color.
32434 WARNING: Some terminal emulators have the property that the screen will scroll
32435 down one line whenever a character is written to the character cell in the
32436 lower right corner of the screen.
32437 Alpine can usually avoid writing a character in that corner of the screen.
32438 However, if you have defined a KeyLabel Color then Alpine does have to write
32439 a character in that cell in order to color the cell correctly.
32440 If you find that your display sometimes scrolls up a line this could be
32442 The most obvious symptom is probably that the titlebar at the top of the
32443 screen scrolls off the screen.
32444 Try setting KeyLabel Color to Default to see if that fixes the problem.
32446 <A HREF="h_color_setup">Descriptions of the available commands</A>
32448 Look <A HREF="h_edit_nav_cmds">here</A>
32449 to see the available Editing and Navigation commands.
32451 <End of help on this topic>
32454 ====== h_config_keyname_color =====
32457 <TITLE>OPTION: KeyName Color</TITLE>
32460 <H1>OPTION: KeyName Color</H1>
32462 Sets the color Alpine uses for the names of the keys in the two-line
32463 menu at the bottom of the screen.
32464 For example, some of the screens have a "P PrevMsg" command.
32465 This option sets the color used when displaying the "P".
32466 The foreground color is the color of the actual character and the
32467 background color is the color of the area behind the character.
32468 By default, the KeyName Color is the same as the Reverse Color.
32470 <A HREF="h_color_setup">Descriptions of the available commands</A>
32472 Look <A HREF="h_edit_nav_cmds">here</A>
32473 to see the available Editing and Navigation commands.
32475 <End of help on this topic>
32478 ====== h_config_slctbl_color =====
32481 <TITLE>OPTION: Selectable Item Color</TITLE>
32484 <H1>OPTION: Selectable Item Color</H1>
32486 Sets the color Alpine uses for selectable items, such as URLs.
32487 The foreground color is the color of the actual character and the
32488 background color is the color of the area behind the character.
32489 By default, the Selectable Item Color is the same as the Normal Color,
32490 except that it is bold.
32492 <A HREF="h_color_setup">Descriptions of the available commands</A>
32494 Look <A HREF="h_edit_nav_cmds">here</A>
32495 to see the available Editing and Navigation commands.
32497 <End of help on this topic>
32500 ====== h_config_quote_color =====
32503 <TITLE>OPTION: Quote Colors</TITLE>
32506 <H1>OPTION: Quote Colors</H1>
32508 Sets the colors Alpine uses for coloring quoted text in the MESSAGE TEXT
32510 If a line begins with a > character (or space followed by >)
32511 it is considered a quote.
32512 That line will be given the Quote1 Color (first level quote).
32513 If there is a second level of quoting then the Quote2 Color will be used.
32514 Alpine considers there to be a second level of quoting if that first > is
32515 followed by another > (or space followed by >).
32516 If there are characters other than whitespace and > signs, then it isn't
32517 considered another level of quoting.
32518 Similarly, if there is a third level of quoting the Quote3 Color will be
32520 If there are more levels after that the Quote Colors are re-used.
32521 If you define all three colors then it would repeat like Color1, Color2, Color3,
32522 Color1, Color2, Color3, ...
32523 If you only define the first two it would be
32524 Color1, Color2, Color1, Color2, ...
32525 If you define only the Quote1 Color, then the entire quote would be that
32526 color regardless of the quoting levels.
32527 By default, the Quote1 Color is black characters on a greenish-blue background;
32528 the Quote2 Color is black characters on a dull yellow background; and
32529 the Quote3 Color is black characters on a green background.
32531 <A HREF="h_color_setup">Descriptions of the available commands</A>
32533 Look <A HREF="h_edit_nav_cmds">here</A>
32534 to see the available Editing and Navigation commands.
32536 <End of help on this topic>
32539 ====== h_config_folder_color =====
32542 <TITLE>OPTION: Folder Color</TITLE>
32545 <H1>OPTION: Folder Color</H1>
32547 Sets the colors Alpine uses for coloring a folder in the FOLDER LIST
32548 screen. By default, the Folder Color is the normal text color.
32551 If you set a color for this feature, other than the normal color
32552 (the default), or a color for
32553 <A HREF="h_config_directory_color">Directory Color</A>, then directories
32554 will be colored according to the color specified in the
32555 <A HREF="h_config_directory_color">Directory Color</A> option. In this
32556 case, the color will be the only indication that the colored name
32557 refers to a directory. The normal behavior is that Alpine
32558 indicates that a name refers to a directory by appending a
32559 separator (like "/" or ".") to the name of
32563 If a folder is a directory, then the folder name will be painted
32564 according to the color defined by this variable, and a separator
32565 indicator (like "/" or ".") will be added
32567 indicator will be painted according to the color defined in the
32568 <A HREF="h_config_directory_color">Directory Color</A> option.
32571 <End of help on this topic>
32574 ====== h_config_directory_color =====
32577 <TITLE>OPTION: Directory Color</TITLE>
32580 <H1>OPTION: Directory Color</H1>
32582 Sets the colors Alpine uses for coloring a directory in the FOLDER LIST
32583 screen. By default, the Folder Color is the normal text color.
32585 If you set a color for this feature, other than the normal color
32586 (the default), or a color for
32587 <A HREF="h_config_folder_color">Folder Color</A>, then folders
32588 will be colored according to the color specified in the
32589 <A HREF="h_config_folder_color">Folder Color</A> option. In this
32590 case, the color will be the only indication that the colored name
32591 refers to a directory. The normal behavior is that Alpine
32592 indicates that a name refers to a directory by appending a
32593 separator (like "/" or ".") to the name of
32596 If a folder is a directory, then the folder name will be painted
32597 according to the color defined by the option
32598 <A HREF="h_config_folder_color">Folder Color</A>, and the separator
32599 indicator (like "/" or ".") will be added
32600 after the name. That
32601 indicator will be painted according to the color defined in this
32604 <End of help on this topic>
32607 ====== h_config_folder_list_color =====
32610 <TITLE>OPTION: Folder-List Color</TITLE>
32613 <H1>OPTION: Folder-List Color</H1>
32615 Sets the colors Alpine uses for coloring normal text in the FOLDER LIST
32616 screen. By default, the Folder-List Color is the normal text color.
32618 This text refers to the informative text that Alpine displays so you
32619 can recognize each collection. The color of the content of each collection
32620 is determined by the options <A HREF="h_config_folder_color">Folder Color</A>
32621 and <A HREF="h_config_directory_color">Directory Color</A>.
32624 <A HREF="h_config_folder_color">Folder Color</A>
32625 and <A HREF="h_config_directory_color">Directory Color</A>, configuring
32626 this option does not affect the way that Alpine reports folders,
32627 directories and folders that are directories.
32629 <End of help on this topic>
32632 ====== h_config_incunseen_color =====
32635 <TITLE>OPTION: Incoming Unseen Color</TITLE>
32638 <H1>OPTION: Incoming Unseen Color</H1>
32641 <A HREF="h_config_enable_incoming_checking"><!--#echo var="FEAT_enable-incoming-folders-checking"--></A>
32642 is turned on it is possible to highlight the folders that contain
32643 unseen messages by coloring them with this color.
32644 By default, this is the same as the Normal Color and no highlighting is done.
32646 Usually the "current" folder (the folder the cursor is on)
32647 is highlighted using reverse video.
32648 If the current folder is colored because it contains unseen messages then
32649 the color used to show that it is also the current folder is controlled
32651 <A HREF="h_config_index_color_style"><!--#echo var="VAR_current-indexline-style"--></A>
32652 feature at the top of the SETUP COLOR screen.
32654 <A HREF="h_color_setup">Descriptions of the available commands</A>
32656 Look <A HREF="h_edit_nav_cmds">here</A>
32657 to see the available Editing and Navigation commands.
32659 <End of help on this topic>
32662 ====== h_config_signature_color =====
32665 <TITLE>OPTION: Signature Color</TITLE>
32668 <H1>OPTION: Signature Color</H1>
32670 Sets the color Alpine uses for coloring the signature in the MESSAGE TEXT
32671 screen. According to USENET conventions, the signature is defined as the
32672 paragraph following the "sigdashes", that is, the special line
32673 consisting of the three characters
32674 "-- " (i.e., dash, dash, and space). Alpine allows for one
32675 empty line right after the sigdashes to be considered as part of the
32677 By default, the Signature Color is blue characters on a white background.
32679 <A HREF="h_color_setup">Descriptions of the available commands</A>
32681 Look <A HREF="h_edit_nav_cmds">here</A>
32682 to see the available Editing and Navigation commands.
32684 <End of help on this topic>
32687 ====== h_config_prompt_color =====
32690 <TITLE>OPTION: Prompt Color</TITLE>
32693 <H1>OPTION: Prompt Color</H1>
32695 Sets the color Alpine uses for confirmation prompts and questions that
32696 appear in the status line near the bottom of the screen.
32697 The foreground color is the color of the actual character and the
32698 background color is the color of the area behind the character.
32699 By default, the Prompt Color is the same as the Reverse Color.
32701 <A HREF="h_color_setup">Descriptions of the available commands</A>
32703 Look <A HREF="h_edit_nav_cmds">here</A>
32704 to see the available Editing and Navigation commands.
32706 <End of help on this topic>
32709 ====== h_config_header_general_color =====
32712 <TITLE>OPTION: Header General Color</TITLE>
32715 <H1>OPTION: Header General Color</H1>
32717 Sets the color Alpine uses for the headers of a message in the MESSAGE TEXT
32719 The foreground color is the color of the actual character and the
32720 background color is the color of the area behind the character.
32721 By default, this is the same as the Normal Color.
32723 It is also possible to set the colors for specific header fields, for
32724 example the Subject, using
32725 <A HREF="h_config_customhdr_color"><!--#echo var="VAR_viewer-hdr-colors"--></A>.
32726 If both a Header General Color and a specific Viewer Header Color are set
32727 the specific color will override the general color, as you would expect.
32729 <A HREF="h_color_setup">Descriptions of the available commands</A>
32731 Look <A HREF="h_edit_nav_cmds">here</A>
32732 to see the available Editing and Navigation commands.
32734 <End of help on this topic>
32737 ====== h_config_incol =====
32740 <TITLE>Index Line Color</TITLE>
32743 <H1>Index Line Color</H1>
32745 This option is used to set the color of a line in the index when the
32746 message for that line matches the Pattern.
32747 This colors the whole index line, except possibly the status letters,
32748 which may be colored separately using the
32749 <A HREF="h_color_setup">Setup Kolor</A> screen.
32750 The foreground color is the color of the actual characters and the
32751 background color is the color of the area behind the characters.
32753 <A HREF="h_color_setup">Descriptions of the available commands</A>
32755 Look <A HREF="h_edit_nav_cmds">here</A>
32756 to see the available Editing and Navigation commands.
32758 <End of help on this topic>
32761 ====== h_config_usetransparent_color =====
32764 <TITLE>OPTION: Use Transparent Color</TITLE>
32767 <H1>OPTION: Use Transparent Color</H1>
32769 This is a special color supported by some terminal emulators.
32770 It is intended to result in the default foreground or background color
32771 from the terminal emulator.
32772 This is the color the terminal was displaying characters in before you started Alpine.
32773 The reason it is called Transparent is because you could set the foreground color
32774 to some specific color, like Red, and then set the background color to the
32775 Transparent Color. If it works as expected, the background color from the terminal
32776 window in which Alpine is running will show through but with the Red characters
32779 <A HREF="h_color_setup">Descriptions of the available commands</A>
32781 Look <A HREF="h_edit_nav_cmds">here</A>
32782 to see the available Editing and Navigation commands.
32784 <End of help on this topic>
32787 ====== h_config_usenormal_color =====
32790 <TITLE>OPTION: Use Normal Color</TITLE>
32793 <H1>OPTION: Use Normal Color</H1>
32795 When you use this color value, the actual color used will be the same
32796 as the corresponding Normal Color.
32797 For example if your Normal Color is black on white and you set both
32798 the foreground and background colors here to use the Normal Color, you'll
32799 get black on white. If you later change the Normal Color to red on blue
32800 this color will also change to red on blue.
32802 <A HREF="h_color_setup">Descriptions of the available commands</A>
32804 Look <A HREF="h_edit_nav_cmds">here</A>
32805 to see the available Editing and Navigation commands.
32807 <End of help on this topic>
32810 ====== h_config_usenone_color =====
32813 <TITLE>OPTION: Use None Color</TITLE>
32816 <H1>OPTION: Use None Color</H1>
32818 This is a special color that simply means to leave the color alone.
32819 It is useful for Index symbols and for Keyword Colors used in the Subject
32820 field of an index line.
32821 The most likely use is to set an explicit foreground color and then set
32822 the background color to the None Color.
32823 That will cause the symbol or keyword to be drawn in the foreground color
32824 with a background equal to whatever color the rest of the index line is already
32826 You will see no visible effect unless you have assigned Indexcolor Rules to
32827 color index lines or you have set an actual color for the Reverse Color.
32829 <A HREF="h_color_setup">Descriptions of the available commands</A>
32831 Look <A HREF="h_edit_nav_cmds">here</A>
32832 to see the available Editing and Navigation commands.
32834 <End of help on this topic>
32837 ====== h_config_dflt_color =====
32840 <TITLE>OPTION: Default Color</TITLE>
32843 <H1>OPTION: Default Color</H1>
32845 Setting default will cause the color to be the default color.
32846 Unsetting default is normally done by choosing a color, but in some cases
32847 you may want to declare the current default color to be your non-default
32849 For example, the default Keyname Color is the same as the Reverse Color.
32850 Whenever the Reverse Color changes the Keyname Color will also change, unless
32851 you've changed it or unset the default box.
32853 <A HREF="h_color_setup">Descriptions of the available commands</A>
32855 Look <A HREF="h_edit_nav_cmds">here</A>
32856 to see the available Editing and Navigation commands.
32858 <End of help on this topic>
32861 ====== h_config_bold_slctbl =====
32864 <TITLE>OPTION: Bold</TITLE>
32867 <H1>OPTION: Bold</H1>
32869 The color for this particular section may have the Bold attribute turned
32871 Setting bold will cause the characters to be bold.
32873 <A HREF="h_color_setup">Descriptions of the available commands</A>
32875 Look <A HREF="h_edit_nav_cmds">here</A>
32876 to see the available Editing and Navigation commands.
32878 <End of help on this topic>
32881 ====== h_config_kw_color =====
32884 <TITLE>OPTION: Keyword Colors</TITLE>
32887 <H1>OPTION: Keyword Colors</H1>
32889 Sets the colors Alpine uses for Keyword fields in the MESSAGE INDEX screen.
32890 Keywords are displayed as part of the Subject by default.
32891 They are also displayed as part of the Subject if the tokens
32892 "SUBJKEY", "SUBJKEYTEXT", "SUBJKEYINIT", or "SUBJKEYINITTEXT" are used in the
32893 <A HREF="h_config_index_format"><!--#echo var="VAR_index-format"--></A> option.
32894 Keywords may also be displayed in a column of their own in the MESSAGE INDEX
32895 screen by using the "KEY" or "KEYINIT" tokens.
32897 For example, you might have set up a Keyword
32898 "Work" using the
32899 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A> option in the Setup/Config screen.
32900 You could cause that Keyword to show up as a special color
32901 by setting up the Keyword Color using this option, and then including it
32902 in the MESSAGE INDEX screen using one of the tokens listed above in the
32903 <!--#echo var="VAR_index-format"-->.
32905 <A HREF="h_color_setup">Descriptions of the available commands</A>
32907 Look <A HREF="h_edit_nav_cmds">here</A>
32908 to see the available Editing and Navigation commands.
32910 <End of help on this topic>
32913 ====== h_config_customhdr_color =====
32916 <TITLE>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></TITLE>
32919 <H1>OPTION: <!--#echo var="VAR_viewer-hdr-colors"--></H1>
32921 Sets the colors Alpine uses for specific header fields in the MESSAGE TEXT screen.
32922 For example, you may set the color of the Subject header or the From header.
32923 The foreground color is the color of the actual character and the
32924 background color is the color of the area behind the character.
32926 In addition to setting the colors for particular headers (like the Subject)
32927 you may also set a color to be used for all headers unless overridden by a
32928 more specific Viewer Header Color.
32930 <A HREF="h_config_header_general_color">Header General Color</A>.
32933 there is an additional line on the
32934 screen labeled "Pattern to match".
32935 If you leave that blank, then the whole field for that header will
32937 However, if you give a pattern to match, the coloring will only take place
32938 if there is a match for that pattern in the value of the field.
32939 For example, if you are working on a color for the Subject header and
32940 you fill in a pattern of "important", then only Subjects that
32941 contain the word "important" will be colored.
32943 If the pattern you enter is a comma-separated list of patterns, then coloring
32944 happens if any of those patterns matches.
32946 <A HREF="h_color_setup">Descriptions of the available commands</A>
32948 Look <A HREF="h_edit_nav_cmds">here</A>
32949 to see the available Editing and Navigation commands.
32951 <End of help on this topic>
32954 ====== h_config_indextoken_color =====
32957 <TITLE>OPTION: <!--#echo var="VAR_index-token-colors"--></TITLE>
32960 <H1>OPTION: <!--#echo var="VAR_index-token-colors"--></H1>
32962 This option allows you to set up the color in which any token, not specified by the
32963 previous options, will be colored in the MESSAGE INDEX screen.
32965 In order to use this option, you must press the "I" <B>IndxHdr</B> command, and add
32966 a token that can be used in the index format.
32967 The list of available tokens is <A HREF="h_index_tokens">here</A>.
32969 If you fail to enter a valid token your entry will be ignored, and you will be asked to
32970 enter a new one. Once you have entered a valid token, a line will be added to the
32971 configuration screen that you can use to set up the colors in which that token will
32972 be painted. This is done in the same way that you configure colors for other
32975 <A HREF="h_color_setup">Descriptions of the available commands</A>
32977 Look <A HREF="h_edit_nav_cmds">here</A>
32978 to see the available Editing and Navigation commands.
32980 <End of help on this topic>
32983 ====== h_config_customhdr_pattern =====
32986 <TITLE>OPTION: Viewer Header Color Pattern</TITLE>
32989 <H1>OPTION: Viewer Header Color Pattern</H1>
32991 If you leave this blank, then the whole field for the header will
32993 If you give a pattern to match, the coloring will only take place
32994 if there is a match for that pattern in the value of the field.
32995 For example, if you are working on a color for the Subject header and
32996 you fill in a pattern of "important", then only Subjects that
32997 contain the word "important" will be colored.
32999 For address headers (like From and To) and for the Newsgroups header,
33000 a pattern match will cause only the matched addresses or newsgroups to be
33002 If there is no pattern to match, then all of the addresses or newsgroups
33003 in the relevant header will be colored.
33005 The matching pattern may be a comma-separated list of patterns to match
33006 instead of a single pattern.
33007 For example, you could use the pattern "important,urgent" which would
33008 cause a match if either the word "important" or the word
33009 "urgent" appeared in the value of the header.
33010 You could list several comma-separated email addresses in the Header
33011 From Color pattern so that those addresses will be colored when any of
33012 them appear in the From header.
33014 To add a new matching pattern or change the existing pattern use the
33015 <!--chtml if pinemode="function_key"-->
33020 "Change" command that is available when the "Pattern to
33021 match" line is highlighted.
33023 <!--chtml if pinemode="function_key"-->
33028 "Delete" command may be used to quickly remove all patterns
33029 for a particular header.
33031 <End of help on this topic>
33034 ====== h_color_setup =====
33037 <TITLE>SETUP COLOR COMMANDS</TITLE>
33040 <H1>SETUP COLOR COMMANDS</H1>
33041 <!--chtml if pinemode="function_key"-->
33043 Available Commands -- Group 1
33044 -------------------------------
33045 F1 Display this help text
33046 F2 Show other available commands
33047 F3 Exit to MAIN MENU
33048 F4 Select the highlighted foreground or background color
33049 F5 Move to previous line
33050 F6 Move to next line
33053 F9 Add a config section for a header field
33054 F10 Restore all default colors (for all sections)
33055 F11 Print color configuration screen
33056 F12 Whereis (search for word)
33058 Available Commands -- Group 2
33059 -------------------------------
33060 F1 Display this help text
33061 F2 Show other available commands
33062 F5 Delete config section for highlighted header field
33063 F6 Shuffle the order of Header Color sections
33068 -------------------------------------------------
33069 ? Display this help text E Exit back to MAIN MENU
33070 P Previous Line N Next Line
33071 - Previous page Spc (space bar) Next page
33072 W WhereIs (search for word) % Print color configuration screen
33074 Color Setup Commands
33075 ------------------------------------------------
33076 * Select the highlighted foreground or background color
33077 A Add a config section for a header field
33078 D Delete config section for highlighted header field
33079 R Restore all default colors (for all sections)
33080 $ Shuffle the order of Header Color sections
33084 <H2>Description of the Setup Color Screen</H2>
33086 From this screen you may turn on color and set the colors of
33087 various parts of the Alpine display.
33088 For help on turning on color move your cursor into the Color Style section
33089 at the top of the Setup Color screen and ask for help.
33092 There are several sections in the Setup Color Screen.
33093 At the top are some settings that handle the style of color used
33094 with your terminal emulator (UNIX only), and some settings that
33095 control how the current indexline and the titlebar are colored.
33096 After that comes a long section called GENERAL COLORS that allows
33097 you to set the color of many elements in the Alpine screens.
33098 For example, the color of the titlebar, status messages,
33099 selectable links, quotes and signatures in messages, and so on.
33100 After that is a section called INDEX COLORS that allows you to
33101 set the colors of various pieces of the displayed index lines in
33102 the MESSAGE INDEX screen.
33103 The next section is HEADER COLORS. This is for coloring headers of
33104 messages in the MESSAGE TEXT screen in just about any way you would like.
33105 Finally, the KEYWORD COLORS section allows you to highlight
33106 <A HREF="h_config_keywords"><!--#echo var="VAR_keywords"--></A>
33107 in the MESSAGE INDEX screen.
33110 To change a color, highlight the color you want to change (for example,
33111 the Status Color) by moving
33112 the cursor into it.
33113 You may want to read the help text for the color to see a brief desription
33114 of what you are coloring.
33115 Then press "C" for Change to set the color to something new.
33116 That will put you into a screen with two columns of colors, one for
33117 the foreground color and one for the background color.
33118 The foreground color is just the color you want the actual characters
33119 to be and the background color is the color of the rest of the rectangle
33120 behind the characters.
33121 Select the foreground and background colors desired by using the Next and
33122 Prev keys to highlight the color, and the * command to select it.
33124 To set a color to its default value, set the X in the Default line at
33125 the bottom of the list of colors.
33128 The HEADER COLORS section is a little bit different from the others.
33129 Besides coloring the specific fields that Alpine knows about, you may also
33130 color specific header fields when viewing a message in the MESSAGE TEXT
33132 For example, you may color the Subject header a particular color.
33133 There are a few commands for use with headers.
33134 The "AddHeader" command adds a section to the color
33135 configuration screen that allows you to set the color for that header.
33136 You'll be asked for the name of the header field you want to color.
33137 If you wanted to color the Subject, you would answer
33138 with the word "subject".
33139 Once you've added a header field, the color setting works just like the
33140 other color fields, except that there is an additional line on the
33141 configuration screen labeled "Pattern to match".
33142 If you leave that blank, then the whole field for that header will always
33144 However, if you give a pattern to match, the coloring will only take place
33145 if there is a match for that pattern in the value of the field.
33146 For example, if you are working on a color for the Subject header and
33147 you fill in a pattern of "important", then only Subjects that
33148 contain the word "important" will be colored.
33150 The "DeleteHdr" command removes a header section from the
33151 configuration altogether.
33152 The "Shuffle" command changes the order of header sections.
33153 This is only necessary if you use header sections with pattern fields.
33154 For example, if you have two Subject sections, one with one pattern and
33155 another with another pattern, and the subject for a particular message
33156 happens to match both, then the color from the first match is used.
33159 The command "RestoreDefs" will restore all of the default colors.
33160 Each section will change to the default value used for that section when
33161 color is first enabled.
33162 When you restore all default colors the color settings for the Header Colors
33163 will be unset (since that's the default), but the header fields you've
33164 added will remain so that you may easily reset them.
33165 In order to get rid of them completely you'd have to use
33166 the "DeleteHdr" command.
33169 Remember that <A HREF="h_rules_incols">Index Line Colors</A>
33170 may be set with matching rules and that is configured separately from
33171 the rest of the color settings described here.
33172 It is configured in the Setup/Rules/Indexcolors section of the configuration screen
33173 instead of in the Setup/Kolor section.
33176 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33178 <End of help on this topic>
33181 ====== h_config_news_uses_recent ======
33184 <TITLE>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></TITLE>
33187 <H1>FEATURE: <!--#echo var="FEAT_news-approximates-new-status"--></H1>
33189 This feature causes certain messages to be marked as "New" in the
33190 MESSAGE INDEX of newsgroups.
33191 This feature is set by default.
33195 When opening a newsgroup, Alpine will consult your "newsrc" file and
33196 determine the last message you have previously disposed of via the "D"
33197 key. If this feature is set, any subsequent messages will be shown in the
33198 Index with an "N", and the first of these messages will be highlighted.
33199 Although this is only an approximation of true "New" or "Unseen"
33200 status, it provides a useful cue to distinguish more-or-less recent
33201 messages from those you have seen previously, but are not yet ready to
33206 Background: your "newsrc" file (used to store message status information
33207 for newsgroups) is only capable of storing a single flag, and Alpine uses
33208 this to record whether or not you are "done with" a message, as
33209 indicated by marking the message as "Deleted". Unfortunately, this
33210 means that Alpine has no way to record exactly which messages you have
33211 previously seen, so it normally does not show the "N" status flag for
33212 any messages in a newsgroup. This feature enables a starting
33213 *approximation* of seen/unseen status that may be useful.
33215 <End of help on this topic>
33218 ====== h_config_expose_hidden_config =====
33221 <TITLE>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></TITLE>
33224 <H1>FEATURE: <!--#echo var="FEAT_expose-hidden-config"--></H1>
33226 If set, this causes configuration options and features that are normally
33227 hidden from view to be editable in the Setup/Config screen.
33230 The purpose of this feature is to allow you to change configuration
33231 features and variables that are normally hidden.
33232 This is particularly useful if you are using a remote configuration,
33233 where it is difficult to edit the contents manually, but it may also be used
33234 on a local pinerc configuration file.
33236 If set, several configuration variables and features that are normally
33237 hidden from view will show up in the Setup/Configuration screen.
33238 They will be at the bottom of the configuration screen.
33239 You can find them by searching for the words "hidden configuration".
33242 Note that this is an advanced feature that should be used with care.
33243 The reason that this part of the configuration is normally hidden is because
33244 there is a significant potential for causing problems if you change these
33246 If something breaks after a change try changing it back to see if that is
33247 what is causing the problem.
33248 There are also some variables that are normally hidden because they are
33249 manipulated through Alpine in other ways.
33250 For example, colors are normally set using the Setup/Kolors screen and
33251 the "<!--#echo var="VAR_address-book"-->" variable is normally set using
33252 the Setup/AddressBooks screen, so there is little reason to edit these directly.
33253 The "<!--#echo var="VAR_incoming-folders"-->" variable is normally changed by using
33254 the Add, Delete, and Rename commands in the FOLDER LIST screen,
33255 and the "<!--#echo var="VAR_last-time-prune-questioned"-->" variable is normally used
33256 internally by Alpine and not set directly by the user.
33259 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33261 <End of help on this topic>
33264 ====== h_config_disable_signature_edit =====
33267 <TITLE>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></TITLE>
33270 <H1>FEATURE: <!--#echo var="FEAT_disable-signature-edit-cmd"--></H1>
33272 If set, this disables the editing of signature files from within
33273 the Setup/Config screen.
33276 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33278 <End of help on this topic>
33281 ====== h_config_disable_roles_templateedit =====
33284 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></TITLE>
33287 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-template-edit"--></H1>
33289 If set, this disables the editing of template files within the
33293 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33295 <End of help on this topic>
33298 ====== h_config_disable_roles_sigedit =====
33301 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></TITLE>
33304 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-sig-edit"--></H1>
33306 If set, this disables the editing of signature files within the
33310 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33312 <End of help on this topic>
33315 ====== h_config_disable_roles_setup =====
33318 <TITLE>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></TITLE>
33321 <H1>FEATURE: <!--#echo var="FEAT_disable-roles-setup-cmd"--></H1>
33323 If set, this disables the Setup/Rules/Roles command.
33326 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33328 <End of help on this topic>
33331 ====== h_config_disable_pipes_in_templates =====
33334 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></TITLE>
33337 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-templates"--></H1>
33339 By default, if a template file name is followed by a vertical bar (|) then
33340 that causes the file to be executed to produce the text for the template.
33341 If this feature is set, then this is not allowed.
33344 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33346 <End of help on this topic>
33349 ====== h_config_disable_pipes_in_sigs =====
33352 <TITLE>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></TITLE>
33355 <H1>FEATURE: <!--#echo var="FEAT_disable-pipes-in-sigs"--></H1>
33357 By default, if a signature file name is followed by a vertical bar (|) then
33358 that causes the file to be executed to produce the text for the signature.
33359 If this feature is set, then this is not allowed.
33362 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33364 <End of help on this topic>
33367 ====== h_config_disable_password_cmd =====
33370 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></TITLE>
33373 <H1>FEATURE: <!--#echo var="FEAT_disable-password-cmd"--></H1>
33375 If set, then the Setup/Newpassword command is disabled.
33378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33380 <End of help on this topic>
33383 ====== h_config_disable_password_caching =====
33386 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></TITLE>
33389 <H1>FEATURE: <!--#echo var="FEAT_disable-password-caching"--></H1>
33391 Normally, loginname/password combinations are cached in Alpine so that
33392 you do not have to enter the same password more than once in a session.
33393 A disadvantage to this approach is that the password must be stored in
33394 the memory image of the running Alpine in order that it can be re-used.
33395 In the event that Alpine crashes and produces a core dump, and that core
33396 dump is readable by others, the loginname and password could be read
33397 from the core dump.
33399 If this feature is set, then the passwords will not be cached and you
33400 will have to retype the password whenever Alpine needs it.
33401 Even with this feature set there is still some chance that the core
33402 file will contain a password, so care should be taken to make the
33403 core files unreadable.
33405 NOTE: If PASSFILE caching is enabled, this does not disable it.
33406 That is a separate and independent feature.
33408 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33410 <End of help on this topic>
33413 ====== h_config_disable_password_file_saving =====
33416 <TITLE>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></TITLE>
33419 <H1>FEATURE: <!--#echo var="FEAT_disable-password-file-saving"--></H1>
33421 This feature changes the behavior of Alpine when a login name and password combination
33422 for a specific server is not found in the password file. The default behavior is that
33423 Alpine will ask the user if they wish to save this information in the password file for future
33424 use. It is assumed that if a user created a password file it is because they intend
33425 to use it, but in some instances a user might want to save some passwords and not others.
33426 In this case, enabling this feature will make Alpine not add any more passwords to the
33427 password file and will only use the passwords that it already saved. If you wish to allow
33428 Alpine to save more passwords in the password file, disable this feature.
33431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33433 <End of help on this topic>
33436 ====== h_config_disable_kb_lock =====
33439 <TITLE>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></TITLE>
33442 <H1>FEATURE: <!--#echo var="FEAT_disable-keyboard-lock-cmd"--></H1>
33444 If set, then the Keyboard Lock command is removed from the MAIN MENU.
33447 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33449 <End of help on this topic>
33452 ====== h_config_disable_config_cmd =====
33455 <TITLE>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></TITLE>
33458 <H1>FEATURE: <!--#echo var="FEAT_disable-config-cmd"--></H1>
33460 If set, then the Setup/Config screen is disabled.
33463 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33465 <End of help on this topic>
33468 ====== h_config_allow_chg_from =====
33471 <TITLE>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></TITLE>
33474 <H1>FEATURE: <!--#echo var="FEAT_allow-changing-from"--></H1>
33476 This feature affects Alpine's handling of the "From:" header field
33477 in the "<A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>" configuration
33480 If this feature is set then the From line can be changed just like
33481 all the other header fields that can be changed.
33482 This feature defaults to <EM>ON</EM>.
33484 Even with this feature turned ON (the default) you will not be able
33485 to change the From header unless you add it to your list of
33486 <A HREF="h_config_custom_hdrs"><!--#echo var="VAR_customized-hdrs"--></A>.
33487 You may also want to change the
33488 <A HREF="h_config_comp_hdrs"><!--#echo var="VAR_default-composer-hdrs"--></A>
33489 if you want the From header to always show up in the composer without
33490 having to type the Rich Headers command first.
33492 Note that many sites restrict the use of this feature in order to
33493 reduce the chance of falsified addresses and misdirected mail.
33494 If you want to change the value of what gets included in the From header
33495 in messages you send
33496 look <A HREF="h_config_change_your_from">here</A> for a description.
33499 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33501 <End of help on this topic>
33504 ====== h_config_disable_collate =====
33507 <TITLE>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></TITLE>
33510 <H1>FEATURE: <!--#echo var="FEAT_disable-setlocale-collate"--></H1>
33512 This is a hard to understand feature that should only be used in rare cases.
33513 Normally, the C function call
33515 <CENTER><SAMP>setlocale(LC_COLLATE, "")</SAMP></CENTER>
33518 If you want to try turning it off,
33519 setting this feature will turn it off.
33520 This part of the locale has to do with the sort order
33521 of characters in your locale.
33524 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33526 <End of help on this topic>
33529 ====== h_config_quell_attach_extra_prompt =====
33532 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></TITLE>
33535 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extra-prompt"--></H1>
33537 By default, when you attempt to view an attachment externally
33538 from the "Attachment View" screen, you are asked if you
33539 really want to view the selected attachment.
33542 If this feature is set, you will <B>not</B> be prompted to confirm
33543 your selection. Prior to Alpine and to Pine 4.50, the default behavior was to not
33544 prompt. This feature was added for those wanting to preserve that
33545 behavior (along with
33546 <A HREF="h_config_quell_attach_ext_warn"><!--#echo var="FEAT_quell-attachment-extension-warn"--></A>).
33550 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33552 <End of help on this topic>
33555 ====== h_config_quell_attach_ext_warn =====
33558 <TITLE>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></TITLE>
33561 <H1>FEATURE: <!--#echo var="FEAT_quell-attachment-extension-warn"--></H1>
33564 This feature suppresses the extra warning you can get when trying
33565 to view an attachment for which there is no mime-type match. Turning
33566 on this feature will just run the program according to extension
33567 instead of first warning the user that it will run according to the
33570 This feature can be used along side
33571 <A HREF="h_config_quell_attach_extra_prompt"><!--#echo var="FEAT_quell-attachment-extra-prompt"--></A>
33572 to preserve the behavior exhibited in Pine versions prior to Pine 4.50.
33575 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33577 <End of help on this topic>
33580 ====== h_config_mailcap_params =====
33583 <TITLE>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></TITLE>
33586 <H1>FEATURE: <!--#echo var="FEAT_enable-mailcap-param-substitution"--></H1>
33588 If set, this will allow mailcap named parameter substitution to occur
33589 in mailcap entries.
33590 By default, this is turned off to prevent security problems that may occur
33591 with some incorrect mailcap configurations.
33592 For more information, see RFC1524 and look for "named parameters" in the
33596 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33598 <End of help on this topic>
33601 ====== h_config_disable_shared =====
33604 <TITLE>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></TITLE>
33607 <H1>FEATURE: <!--#echo var="FEAT_disable-shared-namespaces"--></H1>
33609 If this feature is set, the automatic search for namespaces "ftp",
33610 "imapshared", and "imappublic" by the underlying library
33612 The reason this feature exists is because there are some implementations
33613 of system password lookup routines that are very slow when presented with
33614 a long loginname that does not exist.
33615 This feature could be set to prevent the delay at startup time when the
33616 names above are searched for in the password file.
33619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33621 <End of help on this topic>
33624 ====== h_config_hide_nntp_path =====
33627 <TITLE>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></TITLE>
33630 <H1>FEATURE: <!--#echo var="FEAT_hide-nntp-path"--></H1>
33632 Normally the Path header that Alpine generates when posting to a newsgroup
33633 contains the name of the computer from which the message is being sent and
33635 Some believe that this information is used by spammers.
33636 If this feature is set, that information will be replaced with the text
33638 <CENTER><SAMP>not-for-mail</SAMP></CENTER>
33642 It should be noted that many servers being connected to will still reveal
33643 the information that this feature attempts to protect.
33646 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33648 <End of help on this topic>
33651 ====== h_config_no_bezerk_zone =====
33654 <TITLE>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></TITLE>
33657 <H1>FEATURE: <!--#echo var="FEAT_quell-berkeley-format-timezone"--></H1>
33659 POSIX mandates a timezone in UNIX mailbox format folder delimiters
33660 (the line that begins with From <SPACE>).
33661 Some versions of Berkeley mail have trouble with this, and don't recognize
33662 the line as a message delimiter.
33663 If this feature is set, the timezone will be left off the delimiter line.
33666 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33668 <End of help on this topic>
33671 ====== h_config_quell_domain_warn =====
33674 <TITLE>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></TITLE>
33677 <H1>FEATURE: <!--#echo var="FEAT_quell-maildomain-warning"--></H1>
33679 When your configuration is set up so that your domain name contains no dots,
33680 it is usually a configuration error.
33681 By default, Alpine will warn you about this when you start it up.
33682 You will see a warning message that looks like
33685 <CENTER><SAMP>Incomplete maildomain "<domain>".</SAMP></CENTER>
33688 If this feature is set, the warning is turned off.
33691 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33693 <End of help on this topic>
33696 ====== h_config_quell_imap_env =====
33699 <TITLE>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></TITLE>
33702 <H1>FEATURE: <!--#echo var="FEAT_quell-imap-envelope-update"--></H1>
33704 In the MESSAGE INDEX screen, if the open folder is being accessed
33705 using IMAP, Alpine normally tries to paint the index lines on the screen
33706 as soon as the information arrives from the IMAP server.
33707 This means that the index information makes it onto the screen more quickly
33708 than it otherwise would.
33709 This sometimes results in behavior that bothers some users.
33710 For example, when paging to a new page of the index, it may be possible for
33711 the lines to be painted on the screen in a random order, rather than from
33715 Setting this feature causes Alpine to wait for all of the information
33716 to be gathered before it paints the index screen.
33717 Once it collects all of the information, the screen will be painted quickly
33718 from top to bottom.
33721 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33723 <End of help on this topic>
33726 ====== h_config_quell_news_env =====
33729 <TITLE>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></TITLE>
33732 <H1>FEATURE: <!--#echo var="FEAT_quell-news-envelope-update"--></H1>
33734 In the MESSAGE INDEX screen, if the open folder is being accessed
33735 using NNTP (News), Alpine normally tries to paint the index lines on the screen
33736 as soon as the information arrives from the NNTP server.
33737 This means that the index information makes it onto the screen more quickly
33738 than it otherwise would.
33739 This sometimes results in behavior that bothers some users.
33740 For example, when paging to a new page of the index, it may be possible for
33741 the lines to be painted on the screen in a random order, rather than from
33745 Setting this feature causes Alpine to wait for all of the information
33746 to be gathered before it paints the index screen.
33747 Once it collects all of the information, the screen will be painted quickly
33748 from top to bottom.
33751 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33753 <End of help on this topic>
33756 ====== h_config_quell_content_id =====
33759 <TITLE>FEATURE: <!--#echo var="FEAT_quell-content-id"--></TITLE>
33762 <H1>FEATURE: <!--#echo var="FEAT_quell-content-id"--></H1>
33764 This feature changes the behavior of Alpine when sending messages.
33765 It is intended to work around a bug in Microsoft's Outlook XP mail user
33767 As of this writing, Microsoft has acknowledged the bug but
33768 has not added it to the Knowledge Base.
33769 We have been told that there will be a post-SP1 hotfix for Outlook XP.
33770 This particular bug has bug fix number OfficeQFE:4781.
33771 The nature of the bug is that messages with attachments that
33772 contain a Content-ID header (which standard Alpine attachments do)
33773 do not show the attachment indicator (a paperclip) when viewed with
33775 So the user has no indication that the message contains an attachment.
33778 If this feature is set then Alpine will remove most Content-ID headers
33779 before sending a message.
33780 If an attachment is of type MESSAGE, then the existing Content-ID headers
33781 inside the message will be left intact.
33782 This would only happen with Alpine if a message was forwarded as an attachment
33783 or if a message with a message attached was forwarded.
33784 Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded,
33785 the Content-ID headers of the alternative parts will not be removed.
33788 Because the Content-ID header is a standard part of MIME it is possible
33789 that setting this feature will break something.
33790 For example, if an attachment has a Content-ID header that is necessary
33791 for the correct functioning of that attachment, it is possible that Alpine
33792 may remove that header when the attachment is forwarded.
33793 However, it seems fairly safe at this time.
33797 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33799 <End of help on this topic>
33802 ====== h_config_winpos_in_config =====
33805 <TITLE>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></TITLE>
33808 <H1>FEATURE: <!--#echo var="FEAT_store-window-position-in-config"--></H1>
33813 Normally, PC-Alpine will store its window size and position in the
33815 This is convenient if you want to use the same remote
33816 configuration from more than one PC.
33817 If you use multiple configuration files to start PC-Alpine, you may want
33818 to store the window size and position in the configuration file instead
33819 of in the Registry.
33820 Setting this feature causes the value to be stored in
33821 <A HREF="h_config_window_position">Window-Position</A>.
33825 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33827 <End of help on this topic>
33830 ====== h_config_quell_ssl_largeblocks =====
33833 <TITLE>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></TITLE>
33836 <H1>FEATURE: <!--#echo var="FEAT_quell-ssl-largeblocks"--></H1>
33840 This feature changes the behavior of fetching messages
33841 and attachments so that the message data is fetched in chunks no larger
33843 This works around a bug in Microsoft's SSL/TLS support.
33844 Some versions of Microsoft SSL are not able to read full-sized (16K)
33846 Some servers will send such packets and this will
33847 cause PC-Alpine to crash with the error
33850 <CENTER><SAMP>incomplete SecBuffer exceeds maximum buffer size</SAMP></CENTER>
33853 Microsoft is aware of the problem and has developed a hotfix for it, it is
33854 discussed in article 300562 in the Microsoft Knowledge Base.
33857 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33859 <End of help on this topic>
33862 ====== h_config_quell_partial =====
33865 <TITLE>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></TITLE>
33868 <H1>FEATURE: <!--#echo var="FEAT_quell-partial-fetching"--></H1>
33870 Partial fetching is a feature of the IMAP protocol.
33872 will use partial fetching when copying the contents of a message or attachment
33873 from the IMAP server to Alpine.
33874 This means that the fetch will be done in many
33875 small chunks instead of one big chunk. The main benefit of this approach is
33876 that the fetch becomes interruptible. That is, the user can type <EM>^C</EM>
33877 to stop the fetch early. In some cases partial fetching may cause a performance
33878 problem so that the fetching of data takes significantly longer when partial
33879 fetching is used. Turning on this feature will turn off partial fetching.
33882 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33884 <End of help on this topic>
33887 ====== h_config_quell_personal_name_prompt =====
33890 <TITLE>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></TITLE>
33893 <H1>FEATURE: <!--#echo var="FEAT_quell-personal-name-prompt"--></H1>
33895 PC-Alpine only. This feature quells the prompting for a
33896 <A HREF="h_config_pers_name">personal name</A>. This
33897 prompt normally happens before composing a message, and only happens when
33898 there is no personal name already set.
33901 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33903 <End of help on this topic>
33906 ====== h_config_quell_user_id_prompt =====
33909 <TITLE>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></TITLE>
33912 <H1>FEATURE: <!--#echo var="FEAT_quell-user-id-prompt"--></H1>
33914 PC-Alpine only. This feature quells the prompting for a
33915 <A HREF="h_config_user_id"><!--#echo var="VAR_user-id"--></A>
33916 if the information can be obtained from the login name used
33917 to open the INBOX. Normally, this prompt happens before composing
33918 a message, and only happens when there is no user-id already set
33919 in the configuration.
33921 With this feature set, composing a message is only possible after
33922 establishing a connection to the INBOX.
33925 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33927 <End of help on this topic>
33930 ====== h_config_save_aggregates =====
33933 <TITLE>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></TITLE>
33936 <H1>FEATURE: <!--#echo var="FEAT_save-aggregates-copy-sequence"--></H1>
33938 This feature will optimize an aggregate copy operation, if
33939 possible, by issuing a single IMAP <EM>COPY</EM> command with a
33940 list of the messages to be copied.
33941 This feature is set by default.
33942 This may reduce network traffic and elapsed time for the Save.
33943 <EM>However, many IMAP servers (including the UW IMAP server) do
33944 not preserve the order of messages when this optimization is applied.</EM>
33945 If this feature is not set,
33946 Alpine will copy each message individually and the order of the messages
33950 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
33952 <End of help on this topic>
33955 ====== h_config_use_system_translation =====
33958 <TITLE>FEATURE: Use System Translation</TITLE>
33961 <H1>FEATURE: Use System Translation</H1>
33965 Alpine normally uses its own internal software to convert between the multi-byte
33966 representation of characters and the Unicode representation of those
33968 It converts from the multi-byte characters your keyboard produces to Unicode,
33969 and from Unicode to the multi-byte characters your display expects.
33970 Alpine also uses its own internal software to decide how much space on
33971 the screen a particular Unicode character will occupy.
33974 Setting this feature tells Alpine to use the system-supplied routines to
33975 perform these tasks instead.
33976 In particular there are three tasks and three system routines that will
33977 be used for these tasks.
33980 To convert from multi-byte to Unicode the routine
33983 <CENTER><SAMP>mbstowcs</SAMP></CENTER>
33987 To convert from Unicode to multi-byte the routine
33990 <CENTER><SAMP>wcrtomb</SAMP></CENTER>
33994 And to find the screen width a particular Unicode character will
33995 occupy the routine used is
33998 <CENTER><SAMP>wcwidth</SAMP></CENTER>
34001 This feature has been only lightly tested.
34002 The internal routines should normally be used unless you run into
34003 a problem that you think may be solved by using the system routines.
34004 Note that your environment needs to be set up for these
34005 routines to work correctly.
34006 In particular, the LANG or LC_CTYPE variable in your environment will
34011 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34013 <End of help on this topic>
34016 ====== h_config_suspend_spawns =====
34019 <TITLE>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></TITLE>
34022 <H1>FEATURE: <!--#echo var="FEAT_use-subshell-for-suspend"--></H1>
34024 This feature affects Alpine's behavior when process suspension is enabled
34025 and then activated via the Ctrl-Z key. Alpine suspension allows one to
34026 temporarily interact with the operating system command "shell"
34028 quitting Alpine, and then subsequently resume the still-active Alpine session.
34031 When the <A HREF="h_config_can_suspend">"<!--#echo var="FEAT_enable-suspend"-->"</A> feature
34032 is set and subsequently the Ctrl-Z key
34033 is pressed, Alpine will normally suspend itself and return temporary control
34034 to Alpine's parent shell process. However, if this feature is set, Alpine
34035 will instead create an inferior subshell process. This is useful when the
34036 parent process is not intended to be used interactively. Examples include
34037 invoking Alpine via the -e argument of the Unix "xterm" program,
34038 or via a menu system.<P>
34040 Note that one typically resumes a suspended Alpine by entering the Unix
34041 "fg" command, but if this feature is set, it will be necessary to
34042 enter the "exit" command instead.
34045 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34047 <End of help on this topic>
34050 ====== h_config_8bit_smtp =====
34053 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></TITLE>
34056 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-esmtp-negotiation"--></H1>
34058 This feature affects Alpine's behavior when sending mail.
34059 By default, this feature is set.
34061 require that all electronic mail messages traversing the global Internet
34062 consist of 7bit ASCII characters unless a pair of cooperating mail
34063 transfer agents explicitly agree to allow 8bit messages. In general,
34064 then, exchanging messages in non-ASCII characters requires MIME encoding.
34066 However, there are now Internet standards that allow for unencoded 8bit
34067 exchange of messages between cooperating systems. When this feature is set
34068 Alpine will try to negotiate unencoded 8bit transmission during the
34069 sending process. Should the negotiation fail, Alpine will fall back to its
34070 ordinary encoding rules.
34072 Note, this feature relies on your system's mail transport agent or
34073 configured <A HREF="h_config_smtp_server">"<!--#echo var="VAR_smtp-server"-->"</A>
34074 having the negotiation mechanism introduced in
34075 "Extended SMTP" (ESMTP) and the specific extension called
34076 "8BITMIME".
34078 ESMTP allows for graceful migration to upgraded mail transfer agents, but
34079 it is possible that this feature might cause problems for some servers.
34081 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34083 <P><End of help on this topic>
34086 ====== h_config_8bit_nntp =====
34089 <TITLE>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></TITLE>
34092 <H1>FEATURE: <!--#echo var="FEAT_enable-8bit-nntp-posting"--></H1>
34094 This feature affects Alpine's behavior when posting news.
34098 The Internet standard for exchanging USENET news messages (RFC-1036)
34099 specifies that USENET messages should conform to Internet mail standards
34100 and contain only 7bit characters, but much of the news transport software
34101 in use today is capable of successfully sending messages containing 8bit
34102 characters. Hence, many people believe that it is appropriate to send 8bit
34103 news messages without any MIME encoding.
34107 Moreover, there is no Internet standard for explicitly negotiating 8bit
34108 transfer, as there is for Internet email. Therefore, Alpine provides the
34109 option of posting unencoded 8bit news messages, though not as the default.
34110 Setting this feature will turn OFF Alpine's MIME encoding of newsgroup
34111 postings that contain 8bit characters.
34115 Note, articles may cross a path or pass through news transport software
34116 that is unsafe or even hostile to 8bit characters. At best this will only
34117 cause the posting to become garbled. The safest way to transmit 8bit
34118 characters is to leave Alpine's MIME encoding turned on, but recipients
34119 who lack MIME-aware tools are often annoyed when they receive MIME-encoded
34122 <End of help on this topic>
34125 ====== h_config_mark_for_cc =====
34128 <TITLE>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></TITLE>
34131 <H1>FEATURE: <!--#echo var="FEAT_mark-for-cc"--></H1>
34133 This feature affects Alpine's MESSAGE INDEX display.
34134 By default, a '+' is displayed in the first column if the
34135 message is addressed directly to you.
34136 When this feature is set and the message is not addressed to you, then a
34137 '-' character is displayed if the message is instead Cc'd directly
34142 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34144 <End of help on this topic>
34147 ====== h_config_tab_uses_unseen =====
34150 <TITLE>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></TITLE>
34153 <H1>FEATURE: <!--#echo var="FEAT_tab-uses-unseen-for-next-folder"--></H1>
34155 This feature affects Alpine's behavior when using the TAB
34156 <A HREF="h_common_nextnew">NextNew Command</A>
34157 to move from one folder to the next.
34158 Alpine's usual behavior is to search for folders
34159 with <EM>Recent</EM> messages in them.
34160 Recent messages are messages that have arrived since the last time the
34164 Setting this feature causes Alpine to search for <EM>Unseen</EM>
34165 messages instead of Recent messages.
34166 Unseen messages remain Unseen until you view them (or flag then as Seen with
34167 the <A HREF="h_common_flag">Flag Command</A>).
34168 Setting this feature allows you to locate messages you have not read
34169 instead of only recently received messages.
34170 When this feature is set, the feature
34171 <A HREF="h_config_fast_recent">"<!--#echo var="FEAT_enable-fast-recent-test"-->"</A>
34172 will have no effect, so the checking may be slower.
34175 Another reason why you might want to use this feature is that Alpine sometimes
34176 opens folders implicitly behind the scenes, and this clears the
34177 Recent status of all messages in the folder.
34178 One example where this happens is when Saving or filtering a
34179 message to another folder.
34180 If that message has some <A HREF="h_config_keywords">keywords</A>
34181 set, then because of some shortcomings
34182 in the IMAP specification, the best way to ensure that those keywords are
34183 still set in the saved copy of the message is to open the folder and
34184 set the keywords explicitly.
34185 Because this clears the Recent status of all messages in that folder the
34186 folder will not be found by the NextNew command unless this feature is set.
34189 <End of help on this topic>
34192 ====== h_config_tab_new_only =====
34195 <TITLE>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></TITLE>
34198 <H1>FEATURE: <!--#echo var="FEAT_tab-visits-next-new-message-only"--></H1>
34200 This feature affects Alpine's behavior when using the TAB key to move from
34201 one message to the next. Alpine's usual behavior is to select the next
34202 unread message or message flagged as "Important".
34206 Setting this feature causes Alpine to skip the messages flagged as important,
34207 and select unread messages exclusively. Tab behavior when there are no
34208 new messages left to select remains unchanged.
34210 <End of help on this topic>
34213 ====== h_config_warn_if_subj_blank =====
34216 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></TITLE>
34219 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-subject"--></H1>
34221 This feature affects Alpine's behavior when you send a message being
34223 If this option is set, Alpine will check to see if the message about to be sent
34224 has a subject or not.
34225 If not, you will be asked if you want to send the message anyway.
34229 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34231 <End of help on this topic>
34234 ====== h_config_warn_if_fcc_blank =====
34237 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></TITLE>
34240 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-fcc"--></H1>
34242 This feature affects Alpine's behavior when you send a message being
34244 If this option is set, Alpine will check to see if the message about to be sent
34246 If not, you will be asked if you want to send the message anyway.
34250 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34252 <End of help on this topic>
34255 ====== h_config_warn_if_no_to_or_cc =====
34258 <TITLE>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></TITLE>
34261 <H1>FEATURE: <!--#echo var="FEAT_warn-if-blank-to-and-cc-and-newsgroups"--></H1>
34263 This feature affects Alpine's behavior when you send a message being
34265 If this option is set, Alpine will check to see if the message about to be sent
34266 has either a To address, a Cc address, or a Newsgroup.
34267 If none of these is set,
34268 you will be asked if you want to send the message anyway.
34271 This feature is closely related to
34272 <A HREF="h_config_auto_fcc_only"><!--#echo var="FEAT_fcc-only-without-confirm"--></A>.
34273 Alpine will normally ask if you want to copy a message only to the Fcc.
34274 This feature also applies to cases where there is a Bcc but still no To, Cc,
34276 If the <!--#echo var="FEAT_fcc-only-without-confirm"--> feature is set and you are sending a
34277 message with only an Fcc, then you won't be asked about sending with
34278 a blank To and Cc and Newsgroups header even if this feature is set.
34279 Similarly, if you have already been asked if you want to send to the Fcc
34280 only and you have answered Yes, then you won't be asked again about sending with
34281 blank To, Cc, and Newsgroups headers even if this feature is set.
34285 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34287 <End of help on this topic>
34290 ====== h_config_quell_dead_letter =====
34293 <TITLE>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></TITLE>
34296 <H1>FEATURE: <!--#echo var="FEAT_quell-dead-letter-on-cancel"--></H1>
34298 This feature affects Alpine's behavior when you cancel a message being
34299 composed. Alpine's usual behavior is to write the canceled message to
34301 <!--chtml if pinemode="os_windows"-->
34302 "DEADLETR",
34304 "dead.letter" in your home directory,
34306 overwriting any previous message. Under
34307 some conditions (some routine), this can introduce a noticeable delay.
34308 Setting this feature will cause Alpine NOT to write canceled compositions
34311 NOTE: Enabling this feature means NO record of canceled messages is
34314 This feature affects the newer option
34315 <A HREF="h_config_deadlets"><!--#echo var="VAR_dead-letter-files"--></A>, which specifies the
34316 number of dead letter files to keep around.
34317 If this feature is set, then the <!--#echo var="VAR_dead-letter-files"--> option has no effect.
34320 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34322 <End of help on this topic>
34325 ====== h_config_quell_beeps =====
34328 <TITLE>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></TITLE>
34331 <H1>FEATURE: <!--#echo var="FEAT_quell-status-message-beeping"--></H1>
34333 This feature affects Alpine's behavior when it displays status message
34334 (e.g., Error complaints, New mail warnings, etc). Setting this feature
34335 will not affect the display of such messages, but will cause those that
34336 emit a beep to become silent.
34340 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34342 <End of help on this topic>
34345 ====== h_config_suppress_user_agent =====
34348 <TITLE>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></TITLE>
34351 <H1>FEATURE: <!--#echo var="FEAT_suppress-user-agent-when-sending"--></H1>
34353 If this feature is set then Alpine will not generate a
34354 <CODE>User-Agent</CODE> header in outgoing messages.
34357 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34359 <End of help on this topic>
34362 ====== h_config_quell_lock_failure_warnings =====
34365 <TITLE>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></TITLE>
34368 <H1>FEATURE: <!--#echo var="FEAT_quell-lock-failure-warnings"--></H1>
34370 This feature affects Alpine's behavior when it encounters a problem
34371 acquiring a mail folder lock. Typically, a secondary file associated
34372 with the mail folder being opened is created as part of the locking
34373 process. On some systems, such file creation has been administratively
34374 precluded by the system configuration.
34376 Alpine issues a warning when such failures occur, which can become bothersome
34377 if the system is configured to disallow such actions. Setting this
34378 feature causes Alpine to remain silent when this part of lock creation fails.
34380 WARNING: systems that have been configured in a way that precludes locking
34381 introduce some risk of mail folder corruption when more than one program
34382 attempts to modify the mail folder. This is most likely to occur to one's
34383 INBOX or other incoming message folder.
34385 See also <A HREF="h_info_on_locking">"What Systems Managers Need to Know about Alpine File Locking"</A>.
34388 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34390 <End of help on this topic>
34393 ====== h_config_enable_role_take ======
34396 <TITLE>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></TITLE>
34399 <H1>FEATURE: <!--#echo var="FEAT_enable-rules-under-take"--></H1>
34401 Normally, the Take command takes addresses from a message and helps you
34402 put them into your Address Book.
34403 If you use Rules for Indexcolors, Roles, Filtering, or Scoring;
34404 you may find it useful
34405 to be able to Take information from a message's headers and put it into
34407 When this feature is set, you will be given an extra prompt that gives
34408 you the choice to Take into the Address Book or Take into a rule.
34410 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34413 <End of help on this topic>
34416 ====== h_config_enable_take_export ======
34419 <TITLE>FEATURE: <!--#echo var="FEAT_enable-take-export"--></TITLE>
34422 <H1>FEATURE: <!--#echo var="FEAT_enable-take-export"--></H1>
34424 Normally, the Take command takes addresses from a message and helps you
34425 put them into your Address Book.
34426 When this feature is set, you will be given an extra prompt that gives you
34427 the choice to Take addresses into a file instead of your Address
34429 Only the user@domain_name part of the address is put in the file.
34431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34434 <End of help on this topic>
34437 ====== h_config_quell_folder_internal_msg ======
34440 <TITLE>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></TITLE>
34443 <H1>FEATURE: <!--#echo var="FEAT_quell-folder-internal-msg"--></H1>
34445 This feature determines whether or not Alpine will create
34446 "pseudo messages" in folders that are in standard Unix or
34449 Alpine will normally create these pseudo messages when they are not already
34450 present in a standard Unix or MMDF folder. Their purpose is to record
34451 certain mailbox state data needed for correct IMAP and POP server
34452 operation, and also for Alpine to be able to mark messages as Answered when
34453 the Reply has been postponed.<P>
34455 Sites that do not use IMAP/POP for remote mail access, and that need to
34456 support mail tools that are adversely affected by the presence of the
34457 pseudo-messages (e.g. some mail notification tools) may enable this
34458 feature to tell Alpine not to create them. Note that Alpine's
34459 "Answered" flag
34460 capability will be adversely affected if this is done.<P>
34462 Note too that, even if this feature is enabled, Alpine will not remove
34463 pseudo-messages when it encounters them (e.g. those created by UW's imapd
34464 or ipopd servers.) This feature has no effect on folders that are not in
34465 standard Unix or MMDF format, as pseudo-messages are not needed in the
34466 other formats to record mailbox state information.
34468 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34471 <End of help on this topic>
34474 ====== h_config_mulnews_as_typed ======
34477 <TITLE>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></TITLE>
34480 <H1>FEATURE: <!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></H1>
34482 This feature will be of little use to most users.
34483 It has no effect unless the feature
34484 <A HREF="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></A>
34487 When the <!--#echo var="FEAT_enable-multiple-newsrcs"--> feature is set
34488 then the setting of this feature may have an effect on the names of the
34490 Normally, the name of the news server will be canonicalized before it is
34491 used in the newsrc file name.
34492 For example, if you type the news server name
34495 <CENTER><SAMP>servername</SAMP></CENTER>
34498 it is likely that the canonical name will be something like
34501 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34504 Or it may be the case that
34507 <CENTER><SAMP>servername.example.com</SAMP></CENTER>
34510 is really an alias (a DNS CNAME) for
34513 <CENTER><SAMP>othername.example.com</SAMP></CENTER>
34516 If this feature is not set, then the canonicalized names will be used.
34517 If this feature is set, then the name you typed in (or put in your
34518 configuration) will be used.
34521 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34524 <End of help on this topic>
34527 ====== h_config_quell_empty_dirs ======
34530 <TITLE>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></TITLE>
34533 <H1>FEATURE: <!--#echo var="FEAT_quell-empty-directories"--></H1>
34535 This feature causes Alpine to remove from the display any directories
34536 that do not contain at least one file or directory. This can be useful
34537 to prevent overly cluttered folder lists when a collection is stored on
34538 a server that treats all names as both a folder and a directory.
34541 Note, enabling this feature can cause surprising behavior! For example,
34542 you can still use Add to create a directory, but unless you immediately
34543 enter that directory and create a folder, that newly created directory
34544 may not be displayed next time you enter the folder list.
34547 The description above is not quite correct.
34548 Only directories which potentially may hold messages are hidden if empty.
34549 That is, a directory which is really just a directory and is not selectable
34550 as a folder will not be hidden.
34551 Such directories can occur on servers that treat most names as both a folder
34553 These directories are typically created implicitly when a folder is created
34554 inside a directory that does not yet exist.
34558 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34560 <End of help on this topic>
34563 ====== h_config_termcap_wins =====
34566 <TITLE>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></TITLE>
34569 <H1>FEATURE: <!--#echo var="FEAT_termdef-takes-precedence"--></H1>
34571 This feature may affect Alpine's low-level input routines. Termcap (or
34572 terminfo, depending on how your copy of Alpine was compiled and linked)
34573 is the name of the database that describes terminal capabilities. In
34574 particular, it describes the sequences of characters that various keys
34578 An example would be the Up Arrow key on the keyboard. Up
34579 Arrow is not a distinct character on most Unix systems. When you press
34580 the Up Arrow key a short sequence of characters are produced. This
34581 sequence is supposed to be described in the termcap database by the
34582 "ku" capability (or by the "kcuu1" capability if you
34583 are using terminfo instead of termcap).
34586 By default, Alpine defines some terminal
34587 escape sequences that are commonly used. For example, the sequence
34588 "ESC O A" is recognized as an Up Arrow key. The sequence
34589 "ESC [ A"
34590 is also recognized as an Up Arrow key. These are chosen because common
34591 terminals like VT100's or ANSI standard terminals produce these
34592 sequences when you press the Up Arrow key.
34595 If your system's termcap
34596 (terminfo) database assigns some other function to the sequence
34597 "ESC O A"
34598 it is usually ignored by Alpine. Also, if your termcap (terminfo)
34599 database assigns a sequence that doesn't begin with an escape
34600 character (<SAMP>ESC</SAMP>) it is usually ignored by Alpine.
34601 This usually works fine
34602 because most terminals emit the escape sequences that Alpine has defined
34603 by default. We have also found that it is usually better to have these
34604 defaults take precedence over the definitions contained in the database
34605 because the defaults are more likely to be correct than the database.
34608 There are some terminals where this breaks down. If you want Alpine to
34609 believe the definitions given in your termcap (terminfo) database in
34610 preference to the defaults the Alpine itself sets up, then you may turn
34611 this feature on. Then, sequences of characters that are defined in
34612 both termcap (terminfo) and in Alpine's set of defaults will be
34613 interpreted the way that termcap (terminfo) says they should be
34614 interpreted. Also, if your terminal capabilities database assigns a
34615 sequence that doesn't begin with escape, it will not be ignored.
34619 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34621 <End of help on this topic>
34624 ====== h_config_cruise_mode =====
34627 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></TITLE>
34630 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode"--></H1>
34632 This feature affects Alpine's behavior when you hit the
34633 "Space Bar" at
34634 the end of a displayed message. Typically, Alpine complains that the end
34635 of the text has already been reached. Setting this feature causes such
34636 keystrokes to be interpreted as if the "Tab" key had been hit, thus
34637 taking you to the next "interesting" message,
34638 or scanning ahead to the
34639 next incoming folder with "interesting" messages.
34643 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34645 <End of help on this topic>
34648 ====== h_config_cruise_mode_delete =====
34651 <TITLE>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></TITLE>
34654 <H1>FEATURE: <!--#echo var="FEAT_enable-cruise-mode-delete"--></H1>
34656 This feature modifies the behavior of Alpine's
34657 <A HREF="h_config_cruise_mode">"<!--#echo var="FEAT_enable-cruise-mode"-->"</A> feature.
34658 Setting this feature causes Alpine to implicitly delete read
34659 messages when it moves on to display the next "interesting" message.
34661 NOTE: Beware when enabling this feature AND the
34662 <A HREF="h_config_auto_expunge">"<!--#echo var="FEAT_expunge-without-confirm"-->"</A>
34666 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34668 <End of help on this topic>
34671 ====== h_config_slash_coll_entire =====
34674 <TITLE>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></TITLE>
34677 <H1>FEATURE: <!--#echo var="FEAT_slash-collapses-entire-thread"--></H1>
34679 The slash (/) command is available from the MESSAGE INDEX screen when
34680 the folder is sorted by either Threads or OrderedSubject, and the
34681 <A HREF="h_config_thread_disp_style"><!--#echo var="VAR_threading-display-style"--></A>
34682 is set to something other than "none".
34683 Normally, the slash command Collapses or Expands the subthread that
34684 starts at the currently highlighted message, if any.
34685 If this option is set, then the slash command Collapses or Expands the
34686 <EM>entire</EM> current thread instead of just the subthread.
34687 The current thread is simply the top-level thread that contains the
34692 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34694 <End of help on this topic>
34697 ====== h_config_color_thrd_import =====
34700 <TITLE>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></TITLE>
34703 <H1>FEATURE: <!--#echo var="FEAT_thread-index-shows-important-color"--></H1>
34705 This option affects only the THREAD INDEX screen.
34706 Whether or not you ever see a THREAD INDEX screen depends on the setting
34707 of the configuration option
34708 <A HREF="h_config_thread_index_style">"<!--#echo var="VAR_threading-index-style"-->"</A>
34709 and on the sort order of the index.
34712 If a message within a thread is flagged as Important
34713 and this option is set, then
34714 the entire line in the THREAD INDEX will be colored the color of the
34715 Index-important Symbol, which can be set using the
34716 <A HREF="h_color_setup">Setup Kolor</A> screen.
34720 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34722 <End of help on this topic>
34725 ====== h_config_allow_goto =====
34728 <TITLE>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></TITLE>
34731 <H1>FEATURE: <!--#echo var="FEAT_enable-goto-in-file-browser"--></H1>
34733 This feature modifies the behavior of Alpine's file browser. Setting this
34734 feature causes Alpine to offer the "G Goto" command in the file browser.
34735 That is the default.
34739 The Goto command allows you to explicitly type in the desired directory.
34741 <End of help on this topic>
34743 ====== h_config_add_ldap =====
34746 <TITLE>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></TITLE>
34749 <H1>FEATURE: <!--#echo var="FEAT_ldap-result-to-addrbook-add"--></H1>
34751 If both the Directory option
34752 <A HREF="h_config_ldap_opts_impl">"Use-Implicitly-From-Composer"</A>
34753 and this feature are set,
34754 then when an implicit directory lookup is done from the
34755 composer you will automatically be prompted to add the result of the
34756 directory lookup to your address book.
34759 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
34761 <End of help on this topic>
34764 ===== h_patterns_compat_behavior =====
34767 <TITLE>Rules Behavior Changes in Pine 4.50</TITLE>
34770 <H1>Rules Behavior Changes in Pine 4.50</H1>
34772 In Alpine, Rules that contain unrecognized elements
34774 In most cases, the unrecognized elements will be something that was
34775 added as a new Rules feature in a later version of Alpine.
34776 In versions of Pine <EM>prior</EM> to 4.50, Pine did <EM>not</EM>
34777 ignore rules that contained unrecognized elements.
34778 For example, a new element of Rules that was added in Pine 4.50 is
34780 Suppose you add an Indexcolor rule, using version Pine 4.50 or later, that colors
34781 all messages older than a week red.
34782 Now, if you run Pine 4.44 using that same configuration file, it will not
34783 recognize the Age interval and so will just ignore it.
34784 That means that all messages will match that rule so all messages will
34785 be colored red when using Pine version 4.44.
34788 This behavior was considered a bug so it is fixed in Alpine and Pine 4.50 and later.
34789 However, since the behavior still exists in versions prior to Pine 4.50 and
34790 since Filtering is a potentially destructive operation, another measure
34791 was taken to attempt to avoid unintentional Filtering of messages.
34792 The first time that you run Alpine or a Pine that is version 4.50 or greater,
34793 the rules in your Filters configuration variable ("Patterns-Filters")
34794 will be copied to a new Filters configuration variable
34795 with a different name ("Patterns-Filters2").
34796 From then on, Alpine will continue to use the new
34798 Of course, Pine version 4.44 or lower will continue to use the old
34800 That means that if you are using Alpine
34801 and also using a version of Pine that is older than 4.50, they will not
34802 share the configuration information about Filters.
34803 If you make a change in one version you won't see it in the other version.
34806 Since Scoring can be used to trigger Filtering, the same thing has been
34807 done for Score rules.
34808 The old configuration variable name is ("Patterns-Scores")
34809 and the new name is ("Patterns-Scores2").
34810 The same is not true of Role, Indexcolor, and Other rules that are
34811 thought to be less harmful when a mistake is made.
34814 <End of help on this topic>
34817 ======= h_config_filt_opts_sentdate =======
34820 <TITLE>PATTERN FEATURE: Use-Date-Header-For-Age</TITLE>
34823 <H1>PATTERN FEATURE: Use-Date-Header-For-Age</H1>
34825 By default, the Age interval of a Pattern uses a message's time of
34826 arrival to compute the age of the message.
34827 If this feature is set, the date in the message's Date header will
34830 <End of help on this topic>
34833 ======= h_config_filt_opts_notdel =======
34836 <TITLE>FILTER FEATURE: Move-Only-if-Not-Deleted</TITLE>
34839 <H1>FILTER FEATURE: Move-Only-if-Not-Deleted</H1>
34841 If this option is set then a message will be moved into the
34842 specified folder only if it is not marked for deletion.
34843 This is useful if you have multiple Alpine sessions running
34844 simultaneously and you don't want messages to be filtered into a
34845 folder more than once.
34846 It is also useful if you want to filter
34847 only the "undeleted" messages in a newsgroup into a folder.
34848 This method is not foolproof.
34849 There may be cases where a message
34850 gets marked deleted and so it is never filtered into the folder.
34851 For example, if you deleted it in another Alpine session or another mail
34852 program that didn't use the filtering rule.
34854 This option has no effect if the Filter Action is not set to Move.
34856 <End of help on this topic>
34859 ======= h_config_filt_opts_nonterm =======
34862 <TITLE>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</TITLE>
34865 <H1>FILTER FEATURE: Dont-Stop-Even-if-Rule-Matches</H1>
34867 If this option is set then this is a non-terminating rule.
34868 Usually, for each message, Alpine searches through the Filter Rules until
34869 a match is found and then it performs the action associated with that rule.
34870 Rules following the match are not considered.
34871 If this option is set then the search for matches will continue at the next
34874 If a non-terminating rule matches then the actions associated with
34875 that rule, except for any implied deletion of the message, are performed
34876 before the match for the next rule is checked.
34877 For example, if the non-terminating rule sets the Important status, then that
34878 status will be set when the next rule is considered.
34879 However, if the non-terminating rule Moves the message, the message will
34880 actually be copied instead of copied and deleted so that it is still there
34882 A moved message is deleted after all the relevant rules have been checked.
34883 The name of the "Move" action is confusing in this case because
34884 a single message can be moved to more than one folder.
34885 It turns the Move into a Copy instead, but it is still followed by a deletion
34888 This option may be useful if you want to have a single message filtered to
34889 two different folders because it matches two different Patterns.
34890 For example, suppose you normally filter messages to a particular mailing
34891 list into one folder, and messages addressed directly to you into a second
34893 If a message is sent to both you and the list (and you can tell that by
34894 looking at the headers of the message) this option may give you a convenient
34895 way to capture a copy to each folder.
34896 (It may also cause you to capture two copies to each folder,
34897 depending on whether your mail system delivers one or two copies of the
34898 message to you and on how the list works.)
34900 <End of help on this topic>
34903 ===== h_mainhelp_smime ======
34906 <TITLE>S/MIME Overview</TITLE>
34909 <H1>S/MIME Overview</H1>
34911 S/MIME is a standard for the public key encryption and signing of email.
34912 UNIX Alpine contains a basic implementation of S/MIME based on
34913 the <A HREF="http://www.openssl.org/">OpenSSL</A> libraries.
34914 To check if this version of Alpine supports S/MIME look at
34915 <A HREF="X-Alpine-Config:">Supported Options in this Alpine</A> and look
34916 for "S/MIME" under the "Encryption" heading.
34920 <LI> There is no PC-Alpine implementation.
34921 <LI> There is no provision for checking for CRLs
34922 (Certificate Revocation Lists) in Alpine.
34923 <LI> This built-in S/MIME implementation is not compatible with and does not help with PGP.
34924 <LI> There is no mechanism available for feeding either an entire incoming
34925 or an entire outgoing message to an external
34926 filter and using that external filter to do S/MIME or PGP processing.
34927 <LI> Because the implementation currently uses OpenSSL, there is only a very
34928 limited integration with the Mac OS Keychain (the storing and access of
34929 public certificates).
34932 The S/MIME configuration screen is reached by going to the Main Menu and typing
34933 the "S Setup" command followed by "M S/MIME".
34936 <H2>S/MIME BASICS</H2>
34938 In order to digitally sign messages you send you must have a public/private key-pair.
34939 This may be obtained from a public Certificate Authority (CA) such as Thawte, Verisign, Comodo,
34940 or GoDaddy; or from a smaller CA such as a university which provides certificates for its
34941 users or a company which provides certificates for its workers.
34942 These certificates are bound to an email address, so the identity being verified is the
34943 email address not a person's name.
34945 Mail is signed by using the sender's private key, which only the owner of the private key
34947 The signature is verified using the signer's public key, which anyone can
34949 With Alpine, the first time you receive a signed message the public key of the
34950 sender will be stored for future use.
34953 Mail is encrypted using the recipient's public key and decrypted by
34954 the recipient with their private key.
34957 You need a key of your own in order to sign outgoing messages and to have others
34958 encrypt messages sent to you.
34959 You do not need a key of your own to verify signed messages sent by others or to
34960 encrypt messages sent to others.
34962 <H2>ALPINE S/MIME CERTIFICATE STORAGE</H2>
34964 By default UNIX Alpine stores the certificates it uses in a directory in your
34966 The directory name is
34968 <CENTER><SAMP>.alpine-smime</SAMP></CENTER>
34970 Within that directory are three subdirectories.
34971 Each of the three subdirectories contains files with PEM-encoded contents,
34972 the default format for OpenSSL.
34973 The "<SAMP>public</SAMP>" directory contains public certificates.
34974 The files within that directory have names that are email addresses with the
34975 suffix "<SAMP>.crt</SAMP>" appended.
34976 An example filename is
34978 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
34980 The "<SAMP>private</SAMP>" directory contains private keys, probably just one for
34982 These are also email addresses but with the suffix "<SAMP>.key</SAMP>" instead.
34983 The third directory is "<SAMP>ca</SAMP>" and it contains certificates for any Certificate
34984 Authorities that you want to trust but that aren't contained in the set of system CAs.
34985 Those files may have arbitrary names as long as they end with the
34986 suffix "<SAMP>.crt</SAMP>".
34988 <H2>HOW TO SIGN AND ENCRYPT</H2>
34990 If you have a certificate you may sign outgoing messages.
34991 After typing the Ctrl-X command to send a message you will see the prompt
34993 <CENTER><SAMP>Send message?</SAMP></CENTER>
34995 Available subcommands include "G Sign" and "E Encrypt".
34996 Typing the "G" command will change the prompt to
34998 <CENTER><SAMP>Send message (Signed)?</SAMP></CENTER>
35000 Typing the "E" command will change the prompt to
35002 <CENTER><SAMP>Send message (Encrypted)?</SAMP></CENTER>
35004 You may even type both to get
35006 <CENTER><SAMP>Send message (Encrypted, Signed)?</SAMP></CENTER>
35009 <H2>HOW TO READ SIGNED OR ENCRYPTED MESSAGES</H2>
35011 The reading of a signed message should not require any special action on
35013 There should be an editorial addition at the start of the message which
35016 <CENTER><SAMP>This message was cryptographically signed.</SAMP></CENTER>
35020 <CENTER><SAMP>This message was cryptographically signed but the signature could not be verified.</SAMP></CENTER>
35022 If an encrypted message is sent to you the encrypted text will not
35024 You will have to type the "Ctrl-D Decrypt" command (from the screen where
35025 you are viewing the message) and supply your passphrase when asked.
35027 For a signed or encrypted message there is also a "Ctrl-E Security" command
35028 which gives you some information about the certificate used to sign or encrypt the message.
35030 <H2>MISCELLANEOUS</H2>
35032 If you have access to a private certificate in the PKCS12 format, which
35033 would sometimes be in a file with a ".p12" extension, then you can
35034 use the following commands to generate private keys, public and certificate
35035 authorities certificates. In the examples below, we assume that the
35036 certificate in the p12 format is called "certificate.p12", and
35037 that your email address is "your@address.com".
35040 In order to create a private key use the command
35042 <CENTER><SAMP>openssl pkcs12 -in certificate.p12 -out your@address.com.key</SAMP></CENTER>
35044 In order to create a public certificate use the command
35047 openssl pkcs12 -in certificate.p12 -clcerts -nokeys -out your@address.com.crt
35050 In order to create a certificate authority certificate use the command
35053 openssl pkcs12 -in certificate.p12 -cacerts -nokeys -out certificate-ca.crt
35056 <P> If the previous command produces an empty file, it means that the
35057 certificate authority was not included in the .p12 file, so you will have
35058 to get it from some other sources. You will need these certificates, so
35059 that you can validate correctly signatures.
35062 After you have exported these certificates and keys, you can use the import
35063 command in Alpine, from the S/MIME configuration screen,
35064 to import these certificates into Alpine. They will be available for use
35065 as soon as you import them.
35067 <End of help on this topic>
35070 ====== h_config_smime_pubcertdir =====
35073 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></TITLE>
35076 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-public-cert-directory"--></H1>
35081 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35082 is set then this option will have no effect.
35084 Normally, Public Certificates for use with S/MIME will be stored in the directory
35085 which is the value of this option.
35086 Those certificates will be stored in PEM format, one certificate per file.
35087 The name of the file for the certificate corresponding to
35089 <CENTER><SAMP>emailaddress</SAMP></CENTER>
35093 <CENTER><SAMP>emailaddress.crt</SAMP></CENTER>
35095 For example, a file for user@example.com would be in the file
35097 <CENTER><SAMP>user@example.com.crt</SAMP></CENTER>
35101 Use the Setup/SMIME screen to modify this variable.
35103 Typically, the public certificates that you have will come from S/MIME signed
35104 messages that are sent to you.
35105 Alpine will extract the public certificate from the signed message and store
35106 it in the certificates directory.
35107 These PEM format public certificates look something like:
35109 -----BEGIN CERTIFICATE-----
35110 MIIFvTCCBKWgAwIBAgIQD4fYFHVI8T20yN4nus097DANBgkqhkiG9w0BAQUFADCB
35111 rjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2Ug
35112 Q2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExho
35114 2b9KGqDyMWW/rjNnmpjzjT2ObGM7lRA8lke4FLOLajhrz4ogO3b4DFfAAM1VSZH8
35115 D6sOwOLJZkLY8FRsfk63K+2EMzA2+qAzMKupgeTLqXIf
35116 -----END CERTIFICATE-----
35120 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35124 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35126 <End of help on this topic>
35129 ====== h_config_smime_pubcertcon =====
35132 <TITLE>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></TITLE>
35135 <H1>OPTION: <!--#echo var="VAR_smime-public-cert-container"--></H1>
35139 If this option is set it will be used instead of
35140 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35142 This option gives you a way to store certificates remotely on an IMAP server
35143 instead of storing the certificates one per file locally.
35144 In order to do that you just give this option a remote folder name for a folder
35145 which does not yet exist.
35146 The name is similar to the name you might use for a remote configuration file.
35147 A remote folder name might look something like:
35149 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/publiccerts</SAMP></CENTER>
35152 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35153 about the syntax of folder names.
35155 Use the Setup/SMIME screen to modify this variable.
35158 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35162 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35164 <End of help on this topic>
35167 ====== h_config_smime_privkeydir =====
35170 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></TITLE>
35173 <H1>OPTION: <!--#echo var="VAR_smime-private-key-directory"--></H1>
35177 In order to sign outgoing S/MIME messages you will need a
35178 personal digital ID certificate.
35179 You will usually get such a certificate from a certificate authority such as
35181 (In order to encrypt outgoing messages you don't need a personal digital ID, you
35182 need the public certificate of the recipient instead.)
35184 <A HREF="h_config_smime_privkeycon"><!--#echo var="VAR_smime-private-key-container"--></A>
35185 is set then this option will have no effect.
35187 Normally, Private Keys for use with S/MIME will be stored in the directory
35188 which is the value of this option.
35189 Those certificates will be stored in PEM format, one certificate per file.
35190 The name of the file for the certificate corresponding to your
35192 <CENTER><SAMP>emailaddress</SAMP></CENTER>
35196 <CENTER><SAMP>emailaddress.key</SAMP></CENTER>
35198 For example, if your address is user@example.com the name of the file would be
35200 <CENTER><SAMP>user@example.com.key</SAMP></CENTER>
35204 Use the Setup/SMIME screen to modify this variable.
35206 Typically, the private key that you have will come from a Certificate
35208 The private key should be stored in a PEM format file that
35209 looks something like:
35211 -----BEGIN RSA PRIVATE KEY-----
35212 Proc-Type: 4,ENCRYPTED
35213 DEK-Info: DES-EDE3-CBC,2CBD328FD84CF5C6
35215 YBEXYLgLU9NJoc1V+vJ6UvcF08RX54S6jXsmgL0b5HGkudG6fhnmHkH7+UCvM5NI
35216 SXO/F8iuZDfs1VGG0NyitkFZ0Zn2vfaGovBvm15gx24b2xnZDLRB7/bNZkurnK5k
35217 VjAjZ2xXn2hFp2GJwqRdmxYNqsKGu52B99oti5HUWuZ2GFRaWjn5hYOqeApZE2uA
35219 oSRqfI51UdSRt0tmGhHeTvybUVrHm9eKft8TTGf+qSBqzSc55CsmoVbRzw4Nfhix
35220 m+4TJybNGNfAgOctSkEyY/OCb49fRRQTCBZVIhzLGGmpYmkO55HbIA==
35221 -----END RSA PRIVATE KEY-----
35225 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35229 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35231 <End of help on this topic>
35234 ====== h_config_smime_privkeycon =====
35237 <TITLE>OPTION: <!--#echo var="VAR_smime-private-key-container"--></TITLE>
35240 <H1>OPTION: <!--#echo var="VAR_smime-private-key-container"--></H1>
35244 If this option is set it will be used instead of
35245 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35247 This option gives you a way to store keys remotely on an IMAP server
35248 instead of storing the keys one per file locally.
35249 In order to do that you just give this option a remote folder name for a folder
35250 which does not yet exist.
35251 The name is similar to the name you might use for a remote configuration file.
35252 A remote folder name might look something like:
35254 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/privatekeys</SAMP></CENTER>
35257 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35258 about the syntax of folder names.
35260 Use the Setup/SMIME screen to modify this variable.
35263 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35267 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35269 <End of help on this topic>
35272 ====== h_config_smime_cacertdir =====
35275 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></TITLE>
35278 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-directory"--></H1>
35283 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>
35284 is set then this option will have no effect.
35286 CACert is a shorthand name for certification authority certificate.
35287 Normally Alpine will use the CACerts that are located in the standard system
35288 location for CACerts.
35289 It may be the case that one of your correspondents has a Digital ID which has
35290 been signed by a certificate authority that is not in the regular set of system certificate
35292 You may supplement the system list by adding further certificates of your own.
35293 These should be stored in the directory
35294 which is the value of this option.
35295 The certificates will be stored in PEM format, one certificate per file.
35296 The names of the files can be anything ending in ".crt".
35298 Use the Setup/SMIME screen to modify this variable.
35300 These PEM format CA certificates look very similar to your public
35301 certificates for particular email addresses
35302 (<A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>).
35305 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35309 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35311 <End of help on this topic>
35314 ====== h_config_smime_cacertcon =====
35317 <TITLE>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></TITLE>
35320 <H1>S/MIME OPTION: <!--#echo var="VAR_smime-cacert-container"--></H1>
35324 If this option is set it will be used instead of
35325 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35327 This option gives you a way to store certificates remotely on an IMAP server
35328 instead of storing the certificates one per file locally.
35329 In order to do that you just give this option a remote folder name for a folder
35330 which does not yet exist.
35331 The name is similar to the name you might use for a remote configuration file.
35332 A remote folder name might look something like:
35334 <CENTER><SAMP>{myimaphost.myschool.k12.wa.us}mail/cacerts</SAMP></CENTER>
35337 <A HREF="h_valid_folder_names">Valid Folder Names</A> for more information
35338 about the syntax of folder names.
35340 Use the Setup/SMIME screen to modify this variable.
35343 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35347 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35349 <End of help on this topic>
35352 ========== h_config_smime_sign_by_default ==========
35355 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></TITLE>
35358 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-sign-by-default"--></H1>
35362 This feature only has an effect if your version of Alpine includes
35363 support for S/MIME.
35364 It affects Alpine's behavior when you send a message.
35365 If this option is set, the "Sign" option will default to ON when sending messages.
35367 Only the default value is affected.
35368 In any case, you may still toggle the Signing option on or off before sending
35369 with the "G Sign" command (provided you have a personal digital ID
35373 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35378 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35380 <End of help on this topic>
35383 ========== h_config_smime_use_cert_store ==========
35386 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></TITLE>
35389 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-use-store-only"--></H1>
35393 This feature only has an effect if your version of Alpine includes
35394 support for S/MIME.
35395 It affects Alpine's behavior when you validate a message, and should
35396 not be disabled, unless you are performing a test.
35398 There are two important aspects of validation: validation of the message
35399 (that is, the message was not modified after it was sent)
35400 as well as validation of the identity of the sender. This option has to
35401 do with the latter.
35403 In order to validate that the message came from the sender in the message
35404 and not an impersonator, Alpine can
35405 either use the certificates that come in the message, or the ones that
35406 you have personally stored. If this feature is enabled (the default) then
35407 Alpine will use certificates that you have already saved in your store
35408 and not those that come in the message to validate the sender of the
35409 message. In particular, the first time that you receive a signed message
35410 from a sender, and their certificate does not validate against your
35411 store, then you will be asked if you wish to save such certificate. If
35412 you do not wish to save the certificate, then Alpine will fail to validate
35413 the signature of the message. Otherwise, Alpine will proceed to validate
35414 the signature of the message. This behavior helps you prevent against impersonation, because
35415 it is assumed that you trust the certificates that you have saved, and
35416 might not trust those that came with the message that you are validating.
35419 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35424 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35426 <End of help on this topic>
35429 ========== h_config_smime_pubcerts_in_keychain ==========
35432 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></TITLE>
35435 <H1>S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></H1>
35439 If this feature is set the Mac OS X default keychain will be used as the place
35440 to store public certificates instead of a
35441 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35443 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35446 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35450 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35452 <End of help on this topic>
35455 ========== h_config_smime_dont_do_smime ==========
35458 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></TITLE>
35461 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-dont-do-smime"--></H1>
35465 Setting this feature turns off all of Alpine's S/MIME support.
35466 You might want to set this if you are having trouble due to the S/MIME support.
35469 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35474 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35476 <End of help on this topic>
35479 ========== h_config_smime_encrypt_by_default ==========
35482 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></TITLE>
35485 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-encrypt-by-default"--></H1>
35489 This feature only has an effect if your version of Alpine includes
35490 support for S/MIME.
35491 It affects Alpine's behavior when you send a message.
35492 If this option is set, the "Encrypt" option will default to ON when sending messages.
35494 Only the default value is affected.
35495 In any case, you may still toggle the Encrypt option on or off before sending
35496 with the "E Encrypt" command (provided you have a the public digital ID
35497 for the recipient).
35500 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35505 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35507 <End of help on this topic>
35510 ========== h_config_smime_remember_passphrase ==========
35513 <TITLE>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></TITLE>
35516 <H1>S/MIME FEATURE: <!--#echo var="FEAT_smime-remember-passphrase"--></H1>
35520 This feature only has an effect if your version of Alpine includes
35521 support for S/MIME.
35522 If this option is set, you will only have to enter your passphrase for your private key
35523 once during an Alpine session.
35526 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35531 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35533 <End of help on this topic>
35536 ====== h_config_smime_transfer_pub_to_con =====
35539 <TITLE>S/MIME: Transfer Public Certs to Container</TITLE>
35542 <H1>S/MIME: Transfer Public Certs to Container</H1>
35546 The Transfer command will copy the public certificates in your configured
35547 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>
35548 to the container in your configured
35549 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>.
35550 This might be useful if you decide to switch from using a cert directory to a cert
35553 Warning: Any previous contents in the container will be lost.
35556 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35560 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35562 <End of help on this topic>
35565 ====== h_config_smime_transfer_pub_to_dir =====
35568 <TITLE>S/MIME: Transfer Public Certs to Directory</TITLE>
35571 <H1>S/MIME: Transfer Public Certs to Directory</H1>
35575 The Transfer command will copy the public certificates in your configured
35576 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35577 to the directory in your configured
35578 <A HREF="h_config_smime_pubcertdir"><!--#echo var="VAR_smime-public-cert-directory"--></A>.
35579 This might be useful if you decide to switch from using a cert container to a cert
35583 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35587 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35589 <End of help on this topic>
35592 ====== h_config_smime_transfer_priv_to_con =====
35595 <TITLE>S/MIME: Transfer Private Keys to Container</TITLE>
35598 <H1>S/MIME: Transfer Private Keys to Container</H1>
35602 The Transfer command will copy the private keys in your configured
35603 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35604 to the container in your configured
35605 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35606 This might be useful if you decide to switch from using a key directory to a key
35609 Warning: Any previous contents in the container will be lost.
35612 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35616 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35618 <End of help on this topic>
35621 ====== h_config_smime_transfer_priv_to_dir =====
35624 <TITLE>S/MIME: Transfer Private Keys to Directory</TITLE>
35627 <H1>S/MIME: Transfer Private Keys to Directory</H1>
35631 The Transfer command will copy the private keys in your configured
35632 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-container"--></A>.
35633 to the directory in your configured
35634 <A HREF="h_config_smime_privkeydir"><!--#echo var="VAR_smime-private-key-directory"--></A>.
35635 This might be useful if you decide to switch from using a key container to a key
35639 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35643 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35645 <End of help on this topic>
35648 ====== h_config_smime_transfer_cacert_to_con =====
35651 <TITLE>S/MIME: Transfer CA Certs to Container</TITLE>
35654 <H1>S/MIME: Transfer CA Certs to Container</H1>
35658 The Transfer command will copy the CA certificates in your configured
35659 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>
35660 to the container in your configured
35661 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35662 This might be useful if you decide to switch from using a CA cert directory to a CA cert
35665 Warning: Any previous contents in the container will be lost.
35668 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35672 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35674 <End of help on this topic>
35677 ====== h_config_smime_transfer_cacert_to_dir =====
35680 <TITLE>S/MIME: Transfer CA Certs to Directory</TITLE>
35683 <H1>S/MIME: Transfer CA Certs to Directory</H1>
35687 The Transfer command will copy the CA certificates in your configured
35688 <A HREF="h_config_smime_cacertcon"><!--#echo var="VAR_smime-cacert-container"--></A>.
35689 to the directory in your configured
35690 <A HREF="h_config_smime_cacertdir"><!--#echo var="VAR_smime-cacert-directory"--></A>.
35691 This might be useful if you decide to switch from using a CA cert container to a CA cert
35695 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35699 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35701 <End of help on this topic>
35704 ====== h_config_smime_transfer_pubcon_to_key =====
35707 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35710 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35712 Mac OS X Alpine only.
35714 The Transfer command will copy the public certificates in your configured
35715 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35716 to your default Mac OS X Keychain.
35717 This might be useful if you decide to switch from using a cert container to using
35718 the Keychain to store your public certs, which you may do by using the
35720 <A HREF="h_config_smime_pubcerts_in_keychain">S/MIME FEATURE: <!--#echo var="FEAT_publiccerts-in-keychain"--></A>.
35723 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35727 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35729 <End of help on this topic>
35732 ====== h_config_smime_transfer_pubkey_to_con =====
35735 <TITLE>S/MIME: Transfer Public Certs to Keychain</TITLE>
35738 <H1>S/MIME: Transfer Public Certs to Keychain</H1>
35742 The Transfer command will copy the public certificates in your configured
35743 <A HREF="h_config_smime_pubcertcon"><!--#echo var="VAR_smime-public-cert-container"--></A>
35744 to your default Mac OS X Keychain.
35745 This might be useful if you decide to switch from using a cert container to using
35746 the Keychain to store your public certs.
35749 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35753 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35755 <End of help on this topic>
35758 ====== h_config_smime_public_certificates =====
35761 <TITLE>S/MIME: Manage Public Certificates</TITLE>
35764 <H1>S/MIME: Manage Public Certificates</H1>
35768 This menu item allows you to manage your public certificates, this
35769 may include your own public certificate, but it normally includes
35770 certificates of people you correspond with. These certificates are
35771 saved by Alpine automatically when they are found in signed messages
35772 that you receive. This interface allows you to manage them, by
35773 giving you the option to delete them, or trust them (in the case
35774 of self-signed certificates).
35777 Please note that Alpine will not validate a message that was sent to you
35778 using a self-signed certificate, unless you decide to trust that certificate.
35779 Internally, a certificate is trusted by copying it to the
35780 <A HREF="h_config_smime_certificate_authorities">Certificate Authorities</A>
35781 collection. If you decide that you want to stop trusting a self-signed
35782 certificate, you must delete such certificate from such collection.
35784 The <B>I</B> Import command available in this screen allows you to
35785 import a command to this collection.
35788 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35792 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35794 <End of help on this topic>
35797 ====== h_config_smime_private_keys =====
35800 <TITLE>S/MIME: Manage Private Keys</TITLE>
35803 <H1>S/MIME: Manage Private Keys</H1>
35807 This option allows you to manage your private key. Normally a person has only
35808 one key, in the same way that a person only has one valid passport, or ID card,
35809 at any given time. This option allows you to manage private keys. You can
35810 delete them or import them. Additionally, you can view information
35811 about your public certificate, such as the issuer and the dates of validity
35812 of such certificate, among others.
35815 If you have more than one e-mail address for which you want to use the
35816 same private key, you must add all those addresses to the private key at
35817 the moment that the key is generated. When you receive a signed message using
35818 a key generated for several e-mail addresses, Alpine will save a
35819 certificate for each e-mail address included in such certificate.
35821 The <B>I</B> Import command available in this screen allows you to
35822 import a command to this collection.
35825 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35829 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35831 <End of help on this topic>
35834 ====== h_config_smime_certificate_authorities =====
35837 <TITLE>S/MIME: Manage Certificate Authorities</TITLE>
35840 <H1>S/MIME: Manage Certificate Authorities</H1>
35844 This collection contains certificates that are needed to validate the
35845 certificate of another person, and therefore contains certificates that
35846 you trust. Typically a certificate is signed by another entity, called a
35847 certificate authority. This option allows you to manage which certificates
35848 you trust, allowing you to import them and to delete them or view information
35849 about each certificate, such as the issuer and the dates of validity
35850 of such certificate.
35852 The <B>I</B> Import command available in this screen allows you to
35853 import a command to this collection.
35856 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35860 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35862 <End of help on this topic>
35865 ====== h_config_smime_password_file_certificates =====
35868 <TITLE>S/MIME: Manage Password File Certificates</TITLE>
35871 <H1>S/MIME: Manage Password File Certificates</H1>
35875 This option allows you to manage the certificates that are used to
35876 encrypt and decrypt your password file. This is useful in case you
35877 want to change the certificates used to encrypt your password file.
35879 In order to avoid unauthorized use of this option, you are asked to
35880 enter the password of the current private key used to encrypt your
35883 Once you have entered your password for the current key, you enter a
35884 screen where you can import your new key, and see the information on your
35887 To import a new key press "RETURN" and enter the location of
35888 the new key. You will be asked to enter the password of the new key. If
35889 this part of the process is successful, Alpine will search for the
35890 certificate that matches that key. If your key is named
35891 "your_email@address.com.key", then Alpine will look for your
35892 certificate in the same directory in the file named
35893 "your_email@address.com.crt", otherwise it will look for it
35894 as part of your key (that is, it will look to see if your certificate
35895 is in the file "your_email@address.com.key"), if all of this
35896 fails, Alpine will ask you to enter the location of the certificate
35897 that matches the key you unlocked. If a certificate is found, it will be
35898 used, and in this case, the password file will be read, decrypted with the
35899 old key and encrypted with the new key. Once this is done, the new key and
35900 certificates are saved, and the old keys are permanently deleted.
35902 Alpine does not create a backup of your password file, or your old keys
35903 that will be replaced. If you need to keep old copies, you will have to do
35904 this operation outside Alpine.
35906 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35910 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35912 <End of help on this topic>
35915 ====== h_certificate_information =====
35918 <TITLE>S/MIME: Certificate Information Screen</TITLE>
35921 <H1>S/MIME: Certificate Information Screen</H1>
35925 The CERTIFICATE INFORMATION screen shows you information contained in a certificate
35926 such as its owner, e-mail address, issuer, and interval of validity,
35929 In the case of public certificates, this screen shows you if there was a
35930 failure when attempting to validate such message. If the certificate is
35931 self-signed, then the <B>T</B> Trust command will be available, which
35932 you can use to trust such certificate and make Alpine not fail validating
35933 signatures signed with such certificate.
35935 You can also mark a certificate deleted, with the <B>D</B> command, or
35936 remove the deleted mark with the <B>U</B> undelete command.
35938 In the case of your private key, Alpine shows you the information
35939 from your public key. Additionally, Alpine allows you to see public
35940 and private information about your key, with the <B>B</B> and
35941 <B>R</B> commands respectively.
35943 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35947 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
35949 <End of help on this topic>
35952 ====== h_config_smime_manage_public_menu =====
35955 <TITLE>S/MIME: Menu of Commands to Manage Public Certificates</TITLE>
35958 <H1>S/MIME: Commands that Manage Public Certificates</H1>
35962 This screen allows you to manage your public certificates.
35964 The format of this screen is as follows. There are five fields: The
35965 leftmost field is normally empty, but it could contain the letter
35966 "D" to indicate that that certificate has been marked for
35967 deletion. The next field is the e-mail address of the owner of the
35968 certificate, shown in its entirety. The third and fourth field are the
35969 first and last day validity for that certificate, respectively. The date
35970 is displayed in the user's locale unless the option
35971 <A HREF="h_config_disable_index_locale_dates"><!--#echo var="FEAT_disable-index-locale-dates"--></A>
35972 is set. In this case, the month, day and year are represented by two
35973 digits, and the format used is mm/dd/yy. Finally, the fifth
35974 field is what can be displayed of the MD5 hash of the certificate. You can
35975 use any of the last three fields to distinguish between two certificates
35976 for the same owner.
35978 Available commands in this screen and a short description of what they
35981 <LI> <B>I</B> Imports a public certificate to this collection.
35982 <LI> <B>V</B> View information about a certificate such as the name of the person the
35983 certificate was issued to, its dates of validity, and validity status.
35984 <LI> <B>D</B> Marks a certificate deleted.
35985 <LI> <B>U</B> Removes the deletion mark on a certificate.
35986 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
35987 <LI> <B>T</B> This command is only available for self-signed certificates, and allows you to
35988 trust a certificate by copying it to the collection of trusted certificates.
35991 All commands provide feedback to let you know about their success or failure.
35994 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
35998 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36000 <End of help on this topic>
36003 ====== h_config_smime_manage_private_menu =====
36006 <TITLE>S/MIME: Menu of Commands to Manage Private Keys</TITLE>
36009 <H1>S/MIME: Commands that Manage Private Keys</H1>
36013 This screen allows you to manage your private key.
36015 The format of this screen is as follows. There are five fields: The
36016 leftmost field is normally empty, but it could contain the letter
36017 "D" to indicate that that certificate has been marked for
36018 deletion. The next field is the e-mail address of the owner of the
36019 certificate, shown in its entirety. The third field is the first day of
36020 validity for that certificate; the fourth field in the last day that that
36021 certificate is valid, and the fifth field is what can be displayed of the
36022 MD5 hash of the public certificate corresponding to this private key. You
36023 can use any of the last three fields to distinguish between two
36024 certificates for the same owner.
36026 Available commands and a short description of what they do follows.
36028 <LI> <B>I</B> Imports a new public key to this collection.
36029 <LI> <B>V</B> View information about the public certificate corresponding to this
36031 <LI> <B>D</B> Marks a key to be deleted.
36032 <LI> <B>U</B> Removes the deletion mark on a key.
36033 <LI> <B>X</B> Removes all keys marked deleted permanently (cannot be undone).
36034 Note that expunging a private key does not remove the public key, which must
36035 be removed separately.
36038 All commands provide feedback to let you know about their success or failure.
36041 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
36045 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36047 <End of help on this topic>
36050 ====== h_config_smime_manage_cacerts_menu =====
36053 <TITLE>S/MIME: Menu of Commands to Manage Certificate Authorities</TITLE>
36056 <H1>S/MIME: Commands that Manage Certificate Authorities</H1>
36060 This screen allows you to manage your collection of certificates that you
36063 The format of this screen is as follows. There are five fields: The
36064 leftmost field is normally empty, but it could contain the letter
36065 "D" to indicate that that certificate has been marked for
36066 deletion. The next field is the e-mail address of the owner of the
36067 certificate, shown in its entirety. The third field is the first day of
36068 validity for that certificate; the fourth field in the last day that that
36069 certificate is valid, and the fifth field is what can be displayed of the
36070 MD5 hash of the certificate. You can use any of the last three fields to
36071 distinguish between two certificates for the same owner.
36073 Available commands and a short description of what they do follows.
36075 <LI> <B>I</B> Imports a trusted certificate to this collection. This is
36076 done by reading the certificate and validating it. Once a certificate
36077 is found to be valid, it is saved, adding the extension ".crt"
36078 to the certificate, if necessary.
36079 <LI> <B>V</B> View information about this certificate, such as its issuer
36080 and validity dates.
36081 <LI> <B>D</B> Marks a certificate to be deleted.
36082 <LI> <B>U</B> Removes the deletion mark on a certificate.
36083 <LI> <B>X</B> Removes all certificates marked deleted permanently (cannot be undone).
36086 All commands provide feedback to let you know about their success or failure.
36089 <LI><A HREF="h_mainhelp_smime">General S/MIME help</A>
36093 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36095 <End of help on this topic>
36098 ====== h_config_lame_list_mode =====
36101 <TITLE>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></TITLE>
36104 <H1>FEATURE: <!--#echo var="FEAT_enable-lame-list-mode"--></H1>
36106 This feature modifies the method Alpine uses to ask your IMAP
36107 server for folder names to display in the FOLDER LIST screen.
36108 It is intended to compensate for a small set of IMAP servers that
36109 are programmed to ignore a part of the request, and thus respond
36110 to Alpine's query with nonsensical results.
36113 If you find that Alpine is erroneously displaying blank folder lists,
36114 try enabling this feature.
36117 NOTE: Enabling this feature has consequences for the Goto and Save
36118 commands. Many servers allow access to folders outside the area
36119 reserved for your personal folders via some reserved character,
36120 typically '#' (sharp), '~' (tilde) or '/' (slash). This mechanism
36121 allows, at the Goto and Save prompts, quick access to folders
36122 outside your personal folder collection without requiring a specific
36123 collection definition. This behavior will generally not be available
36124 when this feature is enabled.
36128 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36130 <End of help on this topic>
36133 ====== h_config_enable_mulnewsrcs =====
36136 <TITLE>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></TITLE>
36139 <H1>FEATURE: <!--#echo var="FEAT_enable-multiple-newsrcs"--></H1>
36141 This feature makes it so Alpine can use multiple newsrcs based on
36142 the news server being connected to, which allows for separate lists
36143 of subscribed-to newsgroups. When this feature is not set, there is only
36144 one list of newsgroups.
36146 Under this feature, the name of a newsrc is based on the news server.
36147 For example, if your <a href="h_config_newsrc_path"><!--#echo var="VAR_newsrc-path"--></a>
36148 is set to ".newsrc", and the news server you are connecting to is
36149 news.example.com, then the newsrc to be used is .newsrc-news.example.com.
36150 Setting this feature for the first time will allow for the option of using
36151 your old newsrc the next time you read news.
36153 If this feature is set, then the feature
36154 <A HREF="h_config_mulnews_as_typed"><!--#echo var="FEAT_mult-newsrc-hostnames-as-typed"--></A>
36155 also may affect the name of the newsrc file that is used.
36158 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36160 <End of help on this topic>
36163 ======= h_ab_export_vcard =======
36166 <TITLE>Address Book Export Format</TITLE>
36169 <H1>Address Book Export Format</H1>
36171 You are exporting address book data from Alpine to a file outside of Alpine.
36172 You are being asked to choose the format of the export.
36173 Here are the choices:
36176 <DT><EM>A</EM>ddress List</DT>
36178 The addresses from the address book entries you are saving
36179 from will be saved one address per line.
36180 Address book lists (those with more than one address) will have
36181 all of their addresses saved separately.
36184 <DT><EM>V</EM>Card</DT>
36186 The entries will be saved in
36187 <A HREF="h_whatis_vcard">vCard</A> format.
36190 <DT><EM>T</EM>ab Separated</DT>
36192 The entries will be saved in tab-separated columns.
36193 There will be just 4 columns of data that correspond to Alpine's
36194 Nickname field, Full Name field, Address field, and Comment field.
36195 It might prove useful to Select only the Simple, non-List address book
36196 entries before Saving.
36199 <DT><EM>^C</EM> Cancel</DT>
36201 Cancel out of the Save.
36208 <End of help on this topic>
36211 ====== h_config_predict_nntp_server =====
36214 <TITLE>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></TITLE>
36217 <H1>FEATURE: <!--#echo var="FEAT_predict-nntp-server"--></H1>
36219 This feature allows Alpine to assume that the open NNTP server at the
36220 time of composition is the NNTP server to which the message should be
36221 posted. This is especially recommended when there are multiple News
36222 collections. If this feature is not set, Alpine will try to post to the first server in
36223 the <a href="h_config_nntp_server"><!--#echo var="VAR_nntp-server"--></a> variable. Setting
36224 this feature also negates the need to add News collection servers to
36225 the <!--#echo var="VAR_nntp-server"--> variable.
36227 This feature can be especially handy when used in conjunction with
36228 <a href="h_config_enable_mulnewsrcs"><!--#echo var="FEAT_enable-multiple-newsrcs"--></a>.
36231 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36233 <End of help on this topic>
36236 ====== h_config_nntp_search_uses_overview =====
36239 <TITLE>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></TITLE>
36242 <H1>FEATURE: <!--#echo var="FEAT_nntp-search-uses-overview"--></H1>
36244 This feature should probably be turned on unless it causes trouble.
36245 The results of the NNTP overview command (XOVER) may be used to help
36246 with some searches in news groups.
36247 It should result in quicker response time.
36248 Turning this feature on apparently causes search results which are
36249 different from what you would get with the feature turned off on some
36253 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36255 <End of help on this topic>
36258 ====== h_config_thread_sorts_by_arrival =====
36261 <TITLE>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></TITLE>
36264 <H1>FEATURE: <!--#echo var="FEAT_thread-sorts-by-arrival"--></H1>
36266 This feature affects how a threading sort arranges threads. The default way
36267 to arrange threads is by the date of the earliest message in the thread.
36268 This feature arranges threads by the last message to arrive in a thread.
36270 This feature causes old threads that get recent messages to sort to the bottom,
36271 where previously a message arrival to a thread would not rearrange the order of
36275 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36277 <End of help on this topic>
36280 ====== h_config_textplain_int =====
36283 <TITLE>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></TITLE>
36286 <H1>FEATURE: <!--#echo var="FEAT_show-plain-text-internally"--></H1>
36288 This feature modifies the method Alpine uses to display Text/Plain
36289 MIME attachments from the Attachment Index screen. Normally, the
36290 "View" command searches for any externally defined (usually
36292 "<A HREF="h_config_mailcap_path">Mailcap</A>" file) viewer,
36293 and displays the selected text within that viewer.
36296 Enabling this feature causes Alpine to ignore any external viewer
36297 settings and always display text with Alpine's internal viewer.
36301 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36303 <End of help on this topic>
36306 ====== h_config_wp_columns =====
36309 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></TITLE>
36312 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-columns"--></H1>
36316 This configuration setting specifies the number of horizontal characters
36317 used to format various WebAlpine pages. Smaller values will tend to reduce
36318 the amount of horizontal scrolling required to view pages within narrow
36319 browsers, such as those found on PDAs, and larger values will tend to
36320 spread more information across the page.
36323 The Message List page uses the width to determine how many characters
36324 to assign each field. Note, a smaller value may result in a disproportionate
36325 amount of blank space between fields on each line. Similarly, a large
36326 value may result in cramped fields or horizontal scrolling.
36329 The Message View page uses this value to determine when to wrap lines
36330 in displayed message text. Note, a smaller value may result in jagged
36331 right margins or confusing quoting. A larger value may cause lines of text to
36332 run beyond the browser's right edge, requiring horizontal scrolling.
36336 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36338 <End of help on this topic>
36341 ====== h_config_wp_state =====
36344 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></TITLE>
36347 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-state"--></H1>
36351 Various aspects of cross-session state.
36355 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36357 <End of help on this topic>
36360 ====== h_config_wp_aggstate =====
36363 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></TITLE>
36366 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-aggstate"--></H1>
36370 Aggregate operations tab state.
36374 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36376 <End of help on this topic>
36379 ====== h_config_wp_indexlines =====
36382 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></TITLE>
36385 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexlines"--></H1>
36389 Number of index lines in table.
36393 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36395 <End of help on this topic>
36398 ====== h_config_wp_indexheight =====
36401 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></TITLE>
36404 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_wp-indexheight"--></H1>
36408 Index table row height.
36412 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36414 <End of help on this topic>
36417 ====== h_config_rss_news =====
36420 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss_news"--></TITLE>
36423 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-news"--></H1>
36431 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36433 <End of help on this topic>
36436 ====== h_config_rss_weather =====
36439 <TITLE>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></TITLE>
36442 <H1>WEB ALPINE OPTION: <!--#echo var="VAR_rss-weather"--></H1>
36450 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36452 <End of help on this topic>
36455 ====== h_config_send_confirms_only_expanded =====
36458 <TITLE>FEATURE: send-confirms-only-expanded</TITLE>
36461 <H1>FEATURE: send-confirms-only-expanded (Web Alpine Only)</H1>
36463 This Web Alpine option specifies whether or not a Send confirmations
36464 happens when a composed message is readied for sending or not. The
36465 default behavior is to not confirm that the nicknames were expanded to
36466 the intended addresses.
36470 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36472 <End of help on this topic>
36475 ====== h_config_enable_jump_command =====
36478 <TITLE>FEATURE: enable-jump-command</TITLE>
36481 <H1>FEATURE: enable-jump-command (Web Alpine Only)</H1>
36483 This Web Alpine option specifies whether or not a Jump command is
36484 offered in the Message List and Message View pages. The command is
36485 implemented as an input field in the left column of the List and View
36489 When enabled and a number is entered in the input field while the
36490 Message List is displayed, the Message List is reframed with the
36491 specified message. While viewing a message, the message associated
36492 with the specified message number is displayed.
36496 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36498 <End of help on this topic>
36501 ====== h_config_enable_newmail_sound =====
36504 <TITLE>FEATURE: enable-newmail-sound</TITLE>
36507 <H1>FEATURE: enable-newmail-sound (Web Alpine Only)</H1>
36509 This Web Alpine option specifies whether or not a sound file is sent
36510 to the web browser along with the newmail notification message.
36515 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36517 <End of help on this topic>
36520 ====== h_config_render_html_internally =====
36523 <TITLE>FEATURE: render-html-internally</TITLE>
36526 <H1>FEATURE: render-html-internally (Web Alpine Only)</H1>
36528 By default, Web Alpine will pass cleansed HTML text you receive in messages
36529 to the browser for display (rendering). This feature causes Web Alpine to convert
36530 the HTML text into plain text in the same way Unix and PC-Alpine do.
36535 <LI><A HREF="h_finding_help">Finding more information and requesting help</A>
36537 <End of help on this topic>
36540 ====== h_config_role_undo =====
36541 Yes, remember changes and exit back to list of roles; No, discard changes
36542 made in this screen; ^C, cancel exit and stay in this config screen.
36543 ====== h_exit_editor =====
36544 S, save changes and exit from the editor; D, do not save changes but
36545 do exit from the editor; or ^C, cancel exit and stay in the editor.
36546 ====== h_config_undo =====
36547 Yes, save changes and exit; No, exit without saving any changes made since
36548 entering this CONFIGURATION screen; ^C, cancel exit and stay in config screen.
36549 ====== h_os_index_whereis =====
36550 Enter ^V or ^Y to go immediately to the last or first message in the index.
36551 Or, enter the match string followed by RETURN.
36552 ====== h_os_index_whereis_agg =====
36553 Enter ^V or ^Y to go immediately to the last or first message in the index,
36554 Or, enter the match string followed by RETURN (or ^X to select all matches).
36555 =========== h_oe_add_full ==================
36556 Type the full name of the person being added and press the RETURN key.
36557 Press ^C to cancel addition.
36558 =========== h_oe_add_nick ==================
36559 Type a short nickname and press RETURN. A nickname is a short easy-to-
36560 remember word, name or initials like "joe", or "wcfields." ^C to cancel.
36561 ========== h_oe_add_addr ================
36562 Type the e-mail address and press RETURN.
36563 Press ^C to cancel addition.
36564 ========== h_oe_crlst_full ==============
36565 Type a long name or description for the list that you are creating and
36566 press RETURN. Press ^C to cancel creation of list.
36567 =========== h_oe_crlst_nick =============
36568 Type a nickname (short, easy-to-remember name or single word) for the list
36569 you are creating and press RETURN. Press ^C to cancel.
36570 ========== h_oe_crlst_addr ==============
36571 Type an e-mail address, or a nickname already in the address book that you
36572 want to be part of this list and press RETURN.
36573 ========== h_oe_adlst_addr =============
36574 Type an e-mail address or a nickname already in the address book that you
36575 want to add to this list and press RETURN.
36576 ========== h_oe_editab_nick ============
36577 Change the nickname using the arrow keys and delete key. Press RETURN
36578 when done. Press ^C to cancel editing and leave the nickname as it was.
36579 ========== h_oe_editab_full ============
36580 Change the full name using the arrow keys and delete key. Press RETURN
36581 when done. Press ^C to cancel editing and leave the full name as it was.
36582 ========== h_oe_editab_addr ============
36583 Change the address using the arrow keys and delete key. Press RETURN
36584 when done. Press ^C to cancel editing and leave the address as it was.
36585 ========== h_oe_editab_fcc ============
36586 Change the fcc using the arrow keys and delete key. Press RETURN when
36587 done. Press ^C to cancel editing and leave the fcc as it was.
36588 ========== h_oe_editab_comment ============
36589 Change the comment field using the arrow keys and delete key. Press RETURN
36590 when done. Press ^C to cancel editing and leave the comment as it was.
36591 ====== h_ab_forward =====
36592 Yes, expand nicknames and qualify local names with your current domain name;
36593 No, leave nicknames and local names as is; ^C, cancel.
36594 ========== h_ab_export ==========
36595 Type the name of a file to write the addresses into and
36596 press RETURN. You may also specify an absolute path. Use ^C to cancel.
36597 ========== h_ab_edit_a_field ==========
36598 Edit any of the fields of the currently selected entry by typing one of the
36599 letters at the bottom of the screen. Press ^C to cancel edit.
36600 ====== h_ab_del_data_revert =====
36601 Press B to completely delete addrbook and revert to default, C to delete config
36602 and revert while leaving data, or D to only delete data (make it empty).
36603 ====== h_ab_del_data_modify =====
36604 Press B to completely delete addrbook, C to delete configuration while leaving
36605 data, or D to delete data (make it empty) but leave config. ^C to cancel.
36606 ====== h_ab_del_config_modify =====
36607 Yes, remove this address book from my configuration.
36608 No, make no changes now.
36609 ====== h_ab_del_config_revert =====
36610 Yes, remove this address book from my config and revert to default.
36611 No, make no changes now.
36612 ====== h_ab_del_default =====
36613 Yes, remove this default address book from my configuration.
36614 No, make no changes now.
36615 ====== h_ab_really_delete =====
36616 Yes, delete the actual contents of the address book, not just the
36617 configuration. No, don't delete the data after all, cancel and start over.
36618 ====== h_ab_del_ignore =====
36619 Press I to ignore all the default address books for this category. Press R to
36620 remove this one address book and add the others to your personal list.
36621 ====== h_ab_del_dir_ignore =====
36622 Press I to ignore all the default directory servers for this category.
36623 Press R to remove this one server and add the others to your personal list.
36624 ====== h_ab_copy_dups =====
36625 Yes, overwrite the existing entry.
36626 No, skip duplicates but save the rest. Press ^C to cancel.
36627 ====== h_confirm_cancel =====
36628 Type C to Confirm that you want to abandon the message you are composing.
36629 Type N or ^C to cancel out of the cancel and keep composing.
36630 ====== h_ab_text_or_vcard =====
36631 Text, start composer with displayed text already included.
36632 VCard, start composer with address book entry attached as a vCard. ^C cancels.
36633 ====== h_ab_backup_or_ldap =====
36634 Backup, copy email address from entry and allow editing of it.
36635 LDAP, copy LDAP search criteria, do not allow editing of it. ^C cancels.
36636 ====== h_ldap_text_or_vcard =====
36637 Text: export displayed text for selected entry. Address: export only the
36638 email address. VCard: export entry in vCard format. ^C cancels.
36639 ====== h_ab_save_exp =====
36640 Save, save entry or entries to an address book.
36641 Export, save to file outside of pine. ^C cancels save.
36642 ====== h_ab_add =====
36643 A, add a brand new entry to this address book.
36644 E, edit the entry that is currently highlighted. ^C to cancel.
36645 ====== h_ab_shuf =====
36646 U, swap order of highlighted address book and the one above it.
36647 D, swap order of highlighted address book and the one below it. ^C to cancel.
36648 ====== h_ab_shuf_up =====
36649 U, swap order of highlighted address book and the one above it.
36650 Press ^C to cancel.
36651 ====== h_ab_shuf_down =====
36652 D, swap order of highlighted address book and the one below it.
36653 Press ^C to cancel.
36654 ====== h_folder_prop =====
36655 Count is # of messages in the folder, Unseen means messages that have not
36656 been read, New means messages that were Recently added to the folder.
36657 ====== h_role_shuf =====
36658 U, swap order of highlighted rule and the one above it.
36659 D, swap order of highlighted rule and the one below it. ^C to cancel.
36660 ====== h_role_shuf_up =====
36661 U, swap order of highlighted rule and the one above it.
36662 Press ^C to cancel.
36663 ====== h_role_shuf_down =====
36664 D, swap order of highlighted rule and the one below it.
36665 Press ^C to cancel.
36666 ====== h_incoming_shuf =====
36667 B, swap order of highlighted directory and the one before it.
36668 F, swap order of highlighted directory and the one after it. ^C to cancel.
36669 ====== h_incoming_shuf_up =====
36670 B, swap order of highlighted directory and the one before it.
36671 Press ^C to cancel.
36672 ====== h_incoming_shuf_down =====
36673 F, swap order of highlighted directory and the one after it.
36674 Press ^C to cancel.
36675 ====== h_dir_shuf =====
36676 U, swap order of highlighted directory and the one above it.
36677 D, swap order of highlighted directory and the one below it. ^C to cancel.
36678 ====== h_dir_shuf_up =====
36679 U, swap order of highlighted directory and the one above it.
36680 Press ^C to cancel.
36681 ====== h_dir_shuf_down =====
36682 D, swap order of highlighted directory and the one below it.
36683 Press ^C to cancel.
36684 ====== h_hdrcolor_shuf =====
36685 U, swap order of highlighted Header Color and the one above it.
36686 D, swap order of highlighted Header Color and the one below it. ^C to cancel.
36687 ====== h_hdrcolor_shuf_up =====
36688 U, swap order of highlighted Header Color and the one above it.
36689 Press ^C to cancel.
36690 ====== h_hdrcolor_shuf_down =====
36691 D, swap order of highlighted Header Color and the one below it.
36692 Press ^C to cancel.
36693 ========== h_oe_editab_al ============
36694 Change the address using the arrow keys and delete key. Press RETURN
36695 when done. Press ^C to cancel editing and leave the address as it was.
36696 ========== h_dir_comp_search ===============
36697 Type a string to look for just like you would in the composer. Your configured
36698 rules for the servers with the implicit flag set will be used.
36699 ========== h_oe_searchab ===============
36700 Type the word or name you want to search for and press RETURN. If you press
36701 RETURN without entering anything the word in [] will be searched for.
36702 ========== h_oe_chooseabook ==========
36703 Choose the address book you want to save the new entry in.
36704 Use ^N or ^P to change address books. ^C to cancel.
36705 ========== h_oe_takeaddr ==========
36706 Edit the e-mail address using the arrow and delete keys. Press RETURN
36707 when done. Press ^C to cancel adding this entry to the address book.
36708 ========== h_oe_take_replace ==========
36709 Press R to replace the old entry with this new data. You will still have
36710 another chance to cancel. N to enter another nickname. ^C to cancel now.
36711 ========== h_oe_take_replace_or_add ==========
36712 Press R to replace the old entry. Press A to add the selected addresses to
36713 the old existing list. N to enter another nickname. ^C to cancel now.
36714 ========== h_oe_takename ==========
36715 Edit the full name to be correct using the arrow and delete keys. Press RETURN
36716 when done. Press ^C to cancel adding this entry to the address book.
36717 ========== h_oe_takenick ==========
36718 Type a nickname (short easy-to-remember name, initials or single word) for this
36719 entry in the address book and press RETURN. Press ^C to cancel addition.
36720 ========== h_oe_jump ==========
36721 Type the message number you want to jump to and press RETURN. The word "end"
36722 represents the last message. Press ^C to cancel jumping to another message.
36723 ========== h_oe_jump_thd ==========
36724 Type the thread number you want to jump to and press RETURN. The word "end"
36725 represents the last thread. Press ^C to cancel jumping to another thread.
36726 ========== h_oe_debuglevel ==========
36727 Higher number shows more debugging details.
36728 Press ^C if you want to cancel the change.
36729 ========== h_oe_broach ==========
36730 Type the name of the folder you want to open and press RETURN. Press ^P/^N
36731 to go to the previous/next collections in the list. Press ^C to cancel goto.
36732 ========== h_oe_foldsearch ==========
36733 Type the text you want to search for in foldernames and press RETURN. If you
36734 press RETURN without entering anything, any text in [] will be searched for.
36735 ========== h_oe_foldrename ==========
36736 Change the old name of the folder to the new name using the arrow and
36737 delete keys and press RETURN. Press ^C to cancel rename.
36738 ========== h_oe_login ==========
36739 Enter your login name for the host you are opening the mailbox on. Just press
36740 RETURN to use your login from this host as is, or edit it with delete key.
36741 ========== h_oe_passwd ==========
36742 Type your password for the host and login shown as part of the prompt.
36743 Press ^C to cancel opening folder.
36744 ========== h_oe_choosep ==========
36745 Enter the number associated with the printer you want to select. Press ^C to
36746 cancel the printer selection. The current selection is highlighted.
36747 ========== h_oe_customp ==========
36748 Type the name of the Unix print command and press RETURN. Press ^C to
36749 cancel the printer selection.
36750 ========== h_oe_searchview ==========
36751 Type the word or name you want to search for and press RETURN. If you press
36752 RETURN without entering anything the word in [] will be searched for.
36753 ========== h_oe_keylock ==========
36754 The keyboard is in use and locked by another user. Only that user can
36755 unlock this keyboard by typing the password.
36756 ========== h_wt_expire ==========
36757 At the beginning of each month Alpine offers to rename your current sent-mail
36758 folder to one named for the month so you have a sent-mail folder for each month
36759 ========== h_wt_delete_old ==========
36760 It is the beginning of the month, and we need to conserve disk
36761 space. Please delete any sent-mail that you do not need.
36762 ========== h_select_sort ==========
36763 Select the order for sorting the index by typing the capitalized letter.
36764 Arrival is by arrival in your mailbox; Date is by time/day message was sent.
36765 ========== h_no_F_arg ============
36766 Enter name of file to be opened.
36768 ========== h_sticky_personal_name ==========
36769 Type in your name as you want it to appear on outgoing email. This entry
36770 will be saved into your Alpine configuration file.
36771 ========== h_sticky_inbox ============
36772 INBOX syntax is usually {complete.machine.name}INBOX
36773 This entry will be saved in your Alpine configuration file.
36774 ========== h_sticky_smtp ============
36775 The name of the computer on your campus that relays your outgoing email
36776 to the Internet. This entry will be saved in your Alpine configuration file.
36777 ========== h_sticky_user_id ==========
36778 The username or login-id part of your email address. This entry will be
36779 saved in your Alpine configuration file.
36780 ========== h_sticky_domain ==========
36781 The domain part of your email address, NOT the name of your PC. This
36782 entry will be saved in your Alpine configuration file.
36783 ========== h_bounce =========
36784 Enter the address or nickname of the intended recipient. Alpine will resend
36785 the message, which will retain the original author's From: address.
36786 ========== h_incoming_add_folder_nickname =========
36787 Enter an (optional) nickname that will be used in lieu of the actual
36788 host and folder names in the FOLDER LIST display.
36789 ========== h_anon_forward ==========
36790 Enter the address of your intended recipient, or ^C to cancel.
36791 Example: jsmith@somewhere.edu
36792 ========== h_news_subscribe ==========
36793 Enter the name of the newsgroup to which you wish to subscribe,
36794 or ^C to cancel. Example: comp.mail.pine
36795 ========== h_pipe_msg ==========
36796 Enter the name of the Unix command to which you wish to send this
36797 message, or ^C to cancel.
36798 ========== h_pipe_attach ==========
36799 Enter the name of the Unix command to which you wish to send this
36800 attachment, or ^C to cancel.
36801 ========== h_select_by_num ==========
36802 Enter a list of message numbers (or number ranges), or ^C to cancel. "end"
36803 is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end
36804 ========== h_select_by_thrdnum ==========
36805 Enter a list of message numbers (or number ranges), or ^C to cancel. "end"
36806 is the last message. "." is the current message. Example: 1-.,7-9,11,19,35-end
36807 ========== h_select_txt_from ==========
36808 Messages with From: headers containing the entered string will be selected.
36809 ^C to cancel. ^G again to see original options.
36810 ========== h_select_txt_not_from ==========
36811 Messages without From: headers containing the entered string will be selected.
36812 ^C to cancel. ^G again to see original options.
36813 ========== h_select_txt_to ==========
36814 Messages with To: headers containing the entered string will be selected.
36815 ^C to cancel. ^G again to see original options.
36816 ========== h_select_txt_not_to ==========
36817 Messages without To: headers containing the entered string will be selected.
36818 ^C to cancel. ^G again to see original options.
36819 ========== h_select_txt_cc ==========
36820 Messages with Cc: headers containing the entered string will be selected.
36821 ^C to cancel. ^G again to see original options.
36822 ========== h_select_txt_not_cc ==========
36823 Messages without Cc: headers containing the entered string will be selected.
36824 ^C to cancel. ^G again to see original options.
36825 ========== h_select_txt_subj ==========
36826 Messages with Subject: headers containing the entered string will be selected.
36827 ^C to cancel. ^X enters Subject: line of current message.
36828 ========== h_select_txt_not_subj ==========
36829 Messages without Subject headers containing the entered string will be selected.
36830 ^C to cancel. ^X enters Subject: line of current message.
36831 ========== h_select_txt_all ==========
36832 All messages containing the entered string will be selected. Headers and body,
36833 but not encoded attachments, will be compared. Enter ^C to cancel.
36834 ========== h_select_txt_not_all ==========
36835 All messages that don't contain the entered string will be selected. Headers
36836 and body, but not encoded attachments, will be compared. Enter ^C to cancel.
36837 ========== h_select_txt_body ==========
36838 All messages containing the entered string will be selected. Body text, but
36839 not headers or encoded attachments, will be compared. ^C to cancel.
36840 ========== h_select_txt_not_body ==========
36841 All messages that don't contain the entered string will be selected. Body
36842 text, but not headers or encoded attachments, will be compared. ^C to cancel.
36843 ========== h_select_txt_recip ==========
36844 Messages with Cc: or To: headers containing the entered string will be selected.
36845 ^C to cancel. ^G again to see original options.
36846 ========== h_select_txt_not_recip ==========
36847 Messages without Cc: or To: headers containing the string will be selected.
36848 ^C to cancel. ^G again to see original options.
36849 ========== h_select_txt_partic ==========
36850 Messages with Cc, To, or From headers containing the string will be selected.
36851 ^C to cancel. ^G again to see original options.
36852 ========== h_select_txt_not_partic ==========
36853 Messages without Cc, To, or From headers containing the string will be selected.
36854 ^C to cancel. ^G again to see original options.
36855 ========== h_select_date ==========
36856 If typed, date may be in DD-MMM-YYYY format (04-Jul-2006) or in ISO format
36857 (2006-07-04). ^P/^N also changes default date. ^X enters date of current msg.
36858 ========== h_attach_index_whereis ==========
36859 Enter some text that appears in the Attachment Index entry for the desired
36860 attachment. The first attachment containing that text will be highlighted.
36861 ========== h_kb_lock ==========
36862 Keystrokes entered here (up to a RETURN) comprise a password that must
36863 be entered again later in order to unlock the keyboard.
36864 ========== h_compose_default ==========
36865 N, compose a new message. R, set a role.
36867 ========== h_untranslatable ==========
36868 Send using UTF-8 character set; Send but replace untranslatable characters
36869 with question marks; return to the composer; or cancel message altogether.
36870 ========== h_compose_intrptd ==========
36871 N, compose a new msg. I, continue interrupted msg. R, set a role.
36873 ========== h_compose_postponed ==========
36874 N, compose a new message. P, continue postponed msg. R, set a role.
36876 ========== h_compose_intrptd_postponed ==========
36877 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36878 R, set a role. ^C to cancel.
36879 ========== h_compose_form ==========
36880 N, compose a new message. F, use form letter. R, set a role.
36882 ========== h_compose_intrptd_form ==========
36883 N, compose a new msg. I, continue interrupted msg. F, use form letter.
36884 R, set a role. ^C to cancel.
36885 ========== h_compose_postponed_form ==========
36886 N, compose a new message. P, continue postponed msg. F, use form letter.
36887 R, set a role. ^C to cancel.
36888 ========== h_compose_intrptd_postponed_form ==========
36889 N, compose a new msg. I, continue interrupted msg. P, continue postponed msg.
36890 F, use form letter. R, set a role. ^C to cancel.
36891 ========== h_config_context_del_except ==========
36892 If you delete the last exceptional collection you can only add it back by
36893 manually editing the exceptions config file.
36894 ========== h_config_whereis ==========
36895 To move quickly to a particular line, enter a search string or
36897 ========== h_config_edit_scorei ==========
36898 Enter interval in the form (min,max). -INF and INF may be used to represent
36899 -infinity and infinity. ^C to cancel change. RETURN to accept change.
36900 ========== h_config_add ==========
36901 Enter desired value; use normal editing keys to modify (e.g. ^K, ^D). Just
36902 pressing RETURN sets the Empty Value (this turns off any global default).
36903 ========== h_config_add_custom_color ==========
36904 Enter a header fieldname. For example, "subject" or "from".
36906 ========== h_config_add_pat_hdr ==========
36907 Enter a header fieldname. For example, "reply-to" or "organization" or
36908 any fieldname you want that isn't included already.
36909 ========== h_config_print_opt_choice ==========
36910 You may edit either the initialization string (characters printed before
36911 printing starts) or the trailer string. Choose one or ^C to cancel.
36912 ========== h_config_print_init ==========
36913 Enter a C-style string for this. You may use common backslash escapes like
36914 \\n for newline, \\ooo for octal character, and \\xhh for hex character.
36915 ========== h_config_change ==========
36916 Edit the existing value using arrow keys, ^K to delete entire entry, ^D to
36917 delete current (highlighted) character, etc. Enter ^C to cancel change.
36918 ========== h_config_replace_add ==========
36919 Replace ignores the current default, Add places the current default in your
36920 editing buffer as if you had typed it in.
36921 ========== h_config_insert_after ==========
36922 Enter a nickname for this print command. (InsertBefore puts the new item
36923 before the current line, InsertAfter puts it after the current line.)
36924 ========== h_config_print_cmd ==========
36925 Enter command to be executed for the printer. Use normal editing keys
36926 to modify, ^C to cancel, carriage return to accept current value.
36927 ========== h_config_role_del ==========
36928 Answering Yes will remove this rule completely from your rules list.
36929 ========== h_config_role_addfile ==========
36930 Type the name of a file to add to your configuration. You don't need to
36931 use a file, you may add rules directly (with Add) without using a file.
36932 ========== h_config_role_delfile ==========
36933 Answering Yes will remove this rule file completely from your rules list.
36934 The rules data file itself will not be removed.
36935 ========== h_config_print_del ==========
36936 Answering Yes will remove this printer completely from your printer list.
36937 ========== h_config_print_name_cmd ==========
36938 You may edit the Nickname of this printer, the Command to be executed when
36939 printing, or change the Options associated with this printer.
36940 ========== h_send_check_fcc ==========
36941 Yes, send message without an Fcc.
36942 No, return to composer.
36943 ========== h_send_check_subj ==========
36944 Yes, send message without a Subject.
36945 No, return to composer.
36946 ========== h_send_check_to_cc ==========
36947 Yes, send message without a To address, or a Cc address, or a Newsgroup.
36948 No, return to composer.
36949 ========== h_send_fcc_only ==========
36950 Yes, copy message to Fcc only and send to NO recipients.
36951 No, return to composer.
36952 ========== h_send_prompt ==========
36953 Yes, send the message.
36954 No or ^C, return to composer.
36955 ========== h_send_prompt_flowed ==========
36956 Yes, send the message. No or ^C, return to composer.
36957 What's Flowed? See Do Not Send Flowed Text in config screen.
36958 ========== h_send_prompt_dsn ==========
36959 Yes, send the message. No or ^C, return to composer.
36960 What's DSNOpts? See Enable Delivery Status Notification in config screen.
36961 ========== h_send_prompt_dsn_flowed ==========
36962 Yes, send the message. No or ^C, return to composer. What's DSNOpts? See
36963 Enable Delivery Status Notification. What's Flowed? See Do Not Send Flowed Text.
36964 ========== h_role_confirm ==========
36965 Yes, use displayed role. No, compose without a role.
36966 ^C, cancel the message. ^T, select a role from your other eligible roles.
36967 ========== h_norole_confirm ==========
36968 Return, compose without a role.
36969 ^C, cancel the message. ^T, select a role from your eligible roles.
36970 ========== h_custom_print ==========
36971 Enter a Unix command that accepts its data on standard input.
36972 Alpine will display any information the command sends to standard output.
36973 ========== h_convert_abooks_and_sigs ==========
36974 You will be given the opportunity to convert address books and signature files
36975 to remote configurations.
36976 ========== h_convert_abooks ==========
36977 You will be given the opportunity to convert address books to remote
36979 ========== h_flag_keyword ==========
36980 Enter the name of the keyword you want to add for this folder.
36981 No spaces, parentheses, braces, percents or asterisks are allowed.
36982 ========== h_select_keyword ==========
36983 Enter the keyword you want to match, or use ^T to select a keyword from a list
36984 of possible keywords for this folder. Use ! to look for non-matches instead.
36985 ========== h_type_keyword ==========
36986 Enter the keyword you want to add. You may add a nickname in the next step.
36987 No spaces, parentheses, braces, percents or asterisks are allowed.
36988 ========== h_type_keyword_nickname ==========
36989 Enter an optional nickname for the keyword you want to add.
36990 Type Carriage return to use the keyword name instead of a nickname.
36991 ========== h_convert_sigs ==========
36992 You will be given the opportunity to convert signature files to remote
36994 ========== h_convert_abook ==========
36995 Yes is fairly safe. You will be ADDing a remote address book that is a copy
36996 of the current address book. The current abook won't be removed automatically.
36997 ========== h_convert_sig ==========
36998 Answering Yes copies the contents of the signature file into your Alpine
36999 configuration file. After that, the contents of the file will not be used.
37000 ========== h_save_addman ==========
37001 Enter the simple name of the folder you want to add. Carriage return to
37002 accept what you have typed so far. ^C to get back to SELECT FOLDER screen.
37003 ========== h_reopen_folder ==========
37004 Yes reopens the folder, as if you were starting over. This uncovers new mail.
37005 No leaves the folder index as it was without discovering new mail.
37006 ========== h_convert_pinerc_server ==========
37007 This is the name of the host (computer) where the remote Alpine configuration
37008 will be stored. This should be an IMAP server that you have permission to use.
37009 ========== h_convert_pinerc_folder ==========
37010 Enter the correct remote folder name. This folder is special and should
37011 contain only configuration data. It shouldn't contain other mail messages.
37012 ========== h_role_compose ==========
37013 Compose a New message, Reply to current message, Forward current message, or
37014 Bounce message. Then you will be asked to choose one of your Roles to be used.
37015 ========== h_role_aggregate ==========
37016 Compose a reply, or forward, or bounce the selected messages. Then you
37017 will be asked to choose one of your Roles to be used for this operation.
37018 ========== h_save_size_changed ==========
37019 The reported size of a message is not the same as the actual size. Answer Yes
37020 to continue and hope for the best or No to Cancel the entire Save.
37021 ========== h_select_by_larger_size ==========
37022 Enter a number or ^C to cancel. All messages greater than this many characters
37023 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
37024 ========== h_select_by_smaller_size ==========
37025 Enter a number or ^C to cancel. All messages less than this many characters
37026 in size will be selected. Examples: 2176, 1.53K (1530), or 3M (3000000).
37027 ========== h_preserve_field ==========
37028 Use 'p' to toggle between preserving or not preserving the original To:
37029 and Cc: fields of the message. Enter ^C to cancel message.